Time domain resource block mapping

Abstract

Methods, systems, and apparatus for performing wireless communication are described. A network entity can receive first control information scheduled for the reception of a first message during a time-frequency resource set. The network entity can receive second control information associated with a Time Domain Resource Block (TDRB) pattern, wherein the TDRB pattern defines a first TDRB during at least a portion of the time-frequency resource set, and the first TDRB includes a set of Orthogonal Frequency Division Multiplexing (OFDM) symbols. The network entity can demodulate data based on the TDRB pattern. In some examples, the network entity can receive and cache the data during the first TDRB before demodulating it, wherein demodulation is performed for the first TDRB, and then the data is cached or demodulated for subsequent TDRBs.

Description

[0001] Cross-referencing

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 393,253, entitled “TIME-DOMAINRESOURCE BLOCK MAPPING”, filed December 21, 2023, by YANG et al., which has been assigned to the assignee of this application and is expressly incorporated herein by reference. Background Technology

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE). The following discussion relates to wireless communication in connection with resource element mapping. Summary of the Invention

[0004] The described technology relates to improved methods, systems, devices, and apparatuses supporting Time Domain Resource Block (TDRB) mapping. For example, the described technology provides for performing resource mapping based on a TDRB pattern. For instance, a network entity may receive control information scheduling the reception of messages during a time-frequency resource set, as well as control information associated with the TDRB pattern. In some examples, the network entity may receive an indication of the TDRB pattern, or in other examples, the network entity may receive an indication of the definitions to be used to determine the start and end boundaries of the TDRB pattern. In other words, the network entity may receive an indication of the TDRB pattern or an indication of how to determine the TDRB pattern. The network entity may receive, cache, and demodulate data during a TDRB defined by the TDRB pattern. For example, for the first TDRB in time of the TDRB pattern, the network entity may receive, cache, and demodulate data. The network entity may receive, cache, and demodulate data for a second TDRB in time of the TDRB pattern after demodulating data for the first TDRB. That is, the network entity may cache and demodulate data based on TDRBs.

[0005] A method for wireless communication by a network entity is described. The method may include: receiving first control information, the first control information scheduling the reception of a first message during a time-frequency resource set by the network entity; receiving second control information associated with a TDRB pattern, wherein the TDRB pattern defines a first TDRB during at least a portion of the time-frequency resource set, and wherein the first TDRB includes a set of orthogonal frequency division multiplexing (OFDM) symbols; and demodulating data based on the TDRB pattern.

[0006] A network entity for wireless communication is described. The network entity may include a processing system configured to: receive first control information scheduled for reception of a first message during a time-frequency resource set; receive second control information associated with a TDRB pattern, wherein the TDRB pattern defines a first TDRB during at least a portion of the time-frequency resource set, and wherein the first TDRB includes a set of OFDM symbols; and demodulate data based on the TDRB pattern.

[0007] Another network entity for wireless communication is described. The network entity may include: components for receiving first control information scheduled for the reception of a first message during a time-frequency resource set; components for receiving second control information associated with a TDRB pattern, wherein the TDRB pattern defines a first TDRB during at least a portion of the time-frequency resource set, and wherein the first TDRB includes a set of OFDM symbols; and components for demodulating data based on the TDRB pattern.

[0008] A non-transitory computer-readable medium having code for wireless communication stored thereon is described. When executed by a network entity, the code enables the network entity to: receive first control information, the first control information scheduling the reception of a first message during a time-frequency resource set; receive second control information associated with a TDRB pattern, wherein the TDRB pattern defines a first TDRB during at least a portion of the time-frequency resource set, and wherein the first TDRB includes a set of OFDM symbols; and demodulate data based on the TDRB pattern.

[0009] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving the data during the first TDRB; and caching the data received during the first TDRB for subsequent processing.

[0010] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the network entity may be configured to demodulate the data after the last OFDM symbol at the time of the first TDRB in order to demodulate the data.

[0011] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for performing a channel estimation process after the last OFDM symbol in the time of the first TDRB, wherein the channel estimation process may be based on a portion of the data received during the first TDRB.

[0012] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the TDRB pattern definition includes a set of multiple TDRBs of the first TDRB, and wherein the codewords of the first message can be resource-mapped to the first TDRB according to a per-TDRB-based mapping scheme.

[0013] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the mapping scheme may be a time-first, frequency-second mapping scheme within each of the multiple TDRBs in this set.

[0014] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the mapping scheme may be a frequency-first, time-second mapping scheme within each of the multiple TDRBs in this set.

[0015] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the set of multiple TDRBs includes one or more TDRBs in each of multiple subbands, and wherein the mapping scheme may be a first frequency and a second time mapping scheme within each TDRB in the set of multiple TDRBs, and a first subband and a second time mapping scheme between the various TDRBs in the set of multiple TDRBs.

[0016] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the TDRB pattern includes the first TDRB and one or more second TDRBs that follow the first TDRB in time.

[0017] In some examples of the methods, network entities, and nontransient computer-readable media described herein, the first TDRB includes one or more time boundaries based on the location of demodulation reference signal (DMRS) symbols, wherein the one or more boundaries include at least one of a time start boundary or a time end boundary.

[0018] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the termination boundary may be defined by the fact that the last OFDM symbol in the time of the first TDRB is a DMRS symbol.

[0019] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the starting boundary may be defined by the fact that the first OFDM symbol in the time of the first TDRB is a DMRS symbol.

[0020] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first TDRB and the first second TDRB in time of one or more second TDRBs immediately following the first TDRB may be defined by a DMRS symbol, which may be the last OFDM symbol in time of the first TDRB or the first OFDM symbol in time of the first second TDRB in time of one or more second TDRBs.

[0021] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first TDRB or at least one of the one or more second TDRBs may be defined as including a DMRS symbol, which may be a channel estimation source for one or more OFDM symbols in adjacent TDRBs of the one or more second TDRBs.

[0022] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the adjacent TDRB may be one of the first or last TDRB in time among the one or more second TDRBs.

[0023] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the last TDRB in one or more of the one or more second TDRBs does not include DMRS at any given time.

[0024] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the last TDRB at one or more times each includes only one OFDM symbol or fewer than a threshold number of OFDM symbols.

[0025] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the first TDRB and at least one of the one or more second TDRBs include an end boundary that is temporally aligned with the time slot boundary.

[0026] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the second control information may indicate the number of DMRS or DMRS timings per TDRB, the maximum duration of the TDRB, or a combination thereof.

[0027] In some examples of the methods, network entities, and non-transitory computer-readable media described herein, the second control information may indicate the TDRB pattern.

[0028] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the second control information indicates that the network entity may switch to or from the application of the TDRB pattern.

[0029] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the second control information may be received via Radio Resource Control (RRC) messages, Media Access Control-Control Element (MAC-CE), Downlink Control Message (DCI) messages, or any combination thereof.

[0030] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for reporting channel estimation time window duration information, wherein the second control information may be based on the channel estimation time window duration information.

[0031] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, the second control information includes a DMRS pattern or an updated TDRB pattern, or both, that can be based on channel estimation time window duration information.

[0032] A method for wireless communication performed by a first network entity is described. The method may include: transmitting first control information, the first control information scheduling the reception of a first message by a second network entity during a time-frequency resource set; and transmitting second control information associated with a TDRB pattern, wherein the TDRB pattern defines a first TDRB during at least a portion of the time-frequency resource set, and wherein the first TDRB includes a set of OFDM symbols.

[0033] A first network entity for wireless communication is described. The first network entity may include: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute the code to cause the first network entity to: transmit first control information scheduled for reception of a first message during a time-frequency resource set of the second network entity; and transmit second control information associated with a TDRB pattern, wherein the TDRB pattern defines a first TDRB during at least a portion of the time-frequency resource set, and wherein the first TDRB includes a set of OFDM symbols.

[0034] Another first network entity for wireless communication is described. The first network entity may include: means for transmitting first control information scheduled for reception of a first message during a time-frequency resource set at a second network entity; and means for transmitting second control information associated with a TDRB pattern, wherein the TDRB pattern defines a first TDRB during at least a portion of the time-frequency resource set, and wherein the first TDRB includes a set of OFDM symbols.

[0035] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by one or more processors to: transmit first control information scheduled for reception of a first message by a second network entity during a time-frequency resource set; and transmit second control information associated with a TDRB pattern, wherein the TDRB pattern defines a first TDRB during at least a portion of the time-frequency resource set, and wherein the first TDRB includes a set of OFDM symbols.

[0036] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the TDRB pattern definition includes a set of multiple TDRBs of the first TDRB, and wherein the codewords of the first message can be resource-mapped to the first TDRB according to a per-TDRB-based mapping scheme.

[0037] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the mapping scheme may be a time-first, frequency-second mapping scheme within each of the multiple TDRBs in the set.

[0038] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the mapping scheme may be a frequency-first, time-second mapping scheme within each of the multiple TDRBs in the set.

[0039] In some examples of the methods, first network entities, and nontransitory computer-readable media described herein, the set of multiple TDRBs includes one or more TDRBs in each of multiple subbands, and wherein the mapping scheme may be a first frequency and a second time mapping scheme within each TDRB in the set of multiple TDRBs, and a first subband and a second time mapping scheme between the various TDRBs in the set of multiple TDRBs.

[0040] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the TDRB pattern includes the first TDRB and one or more second TDRBs that follow the first TDRB in time.

[0041] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the first TDRB includes one or more temporal boundaries based on the location of DMRS symbols, wherein the one or more boundaries include at least one of a temporal start boundary or a temporal end boundary.

[0042] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the termination boundary may be defined by the fact that the last OFDM symbol in time of the first TDRB is a DMRS symbol.

[0043] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the initial boundary may be defined by the fact that the first OFDM symbol in the time of the first TDRB is a DMRS symbol.

[0044] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the first TDRB and the first second TDRB in time among one or more second TDRBs immediately following the first TDRB may be defined by a DMRS symbol, which may be the last OFDM symbol in time of the first TDRB or the first OFDM symbol in time of the first second TDRB among the one or more second TDRBs.

