Method and apparatus for wireless communication at user equipment and network entity

Abstract

Aspects described herein relate to apparatuses and methods for wireless communication at a UE and at a network entity. A method for wireless communication at a UE includes determining a resource block allocation for a single carrier waveform associated with time domain processing, where the resource block allocation is determined based on one of (a) a semi-static assignment of resource blocks via RRC signaling and varies based on a predetermined pattern, or (b) receiving a MAC CE, sending an acknowledgement to a network entity; or (c) receiving an assignment of one or more different resource block allocations via a DCI, where the DCI includes a first stage cross-slot DCI that controls resource block allocations and a second stage DCI that indicates scheduling parameters other than resource block allocations, and utilizing the resource block allocations for a period of time after sending an acknowledgement to the network entity, or (c) receiving an assignment of one or more different resource block allocations via the DCI, where the DCI includes a first stage cross-slot DCI that controls the resource block allocations; configuring data for transmission or reception according to the single carrier waveform and based on the resource block allocation; and transmitting or receiving data to the network entity according to the single carrier waveform and the resource block allocation.

Description

[0001] This application is a divisional application of the invention patent application with application number 202080035783.0 and invention name “Resource Block Allocation Technology in Wireless Communications” filed on May 20, 2020.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This patent application claims priority to U.S. Non-Provisional Application No. 16 / 877,834, filed on May 19, 2020, entitled “TECHNIQUES FOR RESOURCE BLOCK ALLOCATION IN WIRELESS COMMUNICATIONS,” and U.S. Provisional Application Serial No. 62 / 850,207, filed on May 20, 2019, entitled “TECHNIQUES FOR RESOURCE BLOCK ALLOCATION IN WIRELESS COMMUNICATIONS,” the entire contents of which are expressly incorporated herein by reference. Technical Field

[0004] Aspects of the present disclosure relate generally to wireless communication systems and, more particularly, to resource block allocation for time-domain single-carrier waveform processing. Background Art

[0005] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, etc. These systems may be multiple-access systems capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, and single-carrier frequency division multiple access (SC-FDMA) systems.

[0006] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, or even global level. For example, the fifth generation (5G) wireless communication technology, which may be referred to as 5G New Radio (5G NR), is envisioned to extend and support different usage scenarios and applications with respect to current mobile network generations. In one aspect, 5G communication technologies may include: enhanced mobile broadband addressing human-centric use cases for accessing multimedia content, services, and data; ultra-reliable low latency communications (URLLC) with certain latency and reliability specifications; and massive machine-type communications, which may allow for very large numbers of connected devices and the transmission of relatively small amounts of non-latency sensitive information.

[0007] For example, for various communication technologies, such as but not limited to NR, the increase in bandwidth may lead to implementation complexity regarding resource block allocation for efficient operation. Therefore, there may be a need to improve wireless communication operations. Summary of the invention

[0008] A simplified summary of one or more aspects is presented below in order to provide a basic understanding of these aspects. This summary is not an extensive overview of all contemplated aspects, and is neither intended to identify key or important elements of all aspects, nor to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description that is presented later.

[0009] According to an example, a method of wireless communication at a user equipment (UE) is provided. The method includes determining a guard band allocation for a single carrier waveform associated with at least one of time domain or frequency domain processing. The method further includes configuring data for transmission or reception according to the single carrier waveform and based on the determined guard band allocation. The method further includes sending or receiving data to a network entity according to the single carrier waveform and the determined guard band allocation.

[0010] In a further aspect, the disclosure includes an apparatus for wireless communication, the apparatus comprising a memory and at least one processor coupled to the memory. The at least one processor may be configured to determine a guard band allocation for a single carrier waveform associated with at least one of time domain or frequency domain processing, configure data for transmission or reception according to the single carrier waveform and based on the determined guard band allocation, and transmit or receive data to a network entity according to the single carrier waveform and the determined guard band allocation.

[0011] In yet another aspect, the disclosure includes an apparatus for wireless communication, the apparatus including means for determining a guard band allocation for a single carrier waveform associated with at least one of time domain or frequency domain processing, means for configuring data for transmission or reception according to the single carrier waveform and based on the determined guard band allocation, and means for transmitting or receiving data to a network entity according to the single carrier waveform and the determined guard band allocation.

[0012] In another aspect, the present disclosure includes a computer-readable medium storing computer-executable code that, when executed by a processor, causes the processor to determine a guard band allocation for a single carrier waveform associated with at least one of time domain or frequency domain processing, configure data for transmission or reception according to the single carrier waveform and based on the determined guard band allocation, and transmit or receive data to a network entity according to the single carrier waveform and the determined guard band allocation.

[0013] According to another example, a method for wireless communication at a network entity is provided. The method includes determining, for a UE, a guard band allocation for a single carrier waveform associated with at least one of time domain or frequency domain processing. The method further includes sending an indication including the guard band allocation to the UE.

[0014] In a further aspect, the disclosure includes an apparatus for wireless communication, the apparatus comprising a memory and at least one processor coupled to the memory. The at least one processor may be configured to determine, for a UE, a guard band allocation for a single carrier waveform associated with at least one of time domain or frequency domain processing, and send an indication including the guard band allocation to the UE.

[0015] In yet another aspect, the disclosure includes an apparatus for wireless communication, the apparatus comprising means for determining, for a UE, a guard band allocation for a single carrier waveform associated with at least one of time domain or frequency domain processing, and means for sending an indication including the guard band allocation to the UE.

[0016] In another aspect, the present disclosure includes a computer-readable medium storing computer-executable code that, when executed by a processor, causes the processor to determine, for a UE, a guard band allocation for a single carrier waveform associated with at least one of time domain or frequency domain processing, and to send an indication to the UE including the guard band allocation.

[0017] According to yet another example, a method of wireless communication at a UE is provided. The method includes determining a resource block allocation for a single carrier waveform associated with time domain processing. The method further includes configuring data for transmission or reception according to the single carrier waveform and based on the determined resource block allocation. The method further includes sending or receiving data to a network entity according to the single carrier waveform and the determined resource block allocation.

[0018] In a further aspect, the disclosure includes an apparatus for wireless communication, the apparatus comprising a memory and at least one processor coupled to the memory. The at least one processor may be configured to determine a resource block allocation for a single carrier waveform associated with time domain processing, configure data for transmission or reception according to the single carrier waveform and based on the determined resource block allocation, and transmit or receive data to a network entity according to the single carrier waveform and the determined resource block allocation.

[0019] In yet another aspect, the disclosure includes an apparatus for wireless communication, the apparatus including means for determining a resource block allocation for a single carrier waveform associated with time domain processing, means for configuring data for transmission or reception according to the single carrier waveform and based on the determined resource block allocation, and means for transmitting or receiving data to a network entity according to the single carrier waveform and the determined resource block allocation.

[0020] In another aspect, the disclosure includes a computer-readable medium storing computer-executable code that, when executed by a processor, causes the processor to determine a resource block allocation for a single carrier waveform associated with time domain processing, configure data for transmission or reception according to the single carrier waveform and based on the determined resource block allocation, and transmit or receive data to a network entity according to the single carrier waveform and the determined resource block allocation.

[0021] According to another example, a method of wireless communication at a network entity is provided. The method includes determining a resource block allocation for a single carrier waveform associated with time domain processing for a UE. The method further includes sending an indication including the resource block allocation to the UE.

[0022] In a further aspect, the disclosure includes an apparatus for wireless communication, the apparatus comprising a memory and at least one processor coupled to the memory. The at least one processor may be configured to determine a resource block allocation for a single carrier waveform associated with time domain processing for a UE and send an indication including the resource block allocation to the UE.

[0023]

[0011] In yet another aspect, the disclosure includes an apparatus for wireless communication comprising means for determining, for a UE, a resource block allocation of a single carrier waveform associated with time domain processing, and means for sending an indication including the resource block allocation to the UE.

