阅读说明：本技术 无线通信中的资源块分配技术 (Resource block allocation techniques in wireless communications ) 是由 M.霍什内维桑 张晓霞 J.孙 T.罗 S.耶拉马利 K.查克拉博蒂 A.钦达马莱坎南 于 2020-05-20 设计创作，主要内容包括：本文描述的方面涉及新无线电(NR)中时域单载波波形处理的资源块分配。具体地,在一个方面,可以在时域或频域中为单载波波形分配保护频带。在另一方面,可以为时域单载波波形分配资源块。(Aspects described herein relate to resource block allocation for time-domain single carrier waveform processing in a New Radio (NR). In particular, in one aspect, guard bands may be allocated for single carrier waveforms in the time or frequency domain. In another aspect, resource blocks may be allocated for a time-domain single-carrier waveform.)

1. A method for wireless communication at a User Equipment (UE), comprising:

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 transmission or reception according to the single carrier waveform and based on the determined guard band allocation; and

and transmitting or receiving the data to a network entity according to the single-carrier waveform and the determined guard band allocation.

2. The method of claim 1, wherein the guard band allocation corresponds to at least one of a fixed ratio of allocated bandwidths or a function of one or more non-bandwidth parameters.

3. The method of claim 2, wherein the fixed ratio is configured by Radio Resource Control (RRC), and wherein the one or more non-bandwidth parameters comprise a Modulation Coding Scheme (MCS).

4. The method of claim 1, wherein determining the guard band allocation comprises receiving the guard band allocation from the network entity for at least one of the time domain or frequency domain processing.

5. The method of claim 1, wherein configuring data for transmission or reception comprises:

selecting at least one of the time domain or frequency domain processes; and

sending a selection of at least one of the time domain or frequency domain processes to the network entity.

6. The method of claim 1, wherein the guard band allocation is further 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.

7. The method of claim 6, wherein the indication of frequency domain processing in the capability signaling indicates at least one of an optional guard band allocation or an unprotected guard band allocation.

8. The method of claim 6, wherein the indication of both time and frequency domain processing triggers selection of the guard band allocation by the network entity.

9. The method of claim 8, wherein determining the guard band allocation comprises receiving a guard band allocation indication from the network entity, the guard band allocation indication corresponding to at least one of a presence or an absence of the guard band allocation.

10. The method of claim 9, wherein configuring data for transmission or reception comprises processing configuration data based on a frequency domain in response to receiving a guard band allocation corresponding to an absence of the guard band allocation or processing configuration data based on a time domain in response to receiving a guard band allocation corresponding to a presence of the guard band allocation.

11. The method of claim 1, wherein determining the guard band allocation is based on determining whether a guard band indication is received from the 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).

12. A method for wireless communication at a network entity, comprising:

determining a guard band allocation of a single carrier waveform associated with at least one of time domain or frequency domain processing for a User Equipment (UE); and

transmitting an indication including the guard band allocation to the UE.

13. The method of claim 12, wherein determining the guard band allocation comprises:

selecting at least one of the time domain or frequency domain processes; and

transmitting a selection of at least one of the time domain or frequency domain processing to the UE.

14. The method of claim 12, wherein the indication comprising the guard band allocation indicates a presence or absence of a guard band.

15. The method of claim 12, further comprising receiving a capability indication from the UE indicating at least one of time domain processing, frequency.

16. An apparatus for wireless communication, comprising:

a transceiver;

a memory configured to store instructions; and

at least one processor communicatively coupled with the transceiver and the memory, wherein the at least one processor is configured to:

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 transmission or reception according to the single carrier waveform and based on the determined guard band allocation; and

and transmitting or receiving the data to a network entity according to the single-carrier waveform and the determined guard band allocation.

17. The apparatus of claim 16, wherein the guard band allocation corresponds to at least one of a fixed ratio of allocated bandwidths or a function of one or more non-bandwidth parameters.

18. The apparatus of claim 17, wherein the fixed ratio is configured by Radio Resource Control (RRC), and wherein the one or more non-bandwidth parameters comprise a Modulation Coding Scheme (MCS).

19. The apparatus of claim 16, wherein to determine the guard band allocation, the at least one processor is further configured to receive the guard band allocation from the network entity for at least one of the time domain or frequency domain processing.

20. The apparatus of claim 16, wherein to configure data for transmission or reception, the at least one processor is further configured to:

selecting at least one of the time domain or frequency domain processes; and

sending a selection of at least one of the time domain or frequency domain processes to the network entity.

21. The apparatus of claim 16, wherein the guard band allocation is further 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.

22. The apparatus of claim 21, wherein the indication of frequency domain processing in the capability signaling indicates at least one of an optional guard band allocation or an unprotected guard band allocation.

23. The apparatus of claim 21, wherein the indication of both time and frequency domain processing triggers selection of the guard band allocation by the network entity.

24. The apparatus of claim 23, wherein to determine the guard band allocation, the at least one processor is further configured to receive a guard band allocation indication from the network entity, the guard band allocation indication corresponding to at least one of a presence or an absence of the guard band allocation.