[0045] In some examples of the methods described herein, the first network entity, and the nontransient computer-readable medium, the first TDRB or at least one of the one or more second TDRBs may be defined as including DMRS symbols, which may be a channel estimation source for one or more OFDM symbols in adjacent TDRBs of the one or more second TDRBs.

[0046] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the adjacent TDRB may be one of the first or last TDRB in time among the one or more second TDRBs.

[0047] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the last TDRB in one or more of the one or more second TDRBs does not include the DMRS at any given time.

[0048] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the one or more time-last TDRBs each comprise only one OFDM symbol or fewer than a threshold number of OFDM symbols.

[0049] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the first TDRB and at least one of the one or more second TDRBs include an end boundary that is temporally aligned with the time slot boundary.

[0050] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the second control information may indicate the number of DMRS or DMRS timings per TDRB, the maximum duration of the TDRB, or a combination thereof.

[0051] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the second control information may indicate the TDRB pattern.

[0052] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the second control information indicates that the second network entity may switch to or from the application of the TDRB pattern.

[0053] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the second control information may be sent via an RRC message, a Media Access Control-Control Element (MAC-CE), a DCI message, or any combination thereof.

[0054] The methods described herein, examples of the first network entity, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for receiving a report including channel estimation time window duration information, wherein the second control information may be based on the channel estimation time window duration information.

[0055] In some examples of the methods described herein, the first network entity, and the nontransitory computer-readable medium, the second control information includes a DMRS pattern or an updated TDRB pattern, or both, that can be based on channel estimation time window duration information. Attached Figure Description

[0056] Figure 1 and Figure 2 Examples of wireless communication systems supporting TDRB mapping according to one or more aspects of this disclosure are shown.

[0057] Figure 3 Examples of TDRB pattern diagrams supporting TDRB mapping according to one or more aspects of this disclosure are shown.

[0058] Figure 4 An example of a resource element mapping diagram supporting TDRB mapping according to one or more aspects of this disclosure is shown.

[0059] Figure 5 An example of a process flow supporting TDRB mapping is shown according to one or more aspects of this disclosure.

[0060] Figure 6 and Figure 7 A block diagram of a device supporting TDRB mapping according to one or more aspects of this disclosure is shown.

[0061] Figure 8 A block diagram of a communication manager supporting TDRB mapping according to one or more aspects of this disclosure is shown.

[0062] Figure 9 A diagram of a system including a device supporting TDRB mapping is shown according to one or more aspects of this disclosure.

[0063] Figure 10 and Figure 11 A flowchart illustrating a method for supporting TDRB mapping according to one or more aspects of this disclosure is shown. Detailed Implementation

[0064] Wireless devices can map data signals to resources in a frequency-first, time-second manner, where the data signal is mapped across all frequency tones of a first symbol, then across all frequency tones of a second symbol, and so on. This frequency-first, time-second mapping allows for relatively rapid channel estimation after the data signal is received. However, channel estimation can be performed quickly when a demodulation reference signal (DMRS) appears at the beginning of the data signal. In other words, channel estimation can be performed quickly when the DMRS of the data signal is preloaded. For example, a receiving device can perform demodulation after decoding the first symbol of the signal (which may include the DMRS) and subsequently perform channel estimation. In some cases, to improve the quality of channel estimation, the data signal may include DMRS at the beginning of the signal and at one or more other instances. In other words, several symbols of the data signal may include DMRS, which may be discontinuous in time. In such cases, the receiving device may experience delays associated with channel estimation, demodulation, or both, based on waiting to decode additional symbols appearing throughout the data signal before initiating channel estimation. Furthermore, storing channel estimates across the entire frequency range may be associated with high memory usage at the receiving device.

[0065] Wireless devices can perform multi-round channel estimation based on channel estimation windows. For example, a wireless device can decompose the channel estimation into multiple groups, which can be called channel estimation windows, allowing the wireless device to perform demodulation after each corresponding group, thereby reducing latency. The channel estimation window can correspond to a Time Domain Resource Block (TDRB), where resource mapping is performed for each TDRB. That is, the transmitting device can map the corresponding codeword to a first TDRB, then to a second TDRB, and so on. This mapping can be a time-first, frequency-second mapping within each TDRB, and in some examples, it can be based on one or more subbands. TDRB mapping can support reduced memory usage at the receiving device because the receiving device can store channel estimates for a given TDRB, TDRB subband, or both, rather than channel estimates across the entire frequency and resource block. TDRB mapping can also support reduced latency at the receiving device when, for example, the data signal comprises multiple discontinuous DMRSs.

[0066] The various aspects of this disclosure are first described in the context of a wireless communication system. They are also described in the context of TDRB pattern diagrams, resource element mapping diagrams, and process flows. The various aspects of this disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts related to TDRB mapping.

[0067] Figure 1An example of a wireless communication system 100 supporting TDRB mapping according to one or more aspects of this disclosure is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

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

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

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

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

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

[0073] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC, a non-real-time RIC), a service management and orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

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

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

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

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

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

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

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

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

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

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

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

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

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

[0087] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base station 140) can have similar frame timings, and transmissions from different network entities 105 can be approximately time-aligned. For asynchronous operation, network entities 105 can have different frame timings, and in some examples, transmissions from different network entities 105 may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

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

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

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

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

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

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

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

[0095] Network entity 105 or UE 115 can use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique is known as spatial multiplexing. The multiple signals can be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals can be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.

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

[0097] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority processing and multiplexing of logical channels to transport channels. The MAC layer can also implement error detection, error correction, or both to support retransmission and improve link efficiency. In the control plane, the RRC layer can provide the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 supporting user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0098] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0099] As described herein, a network entity (which may alternatively be referred to as an entity, node, network node, or wireless entity) can be, can be similar to, can include, or can be included in (e.g., can be a component of): a base station (e.g., any base station described herein, including a decomposed base station), a UE (e.g., any UE described herein), a RedCap device, an enhanced RedCap device, an ambient Internet of Things (IoT) device, an energy harvesting (EH) capable device, a network controller, apparatus, device, computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, a network entity can be a UE. As another example, a network entity can be a base station. As used herein, “network entity” can mean an entity configured to operate in a network (such as network 105). For example, “network entity” is not limited to an entity currently located in and / or currently operating in the network. Instead, a network entity can be any entity capable of communicating and / or operating within a network.

[0100] The adjectives "first," "second," "third," etc., are used to distinguish between two or more modified nouns in context, and do not imply absolute modifiers applicable only to a specific corresponding entity throughout the document. For example, a network entity may be referred to as "first network entity" in one discussion and as "second network entity" in another, and vice versa. As an example, the first network entity may be configured to communicate with a second network entity or a third network entity. In one aspect of this example, the first network entity may be a UE, the second network entity may be a base station, and the third network entity may be a UE. In another aspect of this example, the first network entity may be a UE, the second network entity may be a base station, and the third network entity may be a base station. In yet other aspects of this example, the first, second, and third network entities may be different from these examples.

[0101] Similarly, references to UE, base station, device, equipment, computing system, etc., may include disclosures of UE, base station, device, equipment, computing system, etc., as network entities. For example, a disclosure of a UE being configured to receive information from a base station also discloses that a first network entity is configured to receive information from a second network entity. Consistent with this disclosure, once a particular example is extended according to this disclosure (e.g., a disclosure of a UE being configured to receive information from a base station also discloses that a first network entity is configured to receive information from a second network entity), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station and a first network entity is configured to receive information from a second network entity, the first network entity may refer to a first UE, a first base station, a first device, a first equipment, a first computing system, a first set of one or more components, a first processing entity, etc., configured to receive information; and the second network entity may refer to a second UE, a second base station, a second device, a second equipment, a second computing system, a second set of one or more components, a second processing entity, etc.

[0102] As described herein, different terms may be used in various contexts to describe the transmission of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network entity may be described as being configured to send information to a second network entity. In this example and consistent with this disclosure, disclosure that a first network entity is configured to send information to a second network entity includes disclosure that the first network entity is configured to provide, transmit, output, communicate, or send information to the second network entity. Similarly, in this example and consistent with this disclosure, disclosure that a first network entity is configured to send information to a second network entity includes disclosure that the second network entity is configured to receive, obtain, or decode information provided, transmitted, output, communicate, or sent by the first network entity.

[0103] As shown in the figure, a network entity (e.g., network entity 105) may include a processing system 106. Similarly, a network entity (e.g., UE 115) may include a processing system 112. A processing system may include one or more components (or sub-components), such as those described herein. For example, a corresponding component among these one or more components may be, similar to, include, or be included in at least one memory, at least one communication interface, or at least one processor. For example, a processing system may include one or more components. In such an example, the one or more components may include a first component, a second component, and a third component. In this example, the first component may be coupled to the second and third components. In this example, the first component may be at least one processor, the second component may be a communication interface, and the third component may be at least one memory. A processing system is generally one or more components of a system capable of performing one or more functions (such as any function or combination of functions described herein). For example, one or more components may receive input information (e.g., any information as input, such as a signal, any digital information, or any other information), one or more components may process the input information to generate output information (e.g., any information as output, such as a signal or any other information), one or more components may perform any function as described herein or any combination thereof. As described herein, “input” and “input information” can be used interchangeably. Similarly, as described herein, “output” and “output information” can be used interchangeably. Any information generated by any component can be provided to one or more other systems or components of network entities such as those described herein. For example, a processing system may include a first component configured to receive or obtain information, a second component configured to process the information to generate output information, and / or a third component configured to provide the output information to other systems or components. In this example, the first component may be a communication interface (e.g., a first communication interface), the second component may be at least one processor (e.g., coupled to the communication interface and / or at least one memory), and the third component may be a communication interface (e.g., a first communication interface or a second communication interface). For example, a processing system may include at least one memory, at least one communication interface, and / or at least one processor, wherein the at least one processor may, for example, be coupled to the at least one memory and the at least one communication interface.