[0024] In another aspect, the disclosure includes a computer-readable medium storing computer-executable code that, when executed by a processor, causes the processor to determine a resource block allocation for a single carrier waveform associated with time-domain processing for a UE and send an indication including the resource block allocation to the UE.

[0025] To accomplish the foregoing and related ends, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail certain illustrative features of one or more aspects. However, these features are indicative of only some of the various ways in which the principles of the various aspects may be employed, and this description is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The disclosed aspects will be described below in conjunction with the accompanying drawings, which are provided to illustrate and not to limit the disclosed aspects, wherein like reference numerals represent like elements, and wherein:

[0027] Figure 1 An example of a wireless communication system according to various aspects of the present disclosure is shown;

[0028] Figure 2 is a block diagram illustrating an example of a UE according to various aspects of the present disclosure;

[0029] Figure 3 is a block diagram illustrating an example of a base station according to various aspects of the present disclosure;

[0030] Figure 4 is a flow chart illustrating an example of a method for determining guard band allocation at a UE according to various aspects of the present disclosure;

[0031] Figure 5 is a flow chart illustrating an example of a method for determining guard band allocation at a network entity according to various aspects of the present disclosure;

[0032] Figure 6 is a flow chart illustrating an example of a method for determining resource block allocation at a UE according to various aspects of the present disclosure;

[0033] Figure 7 is a flow chart illustrating an example of a method for determining resource block allocation at a network entity according to various aspects of the present disclosure;

[0034] Figure 8 is a conceptual diagram of one or more example single carrier waveform implementations according to various aspects of the present disclosure;

[0035] Fig. 9 A conceptual diagram illustrating one or more example single carrier waveform implementations at a transmitter and a receiver according to various aspects of the present disclosure;

[0036] Fig.10 shows example guard band and resource block allocations in accordance with various aspects of the present disclosure; and

[0037] Fig.11 is a block diagram illustrating an example of a MIMO communication system including a base station and a UE according to various aspects of the present disclosure. DETAILED DESCRIPTION

[0038] Various aspects are now described with reference to the accompanying drawings. In the following description, for the purpose of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects. However, it is apparent that these aspects can be implemented without these specific details.

[0039] The described features generally relate to resource block allocation for time domain single carrier waveform processing for higher frequency band operation, including frequency ranges greater than 52.6 GHz, which may be referred to as frequency range four (FR4). For 5G NR, communications in the FR4 spectrum may occur between 52-115 GHz in licensed and / or unlicensed bands. Specifically, the complexity of the FFT operation may increase with increasing bandwidth (in FR4, the bandwidth may be greater than 1 or 2 GHz). For frequency domain implementations of OFDM waveforms or single carrier waveforms, FFT operations are required. As such, as bandwidth increases, a time domain implementation of a single carrier waveform with cyclic prefix insertion may be used, which has less complexity than a frequency domain implementation of an OFDM waveform or single carrier waveform. For time domain implementations of single carrier waveforms, due to the bandwidth growth associated with the time domain implementation of a single carrier waveform, guard bands may be required, which may accordingly have different filter designs applied to different allocated bandwidths. For resource block allocations, the allocations for each user equipment (UE) may be continuous in a single carrier waveform. Depending on the complexity of the time domain implementation, the number of allocated resource blocks may be limited (e.g., may be allocated at the bandwidth quantization level). In contrast, a frequency domain implementation may be more flexible (e.g., in terms of the possible number of resource blocks). Further, the exact location of the limited contiguous resource blocks may be flexible. For example, appropriate phase ramping or radio frequency retuning may move the signal to the desired frequency location. As such, it may be desirable to address the allocation of guard bands and resource blocks for a time domain implementation of a single carrier waveform.

[0040] For guard band allocation, the number of guard bands may be a fixed ratio of the allocated bandwidth. Alternatively, the fixed ratio may be a radio resource control (RRC) configuration. Further, the number of guard bands may be a function of other parameters (e.g., in addition to bandwidth), such as the allocated modulation and coding scheme (MCS). The mapping between the guard bands and those parameters may be an RRC configuration. In one example of guard band allocation, the guard bands may always be allocated / assumed for a single carrier waveform. In addition to the resources allocated for downlink and uplink transmissions, the gNB may always ensure sufficient guard bands to allow time or frequency domain processing. A node (e.g., UE or gNB) may select time or frequency domain processing in transmission or reception. The selection may be known to the transmitter and receiver.

[0041] In another example of guard band allocation, the guard band may be allocated based on capability signaling (e.g., from UE to gNB) or RRC, media access control (MAC) control element (CE), or downlink control information (DCI) signaling (e.g., from gNB to UE). The UE may indicate the capability of frequency domain or time domain implementation of a single carrier waveform for transmission or reception processing. Further, the gNB may indicate the presence or absence of the guard band. Specifically, if the UE indicates only the time domain in the capability signaling, the guard band may always be present. If the UE indicates only the frequency domain in the capability signaling, the guard band may not be allocated (e.g., or may be optional). If the UE indicates both in the capability signaling, the guard band allocation may be at the discretion of the gNB, which indicates a choice to the UE. If the guard band is not allocated, the UE may perform frequency domain processing (e.g., time domain processing is allowed only when the guard band is allocated). Signaling to the UE may be done through RRC signaling, or may be activated through MAC-CE, or dynamically activated through DCI. If indicated by DCI, cross-slot scheduling (k0>0) can be applied to the UE to detect the DCI and utilize corresponding processing accordingly. Within the scheduling offset, the UE can apply the previous (e.g., ongoing) processing, or can be based on a semi-static time domain or frequency domain configuration (e.g., configure default operation).

[0042] For example, the UE may determine a guard band allocation for a single carrier waveform associated with at least one of time domain or frequency domain processing. The UE may further configure data for transmission or reception based on the single carrier waveform and based on the determined guard band allocation. The UE may further transmit or receive data to a network entity based on the single carrier waveform and the determined guard band allocation. Further, the network entity (e.g., gNB) may determine a guard band allocation for a single carrier waveform associated with at least one of time domain or frequency domain processing for the UE. The network entity may also send an indication including the guard band allocation to the UE.

[0043] According to one of multiple examples, a resource block allocation (i.e., frequency domain resource allocation) can be determined for a time domain implementation of a single carrier waveform. In one example, a semi-static resource block allocation (e.g., RRC configuration) can be implemented. Specifically, the resource block allocation to the UE can be semi-statically allocated via RRC signaling. The semi-static allocation can vary based on a predetermined pattern indicated via a network entity (e.g., a gNB). For example, the resource block allocation (e.g., based on the number and location of resource blocks) may be different in different sets of time slots. In addition to the frequency domain resource allocation (FDRA), DCI can be used for scheduling of all parameters. The resource block allocation can be determined separately from the RRC configuration pattern (e.g., if PDSCH / PUSCH is authorized to be scheduled in a first set of time slots, a first resource block allocation can be used; if in a second set of time slots, a second resource block allocation can be used).

[0044] In another example of resource block allocation, the resource block allocation can be based on MAC-CE. A set of resource block allocations can be configured by RRC and activated by MAC-CE; or the resource block allocation can be provided directly in MAC-CE (e.g., without configuring the set in RRC). The resource block allocation in MAC-CE may take effect after a defined duration ('x' milliseconds) (e.g., x = 3 milliseconds) after the UE issues an acknowledgement corresponding to the PDSCH carrying the MAC-CE. DCI can be used for scheduling of all parameters except FDRA. Activating a resource block allocation by MAC-CE may not mean that PDSCH / PUSCH is authorized, but rather means that if authorized by DCI, the resource block allocation (i.e., FDRA) can be used.

