Method for scheduling offset determination in an ultra-wide bandwidth beamforming system

Abstract

Aspects presented herein can enhance configuration of scheduling offsets for communication devices within a channelized frequency band. In one aspect, a UE receives a PDCCH including a scheduling offset parameter. The PDCCH schedules one of a PDSCH for reception in a first sub-band within a BWP or provides an uplink scheduling grant for a PUSCH for transmission in a second sub-band within the BWP. The UE communicates with the base station based on one of a slot for receiving the PDSCH based on the first sub-band within the BWP and the scheduling offset parameter when the PDCCH schedules the PDSCH or a slot for transmitting the PUSCH based on the second sub-band within the BWP and the scheduling offset parameter when the PUCCH is used to schedule the PUSCH.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to Provisional Application No. 63 / 074,701, filed September 4, 2020, entitled “METHODS FOR SCHEDULING OFFSET DETERMINATION IN ULTRA WIDE BANDWIDTH BEAMFORMING SYSTEMS,” and U.S. Patent Application No. 17 / 398,843, filed August 10, 2021, entitled “METHODS FOR SCHEDULING OFFSET DETERMINATION IN ULTRA WIDE BANDWIDTH BEAMFORMING SYSTEMS,” the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] This disclosure generally relates to communication systems, and more specifically, to wireless communication including scheduling offsets in beamforming systems. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources. Examples of such multiple access technologies 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, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different wireless devices to communicate at the municipal, national, regional, and even global levels. One example of a telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Mobile Broadband Evolution (CMB) initiative issued by the 3rd Generation Partnership Project (3GPP) to meet new requirements related to latency, reliability, security, scalability (e.g., the Internet of Things (IoT)), and other requirements. 5G NR includes services related to enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. These improvements can also be applied to other multiple access technologies and telecommunications standards that adopt them. Summary of the Invention

[0006] The following is a simplified overview of one or more aspects to provide a basic understanding of such aspects. This overview is not a comprehensive overview of all anticipated aspects, and is neither intended to identify key or important elements of all aspects, nor to depict 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 descriptions that follow.

[0007] In one aspect of this disclosure, a method, computer-readable medium, and apparatus for wireless communication at a user equipment (UE) are provided. The apparatus receives a physical downlink control channel (PDCCH) including a scheduling offset parameter, wherein the PDCCH schedules one of the physical downlink shared channels (PDSCH) for reception in a first subband within a bandwidth portion (BWP), or provides uplink scheduling permission for a physical uplink shared channel (PUSCH) for transmission in a second subband within the BWP. The apparatus communicates with a base station based on a time slot used to receive the PDSCH based on the first subband within the BWP and the scheduling offset parameter when the PDCCH schedules the PDSCH, or a time slot used to transmit the PUSCH based on the second subband within the BWP and the scheduling offset parameter when the PUSCH is scheduled using a physical uplink control channel (PUCCH).

[0008] In one aspect of this disclosure, a method, computer-readable medium, and apparatus for wireless communication at a base station are provided. The apparatus transmits a PDCCH including a scheduling offset parameter, wherein the PDCCH schedules one of a PDSCH for reception by a UE in a first subband within a BWP, or provides uplink scheduling permission for a PUSCH for transmission by the UE in a second subband within the BWP. The apparatus communicates with the UE based on a time slot used for transmitting the PDSCH based on the first subband within the BWP and the scheduling offset parameter when the PDCCH schedules the PDSCH, or a time slot used for receiving the PUSCH based on the second subband within the BWP and the scheduling offset parameter when the PUCCH is used to schedule the PUSCH.

[0009] To achieve the foregoing and related objectives, one or more of the foregoing aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth certain illustrative features of one or more of the foregoing aspects in detail. However, these features indicate only a portion of the various ways in which the principles of each aspect can be employed, and this description is intended to include all such aspects and their equivalents. Attached Figure Description

[0010] Figure 1 This is a diagram illustrating examples of wireless communication systems and access networks based on some aspects.

[0011] Figure 2A , 2B Figures 2C and 2D are examples illustrating, respectively, the DL channel within a first 5G / NR frame, a 5G / NR subframe, a second 5G / NR frame, and a UL channel within a 5G / NR subframe, according to some aspects.

[0012] Figure 3 This is a diagram illustrating examples of base stations and user equipment (UEs) in an access network according to some aspects.

[0013] Figure 4 This is a diagram illustrating an example of Physical Downlink Shared Channel (PDSCH) scheduling according to various aspects of this disclosure.

[0014] Figure 5 This is a diagram illustrating an example of Physical Uplink Shared Channel (PUSCH) scheduling according to various aspects of this disclosure.

[0015] Figure 6 This is a diagram illustrating examples of channelized frequency bands according to various aspects of this disclosure.

[0016] Figure 7 This is a diagram illustrating examples of channel-based beam optimization according to various aspects of this disclosure.

[0017] Figure 8 This is a diagram illustrating an example of providing scheduling offsets based on channels according to various aspects of this disclosure.

[0018] Figure 9 This is a diagram illustrating examples of cross-carrier scheduling according to various aspects of this disclosure.

[0019] Figure 10A and 10B This is a diagram illustrating an example of a beamforming codebook according to various aspects of this disclosure.

[0020] Figure 11 This is a communication flow that illustrates an example of determining a scheduling offset based on sub-bands according to various aspects of this disclosure.

[0021] Figure 12 This is a flowchart of a wireless communication method.

[0022] Figure 13 This is a diagram illustrating an example hardware implementation of the example device.

[0023] Figure 14 This is a flowchart of a wireless communication method.

[0024] Figure 15 This is a diagram illustrating an example hardware implementation of the example device. Detailed Implementation

[0025] The detailed description following, taken in conjunction with the accompanying drawings, is intended as a description of various configurations, and not as representing only the configurations in which the concepts described herein can be practiced. The detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0026] Various apparatuses and methods will now be used to present several aspects of a telecommunications system. These apparatuses and methods will be described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements may be implemented using electronic hardware, computer software, or any combination thereof. The implementation of these elements as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0027] For example, an element, any part of an element, or any combination of elements can be implemented as a "processing system" comprising one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuitry, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more processors in a processing system can execute software. Software should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether or not referred to as software, firmware, middleware, microcode, hardware description languages, or others.

[0028] Therefore, in one or more example embodiments, the described functionality can be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality can be stored on a computer-readable medium or encoded on a computer-readable medium as one or more instructions or code. A computer-readable medium includes a computer storage medium. The storage medium can be any available medium that can be accessed by a computer. By way of example, and not limitation, such a computer-readable medium can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of computer-readable medium types, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0029] While aspects and implementations have been described in this application by way of example, those skilled in the art will understand that additional implementations and use cases may arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, implementations and / or uses may be implemented via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (AI) enabling devices, etc.). While some examples may or may not be specific to a particular use case or application, a wide variety of applicability to the described innovations is possible. The scope of implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to collections, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementation and practice that are claimed and described. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / accumulators, etc.). The innovations described herein are intended to be implemented in devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user equipment, etc., of various sizes, shapes, and constructions.

[0030] Figure 1This is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also known as a wireless wide area network (WWAN)) includes base station 102, UE 104, evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells include base stations. Small cells include femtocells, picocells, and microcells.

[0031] In some aspects, UE 104 may include a PDSCH / PUSCH configuration component 198 configured to receive PDSCH or transmit PUSCH based on a scheduling offset received from the base station. In one configuration, the PDSCH / PUSCH configuration component 198 may be configured to receive a PDCCH including scheduling offset parameters, wherein the PDCCH schedules one of the PDSCHs for reception in a first subband within the BWP, or provides uplink scheduling clearance for PUSCHs for transmission in a second subband within the BWP. In this configuration, the PDSCH / PUSCH configuration component 198 may communicate with the base station based on a time slot used to receive PDSCHs based on the first subband within the BWP and scheduling offset parameters when the PDCCH schedules PDSCHs, or a time slot used to transmit PUSCHs based on the second subband within the BWP and scheduling offset parameters when the Physical Uplink Control Channel (PUCCH) is used to schedule PUSCHs.

[0032] In some aspects, base station 102 / 180 may include a PDSCH / PUSCH scheduling component 199 configured to schedule PDSCH to UE 104 for reception or to schedule PUSCH to UE 104 for transmission. In one configuration, PDSCH / PUSCH scheduling component 199 may transmit a PDCCH including a scheduling offset parameter, wherein the PDCCH schedules one of the PDSCHs for UE reception in a first subband within the BWP, or provides uplink scheduling permission for PUSCH transmission by the UE in a second subband within the BWP. In this configuration, PDSCH / PUSCH scheduling component 199 may communicate with the UE in a time slot used for transmitting PDSCH based on the first subband within the BWP and the scheduling offset parameter when PDCCH schedules PDSCH, or in a time slot used for receiving PUSCH based on the second subband within the BWP and the scheduling offset parameter when PUCCH is used to schedule PUSCH.

[0033] Base station 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interface with EPC 160 via a first backhaul link 132 (e.g., S1 interface). Base station 102 configured for 5G NR (collectively referred to as Next Generation RAN (NG-RAN)) can interface with core network 190 via a second backhaul link 184. Among other functions, base station 102 can perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of Non-Access Stratum (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, location, and warning message delivery. Base stations 102 can communicate directly or indirectly with each other (e.g., via EPC 160 or core network 190) via a third backhaul link 134 (e.g., an X2 interface). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 can be wired or wireless.

[0034] Base station 102 can wirelessly communicate with UE 104. Each base station 102 can provide communication coverage for its respective geographic coverage area 110. Overlapping geographic coverage areas 110 may exist. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage areas 110 of one or more macro base stations 102. A network that includes both small cells and macro cells can be referred to as a heterogeneous network. A heterogeneous network may also include a Home Evolved Node Base Station (eNB) (HeNB), which can provide services to a restricted group called a Closed Subscriber Group (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also known as forward link) transmission from base station 102 to UE 104. The communication link 120 may use multiple-input multiple-output (MIMO) antenna technologies, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may use one or more carriers. Base station 102 / UE 104 may use a spectrum bandwidth of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) per carrier, which is allocated in carrier aggregation for a total of Yx MHz (x component carriers) for transmission in each direction. Carriers may or may not be adjacent to each other. Regarding DL and UL, carrier allocation may be asymmetrical (e.g., more or fewer carriers may be allocated to DL than to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell), and the secondary component carriers may be referred to as secondary cells (SCells).