[0104] The processing system of the network entity described herein can interface with one or more other components of the network entity, process information received from one or more other components (such as input information), or output such information to one or more other components. For example, the processing system may include a first component configured to interface with one or more other components of the network entity to receive or obtain information, a second component configured to process the information to generate one or more outputs, and / or a third component configured to output the one or more outputs to one or more other components. In this example, the first component may be a communication interface (e.g., a first communication interface), the second component may be at least one processor (e.g., coupled to the communication interface and / or at least one memory), and the third component may be a communication interface (e.g., the first communication interface or the second communication interface). For example, a chip or modem of the network entity may include the processing system. The processing system may include a first communication interface for receiving or obtaining information, and a second communication interface for outputting, transmitting, or providing information. In some examples, the first communication interface may be an interface configured to receive input information, and such information may be provided to the processing system. In some examples, the second system interface may be configured to transmit information output from the chip or modem. The second communication interface can also obtain or receive input information, and the first communication interface can also output, send, or provide information.

[0105] As described herein, network entity 105, UE 115, or both may perform resource mapping according to a TDRB pattern. For example, network entity 105 may receive control information scheduling the reception of messages during a time-frequency resource set, as well as control information associated with the TDRB pattern. In some examples, network entity 105 may (e.g., directly) receive an indication of the TDRB pattern, or network entity 105 may receive an indication of the definition of the start and end boundaries to be used to determine the TDRB pattern (e.g., an indication of how to determine the TDRB pattern). Network entity 105 may receive, cache, and demodulate data during a TDRB defined by the TDRB pattern. For example, during a first TDRB (e.g., temporally) of the TDRB pattern, network entity 105 may receive, cache, and demodulate data. Network entity 105 may receive, cache, and demodulate data during a second TDRB (e.g., temporally) of the TDRB pattern after demodulating data for the first TDRB.

[0106] Figure 2 An example of a wireless communication system 200 supporting TDRB mapping according to one or more aspects of this disclosure is shown. The wireless communication system 200 may implement, or be implemented by, various aspects of the wireless communication system 100. For example, the wireless communication system 200 may include network entities 105 and UE 115, which may represent as referenced... Figure 1 Examples of the corresponding devices described.

[0107] Network entity 105 may transmit one or more data signals, including DMRS 205, to UE 115. For example, network entity 105 may transmit data signal 210 via a time-frequency resource set. One or more symbols of the time-frequency resources may include DMRS 205. For example, the time-frequency resource set may include at least a first OFDM symbol in which DMRS 205 may be distributed. That is, DMRS 205 may be mapped to resource elements of the time-frequency resource set according to a DMRS sequence or configuration. As an example, DMRS 205 in the first OFDM symbol may be distributed to every other (e.g., every two) resource elements in the frequency domain of the time-frequency resource set. In some other examples, DMRS 205 in the first OFDM symbol may be distributed to every other two resource elements in the frequency domain of the time-frequency resource set. Resource elements in the first OFDM symbol that are not filled with DMRS 205 may include data or may be empty (e.g., excluding signals).

[0108] UE 115 can use DMRS 205 to demodulate signals from the physical channel and perform channel estimation. For example, UE 115 can estimate properties associated with the physical channel (e.g., PDCCH, PDSCH, etc.) based on receiving and demodulating data signal 210 including DMRS 205. In other words, UE 115 can perform channel estimation after receiving DMRS 205. However, in some examples, data signal 210 may include more than one DMRS to improve the quality of UE 115's channel estimation, where DMRS 205 may be distributed across a set of time-frequency resources. That is, DMRS 205 may not be preloaded. UE 115 may experience increased latency (e.g., compared to the case of preloaded DMRS) because UE 115 may wait until all DMRS 205 are received before performing channel estimation. Furthermore, the data signal 210, including DMRS 205, can be associated with large memory usage at UE 115, because UE 115 can store channel estimates across the entire time-frequency resource set before demodulating the data signal 210.

[0109] Network entity 105 and UE 115 can reduce latency and memory usage at UE 115 associated with receiving data signal 210 by implementing TDRB. For example, network entity 105 can map data signal 210 according to a TDRB pattern that includes a corresponding TDRB group, on which UE 115 will cache and demodulate data (e.g., to perform channel estimation). In other words, UE 115 can cache and demodulate data signal 210 according to the TDRB pattern to reduce latency and memory usage associated with receiving data signal 210 including DMRS 205.

[0110] For example, network entity 105 may send first control information 215 to UE 115, which schedules the reception of a first message during a time-frequency resource set. Data signal 210 may include the first message. Network entity 105 may send second control information 220 to UE 115 associated with a TDRB pattern. For example, the TDRB pattern may define at least a first TDRB during at least a portion of the time-frequency resource set. The first TDRB may correspond to an OFDM symbol set.

[0111] The second control information 220 associated with the TDRB pattern may include the TDRB pattern itself or information associated with the TDRB pattern, such that the UE 115 can identify (e.g., determine) the TDRB pattern based on this information. For example, network entity 105 may send one or more signals including information for the UE 115 to determine the TDRB pattern via RRC messages, Media Access Control-Control Element (MAC-CE) messages, Downlink Control Information (DCI) messages, etc.

[0112] In some examples, network entity 105 may indicate the number of DMRS symbols per TDRB. Additionally or alternatively, network entity 105 may indicate the number of DMRS timings per TDRB (e.g., in a dual DMRS symbol example). That is, UE 115 may receive an indication of the number of DMRS symbols per TDRB and accordingly identify or determine the boundaries between TDRBs. Additionally or alternatively, network entity 105 may indicate a threshold (e.g., minimum or maximum) duration for a TDRB. For example, UE 115 may determine a TDRB pattern to satisfy the indicated threshold duration. In some examples, network entity 105 may indicate a TDRB pattern (e.g., an exact TDRB pattern, a direct indication, etc.). For example, network entity 105 may indicate a TDRB pattern to be used by UE 115 to cache and demodulate data signal 210.

[0113] In some examples, network entity 105 may indicate (e.g., via second control information 220 or transmitted separately) mapping rules. For example, network entity 105 may instruct UE 115 to use TDRB-based mapping; frequency-first, time-second mapping; subband-based mapping; or a combination thereof. In some examples, network entity 105 may indicate a new mapping rule that overrides a previously indicated mapping rule.

[0114] Network entity 105 may send data signal 210 to UE 115 after, for example, instructing first control information 215, second control information 220, or both. UE 115 may cache (e.g., store) data for OFDM symbols of TDRB and perform channel estimation based on TDRB values. In other words, UE 115 may cache data and perform channel estimation based on the received first and second control information. As an example, UE 115 may cache data for a first set of OFDM symbols of first TDRB 225-a and perform channel estimation based on DMRS 205 in first TDRB 225-a. After performing channel estimation for first TDRB 225-a, UE 115 may cache data for a second set of OFDM symbols of second TDRB 225-b and perform channel estimation based on DMRS 205 in second TDRB 225-b. For example, first TDRB 225-a may occur before second TDRB 225-b in time.

[0115] In some examples, UE 115 may decode data within a first TDRB 225-a, a second TDRB 225-b, or both, according to a time-first, frequency-second mapping scheme. In other examples, UE 115 may decode data within a first TDRB 225-a, a second TDRB 225-b, or both, according to a subband-first, time-second mapping scheme. That is, UE 115 may first decode data across subbands of frequency resource sets within a TDRB, and then decode data across TDRBs of time resource sets. For example, UE 115 may decode data across a first subband 230-a and a first TDRB 225-a, across a second subband 230-b and a first TDRB 225-a, across a first subband 230-a and a second TDRB 225-b, and finally across a second subband 230-b and a second TDRB 225-b. Subband- and TDRB-based mappings may be found elsewhere in this document (including references). Figure 4 (See further details.) Subband-based mapping can reduce memory usage at UE 115 (e.g., compared to mapping across the entire frequency band). For example, UE 115 can cache data for subband-TDRB combinations.

[0116] UE 115 may report channel estimation time window duration information 235 to network entity 105. For example, UE 115 may report channel estimation time window duration information 235 based on performing channel estimation after receiving data signal 210 or before receiving second control information 220. Channel estimation time window duration information 235 may include a request from UE 115 to shorten or extend the channel estimation time window duration based on receiving data signal 210 and performing channel estimation. As an example, UE 115 may report that the channel estimation time window duration (e.g., the symbol length of TDRB) is too long and request a shorter duration to reduce latency. Alternatively, UE 115 may request the channel estimation time window duration to meet a threshold latency before receiving second control information 220. Network entity 105 may send second control information 220 based on receiving channel estimation time window duration information 235, or in some other examples, adjust the DMRS pattern, TDRB pattern, or both used for downlink transmission.

[0117] Figure 3 An example of a TDRB pattern diagram 300 supporting TDRB mapping according to one or more aspects of this disclosure is shown. The TDRB pattern diagram 300 may implement, or be implemented by, various aspects of wireless communication system 100, wireless communication system 200, or both. For example, the TDRB pattern diagram 300 may be implemented by a wireless device such as network entity 105 or UE 115, which may represent as referenced... Figure 1 and Figure 2 Examples of the corresponding devices described.

[0118] A network entity or UE may perform multi-round channel estimation based on multiple channel estimation windows. A channel estimation window may correspond to a corresponding TDRB, where each TDRB comprises a set of OFDM symbols. In some examples, the network entity or UE may determine a TDRB pattern. That is, the network entity or UE may determine the boundaries between corresponding TDRBs on a set of time-frequency resources. In some examples, the boundaries between corresponding TDRBs may be based on the position of DMRS symbols within the set of time-frequency resources. For example, the network entity may indicate a set of rules to be used by the UE to determine the TDRB pattern, or in some other examples, the network entity may determine the TDRB pattern based on that set of rules and indicate the TDRB pattern to the UE. The following examples of TDRB patterns may represent TDRB patterns determined or identified by a network entity or UE.

[0119] In the example of TDRB pattern diagram 300, the TDRB pattern can be determined (e.g., by a network entity or UE) based on the location of the DMRS within the time-frequency resource set. For example, the first TDRB pattern 305-a may include TDRB 310-a and TDRB 310-b. The boundary between TDRB 310-a and TDRB 310-b may be defined by the last DMRS symbol of TDRB 310-a. For example, this boundary may be the end boundary of TDRB 310-a. In some other examples, the boundary DMRS symbol (e.g., the last DMRS symbol of TDRB 310-a in the previous example) may be defined as the start boundary of TDRB 310-b. That is, TDRB 310-a may include the boundary DMRS symbol. In other words, the boundary between TDRB 310-a and TDRB 310-b can be defined by a DMRS symbol, which can be included in TDRB 310-a (e.g., as shown in the example of the first TDRB pattern 305-a) or TDRB 310-b.