[0045] In a further example of resource block allocation, the UE may be configured via RRC signaling with a set of resource block allocations. The UE may be assigned to different resource block allocations (e.g., resource block allocations selected from the above set, or resource block allocations given directly in the DCI) via DCI. The UE may apply appropriate filtering to signal extraction / generation based on the DCI together with cross-slot scheduling. The core set may have a semi-static bandwidth allocation. In some aspects, all other scheduling parameters may come from the same DCI. In some aspects related to two-stage DCI, the earlier arriving first-stage DCI may control resource block allocations. However, the DCI may be cross-slot (e.g., to allow preparation time for the UE). The second-stage DCI may indicate other scheduling parameters. The second-stage DCI may be faster (e.g., within a slot). The first-stage DCI may not need to be issued as frequently as the second-stage DCI (e.g., the second-stage DCI may be the one that is actually scheduled, and the first stage changes the RB allocation in the case of scheduling).

[0046] In an example related to resource block allocation, different resource block allocations may be associated with different numerologies, such as subcarrier spacing (SCS), cyclic prefix (CP) / guard interval (GI) length, and / or guard band. The initial resource block allocation may be obtained from the core set configuration obtained from the PBCH. Further, temporary switching may allow a timer-based mechanism to switch back to the initial / default resource block allocation. After the switch, another command (e.g., MAC-CE or DCI) may be used to change the RB allocation again (e.g., including switching back). A switching gap may be defined. During the switching gap, the UE / gNB may not be able to send or receive data. Further, the resource block allocation in the frequency domain may be applied to both data and control.

[0047] In a first aspect, a switching gap may provide a change to a resource block allocation (e.g., from a given (first) resource block allocation to a new (second) resource block allocation, or vice versa). During a switching gap, the UE may not be able to transmit or receive. The above aspects may apply to all resource block allocation scenarios.

[0048] In some aspects, a mechanism for switching back to the initial resource block allocation may be provided. The duration may be related or associated with the switching gap, or may not be related or associated with the switching gap. Instead, the duration may be based on a timer, for example, when a new resource block allocation is provided to the UE, the UE may switch to the new resource block allocation (e.g., after the above gap), and may use the new resource block allocation to transmit and / or receive, and once the timer expires, the UE may return to the initial resource block allocation (e.g., after the above gap). In some aspects, the initial resource allocation may be determined based on the configuration received on the PBCH. The above aspects may be applicable to MAC-CE based or DCI based scenarios, but in some aspects, not semi-static scenarios.

[0049] In a further example, the UE may determine a resource block allocation for a single carrier waveform associated with time domain processing. The UE may further configure data for transmission or reception according to the single carrier waveform and based on the determined resource block allocation. The UE may further transmit or receive data to a network entity according to the single carrier waveform and the determined resource block allocation. In another example, a network entity (e.g., a gNB) may determine a resource block allocation for a single carrier waveform associated with time domain processing for the UE. The network entity may further send an indication including the resource block allocation to the UE.

[0050] The following will refer to Figure 1-11 The described features are described in more detail.

[0051] As used in this application, the terms "component", "module", "system", etc. are intended to include computer-related entities, such as but not limited to hardware, software, a combination of hardware and software, or software in execution. For example, a component can be, but not limited to, a process, a processor, an object, an executable file, an execution thread, a program, and / or a computer running on a processor. As an illustration, both an application running on a computing device and a computing device can be a component. One or more components can reside in a process and / or an execution thread, and a component can be located on a computer and / or distributed between two or more computers. In addition, these components can be executed from various computer-readable media having various data structures stored thereon. These components can communicate through local and / or remote processes, such as according to a signal with one or more data packets, such as data from a component, the component interacts with another component in a local system, a distributed system, and / or interacts with other systems through a network such as the Internet. Software shall be construed broadly to include instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subprograms, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0052] The technology described herein can be used in various wireless communication systems, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and other systems. The terms "system" and "network" are often used interchangeably. A CDMA system can implement radio technologies such as CDMA2000, Universal Terrestrial Radio Access (UTRA), etc. CDMA2000 covers IS-2000, IS-95 and IS-856 standards. IS-2000 versions 0 and A are often referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is often referred to as CDMA2000 1xEV-DO, High Speed ​​Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. A TDMA system can implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA systems can implement radio technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM™, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) and Advanced LTE (LTE-A) are new versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). CDMA2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). The techniques described herein can be used for the above systems and radio technologies as well as other systems and radio technologies, including cellular (e.g., LTE) communications on shared radio spectrum bands. However, the following description describes an LTE / LTE-A system for example purposes, and LTE terminology is used in much of the description below, although the techniques are applicable beyond LTE / LTE-A applications (e.g., fifth generation (5G) new radio (NR) networks or other next generation communication systems).

[0053] The following description provides examples and does not limit the scope, applicability or examples set forth in the claims. The functions and arrangements of the elements discussed may be changed without departing from the scope of the present disclosure. Various examples may appropriately omit, replace or add various processes or components. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted or combined. In addition, the features described with respect to some examples may be combined in other examples.

[0054] Various aspects or features will be presented in terms of systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that the various systems may include additional devices, components, modules, etc., and / or may not include all of the devices, components, modules, etc. discussed in conjunction with the figures. Combinations of these schemes may also be used.

[0055] Figure 1 1 is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) may include a base station 102, a UE 104, an evolved packet core (EPC) 160, and / or a 5G core (5GC) 190. The base station 102 may include a macro cell (a high power cellular base station) and / or a small cell (a low power cellular base station). A macro cell may include a base station. A small cell may include a femto cell, a pico cell, and a micro cell. In an example, the base station 102 may also include a gNB 180, as further described herein. In one example, some nodes of the wireless communication system may have a modem 240 and a communication component 242 for determining a guard band and / or resource block allocation, as described herein. Additionally, some nodes may have a modem 340 and a configuration component 342 for determining a guard band and / or resource block allocation, as described herein. Although UE 104 is shown as having modem 240 and communication component 242 and base station 102 / gNB 180 is shown as having modem 340 and configuration component 342, this is an illustrative example and substantially any node or type of node may include modem 240 and communication component 242 and / or modem 340 and configuration component 342 to provide the corresponding functionality described herein.

[0056] Base stations 102 configured for 4G LTE (which may be collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with EPC 160 via a backhaul link 132 (e.g., using an S1 interface). Base stations 102 configured for 5G NR (which may be collectively referred to as Next Generation RAN (NG-RAN)) may interface with 5GC 190 via a backhaul link 184. Among other functions, the base station 102 may perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, non-access stratum distribution (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and device tracking, RAN information management (RIM), paging, positioning, and transmission of warning messages. The base stations 102 may communicate with each other directly or indirectly (e.g., through the EPC 160 or the 5GC 190) via a backhaul link 134 (e.g., using an X2 interface). The backhaul link 134 may be wired or wireless.

[0057] The base station 102 may communicate wirelessly with one or more UEs 104. Each base station 102 may provide communication coverage for a respective geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group, which may be referred to as a closed subscriber group (CSG). The communication link 120 between the base station 102 and the UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from the UE 104 to the base station 102 and / or a downlink (downlink) (also referred to as a forward link) transmission from the base station 102 to the UE 104. The communication link 120 may use multiple input multiple output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be through one or more carriers. The base station 102 / UE 104 can use spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth for each carrier allocated in a carrier aggregation of a total of Yx MHz (e.g., for x component carriers) for transmission in the DL and / or UL direction. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​than for UL). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0058] In another example, some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through various wireless D2D communication systems, such as FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on IEEE 802.11 standards, LTE, or NR.

[0059] The wireless communication system may further include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 in the 5 GHz unlicensed spectrum via a communication link 154. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) prior to communication to determine whether the channel is available.