[0035] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL WWAN spectrum. D2D communication link 158 can use one or more sideline channels, such as the Physical Sideline Broadcast Channel (PSBCH), Physical Sideline Discovery Channel (PSDCH), Physical Sideline Shared Channel (PSSCH), and Physical Sideline Control Channel (PSCCH). D2D communication can be conducted through various wireless D2D communication systems, such as WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0036] The wireless communication system may further include a Wi-Fi access point (AP) 150, which communicates with a Wi-Fi station (STA) 152 via a communication link 154, for example, in an unlicensed spectrum of 5 GHz. When communicating in unlicensed spectrum, the STA 152 / AP 150 may perform a free channel assessment (CCA) before communication to determine whether the channel is available.

[0037] Small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in unlicensed spectrum, small cell 102' can employ NR and use the same unlicensed spectrum (e.g., 5 GHz) as the Wi-Fi AP 150. Using NR in unlicensed spectrum can improve the coverage and / or increase the capacity of the access network.

[0038] The electromagnetic spectrum is typically subdivided into different categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating frequency bands were identified as the frequency range names FR1 (410MHz 7.125GHz) and FR2 (24.25GHz 52.6GHz). Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is generally (interchangeably) referred to as the "sub-6GHz" band. Similar naming issues sometimes arise regarding FR2; although it differs from the extremely high frequency (EHF) band (30GHz-300GHz), it is generally (interchangeably) referred to in documents and articles as the "millimeter wave" band, which is designated as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0039] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating frequency band for these mid-band frequencies as the frequency range name FR3 (7.125GHz 24.25GHz). Bands belonging to FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation above 52.6GHz. For example, three higher operating frequency bands have been identified as the frequency range names FR4a or FR4-1 (52.6GHz 71GHz), FR4 (52.6GHz 114.25GHz), and FR5 (114.25GHz 300GHz). Each of these higher frequency bands belongs to the EHF band.

[0040] In light of the foregoing, unless otherwise stated, it should be understood that the term "below 6 GHz," if used herein, can broadly refer to frequencies below 6 GHz, within FR1, or may include intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that the term "millimeter wave," if used herein, can broadly refer to frequencies that may include intermediate frequency band frequencies, within FR2, FR4, FR4-a or FR4-1, and / or FR5, or within the EHF band.

[0041] Whether it is a small cell 102' or a large cell (e.g., a macro base station), base station 102 may include and / or be referred to as an eNB, gNodeB (gNB), or another type of base station. Some base stations (such as gNB 180) may operate in conventional sub-6 GHz spectrum at millimeter wave frequencies and / or near-millimeter wave frequencies to communicate with UE 104. When gNB 180 operates in millimeter wave or near-millimeter wave frequencies, gNB 180 may be referred to as a millimeter wave base station. Millimeter wave base station 180 may use beamforming 182 with UE 104 to compensate for path loss and very short distances. Base station 180 and UE 140 may each include multiple antennas, such as antenna elements, antenna panels, and / or antenna arrays, to facilitate beamforming.

[0042] Base station 180 can transmit beamformed signals to UE 140 in one or more transmit directions 182'. UE 104 can receive beamformed signals from base station 180 in one or more receive directions 182'. UE 104 can transmit beamformed signals to base station 180 in one or more transmit directions. Base station 180 can receive beamformed signals from UE 104 in one or more receive directions. Base station 180 / UE 104 can perform beam training to determine the optimal receive and transmit directions for each of base station 180 / UE 104. The transmit and receive directions of base station 180 can be the same or different. The transmit and receive directions of UE 104 can be the same or different.

[0043] EPC 160 may include Mobility Management Entity (MME) 162, other MMEs 164, Serving Gateway 166, Multimedia Broadcast Multicast Service (MBMS) Gateway 168, Broadcast Multicast Service Center (BM-SC) 170, and Packet Data Network (PDN) Gateway 172. MME 162 may communicate with Home Subscriber Server (HSS) 174. MME 162 is the control node that handles signaling between UE 104 and EPC 160. Typically, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which is itself connected to PDN Gateway 172. PDN Gateway 172 provides IP address allocation and other functions for the UE. PDN Gateway 172 and BM-SC 170 are connected to IP Service 176. IP Service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. BM-SC 170 can provide service provisioning and delivery functions for MBMS users. The BM-SC 170 can act as an entry point for content provider MBMS transmissions, authorizing and initiating MBMS bearer services within a Public Land Mobile Network (PLMN), and scheduling MBMS transmissions. The MBMS gateway 168 can distribute MBMS services to base stations 102 belonging to a Broadcast-Specific Service Single Frequency Network (MBSFN) area, and is responsible for session management (start / stop) and collecting billing information related to eMBMS.

[0044] Core network 190 may include Access and Mobility Management Functions (AMF) 192, other AMFs 193, Session Management Functions (SMF) 194, and User Plane Functions (UPF) 195. AMF 192 can communicate with Unified Data Management (UDM) 196. AMF 192 is the control node that handles signaling between UE 104 and core network 190. Typically, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transmitted through UPF 195. UPF 195 provides UE IP address allocation and other functions. UPF 195 connects to IP service 197. IP service 197 may include the Internet, intranet, IP Multimedia Subsystem (IMS), Packet Switched (PS) Streaming (PSS) service, and / or other IP services.

[0045] Base stations may include and / or be referred to as gNB, Node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), Transmitter Receiver Point (TRP), or some other suitable terminology. Base station 102 provides UE 104 with access to EPC 160 or core network 190. Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similar functional devices. Some UE 104 may be referred to as IoT devices (e.g., parking meters, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as station, mobile station, subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, radio terminal, remote terminal, mobile phone, user agent, mobile client, client, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more accompanying devices, such as in a device constellation arrangement. One or more of these devices may jointly access the network and / or individually access the network.

[0046] Figure 2A Figure 200 shows an example of the first subframe within a 5G NR frame structure. Figure 2B Figure 230 shows an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 shows an example of a second subframe within a 5G NR frame structure. Figure 2D Figure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD), where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL, or it can be Time Division Duplex (TDD), where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL. Figure 2A , 2CIn the provided example, it is assumed that the 5G NR frame structure is TDD, where subframe 4 is configured with slot format 28 (mostly DL), where D is DL, U is UL, and F is flexibly used between DL / UL, and subframe 3 is configured with slot format 1 (all UL). Although subframes 3 and 4 are shown with slot formats 1 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are both DL and UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The UE is configured with a slot format via the received Slot Format Indicator (SFI) (dynamically via DL Control Information (DCI), or semi-statically / statically via Radio Resource Control signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0047] Figures 2A-2D The frame structure is illustrated, and aspects of this disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10 ms) can be divided into 10 equal-sized subframes (1 ms). Each subframe may include one or more time slots. Subframes may also include smaller time slots, which may contain 7, 4, or 2 symbols. Each time slot may contain 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each time slot may contain 14 symbols, while for extended CP, each time slot may contain 12 symbols. Symbols on the DL can be CP Orthogonal Frequency Division Multiplexing (OFDM) (CP-OFDM) symbols. Symbols on the UL can be CP-OFDM symbols (for high-throughput scenarios) or Discrete Fourier Transform (DFT) Extended OFDM (DFT-s-OFDM) symbols (also known as Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols) (for power-constrained scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0048]

[0049] For a normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For an extended CP, parameter set 2 allows 4 slots per subframe. Therefore, for a normal CP and parameter set μ, there are 14 symbols / slots and 2... μ One time slot / subframe. The subcarrier spacing can be equal to 2. μ*15kHz, where μ is the parameter set from 0 to 4. Thus, parameter set μ = 0 has a subcarrier spacing of 15kHz, and subcarrier μ = 4 has a subcarrier spacing of 240kHz. The symbol length / duration is inversely proportional to the subcarrier spacing. Figures 2A-2D An example of a normal CP is provided, with 14 symbols per slot, parameter set μ = 2, and 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a set of frames, there may be one or more different bandwidth portions (BWPs) of frequency division multiplexing (see 2B). Each BWP may have a specific parameter set and CP (normal or extended).

[0050] A resource grid can be used to represent the frame structure. Each time slot consists of a resource block (RB) extending for 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0051] like Figure 2A As shown, a portion of the RE is a reference (pilot) signal (RS) carried by the UE. This RS may include a demodulation RS (DM-RS) (indicated as R for a particular configuration, but other DM-RS configurations are also possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0052] Figure 2BExamples of individual DL channels within a subframe of a frame are shown. The Physical Downlink Control Channel (PDCCH) carries the DCI in one or more Control Channel Elements (CCEs) (e.g., 1, 2, 3, 8, or 16 CCEs), each CCE comprising six RE groups (REGs), each REG comprising 12 consecutive REs in the OFDM symbols of an RB. A PDCCH within a BWP can be referred to as a Control Resource Set (CORESET). The UE is configured to listen for PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during the PDCCH listening time on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs can reside at higher and / or lower frequencies across the channel bandwidth. The Primary Synchronization Signal (PSS) can be located within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) can be located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the physical layer cell identification group number and radio frame timing. Based on the Physical Layer Identifier and Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on this PCI, the UE can determine the location of the DM-RS. The Physical Broadcast Channel (PBCH) block (also known as the SS block (SSB)) carrying the Master Information Block (MIB) can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block. The MIB provides multiple Restricted Blocks (RBs) in the system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH such as the System Information Block (SIB), and paging messages.

[0053] like Figure 2C As shown, some of these REs carry DM-RS for channel estimation at the base station (indicated as R for a specific configuration, but other DM-RS configurations are also possible). The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first one or two symbols of the PUSCH. Depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of these comb structures. The base station can use the SRS for channel quality estimation to enable frequency-dependent scheduling on the UL.

[0054] Figure 2DExamples of individual UL channels within a subframe of a frame are shown. The PUCCH can be positioned according to an indication in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUCCH carries data and may additionally be used to carry buffer status reports (BSR), power headroom reports (PHR), and / or UCIs.

[0055] Figure 3 This is a block diagram of base station 310 communicating with UE 350 in the access network. In the DL, IP packets from EPC 160 can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, while Layer 2 includes the Serving Data Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functions associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reports; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with upper-layer packet data unit (PDU) transmission, error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs to transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and priority determination for logical channels.

