Joint shared channel timing allocation in downlink control information

Abstract

Methods, systems, and apparatuses for wireless communication are described, supporting joint allocation for both uplink and downlink messages. In some cases, joint downlink control information (DCI) can indicate time-domain resource allocation (TDRA) for downlink and uplink data channels. For example, bits of the joint DCI can be configured to indicate TDRA parameters for the downlink data channel (e.g., start symbol, length value, slot offset, mapping type, timing advance, repetition count), and based on the TDRA parameters of the downlink data channel, the user equipment (UE) can use the joint DCI to determine the TDRA parameters for the uplink data channel.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. Patent Application No. 17 / 233,255, filed April 16, 2021, entitled “JOINT SHARED CHANNEL TIMING ALLOCATION IN DOWNLINK CONTROL INFORMATION”, and to U.S. Provisional Patent Application No. 63 / 023,818, filed May 12, 2020, entitled “JOINT SHARED CHANNEL TIMING ALLOCATION IN DOWNLINK CONTROLINFORMATION”, all of which are assigned to the assignee of this application and are expressly incorporated herein by reference. Technical Field

[0003] In summary, the following text relates to wireless communications, and more specifically, to the joint shared channel allocation in downlink control information (DCI). Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, and broadcasting. 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 (e.g., Long Term Evolution (LTE) systems, improved LTE (LTE-A) systems, or LTE-A specialist systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems can 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 or one or more network access nodes, each base station or network access node simultaneously supporting communication with multiple communication devices (which may also be referred to as User Equipment (UE)).

[0005] Some wireless communication systems can support communication between a base station and a UE operating on a portion of the radio frequency spectrum band (which may be referred to as the bandwidth portion (BWP)). The base station can use downlink control information (DCI) on the BWP to schedule one or more resources for the UE. The DCI can schedule resources via a downlink channel (e.g., the physical downlink control channel (PDCCH)). However, the DCI can be used to schedule uplink and downlink messages in separate PDCCH messages, which can lead to increased signaling overhead and decoding complexity at the UE when both uplink and downlink messages are scheduled for use. Summary of the Invention

[0006] This disclosure relates to methods, systems, apparatuses, and devices that support the allocation of joint downlink control information (DCI) for both uplink and downlink messages in unpaired radio frequency spectrum bands. In some cases, the carrier bandwidth can be divided into multiple bandwidth portions (BWPs), and communication between a user equipment (UE) and a base station can use one or more sub-bands within a BWP. In some cases, the UE can implement a sub-band full-duplex (SBFD) configuration. SBFD configuration can allow one or more BWPs to be used for associated downlink or uplink transmissions and can provide the ability to receive downlink information and transmit uplink information within overlapping time resources within the carrier bandwidth.

[0007] Various aspects of this disclosure provide a UE with SBFD capability that determines time-frequency resources based on a joint DCI message. In some aspects, the DCI may indicate a Time Domain Resource Allocation (TDRA) for downlink data channels (e.g., Physical Downlink Shared Channel (PDSCH)). Additionally, the DCI may indicate a TDRA for uplink data channels (e.g., Physical Uplink Shared Channel (PUSCH)). Some bits of the DCI may be configured to indicate TDRA channel characteristics for each data channel (e.g., start symbol, length value, slot offset, mapping type, timing advance, number of repetitions). In some examples, some bits of the DCI may indicate scheduling information that allocates a first resource for downlink messages and a second resource for uplink messages, the second resource at least partially overlapping the first resource in time, frequency, or both. In some cases, the allocation of downlink and uplink resources in some bits of the DCI can be transmitted via a control message (e.g., a joint control message), which can result in less signaling overhead and decoding complexity at the UE compared to scheduling downlink and uplink allocation messages in separate control messages.

[0008] A method for wireless communication at a UE is described. The method may include: receiving a control message from a base station, the control message including scheduling information for downlink messages to be received by the UE and uplink messages to be transmitted by the UE, the scheduling information allocating a first resource for the downlink messages and a second resource for the uplink messages; using the first resource to receive the downlink messages according to timing information for the downlink messages determined based on the scheduling information; and using the second resource to transmit the uplink messages according to the timing information for the downlink messages and the timing information for the uplink messages determined based on the scheduling information.

[0009] An apparatus for wireless communication at a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: receive a control message from a base station, the control message including scheduling information for downlink messages to be received by the UE and uplink messages to be transmitted by the UE, the scheduling information allocating a first resource for the downlink messages and a second resource for the uplink messages; receive the downlink messages using the first resource according to timing information for the downlink messages determined based on the scheduling information; and transmit the uplink messages using the second resource according to the timing information for the downlink messages and the timing information for the uplink messages determined based on the scheduling information.

[0010] Another apparatus for wireless communication at a UE is described. The apparatus may include: a unit for receiving a control message from a base station, the control message including scheduling information for downlink messages to be received by the UE and uplink messages to be transmitted by the UE, the scheduling information allocating a first resource for the downlink messages and a second resource for the uplink messages; a unit for receiving the downlink messages using the first resource based on timing information for the downlink messages determined based on the scheduling information; and a unit for transmitting the uplink messages using the second resource based on the timing information for the downlink messages and the timing information for the uplink messages determined based on the scheduling information.

[0011] A non-transitory computer-readable medium is described, storing code for wireless communication at a UE. The code may include instructions executable by a processor to: receive a control message from a base station, the control message including scheduling information for downlink messages to be received by the UE and uplink messages to be transmitted by the UE, the scheduling information allocating a first resource for the downlink messages and a second resource for the uplink messages; using the first resource to receive the downlink messages according to timing information for the downlink messages determined based on the scheduling information; and using the second resource to transmit the uplink messages according to the timing information for the downlink messages and the timing information for the uplink messages determined based on the scheduling information.

[0012] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for determining, based on the TDRA field of the control message, the start symbol, length value, slot offset, mapping type, or any combination thereof for the downlink message.

[0013] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: receiving from the base station a message indicating an incremental symbol value associated with the timing information for the uplink message, wherein the message may be received via Radio Resource Control (RRC) signaling, Media Access Control (MAC) control element (MAC-CE), or DCI.

[0014] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for determining a start symbol for the uplink message based on the start symbol of the downlink message and the increment symbol value.

[0015] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for determining a start symbol for the uplink message based on the incremental symbol value and a symbol in which the control message can be received during the monitoring period.

[0016] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the message includes a set of incremental symbol values, and the methods, apparatuses, and non-transitory computer-readable media may also include operations, features, units, or instructions for selecting incremental symbol values ​​from the set of incremental symbol values ​​based on the scheduling information.

[0017] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: receiving from the base station a message indicating an incremental timeslot value associated with the timing information for the uplink message, wherein the message may be received via RRC signaling, MAC-CE, or DCI.

[0018] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for determining a time slot for transmitting the uplink message based on a start symbol for the downlink message, the incremental time slot value, and a ratio, which may be based on a first subcarrier interval for the uplink message and a second subcarrier interval for the downlink message.

[0019] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for determining a time slot for the transmission of the uplink message based on a time slot scheduled for the downlink message and the incremental time slot value.

[0020] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: determining a set of time resources for transmitting the uplink message based on the timing information for the downlink message; applying a timing advance for the UE to transmit the uplink message based on the time resource set; and transmitting the uplink message according to the time resource set and the applied timing advance.

[0021] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: determining a set of time resources for the transmission of the uplink message based on timing information for the downlink message or timing information for the uplink message, the set of time resources being aligned with a set of downlink symbols; and transmitting the uplink message via the set of time resources.

[0022] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for determining the symbol length for transmission of the uplink message based on the start symbol of the uplink message.

[0023] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: receiving from the base station a message including a length indicator for the transmission of the uplink message, wherein the message may be received via RRC signaling, MAC-CE, or DCI; determining a symbol length for the uplink message based on the length indicator; and transmitting the uplink message according to the determined symbol length.

[0024] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, determining the symbol length for the uplink message may include operations, features, units, or instructions for selecting the symbol length from the set of symbol lengths based on the scheduling information.

[0025] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for determining a reference signal mapping type for the uplink message based on a portion of the scheduling information of the control message.

[0026] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: determining the reference signal mapping type based on the start symbol and symbol length of the uplink message, which may be a type A mapping.

[0027] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: determining a duplication index based on the scheduling information; and determining the number of duplications for the uplink message based on the duplication index.

[0028] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: determining the number of repetitions for the downlink message based on the scheduling information; and determining the number of repetitions for the uplink message based on the number of repetitions of the downlink message.

[0029] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for determining the number of repetitions for the uplink message based on the number of repetitions and increment values ​​for the downlink message.

[0030] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for receiving a message including the duplicate index from the base station, wherein the message may be received via RRC signaling.

[0031] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for transmitting the uplink messages and the downlink messages with the base station via the same carrier based on the scheduling information.

[0032] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for receiving the control message via a carrier different from the same carrier used for the uplink message and the downlink message.

[0033] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for performing the following: determining a first modulation and coding scheme (MCS) for the downlink message based on the control message; and determining a second MCS for the uplink message based on the first MCS for the downlink message.

[0034] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first resource at least partially overlaps with the second resource in at least one of time or frequency. Attached Figure Description

[0035] Figure 1 An example of a wireless communication system supporting joint shared channel allocation in downlink control information (DCI) according to various aspects of this disclosure is shown.

[0036] Figure 2 An example of a wireless communication system supporting joint shared channel allocation in DCI is shown, according to various aspects of this disclosure.

[0037] Figure 3 An example of a time-frequency diagram supporting joint shared channel allocation in DCI according to various aspects of this disclosure is shown.

[0038] Figure 4 An example of a time-frequency diagram supporting joint shared channel allocation in DCI according to various aspects of this disclosure is shown.

[0039] Figure 5A and 5BAn example of a time-frequency diagram supporting joint shared channel allocation in DCI according to various aspects of this disclosure is shown.

[0040] Figure 6 An example of the process flow supporting joint shared channel allocation in DCI according to various aspects of this disclosure is shown.

[0041] Figure 7 and 8 A block diagram of an apparatus supporting joint shared channel allocation in DCI is shown, according to various aspects of this disclosure.

[0042] Figure 9 A block diagram of a communication manager supporting joint shared channel allocation in DCI is shown, according to various aspects of this disclosure.

[0043] Figure 10 A diagram of a system including devices supporting joint shared channel allocation in DCI is shown, according to various aspects of this disclosure.

[0044] Figures 11 to 18 A flowchart illustrating a method for supporting joint shared channel allocation in DCI according to various aspects of this disclosure is shown. Detailed Implementation

[0045] In some wireless communication systems, user equipment (UE) and base stations can communicate using unpaired radio frequency spectrum bands (which can be divided into one or more bandwidth portions (BWPs)). Each BWP may include one or more sub-bands (e.g., sub-channels or other forms of frequency resource sets). In some cases, the base station can transmit downlink control information (DCI) on the BWP to schedule one or more resources for the UE. In some aspects, the DCI can schedule resources via a downlink control channel (e.g., a physical downlink control channel (PDCCH)). The UE can use the DCI to dynamically allocate resources via separate PDCCH messages. For example, a PDCCH message configured for downlink allocation can send an indication of downlink resources to the UE, and a PDCCH message configured for uplink allocation can send only an indication of uplink resources to the UE. However, when both uplink and downlink messages are scheduled for the UE, using separate PDCCH messages on the BWP to allocate resources can result in increased signaling overhead and decoding complexity at the UE.

[0046] This document describes techniques for joint DCI allocation of both uplink and downlink messages in unpaired radio frequency spectrum bands. In some examples, the UE may receive a DCI indicating at least one uplink BWP, or a downlink BWP, or both. In some cases, the base station may transmit to a UE implementing a Subband Full-Duplex (SBFD) configuration, which allows the UE to transmit downlink and uplink information on one or more subbands of a BWP. Additionally, the UE's SBFD capability may allow the UE to receive downlink messages and transmit uplink messages in overlapping time resources between and within BWPs (e.g., such that downlink and uplink messages partially or completely overlap in time). In some cases, a UE with SBFD capability can determine time-frequency resources based on the joint DCI message. The joint DCI message may indicate a time-domain resource allocation (TDRA) for downlink data channels (e.g., Physical Downlink Shared Channel (PDSCH)). Using TDRA for downlink channels, the UE can determine resource allocation for uplink data channels (e.g., Physical Uplink Shared Channel (PUSCH)). Some bits in the DCI can indicate scheduling information for a first resource allocated for downlink messages and a second resource for uplink messages. The second resource may overlap at least partially with the first resource in terms of time, frequency, or both. In some cases, the allocation of downlink and uplink resources in some bits of the DCI can be sent via a joint control message, which can result in less signaling overhead and decoding complexity at the UE compared to scheduling downlink and uplink allocations separately.

[0047] In some aspects, the DCI can indicate the TDRA channel characteristics for each data channel used for a message. For example, the DCI can allocate TDRA for a PDSCH by configuring a first number of most significant bits (MSB) or least significant bits (LSB) in the TDRA bit field of the DCI. The MSB of the TDRA field can indicate multiple characteristics of the PDSCH (e.g., start symbol, transmission allocation length, transmission slot, mapping type). Additionally, the DCI can indicate multiple characteristics of the PUSCH (e.g., start symbol, transmission allocation length, transmission slot, mapping type, transmission repetition count). In some cases, TDRA channel characteristics can be configured via higher-layer signaling or dynamically indicated from a configured set. For example, a base station can send a control message indicating an incremental symbol value associated with timing information used for uplink messages. The incremental symbol value can be used to determine the start symbol of the uplink message. In some examples, a base station can send a control message indicating an incremental slot value associated with timing information used for uplink messages. The incremental slot value helps determine the slots used for transmission of uplink messages. In some examples, the base station may send a length indicator that determines the symbol length used for uplink messages.

[0048] In some cases, TDRA allocation can also enable timing advance. In some examples, the TDRA channel characteristics of the PDSCH can help determine the TDRA channel characteristics of the PUSCH. For example, the start symbol value of the downlink message can be used to obtain the start symbol of the uplink message.

[0049] First, various aspects of this disclosure are described in the context of a wireless communication system. Then, aspects are described with respect to time-frequency diagrams and process flows. Further, various aspects of this disclosure are illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to the joint shared channel allocation in DCI.

[0050] Figure 1 Examples of a wireless communication system 100 supporting joint shared channel allocation in DCI according to various aspects of this disclosure are shown. The wireless communication system 100 may include one or more base stations 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 improved LTE (LTE-A) network, an LTE-A specialist network, or a New Radio (NR) network. In some examples, the wireless communication system 100 may support enhanced broadband communication, ultra-reliable (e.g., mission-critical) communication, low-latency communication, communication with low-cost and low-complexity devices, or any combination thereof.

[0051] Base stations 105 can be distributed throughout a geographical area to form a wireless communication system 100, and can be devices of different forms or with different capabilities. Base stations 105 and UE 115 can communicate wirelessly via one or more communication links 125. Each base station 105 can provide a coverage area 110, and UE 115 and base station 105 can establish one or more communication links 125 on the coverage area 110. Coverage area 110 can be an example of a geographical area where base station 105 and UE 115 can support signal transmission according to one or more radio access technologies.

[0052] UE 115 can be distributed throughout the entire coverage area 110 of the wireless communication system 100, and each UE 115 can be stationary, mobile, or both at different times. UE 115 can be devices of different forms or with different capabilities. Figure 1 Some example UE 115s are shown in the document. The UE 115 described herein is capable of communicating with various types of devices, such as other UE 115s, base station 105, or network devices (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network devices), such as... Figure 1 As shown.

[0053] Base station 105 can communicate with core network 130, communicate with each other, or perform both operations. For example, base station 105 can interface with core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3, or other interfaces). Base station 105 can communicate with each other directly (e.g., directly between base stations 105) on backhaul links 120 (e.g., via X2, Xn, or other interfaces), or indirectly (e.g., via core network 130), or perform both operations. In some examples, backhaul link 120 can be or includes one or more radio links.