25. The apparatus of claim 24, wherein to configure data for transmission or reception, the at least one processor is further configured to configure data based on frequency domain processing in response to receiving a guard band allocation corresponding to an absence of the guard band allocation or to configure data based on time domain processing in response to receiving a guard band allocation corresponding to a presence of the guard band allocation.

26. The apparatus of claim 16, wherein the guard band allocation is determined based on whether a guard band indication is received from the 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).

27. An apparatus for wireless communication, comprising:

a transceiver;

a memory configured to store instructions; and

at least one processor communicatively coupled with the transceiver and the memory, wherein the at least one processor is configured to:

determining a guard band allocation of a single carrier waveform associated with at least one of time domain or frequency domain processing for a User Equipment (UE); and

transmitting an indication including the guard band allocation to the UE.

28. The apparatus of claim 27, wherein to determine a guard band allocation, the at least one processor is further configured to:

selecting at least one of the time domain or frequency domain processes; and

sending the selection of the at least one of the time domain or frequency domain processing to the UE.

29. The apparatus of claim 27, wherein the indication comprising a guard band allocation indicates a presence or absence of a guard band.

30. The apparatus of claim 27, in which the at least one processor is further configured to receive a capability indication from the UE indicating at least one of time domain processing, frequency.

Technical Field

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

Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. 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.

These multiple access techniques have been employed in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate on a city, country, region, or even global level. For example, fifth generation (5G) wireless communication technologies, which may be referred to as 5G new radios (5G NRs), are envisioned to extend and support different usage scenarios and applications with respect to the current mobile network generation. In one aspect, the 5G communication technology may include: enhanced mobile broadband addresses human-centric use cases for accessing multimedia content, services and data; ultra-reliable low-latency communications (URLLC), with certain latency and reliability specifications; and a large number of machine-type communications, which may allow for the transmission of a very large number of connected devices and a relatively small amount of non-delay sensitive information.

For example, for various communication technologies, such as but not limited to NR, the increase in bandwidth may lead to implementation complexity with respect to efficiently operating resource block allocations. Accordingly, there may be a need for improved wireless communication operations.

Disclosure of Invention

The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate 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 the more detailed description that is presented later.

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 transmitting or receiving data to a network entity according to the single carrier waveform and the determined guard band allocation.

In a further aspect, the disclosure includes an apparatus for wireless communication 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 in accordance with the single carrier waveform and based on the determined guard band allocation, and transmit or receive data to a network entity in accordance with the single carrier waveform and the determined guard band allocation.

In yet another aspect, the disclosure includes an apparatus for wireless communication, comprising 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 in accordance with the single carrier waveform and based on the determined guard band allocation, and means for transmitting or receiving data to a network entity in accordance with the single carrier waveform and the determined guard band allocation.

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 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 in accordance with the single carrier waveform and based on the determined guard band allocation, and transmit or receive data to a network entity in accordance with the single carrier waveform and the determined guard band allocation.

According to another example, a method of 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 transmitting an indication including a guard band allocation to the UE.

In a further aspect, the disclosure includes an apparatus for wireless communication 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 to transmit an indication including the guard band allocation to the UE.

In yet another aspect, the disclosure includes an apparatus for wireless communication, 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 transmitting, to the UE, an indication comprising the guard band allocation.

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

According to yet another example, a method of wireless communication at a UE is provided. The method includes determining a resource block allocation of 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 transmitting or receiving data to a network entity according to the single carrier waveform and the determined resource block allocation.

In a further aspect, the disclosure includes an apparatus for wireless communication 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 of a single carrier waveform associated with time domain processing, configure data for transmission or reception in accordance with the single carrier waveform and based on the determined resource block allocation, and transmit or receive data to a network entity in accordance with the single carrier waveform and the determined resource block allocation.

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

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 of 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.

According to another example, a method of wireless communication at a network entity is provided. The method includes determining a resource block allocation of 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.

In a further aspect, the disclosure includes an apparatus for wireless communication 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 of a single carrier waveform associated with time domain processing for a UE and transmit an indication including the resource block allocation to the UE.

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

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

To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed and the description is intended to include all such aspects and their equivalents.

Drawings

The disclosed aspects will hereinafter be described in conjunction with the appended drawings, provided to illustrate and not to limit the disclosed aspects, wherein like designations denote like elements, and in which:

fig. 1 illustrates an example of a wireless communication system in accordance with various aspects of the present disclosure;

fig. 2 is a block diagram illustrating an example of a UE in accordance with various aspects of the present disclosure;

fig. 3 is a block diagram illustrating an example of a base station in accordance with various aspects of the present disclosure;

fig. 4 is a flow diagram illustrating an example of a method for determining a guard band allocation at a UE in accordance with various aspects of the present disclosure;

fig. 5 is a flow diagram illustrating an example of a method for determining a guard band allocation at a network entity in accordance with various aspects of the present disclosure;

fig. 6 is a flow diagram illustrating an example of a method for determining resource block allocation at a UE in accordance with various aspects of the present disclosure;