[0120] The second TDRB pattern 305-b may include TDRB 310-c and TDRB 310-d. In an example of the second TDRB pattern 305-b, TDRB 310-c and TDRB 310-d may include resource blocks adjacent to the first DMRS symbol, the last DMRS symbol, or both. For example, TDRB 310-c may include a resource block adjacent to the first DMRS symbol of TDRB 310-c. Additionally or alternatively, TDRB 310-d may include a resource block adjacent to the last DMRS symbol of TDRB 310-d. In other words, the first and last TDRBs of the time-frequency resource set may include adjacent resource blocks at the beginning or end of the TDRB.

[0121] The third TDRB pattern 305-c may include TDRB 310-e, TDRB 310-f, TDRB 310-g, and TDRB 310-h. In the example of the third TDRB pattern 305-c, resource blocks adjacent to the last DMRS symbol of the last TDRB that includes DMRS may form individual TDRBs. That is, resource blocks following the last DMRS symbol of TDRB 310-f may form TDRB 310-g and TDRB 310-h, instead of being included in adjacent TDRBs. In some examples, resource blocks following the last DMRS symbol of TDRB 310-f may form TDRBs per OFDM symbol, or in some other examples, TDRBs per threshold number of OFDM symbols. For example, TDRB 310-g or TDRB 310-h may include a number of OFDM symbols less than a threshold number of OFDM symbols.

[0122] In an example of the third TDRB pattern 305-c, TDRB 310-e may include adjacent resource blocks preceding the first DMRS symbol. In other words, the third TDRB pattern 305-c may include grouping adjacent resource blocks preceding the first DMRS symbol, but not grouping adjacent resource blocks following the last DMRS symbol. In some examples, the third TDRB pattern 305-c may support receive pipelined operations compared to, for example, the second TDRB pattern 305-b. Additionally or alternatively, the third TDRB pattern 305-c may allow the radio device to fall back to a frequency-first, time-second resource mapping with a preloaded DMRS.

[0123] Although not explicitly shown in the example of TDRB pattern diagram 400, a TDRB pattern may include a first TDRB and a second TDRB having boundaries defined by time slot boundaries. That is, the first TDRB may end at the end of the first time slot, and the second TDRB may begin at the beginning of the second time slot. For example, time-frequency resource sets may occur across time slot boundaries (e.g., in the case of a long SLIV).

[0124] Figure 4 An example of a resource element mapping diagram 400 supporting TDRB mapping according to one or more aspects of this disclosure is shown. The resource element mapping diagram 400 may implement, or be implemented by, various aspects of wireless communication system 100, wireless communication system 200, or both. For example, the resource element mapping diagram 400 may be implemented by a wireless device such as network entity 105 or UE 115, which may represent as referenced... Figure 1 and Figure 2 Examples of the corresponding devices described.

[0125] A network entity or UE can perform multi-round channel estimation based on multiple channel estimation windows. A channel estimation window may correspond to a corresponding TDRB, where each TDRB comprises a set of OFDM symbols. In some examples, the network entity or UE can determine a TDRB pattern. That is, the network entity or UE can determine the boundaries between corresponding TDRBs on a set of time-frequency resources. In some examples, the set of time-frequency resources can be further partitioned by splitting the frequency resources into two or more sub-bands. That is, the UE can decode transmissions for a given sub-band, and in some examples, decode transmissions for a sub-band-TDRB combination.

[0126] For example, the UE can decode data signals within the corresponding TDRB according to a subband first, time second mapping scheme. That is, the UE can first decode data across subbands of frequency resource sets within a TDRB, and then decode data across TDRBs of time resource sets. In other words, TDRBs and subbands can form subband-TDRB combinations (e.g., portions of time-frequency resources), and the UE can individually decode, cache, and perform channel estimation based on this subband-TDRB combination. Figure 4 In the example, the time-frequency resource set may include a first TDRB 405-a and a second TDRB 405-b in the time domain and a first subband 410-a and a second subband 410-b in the frequency domain. Although Figure 4 The example shows two TDRBs and two subbands, but it is understood that more or fewer TDRBs or subbands can be implemented. The corresponding pairing of TDRBs and subbands forms a subband-TDRB combination. As an example, the combination of the first TDRB 405-a and the first subband 410-a forms a first subband-TDRB combination 415-a.

[0127] The UE (e.g., a receiving device) can decode data for each sub-band-TDRB combination using a first sub-band, second TDRB sequence. For example, the UE can decode data in the first sub-band-TDRB combination 405-a for a portion of a first OFDM symbol across the first sub-band 230-a, a portion of a second OFDM symbol across the first sub-band 230-a, and so on for each OFDM symbol in the first TDRB 415-a. In other words, the UE can decode data within each sub-band-TDRB combination using a first frequency, second time sequence.

[0128] After decoding data for the first subband-TDRB combination 415-a, the UE can decode data for the second subband-TDRB combination 415-b formed by the second subband 410-b and the first TDRB 405-a. That is, the UE can decode data for subsequent subbands of the first TDRB 405-a before decoding data for the second TDRB 405-b. For example, after decoding data for the second subband-TDRB combination 415-b, the UE can decode data for the third subband-TDRB combination 415-c formed by the first subband 410-a and the second TDRB 405-b, and the fourth subband-TDRB combination 415-d formed by the second subband 410-b and the second TDRB 405-b.

[0129] Additionally or alternatively, network entities (e.g., transmitting devices) may map data for each subband-TDRB combination in a first subband, second TDRB order. For example, a network entity may map data in the first subband-TDRB combination 405-a for a portion of a first OFDM symbol across the first subband 230-a, a portion of a second OFDM symbol across the first subband 230-a, and so on for each OFDM symbol in the first TDRB 415-a. In other words, a network entity may map data within each subband-TDRB combination in a frequency-first, time-second manner.

[0130] After mapping data for the first subband-TDRB combination 415-a, the network entity can map data for the second subband-TDRB combination 415-b formed by the second subband 410-b and the first TDRB 405-a. That is, the network entity can map data for subsequent subbands of the first TDRB 405-a before decoding data for the second TDRB 405-b. For example, after mapping data for the second subband-TDRB combination 415-b, the network entity can map data for the third subband-TDRB combination 415-c formed by the first subband 410-a and the second TDRB 405-b, and the fourth subband-TDRB combination 415-d formed by the second subband 410-b and the second TDRB 405-b.

[0131] Figure 5 An example of a process flow 500 supporting TDRB mapping according to one or more aspects of this disclosure is shown. In some examples, process flow 500 may be implemented as described in the reference. Figure 1 or Figure 2 The described aspects of wireless communication system 100 or wireless communication system 200, or aspects of these two wireless communication systems, are implemented. For example, process flow 500 may be implemented by network entity 105-a and network entity 105-b, which may be as described in the reference... Figure 1 and Figure 2 An example of the described network entity 105. Process flow 500 may also implement aspects of TDRB pattern diagram 300, resource element mapping diagram 400, or both, or be implemented by these aspects. Alternative examples are possible, some of which may be performed in a different order than described or not at all. In some cases, steps may include additional features not mentioned below, or additional steps may be added.

[0132] At point 505, network entity 105-b can receive first control information, which is scheduled for reception of a first message at network entity 105-b during a time-frequency resource set. For example, the first control information can be scheduled for data signals (such as reference signals). Figure 2 The data signal 210 described is received.

[0133] At point 510, network entity 105-b can report channel estimation time window duration information. For example, the channel estimation time window duration information may include information about the length of the channel estimation time window. For example, network entity 105-b can report channel estimation time window duration information 225, as referenced... Figure 2 As described.

[0134] At 515, network entity 105-b may receive second control information associated with the TDRB pattern. In some examples, network entity 105-a may transmit the second control information via RRC messages, MAC-CE, DCI messages, etc. The TDRB pattern may define a first TDRB during at least a portion of the time-frequency resource set. The first TDRB may include a set of OFDM symbols. In some examples, the second control information may be based on channel estimation time window duration information received by network entity 105-a at 510. For example, the second control information may include a DMRS pattern based on the channel estimation time window duration information, an updated TDRB pattern, or both.

[0135] A TDRB pattern can define multiple TDRBs including a first TDRB, wherein the codewords of a first message are resource-mapped to the first TDRB according to a per-TDRB-based mapping scheme. In some examples, the mapping scheme may be a time-first, frequency-second mapping scheme within each TDRB of the multiple TDRBs. In some other examples, the mapping scheme may be a frequency-first, time-second mapping scheme within each TDRB of the multiple TDRBs. Additionally or alternatively, the multiple TDRBs may include one or more TDRBs in each of a multiple sub-bands. For example, the mapping scheme may be a frequency-first, time-second mapping scheme within each TDRB of the multiple TDRBs, and a sub-band-first, time-second mapping scheme between the various TDRBs of the multiple TDRBs. That is, the mapping scheme may be as referenced. Figure 4 Example of the resource element mapping diagram 400 described.

[0136] In some examples, a TDRB pattern may include a first TDRB and one or more second TDRBs that follow the first TDRB in time. That is, a TDRB pattern may include multiple TDRBs, some of which follow the first TDRB in time. The first TDRB may include one or more temporal boundaries based on the location of the DMRS symbol, wherein the one or more boundaries include a temporal start boundary, a temporal end boundary, or both. For example, the end boundary may be defined by the fact that the last OFDM symbol of the first TDRB in time is a DMRS symbol. Additionally or alternatively, the start boundary may be defined by the fact that the first OFDM symbol of the first TDRB in time is a DMRS symbol.