[0054] One or more of the base stations 105 described herein may include, or may be referred to by those skilled in the art as, a base station transceiver, a radio base station, an access point, a radio transceiver, a node B, an evolved node B (eNB), a next-generation node B or a gigabit node B (any of which may be referred to as a gNB), a home node B, a home evolved node B, or some other suitable term.

[0055] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or some other suitable term, wherein "device" may also be referred to as a unit, station, terminal, or client, and other examples. 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, and other examples, which may be implemented in various items such as electrical appliances, vehicles, meters, and other examples.

[0056] The UE 115 described in this document can communicate with various types of devices, such as other UE 115s that can sometimes act as repeaters, as well as base station 105 and network devices, including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, and other examples, such as... Figure 1 As shown in the image.

[0057] UE 115 and base station 105 can communicate wirelessly with each other via one or more communication links 125 on one or more carriers. The term "carrier" can refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of a radio frequency spectrum band (e.g., BWP) that operates according to one or more physical layer channels of 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 the operation of the carrier, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers.

[0058] In some examples (e.g., in a carrier aggregation configuration), the carrier may also have acquisition or control signaling that coordinates the operation of other carriers. The carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be positioned according to a channel grid for discovery by UE 115. The carrier may operate in standalone mode, where UE 115 performs initial acquisition and connection via the carrier, or the carrier may operate in non-standalone mode, where different carriers (e.g., the same or different radio access technologies) are used to anchor the connection.

[0059] The communication link 125 shown in the wireless communication system 100 may include uplink transmission from UE 115 to base station 105, or downlink transmission from base station 105 to UE 115. The carrier may carry downlink or uplink communication (e.g., in FDD mode) or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0060] A carrier may be associated with a specific bandwidth of the radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one of a plurality of defined bandwidths for a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz). Devices of the wireless communication system 100 (e.g., base station 105, UE 115, or both) may have a hardware configuration that supports communication on a specific carrier bandwidth, or may be configurable to support communication on one carrier bandwidth in a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 or UE 115 that supports simultaneous communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, BWP) or all of the carrier bandwidth.

[0061] The signal waveform transmitted on a carrier can consist of multiple subcarriers (e.g., using multicarrier modulation (MCM) techniques such as Orthogonal Frequency Division Multiplexing (OFDM) or Discrete Fourier Transform Spread Spectrum OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element can include a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element can depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Therefore, the more resource elements UE 115 receives and the higher the order of the modulation scheme, the higher the data rate can be for UE 115. Wireless communication resources can refer to a combination of radio frequency spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers can further increase the data rate or data integrity used for communication with UE 115.

[0062] One or more digital schemes can be supported for the carrier, where the digital scheme may include subcarrier spacing (Δf) and a cyclic prefix. The carrier can be divided into one or more BWPs with the same or different digital schemes. In some examples, UE 115 can be configured with multiple BWPs. In some examples, a single BWP for the carrier is active at a given time, and communication for UE 115 can be restricted to one or more active BWPs.

[0063] It can be expressed in a basic unit of time (which can be, for example, T). s =1 / (Δf) max ·N f The sampling period is ) seconds, where Δf max This can represent the maximum supported subcarrier spacing, and N f The time interval for base station 105 or UE 115 can be represented as a multiple of the maximum supported Discrete Fourier Transform (DFT) size. The time interval for communication resources can be organized based on radio frames, each having 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).

[0064] 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 be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into multiple 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 multiple symbol periods (e.g., this depends on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N) f (Number) sampling periods. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0065] 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. Alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0066] Physical channels can be multiplexed on a carrier using various techniques. 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 on a downlink carrier. A control region (e.g., a control resource set (CORESET)) for physical control channels can be defined by multiple symbol periods and can extend over the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) can be configured for a set of UEs 115. For example, one or more UEs 115 can monitor or search for control regions for 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 cascaded manner. The aggregation level for control channel candidates can refer to the number 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 send control information to multiple UEs 115 and a UE-specific search space set used to send control information to a specific UE 115.

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

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

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

[0070] In some examples, base station 105 may be mobile, and therefore provide communication coverage for mobile geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, but different geographic coverage areas 110 may be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105. Wireless communication system 100 may include, for example, a heterogeneous network, in which different types of base stations 105 use the same or different radio access technologies to provide coverage for various geographic coverage areas 110.

[0071] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, base stations 105 can have similar frame timings, and transmissions from different base stations 105 can be approximately time-aligned. For asynchronous operation, base stations 105 can have different frame timings, and in some examples, transmissions from different base stations 105 may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

[0072] Some UE 115s (e.g., MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated machine-to-machine communication (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with base station 105 without human intervention. In some examples, M2M communication or MTC can include communication from devices that have integrated sensors or meters to measure or capture information and relay such information to a central server or application that uses the information or presents it to humans interacting with the application. Some UE 115s can be designed to collect information or automate the behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, climate and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based billing.

[0073] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via either transmission or reception, rather than simultaneous transmission and reception). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power-saving techniques for UE 115 include entering a power-saving deep sleep mode when not engaged in active communication, when operating on limited bandwidth (e.g., according to narrowband communication), or when a combination of these techniques is used. 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.

[0074] Wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC) or mission-critical communication. UE 115 can be designed to support ultra-reliable, low-latency, or mission-critical functions (e.g., mission-critical functions). Ultra-reliable communication can include private or group communication and can be supported by one or more mission-critical services (such as mission-critical push-to-talk (MCPTT), mission-critical video (MCVideo), or mission-critical data (MCData)). Support for mission-critical functions can include service prioritization, and mission-critical services can be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, mission-critical, and ultra-reliable low-latency are used interchangeably herein.

[0075] In some examples, UE 115 can also communicate directly with other UE 115s on a device-to-device (D2D) communication link 135 (e.g., using peer-to-peer (P2P) or D2D protocols). One or more UEs 115s utilizing D2D communication can be within the geographic coverage area 110 of base station 105. Other UEs 115s in such a group can be outside the geographic coverage area 110 of base station 105, or otherwise unable to receive transmissions from base station 105. In some examples, multiple groups of UEs 115 communicating via D2D communication can utilize a one-to-many (1:M) system, where each UE 115 transmits to every other UE 115 in the group. In some examples, base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between UEs 115 without involving base station 105.

[0076] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, the vehicle may communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these. The vehicle may signal information relating to traffic conditions, signal control, weather, safety, emergencies, or any other information relating to the V2X system. In some examples, a vehicle in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., base station 105) using vehicle-to-network (V2N) communication, or both.

[0077] Core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), and can include at least one control plane entity (e.g., a mobility management entity (MME), access and mobility management function unit (AMF)) 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 unit (UPF)) routing or interconnecting packets to external networks. The control plane entity can manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management for UE 115 served by base station 105 associated with core network 130. User IP packets can be transmitted through the user plane entity, which can provide IP address allocation and other functions. The user plane entity can connect to network operator IP service 150. Operator IP service 150 can include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0078] Some network devices (e.g., base station 105) may include sub-components such as access network entity 140, which may be an example of an access node controller (ANC). Each access network entity 140 may communicate with UE 115 through one or more other access network transport entities 145 (which may be referred to as a radio headend, smart radio headend, or transmit / receive point (TRP)). Each access network transport entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 may be distributed across individual network devices (e.g., radio headends and ANCs) or incorporated into a single network device (e.g., base station 105).

[0079] Wireless communication system 100 can operate using one or more frequency bands (typically in the range of 300 MHz to 300 GHz). The region from 300 MHz to 3 GHz is often referred to as the Ultra High Frequency (UHF) region or decimeter band because the wavelength range extends from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, but the waves can be sufficiently permeable to penetrate structures for use in macrocells to provide service to UE 115 located indoors. Compared to the transmission of smaller frequencies and longer waves in the lower 300 MHz portion of the spectrum in the High Frequency (HF) or Very High Frequency (VHF) regions, UHF wave transmission can be associated with smaller antennas and shorter distances (e.g., less than 100 km).

[0080] The wireless communication system 100 can also operate in the ultra-high frequency (SHF) region using a frequency band from 3 GHz to 30 GHz (also referred to as the centimeter band) or in the extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also referred to as the millimeter band). In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and the base station 105, and the EHF antennas of the corresponding device can be even smaller and more closely spaced compared to UHF antennas. In some examples, this can facilitate the use of antenna arrays within the device. However, EHF transmissions may suffer from even greater atmospheric attenuation and shorter distances compared to SHF or UHF transmissions. The techniques disclosed herein can be employed across transmissions using one or more different frequency regions, and the designated use of frequency bands across these frequency regions may vary depending on the country or regulatory authority.

[0081] Wireless communication system 100 can utilize both licensed and unlicensed radio frequency spectrum bands. For example, wireless communication system 100 can employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology in unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating in unlicensed radio frequency spectrum bands, devices (such as base station 105 and UE 115) can employ carrier sensing for collision detection and avoidance. In some examples, operation in unlicensed frequency bands can be based on carrier aggregation configurations that combine component carriers operating in licensed frequency bands (e.g., LAA). Operation in unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, and other examples.

[0082] Base station 105 or UE 115 may be equipped with multiple antennas, which can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of base station 105 or UE 115 may be located within one or more antenna arrays or antenna panels (which may 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 base station 105 may be located in different geographical locations. Base station 105 may have antenna arrays with multiple rows and columns of antenna ports that base station 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Alternatively or additionally, antenna panels may support radio frequency beamforming for signals transmitted via antenna ports.

[0083] Base station 105 or UE 115 can use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such a technique can be called spatial multiplexing. For example, a transmitting device can transmit multiple signals via different antennas or different combinations of antennas. Similarly, a receiving device can receive multiple signals 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 bits 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).

[0084] Beamforming (which may also be referred to 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., base station 105, UE 115) to form or guide an antenna beam (e.g., transmit beam, 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 relative to a specific orientation of the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements can include applying amplitude offset, phase offset, or both to the signals carried via the antenna elements associated with the transmitting or receiving device. The adjustments associated with each antenna element can be defined by a set of beamforming weights associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device, or relative to some other orientation).

[0085] As part of beamforming operations, base station 105 or UE 115 may use beam scanning techniques. For example, base station 105 may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Base station 105 may transmit some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) multiple times in different directions. For example, base station 105 may transmit signals according to different sets of beamforming weights associated with different transmission directions. Transmissions in different beam directions may be used (e.g., by a transmitting device (such as base station 105) or by a receiving device (such as UE 115)) to identify the beam direction for subsequent transmissions or receptions performed by base station 105.

[0086] Base station 105 may transmit signals (e.g., data signals associated with a specific receiving device, such as UE 115) in a single beam direction (e.g., a direction associated with a particular receiving device, such as UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on signals transmitted in one or more beam directions. For example, UE 115 may receive one or more signals transmitted by base station 105 in different directions and may report to base station 105 an indication of the signal received by UE 115 that has the highest signal quality or otherwise acceptable signal quality.

[0087] In some examples, multiple beam directions can be used to perform transmissions by a device (e.g., base station 105 or UE 115), and the device can use a combination of digital precoding or radio frequency beamforming to generate combined beams for (e.g., from base station 105 to UE 115) transmissions. UE 115 can report feedback indicating precoding weights for one or more beam directions, and this feedback can correspond to a configured number of beams spanning the system bandwidth or one or more subbands. Base station 105 can transmit reference signals that can be precoded or unprecoded (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)). UE 115 can provide feedback on beam selection, which can be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel type codebook, linear combination type codebook, port selection type codebook). Although these techniques are described with reference to signals transmitted by base station 105 in one or more directions, UE 115 may employ similar techniques to transmit signals multiple times in different directions (e.g., to identify beam directions for subsequent transmissions or receptions by UE 115) or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

[0088] When receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from base station 105, the receiving device (e.g., UE 115) can attempt multiple receiving configurations (e.g., directional listening). For example, the receiving device can attempt multiple receiving directions by receiving via different antenna subarrays, by processing the received signals according to different antenna subarrays, by receiving according to different sets of receiving beamforming weights applied to signals received at multiple antenna elements of the antenna array (e.g., different sets of directional listening weights), or by processing the received signals according to different sets of receiving beamforming weights applied to signals received at multiple antenna elements of the antenna array (any of these operations can be referred to as "listening" according to different receiving configurations or receiving directions). In some examples, the receiving device can use a single receiving configuration to receive along a single beam direction (e.g., when receiving data signals). A single receiver configuration can be aligned on a beam direction determined based on listening to different receiver configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening to multiple beam directions).

[0089] 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 Packet Data Convergence Protocol (PDCP) layer can be IP-based. The Radio Link Control (RLC) layer can perform packet segmentation and reassembly for transmission over logical channels. The Media Access Control (MAC) layer can perform priority handling and multiplexing of logical channels to transport channels. The MAC layer can also use error detection techniques, error correction techniques, or both to support retransmissions at the MAC layer to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer can provide the establishment, configuration, and maintenance of RRC connections (which support radio bearers for user plane data) between the UE 115 and the base station 105 or core network 130. At the physical layer, transport channels can be mapped to physical channels.

[0090] UE 115 and base station 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 correct data reception on communication link 125. HARQ can 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 and noise conditions). In some examples, the device can support same-slot HARQ feedback, where the device can provide HARQ feedback for data received in a previous symbol within a specific time slot. In other cases, the device can provide HARQ feedback in subsequent time slots or according to some other time interval.

[0091] Base station 105 may send a joint DCI to UE 115, which indicates resource allocation information for uplink messages to be transmitted by UE 115 and downlink messages to be received by UE 115. In some cases, the joint DCI may include time or frequency allocation information (such as a TDRA field or a frequency domain resource allocation (FDRA) field) indicating time-frequency resources allocated for downlink and uplink messages of UE 115. For example, base station 105 may send a joint DCI including a TDRA field, which indicates timing information (e.g., start symbol, transmission length) for downlink messages to be received by UE 115. Based on the timing information for downlink messages, UE 115 may determine timing information (e.g., start symbol, transmission length, timeslot index) for uplink messages.

[0092] Figure 2Examples of a wireless communication system 200 supporting joint shared channel allocation in DCI according to various aspects of this disclosure are shown. In some examples, wireless communication system 200 may implement various aspects of wireless communication system 100. For example, wireless communication system 200 may include UE 115-a and base station 105-a, which may be as described in reference Figure 1 Examples of UE115 and base station 105 are described.

[0093] In some examples, UE 115-a may use time-frequency resources (such as bandwidth 225) to communicate with base station 105-a. Bandwidth 225 may be used to transmit or receive data on resources in one or more areas (e.g., as indicated by uplink data area 205, uplink control area 210, downlink data area 215, downlink control area 220, or any combination thereof). In some cases, bandwidth 225 may be an example of a single frequency band or carrier allocated for both uplink and downlink communication (e.g., a single frequency band may be allocated for both uplink and downlink communication using TDD or FDD modes). For example, according to TDD mode, the bandwidth 225 (e.g., frequency band) used for uplink communication may be the same as the frequency band used for downlink communication.