fig. 7 is a flow diagram illustrating an example of a method for determining resource block allocation at a network entity in accordance with various aspects of the present disclosure;

fig. 8 is a conceptual diagram of one or more example single carrier waveform implementations in accordance with various aspects of the present disclosure;

fig. 9 illustrates a conceptual diagram of one or more example single carrier waveform implementations at a transmitter and receiver in accordance with various aspects of the present disclosure;

fig. 10 illustrates example guard band and resource block allocations in accordance with various aspects of the present disclosure; and

fig. 11 is a block diagram illustrating an example of a MIMO communication system including a base station and a UE in accordance with various aspects of the present disclosure.

Detailed Description

Various aspects are now described with reference to the drawings. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects. It may be evident, however, that such aspect(s) may be practiced without these specific details.

The described features generally relate to resource block allocation for time-domain single carrier waveform processing for higher frequency band operation, including a frequency range greater than 52.6GHz, which may be referred to as frequency range four (FR 4). For 5G NR, communication in the FR4 spectrum may occur between 52-115GHz in the licensed and/or unlicensed bands. In particular, the complexity of 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, time domain implementations of single carrier waveforms with cyclic prefix insertion may be used, which are less complex than frequency domain implementations of OFDM waveforms or single carrier waveforms. For a time-domain implementation of a single-carrier waveform, a guard band may be required due to the bandwidth increase associated with the time-domain implementation of the single-carrier waveform, which in turn may have different filter designs applied to different allocated bandwidths. For resource block allocation, the allocation for each User Equipment (UE) may be contiguous 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 a bandwidth quantization level). In contrast, frequency domain implementations may be more flexible (e.g., in terms of the possible number of resource blocks). Further, the precise 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 time-domain implementations of single carrier waveforms.

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., other than bandwidth), such as the assigned 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, guard bands may always be allocated/presented (allocated) for single carrier waveforms. In addition to the resources allocated for downlink and uplink transmissions, the gNB may always ensure enough guard bands to allow time or frequency domain processing. A node (e.g., a UE or a gNB) may select time or frequency domain processing in transmission or reception. The selection may be known by the transmitter and the receiver.

In another example of a guard band allocation, the guard band may be allocated based on capability signaling (e.g., from the UE to the gNB) or RRC, Medium Access Control (MAC) Control Element (CE), or Downlink Control Information (DCI) signaling (e.g., from the gNB to the UE). The UE may indicate the capability of frequency domain or time domain implementation of a single carrier waveform for transmit or receive processing. Further, the gNB may indicate the presence or absence of a guard band. In particular, if the UE indicates the time domain only in the capability signaling, the guard band may always be presented. If the UE indicates the frequency domain only in the capability signaling, the guard band may not be allocated (e.g., or optional). If the UE indicates both in capability signaling, the guard band allocation may be handled at the grant of the gNB, which indicates the selection to the UE. If a guard band is not allocated, the UE may perform frequency domain processing (e.g., allow time domain processing only when a guard band is allocated). The signaling to the UE may be through RRC signaling, or may be activated through MAC-CE, or dynamically activated through DCI. If indicated by the DCI, cross-slot scheduling (k0>0) may be applied to the UE to detect the DCI and utilize the corresponding processing accordingly. Within the scheduling offset, the UE may apply previous (e.g., ongoing) processing or may configure (e.g., configure default operations) based on a semi-static time or frequency domain configuration.

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 according to 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., the gNB) can determine a guard band allocation for the UE for a single carrier waveform associated with at least one of time domain or frequency domain processing. The network entity may also send an indication to the UE including a guard band allocation.

According to one of many examples, resource block allocations (i.e., frequency domain resource allocations) can be determined for time domain implementations of single carrier waveforms. In one example, semi-static resource block allocation (e.g., RRC configuration) may be implemented. In particular, resource block allocations to the UE may be semi-statically allocated through RRC signaling. The semi-static allocation may vary based on a predetermined pattern indicated via a network entity (e.g., the 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 slots. The DCI may be used for scheduling of all parameters except Frequency Domain Resource Allocation (FDRA). The resource block allocation may be determined separately from the RRC configuration pattern (e.g., a first resource block allocation may be used if the PDSCH/PUSCH is authorized to be scheduled in a first set of slots; a second resource block allocation may be used if in a second set of slots).

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

In a further example of resource block allocation, the UE may be configured by RRC signaling with a set of resource block allocations. The UE may be assigned to different resource block allocations via the DCI (e.g., a resource block allocation selected from the set above, or a resource block allocation given directly in the DCI). The UE may apply appropriate filtering for signal extraction/generation based on the DCI along with cross-slot scheduling. The core set may have a semi-static bandwidth allocation. In some aspects, all other scheduling parameters may be from the same DCI. In some aspects related to two-stage DCI, the first stage DCI from the earlier may control resource block allocation. However, the DCI may be cross-slot (e.g., to set aside 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 actually scheduled, the first stage changing RB allocation with scheduling).

In examples related to resource block allocation, different resource block allocations may be associated with different numbers, 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 a core set configuration obtained from the PBCH. Further, the temporary handover 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 handover gap may be defined. During the handover gap, the UE/gNB may not be able to send or receive data. Further, resource block allocation in the frequency domain may be applied to data and control.

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 the handover gap, the UE may not be able to transmit or receive. The above aspects are applicable to all resource block allocation scenarios.

In some aspects, a mechanism may be provided to switch back to the initial resource block allocation. The duration may or may not be related or associated with the handover gap. Rather, the duration may be based on a timer, e.g., 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 gap described above) and may transmit and/or receive using the new resource block allocation, and once the timer expires, the UE may return to the initial resource block allocation (e.g., after the gap described above). In some aspects, the initial resource allocation may be determined according to a configuration received on the PBCH. The above aspects may be applicable to MAC-CE based or DCI based scenarios, but in some aspects are not semi-static scenarios.

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) can determine a resource block allocation for a single carrier waveform associated with time domain processing for a UE. The network entity may further send an indication to the UE including the resource block allocation.