[0060] The small cell 102' can operate in a licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 102' can employ NR and use the same 5 GHz unlicensed spectrum used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum can improve the coverage of the access network and / or increase the capacity of the access network.

[0061] Base stations 102, whether small cells 102' or large cells (e.g., macro base stations), may include eNBs, gNode Bs (gNBs), or other types of base stations. Some base stations, such as gNB 180, may operate in traditional sub-6 GHz spectrum, in millimeter wave (mmW) frequencies, and / or near mmW frequencies to communicate with UE 104. When gNB 180 operates at mmW or near mmW frequencies, gNB 180 may be referred to as a mmW base station. Extremely high frequency (EHF) is a portion of the RF in the electromagnetic spectrum. EHF has a frequency range of 30 GHz to 300 GHz, with wavelengths between 1 mm and 10 mm. Radio waves in this band may be referred to as millimeter waves. Near mmW may extend below 3 GHz frequencies, with wavelengths of 100 mm. Super high frequency (SHF) bands extend between 3 GHz and 30 GHz, also known as centimeter waves. Communications using mmW / near mmW radio frequency bands have extremely high path loss and short range. The mmW base station 180 can utilize beamforming 182 with the UE 104 to compensate for the extremely high path loss and short distance. The base station 102 mentioned in this article can include a gNB 180.

[0062] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. Typically, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides IP address allocation to the UE, as well as other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS delivery, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS delivery. The MBMS Gateway 168 may be used to distribute MBMS services to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area that broadcasts specific services, and may be responsible for session management (start / stop) and collecting MBMS-related billing information.

[0063] 5GC 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. AMF 192 may communicate with unified data management (UDM) 196. AMF 192 may be a control node that handles signaling between UE 104 and 5GC 190. Typically, AMF 192 may provide QoS flow and session management. User Internet Protocol (IP) packets (e.g., from one or more UEs 104) may be transmitted through UPF 195. UPF 195 may provide UE IP address allocation and other functions for one or more UEs. UPF 195 is connected to IP services 197. IP services 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services.

[0064] A base station may also be referred to as a gNB, a Node B, an evolved Node B (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), or some other suitable terminology. Base station 102 provides an access point to EPC 160 or 5GC 190 for UE 104. Examples of UE 104 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, positioning systems (e.g., satellite, terrestrial), multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, robots, drones, industrial / manufacturing equipment, wearable devices (e.g., smart watches, smart clothing, smart glasses, virtual reality goggles, smart wristbands, smart jewelry (e.g., smart rings, smart bracelets)), vehicle / onboard equipment, meters (e.g., parking meters, electricity meters, gas meters, water meters, flow meters), gas pumps, large or small kitchen appliances, medical / health care equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some UE 104 may be referred to as IoT devices (e.g., meters, pumps, monitors, cameras, industrial / manufacturing equipment, appliances, vehicles, robots, drones, etc.). IoT UEs may include MTC / enhanced MTC (eMTC, also known as CAT-M, Cat M1) UEs, NB-IoT (also known as CAT NB1) UEs, and other types of UEs. In the present disclosure, eMTC and NB-IoT may refer to future technologies that may evolve from or may be based on these technologies. For example, eMTC may include FeMTC (further eMTC), eFeMTC (further enhanced eMTC), mMTC (massive MTC), etc., and NB-IoT may include eNB-IoT (enhanced NB-IoT), FeNB-IoT (further enhanced NB-IoT), etc. UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a mobile phone, a user agent, a mobile client, a client, or some other suitable terminology.

[0065] Now go to Figure 2-11 , various aspects are depicted with reference to one or more components and one or more methods that can perform the actions or operations described herein, where aspects in dashed lines may be optional. Figure 4-7The operations described in the present invention are presented in a particular order and / or performed by example components, but it should be understood that the order of actions and the components performing the actions may vary depending on the implementation. Further, it should be understood that the following actions, functions, and / or components described may be performed by a specially programmed processor, a processor executing specially programmed software or computer-readable media, or any other combination of hardware components and / or software components capable of performing the described actions or functions.

[0066] refer to Figure 2 , an example of an implementation of UE 104 may include various components, some of which have been described above and are further described herein, including components such as one or more processors 212 and memory 216 communicating via one or more buses 244 and a transceiver 202, which may operate in conjunction with a modem 240 and / or a communication component 242 for sending random access messages.

[0067] In one aspect, the one or more processors 212 may include the modem 240 and / or may be part of the modem 240 using one or more modem processors. Thus, various functions associated with the communication component 242 may be included in the modem 240 and / or the processor 212, and in one aspect, may be performed by a single processor, while in other aspects, different functions may be performed by a combination of two or more different processors. For example, in one aspect, the one or more processors 212 may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receiver processor, or a transceiver processor associated with the transceiver 202. In other aspects, some features of the one or more processors 212 and / or the modem 240 associated with the communication component 242 may be performed by the transceiver 202.

[0068] Further, the memory 216 may be configured to store data used herein and / or local versions of the applications 275 or the communication component 242 and / or one or more subcomponents thereof executed by the at least one processor 212. The memory 216 may include any type of computer-readable medium usable by a computer or the at least one processor 212, such as a random access memory (RAM), a read-only memory (ROM), a tape, a disk, an optical disk, a volatile memory, a non-volatile memory, and any combination thereof. In one aspect, for example, the memory 216 may be a non-transitory computer-readable storage medium that stores one or more computer-executable codes defining the communication component 242 and / or one or more subcomponents thereof and / or data associated therewith when the UE 104 operates the at least one processor 212 to execute the communication component 242 and / or one or more subcomponents thereof.

[0069] The transceiver 202 may include at least one receiver 206 and at least one transmitter 208. The receiver 206 may include hardware and / or software executable by a processor for receiving data, the code including instructions and stored in a memory (e.g., a computer-readable medium). The receiver 206 may be, for example, a radio frequency (RF) receiver. In one aspect, the receiver 206 may receive a signal transmitted by at least one base station 102. In addition, the receiver 206 may process such a received signal and may also obtain measurement values ​​of the signal, such as, but not limited to, Ec / Io, signal-to-noise ratio (SNR), reference signal received power (RSRP), received signal strength indicator (RSSI), etc. The transmitter 208 may include hardware and / or software executable by a processor for transmitting data, the code including instructions and stored in a memory (e.g., a computer-readable medium). Suitable examples of the transmitter 208 may include, but are not limited to, an RF transmitter.

[0070] Further, in one aspect, the UE 104 may include an RF front end 288 that may be in communication with the one or more antennas 265 and the transceiver 202 for receiving and transmitting radio transmissions, such as wireless communications transmitted by at least one base station 102 or wireless transmissions transmitted by the UE 104. The RF front end 288 may be connected to the one or more antennas 265 and may include one or more low noise amplifiers (LNAs) 290, one or more switches 292, one or more power amplifiers (PAs) 298, and one or more filters 296 for transmitting and receiving RF signals.

[0071] In one aspect, the LNA 290 can amplify the received signal at a desired output level. In one aspect, each LNA 290 can have a specified minimum and maximum gain value. In one aspect, the RF front end 288 can use one or more switches 292 to select a particular LNA 290 and its specified gain value based on the desired gain value for a particular application.

[0072] Further, for example, the RF front end 288 can use one or more PAs 298 to amplify the RF output signal at a desired output power level. In one aspect, each PA 298 can have a specified minimum and maximum gain value. In one aspect, the RF 288 can use one or more switches 292 to select a specific PA 298 and its specified gain value based on the desired gain value for a particular application.

[0073] In addition, for example, the RF front end 288 can use one or more filters 296 to filter the received signal to obtain an input RF signal. Similarly, in one aspect, for example, a corresponding filter 296 can be used to filter the output from the respective PA 298 to produce an output signal for transmission. In one aspect, each filter 296 can be connected to a specified LNA 290 and / or PA 298. In one aspect, based on the configuration specified by the transceiver 202 and / or the processor 212, the RF front end 288 can use one or more switches 292 to select a transmit or receive path using a specific filter 296, LNA 290, and / or PA 298.