[0094] In some cases, multiple different BWPs can span bandwidth 225 to allow concurrent (e.g., at least partially overlapping in time) uplink and downlink communication for UE 115-a. In some examples, bandwidth 225 may be an example of a single carrier in an unpaired spectrum. In some cases, bandwidth 225 may be divided into one or more BWPs (e.g., BWPs 230-a, 230-b, and 230-c), and base station 105-a may designate BWPs for, for example, receiving downlink communication according to FDD mode (e.g., PDSCH transmission via downlink data area 215) or sending uplink communication to UE 115-a (e.g., PUSCH transmission via uplink data area 205). Frequency guard bands may be located between BWPs 230 to minimize signaling interference. In some cases, base station 105-a may divide bandwidth 225 into BWPs 230 of different sizes. For example, base station 105-a may divide bandwidth 225 (e.g., 80MHz bandwidth) into a first BWP 230-a with a first size (e.g., 40MHz), a second BWP 230-b with a second size (e.g., 20MHz), and a third BWP 230-c with a third size (e.g., 20MHz). Each BWP 230 may be further divided into one or more subbands, which may allow concurrent (or at least partially overlapping in time) uplink and downlink communication for UE 115-a. For example, base station 105-a may designate subbands of BWP 230 for, for example, receiving downlink communication (e.g., via PDSCH transmission in downlink data area 215) according to FDD mode or for sending uplink communication to UE 115-a (e.g., via PUSCH transmission in uplink data area 205).

[0095] In some cases, UE 115-a and base station 105-a may communicate on one or more BWP 230s according to one or more operating modes (e.g., FDD operating mode, TDD operating mode, or both). For example, base station 105-a may send control signaling to UE 115-a on bandwidth 225 in unpaired radio frequency spectrum. In some examples, the control signaling may instruct UE 115-a (e.g., configure UE 115-a) one or more BWP 230s associated with one or more operating modes from bandwidth 225. For example, the control signaling may instruct one or more downlink BWP 230s for operation in TDD mode, one or more uplink BWP 230s for operation in TDD mode, or both. Alternatively, a single BWP 230 can provide operation in FDD mode, since each BWP 230 can receive instructions for receiving downlink communication (e.g., PDSCH transmission via downlink data area 215) or for sending uplink communication to UE 115-a (e.g., PUSCH transmission via uplink data area 205). For example, during time periods 235-a and 235-d, UE 115-a can receive messages (e.g., downlink or uplink) on any combination of BWPs 230-a, 230-b, or 230-c. During time periods 235-b and 235-c, UE 115-a can receive and send messages on a separate BWP 230 (e.g., UE 115-a can receive PDSCH transmissions via downlink data area 215 on BWP 230-a and 230-c, and UE 115-a can send PUSCH transmissions via uplink data area 205 on BWP 230-b). Such a communication configuration can be referred to as SBFD configuration.

[0096] In some examples, UE 115-a may receive a DCI (e.g., via downlink control area 220) from base station 105, which indicates a BWP for receiving downlink communication (e.g., PDSCH transmission via downlink data area 215) or for transmitting uplink communication (e.g., PUSCH transmission via uplink data area 205). For example, base station 105-a may send a DCI to UE 115-a for each physical channel via downlink control area 220. For example, base station 105-a may schedule FDRA (e.g., PDSCH resources) for a first physical channel via a first DCI on a first BWP 230 (e.g., BWP 230-a) and schedule FDRA (e.g., PUSCH resources) for a second physical channel via a second DCI on a second BWP 230 (e.g., BWP 230-b). However, in some examples, sending multiple DCI messages may lead to increased signaling overhead and decoding complexity at both base station 105-a and UE 115-a. For example, if UE 115-a receives multiple DCI messages, UE 115-a may decode each DCI message received by UE 115-a and perform error checks, such as Cyclic Redundancy Check (CRC), which may increase the number of processing operations performed by UE 115-a.

[0097] Depending on various aspects, base station 105-a can jointly schedule multiple physical channels (e.g., PDSCH and PUSCH) between base station 105-a and UE 115-a (e.g., in unpaired radio frequency bands). For example, base station 105-a can transmit a joint control message that may include scheduling information for downlink messages to be received by UE 115-a and uplink messages to be transmitted by UE 115-a. In some cases, the scheduling information allocates a first resource for downlink messages that at least partially overlaps with a second resource for uplink messages in at least one of time or frequency. In some cases, the joint control message may be received via RRC signaling, MAC-CE, or DCI. In some examples, the joint DCI may provide timing information in the TDRA field or frequency information in the FDRA field, which may indicate the time-frequency resources for both downlink and uplink messages for UE 115-a.

[0098] Joint DCI can utilize different DCI formats to provide this information. For example, a joint DCI can have DCI format 0_0, which may include parameters such as: an identifier for the DCI format, FDRA, TDRA, frequency hopping flag, modulation and coding scheme (MCS), new data indicator, redundancy version, HARQ process number, transmit power control (TPC) command for scheduled PUSCH, and uplink / supplementary uplink indicator. In other examples, a joint DCI can have DCI format 1_0, which may include parameters such as: an identifier for the DCI format, FDRA, TDRA, virtual RB (VRB) to physical RB (PRB) mapping, MCS, new data indicator, redundancy version, HARQ process number, downlink assignment index (DAI), TPC command for scheduled physical uplink control channel (PUCCH), PUCCH resource indicator, and PDSCH to HARQ feedback timing indicator. In some examples, FDRA can be configured based on one or more resource assignment types (e.g., type-0, type-1, or dynamic).

[0099] In some examples, UE 115-a can determine the timing information for downlink and uplink messages. In some cases, downlink timing information may be timing parameters of the TDRA field in a joint control message. Alternatively or concurrently, uplink timing information may be timing parameters associated with or determined based on the following: the TDRA field, downlink timing information, higher-layer signaling, or other information. In some examples, the TDRA field may indicate the start symbol, length value, slot offset, mapping type, or any combination thereof for each item in the uplink and downlink messages.

[0100] In some aspects, the DCI can use the number of MSBs or LSBs of the TDRA bit field in the DCI to indicate the TDRA used for PDSCH. The MSB of the TDRA field can indicate one or more characteristics of the PDSCH (e.g., start symbol, length value, slot offset, mapping type). For example, the MSB of the TDRA field can be mapped to a predefined index of the TDRA used for PDSCH. Additionally, some bits of the DCI can indicate one or more characteristics of the PUSCH (e.g., start symbol, transmission allocation length, transmission slot, mapping type, transmission repetition count).

[0101] In some examples, the timing information for the PDSCH can be used by UE 115-a to determine the timing information for the PUSCH. For example, the start symbol value of the downlink message can be used to obtain the start symbol, length value, or slot offset, or a combination thereof, of the uplink message. Additionally, the TDRA parameters used for the uplink message can be configured via higher-layer signaling or dynamically indicated from a configured set. For example, base station 105-a can send a control message indicating the incremental symbol value Δ associated with the timing information used for the uplink message. S Incremental sign value Δ S It can be used to calculate the start symbol of uplink messages. In some examples, the base station can send a control message indicating the incremental timeslot value Δ associated with the timing information used for uplink messages. K Incremental time slot value Δ K These parameters can be used to calculate the time slots for uplink message transmission. In some examples, the base station can send a length indicator, which determines the symbol length for the uplink message. These parameters, along with others, can be used by UE 115-a to determine the timing information for the uplink message.

[0102] In some examples, UE 115-a can determine frequency information for downlink messages (e.g., communications via downlink data area 215) and uplink messages (e.g., communications via uplink data area 205). In some cases, the frequency information can be frequency parameters identified based on the FDRA field in a joint control message (e.g., joint DCI). For example, the frequency information can indicate parameters such as: the starting frequency allocation location (e.g., the index of an RB or RB group (RBG)), the length of the frequency allocation (e.g., the number of RBs or RBGs scheduled for the channel), the offset between the subband receiving the control message and the scheduled downlink or uplink message, and other example frequency parameters.

[0103] UE 115-a can receive joint control messages that include scheduling information (e.g., resource allocation) for downlink and uplink messages. The joint control information may include FDRA indications. UE 115-a can determine one or more frequency domain resource allocations (e.g., BWP230 for uplink data area 205 and downlink data area 215) based on the FDRA indications.

[0104] In some examples, the FDRA indication may be a bitmap. The bitmap may correspond to frequency bandwidth 225, which includes uplink BWP 230 and downlink BWP 230 scheduled for communication between base station 105-a and UE 115-a. Each bit of the bitmap may indicate the RBG allocation for such communication. UE 115-a may determine the BWP 230 for receiving downlink messages within the configured downlink portion of frequency bandwidth 225 based on the indicated RBG allocation. Alternatively, UE 115-a may determine the BWP 230 for transmitting uplink messages within the configured uplink portion of frequency bandwidth 225 based on the indicated RBG allocation. In such examples, a single FDRA field (e.g., a bitmap) in the DCI may indicate both uplink and downlink frequency allocations.

[0105] In some examples, the FDRA indication may be an example of a Resource Indicator Value (RIV). UE 115-a may determine first frequency information associated with downlink or uplink allocation based on the FDRA (e.g., the number of initial RBs and consecutively allocated RBs for uplink or downlink messages may be determined based on all or part of the FDRA). In some examples, the FDRA bit field may indicate uplink frequency allocation for one or more uplink BWP 230s. In some other examples, the FDRA bit field may indicate downlink frequency allocation for one or more downlink BWP 230s (e.g., if the size of the bit field indicating downlink BWP 230 is smaller than the size of the bit field indicating uplink BWP 230, for example, because the size of downlink BWP 230 is smaller than the size of uplink BWP 230).

[0106] UE 115-a can determine second frequency information based on determining first frequency information. For example, UE 115-a can identify one or more adjustment factors for determining the second frequency information. In some examples, UE 115-a can determine the adjustment factors based on one or more pre-configured rules (e.g., scaling parameter K can be determined based on the size of downlink BWP 230 and uplink BWP 230). Alternatively, UE 115-a can determine the adjustment factors based on a subset of bits indicated by FDRA. For example, a first subset of bits X indicated by FDRA can indicate the first frequency information, and a second subset of bits Y indicated by FDRA can indicate the adjustment factors for determining the second frequency information (e.g., scaling parameter B and offset parameter A can be dynamically selected and indicated by the second subset of bits indicated by FDRA). As an illustrative example, UE 115-a can scale the frequency allocation of the first frequency information (e.g., multiply the scaling parameter by the number of RBs), offset the frequency allocation of the first frequency information (e.g., add or subtract the number of RBs from the starting RBs of the first frequency information), or a combination thereof, to determine the second frequency information. In such an example, a single DCI message can indicate uplink and downlink frequency allocations with a relatively small number of bits, which can lead to more efficient communication.

[0107] In some examples, UE 115-a can determine the second frequency information based on at least some bits of the FDRA indication that indicates the first frequency information. For example, the FDRA indication may include an indication of the first frequency information for uplink (or downlink) messages, and some bits of the FDRA indication may indicate the second frequency information in addition to indicating a portion of the first frequency information. For example, the number of MSBs or LSBs indicated by the FDRA may be configured to indicate the second frequency information for downlink (or uplink) messages. In some examples, the FDRA indication may indicate the frequency resource allocation for uplink or downlink messages based on a comparison of the bit field size associated with the uplink message and the bit field size associated with the downlink message. As an illustrative example, the number of bits used to indicate the downlink BWP 230 using the first resource allocation type may be greater than the number of bits used to indicate the uplink BWP 230 using the same or a different resource allocation type. In such examples, the FDRA indication of the FDRA may indicate the frequency allocation for downlink messages, and some bits of the FDRA indication may be configured to indicate the frequency allocation for uplink messages. Therefore, a single DCI message can instruct both uplink and downlink frequency allocations, leading to more efficient communication. Alternatively, the resource assignment type for uplink messages can be configured independently of the resource assignment type for downlink messages, which can improve scheduling flexibility at base station 105-a and other benefits.

[0108] Figure 3 An example of a time-frequency diagram 300 supporting joint shared channel allocation in DCI according to various aspects of this disclosure is shown. In some examples, the time-frequency diagram 300 may be implemented by various aspects of wireless communication systems 100 or 200.

[0109] In some cases, the UE can indicate one or more BWP 330s on the carrier bandwidth to be used for communication with the base station. Additionally, BWP 330s can be selected for downlink or uplink transmission. For example, the UE can select BWP 330-a for receiving downlink communication and BWP 330-b for transmitting uplink communication to the base station on carrier bandwidth 325. In some examples, the UE can receive messages from the base station via one or more subbands of downlink BWP 330-a. Alternatively, the UE can transmit messages to the base station via one or more subbands of uplink BWP 330-b. In some cases, the DCI (e.g., via PDCCH 320) can indicate the direction of communication of the BWP 330s (e.g., downlink or uplink).

[0110] In some examples, the base station can indicate TDRA scheduling information for downlink messages via control messages (e.g., DCI). For example, the DCI can be sent to the UE via PDCCH 320. In some examples, the first number of MSBs in the DCI TRDA bit field can indicate the TDRA for PDSCH 315. In other examples, the LSB in the DCI TRDA bit field can indicate the TDRA for PDSCH 315. The value of the MSB can provide a row index to the allocation table for PDSCH 315. The row index can be calculated by adding 1 to the value of the MSB. For example, the first number of MSBs (e.g., number = 3) in the DCI TRDA field can indicate TDRA timing information for downlink messages. The value of the MSB (e.g., 5) can provide a row index (e.g., 6) to the allocation table for PDSCH 315. The allocation table can then set the timing information for PDSCH 315, such as the start symbol 340-a S. PDSCH (For example, S) PDSCH =2), Transmission length 345-a L PDSCH (For example, L) PDSCH =11), time slot offset K0 (e.g., K0=1) and PDSCH mapping type K PDSCH (For example, demodulation reference signal (DMRS) mapping type K) PDSCH =A).

[0111] The UE can expect in downlink time slot K DL It receives downlink messages. In some examples, downlink time slot K DL This can be represented by Equation 1:

[0112]

[0113] In Equation 1, n can represent the time slot for scheduling DCI. μ PDSCH This can represent the subcarrier spacing configuration used for PDSCH 315, and μ PDCCH The subcarrier spacing configuration for PDCCH 320 can be represented. As an illustrative example of implementing Equation 1, time slot 335-a can represent time slot n, time slot 335-b can represent time slot n+1, and time slot 335-c can represent time slot n+2. If the subcarrier spacing of PDSCH 315 and PDCCH 320 is equal (e.g., 30 kHz) and the time slot offset K0 is equal to 1, then the allocation of PDSCH 315 for downlink messages can begin in time slot n+1 (e.g., time slot 335-b).

[0114] In some cases, the base station may send a joint control message to the UE, which indicates resource allocation information for both uplink messages to be sent to the UE and downlink messages to be received by the UE. The joint control message may include a DCI for TDRA timing information for multiple physical channels (e.g., PDSCH 315, PUSCH 305). For example, the base station may send a joint DCI (e.g., via PDCCH 320) that includes a TDRA field indicating timing information (e.g., start symbol, transmission length, slot index, mapping type) for downlink messages to be received by the UE 115. Additionally, based on the timing information for downlink messages, the UE 115 may determine timing information (e.g., start symbol, transmission length, slot index, mapping type) for uplink messages.

[0115] In some examples, the UE can use timing information from downlink messages to determine the start symbol 340-bS. PUSCH In some examples, the starting symbol is 340-b S. PUSCH It can be expressed by equation 2 or equation 3:

[0116] S PUSCH =(S PDSCH +Δ S )mod 14 (2)

[0117] S PUSCH =(S PDCCH +Δ S )mod 14 (3)