[0137] In some examples, the first TDRB and the time-first second TDRB in one or more second TDRBs immediately following the first TDRB may be defined by a DMRS symbol, which is either the time-last OFDM symbol of the first TDRB or the time-first OFDM symbol of the time-first second TDRB in one or more second TDRBs. Additionally or alternatively, the first TDRB or at least one of the one or more second TDRBs may be defined as including a DMRS symbol, which is a channel estimation source for one or more OFDM symbols in adjacent TDRBs of one or more second TDRBs. For example, an adjacent TDRB may be either the time-first TDRB or the time-last TDRB in one or more second TDRBs.

[0138] In some examples, the last TDRB in one or more times of a second TDRB may not include DMRS. For example, after the last DMRS, the TDRB pattern may include a single TDRB per OFDM symbol or a small number of OFDM symbols. In other words, the last TDRB in one or more times may each include only one OFDM symbol or fewer than a threshold number of OFDM symbols.

[0139] Additionally or alternatively, at least one of the first TDRB and one or more second TDRBs may include an end boundary that is time-aligned with the time slot boundary. For example, in the case of transmission across time slot boundaries (e.g., in the case of a long SLIV), the first TDRB may stop at the time slot boundary.

[0140] In some examples, the second control information may indicate the number of DMRS or DMRS timings per TDRB, the maximum duration of the TDRB, or both. Additionally or alternatively, the second control information may indicate the TDRB pattern (e.g., the exact TDRB pattern).

[0141] The second control information can instruct network entity 105-b to switch to or from the application of a TDRB pattern. For example, the second control information can instruct network entity 105-b to switch between a TDRB-based mapping and another mapping rule (e.g., frequency first, time second, sub-band based mapping, etc.).

[0142] At 520, network entity 105-b may receive data during the first TDRB. When network entity 105-b receives data, at 525, network entity 105-b may (e.g., simultaneously or immediately after receiving the data) cache the data received at 520 during the first TDRB for subsequent processing.

[0143] At position 530, network entity 105-b can demodulate data. For example, network entity 105-b can demodulate data based on a TDRB pattern. In some examples, network entity 105-b can demodulate data after the last OFDM symbol at the time of the first TDRB.

[0144] At 535, network entity 105-b may perform a channel estimation process after the last OFDM symbol in the first TDRB time, wherein the channel estimation process is based on a portion of the data received during the first TDRB.

[0145] Figure 6A block diagram 600 of a device 605 supporting TDRB mapping according to one or more aspects of this disclosure is shown. Device 605 may be an example of aspects of network entity 105 as described herein. Device 605 may include receiver 610, transmitter 615, and communication manager 620. Device 605, or one or more components of device 605 (e.g., receiver 610, transmitter 615, and communication manager 620), may include at least one processor that can be coupled to at least one memory to individually or jointly support or implement the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

[0146] Receiver 610 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 605. In some examples, receiver 610 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 610 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0147] Transmitter 615 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 605. For example, transmitter 615 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 615 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 615 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 615 and receiver 610 may be co-located in a transceiver, which may include or be coupled to a modem.

[0148] The communication manager 620, receiver 610, transmitter 615, or various combinations thereof, or various components thereof, may be examples of components for performing various aspects of the TDRB mapping as described herein. For example, the communication manager 620, receiver 610, transmitter 615, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

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

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

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

[0152] According to the examples disclosed herein, the communication manager 620 may support wireless communication. For example, the communication manager 620 is capable of, configured to, or operable to support components for receiving first control information scheduled for reception of a first message during a time-frequency resource set by a network entity. The communication manager 620 is capable of, configured to, or operable to support components for receiving second control information associated with a TDRB pattern, wherein the TDRB pattern defines a first TDRB during at least a portion of the time-frequency resource set, and wherein the first TDRB includes a set of OFDM symbols. The communication manager 620 is capable of, configured to, or operable to support components for demodulating data based on the TDRB pattern.

[0153] Additionally or alternatively, the communication manager 620 may support wireless communication according to the examples disclosed herein. For example, the communication manager 620 may be capable of, configured to, or operable to support components for transmitting first control information scheduled for reception of a first message at a second network entity during a time-frequency resource set. The communication manager 620 may be capable of, configured to, or operable to support components for transmitting second control information associated with a TDRB pattern, wherein the TDRB pattern defines a first TDRB during at least a portion of the time-frequency resource set, and wherein the first TDRB includes a set of OFDM symbols.

[0154] By including or configuring a communication manager 620 according to an example as described herein, device 605 (e.g., controlling receiver 610, transmitter 615, communication manager 620 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for more efficient use of communication resources.

[0155] Figure 7 A block diagram 700 of a device 705 supporting TDRB mapping according to one or more aspects of this disclosure is shown. Device 705 may be an example of aspects of device 605 or network entity 105 as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. Device 705, or one or more components of device 705 (e.g., receiver 710, transmitter 715, and communication manager 720), may include at least one processor that can be coupled to at least one memory to support the described technology. Each of these components may communicate with each other (e.g., via one or more buses).

[0156] Receiver 710 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 705. In some examples, receiver 710 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 710 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0157] Transmitter 715 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 705. For example, transmitter 715 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 715 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 715 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 715 and receiver 710 may be co-located in a transceiver, which may include or be coupled to a modem.

[0158] Device 705 or its various components may be examples of parts for performing various aspects of TDRB mapping as described herein. For example, communication manager 720 may include scheduling component 725, TDRB patterning component 730, demodulation component 735, or any combination thereof. Communication manager 720 may be examples of aspects of communication manager 620 as described herein. In some examples, communication manager 720 or its various components may be configured to use or otherwise cooperate with receiver 710, transmitter 715, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 720 may receive information from receiver 710, transmit information to transmitter 715, or be integrated in combination with receiver 710, transmitter 715, or both to acquire information, output information, or perform various other operations as described herein.

[0159] According to the examples disclosed herein, the communication manager 720 may support wireless communication. The scheduling component 725 is capable of, configured to, or operable to support components for receiving first control information scheduled for reception of a first message during a time-frequency resource set by a network entity. The TDRB pattern component 730 is capable of, configured to, or operable to support components for receiving second control information associated with a TDRB pattern, wherein the TDRB pattern defines a first TDRB during at least a portion of the time-frequency resource set, and wherein the first TDRB includes a set of OFDM symbols. The demodulation component 735 is capable of, configured to, or operable to support components for demodulating data based on the TDRB pattern.

[0160] Additionally or alternatively, the communication manager 720 may support wireless communication according to examples disclosed herein. The scheduling component 725 is capable of, configured to, or operable to support components for transmitting first control information scheduled for reception of a first message at a second network entity during a time-frequency resource set. The TDRB pattern component 730 is capable of, configured to, or operable to support components for transmitting second control information associated with a TDRB pattern, wherein the TDRB pattern defines a first TDRB during at least a portion of the time-frequency resource set, and wherein the first TDRB includes a set of OFDM symbols.

[0161] Figure 8 A block diagram 800 of a communication manager 820 supporting TDRB mapping according to one or more aspects of this disclosure is shown. The communication manager 820 may be an example of aspects of the communication manager 620, communication manager 720, or both as described herein. The communication manager 820 or its various components may be examples of components for performing various aspects of TDRB mapping as described herein. For example, the communication manager 820 may include a scheduling component 825, a TDRB patterning component 830, a demodulation component 835, a data receiving component 840, a cache component 845, a channel estimation component 850, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and this communication may include communication within protocol layers of a protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0162] According to the examples disclosed herein, the communication manager 820 may support wireless communication. The scheduling component 825 is capable of, configured to, or operable to support components for receiving first control information scheduled for reception of a first message during a time-frequency resource set by a network entity. The TDRB pattern component 830 is capable of, configured to, or operable to support components for receiving second control information associated with a TDRB pattern, wherein the TDRB pattern defines a first TDRB during at least a portion of the time-frequency resource set, and wherein the first TDRB includes a set of OFDM symbols. The demodulation component 835 is capable of, configured to, or operable to support components for demodulating data based on the TDRB pattern.

[0163] In some examples, the data receiving component 840 is capable of, configured to, or operable to support components for receiving data during the first TDRB. In some examples, the cache component 845 is capable of, configured to, or operable to support components for caching data received during the first TDRB for subsequent processing.

[0164] In some examples, to demodulate data, the network entity is configured to demodulate data after the last OFDM symbol at the time of the first TDRB.

[0165] In some examples, the channel estimation component 850 is capable of, configured to, or able to operate to support components for performing a channel estimation process after the last OFDM symbol at the time of the first TDRB, wherein the channel estimation process is based on a portion of the data received during the first TDRB.

[0166] In some examples, the TDRB pattern definition includes a set of multiple TDRBs of the first TDRB, and the codeword of the first message is resource-mapped to the first TDRB according to a per-TDRB-based mapping scheme.

[0167] In some examples, the mapping scheme is a time-first, frequency-second mapping scheme within each TDRB in a set of multiple TDRBs.

[0168] In some examples, the mapping scheme is a frequency-first, time-second mapping scheme within each TDRB in a set of multiple TDRBs.

[0169] In some examples, the set of multiple TDRBs includes one or more TDRBs in each of multiple subbands, and the mapping scheme is a first frequency and a second time mapping scheme within each TDRB in the set of multiple TDRBs, and a first subband and a second time mapping scheme between the various TDRBs in the set of multiple TDRBs.

[0170] In some examples, the TDRB pattern includes a first TDRB and one or more second TDRBs that follow the first TDRB in time.

[0171] In some examples, the first TDRB includes one or more time boundaries based on the location of the DMRS symbol, wherein the one or more boundaries include at least one of a time start boundary or a time end boundary.

[0172] In some examples, the end boundary is defined by the last OFDM symbol in the first TDRB time being the DMRS symbol.

[0173] In some examples, the starting boundary is defined by the first OFDM symbol in the time of the first TDRB being the DMRS symbol.

[0174] In some examples, the first TDRB and the first second TDRB in time within one or more second TDRBs immediately following the first TDRB are defined by a DMRS symbol, which is either the last OFDM symbol in time of the first TDRB or the first OFDM symbol in time of the first second TDRB within one or more second TDRBs.

[0175] In some examples, a first TDRB or at least one of one or more second TDRBs is defined as including a DMRS symbol, which is a channel estimation source for one or more OFDM symbols in adjacent TDRBs of one or more second TDRBs.