[0074] As such, the transceiver 202 may be configured to transmit and receive wireless signals through one or more antennas 265 via the RF front end 288. In one aspect, the transceiver may be tuned to operate at a specified frequency so that the UE 104 may communicate with, for example, one or more base stations 102 or one or more cells associated with the one or more base stations 102. In one aspect, the modem 240 may configure the transceiver 202 to operate at a specified frequency and power level based on, for example, the UE configuration of the UE 104 and the communication protocol used by the modem 240.

[0075] In one aspect, the modem 240 can be a multi-band multi-mode modem that can process digital data and communicate with the transceiver 202 so that the digital data is sent and received using the transceiver 202. In one aspect, the modem 240 can be multi-band and configured to support multiple frequency bands of a specified communication protocol. In one aspect, the modem 240 can be multi-mode and configured to support multiple operating networks and communication protocols. In one aspect, the modem 240 can control one or more components (e.g., RF front end 288, transceiver 202) of the UE 104 to enable the transmission and / or reception of signals from the network based on a specified modem configuration. In one aspect, the modem configuration can be based on the mode of the modem and the frequency band used. In another aspect, the modem configuration can be based on UE configuration information associated with the UE 104 provided by the network during cell selection and / or cell reselection.

[0076] In one aspect, the communication component 242 can optionally include a guard band allocation component 252 and a resource block allocation component 254, wherein the guard band allocation component 252 is used to determine the guard band allocation, as described herein. Figure 4 As further described; resource block allocation component 254 is used to determine resource block allocation, as described herein Figure 6 Further described.

[0077] In one aspect, the one or more processors 212 may correspond to a processor that is associated with Fig.11 Similarly, the memory 216 may correspond to the one or more processors described in conjunction with the UE. Fig.11 The memory described by the UE in .

[0078] refer to Figure 3 , an example of an implementation of a base station 102 (e.g., base station 102 and / or gNB 180 as described above) may include various components, some of which have been described above, but include components such as one or more processors 312 and memory 316 and a transceiver 302 that communicate via one or more buses 344, which may operate in conjunction with a modem 340 and a configuration component 342 to schedule or otherwise enable the use of resources to send random access messages, send response messages to random access messages, and the like.

[0079] The transceiver 302, receiver 306, transmitter 308, one or more processors 312, memory 316, applications 375, bus 344, RF front end 388, LNA 390, switch 392, filter 396, PA 398 and one or more antennas 365 can be the same as or similar to the corresponding components of UE 104 described above, but are configured or otherwise programmed for base station operation rather than UE operation.

[0080] In one aspect, configuration component 342 may optionally include a guard band allocation component 352 and a resource block allocation component 354, wherein guard band allocation component 352 is used to determine guard band allocations, as described herein. Figure 5 As further described; resource block allocation component 354 is used to determine resource block allocation, as described herein Figure 7 Further described.

[0081] In one aspect, the one or more processors 312 may correspond to a Fig.11 Similarly, the memory 316 may correspond to the one or more processors described in the base station in the embodiment of the present invention. Fig.11 The memory described by the base station in.

[0082] Figure 4 A flow chart showing an example of a method 400 for determining guard band allocation at a UE. In one example, the UE 104 may use Figure 1 , 2 and one or more components described in 11 to perform the functions described in method 400.

[0083] At block 402, method 400 can determine a guard band allocation for a single carrier waveform associated with at least one of time domain or frequency domain processing. In one aspect, guard band allocation component 252, e.g., in conjunction with one or more processors 212, memory 216, transceiver 202, communication component 242, etc., can be configured to determine a guard band allocation for a single carrier waveform associated with at least one of time domain or frequency domain processing.

[0084] In some aspects, the guard band allocation may correspond to at least one of a fixed ratio of allocated bandwidth or a function of one or more non-bandwidth parameters. In some aspects, the fixed ratio may be configured via RRC, and the one or more non-bandwidth parameters include MCS. In some aspects, determining the guard band allocation may include receiving a guard band allocation for at least one of time domain or frequency domain processing from a network entity. In some aspects, configuring data for transmission or reception may include selecting at least one of time domain or frequency domain processing, and sending the selection of at least one of time domain or frequency domain processing to the network entity.

[0085] In some aspects, the guard band allocation may be further determined based on capability signaling sent to the network entity, and the capability signaling may include an indication of at least one of time domain or frequency domain processing.

[0086] In some aspects, the indication of frequency domain processing in the capability signaling indicates at least one of an optional guard band allocation or an unguard band allocation.

[0087] In some aspects, an indication of both time domain and frequency domain processing triggers a network entity's selection of a guard band allocation.

[0088] In some aspects, determining a guard band allocation may include receiving a guard band allocation indication from a network entity, the indication corresponding to at least one of a presence of a guard band allocation or an absence of a guard band allocation.

[0089] In some aspects, configuring data for transmission or reception may include configuring data based on frequency domain processing in response to receiving a guard band assignment corresponding to the absence of a guard band, or configuring data based on time domain processing in response to receiving a guard band assignment corresponding to the presence of a guard band.

[0090] In some aspects, determining the guard band allocation is based on determining whether a guard band indication is received from a network entity, and the guard band indication corresponds to at least one of an RRC message, a MAC CE, or a DCI.

[0091] At block 404, method 400 may configure data for transmission or reception according to the single carrier waveform and based on the determined guard band allocation. In one aspect, guard band allocation component 252, e.g., in conjunction with one or more processors 212, memory 216, transceiver 202, communication component 242, etc., may be configured to configure data for transmission or reception according to the single carrier waveform and based on the determined guard band allocation.

[0092] At block 406, method 400 may transmit or receive data to a network entity based on the single carrier waveform and the determined guard band allocation. In one aspect, guard band allocation component 252, e.g., in conjunction with one or more processors 212, memory 216, transceiver 202, communication component 242, etc., may be configured to transmit or receive data to a network entity based on the single carrier waveform and the determined guard band allocation.

[0093] Figure 5 A flow chart showing an example of a method 500 for wireless communication at a network entity 102. In an example, the base station 102 may use Figure 1 , 3 and one or more components described in 11 to perform the functions described in method 500.

[0094] At block 502, method 500 determines a guard band allocation for a single carrier waveform associated with at least one of time domain or frequency domain processing for a UE. In one aspect, preamble determining component 252, for example, in combination with one or more processors 212, memory 216, transceiver 202, communication component 242, etc., may send to a base station (e.g., base station 102), which may be configured to determine a guard band allocation for a single carrier waveform associated with at least one of time domain or frequency domain processing for a UE.

[0095] In some aspects, determining the guard band allocation may include selecting at least one of time domain or frequency domain processing, and transmitting the selection of at least one of time domain or frequency domain processing to the UE.

[0096] In some aspects, the indication including the guard band allocation corresponds to at least one of an RRC message, a MAC CE, or a DCI.

[0097] In some aspects, the indication including a guard band allocation indicates the presence or absence of a guard band.

[0098] Although not shown, the method 500 may receive a capability indication from the UE, the capability indication indicating at least one of time domain processing, frequency domain processing, or both time domain and frequency domain processing.

[0099] At block 504, method 500 transmits an indication including a guard band assignment to the UE. In one aspect, preamble determining component 252, e.g., in conjunction with one or more processors 212, memory 216, transceiver 202, communication component 242, etc., may transmit to a base station (e.g., base station 102) and may be configured to transmit an indication including a guard band assignment to the UE.

[0100] Figure 6 A flow chart showing an example of a method 400 for determining guard band allocation at a UE. In one example, the UE 104 may use Figure 1 , 2 and one or more components described in 11 to perform the functions described in method 600.