[0118] In equation 2, S PDSCH This can represent the start symbol 340-a of a downlink message. In Equation 3, S PDCCH This can represent the start symbol of DCI (e.g., the start symbol of PDCCH 320). The increment symbol value Δ in both Equations 2 and 3... S You can set S PUSCH This provides greater flexibility. For example, if Equation 2 can be used to configure the starting symbol 340-b S PUSCH The starting symbol is 340-a S. PDSCH It equals 2, and the increment sign value Δ S If the value is 1, then the starting symbol is 340-b S. PUSCH Equals 3. In other examples, if equation 3 can be used to configure the starting symbol 340-b S PUSCH DCI S PDCCH The initial sign is equal to 2, and the increment sign value is Δ. S If the value is 1, then the starting symbol is 340-b S. PUSCHIt equals 2. The incremental symbol value Δ can be configured via higher-layer signaling. S For example, the UE can receive an indication of the incremental symbol value Δ from the base station. S Messages (e.g., RRC signaling, MAC-CE, or DCI). The incremental symbol value Δ can also be indicated in the joint control information. S Alternatively, the incremental symbol value Δ can be dynamically indicated from a configured set. S For example, a base station or UE can select an increment symbol value Δ from a set of increment symbol values ​​based on the set of bits in the DCI. S For example, DCI can be the incremental sign value Δ S Configure 2 bits. Increment symbol value Δ S Bits can be mapped to a configured set of values ​​(e.g., {0, 4, 7, 11}). In some cases, the UE or base station can check for error conditions in the scheduling message. For example, scheduling an uplink message more than N2 symbols after a downlink message.

[0119] In some examples, the UE can use the timing information of the downlink message to determine the PUSCH 305 transmission slot K2 for the uplink message. In some examples, the PUSCH 305 transmission slot K2 can be represented by Equation 4:

[0120]

[0121] In equation 4, K DL This can represent the downlink time slot of a downlink message. μ PUSCH This can represent the subcarrier spacing configuration used for PUSCH305, and μ PDSCH This can represent the subcarrier spacing configuration used for PDSCH 315. S PDSCH The start symbol 340-a can represent the downlink message, and the increment symbol value Δ S This can represent a variable that is notified by a signal from a higher level. The incremental time slot value Δ in Equation 4... K Greater flexibility is provided when setting transmission time slot K2. As an illustrative example of implementing Equation 4, time slot 335-a can represent time slot n, time slot 335-b can represent time slot n+1, and time slot 335-c can represent time slot n+2. If the subcarrier spacing of PDSCH 315 and PDCCH 320 is equal (e.g., 30 kHz), K DL Equals n+1, starting symbol 340-b S PDSCH Equals 2, increment sign value Δ S It equals 1, and the incremental time slot value Δ KIf the value is 1, then the allocation of PUSCH 305 for uplink messages can begin in slot n+2 (e.g., slot 335-c). The incremental slot value Δ can be configured via higher-layer signaling. K For example, the UE can receive an indication of the incremental timeslot value Δ from the base station. K Messages (e.g., RRC signaling, MAC-CE, or DCI). The incremental slot value Δ can also be indicated in the joint control message. K Alternatively, the incremental time slot value Δ can be dynamically indicated from a configured set. K For example, a base station or UE can select an incremental time slot value Δ from a set of incremental time slot values ​​based on a set of bits in the DCI. K For example, DCI can be an incremental time slot value Δ K Configure 1 bit. Incremental time slot value Δ K Bits can be mapped to a configured set of values ​​(e.g., {0, 1}).

[0122] In some examples, the UE can use the timing information of the downlink message to determine the transmission length of the uplink message (345-b). Length indicator L PUSCH This can be used to determine the transmission length 345-b (e.g., nominal duration) for the PUSCH 305. In some cases, the length indicator L... PUSCH The number of symbols for a transmission length of 345-bit can be explicitly indicated, and the length indicator L can be configured via higher-layer signaling. PUSCH For example, the UE can receive an indication length indicator L from the base station. PUSCH Messages (e.g., RRC signaling, MAC-CE, or DCI). In some cases, the length indicator L can be indicated in the joint control message (e.g., PDCCH 320). PUSCH Alternatively, the length indicator L can be dynamically indicated from a configured set. PUSCH For example, the length indicator L PUSCH This can correspond to a set of symbol values, and the UE or base station can select the transmission length 345-b from the set of symbol values. In some aspects, the DCI can configure 2 bits for delta-s, which can be mapped to a configured set of values ​​(e.g., {4, 7, 11, 14}). In some cases, the length indicator L... PUSCH It can be based on the start symbol 340-b determined for PUSCH 305. For example, if the start symbol 340-b is less than 7, then the sum of the start symbol 340-b and the transmission length 345-b is 14 symbols. Otherwise, the sum of the start symbol 340-b and the transmission length 345-b is 21 symbols.

[0123] Depending on several factors, a mapping type (e.g., type A or type B) can be determined for the DMRS used for PUSCH 305. In some examples, only one mapping type, such as type A or type B, is supported for the DMRS used for PUSCH 305. In other examples, type A can be supported based on bits of the DCI field (e.g., contained within PDCCH 320), start symbol 340-b, or transmission length 345-b. For example, if the first X bits of the TDRA field within the DCI carried via PDCCH 320 can indicate support for mapping type A. Alternatively, if start symbol 340-b is symbol index 0 (the first symbol in slot 335-c), and the sum of start symbol 340-b and transmission length 345-b is determined to be greater than 4 symbols, then DMRS mapping type A can be supported and used for transmissions on PUSCH 305.

[0124] In some examples, the number of repetitions for PUSCH 305 can be determined by the UE or the base station. For example, DCI can be used to dynamically indicate the number of repetitions for PUSCH 305, which can be represented as K. PUSCH In some cases, K PUSCH The number of repetitions K that can be used with PDSCH315 PDSCH The same information can be provided to the UE via the DCI (e.g., one or more bits within the DCI carried by PDCCH 320 can indicate to the UE that the number of repetitions for PDSCH 315 and PUSCH 305 is the same). In some examples, the UE can be configured with a fixed value that can be used based on K. PDSCH Determine K PUSCH This makes the fixed value related to K. PDSCH Add to determine K PUSCH For example, the fixed value can be 1, and in the illustrative example, if K PDSCH If there are two repetitions, then K PUSCH It could be K PDSCH The sum of fixed values ​​(in this case, for K) PUSCH (This results in 2+1=3 repetitions). This technique can leverage the reciprocity between uplink and downlink in unpaired spectrum. Alternatively, K can be configured via higher-layer signaling. PUSCH For example, the UE can receive from the base station an indication of the number of repetitions K for PUSCH 305. PUSCH Messages (e.g., RRC signaling, MAC-CE, or DCI).

[0125] Based on the timing information determined for PUSCH 305 and PDSCH 315, the UE can send PUSCH 305 according to the uplink timing information and receive PDSCH 315 according to the downlink timing information.

[0126] Figure 4 An example of a time-frequency diagram 400 supporting joint shared channel frequency allocation in DCI according to various aspects of this disclosure is shown. In some examples, the time-frequency diagram 400 can implement various aspects of wireless communication systems 100 and 200. For example, the time-frequency diagram 400 can be as shown in reference... Figure 1 and 2 An example of communication between base station 105 and UE 115 is described. Time-frequency diagram 400 may illustrate an example of joint control messages scheduling uplink and downlink communication. For example, the DCI sent in PDCCH message 415 may indicate time-frequency resources for PDSCH message 420 and PUSCH message 425, as described herein.

[0127] The base station may transmit a PDCCH message 415 (e.g., a joint control message) that includes an FDRA field, a TDRA field, or both. The FDRA field may indicate both uplink and downlink frequency information. For example, a UE may receive a PDCCH message 415 that includes scheduling information (e.g., resource allocation) for PDSCH messages 420 and PUSCH messages 425. The PDCCH message 415 may include an FDRA indication. The UE may determine one or more frequency domain resource allocations based on the FDRA indication. For example, the UE may use the FDRA indication to determine the frequency range (e.g., subband) for transmitting PDSCH messages 420 in BWP 410-a and the frequency range for receiving PUSCH messages 425 in BWP 410-b.

[0128] In some examples, FDRA can be configured as type 0, type 1, or dynamic resource allocation type. For example, FDRA can be type 0, and the frequency resource allocation can be in the form of a bitmap, where each bit of the bitmap can correspond to a nominal RBG allocation of a number of consecutive RBs. In some examples, the number of consecutive RBs can be configured, or it can depend on the size of the BWP 410 associated with the frequency allocation. Alternatively or concurrently, FDRA can be type 1, and the frequency resource allocation can be in the form of a continuous RB allocation (e.g., determined according to the RIV equation), where the starting RB and the number of consecutive (e.g., consecutive in frequency or time) allocated RBs are determined based on FDRA. In some examples, the fallback DCI procedure can support type 1 FDRA.

[0129] In some examples, the FDRA can correspond to both first frequency information for downlink messages (e.g., PDSCH message 420) and second frequency information for uplink messages (e.g., PUSCH message 425). For example, the FDRA can be type 0 and can include a bitmap. A bitmap can be defined on bandwidth 405, which covers all configured (e.g., scheduled) uplink and downlink BWPs 410 (e.g., uplink BWP 410-b and downlink BWP 410-a) in slot 435. Bits in the bitmap can indicate the allocation of an associated RBG for communication (e.g., a value of 0 can indicate the allocation of an associated RBG for communication, and a value of 1 can indicate that no associated RBG has been allocated for communication). The UE can be configured to determine whether an RBG is allocated for downlink or uplink messages based on the position of the RBG in bandwidth 405. For example, if an RBG with a flag bit indicating allocation (e.g., a bit with a value of 1) is in BWP 410-a corresponding to downlink communication, the UE can determine that the allocation is for PDSCH message 420. If an RBG with a flag bit indicating allocation (e.g., a bit with a value of 1) is in BWP 410-b corresponding to uplink communication, the UE can determine that the allocation is for PUSCH message 425. Therefore, a single FDRA field in the DCI can indicate both uplink and downlink resource allocation. In some examples, the bit field size of an FDRA that includes a bitmap for both uplink and downlink allocation can be larger than the bit field size of an FDRA that includes a bitmap for either uplink or downlink communication.

[0130] In some examples, the UE can determine the first frequency information associated with downlink or uplink allocation based on the FDRA. For example, the FDRA can indicate resource allocation information. In some examples, the first frequency information can correspond to uplink allocation (e.g., the FDRA can indicate frequency information for PUSCH message 425 in BWP 410-b). In some other examples, the first frequency information can correspond to downlink allocation (e.g., the FDRA can indicate frequency information for PDSCH message 420 in BWP 410-a). The UE can be configured to determine the first frequency for uplink or downlink allocation based on one or more sizes of BWP 410. For example, the UE can compare the size of BWP 410-a associated with downlink communication (e.g., the number of physical RBs in BWP 410-a) with the size of BWP 410-b associated with uplink communication. The UE can determine that the first frequency information corresponds to an uplink allocation based on the fact that the size of BWP 410-b is less than (or greater than) the size of BWP 410-a. Alternatively, the UE can determine that the first frequency information corresponds to a downlink allocation based on the size of BWP 410-a being less than (or greater than) the size of BWP410-a. In some examples, a relatively smaller BWP410 can use fewer bits in the FDRA indication (e.g., a relatively small bit field can be implemented for the FDRA). In some examples, determining the first frequency information includes determining the frequency information according to the RIV equation (e.g., for type 1 resource allocation).