The described features will be described in more detail below with reference to fig. 1-11.

As used in this application, the terms "component," "module," "system," and the like are intended to include a computer-related entity, such as but not limited to hardware, software, a combination of hardware and software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components can reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets, such as data from one component interacting with another component in a local system, distributed system, and/or across a network such as the internet with other systems by way of the signal. Software shall be construed broadly to mean instructions, instruction sets, code segments, program code, programs, subroutines, software modules, applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

The techniques described herein may be used for 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 may implement a radio technology such as CDMA2000, Universal Terrestrial Radio Access (UTRA), and so on. CDMA2000 covers IS-2000, IS-95 and IS-856 standards. IS-2000 releases 0 and A are commonly referred to as CDMA 20001X, 1X, etc. IS-856(TIA-856) IS commonly referred to as CDMA 20001 xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes wideband CDMA (wcdma) and other variants of CDMA. TDMA systems may implement radio technologies such as global system for mobile communications (GSM). OFDMA systems may 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^TMAnd the like. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). 3GPP Long Term Evolution (LTE) and LTE-advanced (LTE-A) are new versions of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE-A, and GSM are described in documents from an organization named "third Generation partnership project" (3 GPP). CDMA2000 and UMB are described in documents from an organization named "third generation partnership project 2" (3GPP 2). The techniques described herein may be used for the above-described systems and radio technologies, as well as other systems and radio technologies, including cellular (e.g., LTE) communications over a shared radio frequency spectrum band. However, the following description describes an LTE/LTE-a system for purposes of example, and LTE terminology is used in much of the following description, 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).

The following description provides examples, and does not limit the scope, applicability, or examples set forth in the claims. Changes may be made in the function and arrangement of elements discussed without departing from the scope of the disclosure. Various examples may omit, replace, or add various procedures or components as appropriate. For example, the described methods may be performed in an order different than described, and various steps may be added, omitted, or combined. In addition, features described with respect to some examples may be combined in other examples.

Various aspects or features will be presented in terms of systems that may include a number of devices, components, modules, and the like. It is to 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 connection with the figures. Combinations of these schemes may also be used.

Fig. 1 is a diagram illustrating an example of a wireless communication system and an access network 100. A 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. Base station 102 may include a macro cell (high power cellular base station) and/or a small cell (low power cellular base station). The macro cell may include a base station. Small cells may include femto cells, pico cells, and micro cells. In an example, base station 102 can also include a gNB 180, as further described herein. In one example, some nodes of a wireless communication system can have a modem 240 and a communication component 242 for determining guard bands and/or resource block allocations, as described herein. Additionally, some nodes can have a modem 340 and a configuration component 342 for determining guard band and/or resource block allocations, as described herein. Although UE 104 is shown with modem 240 and communication component 242, base station 102/gNB 180 is shown with modem 340 and configuration component 342, which 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 for providing the respective functionality described herein.

A base station 102 configured for 4G LTE, which may be collectively referred to as an evolved Universal Mobile Telecommunications System (UMTS) terrestrial radio access network (E-UTRAN), may interface with the EPC 160 over a backhaul link 132 (e.g., using an S1 interface). A base station 102 configured for a 5G NR, which may be collectively referred to as a next generation RAN (NG-RAN), may interface with a 5GC 190 over a backhaul link 184. Base station 102 may perform one or more of the following functions, among others: 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 delivery of warning messages. Base stations 102 may communicate with each other directly or indirectly (e.g., through EPC 160 or 5GC 190) over backhaul link 134 (e.g., using X2 interface). The backhaul link 134 may be wired or wireless.

A base station 102 may wirelessly communicate 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. The 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 techniques including spatial multiplexing, beamforming, and/or transmit diversity. The communication link may be through one or more carriers. The base station 102/UE 104 may use a spectrum up to a Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth for each carrier allocated in carrier aggregation for a total of yxmhz (e.g., for x component carriers) for transmitting in the DL and/or UL directions. 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 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).

In another example, certain 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. 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.