[0101] At block 602, method 600 can determine a resource block allocation for a single carrier waveform associated with time domain processing. In one aspect, resource block allocation component 262, e.g., in conjunction with one or more processors 212, memory 216, transceiver 202, communication component 242, etc., can be configured to determine a resource block allocation for a single carrier waveform associated with time domain processing.

[0102] In some aspects, resource block allocation is determined based on a semi-static assignment of resource blocks via RRC signaling.

[0103] In some aspects, the semi-static assignment of resource blocks varies based on a predetermined pattern received via a network entity indication.

[0104] In some aspects, at least one resource block of the resource block allocation determined via RRC signaling based on a semi-static assignment of resource blocks is activated via a MAC CE.

[0105] In some aspects, determining the resource block allocation includes receiving a MAC CE.

[0106] In some aspects, determining the resource block allocation may include sending an acknowledgement to the network entity in response to receiving the MAC CE, and utilizing the resource block allocation within a period of time after sending the acknowledgement to the network entity.

[0107] In some aspects, determining resource block allocations for a single carrier waveform associated with time domain processing may include receiving assignments of one or more different resource block allocations via DCI. In some aspects, the DCI includes a first stage cross-slot DCI controlling resource block allocations and a second stage DCI indicating scheduling parameters.

[0108] In some aspects, determining the resource block allocation may include switching from an initial resource block allocation to the resource block allocation.

[0109] Although not shown, the method 600 may include determining whether a switching duration has been met after switching to the resource allocation, and switching from the resource block allocation to the initial resource block allocation based on determining that the switching duration has been met.

[0110] In some aspects, the switching duration may be defined based on at least one of a DCI, RRC signaling, or a MAC entity when a random access procedure is initiated that includes an indication of the switching duration.

[0111] In some aspects, the resource block allocation is associated with at least one of different parameter sets, cyclic prefix length, guard interval length, or guard band.

[0112] In some aspects, resource block allocations are applied to one or both of data or control channel communications.

[0113] At block 604, method 600 may configure data for transmission or reception according to the single carrier waveform and based on the determined resource block allocation. In one aspect, resource block allocation component 262, e.g., in conjunction with one or more processors 212, memory 216, transceiver 202, communication component 242, etc., may be configured to configure data for transmission or reception according to the single carrier waveform and based on the determined resource block allocation.

[0114] At block 606, method 600 transmits or receives data to a network entity in accordance with the single carrier waveform and the determined resource block allocation. In one aspect, resource block allocation component 262, e.g., in conjunction with one or more processors 212, memory 216, transceiver 202, communication component 242, etc., may be configured to transmit or receive data to a network entity in accordance with the single carrier waveform and the determined resource block allocation.

[0115] Figure 7 A flow chart showing an example of a method 700 for wireless communication at a network entity 102. In one example, a base station 102 may use Figure 1 , 3 and one or more components described in 11 to perform the functions described in method 700.

[0116] At block 702, method 700 can determine resource block allocations for a single carrier waveform associated with time domain processing for a UE. In one aspect, preamble determining component 252, e.g., in conjunction with one or more processors 212, memory 216, transceiver 202, communication component 242, etc., can transmit to a base station (e.g., base station 102) and can be configured to determine resource block allocations for a single carrier waveform associated with time domain processing for a UE.

[0117] In some aspects, the indication is sent via RRC signaling based on a semi-static assignment of resource blocks.

[0118] In some aspects, the indication corresponds to a MAC CE. In some aspects, the indication corresponds to a DCI.

[0119] In some aspects, the DCI includes a first stage cross-slot DCI that controls resource block allocations and a second stage DCI that indicates scheduling parameters.

[0120] At block 704, method 700 can send an indication including a resource block assignment to the UE. In one aspect, preamble determining component 252, e.g., in conjunction with one or more processors 212, memory 216, transceiver 202, communication component 242, etc., can send to a base station (e.g., base station 102) and can be configured to send an indication including a resource block assignment to the UE.

[0121] Figure 8 8 is a conceptual diagram of one or more single carrier waveform implementations 800. Specifically, one or more single carrier waveform implementations 800 may include orthogonal frequency division multiple access (OFDMA) in a long term evolution (LTE) uplink 802, single carrier frequency division multiple access (SC-FDMA) in a long term evolution (LTE) uplink 804, and a single carrier waveform implementation in the time domain 806. Compared to OFDM, a single carrier waveform may have a lower peak power to average power ratio (PAPR), which may increase cell coverage. Further, a low complexity implementation of a single carrier waveform may be critical for higher frequency bands, such as frequency range four (FR4) (>52.6 GHz). In the case of wide bandwidth (>1-2 GHz bandwidth), the sampling rate may be very high. The single carrier waveform may allow potential time domain processing to reduce complexity. Further, due to pulse shaping, there is a cost in bandwidth increase (e.g., guard bands may be required).

[0122] Fig. 9 A conceptual diagram of a single carrier waveform implementation 900 at a transmitter and receiver is shown. For example, a transmitter implementation 902 may correspond to a DFT and IFFT (e.g., higher complexity) for efficient bandwidth utilization (e.g., no guard bands are required). Further, direct time-domain pulse shaping may be implemented to reduce transmitter complexity and peak power to average power ratio (PAPR). Additionally, guard bands may be implemented for bandwidth growth. However, the transmitter implementation 902 may include additional constraints on resource allocation (RA) bandwidth selection. For example, a receive implementation 904 may be frequency domain processing to handle larger delay spreads and MIMO channels. Further, time domain equalization may be used to reduce receive complexity.

[0123] Fig.10An example guard band and resource block allocation 1000 is shown. For example, the guard band and resource block allocation 1000 may include a semi-static RA1 and the presence / absence of a guard band. The resource block allocation 1000 may further include a semi-static RA2 and the presence / absence of a guard band. Further, for example, the semi-static resource allocation may correspond to a resource block assignment, and the presence / absence of a guard band may be known via a semi-static indication. In some aspects, a DCI indication on a RA and the presence of a guard band, PDSCH / PUSCH is based on a semi-static indication, and PDSCH / PUSCH is based on a DCI. Further, cross-slot scheduling is used for dynamic RA and protection indications.

[0124] Fig.11 1 is a block diagram of a MIMO communication system 1100 including a base station 102 and a UE 104. The MIMO communication system 1100 may be shown Figure 1 The wireless communication access network 100 is described in detail. The base station 102 may be Figure 1 Examples of various aspects of base station 102 are described. Base station 102 can be equipped with antennas 1134 and 1135, and UE 104 can be equipped with antennas 1152 and 1153. In MIMO communication system 1100, base station 102 may be able to send data through multiple communication links at the same time. Each communication link can be referred to as a "layer", and the "rank" of the communication link can indicate the number of layers used for communication. For example, in a 2×2 MIMO communication system where base station 102 sends two "layers", the rank of the communication link between base station 102 and UE 104 is 2.

[0125] At the base station 102, a transmit (Tx) processor 1120 may receive data from a data source. The transmit processor 1120 may process data. The transmit processor 1120 may also generate a control symbol or a reference symbol. If applicable, the transmit MIMO processor 1130 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, or reference symbols, and may provide an output symbol stream to transmit modulators / demodulators 1132 and 1133. Each modulator / demodulator 1132 to 1133 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator / demodulator 1132 to 1133 may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a DL signal. In an example, the DL signals from modulators / demodulators 1132 and 1133 may be transmitted via antennas 1134 and 1135, respectively.