[0176] In some examples, an adjacent TDRB is one of the first or last second TDRB in time among one or more second TDRBs.

[0177] In some examples, the last TDRB in one or more of the second TDRBs does not include the DMRS at one or more times.

[0178] In some examples, the last TDRB at one or more times each includes only one OFDM symbol or fewer than the threshold number of OFDM symbols.

[0179] In some examples, at least one of the first TDRB and one or more second TDRBs includes an end boundary that is temporally aligned with the slot boundary.

[0180] In some examples, the second control information indicates the number of DMRS or DMRS timings per TDRB, the maximum duration of the TDRB, or a combination thereof.

[0181] In some examples, the second control information indicates the TDRB pattern.

[0182] In some examples, the second control information instructs the network entity to switch to or from the application of the TDRB pattern.

[0183] In some examples, the second control information is received via RRC messages, MAC-CE, DCI messages, or any combination thereof.

[0184] In some examples, the channel estimation component 850 is capable of, configured to, or able to operate to support components for reporting channel estimation time window duration information, wherein the second control information is based on the channel estimation time window duration information.

[0185] In some examples, the second control information includes a DMRS pattern based on channel estimation time window duration information or an updated TDRB pattern, or both.

[0186] Additionally or alternatively, the communication manager 820 may support wireless communication according to examples disclosed herein. In some examples, the scheduling component 825 is capable of, configured to, or operable to support means for transmitting first control information scheduled for reception of a first message at a second network entity during a time-frequency resource set. In some examples, the TDRB pattern component 830 is capable of, configured to, or operable to support means for transmitting second control information associated with a TDRB pattern, wherein the TDRB pattern defines a first TDRB during at least a portion of the time-frequency resource set, and wherein the first TDRB includes a set of OFDM symbols.

[0187] In some examples, the TDRB pattern definition includes a set of multiple TDRBs of the first TDRB, and the codeword of the first message is resource-mapped to the first TDRB according to a per-TDRB-based mapping scheme.

[0188] In some examples, the mapping scheme is a time-first, frequency-second mapping scheme within each TDRB in a set of multiple TDRBs.

[0189] In some examples, the mapping scheme is a frequency-first, time-second mapping scheme within each TDRB in a set of multiple TDRBs.

[0190] In some examples, the set of multiple TDRBs includes one or more TDRBs in each of multiple subbands, and the mapping scheme is a first frequency and a second time mapping scheme within each TDRB in the set of multiple TDRBs, and a first subband and a second time mapping scheme between the various TDRBs in the set of multiple TDRBs.

[0191] In some examples, the TDRB pattern includes a first TDRB and one or more second TDRBs that follow the first TDRB in time.

[0192] In some examples, the first TDRB includes one or more time boundaries based on the location of the DMRS symbol, wherein the one or more boundaries include at least one of a time start boundary or a time end boundary.

[0193] In some examples, the end boundary is defined by the last OFDM symbol in the first TDRB time being the DMRS symbol.

[0194] In some examples, the starting boundary is defined by the first OFDM symbol in the time of the first TDRB being the DMRS symbol.

[0195] In some examples, the first TDRB and the first second TDRB in time within one or more second TDRBs immediately following the first TDRB are defined by a DMRS symbol, which is either the last OFDM symbol in time of the first TDRB or the first OFDM symbol in time of the first second TDRB within one or more second TDRBs.

[0196] In some examples, a first TDRB or at least one of one or more second TDRBs is defined as including a DMRS symbol, which is a channel estimation source for one or more OFDM symbols in adjacent TDRBs of one or more second TDRBs.

[0197] In some examples, an adjacent TDRB is one of the first or last second TDRB in time among one or more second TDRBs.

[0198] In some examples, the last TDRB in one or more of the second TDRBs does not include the DMRS at one or more times.

[0199] In some examples, the last TDRB at one or more times each includes only one OFDM symbol or fewer than the threshold number of OFDM symbols.

[0200] In some examples, at least one of the first TDRB and one or more second TDRBs includes an end boundary that is temporally aligned with the slot boundary.

[0201] In some examples, the second control information indicates the number of DMRS or DMRS timings per TDRB, the maximum duration of the TDRB, or a combination thereof.

[0202] In some examples, the second control information indicates the TDRB pattern.

[0203] In some examples, the second control information instructs the second network entity to switch to or from the application of the TDRB pattern.

[0204] In some examples, the second control information is sent via RRC messages, Media Access Control-Control Element (MAC-CE), DCI messages, or any combination thereof.

[0205] In some examples, the channel estimation component 850 is capable of, configured to, or able to operate to support components for receiving reports including channel estimation time window duration information, wherein the second control information is based on the channel estimation time window duration information.

[0206] In some examples, the second control information includes a DMRS pattern based on channel estimation time window duration information or an updated TDRB pattern, or both.

[0207] Figure 9 A diagram of a system 900 including a device 905 supporting TDRB mapping, according to one or more aspects of this disclosure, is shown. Device 905 may be an example of device 605, device 705, or network entity 105 as described herein, or may include components thereof. Device 905 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and this communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 905 may include components supporting output and acquisition of communication, such as a communication manager 920, a transceiver 910, an antenna 915, at least one memory 925, code 930, and at least one processor 935. These components may communicate electronically or otherwise (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 940).

[0208] Transceiver 910 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 910 may include a wired transceiver and be able to communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, transceiver 910 may include a wireless transceiver and be able to communicate bidirectionally with another wireless transceiver. In some examples, device 905 may include one or more antennas 915 that may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). Transceiver 910 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., by one or more antennas 915, by a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 915, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 910 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 915 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 915 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 910 may include one or more processors or one or more memory components, or be configured to couple to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 910, or transceiver 910 and one or more antennas 915, or transceiver 910 and one or more antennas 915 and one or more processors or one or more memory components (e.g., at least one processor 935, at least one memory 925, or both), may be included in a chip or chip assembly mounted in device 905. In some examples, transceiver 910 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0209] At least one memory 925 may include RAM, ROM, or any combination thereof. At least one memory 925 may store computer-readable, computer-executable code 930 including instructions that, when executed by one or more processors of at least one processor 935, cause device 905 to perform the various functions described herein. Code 930 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 930 may not be directly executable by one of the processors of at least one processor 935, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 925 may also include a BIOS, among other things, that controls basic hardware or software operation, such as interaction with peripheral components or devices. In some examples, at least one processor 935 may include multiple processors, and at least one memory 925 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0210] At least one processor 935 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 935 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into one or more processors in at least one processor 935. At least one processor 935 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 925) to cause device 905 to perform various functions (e.g., functions or tasks supporting TDRB mapping). For example, device 905 or components of device 905 may include at least one processor 935 and at least one memory 925 coupled to one or more processors in at least one processor 935, at least one processor 935 and at least one memory 925 configured to perform the various functions described herein. At least one processor 935 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can host functions (e.g., by executing code 930) to perform the functions of device 905. At least one processor 935 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 905, such as within one or more memories of at least one memory 925. In some examples, at least one processor 935 may include multiple processors, and at least one memory 925 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 935 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 935) and memory circuitry (which may include at least one memory 925)) or components that receive or obtain input and process the input to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 935 or a processing system including at least one processor 935 may be configured, configured to, or operable to cause device 905 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 925 or otherwise.

[0211] In some examples, bus 940 may support communication at protocol layers (e.g., within a protocol layer) in a protocol stack. In some examples, bus 940 may support communication associated with logical channels of a protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 905, or communication performed between different components of device 905 that are co-addressable or may be located in different locations (e.g., where device 905 may refer to a system in which one or more of communication manager 920, transceiver 910, at least one memory 925, code 930, and at least one processor 935 may be located in one of the different components or partitioned between the different components).

[0212] In some examples, the communication manager 920 can manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 920 can manage the transfer of data communication between client devices such as one or more UEs 115. In some examples, the communication manager 920 can manage communication with other network entities 105 and may include a controller or scheduler for cooperating with other network entities 105 to control communication with UE 115. In some examples, the communication manager 920 may support the X2 interface in LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0213] According to the examples disclosed herein, the communication manager 920 may support wireless communication. For example, the communication manager 920 is capable of, configured to, or operable to support components for receiving first control information scheduled for reception of a first message during a time-frequency resource set by a network entity. The communication manager 920 is capable of, configured to, or operable to support components for receiving second control information associated with a TDRB pattern, wherein the TDRB pattern defines a first TDRB during at least a portion of the time-frequency resource set, and wherein the first TDRB includes a set of OFDM symbols. The communication manager 920 is capable of, configured to, or operable to support components for demodulating data based on the TDRB pattern.

[0214] Additionally or alternatively, the communication manager 920 may support wireless communication according to examples disclosed herein. For example, the communication manager 920 may be capable of, configured to, or operable to support components for transmitting first control information scheduled for reception of a first message at a second network entity during a time-frequency resource set. The communication manager 920 may be capable of, configured to, or operable to support components for transmitting second control information associated with a TDRB pattern, wherein the TDRB pattern defines a first TDRB during at least a portion of the time-frequency resource set, and wherein the first TDRB includes a set of OFDM symbols.

[0215] By including or configuring a communication manager 920 according to an example as described herein, device 905 can support techniques for reducing latency, utilizing communication resources more efficiently, and improving processing power utilization.

[0216] In some examples, the communication manager 920 may be configured to use a transceiver 910, one or more antennas 915 (e.g., where applicable), or any combination thereof, or otherwise cooperate with them, to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported or performed by the transceiver 910, one or more processors in at least one processor 935, one or more memories in at least one memory 925, code 930, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 935, at least one memory 925, code 930, or any combination thereof). For example, code 930 may include instructions that can be executed by one or more processors in at least one processor 935 to cause device 905 to perform various aspects of the TDRB mapping as described herein, or at least one processor 935 and at least one memory 925 may be otherwise configured to perform or support such operations individually or jointly.

[0217] Figure 10 A flowchart illustrating a method 1000 supporting TDRB mapping according to one or more aspects of this disclosure is shown. The operation of method 1000 may be implemented by a network entity or its components as described herein. For example, the operation of method 1000 may be implemented by, as referenced... Figures 1 to 9 The network entity described herein performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0218] At 1005, the method may include receiving first control information, which is scheduled for reception of a first message by the network entity during a time-frequency resource set. The operation of block 1005 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1005 may be provided by reference to [reference needed]. Figure 8 The described scheduling component 825 is used for execution.