The wireless communication system may further include a Wi-Fi Access Point (AP)150 that communicates with Wi-Fi Stations (STAs) 152 in the 5GHz unlicensed spectrum over a communication link 154. When communicating in the unlicensed spectrum, the STA152/AP 150 may perform a Clear Channel Assessment (CCA) prior to the communication in order to determine whether the channel is available.

The small cell 102' may operate in licensed and/or unlicensed spectrum. When operating in unlicensed spectrum, the small cell 102' may employ NR and use the same 5GHz unlicensed spectrum as used by the Wi-Fi AP 150. Small cells 102' employing NR in the unlicensed spectrum may improve coverage and/or increase capacity of the access network.

The base station 102, whether a small cell 102' or a large cell (e.g., a macro base station), may include an eNB, a g-node b (gnb), or other type of base station. Some base stations, such as the gNB 180, may operate in the conventional sub-6 GHz spectrum, at millimeter wave (mmW) frequencies, and/or near mmW frequencies to communicate with the UE 104. When gNB 180 is operating at or near mmW, gNB 180 may be referred to as an mmW base station. Extremely High Frequencies (EHF) are part of the RF in the electromagnetic spectrum. The EHF has a frequency in the range of 30GHz to 300GHz and a wavelength between 1 mm and 10 mm. The radio waves of this band may be referred to as millimeter waves. Near mmW may extend below 3GHz frequency with a wavelength of 100 mm. The ultra-high frequency (SHF) band extends between 3GHz and 30GHz, also known as centimeter waves. Communications using the mmW/near mmW radio frequency band have extremely high path loss and short range. The mmW base station 180 may utilize beamforming 182 with the UE 104 to compensate for extremely high path loss and short range. Base station 102 as referred to herein may include a gNB 180.

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. MME 162 may communicate with Home Subscriber Server (HSS) 174. MME 162 is a control node that handles signaling between UE 104 and EPC 160. Generally, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the serving gateway 166, and the serving gateway 166 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 BM-SC 170 are connected to an IP service 176. IP services 176 may include the internet, intranets, IP Multimedia Subsystem (IMS), PS streaming services, 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 transmissions, may be used to authorize and initiate MBMS bearer services within a Public Land Mobile Network (PLMN), and may be used to schedule MBMS transmissions. The MBMS gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area broadcasting a particular service and may be responsible for session management (start/stop) and for collecting MBMS-related charging information.

The 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. The AMF 192 may communicate with a Unified Data Management (UDM) 196. The AMF 192 may be a control node that processes signaling between the UE 104 and the 5GC 190. In general, 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 the UPF 195. The UPF195 may provide UE IP address assignment and other functionality for one or more UEs. The UPF195 is connected to the IP service 197. The IP services 197 may include the internet, intranets, IP Multimedia Subsystem (IMS), PS streaming services, and/or other IP services.