[0126] UE 104 may be Figure 1-2An example of aspects of the UE 104 described herein. At the UE 104, the UE antennas 1152 and 1153 may receive DL signals from the base station 102, and may provide received signals to modulators / demodulators 1154 and 1155, respectively. Each modulator / demodulator 1154 to 1155 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each modulator / demodulator 1154 to 1155 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. The MIMO detector 1156 may obtain received symbols from the modulator / demodulators 1154 and 1155, perform MIMO detection on the received symbols if applicable, and provide detected symbols. The receive (Rx) processor 1158 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 104 to a data output, and provide decoded control information to the processor 1180 or the memory 1182.

[0127] In some cases, processor 1180 may execute stored instructions to instantiate communication component 242 (see, e.g., Figure 1 and 2 ).

[0128] On the uplink (UL), at the UE 104, a transmit processor 1164 may receive and process data from a data source. The transmit processor 1164 may also generate reference symbols for a reference signal. If applicable, the symbols from the transmit processor 1164 may be precoded by a transmit MIMO processor 1166, further processed by modulators / demodulators 1154 and 1155 (e.g., for SC-FDMA, etc.), and transmitted to the base station 102 based on the communication parameters received from the base station 102. At the base station 102, the UL signals from the UE 104 may be received by antennas 1134 and 1135, processed by modulators / demodulators 1132 and 1133, detected by a MIMO detector 1136 (if applicable), and further processed by a receive processor 1138. The receive processor 1138 may provide decoded data to a data output and to the processor 1140 or memory 1142.

[0129] In some cases, processor 1140 may execute stored instructions to instantiate configuration component 342 (see, e.g., Figure 1 and 3 ).

[0130] The components of UE 104 may be implemented individually or collectively with one or more ASICs adapted to perform some or all applicable functions in hardware. Each specifically mentioned module may be a component for performing one or more functions related to the operation of MIMO communication system 1100. Similarly, the components of base station 102 may be implemented individually or collectively with one or more ASICs adapted to perform some or all applicable functions in hardware. Each specifically mentioned component may be a component for performing one or more functions related to the operation of MIMO communication system 1100.

[0131] Some further examples

[0132] In one example, a method for wireless communication at a user equipment includes: determining a guard band allocation for a single carrier waveform associated with at least one of time domain or frequency domain processing; configuring data for sending or receiving according to the single carrier waveform and based on the determined guard band allocation; and sending or receiving data to a network entity according to the single carrier waveform and the determined guard band allocation.

[0133] One or more of the above examples may further include, wherein the guard band allocation corresponds to at least one of a fixed ratio of the allocated bandwidth or a function of one or more non-bandwidth parameters.

[0134]

[0013] One or more of the above examples may further include, wherein the fixed ratio is configured by radio resource control (RRC), and wherein the one or more non-bandwidth parameters include a modulation and coding scheme (MCS).

[0135] One or more of the above examples may further include, wherein determining a guard band allocation comprises receiving a guard band allocation from a network entity for at least one of time domain or frequency domain processing.

[0136] One or more of the above examples may further include, wherein configuring the data for sending or receiving includes: selecting at least one of time domain or frequency domain processing; and sending the selection of at least one of time domain or frequency domain processing to the network entity.

[0137] One or more of the above examples may further include, wherein the guard band allocation is also determined based on capability signaling sent to the network entity, and wherein the capability signaling includes an indication of at least one of time domain or frequency domain processing.

[0138] One or more of the above examples may further include, wherein the indication of frequency domain processing in the capability signaling indicates at least one of an optional guard band allocation or an unguard band allocation.

[0139] One or more of the above examples may further include, wherein an indication of both time domain and frequency domain processing triggers a selection of a guard band allocation by the network entity.

[0140] One or more of the above examples may further include, wherein determining a guard band allocation comprises receiving a guard band allocation indication from a network entity, the indication corresponding to at least one of a presence of a guard band allocation or an absence of a guard band allocation.

[0141] One or more of the above examples may further include, wherein configuring the data for transmission or reception includes configuring the data based on frequency domain processing in response to receiving a guard band allocation corresponding to the absence of a guard band, or configuring the data based on time domain processing in response to receiving a guard band allocation corresponding to the presence of a guard band.

[0142] One or more of the above examples may further include, wherein determining the guard band allocation is based on determining whether a guard band indication is received from a network entity, and wherein the guard band indication corresponds to at least one of a radio resource control (RRC) message, a medium access control (MAC) control element (CE), or downlink control information (DCI).

[0143] In one example, a method for wireless communications at a network entity includes determining, for a user equipment (UE), a guard band allocation for a single carrier waveform associated with at least one of time domain or frequency domain processing; and sending an indication to the UE including the guard band allocation.

[0144] One or more of the above examples may further include, wherein determining the guard band allocation includes: selecting at least one of time domain or frequency domain processing; and sending the selection of at least one of time domain or frequency domain processing to the UE.

[0145] One or more of the above examples may further include where the indication including the guard band allocation corresponds to at least one of a radio resource control (RRC) message, a medium access control (MAC) control element (CE), or downlink control information (DCI).

[0146] One or more of the above examples may further include, wherein the indication including the guard band allocation indicates the presence or absence of the guard band.

[0147] One or more of the above examples may further include receiving a capability indication from the UE, the capability indication indicating at least one of time domain processing, frequency domain processing, or both time domain and frequency domain processing.

[0148] In one example, a method for wireless communication at a UE includes: determining a resource block allocation for a single carrier waveform associated with time domain processing; configuring data for transmission or reception according to the single carrier waveform and based on the determined resource block allocation; and sending or receiving data to a network entity according to the single carrier waveform and the determined resource block allocation.

[0149]

[0013] One or more of the above examples may further include, wherein the resource block allocation is determined based on a semi-static assignment of resource blocks via radio resource control (RRC) signaling.

[0150]

[0013] One or more of the above examples may further include, wherein the semi-static assignment of resource blocks varies based on a predetermined pattern received via a network entity indication.

[0151]

[0013] One or more of the above examples may further include, wherein at least one resource block of the resource block allocation determined based on the semi-static assignment of resource blocks via RRC signaling is activated via a medium access control (MAC) control element (CE).

[0152]

[0013] One or more of the above examples may further include, wherein determining the resource block allocation includes receiving a medium access control (MAC) control element (CE).

[0153]

[0013] One or more of the above examples may further include, wherein determining the resource block allocation comprises: sending an acknowledgement to the network entity in response to receiving the MAC CE; and utilizing the resource block allocation within a period of time after sending the acknowledgement to the network entity.

[0154]

[0013] One or more of the above examples may further include, wherein determining a resource block allocation for a single carrier waveform associated with time domain processing includes receiving an assignment of one or more different resource block allocations via downlink control information (DCI).

[0155] One or more of the above examples may further include, wherein the DCI includes a first stage cross-slot DCI that controls resource block allocation and a second stage DCI that indicates scheduling parameters other than resource block allocation.

[0156] One or more of the above examples may further include, wherein determining the resource block allocation includes switching from a first resource block allocation to a second resource block allocation, the method further includes determining whether a switching duration for switching to the second resource block allocation has been met.

[0157] One or more of the above examples may further include, wherein the switching duration is defined based on at least one of: a DCI, RRC signaling, or a MAC CE including an indication of the switching duration.

[0158] One or more of the above examples may switch from the resource block allocation to the initial resource block allocation based on determining that the switching duration has been met.

[0159] One or more of the above examples may further include, wherein the resource block allocation is associated with at least one of different parameter sets, cyclic prefix length, guard interval length, or guard band.

[0160]

[0013] One or more of the above examples may further include, wherein the resource block allocation is applied to one or both of data or control channel communications.

[0161] In one example, a method for wireless communications at a network entity includes determining a resource block allocation for a single carrier waveform associated with time domain processing for a user equipment (UE); and sending an indication including the resource block allocation to the UE.

[0162]

[0013] One or more of the above examples may further include, wherein the indication is sent based on a semi-static assignment of resource blocks via radio resource control (RRC) signaling.