[0219] At 1010, the method may include receiving second control information associated with a TDRB pattern, wherein the TDRB pattern defines a first TDRB during at least a portion of a time-frequency resource set, and wherein the first TDRB includes a set of OFDM symbols. Operation of block 1010 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1010 may be provided by reference to [reference needed]. Figure 8 The TDRB mode component 830 described is used to execute this.

[0220] At 1015, the method may include demodulating data based on a TDRB pattern. The operation of block 1015 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1015 may be derived from references... Figure 8 The demodulation component 835 described is used to perform this.

[0221] Figure 11 A flowchart illustrating a method 1100 supporting TDRB mapping according to one or more aspects of this disclosure is shown. The operation of method 1100 may be implemented by a network entity or its components as described herein. For example, the operation of method 1100 may be implemented by, as referenced... Figures 1 to 9 The network entity described herein performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0222] At 1105, the method may include receiving first control information, which is scheduled for reception of a first message at a time-frequency resource set by the network entity. Operation of block 1105 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1105 may be provided by reference to [reference needed]. Figure 8 The described scheduling component 825 is used for execution.

[0223] At 1110, the method may include receiving second control information associated with a TDRB pattern, wherein the TDRB pattern defines a first TDRB during at least a portion of a time-frequency resource set, and wherein the first TDRB includes a set of OFDM symbols. The operation of block 1110 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1110 may be provided by reference to [reference needed]. Figure 8 The TDRB mode component 830 described is used to execute this.

[0224] At 1115, the method may include receiving data during the first TDRB. The operation of block 1115 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1115 may be derived from references... Figure 8 The data receiving component 840 described herein shall perform this action.

[0225] At 1120, the method may include caching data received during the first TDRB for subsequent processing. The operation of block 1120 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1120 may be provided by reference to [reference needed]. Figure 8 The described cache component 845 is used for execution.

[0226] At 1125, the method may include demodulating data based on a TDRB pattern. The operation of block 1125 may be performed according to examples disclosed herein. In some examples, aspects of the operation of 1125 may be derived from references... Figure 8 The demodulation component 835 described is used to perform this.

[0227] The following provides an overview of the various aspects of this disclosure: Aspect 1: A method for wireless communication by a network entity, the method comprising: receiving first control information, the first control information scheduling the reception of a first message by the network entity during a time-frequency resource set; receiving second control information associated with a TDRB pattern, wherein the TDRB pattern defines a first TDRB during at least a portion of the time-frequency resource set, and wherein the first TDRB includes a set of OFDM symbols; and demodulating data based on the TDRB pattern.

[0228] Aspect 2: According to the method of aspect 1, the method further includes: receiving the data during the first TDRB; and caching the data received during the first TDRB for subsequent processing.

[0229] Aspect 3: The method according to any one of Aspects 1 to 2, wherein, in order to demodulate the data, the network entity is configured to demodulate the data after the last OFDM symbol in the time of the first TDRB.

[0230] Aspect 4: The method according to any one of Aspects 1 to 3, the method further comprising: performing a channel estimation process after the last OFDM symbol in the time of the first TDRB, wherein the channel estimation process is based on a portion of the data received during the first TDRB.

[0231] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the TDRB pattern definition includes a plurality of TDRBs of the first TDRB, and wherein the codeword of the first message is resource-mapped to the first TDRB according to a mapping scheme based on each TDRB.

[0232] Aspect 6: According to the method of aspect 5, the mapping scheme is a time first and frequency second mapping scheme within each of the plurality of TDRBs.

[0233] Aspect 7: The method according to any one of Aspects 5 to 6, wherein the mapping scheme is a first frequency and a second time mapping scheme within each of the plurality of TDRBs.

[0234] Aspect 8: The method according to any one of Aspects 5 to 7, wherein the plurality of TDRBs includes one or more TDRBs in each of a plurality of subbands, and wherein the mapping scheme is a first frequency and a second time mapping scheme within each of the plurality of TDRBs, and a first subband and a second time mapping scheme between the respective TDRBs of the plurality of TDRBs.

[0235] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the TDRB pattern includes the first TDRB and one or more second TDRBs that follow the first TDRB in time.

[0236] Aspect 10: According to the method of aspect 9, the first TDRB includes one or more time boundaries based on the location of the DMRS symbol, wherein the one or more boundaries include at least one of a time start boundary or a time end boundary.

[0237] Aspect 11: According to the method of aspect 10, the termination boundary is defined by the last OFDM symbol in time of the first TDRB being a DMRS symbol.

[0238] Aspect 12: The method according to any one of Aspects 10 to 11, wherein the starting boundary is defined by the first OFDM symbol in time of the first TDRB being a DMRS symbol.

[0239] Aspect 13: The method according to any one of Aspects 9 to 12, wherein the first second TDRB immediately following the first TDRB in time is defined by a DMRS symbol, the DMRS symbol being either the last OFDM symbol in time of the first TDRB or the first OFDM symbol in time of the first second TDRB in time of the one or more second TDRBs.

[0240] Aspect 14: The method according to any one of Aspects 9 to 13, wherein the first TDRB or at least one of the one or more second TDRBs is defined as including a DMRS symbol, the DMRS symbol being a channel estimation source for one or more OFDM symbols in adjacent TDRBs of the one or more second TDRBs.

[0241] Aspect 15: According to the method of aspect 14, the adjacent TDRB is one of the first or last second TDRB in time among the one or more second TDRBs.

[0242] Aspect 16: The method according to any one of aspects 9 to 15, wherein the last TDRB at one or more times of the one or more second TDRBs does not include DMRS.

[0243] Aspect 17: According to the method of aspect 16, the last TDRB in one or more times each includes only one OFDM symbol or fewer than a threshold number of OFDM symbols.

[0244] Aspect 18: The method according to any one of Aspects 9 to 17, wherein at least one of the first TDRB and the one or more second TDRBs includes an end boundary that is temporally aligned with the time slot boundary.

[0245] Aspect 19: The method according to any one of Aspects 1 to 18, wherein the second control information indicates the number of DMRS or DMRS timings per TDRB, the maximum duration of the TDRB, or a combination thereof.

[0246] Aspect 20: The method according to any one of aspects 1 to 19, wherein the second control information indicates the TDRB pattern.

[0247] Aspect 21: The method according to any one of Aspects 1 to 20, wherein the second control information instructs the network entity to switch to or from the application of the TDRB pattern.

[0248] Aspect 22: The method according to any one of Aspects 1 to 21, wherein the second control information is received via an RRC message, MAC-CE, DCI message or any combination thereof.

[0249] Aspect 23: The method according to any one of aspects 1 to 22, the method further comprising: reporting channel estimation time window duration information, wherein the second control information is based on the channel estimation time window duration information.

[0250] Aspect 24: The method according to any one of Aspects 1 to 23, wherein the second control information comprises a DMRS pattern based on channel estimation time window duration information or an updated TDRB pattern or both.

[0251] Aspect 25: A method for wireless communication by a first network entity, the method comprising: transmitting first control information, the first control information scheduling the reception of a first message by a second network entity during a time-frequency resource set; transmitting second control information associated with a TDRB pattern, wherein the TDRB pattern defines a first TDRB during at least a portion of the time-frequency resource set, and wherein the first TDRB includes a set of OFDM symbols.

[0252] Aspect 26: According to the method of aspect 25, wherein the TDRB pattern definition includes a plurality of TDRBs of the first TDRB, and wherein the codeword of the first message is resource-mapped to the first TDRB according to a per-TDRB-based mapping scheme.

[0253] Aspect 27: According to the method of aspect 26, the mapping scheme is a time first and frequency second mapping scheme within each of the plurality of TDRBs.

[0254] Aspect 28: The method according to any one of Aspects 26 to 27, wherein the mapping scheme is a first frequency and a second time mapping scheme within each of the plurality of TDRBs.

[0255] Aspect 29: The method according to any one of Aspects 26 to 28, wherein the plurality of TDRBs includes one or more TDRBs in each of a plurality of subbands, and wherein the mapping scheme is a first frequency and a second time mapping scheme within each of the plurality of TDRBs, and a first subband and a second time mapping scheme between the respective TDRBs of the plurality of TDRBs.

[0256] Aspect 30: The method according to any one of Aspects 25 to 29, wherein the TDRB pattern comprises the first TDRB and one or more second TDRBs that follow the first TDRB in time.

[0257] Aspect 31: According to the method of aspect 30, the first TDRB includes one or more time boundaries based on the location of the DMRS symbol, wherein the one or more boundaries include at least one of a time start boundary or a time end boundary.

[0258] Aspect 32: According to the method of aspect 31, the end boundary is defined by the last OFDM symbol in time of the first TDRB being a DMRS symbol.

[0259] Aspect 33: The method according to any one of aspects 31 to 32, wherein the starting boundary is defined by the first OFDM symbol in time of the first TDRB being a DMRS symbol.

[0260] Aspect 34: The method according to any one of aspects 30 to 33, wherein the first second TDRB immediately following the first TDRB in time is defined by a DMRS symbol, the DMRS symbol being the last OFDM symbol in time of the first TDRB or the first OFDM symbol in time of the first second TDRB in time of the one or more second TDRBs.

[0261] Aspect 35: The method according to any one of aspects 30 to 34, wherein the first TDRB or at least one of the one or more second TDRBs is defined as including a DMRS symbol, the DMRS symbol being a channel estimation source for one or more OFDM symbols in adjacent TDRBs of the one or more second TDRBs.

[0262] Aspect 36: According to the method of aspect 35, the adjacent TDRB is one of the first or last second TDRB in time among the one or more second TDRBs.

[0263] Aspect 37: The method according to any one of aspects 30 to 36, wherein the last TDRB at one or more times of the one or more second TDRBs does not include DMRS.

[0264] Aspect 38: According to the method of aspect 37, each of the one or more time-term last TDRBs comprises only one OFDM symbol or fewer than a threshold number of OFDM symbols.