[0131] In some examples, the UE can determine the second frequency information based on determining the first frequency information. For example, the UE can identify one or more adjustment factors for determining the second frequency information. In some examples, the UE can determine the adjustment factors based on one or more pre-configured rules (e.g., rules configured by RRC signaling or the UE's configuration). As an illustrative example, the UE can identify a scaling parameter (e.g., scaling parameter K) based on the size of the downlink BWP 410-a and the size of the uplink BWP 410-b. For example, K can be an equation satisfying a set of values ​​(such as 1, 2, 4, 8, etc.). The maximum value of DL, where DL BWP This indicates the size of the downlink BWP 410-a, and the UL BWP This indicates the size of the uplink BWP 410-b (e.g., the number of physical RBs in the BWP 410-b).

[0132] Alternatively, the UE may determine the adjustment factor based on a subset of bits in the FDRA. For example, a first subset of bits in the FDRA (e.g., X MSBs or LSBs in the FDRA) may indicate first frequency information, and a second subset of bits in the FDRA (e.g., Y bits in the FDRA, where the FDRA comprises a total of X+Y bits) may indicate an adjustment factor for determining second frequency information. For example, a scaling parameter B and an offset parameter A (e.g., A may be a value between 10 and 20, B may be a value of 1, and other parameter examples) may be dynamically selected (e.g., by the base station) from a set of parameters configured at a higher layer. Such parameters may be indicated by a second subset of bits in the FDRA (e.g., Y bits, such as 1 bit in the FDRA).

[0133] The UE can identify the second frequency information based on the first frequency information or one or more adjustment factors. For example, the UE can identify the first frequency information from the FDRA and adjust the first frequency information to derive the second frequency information. As an illustrative example, the first frequency information may correspond to an uplink allocation, and the UE can scale the starting RB of the first frequency information according to Equation 1 to determine the starting RB of the second frequency information:

[0134]

[0135] In equation 5, The starting RB can represent the PDSCH message 420, and K can represent the scaling factor as described herein. This can represent the start RB of PUSCH message 425. Alternatively, the UE can, for example, according to...

[0136] Equation 6 is used to scale the number of RBs in the first information to determine the number of RBs in the second frequency information:

[0137]

[0138] In equation 6, This can represent the frequency length in the RB of PDSCH message 420, and It can represent the frequency length in the RB of PUSCH message 425.

[0139] As another illustrative example of adjusting the first frequency information to determine the second frequency information, the UE can implement equations 7 and 8:

[0140]

[0141]

[0142] In Equations 7 and 8, B can represent the scaling parameter, and A can represent the determined offset parameter as described herein.

[0143] In some examples, the UE may determine the second frequency information based on an indication of the first frequency information. For example, the FDRA indication may include an indication of the first frequency information used for PUSCH message 425 (or PDSCH message 420). The UE may be configured to determine whether the first frequency information corresponds to an uplink allocation or a downlink allocation based on one or more bit field sizes. For example, the UE may compare the bit field size associated with PDSCH message 420 (e.g., the number of bits resulting from the resource assignment type of the downlink allocation or the size of BWP 410-a) with the bit field size associated with PUSCH message 425 (e.g., the number of bits resulting from the resource assignment type of the downlink allocation or the size of BWP 410-b). The UE may determine that the first frequency information corresponds to an uplink allocation based on the fact that the bit field size of the uplink allocation is greater than the bit field size of the downlink allocation. Alternatively, the UE may determine that the first frequency information corresponds to a downlink allocation based on the fact that the bit field size of the downlink allocation is greater than the bit field size of the uplink allocation.

[0144] In some examples, a subset of bits can be repurposed (e.g., by a base station) to indicate secondary frequency information. For example, a subset of bits in an FDRA (e.g., Y LSBs or MSBs of the bit field of the FDRA) can be configured to indicate second frequency information for PDSCH message 420 (or PUSCH message 425) in addition to indicating a portion of the first frequency information. In some examples, the number of bits included in the bit subset can be based on the size of BWP 410-a, the size of BWP 410-b, the resource assignment type for PUSCH message 425, the resource assignment type for PDSCH message 420, or any combination thereof. In some examples, by implementing an FDRA to indicate the first frequency information and using a subset of bits in the FDRA to indicate the second frequency information, the resource assignment type for PDSCH message 420 can be configured independently of the resource assignment type for PUSCH message 425.

[0145] In some examples, the various operations described in time-frequency diagram 400 may be performed in different orders or combinations, or may be performed by different devices. For example, an operation performed by the UE may be performed by the base station, or an operation performed by the base station may be performed by the UE, and other examples.

[0146] Figure 5A and 5BAn example time-frequency diagram 500 supporting joint shared channel allocation in DCI is shown according to various aspects of this disclosure. In some examples, the time-frequency diagram 500 may be implemented by various aspects of wireless communication systems 100 or 200.

[0147] exist Figure 5A In this context, the Joint Control Message 520-a can schedule uplink messages (such as PUSCH 505-a) to be sent by the UE and downlink messages (such as PDSCH 515-a) to be sent from the base station to the UE. In some cases, the Joint Control Message 520-a can be a PDCCH carrying a Joint DCI, which includes a TDRA field that can be used by the UE to determine timing information for PUSCH 505-a and PDSCH 515-a.

[0148] In some aspects, PUSCH 505-a can be scheduled for transmission via BWP 530-b, and PDSCH 515-a can be scheduled for transmission via BWP 530-a. BWP 530-a and BWP 530-b can be on the same carrier or within bandwidth 525-a. In some cases, the timing information determined by the UE for transmitting PUSCH 505-a can be timing information associated with when the base station expects to receive PUSCH 505-a. In such cases, from the base station's perspective, time slot 535-a at the UE may be misaligned in time with the corresponding time slot. Therefore, as part of transmitting PUSCH 505-a to the base station, the UE can determine to apply a timing advance 550 (as shown, this timing advance 550 spans one symbol length in duration, but can be of any length in time) so that PUSCH 505-a arrives at the base station at the expected time.

[0149] exist Figure 5B In this context, the Joint Control Message 520-b can schedule uplink messages (such as PUSCH 505-b) to be sent by the UE and downlink messages (such as PDSCH 515-b) to be sent from the base station to the UE. In some cases, the Joint Control Message 520-b can be a PDCCH carrying a Joint DCI, which includes a TDRA field that can be used by the UE to determine timing information for PUSCH 505-b and PDSCH 515-b.

[0150] In some aspects, PUSCH 505-b can be scheduled for transmission via BWP 530-d, and PDSCH 515-b can be scheduled for transmission via BWP 530-c. BWP 530-c and BWP 530-d can be on the same carrier or within bandwidth 525-b. In some cases, the timing information determined by the UE for transmitting PUSCH 505-b can be absolute timing information, such that from the base station's perspective, time slot 535-b at the UE is time-aligned with the corresponding time slot. Therefore, the UE can avoid applying timing advances, such as in... Figure 5A This is carried out as part of sending PUSCH 505-b to the base station.

[0151] Figure 6 An example of a process flow 600 supporting joint shared channel allocation in DCI according to various aspects of this disclosure is shown. In some examples, process flow 600 may implement various aspects of wireless communication system 100 or 200. Process flow 600 may include UE 115-b and base station 105-b, which may be examples of corresponding devices as described herein. 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.

[0152] At point 605, base station 105-b can determine scheduling information for UE 115-b. The scheduling information may include information for downlink messages to be received by UE 115-b and uplink messages to be transmitted by UE 115-b. In some cases, the time-frequency resources for uplink and downlink messages may at least partially overlap in one or both of time and frequency. Alternatively, downlink messages and uplink messages may be scheduled via the same carrier.

[0153] At position 610, base station 105-b may send a control message (e.g., a joint control message) to UE 115-b. The control message may indicate scheduling information for uplink and downlink messages determined by base station 105-b at position 605. In some examples, base station 105-b may send a control channel, such as a PDCCH, that generates the control message. In some cases, the control message may be a joint DCI message including a TDRA field, which may indicate timing information for both uplink and downlink messages for UE 115-b. The control message may indicate the MCS for downlink messages, uplink messages, or both.

[0154] At 615, base station 105-b may optionally send a message to UE 115-b. For example, base station 105-b may send a control channel (such as PDCCH) including the message (e.g., in DCI), or the base station may send the message to UE 115-b on PDSCH (e.g., MAC-CE, RRC). The message may be sent before or after the control message sent at 610. In some cases, the message may be included in the control message sent at 610. The message may indicate an incremental value (e.g., an incremental symbol value or an incremental timeslot value) that can be used by UE 115-b to determine timing information for uplink messages. In some cases, the message may indicate a set of incremental values ​​from which UE 115-b selects a symbol or timeslot value when determining timing information for uplink messages. In some cases, the message may include a length indicator indicating the transmission length of the uplink message or a repetition index corresponding to the number of repetitions in the downlink or uplink message.

[0155] At 620, UE 115-b can determine timing information for downlink messages based on control message 610 and the optional RRC message sent at 615. For example, UE 115-b can determine the start symbol, transmission length, or timeslot for receiving downlink messages. In some cases, the timing information for downlink messages can be based on the TDRA field within the control message. The TDRA field can indicate the Start Length Indicator (SLIV) value, the mapping type for DMRS, or the timeslot offset for receiving downlink messages.

[0156] At 625, UE 115-b may determine the timing information for the uplink message based on control message 610, the downlink timing information determined at 620, or an optional RRC message sent at 615. For example, UE 115-b may determine the start symbol or transmission length of the uplink message based on the downlink message timing information (e.g., start symbol or transmission length). In some cases, UE 115-b may determine the timing information for the uplink message based on one or more incremental values ​​(e.g., incremental slot value or incremental symbol value), and may indicate the one or more incremental values ​​to UE 115-b in the RRC message sent at 615. Alternatively or additionally, UE 115-b may determine the DMRS mapping type or repetition number of the uplink message based on the timing information for the uplink message, the downlink message, or the number of repetitions of the downlink message.

[0157] At 630, base station 105-b can transmit and UE 115-b can receive downlink messages scheduled by the control message transmitted at 610. Downlink messages can be carried in the PDSCH. Downlink messages can be transmitted based on timing information included in the control message or determined by UE 115-b at 620. In some examples, downlink messages can be received at UE 115-b via a carrier different from the carrier used for transmitting the control message at 610.

[0158] At 635, UE 115-b can send an uplink message scheduled by the control message sent at 610 to base station 105-b. The uplink message can be carried by the PUSCH. The uplink message can be sent based on timing information included in the control message or determined by UE 115-b at 625. In some examples, the uplink message can be sent by UE 115-b via a different carrier than the carrier used for transmitting the control message at 610. In some cases, the uplink message can be sent via the same carrier as the downlink message received at 630 and can partially overlap with the downlink message in time. In some examples, the MCS used for the uplink message can be different from the MCS used for transmitting the downlink message. The MCS used for the uplink message can be indicated by the control message sent at 610, or it can be determined based on the MCS used for the downlink message (which can be indicated by the control message sent at 610).

[0159] Figure 7 A block diagram 700 of an apparatus 705 supporting joint shared channel allocation in DCI is shown according to various aspects of this disclosure. Apparatus 705 may be an example of various aspects of UE 115 as described herein. Apparatus 705 may include a receiver 710, a communications manager 715, and a transmitter 720. Apparatus 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0160] Receiver 710 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to joint shared channel allocation supporting DCI). This information can be passed to other components of device 705. Receiver 710 can be a reference... Figure 10 Examples of various aspects of the transceiver 1020 are described. The receiver 710 may utilize a single antenna or an array of antennas.

[0161] The communication manager 715 can perform the following operations: receive a control message from a base station, the control message including scheduling information for downlink messages to be received by the UE and uplink messages to be transmitted by the UE, the scheduling information allocating a first resource for downlink messages and a second resource for uplink messages; determine timing information for downlink messages based on the scheduling information; determine timing information for uplink messages based on the timing information for downlink messages and the scheduling information; use the first resource to receive downlink messages according to the timing information for downlink messages determined based on the scheduling information; and use the second resource to transmit uplink messages according to the timing information for uplink messages determined based on the timing information for downlink messages and the scheduling information. In some examples, the first resource may at least partially overlap with the second resource in at least one of time or frequency. The communication manager 715 may be an example of aspects of the communication manager 1010 described herein.

[0162] The communication manager 715 or its sub-components may be implemented in hardware, processor-executable code (e.g., software or firmware), or any combination thereof. If implemented in processor-executable code, the functionality of the communication manager 715 or its sub-components may be performed by a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described in this disclosure.

[0163] The communication manager 715 or its sub-components may be physically located at various locations, including being distributed such that some functions are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of this disclosure, the communication manager 715 or its sub-components may be separate and distinct components. In some examples, according to various aspects of this disclosure, the communication manager 715 or its sub-components may be combined with one or more other hardware components, including but not limited to input / output (I / O) components, transceivers, network servers, other computing devices, one or more other components described in this disclosure, or combinations thereof.

[0164] Transmitter 720 can transmit signals generated by other components of device 705. In some examples, transmitter 720 can be co-located with receiver 710 in a transceiver module. For example, transmitter 720 can be a reference... Figure 10 Examples of various aspects of the transceiver 1020 are described. The transmitter 720 may utilize a single antenna or an array of antennas.

[0165] In some examples, the communication manager 715 may be implemented as an integrated circuit or chipset for a mobile device modem, and the receiver 710 and transmitter 720 may be implemented as analog components (e.g., amplifiers, filters, antennas) coupled to the mobile device modem to enable wireless transmission and reception on one or more frequency bands.

[0166] A communication manager 715 as described herein can be implemented to achieve one or more potential advantages. One implementation allows device 705 to use control messages (e.g., joint DCI) to determine timing information (e.g., timing resource allocation information or parameters associated with the TDRA field) for uplink and downlink communications. Based on the techniques used to determine timing information for both uplink and downlink messages (e.g., in joint control messages such as joint DCI), device 705 can more efficiently power the processor or one or more processing units associated with transmit and receive communications, which can enable the device to save power and extend battery life.

[0167] Figure 8 A block diagram 800 of an apparatus 805 supporting joint shared channel allocation in DCI is shown according to various aspects of this disclosure. Apparatus 805 may be an example of aspects of apparatus 705 or UE 115 as described herein. Apparatus 805 may include a receiver 810, a communications manager 815, and a transmitter 840. Apparatus 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0168] Receiver 810 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to joint shared channel allocation in DCI). It can pass this information to other components of device 805. Receiver 810 can be a reference... Figure 10 Examples of various aspects of the transceiver 1020 are described. The receiver 810 may utilize a single antenna or an array of antennas.

[0169] Communication manager 815 may be an example of aspects of communication manager 715 as described herein. Communication manager 815 may include joint control receiver 820, downlink timing component 825, uplink timing component 830, and message transmitter 835. Communication manager 815 may be an example of aspects of communication manager 1010 as described herein.

[0170] The joint control receiver 820 can receive control messages from the base station, which include scheduling information for downlink messages to be received by the UE and uplink messages to be transmitted by the UE. This scheduling information allocates a first resource for downlink messages and a second resource for uplink messages. In some examples, the first resource may at least partially overlap with the second resource in at least one of time or frequency.

[0171] The downlink timing component 825 can determine the timing information for downlink messages based on scheduling information.

[0172] The uplink timing component 830 can determine the timing information for uplink messages based on the timing and scheduling information used for downlink messages.

[0173] The message transmitter 835 may use a first resource to receive downlink messages based on timing information for downlink messages determined based on scheduling information; and use a second resource to send uplink messages based on timing information for uplink messages determined based on both the timing information for downlink messages and scheduling information.

[0174] Transmitter 840 can transmit signals generated by other components of device 805. In some examples, transmitter 840 can be co-located with receiver 810 in a transceiver module. For example, transmitter 840 can be a reference... Figure 10 Examples of various aspects of the transceiver 1020 are described. The transmitter 840 may utilize a single antenna or an array of antennas.

[0175] Receiver 810 can receive analog or digital radio frequency (RF) signals 801 via an antenna or antenna array, and can pass signaling 811 to joint control receiver 820. Signaling 811 may include one or more sets of bits of control messages (such as joint DCI) for scheduling both uplink and downlink messages for device 805. Joint control receiver 820 can send timing information 812 to downlink timing component 830 and uplink timing component 830. Timing information 812 may include bits corresponding to one or more bit fields of the control message indicating timing information for uplink or downlink messages for device 805.

[0176] Downlink timing component 825 can send downlink timing information 826, such as a start symbol, SLIV, or other timing parameters corresponding to a downlink message for device 805, to message transmitter 835. Uplink timing component 830 can send uplink timing information 831, such as a start symbol, SLIV, or other timing parameters corresponding to an uplink message for device 805, to message transmitter 835. Message transmitter 835 can prepare an uplink message or other uplink information 836 for transmission to transmitter 840, which can then transmit the uplink message 841. Message transmitter 835 can send downlink message information 837 to receiver 810, and receiver 810 receives downlink message 828 based on downlink message information 837.

[0177] Figure 9 A block diagram 900 of a communication manager 905 supporting joint shared channel allocation in DCI according to various aspects of this disclosure is shown. The communication manager 905 may be an example of aspects of the communication manager 715, communication manager 815, or communication manager 1010 described herein. The communication manager 905 may include a control receiver 910, a downlink timing component 915, an uplink timing component 920, a message transmitter 925, an incremental receiver 930, an uplink symbol component 935, a timeslot manager 940, a resource component 945, a timing advance component 950, a length manager 955, a mapping component 960, a repeat manager 965, and an MCS component 970. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0178] Control receiver 910 can receive control message 901 from base station. Control message 901 includes scheduling information for downlink messages to be received by UE and uplink messages to be transmitted by UE. The scheduling information allocates a first resource for downlink messages and a second resource for uplink messages. In some examples, the first resource may at least partially overlap with the second resource in at least one of time or frequency. In some examples, control receiver 910 may receive control message 901 via a carrier different from the carriers used for uplink and downlink messages. Control receiver 910 may transmit control message 901 to one or more of downlink timing component 915, uplink timing component 920, or MCS component 970.

[0179] Downlink timing component 915 can determine downlink timing information 916 for downlink messages based on fields of control message 901. In some examples, downlink timing component 915 can determine the start symbol, length value, slot offset, mapping type, or any combination thereof for downlink messages based on the TDRA field of the control message.

[0180] The uplink timing component 920 can determine the uplink timing information 921 for the uplink message based on the downlink timing information 916 and the control message 901. In some examples, the uplink timing component 920 can receive the control message 901, the timing information for the downlink message 916, or both.

[0181] The message transmitter 925 can transmit uplink and downlink messages 926 (e.g., with a base station) based on downlink timing information 916 and uplink timing information 921. In some examples, the message transmitter 925 can receive downlink timing information 916 from downlink timing component 915, uplink timing information 921 from uplink timing component 920, or both. In some examples, the message transmitter 925 can send uplink messages based on a time resource set and the timing advance of the application. In some cases, the message transmitter 925 can send uplink messages via a time resource set. In some cases, the message transmitter 925 can send uplink messages based on a determined symbol length. In some aspects, the message transmitter 925 can transmit uplink and downlink messages with the base station via the same carrier based on scheduling information.

[0182] Incremental receiver 930 can receive from the base station a message indicating an incremental symbol value 931 associated with an uplink message, wherein this message is received via RRC signaling, MAC-CE, or DCI. In some examples, incremental receiver 930 can select an incremental symbol value from a set of incremental symbol values ​​based on scheduling information (e.g., included in control message 901). In some examples, incremental receiver 930 can receive joint control message 901. In some cases, incremental receiver 930 can receive from the base station a message indicating an incremental timeslot value 932 associated with timing information of an uplink message, wherein this message is received via RRC signaling, MAC-CE, or DCI.