A base station may also be referred to as a gbb, 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. The base station 102 provides an access point for the UE 104 to the EPC 160 or the 5GC 190. Examples of UEs 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 player), cameras, game consoles, tablets, smart devices, robots, drones, industrial/manufacturing devices, wearable devices (e.g., smart watches, smart clothing, smart glasses, virtual reality goggles, smart wristbands, smart jewelry (e.g., smart rings, smart)), vehicles/in-vehicle devices, meters (e.g., parking meters, electricity meters, gas meters, water meters, flow meters), air pumps, large or small kitchen appliances, medical/healthcare devices, implants, sensors/actuators, A display or any other similar functional device. Some UEs 104 may be referred to as IoT devices (e.g., meters, pumps, monitors, cameras, industrial/manufacturing devices, 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 this disclosure, eMTC and NB-IoT may refer to future technologies that may evolve from or may be based on these technologies. For example, emtcs may include femmtc (further eMTC), efmtc (further enhanced eMTC), MTC (large scale 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, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, or some other suitable terminology.

2-11, aspects are depicted with reference to one or more components and one or more methods that may perform the acts or operations described herein, where aspects in dashed lines may be optional. 4-7 are presented in a particular order and/or performed by example components, it should be understood that the order of the actions and the components performing the actions may vary depending on the implementation. Further, it should be understood that the following acts, functions and/or described components may occur to those ordinarily skilled in the art upon reading and writing a computer program product from a memory or other device.

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

In an aspect, the one or more processors 212 may include a modem 240 and/or may be part of the modem 240 using one or more modem processors. Thus, various functions associated with the communications 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 modem 240 and/or one or more processors 212 associated with the communication component 242 may be performed by the transceiver 202.

Further, the memory 216 may be configured to store data used herein and/or local versions of the application 275 or the communication component 242 and/or one or more subcomponents thereof that are executed by the at least one processor 212. The memory 216 may include any type of computer-readable medium usable by the computer or at least one processor 212, such as Random Access Memory (RAM), Read Only Memory (ROM), magnetic tape, magnetic disk, optical disk, volatile memory, non-volatile memory, and any combination thereof. In an 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.

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 comprising instructions and being stored in a memory (e.g., a computer-readable medium). The receiver 206 may be, for example, a Radio Frequency (RF) receiver. In an aspect, receiver 206 may receive signals transmitted by at least one base station 102. In addition, receiver 206 may process such received signals and may also obtain measurements of signals such as, but not limited to, Ec/Io, signal-to-noise ratio (SNR), Reference Signal Received Power (RSRP), Received Signal Strength Indicator (RSSI), and the like. The transmitter 208 may include hardware and/or software executable by a processor for transmitting data, the code comprising instructions and being stored in a memory (e.g., a computer-readable medium). Suitable examples of transmitter 208 may include, but are not limited to, an RF transmitter.

Further, in an aspect, the UE 104 may include an RF front end 288, which may be in communication with the one or more antennas 265 and the transceiver 202 for receiving and transmitting radio transmissions, e.g., wireless communications transmitted by the at least one base station 102 or wireless transmissions transmitted by the UE 104. The RF front end 288 may be connected to 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.

In one aspect, LNA290 may amplify the received signal at a desired output level. In one aspect, each LNA290 may have prescribed minimum and maximum gain values. In one aspect, the RF front end 288 may use one or more switches 292 to select a particular LNA290 and its specified gain value based on the desired gain value for a particular application.

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

Additionally, for example, the RF front end 288 may filter the received signal using one or more filters 296 to obtain an input RF signal. Similarly, in one aspect, for example, a respective filter 296 may be used to filter the output from a respective PA 298 to produce an output signal for transmission. In one aspect, each filter 296 may be connected to a prescribed LNA290 and/or PA 298. In one aspect, the RF front end 288 may use one or more switches 292 to select transmit or receive paths using specific filters 296, LNAs 290, and/or PAs 298, based on the configuration specified by the transceiver 202 and/or processor 212.

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

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 such that the digital data is transmitted and received using the transceiver 202. In one aspect, the modem 240 may be multi-band and configured to support multiple bands of a prescribed communication protocol. In one aspect, the modem 240 may be multi-mode and configured to support multiple operating networks and communication protocols. In an aspect, the modem 240 may control one or more components of the UE 104 (e.g., the RF front end 288, the transceiver 202) to enable transmission and/or reception of signals from the network based on a specified modem configuration. In one aspect, the modem configuration may be based on the mode of the modem and the frequency band used. In another aspect, the modem configuration may be based on UE configuration information associated with the UE 104 provided by the network during cell selection and/or cell reselection.

In an aspect, communications component 242 can optionally include a guard band allocation component 252 and a resource block allocation component 254, guard band allocation component 252 for determining guard band allocations, as further described herein with respect to fig. 4; resource block allocation component 254 is used to determine resource block allocations as further described herein with respect to fig. 6.

In an aspect, the one or more processors 212 may correspond to the one or more processors described in connection with the UE in fig. 11. Similarly, memory 216 may correspond to the memory described in connection with the UE in fig. 11.

With reference to fig. 3, one 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 including components such as one or more processors 312 and memory 316 and transceiver 302 in communication via one or more buses 344, which may operate in conjunction with modem 340 and configuration component 342 to schedule or otherwise enable use of resources to send random access messages, send response messages for random access messages, and so forth.

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

In an aspect, configuration component 342 can optionally include a guard band allocation component 352 and a resource block allocation component 354, guard band allocation component 352 for determining a guard band allocation, as further described herein with respect to fig. 5; resource block allocation component 354 is used to determine resource block allocation as further described herein with respect to fig. 7.

In an aspect, the one or more processors 312 may correspond to the one or more processors described in connection with the base station in fig. 11. Similarly, memory 316 may correspond to the memory described in connection with the base station in fig. 11.

Fig. 4 shows a flow diagram of an example of a method 400 for determining a guard band allocation at a UE. In one example, the UE 104 may perform the functions described in the method 400 using one or more of the components described in fig. 1, 2, and 11.

At block 402, the method 400 may determine a guard band allocation for a single carrier waveform associated with at least one of time domain or frequency domain processing. In an aspect, guard band allocation component 252, e.g., in conjunction with one or more processors 212, memory 216, transceiver 202, communication component 242, and/or the like, 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.

In some aspects, the guard band allocation may correspond to at least one of a fixed ratio of allocated bandwidths or a function of one or more non-bandwidth parameters. In some aspects, the fixed ratio may be configured by RRC, and the one or more non-bandwidth parameters include MCS. In some aspects, determining the guard band allocation may include receiving the 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 a time domain or a frequency domain process and transmitting the selection of the at least one of the time domain or the frequency domain process to the network entity.

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.

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 unprotected band allocation.

In some aspects, the indication of both time and frequency domain processing triggers selection of a guard band allocation by a network entity.

In some aspects, determining the 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.

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 allocation corresponding to the absence of guard bands, or configuring data based on time domain processing in response to receiving a guard band allocation corresponding to the presence of guard bands.

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.

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

At block 406, the method 400 may transmit or receive data to a network entity according to the single carrier waveform and the determined guard band allocation. In an aspect, guard band allocation component 252, e.g., in conjunction with one or more processors 212, memory 216, transceiver 202, communication component 242, and/or the like, can be configured to transmit or receive data to a network entity in accordance with a single carrier waveform and the determined guard band allocation.

Fig. 5 shows a flowchart of an example of a method 500 for wireless communication at the network entity 102. In an example, base station 102 can perform the functions described in method 500 using one or more of the components described in fig. 1, 3, and 11.

At block 502, the 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 an aspect, preamble determining component 252, e.g., in conjunction with one or more processors 212, memory 216, transceiver 202, communication component 242, and/or the like. Can transmit to a base station (e.g., base station 102), 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 for a UE.

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

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

In some aspects, the indication comprising the guard band allocation indicates the presence or absence of a guard band.

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

At block 504, the method 500 sends an indication to the UE including a guard band allocation. In an aspect, preamble determining component 252, e.g., in conjunction with one or more processors 212, memory 216, transceiver 202, communicating component 242, and/or the like, may be configured to transmit to a base station (e.g., base station 102), may be configured to transmit to a UE an indication including a guard band allocation.

Fig. 6 shows a flow diagram of an example of a method 400 for determining a guard band allocation at a UE. In one example, the UE 104 may perform the functions described in the method 600 using one or more of the components described in fig. 1, 2, and 11.

At block 602, the method 600 may determine a resource block allocation for a single carrier waveform associated with time domain processing. In an aspect, resource block allocation component 262, e.g., in conjunction with one or more of processor 212, memory 216, transceiver 202, communication component 242, and/or the like, can be configured to determine a resource block allocation of a single carrier waveform associated with time domain processing.

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

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

In some aspects, 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 the MAC CE.

In some aspects, determining the resource block allocation comprises receiving a MAC CE.

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

In some aspects, determining a resource block allocation of a single carrier waveform associated with time domain processing may include receiving an assignment of one or more different resource block allocations via DCI. In some aspects, the DCI includes a first stage cross-slot DCI that controls resource block allocation and a second stage DCI that indicates scheduling parameters.

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

Although not shown, 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.

In some aspects, the handover duration may be defined based on at least one of DCI including an indication of the handover duration, RRC signaling, or a MAC entity at the start of a random access procedure.

In some aspects, the resource block allocations are associated with at least one of different numerology, cyclic prefix length, guard interval length, or guard band.

In some aspects, resource block allocation is applied to one or both of data or control channel communications.

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

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

Fig. 7 shows a flowchart of an example of a method 700 for wireless communication at the network entity 102. In one example, base station 102 can perform the functions described in method 700 using one or more of the components described in fig. 1, 3, and 11.

At block 702, the methodology 700 can determine a resource block allocation for a single carrier waveform associated with time domain processing for a UE. In an aspect, preamble determining component 252, e.g., in conjunction with one or more processors 212, memory 216, transceiver 202, communicating component 242, and/or the like, can transmit to a base station (e.g., base station 102), which can be configured to determine a resource block allocation for a single carrier waveform associated with time domain processing for a UE.

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

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

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

At block 704, the method 700 may send an indication including a resource block allocation to the UE. In an aspect, the preamble determining component 252, e.g., in conjunction with the one or more processors 212, memory 216, transceiver 202, communicating component 242, and/or the like, may be configured to transmit to a base station (e.g., base station 102), may be configured to transmit to a UE an indication including a resource block allocation.

Fig. 8 is a conceptual diagram of one or more single carrier waveform implementations 800. In particular, the one or more single-carrier waveform realizations 800 may include Orthogonal Frequency Division Multiple Access (OFDMA)802 in a Long Term Evolution (LTE) uplink, single-carrier frequency division multiple access (SC-FDMA)804 in a Long Term Evolution (LTE) uplink, and single-carrier waveform realizations 806 in the time domain. Compared to OFDM, a single carrier waveform may have a lower peak-to-average power ratio (PAPR), which may increase cell coverage. Further, low complexity implementations of single carrier waveforms may be critical for higher frequency bands, such as the frequency range four (FR4) (>52.6 GHz). In the case of wide bandwidths (>1-2GHz bandwidth), the sampling rate can be very high. Single carrier waveforms may allow for potential time domain processing to reduce complexity. Further, due to pulse shaping, at the cost of increased bandwidth (e.g., guard bands may be needed).

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

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

Fig. 11 is a block diagram of a MIMO communication system 1100 that includes a base station 102 and a UE 104. The MIMO communication system 1100 may illustrate aspects of the wireless communication access network 100 described in fig. 1. Base station 102 may be an example of aspects of base station 102 described in fig. 1. The base station 102 may be equipped with antennas 1134 and 1135 and the UE 104 may be equipped with antennas 1152 and 1153. In the MIMO communication system 1100, the base station 102 may be capable of transmitting data over multiple communication links simultaneously. Each communication link may be referred to as a "layer," and the "rank" of a communication link may indicate the number of layers used for communication. For example, in a2 × 2MIMO communication system in which the base station 102 transmits two "layers," the rank of the communication link between the base station 102 and the UE 104 is 2.

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

The UE 104 may be an example of aspects of the UE 104 described in fig. 1-2. At the UE 104, UE antennas 1152 and 1153 may receive the DL signals from the base station 102 and may provide the received signals to modulators/demodulators 1154 and 1155, respectively. Each modulator/demodulator 1154-1155 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each modulator/demodulator 1154-1155 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 1156 may obtain received symbols from modulators/demodulators 1154 and 1155, perform MIMO detection on the received symbols, if applicable, and provide detected symbols. A 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 a processor 1180 or a memory 1182.

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

On the Uplink (UL), at the UE 104, a transmit processor 1164 may receive and process data from a data source. Transmit processor 1164 may also generate reference symbols for the reference signal. The symbols from transmit processor 1164 may be precoded by a transmit MIMO processor 1166 if applicable, further processed by modulators/demodulators 1154 and 1155 (e.g., for SC-FDMA, etc.), and transmitted to base station 102 based on the communication parameters received from base station 102. At base station 102, the UL signals from 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 processor 1140 or memory 1142.

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

The components of the UE 104 may be implemented, individually or collectively, with one or more ASICs adapted to perform some or all of the applicable functions in hardware. Each particularly presented module may be a means for performing one or more functions associated with the operation of MIMO communication system 1100. Similarly, components of base station 102 may be implemented individually or collectively with one or more ASICs adapted to perform some or all of the applicable functions in hardware. Each particularly contemplated component may be a means for performing one or more functions associated with the operation of MIMO communication system 1100.

Some further examples

In one example, a method for wireless communication at a user equipment comprises: 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 transmission or reception according to the single carrier waveform and based on the determined guard band allocation; and transmitting or receiving data to a network entity according to the single carrier waveform and the determined guard band allocation.

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 allocated bandwidths or a function of one or more non-bandwidth parameters.

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 Coding Scheme (MCS).

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

One or more of the above examples may further include wherein the data configured for transmission or reception comprises: selecting at least one of a time domain or a frequency domain process; and sending the selection of the at least one of the time domain or frequency domain processing to a network entity.

One or more of the above examples may further include wherein the guard band allocation is determined further 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.

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 unprotected guard band allocation.

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

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

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 responsive to receiving a guard band allocation corresponding to the guard band not being present, or configuring the data based on time domain processing responsive to receiving a guard band allocation corresponding to the guard band being present.

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).

In one example, a method for wireless communication at a network entity, comprising: determining a guard band allocation of a single carrier waveform associated with at least one of time domain or frequency domain processing for a User Equipment (UE); and transmitting an indication including the guard band allocation to the UE.

One or more of the above examples may further include wherein determining the guard band allocation comprises: selecting at least one of a time domain or a frequency domain process; and transmitting the selection of the at least one of the time domain or the frequency domain processing to the UE.

One or more of the above examples may further include wherein the indication of the guard band allocation is included 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).