[0265] Aspect 39: The method according to any one of Aspects 30 to 38, wherein at least one of the first TDRB and the one or more second TDRBs includes an end boundary that is temporally aligned with the time slot boundary.

[0266] Aspect 40: The method according to any one of Aspects 25 to 39, wherein the second control information indicates the number of DMRS or DMRS timings per TDRB, the maximum duration of the TDRB, or a combination thereof.

[0267] Aspect 41: The method according to any one of aspects 25 to 40, wherein the second control information indicates the TDRB pattern.

[0268] Aspect 42: The method according to any one of Aspects 25 to 41, wherein the second control information instructs the second network entity to switch to or from the application of the TDRB pattern.

[0269] Aspect 43: The method according to any one of Aspects 25 to 42, wherein the second control information is transmitted via an RRC message, MAC-CE, DCI message or any combination thereof.

[0270] Aspect 44: The method according to any one of Aspects 25 to 43, the method further comprising: receiving a report including channel estimation time window duration information, wherein the second control information is based on the channel estimation time window duration information.

[0271] Aspect 45: The method according to any one of Aspects 25 to 44, wherein the second control information comprises a DMRS pattern based on channel estimation time window duration information or an updated TDRB pattern or both.

[0272] Aspect 46: A network entity for wireless communication, the network entity including a process configured to perform the method according to any one of aspects 1 to 24.

[0273] Aspect 47: A network entity for wireless communication, the network entity comprising at least one component for performing the method according to any one of aspects 1 to 24.

[0274] Aspect 48: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the method according to any one of aspects 1 to 24.

[0275] Aspect 49: A first network entity for wireless communication, the first network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the first network entity to perform a method according to any one of aspects 25 to 45.

[0276] Aspect 50: A first network entity for wireless communication, the first network entity comprising at least one component for performing the method according to any one of aspects 25 to 45.

[0277] Aspect 51: A non-transitory computer-readable medium having stored thereon code for wireless communication, the code causing the network entity to perform the method according to any one of aspects 25 to 45 when executed by the network entity.

[0278] The methods described herein outline possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

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

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

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

[0282] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including portions distributed such that the functions are implemented in different physical locations.

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

[0284] As used herein, the term "or" is inclusive unless restrictive language is used relative to the listed alternatives. For example, a reference to "X is based on A or B" should be interpreted as including, within its scope, X is based on A, X is based on B, and X is based on both A and B. In this respect, a reference to "X is based on A or B" means "at least one of A or B" or "one or more of A or B," because "or" is inclusive. Similarly, a reference to "X is based on A, B, or C" should be interpreted as including, within its scope, X is based on A, X is based on B, X is based on C, X is based on both A and B, X is based on both A and C, X is based on both B and C, and X is based on both A, B, and C. In this respect, a reference to "X is based on A, B, or C" means "at least one of A, B, or C" or "one or more of A, B, or C," because "or" is inclusive. As an example of restrictive language, the reference to "X is based on either A or B" should be interpreted as including, within its scope, both X based on A and X based on B, but excluding X based on both A and B. Furthermore, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, conditions, factors, etc.) should be interpreted as "based on at least A," unless specifically stated differently. Similarly, as used herein, the phrase "set" should be interpreted as including the possibility of a set having one member. That is, the phrase "set" should be interpreted in the same way as "one or more" or "at least one."

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

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

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

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

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

Claims

1. A network entity for wireless communication, the network entity comprising: Processing system, the processing system being configured to: Receive first control information, the first control information scheduling the reception of the first message during the time-frequency resource set of the network entity; Receive second control information associated with a time-domain resource block pattern, wherein the time-domain resource block pattern defines a first time-domain resource block during at least a portion of the time-frequency resource set, and wherein the first time-domain resource block includes an orthogonal frequency division multiplexing (OFDM) symbol set; as well as Data is demodulated based on the time-domain resource block pattern.

2. The network entity according to claim 1, wherein the processing system is configured to: Receive the data during the first time-domain resource block; and The data received during the first time-domain resource block is cached for subsequent processing.

3. The network entity according to claim 1, wherein, To demodulate the data, the processing system is configured to demodulate the data after the last OFDM symbol in the time domain of the first time domain resource block.

4. The network entity according to claim 1, wherein the processing system is configured to: A channel estimation process is performed after the last OFDM symbol in the first time domain resource block, wherein the channel estimation process is based on a portion of the data received during the first time domain resource block.

5. The network entity according to claim 1, wherein the time-domain resource block pattern definition includes a plurality of time-domain resource blocks of the first time-domain resource block, and wherein the codeword of the first message is resource-mapped to the first time-domain resource block according to a mapping scheme based on each time-domain resource block.

6. The network entity according to claim 5, wherein the mapping scheme is a time first and frequency second mapping scheme within each of the plurality of time-domain resource blocks.

7. The network entity according to claim 5, wherein the mapping scheme is a frequency first and time second mapping scheme within each of the plurality of time-domain resource blocks.

8. The network entity of claim 5, wherein the plurality of time-domain resource blocks include one or more time-domain resource blocks in each of the plurality of sub-bands, and wherein the mapping scheme is a frequency first and time second mapping scheme within each of the plurality of time-domain resource blocks, and a sub-band first and time second mapping scheme between the various time-domain resource blocks in the plurality of time-domain resource blocks.

9. The network entity of claim 1, wherein the time-domain resource block pattern comprises the first time-domain resource block and one or more second time-domain resource blocks that follow the first time-domain resource block in time.

10. The network entity of claim 9, wherein the first time-domain resource block includes one or more time boundaries based on the location of demodulation reference signal (DMRS) symbols, wherein the one or more boundaries include at least one of a time-domain start boundary or a time-domain end boundary.

11. The network entity of claim 10, wherein the termination boundary is defined by the fact that the last OFDM symbol in the time domain of the first time-domain resource block is a DMRS symbol.

12. The network entity of claim 10, wherein the starting boundary is defined by the first OFDM symbol in the time domain of the first time domain resource block being a DMRS symbol.

13. The network entity of claim 9, wherein the first time-domain resource block and the first second time-domain resource block immediately following the first time-domain resource block in the one or more second time-domain resource blocks are defined by a DMRS symbol, the DMRS symbol being the last OFDM symbol in time of the first time-domain resource block or the first OFDM symbol in time of the first second time-domain resource block in the one or more second time-domain resource blocks.

14. The network entity of claim 9, wherein the first time-domain resource block or at least one of the one or more second time-domain resource blocks is defined as including DMRS symbols, the DMRS symbols being channel estimation sources for one or more OFDM symbols in adjacent time-domain resource blocks of the one or more second time-domain resource blocks.

15. The network entity of claim 14, wherein the adjacent time-domain resource block is one of the first or last time-domain resource block in time among the one or more second time-domain resource blocks.

16. The network entity of claim 9, wherein the last time-domain resource block in one or more of the one or more second time-domain resource blocks does not include a demodulation reference signal (DMRS).

17. The network entity of claim 16, wherein each of the one or more time-domain resource blocks comprises only one OFDM symbol or fewer than a threshold number of OFDM symbols.

18. The network entity of claim 9, wherein at least one of the first time-domain resource block and the one or more second time-domain resource blocks includes an end boundary that is temporally aligned with the time slot boundary.

19. The network entity of claim 1, wherein the processing system is configured to: The report channel estimation time window duration information is provided, wherein the second control information is based on the channel estimation time window duration information.

20. A first network entity for wireless communication, the first network entity comprising: Processing system, the processing system being configured to: Sending first control information, the first control information being scheduled for reception of the first message by the second network entity during a time-frequency resource set; and Send second control information associated with a time-domain resource block pattern, wherein the time-domain resource block pattern defines a first time-domain resource block during at least a portion of the time-frequency resource set, and wherein the first time-domain resource block includes an orthogonal frequency division multiplexing (OFDM) symbol set.

21. The first network entity of claim 20, wherein the second control information indicates the number of demodulation reference signals (DMRS) or DMRS timings per time-domain resource block, the maximum duration of the time-domain resource block, or a combination thereof.

22. The first network entity of claim 20, wherein the second control information indicates the time-domain resource block pattern.

23. The first network entity of claim 20, wherein the second control information instructs the second network entity to switch to or from the application of the time-domain resource block pattern.

24. The first network entity of claim 20, wherein the second control information is transmitted via a Radio Resource Control (RRC) message, a Media Access Control Element (MAC-CE), a Downlink Control Information (DCI) message, or any combination thereof.

25. The first network entity of claim 20, wherein the second control information comprises a demodulation reference signal (DMRS) pattern based on channel estimation time window duration information or an updated time-domain resource block pattern or both.

26. A method for wireless communication by a network entity, the method comprising: Receive first control information, the first control information scheduling the reception of the first message during the time-frequency resource set of the network entity; Receive second control information associated with a time-domain resource block pattern, wherein the time-domain resource block pattern defines a first time-domain resource block during at least a portion of the time-frequency resource set, and wherein the first time-domain resource block includes an orthogonal frequency division multiplexing (OFDM) symbol set; as well as Data is demodulated based on the time-domain resource block pattern.

27. The method according to claim 26, further comprising: The data is received during the first time-domain resource block; as well as The data received during the first time-domain resource block is cached for subsequent processing.

28. The method according to claim 26, wherein, To demodulate the data, the network entity is configured to demodulate the data after the last OFDM symbol in the time domain of the first time domain resource block.

29. A method for wireless communication by a first network entity, the method comprising: Send first control information, the first control information being scheduled for the reception of the first message during the time-frequency resource set of the second network entity; as well as Send second control information associated with a time-domain resource block pattern, wherein the time-domain resource block pattern defines a first time-domain resource block during at least a portion of the time-frequency resource set, and wherein the first time-domain resource block includes an orthogonal frequency division multiplexing (OFDM) symbol set.

30. The method of claim 29, wherein the time-domain resource block pattern definition includes a plurality of time-domain resource blocks of the first time-domain resource block, and wherein the codeword of the first message is resource-mapped to the first time-domain resource block according to a mapping scheme based on each time-domain resource block.

Images