[0183] The uplink symbol component 935 can determine the start symbol 936 for the uplink message based on the start symbol of the downlink message (e.g., timing information included in downlink timing information 916) and the increment symbol value 931. In some examples, the uplink symbol component 935 can determine the start symbol 936 for the uplink message based on the increment symbol value 931 and the symbol in which control message 901 is received during a monitoring period. In some examples, the uplink symbol component 935 can receive the increment symbol value 931, control message 901, or both.

[0184] The time slot manager 940 can determine the time slots for uplink message transmission based on the start symbol for the downlink message (e.g., included in the timing information for the downlink message 916), the incremental time slot value 932, and a ratio based on a first subcarrier spacing for the uplink message and a second subcarrier spacing for the downlink message. In some examples, the time slot manager 940 can receive the timing information for the downlink message 916, the time slot increment value 932, or both. In some examples, the time slot manager 940 can determine the time slots for uplink message transmission based on the time slots scheduled for downlink messages and the incremental time slot value 932.

[0185] Resource component 945 can determine a set of time resources 946 for uplink message transmission based on timing information used for downlink message 916. In some examples, resource component 945 can determine a set of time resources aligned with the set of downlink symbols (e.g., downlink time slots) for uplink message transmission based on downlink timing information 916 or uplink timing information 921. In some examples, resource component 945 can receive downlink timing information 916, uplink timing information 921, or both.

[0186] The timing advance component 950 can apply timing advance for the UE to send uplink messages based on the time resource set 946. In some examples, the timing advance component 950 can receive the time resource set 946.

[0187] The length manager 955 can determine the symbol length for the transmission of the uplink message 956 based on the start symbol 936. In some examples, the length manager 955 can receive a message from a base station that includes a length indicator 937 for the transmission of the uplink message, wherein the message is received via RRC signaling, MAC-CE, or DCI. In some cases, the length manager 955 can determine the symbol length for the uplink message based on the length indicator. In some cases, the length indicator 937 can include a set of symbol lengths. In some cases, the length manager 955 can select a symbol length from the set of symbol lengths based on scheduling information (e.g., included in control message 901). In some examples, the length manager 955 can receive the start symbol of the uplink symbol 936, control message 901, or both.

[0188] Mapping component 960 can determine the reference signal mapping type for the uplink message based on a portion of the scheduling information in control message 901. In some examples, mapping component 960 can determine that the reference signal mapping type is type A mapping based on the start symbol 936 and symbol length 956 of the uplink message. In some examples, mapping component 960 can receive control message 901, start symbol 936, symbol length 956, or a combination thereof.

[0189] The duplication manager 965 can determine the duplication index based on scheduling information (e.g., included in control message 901). In some examples, the duplication manager 965 can determine the number of duplications for uplink messages based on the duplication index. In some cases, the duplication manager 965 can determine the number of duplications for downlink messages based on scheduling information. In some aspects, the duplication manager 965 can determine the number of duplications for uplink messages based on the number of duplications for downlink messages. In some cases, the duplication manager 965 can determine the number of duplications for uplink messages based on the number of duplications for downlink messages and an increment value 931. In some examples, the duplication manager 965 can receive a message including a duplication index 966 from a base station, wherein the message is received via RRC signaling. In some examples, the duplication manager 965 can receive control message 901, increment value 931, or both.

[0190] MCS component 970 can determine a first MCS for downlink messages based on control message 901. In some examples, MCS component 970 can receive control message 901. In some examples, MCS component 970 can determine a second MCS for uplink messages based on the first MCS for downlink messages.

[0191] Figure 10A diagram of a system 1000 including device 1005 supporting joint shared channel allocation in DCI is shown according to various aspects of this disclosure. Device 1005 may be an example of device 705, device 805, or UE 115 as described herein, or a component including device 705, device 805, or UE 115. Device 1005 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, including a communication manager 1010, an I / O controller 1015, a transceiver 1020, an antenna 1025, a memory 1030, and a processor 1040. These components may communicate electronically via one or more buses (e.g., bus 1045).

[0192] The communication manager 1010 can perform the following operations: receive a control message (e.g., a joint control message) from a base station, the control message including scheduling information for downlink messages to be received by the UE and uplink messages to be transmitted by the UE, the scheduling information allocating a first resource for downlink messages and a second resource for uplink messages; determine timing information for downlink messages based on the scheduling information; determine timing information for uplink messages based on the timing information for downlink messages and the scheduling information; use the first resource to receive downlink messages according to the timing information for downlink messages determined based on the scheduling information; and use the second resource to transmit uplink messages according to the timing information for uplink messages determined based on the timing information for downlink messages and the scheduling information. In some examples, the first resource may at least partially overlap with the second resource in at least one of time or frequency.

[0193] I / O controller 1015 can manage input and output signals for device 1005. I / O controller 1015 can also manage peripheral devices not integrated into device 1005. In some cases, I / O controller 1015 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 1015 can utilize, for example... This can be an operating system such as a modem, keyboard, mouse, touchscreen, or similar device, or an interaction with such devices. In some cases, the I / O controller 1015 may be implemented as part of a processor. In some cases, a user may interact with the device 1005 via the I / O controller 1015 or via hardware components controlled by the I / O controller 1015.

[0194] Transceiver 1020 can communicate bidirectionally via one or more antennas, wired or wireless links as described herein. For example, transceiver 1020 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. Transceiver 1020 may also include a modem for modulating packets and providing the modulated packets to the antenna for transmission, and demodulating packets received from the antenna.

[0195] In some cases, a wireless device may include a single antenna 1025. However, in other cases, the device may have more than one antenna 1025, which are capable of transmitting or receiving multiple wireless transmissions simultaneously.

[0196] Memory 1030 may include random access memory (RAM) and read-only memory (ROM). Memory 1030 may store computer-readable, computer-executable code 1035, which includes instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, in addition, memory 1030 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0197] Processor 1040 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, central processing units (CPUs), microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1040 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 1040. Processor 1040 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1030) to cause device 1005 to perform various functions (e.g., functions or tasks supporting joint shared channel allocation in DCI).

[0198] Code 1035 may include instructions for implementing various aspects of this disclosure, including instructions for supporting wireless communication. Code 1035 may be stored in a non-transitory computer-readable medium (e.g., system memory or other types of memory). In some cases, code 1035 may not be directly executable by processor 1040, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0199] By including or configuring the communication manager 1010 according to the examples described herein, the device 1005 can support technologies for: improved communication reliability, reduced latency, improved user experience associated with reduced processing, reduced power consumption, more efficient use of communication resources, improved coordination between devices, longer battery life, and improved utilization of processing power.

[0200] Figure 11 A flowchart illustrating a method 1100 for supporting joint shared channel allocation in DCI according to various aspects of this disclosure is shown. Operation of method 1100 can be implemented by a UE 115 or base station 105 as described herein, or by components of UE 115 or base station 105. For example, operation of method 1100 can be implemented by, as described in reference... Figures 7 to 10 The described communication manager is used for execution. In some examples, the UE can execute a set of instructions to control the UE's functional units to perform the functions described herein. Alternatively, the UE can use dedicated hardware to perform aspects of the functions described herein.

[0201] At 1105, the UE can receive a control message (e.g., a joint control message) from the base station. This control message includes scheduling information for downlink messages to be received by the UE and uplink messages to be transmitted by the UE. This scheduling information allocates a first resource for downlink messages and a second resource for uplink messages. In some examples, the first resource may at least partially overlap with the second resource in at least one of time or frequency.

[0202] In some examples, the base station may send a control message to the UE, which includes scheduling information for downlink messages to be sent by the base station and uplink messages to be received by the base station. The scheduling information allocates a first resource for downlink messages, which at least partially overlaps with a second resource for uplink messages in at least one of time or frequency.

[0203] The operation of 1105 can be performed according to the method described in this article. In some examples, aspects of the operation of 1105 can be derived from, as referenced... Figures 7 to 10 The described joint control receiver is used to perform this.

[0204] At point 1110, the UE can determine the timing information for downlink messages based on scheduling information. The operation at point 1110 can be performed according to the method described herein. In some examples, aspects of the operation at point 1110 can be determined by, as referenced... Figures 7 to 10 The downlink timing component is described and executed.

[0205] At step 1115, the UE can determine the timing information for the uplink message based on the timing and scheduling information used for the downlink message. The operation at step 1115 can be performed according to the method described herein. In some examples, aspects of the operation at step 1115 can be determined as described in reference... Figures 7 to 10 The uplink timing component described is used for execution.

[0206] At 1110, the UE can use the first resource to receive downlink messages based on timing information determined based on scheduling information. The operation at 1120 can be performed according to the method described herein. In some examples, aspects of the operation at 1110 can be determined as described in reference... Figures 7 to 10 The message transmitter described is used to execute.

[0207] At 1115, the UE can use the second resource to send uplink messages based on the timing information for uplink messages determined based on the timing information and scheduling information for downlink messages. The operation at 1120 can be performed according to the method described herein. In some examples, aspects of the operation at 1120 can be determined as described in reference... Figures 7 to 10 The message transmitter described is used to execute.

[0208] The operation 1115 can be performed according to the method described in this article. In some examples, aspects of the operation 1115 can be derived from, as referenced... Figures 7 to 10 The message transmitter described is used to execute.

[0209] Figure 12 A flowchart illustrating a method 1200 for supporting joint shared channel allocation in DCI according to various aspects of this disclosure is shown. Operation of method 1200 can be implemented by a UE 115 or base station 105, or components of UE 115 or base station 105, as described herein. For example, operation of method 1200 can be implemented by, as described in reference... Figures 7 to 10 The described communication manager is used for execution. In some examples, the UE can execute a set of instructions to control the UE's functional units to perform the functions described herein. Alternatively, the UE can use dedicated hardware to perform aspects of the functions described herein.

[0210] At 1205, the UE can receive a control message (e.g., a joint control message) from the base station. This control message includes scheduling information for downlink messages to be received by the UE and uplink messages to be transmitted by the UE. This scheduling information allocates a first resource for downlink messages and a second resource for uplink messages. In some examples, the first resource may at least partially overlap with the second resource in at least one of time or frequency.

[0211] In some examples, the base station may send a joint control message to the UE, which includes scheduling information for downlink messages to be sent by the base station and uplink messages to be received by the base station. The scheduling information allocates a first resource for the downlink messages, which at least partially overlaps with a second resource for the uplink messages in at least one of time or frequency.

[0212] The operation of 1205 can be performed according to the method described in this article. In some examples, aspects of the operation of 1205 can be derived from, as shown in the reference... Figures 7 to 10 The described joint control receiver is used to perform this.

[0213] At point 1210, the UE can determine the timing information for downlink messages based on scheduling information. The operation at point 1210 can be performed according to the method described herein. In some examples, aspects of the operation at point 1210 can be determined by, as referenced... Figures 7 to 10 The downlink timing component is described and executed.

[0214] At point 1215, the UE can determine the start symbol, length value, slot offset, mapping type, or any combination thereof for the downlink message based on the TDRA field of the control message. The operation at point 1215 can be performed according to the method described herein. In some examples, aspects of the operation at point 1215 can be determined as described in reference... Figures 7 to 10 The downlink timing component is described and executed.

[0215] At point 1220, the UE can determine the timing information for the uplink message based on the timing and scheduling information used for the downlink message. The operation at point 1220 can be performed according to the method described herein. In some examples, aspects of the operation at point 1220 can be determined as described in reference... Figures 7 to 10 The uplink timing component described is used for execution.

[0216] At point 1225, the UE can use a first resource to receive downlink messages based on timing information determined based on scheduling information for downlink messages, and use a second resource to transmit uplink messages based on timing information determined based on both the downlink and scheduling information. The operation at point 1225 can be performed according to the method described herein. In some examples, aspects of the operation at point 1225 can be determined as described in reference... Figures 7 to 10 The message transmitter described is used to execute.

[0217] Figure 13A flowchart illustrating a method 1300 for supporting joint shared channel allocation in DCI according to various aspects of this disclosure is shown. Operation of method 1300 can be implemented by a UE 115 or base station 105, or components of UE 115 or base station 105, as described herein. For example, operation of method 1300 can be implemented by, as described in reference... Figures 7 to 10 The described communication manager is used for execution. In some examples, the UE can execute a set of instructions to control the UE's functional units to perform the functions described herein. Alternatively, the UE can use dedicated hardware to perform aspects of the functions described herein.

[0218] At 1305, the UE can receive a control message (e.g., a joint control message) from the base station. This control message includes scheduling information for downlink messages to be received by the UE and uplink messages to be transmitted by the UE. This scheduling information allocates a first resource for downlink messages and a second resource for uplink messages. In some examples, the first resource may at least partially overlap with the second resource in at least one of time or frequency.

[0219] In some examples, the base station may send a control message to the UE, which includes scheduling information for downlink messages to be sent by the base station and uplink messages to be received by the base station. The scheduling information allocates a first resource for downlink messages, which at least partially overlaps with a second resource for uplink messages in at least one of time or frequency.

[0220] The operation of 1305 can be performed according to the method described in this article. In some examples, aspects of the operation of 1305 can be derived from, as shown in the reference... Figures 7 to 10 The described joint control receiver is used to perform this.

[0221] At 1310, the UE can receive from the base station a message indicating an incremental symbol value associated with timing information used for uplink messages, wherein the message is received via RRC signaling, MAC-CE, or DCI.

[0222] In some examples, the base station may send a message to the UE indicating an incremental symbol value associated with timing information used for uplink messages, wherein the message is sent via RRC signaling, MAC-CE, or DCI.

[0223] The operation of 1310 can be performed according to the method described in this article. In some examples, aspects of the operation of 1310 can be derived from, as shown in the reference... Figures 7 to 10 The incremental receiver described is used to perform this.

[0224] At point 1315, the UE can determine the timing information for downlink messages based on scheduling information. The operation at point 1315 can be performed according to the method described herein. In some examples, aspects of the operation at point 1315 can be determined as described in reference... Figures 7 to 10 The downlink timing component is described and executed.

[0225] At 1320, the UE can determine the timing information for the uplink message based on the timing and scheduling information used for the downlink message. The operation at 1320 can be performed according to the method described herein. In some examples, aspects of the operation at 1320 can be determined as described in reference... Figures 7 to 10 The uplink timing component described is used for execution.

[0226] At point 1325, the UE can use a first resource to receive downlink messages based on timing information determined based on scheduling information for downlink messages, and use a second resource to transmit uplink messages based on timing information determined based on both the downlink and scheduling information. The operation at point 1325 can be performed according to the method described herein. In some examples, aspects of the operation at point 1325 can be determined as described in reference... Figures 7 to 10 The message transmitter described is used to execute.

[0227] Figure 14 A flowchart illustrating a method 1400 for supporting joint shared channel allocation in DCI according to various aspects of this disclosure is shown. Operation of method 1400 can be implemented by a UE 115 or base station 105, or components of UE 115 or base station 105, as described herein. For example, operation of method 1400 can be implemented by, as described in reference... Figures 7 to 10 The described communication manager is used for execution. In some examples, the UE can execute a set of instructions to control the UE's functional units to perform the functions described herein. Alternatively, the UE can use dedicated hardware to perform aspects of the functions described herein.

[0228] At point 1405, the UE can receive a control message (e.g., a joint control message) from the base station. This control message includes scheduling information for downlink messages to be received by the UE and uplink messages to be transmitted by the UE. This scheduling information allocates a first resource for downlink messages and a second resource for uplink messages. In some examples, the first resource may at least partially overlap with the second resource in at least one of time or frequency.

[0229] In some examples, the base station may send a control message to the UE, which includes scheduling information for downlink messages to be sent by the base station and uplink messages to be received by the base station. The scheduling information allocates a first resource for downlink messages, which at least partially overlaps with a second resource for uplink messages in at least one of time or frequency.