[0056] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functions associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include: error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation diagram based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using inverse fast Fourier transform (IFFT) to generate a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from channel estimator 374 can be used to determine coding and modulation schemes and for spatial processing. Channel estimates can be obtained from a reference signal and / or channel condition feedback transmitted by UE 350. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can modulate a radio frequency (RF) carrier with the corresponding spatial stream for transmission.

[0057] At UE 350, each receiver 354RX receives signals through its respective antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides that information to the receive (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, the RX processor 356 can combine them into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with a reference signal, are recovered and demodulated by determining the most probable signal constellation points transmitted by base station 310. These soft decisions can be based on the channel estimate calculated by channel estimator 358. The soft decision is then decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functions.

[0058] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection, supporting HARQ operation using ACK and / or NACK protocols.

[0059] Similar to the functions described in conjunction with DL transmissions performed by base station 310, controller / processor 359 provides: RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with upper-layer PDU transmission, error correction via ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs to TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority processing, and priority determination of logical channels.

[0060] The channel estimate derived by the channel estimator 358 from the reference signal or feedback transmitted from the base station 310 can be used by the TX processor 368 to select an appropriate coding and modulation scheme and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354TX. Each transmitter 354TX can use the respective spatial stream to modulate the RF carrier for transmission.

[0061] At base station 310, UL transmissions are processed in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318RX receives signals through its respective antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides that information to the RX processor 370.

[0062] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets from the UE 350. IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection, using ACK and / or NACK protocols to support HARQ operation.

[0063] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to combine Figure 1 The PDSCH / PUSCH configuration component 198 is used to perform various aspects.

[0064] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 can be configured to combine Figure 1 The PDSCH / PUSCH scheduling component 199 is used to perform various aspects.

[0065] Base stations can operate at mmW or near-mmW frequencies for communication with the UE, such as within FR2, which includes the band between 24.25 GHz and 52.6 GHz. Similarly, some base stations can be further configured to operate at frequencies outside FR2 (such as the band between 52.6 GHz and 114.25 GHz). This band range may be referred to as "Frequency Range 4 (FR4)," "Upper Millimeter Wave Band," or "Sub-THz Range" (hereinafter collectively referred to as "Ultra-Wide Bandwidth Area").

[0066] For communication equipment such as base stations and / or UEs, in order to communicate with other communication equipment, the communication equipment may include cascaded electronic components, circuits, and / or sub-units, such as amplifiers, filters, phase shifters, mixers, attenuators, and detectors. The cascading of these components can be referred to as a radio frequency chain (RF chain). When the communication equipment operates in an ultra-wide bandwidth region, the components within the RF chain of the communication equipment may tend to be expensive, and therefore the number of components included in the RF chain may be limited. For example, for a base station or UE operating in an ultra-wide bandwidth region, beamforming is typically specified, where the base station or UE can frequently adjust the direction of its transmit or receive(multiple) beams using phase shifters. Since phase shifters supporting high frequencies can be relatively expensive, the base station or UE may contain only a limited set of phase shifters. Furthermore, at higher frequencies (e.g., FR2, FR4), beam skew may be more likely to occur when the operating frequency changes, as the beam direction (e.g., angle) may not consistently point in the same direction. In the case of beam skew, an antenna pattern (e.g., a beam) pointing at an angle θ0 at frequency f0 can point at an angle θ0+Δθ at frequency f0+Δf instead of θ0. Phase shifters can be used to mitigate or correct beam skew. However, when the number of phase shifters is limited in an RF chain over ultra-wide bandwidth, the base station or UE may not have enough phase shifters to correct beam skew, which can lead to significant losses in beamforming performance. For example, due to beam skew, the beam of the base station or UE may not be pointing in the correct direction(s), which can result in a loss of signal-to-noise ratio (SNR) in the transmission.

[0067] A base station can configure a UE using one or more time-domain resources to receive data from the base station (e.g., via PDSCH) or transmit data to the base station (e.g., via PUSCH), whereby the base station can transmit this configuration to the UE via PDCCH. In some examples, the UE can use a wider beam (which may be referred to as a “coarse beam”) to receive the PDCCH, and the UE can use a narrower beam (which may be referred to as a “fine beam”) to receive the PDSCH or transmit the PUSCH. Since UE tuning beam weights (e.g., from a wider beam to a narrower beam) may take time, the base station can schedule an offset between the time it transmits the PDCCH to the UE and the time the UE receives the corresponding PDSCH or transmits the corresponding PUSCH, allowing the UE sufficient time to tune the beam during the offset period.

[0068] In one example, the UE can be configured with at least one (which may be the default) time-domain resource allocation configuration. The base station can allocate time-domain resources with offsets to the UE based on a time-domain resource allocation table, which can have multiple rows (e.g., up to 16 rows), each capturing or providing scheduling parameters for the time-domain resources. Scheduling parameters may include a mapping type, a scheduling offset K (e.g., K0 for PDSCH or K2 for PUSCH), a start symbol index (S), and a number of symbols (L). The scheduling offset K can indicate the slot index offset by which the UE receives PDSCH or transmits PUSCH after receiving the corresponding PDCCH. The start symbol index can indicate which symbol within the slot can be used by the UE to receive PDSCH or transmit PUSCH, and the number of symbols can indicate how many consecutive symbols after the start symbol can be used by the UE to receive PDSCH or transmit PUSCH. In some examples, UEs with lower capabilities can specify longer offsets because they may require longer RF setup times to establish their beamweights, while UEs with higher capabilities can use shorter offsets. Therefore, the base station can schedule offsets from the time-domain resource allocation table for the UE based on its capabilities.

[0069] Figure 4 Figure 400 illustrates an example of scheduling PDSCH for a UE according to various aspects of this disclosure. The UE can receive PDCCH 402 in time slot n 404, where PDCCH 402 can indicate to the UE the row index (e.g., 1-16) corresponding to the PDSCH, downlink allocation (e.g., start symbol index (S) 408 and symbol count (L) 410, etc.), and scheduling offset K0 406 associated with the row index. Based on this indication, the UE can determine that the base station will transmit the PDSCH in time slot n+K0, and the UE can listen for the PDSCH in time slot n+K0. Since PDCCH 402 also indicates the downlink resource allocation S 408 and L 410 for the PDSCH within time slot n+K0, the UE can also determine that the PDSCH will be transmitted by the base station on symbols S, S+1…S+(L-1) in time slot n+K0. For example, as… Figure 4 As shown, PDCCH 402 in time slot n 404 can indicate to the UE that the PDSCH will be transmitted by the base station with a scheduling offset of 4 time slots (e.g., K0 = 4 in time slot n+4), and the PDSCH can occupy four symbols (e.g., L = 4) within time slot n+4, starting from the symbol with symbol index #3 (e.g., S = 3). Based on this indication, the UE can listen for the PDSCH from the base station in time slot n+4 on the symbols corresponding to symbol indices 3, 4, 5, and 6 within time slot n+4.

[0070] Figure 5Figure 500 illustrates an example of scheduling a PUSCH for a UE according to various aspects of this disclosure. Similar to... Figure 4 In an example used for scheduling PDSCH, the UE can receive PDCCH 502 in time slot n 504. PDCCH 502 can indicate to the UE the row index corresponding to the PUSCH, uplink scheduling clearance (e.g., start symbol index (S) 508 and symbol quantity (L) 510, etc.), and the scheduling offset K2 506 associated with the row index. Based on this indication and uplink scheduling clearance, the UE can send the PUSCH to the base station in time slot n+K2. Since PDCCH 502 also indicates the uplink resource allocation S508 and L510 for the PUSCH within time slot n+K2, the UE can also determine that it can use symbols S, S+1...S+(L1) of time slot n+K2 to send the PUSCH when the PDCCH (or the corresponding PUCCH) is used to schedule the PUSCH. For example, as... Figure 5 As shown, PDCCH 502 in time slot n504 can instruct the UE that the UE can send PUSCH to the base station with a scheduling offset of 3 time slots (e.g., K2 = 3 in time slot n+3), and the PUSCH can occupy 5 symbols (e.g., L = 5) within time slot n+3, starting from the symbol with symbol index #2 (e.g., S = 2). Based on this instruction, the UE can send PUSCH to the base station in time slot n+3 using symbols corresponding to symbol indices 2, 3, 4, 5, and 6 within time slot n+3.

[0071] While UEs can use the duration of a scheduling offset (e.g., K0 or K2) to adjust the beam weights of their (multiple) receive or transmit beams, different UEs may have varying capabilities that allow or disallow them to change their (multiple) receive or transmit beams when the PDSCH or PUSCH is activated at the scheduling offset (K0 or K2). For example, if a UE has the capability to change its (multiple) receive or transmit beams before the scheduling offset, the UE can use one or more beams indicated by the base station. The base station can indicate one or more beams to the UE via the Transmission Configuration Indicator (TCI) state, where the TCI state can be indicated to the UE in the DCI. On the other hand, if a UE does not have the capability to change its receive or transmit beams before the scheduling offset, the UE can be configured to use a more conservative or default approach when tuning its (multiple) beams. For example, one or more antenna ports of a UE used to receive PDSCH DM-RS or to transmit PUSCH DM-RS can be configured to be quasi-co-bit (QCLed) with the antenna ports used to receive PDCCH DM-RS or to transmit PUCCH DM-RS associated with a control resource set (CORESET) having the lowest core set identifier (ID). In some examples, two antenna ports can be quasi-co-bit if the properties of the channel transmitting symbols on one antenna port can be inferred from the channel transmitting symbols on the other antenna port. In other words, if the UE cannot configure or tune the beam indicated by the base station to receive PDSCH or transmit PUSCH within a given offset (K0 or K2), the UE can use the beam used to receive the corresponding PDCCH or transmit the corresponding PUCCH.

[0072] Depending on the UE's capabilities, the UE can perform one or more beam switchings (e.g., up to 13) within a single time slot, and the UE can notify the base station of this capability. For example, the UE can indicate a QCL duration parameter (e.g., timedurationForQCL) to the base station, which defines the minimum number of OFDM symbols used by the UE to perform PDCCH reception and apply spatial QCL information received in DCI to PDSCH processing. The UE can indicate QCL duration parameters for each subcarrier interval at 60 kHz and 120 kHz (e.g., values ​​for the minimum number of OFDM symbols), etc. The base station can use this QCL duration parameter, combined with a scheduling offset (K0 or K2), to configure (multiple) beams for the UE to provide fine-grained beam tuning.

[0073] The aspects presented in this paper can enhance the accuracy and efficiency of configuring scheduling offsets (e.g., K0 or K2) and / or QCL duration parameters (e.g., timedurationForQCL) for communication devices in high-frequency bands (such as FR4). In one aspect, the scheduling offset can be subband / channelization specific. In other aspects, such as during cross-carrier scheduling in FR4, the QCL duration parameter can be configured as a function of the component carrier (CC).

[0074] Frequency bands, such as those within FR2 or FR4, can be channelized by dividing the band into multiple channels (e.g., sub-bands). This allows communication devices to use the bandwidth (e.g., channels) within the band in a more dynamic or flexible manner. Figure 6 Figure 600 illustrates an example of a channelized frequency band according to various aspects of this disclosure. A frequency band ranging from 57 GHz to 71 GHz can be channelized by dividing the band into seven channels (e.g., CH0 to CH6), where each channel can have a bandwidth of 2 GHz. For example, channel zero (CH0) could include a bandwidth ranging from 57 GHz to 59 GHz, channel three (CH3) could include a bandwidth ranging from 63 GHz to 65 GHz, channel six (CH6) could include a bandwidth ranging from 69 GHz to 71 GHz, and so on. In some examples, this segmentation or channelization may also be referred to as 2 GHz channelization of the frequency band. Although Figure 6 The example uses a 57GHz to 71GHz band with 2GHz channelization (e.g., bandwidth per channel), but note that this band can be any frequency range (e.g., 52.6GHz to 71GHz, 71GHz to 114.25GHz, etc.) and the bandwidth used for channelization can be customized according to the implementation (e.g., 2.1GHz, 3.5GHz, 5GHz, etc.). Communication devices can also use one or more channelizations, such as using one channelization (e.g., 2GHz) to communicate with a first device and another channelization (e.g., 3GHz) to communicate with a second device and / or the first device. For example, a communication device can use multiple channelizations in a carrier aggregation (CA) framework for high-performance setups (e.g., 2X CA, 3X CA, 4X CA, etc.). Furthermore, a bandwidth portion (BWP) can be a consecutive set of physical resource blocks (PRBs) on a given component carrier (e.g., 24 PRBs), where PRBs can be selected from consecutive subsets of common resource blocks of a given set of parameters. Therefore, a PRB within a BWP may refer to one or more channels (e.g., subbands) under a channelization.

[0075] After a frequency band is channelized, communication devices (e.g., UEs, base stations, etc.) can use one or more channels within the band for communication. For example, a communication device can use one channel (e.g., CH0 or CH3) at a time or multiple channels (e.g., CH1, CH2, and CH3) at a time, where the communication device can dynamically select (multiple) channels. A communication device can also use one channel to transmit or receive a portion of data in one or more time slots or symbols (multiple) within a time slot, and can use another (multiple) channels (multiple) to transmit or receive another portion of data. However, because beam skew can occur at higher frequencies, where the beam direction from the communication device may not consistently point in the same direction when the operating frequency changes, the beam weights configured or optimized for one channel (e.g., beamwidth, beam direction, sidelobe level, and / or grating lobes, etc.) may not be suitable for another channel, and may result in a loss of link margin when the communication device switches channels. For example, as... Figure 7 As shown in Figure 700, the beam 704 of the communication device 702 can be optimized for communication (e.g., transmitting or receiving data) with a target beam at CH0 (e.g., 57-59 GHz). However, when the communication device 702 switches the communication channel to CH7 (e.g., 69-71 GHz), the direction of the beam 704 may change due to beam skew. This may cause the beam 704 to misalign with the target beam when switching from CH0 to CH7, potentially resulting in a loss of communication link margin. Therefore, after changing the channel, the communication device may need some time to improve its beam(s).

[0076] In aspects of this disclosure, scheduling offsets (e.g., K0 or K2) can be configured to be subband (e.g., channel) or channelization-specific to provide the communication device with sufficient time to tune its(multiple) beams(s) after a channel handover, such as to address beam handover delay. For example, the scheduling offset can be configured as a function of a subband (e.g., channel), such as a function of a subband within a BWP. Furthermore, if a communication device such as a UE is scheduled for one subband and then requests or is notified to change to another subband, the associated time-domain resources (e.g., PDSCH, PUSCH, etc.) can be appropriately modified in their allocation configuration to handle or adapt to radio frequency or beam handover latency.

[0077] Figure 8 Figure 800 illustrates an example of providing a scheduling offset (e.g., K0 or K2) to a UE based at least in part on a sub-band (e.g., a channel) of a channelized frequency band, according to various aspects of this disclosure. Figure 6The frequency band from 57 GHz to 71 GHz can be channelized into seven channels (CH0 to CH6), each with a bandwidth of 2 GHz. In one example, a communication device such as UE 802 can receive PDCCH 804 from the base station in time slot n 806 for scheduling PDSCH for reception or PUSCH for transmission. UE 802 can use one or more channels (e.g., sub-bands) within the frequency band to receive PDSCH or transmit PUSCH, such as using channel 1 808 to receive PDSCH, or UE 802 can use one or more channels (e.g., sub-bands) within BWP 812 within the frequency band to receive PDSCH or transmit PUSCH, such as using channel 4 810 within BWP 812 to transmit PUSCH, etc. UE 802 can then determine the time slot 814 for receiving PDSCH or transmitting PUSCH based at least in part on the selected channel (e.g., 808, 810, etc.). For example, UE 802 can determine, at least in part, a scheduling offset 816 for receiving PDSCH (e.g., for K0) or transmitting PUSCH (e.g., for K2) based on the selected channel, where the scheduling offset 816 can be different for each channel. For example, channel one 808 can specify a scheduling offset of 3 time slots (e.g., K0 or K2 = 3), such that UE 802 can receive PDSCH or transmit PUSCH in time slot n+3. On the other hand, channel four 810 can specify a scheduling offset of 5 time slots (e.g., K0 or K2 = 5), such that UE 802 can receive PDSCH or transmit PUSCH in time slot n+5, etc. Each channel or subband within BWP 812 can also be associated with a different value of scheduling offset 816. For example, CH5 or CH6 can have a different scheduling offset 816 than CH0. In some examples, the value of scheduling offset 816 can be determined based on an analog beamforming codebook, a predefined set of rules or configurations, and / or based on the capabilities of UE 802. Thus, when the PDCCH schedules the PDSCH, the UE 802 can determine the time slot for receiving the PDSCH based on the subband and scheduling offset parameters within the BWP. Similarly, when the PUCCH schedules the PUSCH, the UE can also determine the time slot for transmitting the PUSCH based on the subband and scheduling offset parameters within the BWP.

[0078] In another aspect of this disclosure, for cross-carrier scheduling in high-frequency bands such as FR4, the QCL duration parameter (e.g., timedurationForQCL) can be configured as a function of the CC index. In networks supporting carrier aggregation with cross-carrier scheduling, cross-carrier scheduling allows the UE to connect to different nodes to receive PDCCH on different carriers, thereby reducing or eliminating inter-cell interference on the PDCCH. Using cross-carrier scheduling, the UE's data transmission or reception can be dynamically scheduled on different CCs. For example, the UE can receive PDSCH on a different CC than the CC receiving the corresponding PDCCH. Similarly, the UE can transmit PUSCH on an associated CC different from the CC receiving uplink clearance.

[0079] Figure 9 Figure 900 illustrates an example of cross-carrier scheduling according to various aspects of this disclosure. A PDCCH 904 transmitted on the primary cell can be used to schedule one or more PDSCHs or PUSCHs for UEs on different cells. For example, PDCCH 904 can indicate / schedule a first downlink resource (e.g., a first CC, PDSCH 906, etc.) on the primary cell, a second downlink resource (e.g., a second CC, PDSCH 908, etc.) on secondary cell #1, and a third downlink resource (e.g., a third CC, PDSCH 910, etc.) on secondary cell #2. This can also be applied to PUSCHs, where PDCCH 904 can schedule uplink resources (e.g., PUSCHs) on the primary cell, secondary cell #1, and secondary cell #2, respectively. In some examples, cross-carrier scheduling can enable the primary cell to schedule resources on secondary cells without a PDCCH, but the primary cell may not be able to schedule resources on secondary cells that have their own PDCCHs.

[0080] In some examples, when cross-carrier scheduling is applied together with band channelization, such as combining... Figure 6 As described, each CC (e.g., cell) can be scheduled on different subbands (e.g., channels). For example, return to reference. Figure 9PDSCH 906 transmitted on the primary cell (e.g., the first CC) can use CH2, PDSCH 908 transmitted on the secondary cell #1 (e.g., the second CC) can use CH3, PDSCH 910 transmitted on the secondary cell #2 (e.g., the third CC) can use CH5, and so on. Thus, the base station can be configured to determine the scheduling offset (e.g., K0 or K2) between the PDCCH and the corresponding PDSCH / PUSCH, at least in part, based on which CC or CC index (e.g., the first CC, the second CC, the third CC, etc.) is associated with the corresponding PDSCH / PUSCH. For example, the time slot for receiving PDSCH 908 can be determined based on the second CC, or the time slot for transmitting PUSCH on the second cell #2 can be determined based on the third CC, where the second CC and the third CC can be associated with CH3 and CH5 of the channelized band, respectively. In another example, the PDCCH can be on the first CC, the PDSCH on the second CC, the PUCCH on the third CC, and the PUSCH on the fourth CC, wherein the first CC can be different from the second, third, and / or fourth CC. In other examples, the UE can further determine the time slot for receiving the PDSCH based on the second CC, and can further determine the time slots for transmitting the PUCCH and PUSCH based on the third and fourth CCs. For example, the first subband (e.g., CH3) can be based on the second CC, the second subband (e.g., CH5) can be based on the third and fourth CCs, and so on.

[0081] In some examples, the duration of QCL parameters (e.g., timedurationForQCL) used for receiving PDSCH or transmitting PUSCH can also be based on their respective CCs or CC indices. For example, the QCL parameters for receiving PDSCH 908 can be determined based on a second CC, or the QCL parameters for transmitting PUSCH on secondary cell #2 can be determined based on a third CC, and so on, where the second and third CCs can be associated with different channels (e.g., CH3 and CH5, respectively). The base station can use the determined QCL duration parameters in conjunction with scheduling offsets (K0 or K2) to configure (multiple) beams for the UE to provide fine-grained beam tuning within the channelized high-frequency band, where beamforming operation can be optimized over an ultra-wide bandwidth region via appropriate design of the scheduling offsets.

[0082] In another aspect of this disclosure, a public RF / analog beamforming codebook can be used across an ultrawide bandwidth region or range, and / or a subband (e.g., channel) specific RF / analog beamforming codebook can be mapped to specific variations in the PDSCH or PUSCH time-domain resource allocation configuration. Figure 10AFigure 1000A illustrates an example of using a common analog beamforming codebook across a channelized frequency band according to various aspects of this disclosure. (As in conjunction with...) Figure 6 The frequency band from 57 GHz to 71 GHz can be channelized into seven channels (CH0 to CH6), each with a bandwidth of 2 GHz. A common analog beamforming codebook can be predefined or configured for the UE and / or base station, wherein the common analog beamforming codebook can define one or more parameters for resource allocation, such as scheduling offset (K0 or K2), mapping type, starting symbol index (S), number of symbols (L), and / or QCL duration parameters for each subband (e.g., CH0 to CH6). Therefore, when the base station schedules PDSCH or PUSCH for the UE in one or more channels, the base station can apply one or more resource allocation parameters provided by the common analog beamforming codebook. For example, the base station can use CH2 and CH5 to schedule PDSCH to be sent to the UE, and the common analog beamforming codebook can indicate that a scheduling offset of 3 time slots (e.g., K0) can be applied to the PDSCH at CH2, and a scheduling offset of 5 time slots can be applied to the PDSCH at CH5, and so on. In one example, the common analog beamforming codebook may include row indices for each sub-band (e.g., channel), and the base station can indicate the PUSCH or PDSCH time-domain resource allocation for each sub-band to the UE by indicating the corresponding row index. In other examples, the common analog beamforming codebook may be implemented at the UE rather than at the base station. In this case, the UE can indicate multiple parameters within the common analog beamforming codebook to the base station, and the base station can apply those parameters based on the indication.

[0083] Figure 10BFigure 1000B illustrates an example of using sub-band specific analog beamforming codebooks in a channelized frequency band according to various aspects of this disclosure, wherein each channel (e.g., CH0 to CH6) may have its own analog beamforming codebook. Similarly, each analog beamforming codebook may define one or more parameters for resource allocation, such as scheduling offset (K0 or K2), mapping type, starting symbol index (S), number of symbols (L), and / or QCL duration parameters for each sub-band (e.g., CH0 to CH6). For example, a base station may use CH3 to schedule PDSCHs to be sent to a UE, and may (e.g., by the base station) use a CH3-specific analog beamforming codebook to indicate that scheduling offsets (e.g., K0) for four time slots can be applied to the PDSCHs. Because sub-band specific analog beamforming codebooks can be created and optimized for each sub-band, it can provide better estimations in time-domain resource allocation configurations than ordinary analog beamforming codebooks. Furthermore, each sub-band specific analog beamforming codebook can be modified or replaced without affecting other sub-band specific analog beamforming codebooks. Thus, the scheduling offset (K0 or K2) and / or QCL duration parameters can be configured as a function (e.g., based on) one or more analog beamforming codebooks in the channelized frequency band. Similarly, subband-specific analog beamforming codebooks can be implemented at the UE rather than at the base station. In this case, the UE can indicate to the base station the parameters(s) within the subband-specific analog beamforming codebook(s), and the base station can apply those parameters(s) based on the indication.

[0084] Figure 11 This is a communication flow 1100 illustrating an example of determining a scheduling offset based on sub-bands according to various aspects of this disclosure. The numbers associated with communication flow 1100 do not specify a particular time order and are used only as a reference to communication flow 1100.

[0085] At 1110, base station 1104 can send PDCCH 1106, including scheduling offset parameter 1108, to UE 1102. Base station 1104 can use PDCCH 1106 to schedule PDSCH for UE 1102 to receive in the first subband within the BWP (as shown at 1114), or to provide uplink scheduling permission for PUSCH for UE 1102 to transmit in the second subband within the BWP.

[0086] At 1112, thereafter, if the PDCCH schedules the PDSCH, then UE 1102 can determine the time slot for receiving the PDSCH based on the first subband within the BWP and the scheduling offset parameter 1108, or if the PUCCH is used to schedule the PUSCH, then UE 1102 can determine the time slot for transmitting the PUSCH based on the second subband within the BWP and the scheduling offset parameter 1108.

[0087] In one example, to determine the time slot for receiving PDSCH based on the first subband within the BWP, UE 1102 can determine K0 of the first subband within the BWP, where the time slot for receiving PDSCH can be time slot n + K0 (e.g., n is the time slot for receiving PDCCH and K0 is the time slot scheduling offset). Similarly, to determine the time slot for transmitting PUSCH based on the second subband within the BWP, UE 1102 can determine K2 of the second subband within the BWP, where the time slot for transmitting PUSCH can be time slot n + K2 (e.g., n is the time slot for transmitting PUCCH and K2 is the time slot scheduling offset). In one example, K0 or K2 can be different for at least two different subbands within the same BWP.

[0088] In another example, such as combination Figure 8 and 9 The scheduling offset parameter 1108 can be determined based on the first sub-band or the second sub-band, and the first sub-band or the second sub-band can be a channel within the channelized frequency band, such as shown at 1114.

[0089] At 1116, UE 1102 can determine the analog beamforming weights based on the analog beamforming codebook, which can be specific to the first subband or the second subband.

[0090] At 1118, UE 1102 can send information indicating the determined analog beamforming weights to base station 1104. In response, at 1120, UE 1102 can receive information indicating K0 or K2 from base station 1104.

[0091] In one example, the PDCCH can be on the first CC, the PDSCH on the second CC, the PUCCH on the third CC, and the PUSCH on the fourth CC, where the first CC can be different from the second, third, or fourth CC. In such an example, the time slot for receiving the PDSCH can be further determined based on the second CC, and the time slots for transmitting the PUCCH and PUSCH can be further determined based on the third and fourth CCs, where the first subband can be based on the second CC, and the second subband can be based on the third and fourth CCs, and so on. In such an example, the duration of the QCL parameter for receiving the PDSCH within the BWP can be based on the second CC, and the duration for transmitting the PUCCH and PUSCH within the BWP can be based on the third and fourth CCs.

[0092] At 1117, UE 1102 can communicate with base station 1104 based on the first or second subband within the BWP and the scheduling offset parameter 1108. For example, when PDCCH schedules PDSCH, UE 1102 can receive PDSCH from base station 1104 based on the first subband within the BWP and the scheduling offset parameter 1108, and / or when PUCCH is used to schedule PUSCH, UE 1102 can send PUSCH based on the second subband within the BWP and the scheduling offset parameter 1108, and so on.

[0093] Figure 12 This is a flowchart of a wireless communication method 1200. The method can be performed by a UE or a component of a UE (e.g., UE 106, 350, 802, 1102; communication device 702; apparatus 1202; processing system, which may include memory 360, and may be the entire UE 350 or components of UE 350, such as TX processor 368, RX processor 356, and / or controller / processor 359). The method enables the UE to receive a PDCCH including a scheduling offset parameter, wherein the scheduling offset parameter may indicate that the UE will receive the corresponding PDSCH time slot in a subband within the BWP, or that the UE will transmit the corresponding PUSCH time slot in a subband within the BWP.

[0094] At 1202, the UE can receive a PDCCH including a scheduling offset parameter, wherein the PDCCH can be one of an uplink scheduling permission to schedule either a PDSCH for reception in the first subband within the BWP or a PUSCH for transmission in the second subband within the BWP, such as in combination. Figure 4 , 5 As described in 8 and 11. For example, at 1110, UE 1102 can receive PDCCH 1106 including scheduling offset parameter 1108 from base station 1104, wherein the scheduling offset parameter can be determined based on a first subband or a second subband, and the first subband or the second subband can be a channel within a channelized frequency band, as shown at 1114. The reception of PDCCH including the scheduling offset parameter can be, for example, by Figure 13 The scheduling offset processing component 1340 and / or receiving component 1330 of the device 1302 in the middle are used to perform the operation.

[0095] At 1204, the UE can communicate with the base station based on one of the time slots used to receive PDSCH based on the first subband and scheduling offset parameters within the BWP when PDCCH is scheduled for PDSCH, or the time slot used to transmit PUSCH based on the second subband and scheduling offset parameters within the BWP when PUCCH is used to schedule PUSCH, such as combining... Figure 4 , Figure 5 , Figure 8and Figure 11 As described. For example, at 1117, UE 1102 can communicate with base station 1104 based on the first or second subband within the BWP and scheduling offset parameter 1108. This communication can be, for example, by Figure 13 The time slot determination component 1342, the receiving component 1330, and / or the transmitting component 1334 of the device 1302 are used to perform this action.

[0096] In one example, the time slot used for receiving PDSCH can be based on the first subband within the BWP and K0 of the first subband within the BWP. The time slot used for receiving PDSCH is time slot n + K0, where n is the time slot for receiving PDCCH and K0 is the time slot scheduling offset for PDSCH, such as combining... Figure 4 , 5 As described in 8. Similarly, the time slot used to transmit PUSCH can be based on the second subband within the BWP, and based on K2 of the second subband within the BWP, the time slot used to transmit PUSCH is time slot n + K2, where n is the time slot for transmitting PUSCH and K2 is the time slot scheduling offset for PUSCH, as described in combination with 4, 5, and 8. In some examples, K0 can be different for at least two different subbands within the same BWP, and K2 can also be different for at least two different subbands within the same BWP.

[0097] At point 1206, the UE can send information to the base station indicating simulated beamforming weights. These simulated beamforming weights can be based on a simulated beamforming codebook, which is specific to either the first or second sub-band, such as combining... Figure 10A , 10B As described in section 11. For example, at 1116, UE 1102 can determine the analog beamforming weights based on the analog beamforming codebook, wherein the analog beamforming codebook is specific to a first sub-band or a second sub-band. Then, at 1118, UE 1102 can transmit the determined analog beamforming weights to base station 1104. The transmission of the analog beamforming weights can be, for example, by... Figure 13 The time-slot beamforming weight determination component 1344 and / or transmission component 1334 of the device 1302 perform this action. Then, in response to the transmitted information, the UE can receive information indicating one of K0 or K2, such as... Figure 11 As shown in 1118 and 1120.

[0098] In another example, PDCCH can be on the first CC, PDSCH on the second CC, PUCCH on the third CC, and PUSCH on the fourth CC, where the first CC can be different from the second, third, or fourth CC. Note that the use of "first," "second," "third," and "fourth" does not specify a particular time order, but merely indicates different CCs, such as combinations. Figure 9 As described. In one example, the UE can determine the time slot for receiving PDSCH based on the second CC, and the UE can determine the time slot for transmitting PUCCH and PUSCH based on the third and fourth CCs, wherein the first subband can be based on the second CC, and the second subband can be based on the third and fourth CCs, and so on. In another example, the duration of the QCL parameter for the UE to receive PDSCH within the BWP can be based on the second CC, and the duration for the UE to transmit PUCCH and PUSCH within the BWP can be based on the third and fourth CCs.

[0099] Figure 13Figure 1300 illustrates an example of a hardware implementation of device 1302. Device 1302 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, device 1302 may include a baseband processor 1304 (also referred to as a modem) coupled to an RF transceiver 1322. In some aspects, device 1302 may also include one or more Subscriber Identity Module (SIM) cards 1320, an application processor 1306 coupled to a Secure Digital Card (SD) card 1308 and a screen 1310, a Bluetooth module 1312, a Wireless Local Area Network (WLAN) module 1314, a Global Positioning System (GPS) module 1316, or a power supply 1318. Baseband processor 1304 communicates with UE 104 and / or BS 102 / 180 via RF transceiver 1322. Baseband processor 1304 may include computer-readable media / memory. The computer-readable media / memory may be non-transitory. Baseband processor 1304 is responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by the baseband processor 1304, the software causes the baseband processor 1304 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the baseband processor 1304 during software execution. The baseband processor 1304 also includes a receiving component 1330, a communication manager 1332, and a transmitting component 1334. The communication manager 1332 includes one or more of the components shown. The components within the communication manager 1332 can be stored in a computer-readable medium / memory and / or configured as hardware within the baseband processor 1304. The baseband processor 1304 can be a component of a UE (e.g., of device 350) and can include a memory 360 and / or at least one of a TX processor 368, an RX processor 356, and a controller / processor 359. In one configuration, device 1302 can be a modem chip and includes only the baseband processor 1304, while in another configuration, device 1302 can be the entire UE (e.g., see...). Figure 3 (350), and includes an additional module for device 1302.

[0100] Communication manager 1332 includes a scheduling offset processing component 1340 configured to receive a PDCCH including scheduling offset parameters, wherein the PDCCH schedules one of an uplink scheduling permission for either a PDSCH for reception in a first subband within the BWP or a PUSCH for transmission in a second subband within the BWP, for example, as in combination Figure 12As described in 1202. The communication manager 1332 further includes a time slot determination component 1342 configured to communicate with the base station based on one of the time slots used to receive PDSCH based on a first subband and scheduling offset parameter within the BWP when the PDCCH schedules PDSCH (e.g., as shown at 1208) or the time slots used to transmit PUSCH based on a second subband and scheduling offset parameter within the BWP when the PUCCH is used to schedule PUSCH (e.g., as shown at 1210), for example, as in combination with... Figure 12 As described in 1202. The communication manager 1332 further includes a beamforming weight determination component configured to send information to the base station indicating simulated beamforming weights, which are based on a simulated beamforming codebook, wherein the simulated beamforming codebook is specific to a first subband or a second subband, for example, as described in 1206 in conjunction with 12.

[0101] The device may include execution Figure 12 The additional components of each box in the flowchart of the algorithm. Thus, Figure 12 Each block in the flowchart can be executed by a component, and the apparatus can include one or more of these components. These components can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for processor implementation, or some combination thereof.

[0102] As shown in the figure, device 1302 may include various components configured for various functions. In one configuration, device 1302, particularly baseband processor 1304, includes components for receiving a PDCCH including scheduling offset parameters, wherein the PDCCH schedules one of an uplink scheduling permission for receiving a PDSCH in a first subband within the BWP or for transmitting a PUSCH in a second subband within the BWP (e.g., scheduling offset processing component 1340 and / or receiving component 1330). Device 1302 includes components for determining one of the time slots for receiving the PDSCH based on the first subband within the BWP and the scheduling offset parameters when the PDCCH schedules the PDSCH, or for transmitting the PUSCH based on the second subband within the BWP and the scheduling offset parameters when the PUCCH is used to schedule the PUSCH (e.g., time slot determination component 1342, receiving component 1330, and / or transmitting component 1334). The apparatus 1302 includes components for transmitting information indicating simulated beamforming weights to a base station. The simulated beamforming weights are based on a simulated beamforming codebook, wherein the simulated beamforming codebook is specific to a first subband or a second subband (e.g., a time-slot beamforming weight determination component 1344 and / or a transmission component 1334).

[0103] In one configuration, the time slots used for receiving PDSCH are based on the first subband within the BWP and K0 of the first subband within the BWP. The time slot for receiving PDSCH is time slot n + K0, where n is the time slot for receiving PDCCH and K0 is the time slot scheduling offset for PDSCH. Alternatively, the time slots used for transmitting PUSCH are based on the second subband within the BWP and K2 of the second subband within the BWP. The time slots used for transmitting PUSCH are time slot n + K2, where n is the time slot for transmitting PUCCH and K2 is the time slot scheduling offset for PUSCH. In one example, K0 can be different for at least two different subbands within the same BWP. Similarly, K2 can be different for at least two different subbands within the same BWP.

[0104] In another configuration, the scheduling offset parameters are determined based on the first sub-band or the second sub-band, and the first sub-band or the second sub-band is a channel within the channelized frequency band.

[0105] In another configuration, device 1302 includes a component for receiving information indicating one of K0 or K2 in response to the transmitted information.

[0106] In another configuration, the PDCCH is on the first CC, the PDSCH is on the second CC, the PUCCH is on the third CC, and the PUSCH is on the fourth CC, where the first CC is different from the second, third, or fourth CC. The time slot for receiving the PDSCH can be further determined based on the second CC, and the time slots for transmitting the PUCCH and PUSCH can be further determined based on the third and fourth CCs, with the first subband based on the second CC and the second subband based on the third and fourth CCs.

[0107] In another configuration, the duration of the QCL parameter used to receive PDSCH within the BWP can be based on the second CC, and the duration of the PUCCH and PUSCH used to send within the BWP can be based on the third and fourth CCs.

[0108] The component may be one or more components of device 1302, configured to perform the functions described therein. As described above, device 1302 may include TX processor 368, RX processor 356, and controller / processor 359. Thus, in one configuration, the component may be TX processor 368, RX processor 356, and controller / processor 359, configured to perform the functions listed in the component.

[0109] Figure 14This is a flowchart 1400 of a wireless communication method. The method can be executed by a base station or a component of a base station (e.g., base stations 102, 180, 310, 1104; device 1502; which may include memory 376, and may be the entire base station 310 or components of base station 310, such as TX processor 316, RX processor 370, and / or controller / processor 375). The method enables the base station to schedule offsets for the UE to receive PDSCH or transmit PUCCH and PUSCH. These offsets can be based on subbands within the BWP or on one or more channels within a channelized frequency band.

[0110] At 1402, the base station can transmit a PDCCH including scheduling offset parameters, wherein the PDCCH can schedule one of the uplink scheduling permissions for either a PDSCH for the UE to receive in the first subband within the BWP or a PUSCH for the UE to transmit in the second subband within the BWP, such as combining Figure 4 , 5 8 and 11. For example, at 1110, base station 1104 can send PDCCH 1106 with scheduling offset parameter 1108 to UE 1102. The transmission of PDCCH including scheduling offset parameter can be, for example, by Figure 15 The scheduling component 1540 and / or sending component 1534 of the device 1502 are used to perform this.

[0111] At 1404, the base station can receive information from the UE indicating simulated beamforming weights, wherein the simulated beamforming weights can be determined by the UE based on a simulated beamforming codebook, and the simulated beamforming codebook is specific to a first sub-band or a second sub-band, such as in combination with... Figure 10A , 10B As described in section 11. For example, at section 1118, base station 1104 can receive the determined analog beamforming weights from UE 1102. In response, the base station can send an indication of one of K0 or K2. The reception of information indicating the analog beamforming weights can be achieved by, for example... Figure 15 The beamforming weighting processing component 1542 and / or receiving component 1530 of the device 1502 are used to perform this.

[0112] At 1406, the base station can communicate with the UE in a time slot used to transmit PDSCH based on the first subband and scheduling offset parameters within the BWP if PDCCH is used to schedule PDSCH (e.g., as shown in 1408), or in a time slot used to receive PUSCH based on the second subband and scheduling offset parameters within the BWP if PUCCH is used to schedule PUSCH (e.g., as shown in 1410), such as combining Figure 11As described above. For example, at 1117, base station 1104 can receive PUSCH from UE 1102, or send PDSCH to UE 1102 based on a first subband or a second subband. This communication can be, for example, Figure 15 The communication processor 1544, the transmitting component 1534, and / or the receiving component 1530 of the device 1502 are used to perform this function.

[0113] In one example, a base station can be configured with the PDCCH on the first CC, the PDSCH on the second CC, the PUCCH on the third CC, and the PUSCH on the fourth CC, where the first CC can be different from the second, third, or fourth CC. Note that the use of "first," "second," "third," and "fourth" does not specify a particular time order, but merely indicates different CCs, such as a combination of... Figure 9 As described, the UE can determine the time slot for receiving PDSCH based on the second CC, and the UE can determine the time slot for transmitting PUCCH and PUSCH based on the third and fourth CCs, wherein the first subband can be based on the second CC, and the second subband can be based on the third and fourth CCs, and so on. In another example, the base station can configure the duration of the QCL parameter for the UE to receive PDSCH within the BWP based on the second CC, and configure the duration for the UE to transmit PUCCH and PUSCH within the BWP based on the third and fourth CCs.

[0114] Figure 15 Figure 1500 illustrates an example of a hardware implementation of device 1502. Device 1502 may be a base station, a base station for a UE, or may implement base station functions. In some aspects, device 1502 may include a baseband unit 1504. Baseband unit 1504 may communicate with UE 104 via cellular RF transceiver 1522. Baseband unit 1504 may include computer-readable medium / memory. Baseband unit 1504 is responsible for general processing, including executing software stored on computer-readable medium / memory. When executed by baseband unit 1504, the software causes baseband unit 1504 to perform the various functions described above. Computer-readable medium / memory may also be used to store data manipulated by baseband unit 1504 when executing the software. Baseband unit 1504 also includes a receiving component 1530, a communication manager 1532, and a transmitting component 1534. Communication manager 1532 includes one or more of the components shown. Components within communication manager 1532 may be stored in computer-readable medium / memory and / or configured as hardware within baseband unit 1504. The baseband unit 1504 may be a component of the base station 310 and may include at least one of the memory 376 and / or the TX processor 316, the RX processor 370 and the controller / processor 375.

[0115] The communication manager 1532 includes a PDCCH scheduling component 1540 configured to transmit a PDCCH scheduling parameter, wherein the PDCCH schedules one of an uplink scheduling permission for the UE to receive a PDSCH in a first subband within the BWP or for the UE to transmit a PUSCH in a second subband within the BWP, and wherein the UE determines one of the time slots for receiving the PDSCH based on the first subband within the BWP and the scheduling offset parameter when the PDCCH schedules the PDSCH, or for transmitting the PUSCH based on the second subband within the BWP and the scheduling offset parameter when the PUCCH is used to schedule the PUSCH, for example, as in combination Figure 14 As described in 1402. The communication manager 1532 includes a beamforming weight processing component 1542 configured to receive information from the UE indicating simulated beamforming weights, wherein the simulated beamforming weights are determined by the UE based on a simulated beamforming codebook, and the simulated beamforming codebook is specific to a first subband or a second subband, for example, as described in 1404 of 14. The communication manager 1532 includes a communication processor 1544 configured to communicate with the UE in one of the time slots for transmitting PDSCH based on a first subband and scheduling offset parameter within the BWP if the PDCCH schedules PDSCH, or for receiving PUSCH based on a second subband and scheduling offset parameter within the BWP if the PUCCH is used to schedule PUSCH, for example, as described in 1404 of 14. Figure 14 As described in 1406.

[0116] The device may include execution Figure 14 The additional components of each box in the flowchart of the algorithm. Thus, Figure 14 Each block in the flowchart can be executed by a component, and the apparatus can include one or more of these components. These components can be one or more hardware components specifically configured to execute the process / algorithm, implemented by a processor configured to execute the process / algorithm, stored in a computer-readable medium for processor implementation, or some combination thereof.

[0117] In one configuration, apparatus 1502, and particularly in baseband unit 1504, includes components for transmitting a PDCCH including scheduling offset parameters, wherein the PDCCH schedules one of the PDSCHs for the UE to receive in a first subband within the BWP, or provides uplink scheduling permission for the PUSCH to be transmitted by the UE in a second subband within the BWP (e.g., scheduling component 1540 and / or transmission component 1534). Apparatus 1502 includes components for communicating with the UE in a time slot for transmitting the PDSCH based on the first subband within the BWP and the scheduling offset parameters if the PDCCH schedules the PDSCH, or in a time slot for receiving the PUSCH based on the second subband within the BWP and the scheduling offset parameters if the PUCCH is used to schedule the PUSCH (e.g., communication processor 1544, transmission component 1534, and / or reception component 1530).

[0118] Apparatus 1502 includes components (e.g., beamforming weight processing component 1542 and / or receiving component 1530) for receiving information indicating analog beamforming weights from a UE. The analog beamforming weights may be determined by the UE based on an analog beamforming codebook, wherein the analog beamforming codebook may be specific to a first subband or a second subband. Apparatus 1502 includes components for transmitting an indication of one of K0 or K2 in response to the received information.

[0119] In one configuration, the PDCCH is on the first CC, the PDSCH is on the second CC, the PUCCH is on the third CC, and the PUSCH is on the fourth CC, wherein the first CC may be different from the second, third, or fourth CC. The time slots used to transmit the PDSCH may be based on the second CC, and the time slots used to receive the PUCCH and PUSCH may be based on the third and fourth CCs, wherein the first subband may be based on the second CC, and the second subband may be based on the third and fourth CCs.

[0120] In another configuration, the duration of the QCL parameter used to send PDSCH within the BWP can be based on the second CC, and the duration of the PUCCH and PUSCH used to receive within the BWP can be based on the third and fourth CCs.

[0121] The component may be one or more components of device 1502, configured to perform the functions described therein. As described above, device 1502 may include TX processor 316, RX processor 370, and controller / processor 375. Thus, in one configuration, the component may be TX processor 316, RX processor 370, and controller / processor 375, configured to perform the functions listed in the component.

[0122] It should be understood that the specific order or hierarchy of blocks in the disclosed process / flowchart is an illustration of exemplary methods. Based on design preferences, it should be understood that the specific order or hierarchy of blocks in the process / flowchart can be rearranged. Furthermore, some blocks can be combined or omitted. The appended method claims present the elements of the various blocks in an exemplary order and are not intended to limit one to the specific order or hierarchy presented.

[0123] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, these claims are not intended to be limited to the aspects shown herein, but rather to conform to the full scope consistent with the language of the claims, wherein, unless specifically stated otherwise, a singular reference does not mean “one and only one,” but rather “one or more.” Terms such as “if,” “when,” and “when” should be interpreted as meaning “under the condition of,” rather than implying a direct temporal relationship or reaction. That is, these phrases, such as “when,” do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply mean that if the condition is met, the action will occur, without requiring a specific or immediate time limit for the occurrence of the action. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as superior to or better than other aspects. Unless otherwise specifically stated, the term “some” means one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may contain one or more members of A, B, or C. All structural and functional equivalents of elements throughout the various aspects described in this disclosure that are known to or will be known hereafter by those skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly recited in the claims. The terms “module,” “mechanism,” “component,” and “device” cannot replace the term “part.” Therefore, unless the element is explicitly described using the phrase “part for…”, no claim element may be interpreted as a part plus a function.

[0124] The following aspects are illustrative only and may be combined with other aspects or teachings described herein without limitation.

[0125] Aspect 1 is an apparatus for wireless communication, including at least one processor coupled to a memory, the at least one processor being configured to: receive a PDCCH including a scheduling offset parameter, wherein the PDCCH schedules one of a PDSCH for reception in a first subband within a BWP, or provides an uplink scheduling permission for a PUSCH for transmission in a second subband within the BWP; and communicate with a base station based on a time slot for receiving the PDSCH based on the first subband within the BWP and the scheduling offset parameter when the PDCCH schedules the PDSCH, or for transmitting the PUSCH based on the second subband within the BWP and the scheduling offset parameter when the PUCCH is used to schedule the PUSCH.

[0126] Aspect 2 is the apparatus according to aspect 1, wherein the time slot for receiving PDSCH is based on a first subband within the BWP and K0 of the first subband within the BWP, and the time slot for receiving PDSCH is time slot n+K0, where n is the time slot for receiving PDCCH and K0 is the time slot scheduling offset of PDSCH; or the time slot for transmitting PUSCH is based on a second subband within the BWP and K2 of the second subband within the BWP, and the time slot for transmitting PUSCH is time slot n+K2, where n is the time slot for transmitting PUCCH and K2 is the time slot scheduling offset of PUSCH.

[0127] Aspect 3 is the apparatus according to any one of aspects 1 and 2, wherein K0 is different for at least two different sub-bands within the BWP.

[0128] Aspect 4 is the apparatus according to any one of aspects 1 to 3, wherein K2 is different for at least two different sub-bands within the BWP.

[0129] Aspect 5 is an apparatus according to any one of Aspects 1 to 4, wherein the scheduling offset parameter is determined based on a first sub-band or a second sub-band, and the first sub-band or the second sub-band is a channel within a channelized frequency band.

[0130] Aspect 6 is an apparatus according to any one of aspects 1 to 5, wherein the memory and at least one processor are further configured to: send information to a base station indicating simulated beamforming weights, the simulated beamforming weights being based on a simulated beamforming codebook, wherein the simulated beamforming codebook is specific to a first subband or a second subband; and receive an indication of one of K0 or K2 in response to the sent information.

[0131] Aspect 7 is an apparatus according to any one of aspects 1 to 6, wherein the PDCCH is on a first CC, the PDSCH is on a second CC, the PUCCH is on a third CC, and the PUSCH is on a fourth CC, the first CC being different from the second, third, or fourth CC.

[0132] Aspect 8 is an apparatus according to any one of aspects 1 to 7, wherein the time slot for receiving PDSCH is further determined based on a second CC, and the time slot for transmitting PUCCH and PUSCH is further determined based on a third and a fourth CC, the first subband is based on the second CC, and the second subband is based on the third and a fourth CC.

[0133] Aspect 9 is an apparatus according to any one of aspects 1 to 8, wherein the duration of the QCL parameter for receiving PDSCH within the BWP is based on a second CC, and the duration of transmitting PUCCH and PUSCH within the BWP is based on a third and a fourth CC.

[0134] Aspect 10 is a wireless communication method for implementing any one of aspects 1 to 9.

[0135] Aspect 11 is a device for wireless communication, including components for implementing any one of aspects 1 to 9.

[0136] Aspect 12 is a computer-readable medium storing computer-executable code, wherein when executed by a processor, the code causes the processor to perform any of aspects 1 to 9.

[0137] Aspect 13 is an apparatus for wireless communication, including at least one processor coupled to a memory, the at least one processor being configured to: transmit a PDCCH including a scheduling offset parameter, wherein the PDCCH schedules one of the PDSCHs for a UE to receive in a first subband within a BWP, or provides uplink scheduling permission for a PUSCH to be transmitted by the UE in a second subband within the BWP; and, if the PDCCH schedules the PDSCH, communicate with the UE in a time slot for transmitting the PDSCH based on the first subband within the BWP and the scheduling offset parameter, or if the PUCCH is used to schedule the PUSCH, communicate with the UE in a time slot for receiving the PUSCH based on the second subband within the BWP and the scheduling offset parameter.

[0138] Aspect 14 is the apparatus according to aspect 13, wherein the scheduling offset parameter is based on a first subband or a second subband, and the first subband or the second subband is a channel within a channelized frequency band.

[0139] Aspect 15 is an apparatus according to any one of aspects 13 and 14, wherein the memory and at least one processor are further configured to: receive from the UE information indicating analog beamforming weights, wherein the analog beamforming weights are determined by the UE based on an analog beamforming codebook, and the analog beamforming codebook is specific to a first subband or a second subband; and in response to the received information, transmit an indication of one of a time slot scheduling offset K0 or a time slot scheduling offset K2.

[0140] Aspect 16 is an apparatus according to any one of aspects 13 to 15, wherein the PDCCH is on a first CC, the PDSCH is on a second CC, the PUCCH is on a third CC, and the PUSCH is on a fourth CC, the first CC being different from the second, third, or fourth CC.

[0141] Aspect 17 is an apparatus according to any one of aspects 13 to 16, wherein the time slot for transmitting PDSCH is further based on a second CC, and the time slot for receiving PUCCH and PUSCH is further based on a third and a fourth CC, the first subband is based on the second CC, and the second subband is based on the third and a fourth CC.

[0142] Aspect 18 is an apparatus according to any one of aspects 13 to 17, wherein the duration of the QCL parameter for transmitting PDSCH within the BWP is based on a second CC, and the duration for receiving PUCCH and PUSCH within the BWP is based on a third and a fourth CC.

[0143] Aspect 19 is a wireless communication method for implementing any one of aspects 13 to 18.

[0144] Aspect 20 is a device for wireless communication, including components for implementing any one of aspects 13 to 18.

[0145] Aspect 21 is a computer-readable medium storing computer-executable code, wherein when executed by a processor, the code causes the processor to perform any of aspects 13 to 18.

Claims

1. An apparatus for performing wireless communication at a user equipment (UE), comprising: Memory; as well as At least one processor coupled to the memory, the at least one processor being configured to cause the UE to: Receive a physical downlink control channel (PDCCH) including a scheduling offset parameter, wherein the PDCCH schedules one of the physical downlink shared channels (PDSCH) for reception in a first subband within the bandwidth portion (BWP), or provides uplink scheduling permission for the physical uplink shared channel (PUSCH) for transmission in a second subband within the BWP. as well as To communicate with the base station, a time slot is used to receive the PDSCH based on the first subband within the BWP and the scheduling offset parameter when the PDCCH schedules the PDSCH, or a time slot is used to transmit the PUSCH based on the second subband within the BWP and the scheduling offset parameter when the PUSCH is scheduled using the Physical Uplink Control Channel (PUCCH), wherein the time slot for receiving the PDSCH is determined to be time slot n+K0, where n is the time slot for receiving the PDCCH and K0 is the time slot scheduling offset of the PDSCH; or the time slot for transmitting the PUSCH is determined to be time slot n+K2, where n is the time slot for transmitting the PUCCH and K2 is the time slot scheduling offset of the PUSCH, wherein K0 is different for at least two different subbands within the BWP, and K2 is different for at least two different subbands within the BWP.

2. The apparatus of claim 1, wherein the scheduling offset parameter is sub-band specific, and the first sub-band or the second sub-band is a channel within a channelized frequency band.

3. The apparatus of claim 1, wherein the at least one processor is further configured to cause the UE to: Sending information indicating simulated beamforming weights to the base station, the simulated beamforming weights being based on a simulated beamforming codebook, wherein the simulated beamforming codebook is specific to the first sub-band or the second sub-band; and Responding to the sent information to receive an instruction from either K0 or K2.

4. The apparatus of claim 1, wherein the PDCCH is on a first component carrier CC, the PDSCH is on a second CC, the PUCCH is on a third CC, and the PUSCH is on a fourth CC, wherein the first CC is different from the second, third, or fourth CC.

5. The apparatus of claim 4, wherein the time slot for receiving the PDSCH is further determined based on the second CC, and the time slot for transmitting the PUCCH and the PUSCH is further determined based on the third and fourth CCs, the first subband being based on the second CC and the second subband being based on the third and fourth CCs.

6. The apparatus of claim 4, wherein the duration for receiving the QCL parameter of the PDSCH within the BWP is based on the second CC, and the duration for transmitting the PUCCH and the PUSCH within the BWP is based on the third and fourth CCs.

7. A wireless communication method for a user equipment (UE), comprising: Receive a physical downlink control channel (PDCCH) including a scheduling offset parameter, wherein the PDCCH schedules one of the physical downlink shared channels (PDSCH) for reception in a first subband within the bandwidth portion (BWP), or provides uplink scheduling permission for the physical uplink shared channel (PUSCH) for transmission in a second subband within the BWP. as well as A time slot is determined for receiving the PDSCH based on the first subband within the BWP and the scheduling offset parameter when the PDCCH schedules the PDSCH, or for transmitting the PUSCH based on the second subband within the BWP and the scheduling offset parameter when the PUSCH is scheduled using the Physical Uplink Control Channel (PUCCH). The time slot for receiving the PDSCH is determined to be time slot n+K0, where n is the time slot for receiving the PDCCH and K0 is the time slot scheduling offset for the PDSCH. Alternatively, the time slot for transmitting the PUSCH is determined to be time slot n+K2, where n is the time slot for transmitting the PUCCH and K2 is the time slot scheduling offset for the PUSCH. K0 is different for at least two different subbands within the BWP, and K2 is different for at least two different subbands within the BWP.

8. The method of claim 7, wherein the scheduling offset parameter is subband-specific, and the first subband or the second subband is a channel within a channelized frequency band.

9. The method according to claim 7, further comprising: Send information to the base station indicating simulated beamforming weights, the simulated beamforming weights being based on a simulated beamforming codebook, wherein the simulated beamforming codebook is specific to the first subband or the second subband; as well as Responding to the sent information to receive an instruction from either K0 or K2.

10. The method of claim 7, wherein the PDCCH is on a first component carrier CC, the PDSCH is on a second CC, the PUCCH is on a third CC, and the PUSCH is on a fourth CC, wherein the first CC is different from the second, third, or fourth CC.

11. The method of claim 10, wherein the time slot for receiving the PDSCH is further determined based on the second CC, and the time slot for transmitting the PUCCH and the PUSCH is further determined based on the third and fourth CCs, the first subband being based on the second CC and the second subband being based on the third and fourth CCs.

12. The method of claim 10, wherein the duration for receiving the QCL parameter of the PDSCH within the BWP is based on the second CC, and the duration for transmitting the PUCCH and the PUSCH within the BWP is based on the third and fourth CCs.

13. An apparatus for conducting wireless communication at a base station, comprising: Memory; as well as At least one processor coupled to the memory, the at least one processor being configured to cause the base station to: Transmit a physical downlink control channel (PDCCH) including a scheduling offset parameter, wherein the PDCCH schedules one of the physical downlink shared channels (PDSCH) for the UE to receive in a first subband within the bandwidth portion (BWP), or provides uplink scheduling permission for the physical uplink shared channel (PUSCH) for the UE to transmit in a second subband within the BWP. as well as The time slot used to transmit the PDSCH based on the first subband within the BWP and the scheduling offset parameter when the PDCCH schedules the PDSCH, or the time slot used to receive the PUSCH based on the second subband within the BWP and the scheduling offset parameter when the PUSCH is scheduled using the Physical Uplink Control Channel (PUCCH), is used to communicate with the UE. The first sub-band and the second sub-band are channels within the channelized frequency band, and the first sub-band and the second sub-band have different scheduling offset parameters.

14. The apparatus of claim 13, wherein the at least one processor is further configured to cause the base station to: Receive information from the UE indicating simulated beamforming weights, wherein the simulated beamforming weights are determined by the UE based on a simulated beamforming codebook, and wherein the simulated beamforming codebook is specific to the first sub-band or the second sub-band; and In response to the received information, an indication of either time slot scheduling offset K0 or time slot scheduling offset K2 is sent.

15. The apparatus of claim 13, wherein the PDCCH is on a first component carrier CC, the PDSCH is on a second CC, the PUCCH is on a third CC, and the PUSCH is on a fourth CC, the first CC being different from the second, third, or fourth CC.

16. The apparatus of claim 15, wherein the time slot for transmitting the PDSCH is further determined based on the second CC, and the time slot for receiving the PUCCH and the PUSCH is further determined based on the third and fourth CCs, the first subband being based on the second CC and the second subband being based on the third and fourth CCs.

17. The apparatus of claim 15, wherein the duration for transmitting the QCL parameter of the PDSCH within the BWP is based on the second CC, and the duration for receiving the PUCCH and the PUSCH within the BWP is based on the third and fourth CCs.

18. A method for conducting wireless communication at a base station, comprising: Transmit a physical downlink control channel (PDCCH) including scheduling offset parameters, wherein the PDCCH schedules one of the physical downlink shared channels (PDSCH) for the UE to receive in a first subband within the bandwidth portion (BWP), or provides uplink scheduling permission for the physical uplink shared channel (PUSCH) for the UE to transmit in a second subband within the BWP. as well as The time slot used to transmit the PDSCH based on the first subband within the BWP and the scheduling offset parameter when the PDCCH schedules the PDSCH, or the time slot used to receive the PUSCH based on the second subband within the BWP and the scheduling offset parameter when the PUSCH is scheduled using the Physical Uplink Control Channel (PUCCH), is used to communicate with the UE. The first sub-band and the second sub-band are channels within the channelized frequency band, and the first sub-band and the second sub-band have different scheduling offset parameters.

19. The method of claim 18, further comprising: The UE receives information indicating simulated beamforming weights, wherein the simulated beamforming weights are determined by the UE based on a simulated beamforming codebook, and wherein the simulated beamforming codebook is specific to the first subband or the second subband. as well as In response to the received information, an indication of either time slot scheduling offset K0 or time slot scheduling offset K2 is sent.

20. The method of claim 18, wherein the PDCCH is on a first component carrier CC, the PDSCH is on a second CC, the PUCCH is on a third CC, and the PUSCH is on a fourth CC, wherein the first CC is different from the second, third, or fourth CC.

21. The method of claim 20, wherein the time slot for transmitting the PDSCH is further determined based on the second CC, and the time slot for receiving the PUCCH and the PUSCH is further determined based on the third and fourth CCs, the first subband being based on the second CC and the second subband being based on the third and fourth CCs.

22. The method of claim 20, wherein the duration for transmitting the QCL parameter of the PDSCH within the BWP is based on the second CC, and the duration for receiving the PUCCH and the PUSCH within the BWP is based on the third and fourth CCs.

Images