One or more of the above examples may further include wherein the indication of the guard band allocation is included to indicate a presence or absence of a guard band.

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

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

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.

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

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).

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).

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

One or more of the above examples may further include wherein determining a resource block allocation of a single carrier waveform associated with time domain processing comprises receiving an assignment of one or more different resource block allocations via Downlink Control Information (DCI).

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.

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 including determining whether a switching duration to switch to the second resource block allocation has been met.

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

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.

One or more of the above examples may further include wherein the resource block allocations are associated with at least one of different numerology, cyclic prefix length, guard interval length, or guard band.

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.

In one example, 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); and transmitting an indication including the resource block allocation to the UE.

One or more of the above examples may further include wherein the indication is sent via Radio Resource Control (RRC) signaling based on a semi-static assignment of resource blocks.

One or more of the above examples may further include wherein the indication corresponds to a Media Access Control (MAC) Control Element (CE).

One or more of the above examples may further include wherein the indication corresponds to Downlink Control Information (DCI).

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.

The detailed description set forth above in connection with the appended drawings describes examples and is not intended to represent the only examples that may be implemented or within the scope of the claims. The term "exemplary" when used in this description means "serving as an example, instance, or illustration," and not "preferred" or "superior to other examples. The detailed description includes specific details for the purpose of providing an understanding of the described technology. However, these techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the examples.

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

The various illustrative blocks and components described in connection with the present disclosure may be implemented or performed 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 in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A specially programmed processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The functions described herein may be implemented in hardware, software, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a non-transitory computer-readable medium. Other examples and implementations are within the scope and spirit of the disclosure and the following claims. For example, due to the nature of software, the functions described above may be implemented using software executed by a specially programmed processor, hardware, hardwired, or any combination of these. Features that perform a function may also be physically located at different positions, including being distributed such that portions of the function are performed at different physical locations. Furthermore, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or" that is, unless stated otherwise, or clear from context, the phrase, e.g., "X employs a or B" is intended to mean any of the natural inclusive permutations. That is, for example, the phrase "X employs a or B" is satisfied by any of the following examples: x is A; x adopts B, or X adopts A and B; also, as used herein, including in the claims, "or" as used in a list of items beginning with "at least one" means a disjunctive list such that a list of, for example, "A, B or at least one of C" means a or B or C or AB or AC or BC or ABC (a and B and C).

Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code means in the form of instructions or data structures and which can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a 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.

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