[0230] The operation of 1405 can be performed according to the method described in this article. In some examples, aspects of the operation of 1405 can be derived from, as shown in the reference... Figures 7 to 10 The described joint control receiver is used to perform this.

[0231] At 1410, the UE can receive from the base station a message indicating an incremental timeslot value associated with timing information used for uplink messages, wherein the message is received via RRC signaling, MAC-CE, or DCI.

[0232] In some examples, the base station may send a message to the UE indicating an incremental timeslot value associated with timing information used for uplink messages, wherein the message is sent via RRC signaling, MAC-CE, or DCI.

[0233] The operation of 1410 can be performed according to the method described in this article. In some examples, aspects of the operation of 1410 can be derived from, as referenced... Figures 7 to 10 The incremental receiver described is used to perform this.

[0234] At point 1415, the UE can determine the timing information for downlink messages based on scheduling information. The operation at point 1415 can be performed according to the method described herein. In some examples, aspects of the operation at point 1415 can be determined by, as referenced... Figures 7 to 10 The downlink timing component is described and executed.

[0235] At 1420, the UE can determine the timing information for the uplink message based on the timing and scheduling information used for the downlink message. The operation at 1420 can be performed according to the method described herein. In some examples, aspects of the operation at 1420 can be determined as described in reference... Figures 7 to 10 The uplink timing component described is used for execution.

[0236] At 1425, the UE can determine the time slot for uplink message transmission based on the start symbol, incremental time slot value, and ratio used for downlink messages, where the ratio is based on the first subcarrier spacing for uplink messages and the second subcarrier spacing for downlink messages. Operation 1425 can be performed according to the method described herein. In some examples, aspects of operation 1425 can be determined as referenced... Figures 7 to 10 The time slot manager described is used to execute this.

[0237] At 1430, the UE can use a first resource to receive downlink messages based on timing information for downlink messages determined based on scheduling information, and use a second resource to transmit uplink messages based on timing information for uplink messages determined based on both the downlink and scheduling information. The operation at 1430 can be performed according to the method described herein. In some examples, aspects of the operation at 1430 can be determined by referring to... Figures 7 to 10 The message transmitter described is used to execute.

[0238] Figure 15 A flowchart illustrating a method 1500 for supporting joint shared channel allocation in DCI according to various aspects of this disclosure is shown. Operation of method 1500 can be implemented by a UE 115 or base station 105, or components of UE 115 or base station 105, as described herein. For example, operation of method 1500 can be implemented by, as described in reference... Figures 7 to 10 The described communication manager is used for execution. In some examples, the UE can execute a set of instructions to control the UE's functional units to perform the functions described herein. Alternatively, the UE can use dedicated hardware to perform aspects of the functions described herein.

[0239] At point 1505, the UE can receive a control message (e.g., a joint control message) from the base station. This control message includes scheduling information for downlink messages to be received by the UE and uplink messages to be transmitted by the UE. This scheduling information allocates a first resource for downlink messages and a second resource for uplink messages. In some examples, the first resource may at least partially overlap with the second resource in at least one of time or frequency.

[0240] In some examples, the base station may send a control message to the UE, which includes scheduling information for downlink messages to be sent by the base station and uplink messages to be received by the base station. The scheduling information allocates a first resource for downlink messages, which at least partially overlaps with a second resource for uplink messages in at least one of time or frequency.

[0241] The operation of 1505 can be performed according to the method described in this article. In some examples, aspects of the operation of 1505 can be derived from, as shown in the reference... Figures 7 to 10 The described joint control receiver is used to perform this.

[0242] At point 1510, the UE can determine timing information for downlink messages based on scheduling information. The operation at point 1510 can be performed according to the method described herein. In some examples, aspects of the operation at point 1510 can be determined by referring to... Figures 7 to 10The downlink timing component is described and executed.

[0243] At point 1515, the UE can determine the timing information for uplink messages based on the timing and scheduling information used for downlink messages. The operation at point 1515 can be performed according to the method described herein. In some examples, aspects of the operation at point 1515 can be determined as described in reference... Figures 7 to 10 The uplink timing component described is used for execution.

[0244] At 1520, the UE can transmit uplink messages to the base station based on the timing information used for uplink messages, and transmit downlink messages to the base station based on the timing information used for downlink messages.

[0245] In some examples, the base station can transmit uplink and downlink messages to the UE based on timing information for downlink messages and timing information for uplink messages.

[0246] The operation of 1520 can be performed according to the method described in this article. In some examples, aspects of the operation of 1520 can be derived from, as shown in the reference... Figures 7 to 10 The message transmitter described is used to execute.

[0247] Figure 16 A flowchart illustrating a method 1600 for supporting joint shared channel allocation in DCI according to various aspects of this disclosure is shown. Operation of method 1600 can be implemented by a UE 115 or base station 105, or components of UE 115 or base station 105, as described herein. For example, operation of method 1600 can be implemented by, as described in reference... Figures 7 to 10 The described communication manager is used for execution. In some examples, the UE can execute a set of instructions to control the UE's functional units to perform the functions described herein. Alternatively, the UE can use dedicated hardware to perform aspects of the functions described herein.

[0248] At point 1605, the UE can receive a control message (e.g., a joint control message) from the base station. This control message includes scheduling information for downlink messages to be received by the UE and uplink messages to be transmitted by the UE. This scheduling information allocates a first resource for downlink messages and a second resource for uplink messages. In some examples, the first resource may at least partially overlap with the second resource in at least one of time or frequency.

[0249] In some examples, the base station may send a control message to the UE, which includes scheduling information for downlink messages to be sent by the base station and uplink messages to be received by the base station. The scheduling information allocates a first resource for downlink messages, which at least partially overlaps with a second resource for uplink messages in at least one of time or frequency.

[0250] The operation 1605 can be performed according to the method described in this article. In some examples, aspects of the operation 1605 can be derived from, as shown in the reference... Figures 7 to 10 The described joint control receiver is used to perform this.

[0251] At 1610, the UE can receive from the base station a message including a length indicator for uplink message transmission, wherein the message is received via RRC signaling, MAC-CE, or DCI.

[0252] In some examples, the base station may send a message to the UE that includes a length indicator for receiving uplink messages, wherein the message is sent via RRC signaling, MAC-CE, or DCI.

[0253] The operations of 1610 can be performed according to the methods described in this article. In some examples, aspects of the operations of 1610 can be derived from, as referenced... Figures 7 to 10 The length manager described is used to perform this.

[0254] At step 1615, the UE can determine the timing information for downlink messages based on scheduling information. The operation at step 1615 can be performed according to the method described herein. In some examples, aspects of the operation at step 1615 can be determined as described in reference... Figures 7 to 10 The downlink timing component is described and executed.

[0255] At 1620, the UE can determine the timing information for the uplink message based on the timing and scheduling information used for the downlink message. The operation at 1620 can be performed according to the method described herein. In some examples, aspects of the operation at 1620 can be determined as described in reference... Figures 7 to 10 The uplink timing component described is used for execution.

[0256] At point 1625, the UE can determine the symbol length for the uplink message based on the length indicator. The operation at point 1625 can be performed according to the method described herein. In some examples, aspects of the operation at point 1625 can be determined by reference to... Figures 7 to 10 The length manager described is used to perform this.

[0257] At 1630, the UE can send uplink messages based on the determined symbol length.

[0258] In some examples, the base station can receive uplink messages based on the symbol length.

[0259] The operation of 1630 can be performed according to the method described in this article. In some examples, aspects of the operation of 1630 can be derived from, as referenced... Figures 7 to 10 The message transmitter described is used to execute.

[0260] Figure 17 A flowchart illustrating a method 1700 for supporting joint shared channel allocation in DCI according to various aspects of this disclosure is shown. Operation of method 1700 can be implemented by a UE 115 or base station 105, or components of UE 115 or base station 105, as described herein. For example, operation of method 1700 can be implemented by, as referred to... Figures 7 to 10 The described communication manager is used for execution. In some examples, the UE can execute a set of instructions to control the UE's functional units to perform the functions described herein. Alternatively, the UE can use dedicated hardware to perform aspects of the functions described herein.

[0261] At 1705, the UE can receive a control message (e.g., a joint control message) from the base station. This control message includes scheduling information for downlink messages to be received by the UE and uplink messages to be transmitted by the UE. This scheduling information allocates a first resource for downlink messages and a second resource for uplink messages. In some examples, the first resource may at least partially overlap with the second resource in at least one of time or frequency.

[0262] In some examples, the base station may send a control message to the UE, which includes scheduling information for downlink messages to be sent by the base station and uplink messages to be received by the base station. The scheduling information allocates a first resource for downlink messages, which at least partially overlaps with a second resource for uplink messages in at least one of time or frequency.

[0263] The operation of 1705 can be performed according to the method described in this article. In some examples, aspects of the operation of 1705 can be derived from, as referenced... Figures 7 to 10 The described joint control receiver is used to perform this.

[0264] At 1710, the UE can determine the timing information for downlink messages based on scheduling information. The operation at 1710 can be performed according to the method described herein. In some examples, aspects of the operation at 1710 can be determined by referring to... Figures 7 to 10 The downlink timing component is described and executed.

[0265] At point 1715, the UE can determine the timing information for uplink messages based on the timing and scheduling information used for downlink messages. The operation at point 1715 can be performed according to the method described herein. In some examples, aspects of the operation at point 1715 can be determined as described in reference... Figures 7 to 10 The uplink timing component described is used for execution.

[0266] At point 1720, the UE can determine the duplicate index based on scheduling information. The operation at point 1720 can be performed according to the method described herein. In some examples, aspects of the operation at point 1720 can be determined by referring to... Figures 7 to 10 The described repeat manager is used to execute.

[0267] At point 1725, the UE can determine the number of repetitions for uplink messages based on the repetition index. The operation at point 1725 can be performed according to the method described herein. In some examples, aspects of the operation at point 1725 can be determined by referring to... Figures 7 to 10 The described repeat manager is used to execute.

[0268] At 1730, the UE can transmit uplink messages to the base station based on the timing information used for uplink messages, and transmit downlink messages to the base station based on the timing information used for downlink messages.

[0269] In some examples, the base station can transmit uplink and downlink messages to the UE based on timing information for downlink messages and timing information for uplink messages.

[0270] The operation of 1730 can be performed according to the method described in this article. In some examples, aspects of the operation of 1730 can be derived from, as referenced... Figures 7 to 10 The message transmitter described is used to execute.

[0271] Figure 18 A flowchart illustrating a method 1800 for supporting joint shared channel allocation in DCI according to various aspects of this disclosure is shown. Operation of method 1800 can be implemented by a UE 115 or base station 105, or components of UE 115 or base station 105, as described herein. For example, operation of method 1800 can be implemented by, as described in reference... Figures 7 to 10 The described communication manager is used for execution. In some examples, the UE can execute a set of instructions to control the UE's functional units to perform the functions described herein. Alternatively, the UE can use dedicated hardware to perform aspects of the functions described herein.

[0272] At position 1805, the UE can receive a control message (e.g., a joint control message) from the base station. This control message includes scheduling information for downlink messages to be received by the UE and uplink messages to be transmitted by the UE. This scheduling information allocates a first resource for downlink messages and a second resource for uplink messages. In some examples, the first resource may at least partially overlap with the second resource in at least one of time or frequency.

[0273] In some examples, the base station may send a control message to the UE, which includes scheduling information for downlink messages to be sent by the base station and uplink messages to be received by the base station. The scheduling information allocates a first resource for downlink messages, which at least partially overlaps with a second resource for uplink messages in at least one of time or frequency.

[0274] The operation of 1805 can be performed according to the method described in this article. In some examples, aspects of the operation of 1805 can be derived from, as referenced... Figures 7 to 10 The described joint control receiver is used to perform this.

[0275] At point 1810, the UE can determine timing information for downlink messages based on scheduling information. The operation at point 1810 can be performed according to the method described herein. In some examples, aspects of the operation at point 1810 can be determined by, as referenced... Figures 7 to 10 The downlink timing component is described and executed.

[0276] At point 1815, the UE can determine the timing information for the uplink message based on the timing and scheduling information used for the downlink message. The operation at point 1815 can be performed according to the method described herein. In some examples, aspects of the operation at point 1815 can be determined as described in reference... Figures 7 to 10 The uplink timing component described is used for execution.

[0277] At 1820, the UE can transmit uplink and downlink messages with the base station via the same carrier based on scheduling information.

[0278] In some examples, the base station can transmit uplink and downlink messages to the UE via the same carrier based on scheduling information.

[0279] The operation of 1820 can be performed according to the method described in this article. In some examples, aspects of the operation of 1820 can be derived from, as referenced... Figures 7 to 10 The message transmitter described is used to execute.

[0280] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods can be combined.

[0281] The following provides an overview of the various aspects of this disclosure:

[0282] Aspect 1: A method for wireless communication at a UE, comprising: receiving a control message from a base station, the control message including the scheduling information for the downlink message to be received by the UE and the uplink message to be transmitted by the UE, the scheduling information allocating a first resource for the downlink message and a second resource for the uplink message; using the first resource to receive the downlink message according to timing information for the downlink message determined at least in part based on the scheduling information; and using the second resource to transmit the uplink message according to the timing information for the downlink message and the timing information for the uplink message determined at least in part based on the timing information for the downlink message and the scheduling information.

[0283] Aspect 2: The method according to aspect 1 further includes: determining, at least in part, the start symbol, length value, slot offset, mapping type, or any combination thereof for the downlink message based on the time-domain resource allocation field of the control message.

[0284] Aspect 3: The method according to any of Aspects 1 to 2 further includes: receiving from the base station a message indicating an incremental symbol value associated with the timing information for the uplink message, wherein the message is received via RRC signaling, MAC control element (MAC-CE), or DCI.

[0285] Aspect 4: The method according to aspect 3 further includes: determining the start symbol for the uplink message based at least in part on the start symbol of the downlink message and the increment symbol value.

[0286] Aspect 5: The method according to any of aspects 3 to 4 further includes: determining the starting symbol for the uplink message based at least in part on the incremental symbol value and the symbol in which the control message is received during the monitoring period.

[0287] Aspect 6: The method according to any of Aspects 3 to 5, wherein the message comprises a set of incremental symbol values, and wherein the method further comprises: selecting the incremental symbol value from the set of incremental symbol values ​​based at least in part on the scheduling information.

[0288] Aspect 7: The method according to any of aspects 1 to 6 further comprises: receiving from the base station a message indicating an incremental timeslot value associated with the timing information for the uplink message, wherein the message is received via RRC signaling, MAC-CE, or DCI.

[0289] Aspect 8: The method according to aspect 7 further includes: determining a time slot for transmitting the uplink message based at least in part on the start symbol for the downlink message, the incremental time slot value, and a ratio, the ratio being at least in part based on a first subcarrier interval for the uplink message and a second subcarrier interval for the downlink message.

[0290] Aspect 9: The method according to any of Aspects 7 to 8 further comprises: determining, at least in part, a time slot for transmitting the uplink message based on the time slot scheduled for the downlink message and the incremental time slot value.

[0291] Aspect 10: The method according to any of aspects 1 to 9 further includes: determining a set of time resources for transmitting the uplink message based at least in part on the timing information for the downlink message; applying a timing advance of the UE for transmitting the uplink message based at least in part on the time resource set; and transmitting the uplink message according to the time resource set and the applied timing advance.

[0292] Aspect 11: The method according to any of aspects 1 to 10 further includes: determining a set of time resources for transmitting the uplink message based at least in part on timing information for the downlink message or timing information for the uplink message, the set of time resources being aligned with a set of downlink symbols; and transmitting the uplink message via the set of time resources.