[0163] One or more of the above examples may further include, wherein the indication corresponds to a medium access control (MAC) control element (CE).

[0164] One or more of the above examples may further include, wherein the indication corresponds to downlink control information (DCI).

[0165] One or more of the above examples may further include, wherein the DCI includes a first stage cross-slot DCI that controls resource block allocation and a second stage DCI that indicates scheduling parameters other than resource block allocation.

[0166] The detailed description set forth above in conjunction with the accompanying drawings describes examples and does not represent the only examples that can be implemented or within the scope of the claims. When used in this description, the term "example" means "used as an example, instance, or illustration," rather than "preferred" or "better than other examples." To provide an understanding of the described techniques, the detailed description includes specific details. However, these techniques can be implemented without these specific details. In some examples, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the examples.

[0167] Information and signals may be represented using a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, computer executable codes or instructions stored on computer-readable media, or any combination thereof.

[0168] The various illustrative blocks and components described in conjunction with the disclosure herein may be implemented or executed with a specially programmed device, such as, but not limited to, a processor, a digital signal processor (DSP), an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The specially programmed processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The specially programmed processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors and a DSP core, or any other such configuration.

[0169] The functions described herein can be implemented in hardware, software, or any combination thereof. If implemented in software executed by a processor, the functions can be stored as one or more instructions or codes on or transmitted by a non-transitory computer-readable medium. Other examples and implementations are within the scope and spirit of the present disclosure and the appended claims. For example, due to the nature of software, the above functions can be implemented using software executed by a specially programmed processor, hardware, hard wiring, or any combination of these. The features that implement the functions can also be physically located in different locations, including being distributed so that some functions are implemented in different physical locations. Moreover, the term "or" is intended to represent an inclusive "or", rather than an exclusive "or". That is, unless otherwise stated, or clearly obtained from the context, the phrase, for example, "X adopts A or B" is intended to represent any natural inclusive replacement. That is, for example, the phrase “X employs A or B” is satisfied by any of the following instances: X employs A; X employs B, or X employs A and B; and, as used herein, including in the claims, “or” used in a list of items beginning with “at least one of” means a disjunctive list, so that, for example, a list such as “at least one of A, B, or C” means A or B or C or AB or AC or BC or ABC (A and B and C).

[0170] Computer readable media include computer storage media and communication media, and communication media include any media that facilitates the transfer of computer programs from one place to another. Storage media can be any available media that can be accessed by a general-purpose or special-purpose computer. As an example and not limitation, computer readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code means in the form of instructions or data structures and can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. And, any connection is properly referred to as a computer readable medium. For example, if the 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 the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio and microwave are included in the definition of medium. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0171] The previous description of the present disclosure is provided to enable those skilled in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to those skilled in the art, and the common principles defined herein may be applied to other variations without departing from the spirit or scope of the present disclosure. Further, although the elements of the described aspects and / or embodiments may be described or claimed in the singular, the plural form is also contemplated unless a limitation to the singular is explicitly stated. Additionally, all or a portion of any aspect and / or embodiment may be used together with all or a portion of any other aspect and / or embodiment, unless otherwise stated. Therefore, the present disclosure is not limited to the examples and designs described herein, but conforms to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment, comprising: Determining a resource block allocation for a single carrier waveform associated with time domain processing, wherein the resource block allocation is determined based on one of: (a) semi-static assignment of resource blocks via Radio Resource Control (RRC) signalling, and varying based on a predetermined pattern received via network entity instructions, or (b) receiving the medium access control MAC control element CE, in response to receiving the MAC CE, sending an acknowledgement to the network entity; and utilizing the resource block allocation within a period of time after sending the acknowledgment to the network entity, or (c) receiving an assignment of one or more different resource block allocations via downlink control information (DCI), wherein the DCI comprises a first stage cross-slot DCI controlling the resource block allocations and a second stage DCI indicating scheduling parameters other than the resource block allocations; configuring data for transmission or reception according to the single carrier waveform and based on the determined resource block allocation; and The data is sent or received to a network entity according to the single carrier waveform and the determined resource block allocation.

2. The method according to claim 1, wherein: At least one resource block of said resource block allocation determined based on said semi-static assignment of resource blocks via RRC signaling is activated via a Medium Access Control MAC control element CE.

3. The method according to claim 1, wherein: Determining the resource block allocation includes switching from a first resource block allocation to a second resource block allocation, the method further comprising: It is determined whether a switching duration for switching to the second resource block allocation has been reached.

4. The method according to claim 3, wherein: The switching duration is defined based on at least one of the following: a DCI comprising an indication of said switching duration, RRC signaling, or MAC CE.

5. The method of claim 3, further comprising switching from the resource block allocation to an initial resource block allocation based on determining that the switching duration has been reached.

6. The method according to claim 5, wherein: The resource block allocation is associated with at least one of different parameter sets, cyclic prefix length, guard interval length, or guard band, and wherein the resource block allocation is applied to one or both of data or control channel communications.

7. A method for wireless communication at a network entity, comprising: determining a resource block allocation of a single carrier waveform associated with time domain processing for a user equipment UE; as well as An indication including the resource block allocation is sent to the UE, wherein the indication corresponds to downlink control information (DCI), the DCI including a first-stage cross-slot DCI controlling the resource block allocation and a second-stage DCI indicating scheduling parameters other than the resource block allocation.

8. An apparatus for wireless communication, comprising: Transceiver; a memory configured to store instructions; as well as at least one processor communicatively coupled to the transceiver and the memory, wherein the at least one processor is configured to: Determining a resource block allocation for a single carrier waveform associated with time domain processing, wherein the resource block allocation is determined based on one of: (a) semi-static assignment of resource blocks via Radio Resource Control (RRC) signalling, and varying based on a predetermined pattern received via network entity instructions, or (b) receiving the medium access control MAC control element CE, in response to receiving the MAC CE, sending an acknowledgement to the network entity; and utilizing the resource block allocation within a period of time after sending the acknowledgment to the network entity, or (c) receiving an assignment of one or more different resource block allocations via downlink control information (DCI), wherein the DCI comprises a first stage cross-slot DCI controlling the resource block allocations and a second stage DCI indicating scheduling parameters other than the resource block allocations; configuring data for transmission or reception according to the single carrier waveform and based on the determined resource block allocation; and The data is sent or received to a network entity according to the single carrier waveform and the determined resource block allocation.

9. The device according to claim 8, wherein: At least one resource block of said resource block allocation determined based on said semi-static assignment of resource blocks via RRC signaling is activated via a Medium Access Control MAC control element CE.

10. The device according to claim 8, wherein: To determine the resource block allocation, the at least one processor is further configured to switch from a first resource block allocation to a second resource block allocation, and wherein the at least one processor is further configured to: It is determined whether a switching duration for switching to the second resource block allocation has been reached.

11. The device according to claim 10, wherein: The switching duration is defined based on at least one of the following: a DCI comprising an indication of said switching duration, RRC signaling, or MAC CE.

12. The device according to claim 10, wherein: The at least one processor is further configured to switch from the resource block allocation to an initial resource block allocation based on determining that the switching duration has been reached.

13. The device according to claim 12, wherein: The resource block allocation is associated with at least one of different parameter sets, cyclic prefix length, guard interval length, or guard band, and wherein the resource block allocation is applied to one or both of data or control channel communications.

14. An apparatus for wireless communication, comprising: Transceiver; a memory configured to store instructions; as well as at least one processor communicatively coupled to the transceiver and the memory, wherein the at least one processor is configured to: determining a resource block allocation of a single carrier waveform associated with time domain processing for a user equipment UE; and An indication including the resource block allocation is sent to the UE, wherein the indication corresponds to downlink control information (DCI), the DCI including a first-stage cross-slot DCI controlling the resource block allocation and a second-stage DCI indicating scheduling parameters other than the resource block allocation.

Images