[0293] Aspect 12: The method according to any of aspects 1 to 11 further includes: determining the symbol length for transmission of the uplink message based at least in part on the start symbol of the uplink message.

[0294] Aspect 13: The method according to any of aspects 1 to 12 further comprises: receiving from the base station a message including a length indicator for transmission of the uplink message, wherein the message is received via RRC signaling, MAC-CE, or DCI; determining a symbol length for the uplink message based at least in part on the length indicator; and transmitting the uplink message according to the determined symbol length.

[0295] Aspect 14: The method according to aspect 13, wherein the length indicator includes a set of symbol lengths, and wherein determining the symbol length for the uplink message includes: selecting the symbol length from the set of symbol lengths based at least in part on the scheduling information.

[0296] Aspect 15: The method according to any of aspects 1 to 14 further includes: determining a reference signal mapping type for the uplink message based at least in part on a portion of the scheduling information of the control message.

[0297] Aspect 16: The method according to aspect 15 further includes: determining, at least in part, that the reference signal mapping type is a type A mapping based on the start symbol and symbol length of the uplink message.

[0298] Aspect 17: The method according to any of aspects 1 to 16 further includes: determining a duplication index based at least in part on the scheduling information; and determining the number of duplications for the uplink message based at least in part on the duplication index.

[0299] Aspect 18: The method according to aspect 17 further includes: determining the number of repetitions for the downlink message based at least in part on the scheduling information; and determining the number of repetitions for the uplink message based at least in part on the number of repetitions of the downlink message.

[0300] Aspect 19: The method according to aspect 18 further includes: determining the number of repetitions for the uplink message based at least in part on the number of repetitions and the increment value for the downlink message.

[0301] Aspect 20: The method according to any of aspects 17 to 19 further comprises: receiving from the base station a message including the duplicate index, wherein the message is received via RRC signaling.

[0302] Aspect 21: The method according to any of aspects 1 to 20 further includes: transmitting the uplink message and the downlink message to the base station via the same carrier, at least in part based on the scheduling information.

[0303] Aspect 22: The method according to aspect 21 further includes receiving the control message via a carrier different from the same carrier used for the uplink message and the downlink message.

[0304] Aspect 23: The method according to any of aspects 1 to 22 further includes: determining a first MCS for the downlink message based at least in part on the control message; and determining a second MCS for the uplink message based at least in part on the first MCS for the downlink message.

[0305] Aspect 24: The method according to any of aspects 1 to 23, wherein the first resource at least partially overlaps with the second resource in at least one of time or frequency.

[0306] Aspect 25: An apparatus for wireless communication at a UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to any one of aspects 1 to 24.

[0307] Aspect 26: An apparatus for wireless communication at a UE, comprising at least one unit for performing the method according to any one of aspects 1 to 24.

[0308] Aspect 27: A non-transitory computer-readable medium storing code for wireless communication at a UE, said code including instructions executable by a processor to perform the methods described in any of aspects 1 to 24.

[0309] 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 extensively in the description, the techniques described herein are applicable to areas beyond 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.

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

[0311] The various illustrative 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, discrete hardware component, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller, or state machine. The 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 combined with a DSP core, or any other such configuration).

[0312] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions can be stored as one or more instructions or code on or transmitted via a computer-readable medium. Other examples and implementations are within the scope of this disclosure and the appended 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 being distributed such that different parts of the functions are implemented in different physical locations.

[0313] Computer-readable media include both non-transitory computer storage media and communication media, with communication media encompassing any medium that facilitates the transfer of computer programs from one place to another. Non-transitory storage media can be any available medium accessible by a general-purpose computer or a special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media can 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 capable of carrying or storing desired units of program code 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 typically copy data magnetically, while optical discs use lasers to copy data optically. The combinations described above are also included within the scope of computer-readable media.

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

[0315] 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 a dash followed by a second reference numeral, used to differentiate between similar components. If only the first reference numeral is used in the specification, the description applies to any one of the similar components having the same first reference numeral, without regard to the second reference numeral or other subsequent reference numerals.

[0316] This document describes exemplary configurations with reference to the accompanying drawings, but 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 "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." Detailed descriptions include specific details for the purpose of providing an understanding of the described techniques. However, these techniques may be implemented without these specific details. In some instances, structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

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

Claims

1. A method for wireless communication performed by a user equipment (UE), comprising: The system receives a joint control message, which includes scheduling information for downlink messages for the UE and for uplink shared channel messages transmitted by the UE. The scheduling information allocates a first resource set within a time slot for the downlink messages and a second resource set within the time slot for the uplink shared channel messages, such that the first resource set and the second resource set at least partially overlap in time or frequency, depending on the UE's subband full-duplex capability. The downlink message is received using the first resource set based on the first timing information, wherein the first timing information is at least partially based on the scheduling information; and The uplink shared channel message is sent using the second resource set according to the second timing information, wherein the second timing information is at least partially based on the first timing information and the scheduling information.

2. The method according to claim 1, further comprising: The start symbol, length value, slot offset, or mapping type for the downlink message are determined at least in part based on the time-domain resource allocation field of the joint control message.

3. The method according to claim 1, further comprising: Receive a message from a network device indicating an incremental symbol value associated with the second timing information for the uplink shared channel message, wherein the message is received via Radio Resource Control (RRC) signaling, Medium Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI).

4. The method according to claim 3, further comprising: The start symbol for the uplink shared channel message is determined at least in part based on the start symbol of the downlink message and the increment symbol value.

5. The method according to claim 3, further comprising: The starting symbol for the uplink shared channel message is determined at least in part based on the incremental symbol value and the symbol in which the joint control message is received during the monitoring period.

6. The method according to claim 3, wherein, The message includes a set of incremental symbol values, and the method further includes: The incremental symbol value is selected from the set of incremental symbol values ​​based at least in part on the scheduling information.

7. The method according to claim 1, further comprising: Receive a message from the network device indicating an incremental timeslot value associated with the second timing information for the uplink shared channel message, wherein the message is received via Radio Resource Control (RRC) signaling, Medium Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI).

8. The method according to claim 7, further comprising: The time slots for transmitting the uplink shared channel messages are determined at least in part based on the start symbol for the downlink messages, the incremental time slot value, and a ratio, wherein the ratio is at least in part based on a first subcarrier spacing for the uplink shared channel messages and a second subcarrier spacing for the downlink messages.

9. The method according to claim 7, further comprising: The time slots for transmitting the uplink shared channel messages are determined at least in part based on the time slots scheduled for the downlink messages and the incremental time slot values.

10. The method according to claim 1, further comprising: The set of time resources for transmitting the uplink shared channel message is determined at least in part based on the first timing information for the downlink message; The timing advance for the UE to transmit the uplink shared channel message is applied at least in part based on the set of time resources. as well as The uplink shared channel message is sent based on the set of time resources and the applied timing advance.

11. The method according to claim 1, further comprising: The time resource set for the transmission of the uplink shared channel message is determined at least in part based on the first timing information for the downlink message or the second timing information for the uplink shared channel message, the time resource set being aligned with the downlink symbol set; as well as The uplink shared channel message is sent via the time resource set.

12. The method according to claim 1, further comprising: The symbol length for the transmission of the uplink shared channel message is determined at least in part based on the start symbol of the uplink shared channel message.

13. The method according to claim 1, further comprising: Receive a message from a network device including a length indicator for the transmission of the uplink shared channel message, wherein the message is received via Radio Resource Control (RRC) signaling, Medium Access Control (MAC) control element (MAC-CE), or Downlink Control Information (DCI). The symbol length for the uplink shared channel message is determined at least in part based on the length indicator; and The uplink shared channel message is sent according to the determined symbol length.

14. The method according to claim 13, wherein, The length indicator includes a set of symbol lengths, and wherein determining the symbol length for the uplink shared channel message includes: The symbol length is selected from the set of symbol lengths based at least in part on the scheduling information.

15. The method according to claim 1, further comprising: The reference signal mapping type for the uplink shared channel message is determined at least in part based on a portion of the scheduling information in the joint control message.

16. The method of claim 15, further comprising: The reference signal mapping type is determined to be type A mapping based at least in part on the start symbol and symbol length of the uplink shared channel message.

17. The method according to claim 1, further comprising: The duplicate index is determined at least in part based on the scheduling information; as well as The number of repetitions for the uplink shared channel messages is determined at least in part based on the repetition index.

18. The method of claim 17, further comprising: The number of repetitions for the downlink message is determined at least in part based on the scheduling information; as well as The number of repetitions for the uplink shared channel message is determined at least in part based on the number of repetitions of the downlink message.

19. The method of claim 18, further comprising: The number of repetitions for the uplink shared channel message is determined at least in part based on the number of repetitions and the increment value for the downlink message.

20. The method of claim 17, further comprising: Receive a message including the duplicate index from a network device, wherein the message is received via Radio Resource Control (RRC) signaling.

21. The method according to claim 1, further comprising: The uplink shared channel messages and the downlink messages are transmitted via the same carrier and network devices, at least in part based on the scheduling information.

22. The method of claim 21, further comprising: The joint control message is received via a carrier different from the same carrier used for the uplink shared channel message and the downlink message.

23. The method according to claim 1, further comprising: The first modulation and coding scheme (MCS) for the downlink message is determined at least in part based on the joint control message; as well as The second MCS for the uplink shared channel message is determined at least in part based on the first MCS for the downlink message.

24. An apparatus for wireless communication at a user equipment (UE), comprising: Memory; as well as At least one processor coupled to the memory, wherein the at least one processor is configured to perform the following operations: The system receives a joint control message, which includes scheduling information for downlink messages for the UE and uplink shared channel messages transmitted by the UE, wherein the scheduling information allocates a first resource set within a time slot for the downlink messages and a second resource set within the time slot for the uplink shared channel messages, such that the first resource set and the second resource set at least partially overlap in time or frequency according to the subband full-duplex capability of the UE. The downlink message is received via the first resource set according to first timing information, wherein the first timing information is at least partially based on the scheduling information; and The uplink shared channel message is transmitted via the second resource set according to the second timing information, wherein the second timing information is at least partially based on the first timing information and the scheduling information.

25. The apparatus according to claim 24, wherein, The at least one processor is configured to perform the following operations: The start symbol, length value, slot offset, or mapping type for the downlink message are determined at least in part based on the time-domain resource allocation field of the joint control message.

26. The apparatus according to claim 24, wherein, The at least one processor is configured to perform the following operations: Receive a message from a network device indicating an incremental symbol value associated with the second timing information for the uplink shared channel message, wherein the message is received via Radio Resource Control (RRC) signaling, Medium Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI).

27. The apparatus according to claim 26, wherein, The at least one processor is configured to perform the following operations: The start symbol for the uplink shared channel message is determined based on the start symbol of the downlink message and the increment symbol value.

28. The apparatus according to claim 26, wherein, The at least one processor is configured to perform the following operations: The starting symbol for the uplink shared channel message is determined at least in part based on the incremental symbol value and the symbol in which the joint control message is received during the monitoring period.

29. The apparatus according to claim 26, wherein, The message includes a set of incremental symbol values, and wherein the at least one processor is configured to perform the following operations: The incremental symbol value is selected from the set of incremental symbol values ​​based at least in part on the scheduling information.

30. The apparatus according to claim 24, wherein, The at least one processor is configured to perform the following operations: Receive a message from the network device indicating an incremental timeslot value associated with the second timing information for the uplink shared channel message, wherein the message is received via Radio Resource Control (RRC) signaling, Medium Access Control (MAC) Control Element (MAC-CE), or Downlink Control Information (DCI).

31. The apparatus according to claim 30, wherein, The at least one processor is configured to perform the following operations: The time slots for transmitting the uplink shared channel messages are determined at least in part based on the start symbol for the downlink messages, the incremental time slot value, and a ratio, wherein the ratio is at least in part based on a first subcarrier spacing for the uplink shared channel messages and a second subcarrier spacing for the downlink messages.

32. The apparatus according to claim 30, wherein, The at least one processor is configured to perform the following operations: The time slots for transmitting the uplink shared channel messages are determined at least in part based on the time slots scheduled for the downlink messages and the incremental time slot values.

33. The apparatus according to claim 24, wherein, The at least one processor is configured to perform the following operations: The set of time resources for transmitting the uplink shared channel message is determined at least in part based on the first timing information for the downlink message; The timing advance for the UE to transmit the uplink shared channel message is applied at least in part based on the set of time resources. as well as The uplink shared channel message is sent based on the set of time resources and the applied timing advance.

34. The apparatus according to claim 24, wherein, The at least one processor is configured to perform the following operations: The time resource set for the transmission of the uplink shared channel message is determined at least in part based on the first timing information for the downlink message or the second timing information for the uplink shared channel message, the time resource set being aligned with the downlink symbol set; as well as The uplink shared channel message is sent via the time resource set.

35. The apparatus according to claim 24, wherein, The at least one processor is configured to perform the following operations: The symbol length for the transmission of the uplink shared channel message is determined at least in part based on the start symbol of the uplink shared channel message.

36. The apparatus according to claim 24, wherein, The at least one processor is configured to perform the following operations: Receive a message from a network device including a length indicator for the transmission of the uplink shared channel message, wherein the message is received via Radio Resource Control (RRC) signaling, Medium Access Control (MAC) control element (MAC-CE), or Downlink Control Information (DCI). The symbol length for the uplink shared channel message is determined at least in part based on the length indicator; and The uplink shared channel message is sent according to the determined symbol length.

37. The apparatus according to claim 36, wherein, The length indicator includes a set of symbol lengths, and wherein, in order to determine the symbol length for the uplink shared channel message, the at least one processor is configured to perform the following operations: The symbol length is selected from the set of symbol lengths based at least in part on the scheduling information.

38. The apparatus according to claim 24, wherein, The at least one processor is configured to perform the following operations: The reference signal mapping type for the uplink shared channel message is determined at least in part based on a portion of the scheduling information in the joint control message.

39. The apparatus according to claim 38, wherein, The at least one processor is configured to perform the following operations: The reference signal mapping type is determined to be type A mapping based at least in part on the start symbol and symbol length of the uplink shared channel message.

40. The apparatus according to claim 24, wherein, The at least one processor is configured to perform the following operations: The duplicate index is determined at least in part based on the scheduling information; and The number of repetitions for the uplink shared channel messages is determined at least in part based on the repetition index.

41. The apparatus according to claim 40, wherein, The at least one processor is configured to perform the following operations: The number of repetitions for the downlink message is determined at least in part based on the scheduling information; and The number of repetitions for the uplink shared channel message is determined at least in part based on the number of repetitions of the downlink message.

42. The apparatus according to claim 41, wherein, The at least one processor is configured to perform the following operations: The number of repetitions for the uplink shared channel message is determined at least in part based on the number of repetitions and the increment value for the downlink message.

43. The apparatus according to claim 40, wherein, The at least one processor is configured to perform the following operations: Receive a message including the duplicate index from a network device, wherein the message is received via Radio Resource Control (RRC) signaling.

44. The apparatus according to claim 24, wherein, The at least one processor is configured to perform the following operations: The uplink shared channel messages and the downlink messages are transmitted via the same carrier and network devices, at least in part based on the scheduling information.

45. The apparatus according to claim 44, wherein, The at least one processor is configured to perform the following operations: The joint control message is received via a carrier different from the same carrier used for the uplink shared channel message and the downlink message.

46. ​​The apparatus according to claim 24, wherein, The at least one processor is configured to perform the following operations: The first modulation and coding scheme (MCS) for the downlink messages is determined at least in part based on the joint control messages; and The second MCS for the uplink shared channel message is determined at least in part based on the first MCS for the downlink message.

Images