Default Beam Configuration Selection for Uplink Transmission

Abstract

Methods, systems, and devices for wireless communications are described. Generally, a user equipment (UE) may receive downlink control information (DCI) from a base station indicating a set of code points corresponding to a set of beam configurations and including an uplink grant. The UE may select a code point from a set of code points corresponding to a default uplink beam for transmitting an uplink message based at least in part on a beam configuration selection criterion indicating a criterion for selecting a subset of valid beam configurations from the set of beam configurations. The UE may transmit a scheduled uplink message according to the uplink grant using the default uplink beam.

Description

Technical Field

[0001]

[0001] The following relates to wireless communication, including default beam configuration selection for uplink transmission.

Background Art

[0002]

[0002] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, etc. These systems may be capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multi-connection systems include fourth-generation (4G) systems such as Long-Term Evolution (LTE (registered trademark)) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth-generation (5G) systems sometimes referred to as New Radio (NR) systems. These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multi-connection communication system may include one or more base stations or one or more network access nodes that each simultaneously support communication for a plurality of communication devices, sometimes known as user equipment (UE).

Summary of the Invention

[0003]

[0003] The techniques described relate to an improved method, system, device, and apparatus for supporting default beam configuration selection for uplink transmission. Generally, a user equipment (UE) may identify a default uplink beam (e.g., a default uplink transmission configuration indicator (TCI) state) for transmitting a scheduled uplink message based on a code point of a TCI indication included in a downlink control information (DCI) message. The DCI message may include a TCI field that may indicate a single TCI state or a pair of TCI states. Some of the indicated TCI states or pairs of TCI states may include an uplink beam (e.g., an uplink TCI state or a common downlink / uplink TCI state). Accordingly, a TCI state code point that includes or indicates an uplink beam may be considered a valid code point. The UE may determine which TCI state code points are valid based on beam configuration (e.g., TCI state) selection criteria.

[0004]

[0004] The beam configuration selection criteria may include one or more rules regarding which beam configuration or how many beam configurations are considered to be valid. In some examples, the beam configuration selection criteria may further include one or more rules for selecting or utilizing one or more valid TCI states from a set of valid TCI states. Among the various TCI state code points included in the TCI field, a subset of the code points may be considered valid code points (for example, a valid code point may indicate or include an uplink beam). The UE may select a code point from the set of valid code points and use the uplink beam associated with the selected valid code point as the default uplink beam for transmitting the scheduled uplink message. In some examples, a single default beam may be considered valid based on a default TCI code point (for example, a pair of TCI states may not be considered valid). In some examples, two default beams may be considered valid based on the default TCI code points indicating both beams (for example, a pair of TCI states may be considered valid). In some examples, the scheduling DCI may not include one or more TCI state code points, and the UE may determine the default uplink beam based on different DCI messages (for example, the most recently received DCI message) that meet one or more rules or conditions.

[0005]

[0005] A method for wireless communication in a user equipment (UE) is described. The method may include receiving, from a base station, downlink control information including an uplink grant for a physical uplink shared channel; selecting a code point from a set of code points corresponding to a default uplink beam for transmitting an uplink message on the physical uplink shared channel based on a beam configuration selection criterion indicating a criterion for selecting a subset of valid beam configurations from a set of beam configurations, where the downlink control information indicates the set of code points corresponding to the set of beam configurations; and transmitting the uplink message on the physical uplink shared channel in accordance with the uplink grant using the default uplink beam.

[0006]

[0006] An apparatus for wireless communication in 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, from a base station, downlink control information including an uplink grant for a physical uplink shared channel; select a code point from a set of code points corresponding to a default uplink beam for transmitting an uplink message on the physical uplink shared channel based on a beam configuration selection criterion indicating a criterion for selecting a subset of valid beam configurations from a set of beam configurations, where the downlink control information indicates the set of code points corresponding to the set of beam configurations; and transmit the uplink message on the physical uplink shared channel in accordance with the uplink grant using the default uplink beam.

[0007] Another apparatus for wireless communication in a UE is described. The apparatus may include means for receiving, from a base station, downlink control information including an uplink grant for a physical uplink shared channel; means for selecting, based on a beam configuration selection criterion indicating a criterion for selecting a subset of valid beam configurations from a set of beam configurations, a code point from a set of code points corresponding to a default uplink beam for transmitting an uplink message on the physical uplink shared channel, where the downlink control information indicates a set of code points corresponding to a set of beam configurations; and means for transmitting an uplink message on the physical uplink shared channel in accordance with the uplink grant using the default uplink beam.

[0008] A non-transitory computer-readable medium storing code for wireless communication in a UE is described. The code may include instructions executable by a processor to receive, from a base station, downlink control information including an uplink grant for a physical uplink shared channel; select, based on a beam configuration selection criterion indicating a criterion for selecting a subset of valid beam configurations from a set of beam configurations, a code point from a set of code points corresponding to a default uplink beam for transmitting an uplink message on the physical uplink shared channel, where the downlink control information indicates a set of code points corresponding to a set of beam configurations; and transmit an uplink message on the physical uplink shared channel in accordance with the uplink grant using the default uplink beam.

[0009] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for comparing code point identifiers of code points corresponding to a subset of valid beam configurations, where selecting a code point from a set of code points may be based on an order of the code point identifiers being compared.

[0010]

[0010] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for selecting a subset of valid beam configurations based on beam configuration selection criteria, where the beam configuration selection criteria include a restriction of the subset of valid beam configurations to beam configurations having a single uplink beam option.

[0011]

[0011] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for selecting a subset of valid beam configurations based on beam configuration selection criteria, where the beam configuration selection criteria include a restriction of the subset of valid beam configurations to beam configurations having a single uplink beam option, multiple uplink beam options, or both.

[0012]

[0012] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for applying rules indicated in the beam configuration selection criteria, where the rules include an indication of which of multiple uplink beam options to select for transmitting an uplink message, and where selecting a code point from a set of code points may be based on applying the rules.

[0013]

[0013] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for selecting a second code point from a set of code points corresponding to a second default uplink beam of a subset of valid beam configurations based on beam configuration selection criteria.

[0014]

[0014] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, transmitting an uplink message may include operations, features, means, or instructions for transmitting a first repetition of the uplink message using a default uplink beam and transmitting a second repetition of the uplink message using a second default uplink beam.

[0015]

[0015] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving, in downlink control information, a beam switching indication indicating which of a plurality of uplink beam options to select for transmitting an uplink message, where selecting a code point from a set of code points may be based on receiving the beam switching indication.

[0016]

[0016] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving downlink control information may include operations, features, means, or instructions for receiving a first downlink control information message including an uplink grant for a physical uplink shared channel and receiving a second downlink control information message including a set of code points before receiving the first downlink control information message.

[0017] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for comparing a first control resource set pool index associated with a first downlink control information message with a second control resource set pool index associated with a second downlink control information message, and determining, based on the comparison, that the first control resource set pool index and the second control resource set pool index may be the same, where selecting a code point may be based on the first control resource set pool index and the second control resource set pool index being the same.

[0018] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for determining that a time period between receiving a second downlink control information message and receiving a first downlink control information message meets a threshold timing gap, where selecting a code point may be based on the determination.

[0019] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, at least one of the first downlink control information message or the second downlink control information message includes a group common downlink control information message.

[0020] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving, from a base station, an indication of a threshold timing gap, where determining that the time period meets the threshold timing gap may be based on receiving the indication of the threshold timing gap.

[0021]

[0021] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for comparing a first time offset value to a second time offset value and selecting the first time offset value based on the comparison, where the first time offset value includes a threshold timing gap, and where determining that a time period meets the threshold timing gap may be based on selecting the first time offset value.

[0022]

[0022] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving an indication of beam configuration selection criteria from a base station, where selecting a code point may be based on receiving the indication of beam configuration selection criteria.

[0023]

[0023] A method for wireless communication at a base station is described. The method may include transmitting downlink control information, including an uplink grant for a physical uplink shared channel, to a UE, and selecting a default uplink beam for receiving an uplink message on the physical uplink shared channel based on a beam configuration selection criteria indicating criteria for selecting a subset of valid beam configurations from a set of beam configurations, where the downlink control information indicates a set of code points corresponding to the set of beam configurations, and receiving the uplink message on the physical uplink shared channel in accordance with the uplink grant using the default uplink beam.

[0024]

[0024] An apparatus for wireless communication at a base station is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may cause the apparatus to transmit downlink control information including an uplink grant for a physical uplink shared channel to a UE, select a default uplink beam for receiving an uplink message on the physical uplink shared channel based on a beam configuration selection criterion indicating a criterion for selecting a subset of valid beam configurations from a set of beam configurations, where the downlink control information indicates a set of code points corresponding to the set of beam configurations, and receive the uplink message on the physical uplink shared channel according to the uplink grant using the default uplink beam, which may be executable by the processor.

[0025]

[0025] Another apparatus for wireless communication at a base station is described. The apparatus may include means for transmitting downlink control information including an uplink grant for a physical uplink shared channel to a UE, means for selecting a default uplink beam for receiving an uplink message on the physical uplink shared channel based on a beam configuration selection criterion indicating a criterion for selecting a subset of valid beam configurations from a set of beam configurations, where the downlink control information indicates a set of code points corresponding to the set of beam configurations, and means for receiving the uplink message on the physical uplink shared channel according to the uplink grant using the default uplink beam.

[0026] A non-transitory computer-readable medium storing code for wireless communication at a base station is described. The code includes instructions executable by a processor to transmit downlink control information, including an uplink grant for a physical uplink shared channel, to a UE, and to select a default uplink beam for receiving an uplink message on the physical uplink shared channel based on a beam configuration selection criterion indicating a criterion for selecting a subset of valid beam configurations from a set of beam configurations, where the downlink control information indicates a set of code points corresponding to a set of beam configurations. The code may also include instructions to receive the uplink message on the physical uplink shared channel according to the uplink grant using the default uplink beam.

[0027]

[0027] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the beam configuration selection criterion includes a restriction of a subset of valid beam configurations to beam configurations having a single uplink beam option.

[0028]

[0028] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the beam configuration selection criterion includes a restriction of a subset of valid beam configurations to beam configurations having a single uplink beam option, a plurality of uplink beam options, or both.

[0029]

[0029] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, receiving the uplink message may include operations, features, means, or instructions for receiving a first iteration of the uplink message using a default uplink beam associated with a first uplink beam option of a plurality of uplink beam options and receiving a second iteration of the uplink message using a second default uplink beam associated with a second uplink beam option of the plurality of uplink beam options.

[0030]

[0030] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, transmitting downlink control information may include transmitting a first downlink control information message including an uplink grant for a physical uplink shared channel, and transmitting a second downlink control information message including a set of code points, before transmitting the first downlink control information message. It may include operations, features, means, or instructions for doing so.

[0031]

[0031] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving an uplink message on a default uplink beam, based on the first control resource set pool index associated with the first downlink control information message being the same as the second control resource set pool index associated with the second downlink control information message.

[0032]

[0032] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for receiving an uplink message on a default uplink beam, based on the time period between transmitting the second downlink control information message and transmitting the first downlink control information message satisfying a threshold timing gap.

[0033]

[0033] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for transmitting an indication of beam configuration selection criteria to a UE, where receiving an uplink message on a default uplink beam may be based on transmitting the indication of beam configuration selection criteria.

Brief Description of the Drawings

[0034]

Figure 1

Figure 2

[0035] FIG. showing an example of a wireless communication system supporting default beam configuration selection for uplink transmission according to an aspect of the present disclosure.

Figure 3

[0036] FIG. showing an example of a process flow for supporting default beam configuration selection for uplink transmission according to an aspect of the present disclosure.

Figure 4

[0037] FIG. showing an example of a timeline for supporting default beam configuration selection for uplink transmission according to an aspect of the present disclosure.

Figure 5

[0038] FIG. showing an example of a process flow for supporting default beam configuration selection for uplink transmission according to an aspect of the present disclosure.

Figure 6

[0039] Block diagram of a device supporting default beam configuration selection for uplink transmission according to an aspect of the present disclosure.

Figure 7

Figure 8

[0040] Block diagram of a communication manager supporting default beam configuration selection for uplink transmission according to an aspect of the present disclosure.

Figure 9

[0041] FIG. of a system including a device supporting default beam configuration selection for uplink transmission according to an aspect of the present disclosure.

Figure 10

[0042] Block diagram of a device supporting default beam configuration selection for uplink transmission according to an aspect of the present disclosure.

Figure 11

Figure 12

[0043] Block diagram of a communication manager that supports default beam configuration selection for uplink transmission according to an aspect of the present disclosure.

Figure 13

[0044] Diagram of a system including a device that supports default beam configuration selection for uplink transmission according to an aspect of the present disclosure.

Figure 14

[0045] Flowchart showing a method for supporting default beam configuration selection for uplink transmission according to an aspect of the present disclosure.

Figure 15

Figure 16

Figure 17

DETAILED DESCRIPTION OF THE INVENTION

[0035]

[0046] A wireless communication system may support communication via directional beams. In some examples, a base station may configure a user equipment (UE) in one or more transmission configuration indicator (TCI) states. The UE may use different active TCI states to generate uplink beams, receive downlink signaling in downlink beams, or any combination thereof. In some examples, the base station may schedule uplink transmissions and indicate the uplink beam on which the UE is to send an uplink transmission. However, in some examples, an uplink grant (e.g., included in a downlink control information (DCI) message) may not include an explicit indication of the uplink beam on which to send an uplink transmission.

[0036]

[0047] If the uplink beam is not explicitly indicated or not available to the UE for scheduled uplink transmission, the UE may select a default uplink beam (e.g., a default uplink TCI state). For example, some wireless communication systems may support the selection of a default uplink beam that matches the downlink beam on which the downlink reference signal is received (e.g., based on the quasi - co - location (QCL) assumption of the CORESET with the lowest identifier). That is, the UE 115 may select a default uplink beam for uplink transmission that matches the downlink beam of a control resource set (CORESET) or a physical downlink shared channel (PDSCH).

[0037]

[0048] However, in some examples, the downlink beam associated with the CORESET having the lowest identifier may not be associated with the corresponding uplink beam. A unified TCI state may be indicated in the DCI of multiple channels, but may not always include the corresponding pair of uplink and downlink beams. For example, the base station may configure only the downlink beam of a particular CORESET, or may configure one or more downlink beams that do not have a corresponding uplink beam. In such an example, a UE attempting to select a default uplink TCI state while referring to the QCL assumption of a particular CORESET may not be able to identify the uplink TCI state (e.g., the QCL assumption that the CORESET may not correspond to an uplink TCI state). In such an example, the UE may have to determine or identify a new uplink TCI state and the uplink beam on which the scheduled uplink message will be transmitted. This can lead to an increase in UE latency, or a transmission failure (e.g., if the UE does not identify the uplink beam on which the scheduled uplink message will be transmitted before the occurrence of the scheduled uplink resources in the PUSCH), or both. Such latency or transmission failure can lead to an increase in system latency, an increase in congestion, inefficient use of resources, and a reduction in the user experience.

[0038]

[0049] In some examples, the UE may identify a default uplink beam (e.g., a default uplink TCI state) for transmitting an uplink message based on the code point of the TCI indication included in downlink control signaling such as a DCI message. The base station may send a DCI message to the UE. The DCI message may include a TCI field that may indicate a single TCI state or a pair of TCI states. Some of the indicated TCI states or pairs of TCI states may include an uplink beam (e.g., an uplink TCI state or a joint downlink / uplink TCI state). Thus, the TCI state code point that includes or indicates an uplink beam may be considered a valid code point. For example, the TCI field in the received DCI message may include one or more TCI indications. The TCI indication may indicate one or more cases (e.g., a pair of TCI states or a single TCI state, or any combination thereof). Some of the cases indicated (e.g., a single TCI state or a joint TCI state or a pair of TCI states) may be considered valid cases (e.g., may indicate an uplink TCI state or a joint uplink / downlink TCI state where a scheduled uplink transmission can be sent). Some of the cases may be considered invalid cases (e.g., may only include a downlink TCI state or a pair of downlink TCI states). The UE may determine which cases are valid based on beam configuration (e.g., TCI state) selection criteria.

[0039]

[0050] The beam configuration selection criteria may include one or more rules regarding which beam configuration (e.g., case) or how many beam configurations (e.g., cases) are considered valid. In some examples, the beam configuration selection criteria may further include one or more rules for selecting or utilizing one or more valid TCI states out of a set of valid TCI states. In such examples, the UE may determine which of the cases indicated in the TCI field are valid (e.g., exclude one or more invalid cases), and may select a valid code point from a set of one or more valid code points. That is, among the various TCI state code points included in the TCI field, a subset of the code points may be considered valid code points (e.g., the valid code points may indicate an uplink beam). The UE may select a code point from the set of valid code points and use the uplink beam associated with the selected valid code point as the default uplink beam.

[0040]

[0051] In some examples, a single default beam may be considered valid based on a default TCI code point (e.g., a pair of TCI states may not be considered valid). In some examples, two default beams may be considered valid based on the default TCI code points indicating both beams (e.g., a pair of TCI states may be considered valid). In some examples, the scheduling DCI may not include one or more TCI state code points, and the UE may determine the default uplink beam based on different DCI messages (e.g., the most recently received DCI message) that meet one or more rules or conditions.

[0041]

[0052] Aspects of the disclosure are first described in the context of a wireless communication system. The aspects of the disclosure are further illustrated by, and described with reference to, a wireless communication system, a process flow, and a timeline. The aspects of the disclosure are further illustrated by, and described with reference to, apparatus diagrams, system diagrams, and flowcharts related to default beam configuration selection for uplink transmission.

[0042]

[0053] FIG. 1 shows an example of a wireless communication system 100 that supports default beam configuration selection for uplink transmission according to aspects of the present disclosure. 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 LTE-Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some examples, the wireless communication system 100 may support extended broadband communication, ultra-reliable (e.g., mission-critical) communication, low-latency communication, communication using low-cost and low-complexity devices, or any combination thereof.

[0043]

[0054] The base stations 105 may be distributed across a geographical area to form the wireless communication system 100 and may be devices of different forms or with different capabilities. The base stations 105 and the UEs 115 may communicate wirelessly via one or more communication links 125. Each base station 105 may provide a coverage area 110 in which the UEs 115 and the base station 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographical area in which the base stations 105 and the UEs 115 may support signal communication according to one or more radio access technologies.

[0044]

[0055] UE 115 can be distributed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 can be fixed, or mobile, or both at different times. UE 115 can be a device with different forms or different capabilities. Some exemplary UEs 115 are shown in FIG. 1. The UE 115 described herein can communicate with various types of devices, such as other UEs 115, base stations 105, or network devices (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network devices), as shown in FIG. 1.

[0045]

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

[0046]

[0057] One or more of the base stations 105 described herein can include a base transceiver station, 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 giga Node B (any of which may be referred to as a gNB), a home Node B, a home eNode B, or other suitable terms, or may be referred to as such by those skilled in the art.

[0047]

[0058] UE115 may include or may be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or some other suitable term, where "device" may also be referred to as a unit, station, terminal, or client, among other examples. UE115 may also include or may 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, UE115 may include or may be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, any Internet of Everything (IoE) device, or a machine type communication (MTC) device, among other examples, that may be implemented in various objects such as appliances, or vehicles, meters, etc.

[0048]

[0059] As shown in FIG. 1, the UE115 described herein may sometimes act as a relay and may be capable of communicating with various types of devices, including other UE115s that may sometimes act as relays, and, among other examples, base station 105 and network equipment including macro eNB or gNB, small cell eNB or gNB, or relay base stations.

[0049]

[0060] UE115 and base station 105 can wirelessly communicate 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, the carrier used for communication link 125 can include a portion of a radio frequency spectrum band (e.g., a bandwidth part (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel can carry acquisition signaling (e.g., synchronization signals, system information), control signaling that coordinates the operation for the carrier, user data, or other signaling. The wireless communication system 100 can support communication with UE115 using carrier aggregation or multi-carrier operation. UE115 can be composed of a plurality of downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation can be used with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers.

[0050]

[0061] In some examples (e.g., in a carrier aggregation configuration), a carrier can also have acquisition signaling or control signaling that coordinates the operation for other carriers. A carrier can be associated with a frequency channel (e.g., an evolved universal terrestrial radio access (E-UTRA) absolute radio frequency channel number (EARFCN)) and can be arranged according to a channel raster for discovery by UE115. A carrier can operate in a stand-alone mode where initial acquisition and connection can be performed by UE115 via the carrier, or the carrier can operate in a non-stand-alone mode where a connection is established using different carriers (e.g., of the same or different radio access technologies).

[0051]

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

[0052]

[0063] A carrier may be associated with a particular bandwidth of the radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as the "system bandwidth" of the carrier or the wireless communication system 100. For example, the carrier bandwidth may be one of several determined bandwidths (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)) for carriers of a particular radio access technology. Devices of the wireless communication system 100 (e.g., the base station 105, the UE 115, or both) may have a hardware configuration that supports communication on a particular carrier bandwidth or may be configurable to support communication on one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 or a 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 sub-band, a BWP) or all of the carrier bandwidth.

[0053]

[0064] The signal waveform transmitted on a carrier can be composed of multiple subcarriers (e.g., using a multi-carrier modulation (MCM) technique such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system adopting an MCM technique, a resource element can consist of one symbol period (e.g., the duration of one modulated symbol) and one subcarrier, where the symbol period and the 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 higher the number of resource elements received by UE115 and the higher the order of the modulation scheme, the higher the data rate for UE115 can be. Wireless communication resources can refer to a combination of radio frequency spectrum resources, time 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 for communication with UE115.

[0054]

[0065] One or more numerologies can be supported for a carrier, where the numerology can include the subcarrier spacing (Δf) and the cyclic prefix. A carrier can be divided into one or more BWPs having the same or different numerologies. In some examples, UE115 can be composed of multiple BWPs. In some examples, a single BWP for a carrier can be active at a given time, and communication for UE115 can be restricted to one or more active BWPs.

[0055]

[0066] The time interval for the base station 105 or UE115 can be expressed in multiples of a basic time unit, for example, T s = 1 / (Δf max ·N f ) seconds, which can refer to the sampling period, where Δf max can represent the maximum supported subcarrier spacing, and N fmay represent the maximum supported Discrete Fourier Transform (DFT) size. The time intervals of communication resources may be organized according to wireless frames each having a specified duration (e.g., 10 milliseconds (ms)). Each wireless frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0056]

[0067] Each frame may include a plurality of consecutively numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a number of slots. Alternatively, each frame may include a variable number of slots, and the number of slots may depend on the subcarrier spacing. Each slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period). In some wireless communication systems 100, a slot may be further divided into a plurality of minislots each including one or more symbols. Excluding the cyclic prefix, each symbol period may include one or more (e.g., N f ) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or the frequency operating band.

[0057]

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

[0058]

[0069] Physical channels can be multiplexed on a carrier according to various techniques. Physical control channels and physical data channels can be multiplexed on a downlink carrier using, for example, one or more of time-division multiplexing (TDM) techniques, frequency-division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region for a physical control channel (e.g., a control resource set (CORESET)) can be defined by a number of symbol periods and can span the system bandwidth of the carrier or a subset of the system bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more of the UEs 115 can monitor or search a control region for control information according to one or more search space sets, where each search space set can include one or more control channel candidates at one or more aggregation levels configured in a cascaded manner. The aggregation level for a control channel candidate can refer to a number of control channel resources (e.g., control channel elements (CCEs)) associated with the encoded information for a control information format having a given payload size. The search space sets can include a common search space set configured to send control information to a plurality of UEs 115 and a UE-specific search space set for sending control information to a specific UE 115.

[0059]

[0070] Each base station 105 may provide communication coverage via one or more cells, such as 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 for communication with a base station 105 (e.g., on a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or others) for distinguishing neighboring cells. In some examples, a cell may also refer to a geographical coverage area 110 in which the logical communication entity operates or a portion (e.g., a sector) of the geographical coverage area 110. Such cells can range from smaller areas (e.g., structures, subsets of structures) to larger areas depending on various factors such as the capabilities of the base station 105. For example, a cell can be, among other examples, a building, a subset of a building, or an external space that is between or overlaps with the geographical coverage areas 110 or includes them.

[0060]

[0071] A macro cell generally covers a relatively large geographical area (e.g., with a radius of several kilometers) and may enable unrestricted access by UEs 115 subscribed to the services of the network provider that supports the macro cell. A small cell may be associated with a low-power base station 105 compared to a macro cell, and the small cell may operate in the same or a different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to UEs 115 subscribed to the services of the network provider or may provide restricted access to UEs 115 associated with the small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users at home or in the office). The base station 105 may support one or more cells and may also support communication on one or more cells using one or more component carriers.

[0061]

[0072] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), extended mobile broadband (eMBB)) that provide access to different types of devices.

[0062]

[0073] In some examples, base station 105 is mobile and thus may provide communication coverage to a moving geographic coverage area 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 a heterogeneous network in which different types of base stations 105 provide coverage to various geographic coverage areas 110 using, for example, the same or different radio access technologies.

[0063]

[0074] Wireless communication system 100 may support synchronous operation or asynchronous operation. In the case of synchronous operation, base stations 105 may have similar frame timings, and transmissions from different base stations 105 may be temporally approximately aligned. In the case of asynchronous operation, base stations 105 may have different frame timings, and in some examples, transmissions from different base stations 105 may not be temporally aligned. The techniques described herein may be used for either synchronous operation or asynchronous operation.

[0064]

[0075] Some UEs 115, such as MTC devices or IoT devices, can be low-cost or low-complexity devices and can provide automatic communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that enable devices to communicate with each other or with the base station 105 without human intervention. In some examples, M2M communication or MTC incorporates sensors or meters to measure or capture information and relays such information to a central server or application program that utilizes the information, or presents the information to a human who interacts with the application program, and can include communication from the device. Some UEs 115 can be designed to collect information or enable automated 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, weather and geological event monitoring, fleet management and tracking, remote security detection, physical access control, and transaction-based business billing.

[0065]

[0076] Some UEs 115 can be configured to adopt an operating mode that reduces power consumption, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception rather than simultaneous transmission and reception). In some examples, half-duplex communication can be implemented at a reduced peak rate. Other power-saving techniques for UEs 115 include entering a power-saving deep sleep mode when not participating in active communication, operating on a limited bandwidth (e.g., in accordance with narrowband communication), or a combination of these techniques. For example, some UEs 115 can be configured for operation using a narrowband protocol type associated with a defined portion or range within a carrier, within a guard band of the carrier, or outside the carrier (e.g., a set of subcarriers or resource blocks (RBs)).

[0066]

[0077] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC) or mission-critical communication. The UE 115 can be designed to support an ultra-reliable function, a low-latency function, or a critical function (e.g., a mission-critical function). Ultra-reliable communication can include private communication 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 prioritization of services, and mission-critical services can be used for public safety or general commercial use cases. The terms ultra-reliable, low-latency, mission-critical, and ultra-reliable low-latency can be used interchangeably herein.

[0067]

[0078] In some examples, the UE 115 may also be able to communicate directly with other UEs 115 over a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs 115 that utilize D2D communication may be within the geographic coverage area 110 of the base station 105. Other UEs 115 in such a group may be outside the geographic coverage area 110 of the base station 105 or may otherwise be unable to receive transmissions from the base station 105. In some examples, a group of UEs 115 that communicate via D2D communication may utilize a one-to-many (1:M) system in which each UE 115 transmits to every other UE 115 in the group. In some examples, the base station 105 facilitates scheduling of resources for D2D communication. In other cases, D2D communication occurs between UEs 115 without the involvement of the base station 105.

[0068]

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

[0069]

[0080] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC) that includes at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) that manages access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) that routes packets or interconnectivity to an external network. The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UE 115 served by the base station 105 associated with the core network 130. User IP packets may be transferred through a user plane entity that may provide IP address allocation and other functions. The user plane entity may be connected to an IP service 150 for one or more network operators. The IP service 150 may include access to the Internet, an (intra)net, an IP multimedia subsystem (IMS), or a packet-switched streaming service.

[0070]

[0081] Some of the network devices, such as base station 105, may include sub-components such as access network entity 140, which can be an example of an access node controller (ANC). Each access network entity 140 can communicate with UE 115 through one or more other access network transmission entities 145, which may be referred to as a radio head, a smart radio head, or a transmission / reception point (TRP). Each access network transmission 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 various network devices (e.g., radio head and ANC) or integrated into a single network device (e.g., base station 105).

[0071]

[0082] Wireless communication system 100 can typically operate using one or more frequency bands within the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or the decimeter band because the wavelength ranges from approximately 1 decimeter to 1 meter in length. UHF waves can be blocked or redirected by buildings and environmental features, but the waves can penetrate structures well enough for macrocells to provide service to UEs 115 located indoors. Transmissions at UHF waves can be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to transmissions using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0072]

[0083] Wireless communication system 100 may also operate in the Super High Frequency (SHF) band, which uses a frequency band from 3 GHz to 30 GHz, also known as the centimeter band, or in the Extremely High Frequency (EHF) band of the spectrum, also known as the millimeter band (e.g., from 30 GHz to 300 GHz). In some examples, wireless communication system 100 may support millimeter wave (mmW) communication between UE 115 and base station 105, and the EHF antennas of each device may be smaller and more closely spaced than UHF antennas. In some examples, this may facilitate the use of antenna arrays within the device. However, EHF transmissions are subject to greater atmospheric attenuation than SHF or UHF transmissions and may have a shorter range. The techniques disclosed herein may be employed across transmissions using one or more different frequency bands, and the specified use of bands across these frequency bands may vary by country or regulatory body.

[0073]

[0084] Wireless communication system 100 may utilize both licensed and unlicensed radio frequency spectrum bands. For example, wireless communication system 100 may employ License Assisted Access (LAA), Long Term Evolution Unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band such as the 5 GHz Industrial, Scientific, and Medical (ISM) band. When operating in an unlicensed radio frequency spectrum band, devices such as base station 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation in the unlicensed band may be based on a carrier aggregation configuration with a component carrier operating in a licensed band (e.g., LAA). Operation in the unlicensed spectrum may include, among other examples, downlink transmission, uplink transmission, peer-to-peer (P2P) transmission, or device-to-device (D2D) transmission.

[0074]

[0085] The base station 105 or the UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the base station 105 or the UE 115 may be located within one or more antenna arrays or antenna panels that can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be collocated in an antenna assembly such as an antenna tower. In some examples, the antennas or antenna arrays associated with the base station 105 may be located in various geographical locations. The base station 105 may have an antenna array with several rows and columns of antenna ports that can be used to support beamforming for communication with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support radio frequency beamforming for signals transmitted via the antenna ports.

[0075]

[0086] Base station 105 or UE 115 may use MIMO communication to increase spectral efficiency by leveraging multipath signal propagation and transmitting or receiving multiple signals via different spatial layers. Such techniques are sometimes referred to as spatial multiplexing. Multiple signals may be transmitted by a transmitting device, for example, via different antennas or different combinations of antennas. Similarly, multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO) in which multiple spatial layers are transmitted to the same receiving device and multi-user MIMO (MU-MIMO) in which multiple spatial layers are transmitted to multiple devices.

[0076]

[0087] Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that can be used in a transmitting device or a receiving device (e.g., base station 105, UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining signals communicated through antenna elements of an antenna array such that some signals propagating in a particular orientation of the antenna array experience constructive interference and others experience destructive interference. Adjustment of the signals communicated through the antenna elements can include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to the signals carried through the antenna elements associated with the device. The adjustment associated with each of the antenna elements can be defined by a set of beamforming weights associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or the receiving device, or with respect to some other orientation).

[0077]

[0088] Base station 105 or UE 115 may use beam sweeping techniques as part of a beamforming operation. For example, base station 105 may use multiple antennas or antenna arrays (e.g., antenna panels) to perform a beamforming operation for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by base station 105 in different directions. For example, base station 105 may transmit signals according to different sets of beamforming weights associated with different transmission directions. Transmission in different beam directions can be used to identify (e.g., by a transmitting device such as base station 105 or by a receiving device such as UE 115) a beam direction for subsequent transmission or reception by base station 105.

[0078]

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

[0079]

[0090] In some examples, transmission by a device (e.g., by base station 105 or UE115) can be performed using multiple beam directions, and the device can use a combination of digital precoding or radio frequency beamforming to generate a combined beam for transmission (e.g., from base station 105 to UE115). UE115 can report feedback indicating precoding weights for one or more beam directions, and the feedback can correspond to the system bandwidth or the configured number of beams over one or more subbands. Base station 105 can transmit a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)) that can be precoded or ampliconverted. UE115 can provide feedback for beam selection that can be a precoding matrix indicator (PMI) or a codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). These techniques have been described with respect to signals transmitted by base station 105 in one or more directions, but UE115 can employ similar techniques for transmitting signals multiple times in different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE115) or for transmitting a signal in a single direction (e.g., to transmit data to a receiving device).

[0080]

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

[0081]

[0092] The wireless communication system 100 can be a packet-based network that operates according to a hierarchical protocol stack. In the user plane, communication in 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 to communicate over logical channels. The Medium 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 retransmission in the MAC layer to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer can provide establishment, configuration, and maintenance of an RRC connection between the UE 115 and the base station 105 or the core network 130 that supports radio bearers for user plane data. In the physical layer, transport channels can be mapped to physical channels.

[0082]

[0093] The UE 115 and the base station 105 can support retransmission of data to increase the likelihood that the data is received correctly. Hybrid Automatic Repeat reQuest (HARQ) feedback is one technique for increasing the likelihood that data is received accurately over the 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 in the MAC layer under poor radio conditions (e.g., low signal-to-noise conditions). In some examples, the device can support same-slot HARQ feedback, where the device can provide HARQ feedback in a particular slot for data received in the previous symbol in that slot. In other cases, the device can provide HARQ feedback in a subsequent slot or according to some other time interval.

[0083]

[0094] UE115 can identify a default uplink beam (e.g., a default uplink transmission configuration indicator (TCI) state) for transmitting a scheduled uplink message based on the code point of the TCI indication included in the DCI message. The DCI message may include a TCI field that can indicate a single TCI state or a pair of TCI states. Some of the indicated TCI states or the pair of TCI states may include an uplink beam (e.g., an uplink TCI state or a common downlink / uplink TCI state). Therefore, the TCI state code point including or indicating the uplink beam can be considered a valid code point. UE115 can determine which TCI state code points are valid based on beam configuration (e.g., TCI state) selection criteria.

[0084]

[0095] The beam configuration selection criteria may include one or more rules as to which beam configuration or how many beam configurations are considered to be valid. In some examples, the beam configuration selection criteria may further include one or more rules for selecting or utilizing one or more valid TCI states out of a set of valid TCI states. Among the various TCI state code points included in the TCI field, a subset of the code points may be considered valid code points (e.g., a valid code point may indicate an uplink beam). UE115 may select a code point from the set of valid code points and use the uplink beam associated with the selected valid code point as the default uplink beam for transmitting the scheduled uplink message. In some examples, a single default beam may be considered valid based on a default TCI code point (e.g., a pair of TCI states may not be considered valid). In some examples, two default beams may be considered valid based on the default TCI code points indicating both beams (e.g., a pair of TCI states may be considered valid). In some examples, the scheduling DCI may not include one or more TCI state code points, and UE115 may determine the default uplink beam based on different DCI messages (e.g., the most recently received DCI message) that meet one or more rules or conditions.

[0085]

[0096] FIG. 2 shows an example of a wireless communication system 200 that supports default beam configuration selection for uplink transmission according to an aspect of the present disclosure. The wireless communication system 200 may implement the aspects of the wireless communication system 100. For example, the wireless communication system 200 may include a base station 205 and a UE 215, which may represent examples of the base station 105 and the UE 115, respectively, as described with reference to FIG. 1. Further, the base station 205 and the UE 215 may support beamformed transmission (e.g., the beams used for beamformed transmission may correspond to different TCI states).

[0086]

[0097] Some examples of wireless communication systems may support a unified transmission configuration indicator (TCI) state. The upper layer configuration may indicate one or more TCI states for each control resource set (CORESET). In some examples, the unified TCI state may support M downlink TCI states and N uplink TCIs. For M = 1 downlink TCI state, one or more reference signals in the downlink TCI state (e.g., two reference signals if a type 2 QCL relationship is configured in addition to the type 1 QCL relationship) may provide QCL information for UE-specific reception in the PDSCH and all CORESTs in at least the component carrier (CC). For N = 1 uplink TCI state, the source reference signal in the uplink TCI state may provide a reference for determining at least a dynamic grant or a configured grant uplink transmission spatial filter based on all of the dedicated PUCCH resources in the PUSCH and the CC. For N = M = 1, a common uplink / downlink TCI state may be configured. In such an example, the TCI state may refer to a common source reference signal used to determine at least both downlink QCL information and the uplink transmission spatial filter. In the case of separate downlink / uplink TCI states, the downlink TCI state and the uplink TCI state may be different (e.g., separate).

[0087]

[0098] For M downlink TCI states where M > 1, each of the M source reference signals in the M downlink TCI states (or 2 × M if a type 2 QCL relationship is configured in addition to the type 1 QCL relationship) may provide QCL information for one of the M beam pair links for UE - specific reception in at least a subset of the CORESETs in the PDSCH or CC. For N uplink TCI states where N > 1, each of the N source reference signals in the N uplink TCI states may provide a reference for determining an uplink transmission spatial filter for one of the N beam pair links associated with the dynamic grant or one of the configured - grant - based PUSCH resources in the CC. For M > 1 or N > 1 or both combined downlink / uplink TCI states, the TCI state may refer to a common source reference signal used to determine at least both the downlink QCL information and the uplink transmission spatial filter. In such an example, M may be equal to N. In the case of separate downlink / uplink TCI states, the M downlink TCI states and the N uplink TCI states are different (e.g., separate).

[0088]

[0099] Accordingly, a unified TCI state can be defined by one or more types. A type 1 TCI state may include a common downlink / uplink common TCI state to indicate a common beam for at least one downlink channel and at least one uplink channel and a reference signal in addition. A type 2 TCI state may include a separate downlink common TCI state to indicate a common beam for at least two downlink channels and a reference signal. A type 3 TCI state may include a separate uplink common TCI state to indicate a common beam for at least two uplink channels and a reference signal. A type 4 TCI state may include a separate downlink single channel and reference signal and TCI state to indicate a beam for a single downlink channel and a reference signal. A type 5 TCI state may include a separate uplink single channel and reference signal and TCI state to indicate a beam for a single uplink channel and a reference signal.

[0089]

[0100] In some examples of the unified TCI framework, UE115 can select, modify, or narrow its selection of a TCI state configuration, or can be configured with one or more TCI states. For example, the base station can dynamically indicate either a common downlink / uplink TCI or separate downlink / uplink TCI states. UE115 can advertise its ability to support either a common downlink / uplink TCI state or separate downlink / uplink TCI states. In some examples, UE115 can be configured with either a common downlink / uplink TCI state or separate downlink / uplink TCI states via RRC signaling. UE115 can be configured with either a common downlink / uplink TCI state, a separate downlink / uplink TCI state, or both via RRC signaling. In some examples, UE115 can be configured with either a common downlink / uplink TCI state or separate downlink / uplink TCI states via MAC-CE signaling. One or more TCI states can be activated by the base station or other wireless device.

[0090]

[0101] Wireless communication system 200 can support beam indication signaling to support common or separate downlink / uplink beam indications in a unified TCI framework. In some examples, L1-based beam indication that uses at least UE-specific (e.g., unicast) DCI messages to indicate common or separate downlink / uplink beam indications from an active TCI state. In some examples, the DCI message for beam indication can be DCI format 1_1, or DCI format 1_2. UE115 can support a mechanism for acknowledging successful decoding of the beam indication. For example, an acknowledgement (ACK) message or negative acknowledgement (NACK) message of a PDSCH scheduled by the DCI that conveys the beam indication can be used as the ACK or NACK message of the received DCI.

[0091]

[0102] In some examples, the DCI message of a cell (e.g., DCI format 0_0) may include a grant but may not include an indication of the uplink beam on which the scheduled uplink transmission should be sent. The UE may send the scheduled uplink transmission on the default uplink beam. For example, when one or more higher layer parameters (e.g., enableDefaultBeamPL-ForPUSCH0-r16) are enabled and the receiving UE115 is not configured with PUCCH resources in the active uplink BWP and the UE115 is operating in the RRC connected mode, the UE115 may transmit an uplink message on the PUSCH according to the spatial relationship (if applicable) while referring to a reference signal (e.g., in the downlink beam) having a QCL type D relationship corresponding to the QCL assumption of the CORESET having the lowest identifier in the active downlink BWP of the cell. That is, if the UE115 is not configured with the uplink beam on which the scheduled uplink transmission is to be sent (e.g., if the UE is not configured with the uplink TCI state on which the scheduled uplink message is to be sent), then the UE may identify the default uplink beam based on the CORESET ID (e.g., determine the uplink or joint uplink / downlink TCI state associated with the CORESET having the lowest ID).

[0092]

[0103] Similarly, PUSCH can be scheduled in a cell by DCI (e.g., DCI format 0_0). When one or more upper layer parameters (e.g., enableDefaultBeamPL-ForPUSCH0-r16) are set to be enabled, for a UE 115 composed of PUCCH resources in an active uplink BWP where all PUCCH resources are not configured in a spatial relationship and the UE 115 is in an RRC-connected mode, when a core set is configured in the cell, the UE 115 can transmit a message on the PUSCH according to the spatial relationship (e.g., if applicable) while referring to a reference signal having QCL type D corresponding to the QCL assumption of the core set having the lowest identifier in the active downlink BWP of the cell.

[0093]

[0104] Therefore, when the uplink TCI state is not explicitly indicated or not available to the UE 115 for a scheduled uplink transmission on the PUSCH, the UE can select a default uplink beam (e.g., a default uplink TCI state) that matches the downlink beam on which the downlink reference signal is received based on the QCL assumption of the core set having the lowest identifier. That is, the UE 115 can select a default uplink beam of the PUSCH that matches the downlink beam of the core set or the PDSCH.

[0094]

[0105] However, in some examples, the downlink beam associated with the CORESET having the lowest identifier may not be associated with the corresponding uplink beam. A unified TCI state may be indicated in the DCI of multiple channels, but may not always include the corresponding pair of uplink and downlink beams. For example, the base station may configure only the downlink beam of a particular CORESET, or may configure one or more downlink beams that do not have a corresponding uplink beam. In such an example, UE 115 attempting to select a default uplink TCI state while referring to the QCL assumption of a particular CORESET may not be able to identify the uplink TCI state (e.g., the QCL assumption that the CORESET may not correspond to the uplink TCI state). In such an example, UE 115 may have to determine or identify a new uplink TCI state and the uplink beam on which the scheduled uplink message is to be transmitted. This can lead to an increase in UE 115's latency (e.g., based on beamforming or beam refinement procedures or re-establishment procedures) or a transmission failure (e.g., if the UE does not identify the uplink beam on which the scheduled uplink message is to be transmitted before the occurrence of the scheduled uplink resources in the PUSCH). Such latency or transmission failure can lead to an increase in system latency, an increase in congestion, inefficient use of resources, and a reduction in the user experience.

[0095]

[0106] The techniques described in this specification may support identifying a default uplink beam (e.g., a default uplink TCI state) for transmitting an uplink message 210 based on a code point of a TCI indication included in a DCI message 220 (instead of, for example, identifying a default uplink beam for transmitting an uplink message 210 based on a CORESET identifier). The base station 205 may transmit the DCI message 220 to the UE 215. The DCI message 220 may include a TCI field 225. The TCI field 225 may indicate a single TCI state or a pair of TCI states of a plurality of TCI state types. For example, the pair of TCI states may include a downlink TCI state and an uplink TCI state (e.g., sometimes referred to as case 1). The pair of TCI states may include two uplink TCI states (e.g., sometimes referred to as case 2). The pair of TCI states may include two joint downlink / uplink TCI states (e.g., sometimes referred to as case 3). The TCI field in the DCI message may indicate a single TCI state. For example, the single TCI state may include a single joint downlink uplink TCI state (e.g., sometimes referred to as case 4). The single TCI state may include a single uplink TCI state (e.g., sometimes referred to as case 5). The MAC-CE may be used to activate a single TCI state or a pair of TCI states of the TCI field 225 in the DCI message 220.

[0096]

[0107] UE 115 may select a default uplink beam (e.g., a default uplink TCI state for generating a default uplink beam) based on code points associated with valid TCI types, as described herein. For example, the TCI field 225 may include one or more TCI indications. The TCI indication may indicate one or more cases (e.g., a pair of TCI states or a single TCI state, or any combination thereof). Some of the indicated cases (e.g., a single TCI state or a combined TCI state or a pair of TCI states) may be considered valid cases (e.g., may indicate an uplink TCI state or a combined uplink / downlink TCI state for which a scheduled uplink transmission can be sent). Some of the cases may be considered invalid cases (e.g., may include only a downlink TCI state or a pair of downlink TCI states). UE 215 may determine which cases are valid based on beam configuration (e.g., TCI state) selection criteria. The beam configuration selection criteria may include one or more rules regarding which beam configuration (e.g., case) or how many beam configurations (e.g., cases) are considered valid. In some examples, the beam configuration selection criteria may further include one or more rules for selecting or using one or more valid TCI states from a set of valid TCI states. In such an example, UE 115 may determine which of the cases indicated in the TCI field are valid (e.g., may exclude one or more invalid cases) and may select a default uplink TCI state for transmitting an uplink message with PUSCH from the valid TCI states. That is, among the various TCI state code points included in the TCI field 225, a subset of the code points may be considered valid code points (e.g., a valid code point may indicate an uplink beam). The UE may select a code point from the set of valid code points and may use the uplink beam associated with the selected valid code point as the default uplink beam.The techniques described in this specification may apply to scenarios where the base station 205 schedules the UE 215 to transmit the uplink message 210 within the explicit indication of the beam (e.g., the DCI message 220 is the fallback DCI0_0 and does not include a beam indication).

[0097]

[0108] In some examples, a single default beam may be considered valid based on the default TCI code point, as described in more detail with reference to FIG. 3 (e.g., a pair of TCI states may not be considered valid). In some examples, two default beams may be considered valid based on the default TCI code points indicating both beams, as described in more detail with reference to FIG. 3 (e.g., a pair of TCI states may be considered valid). In some examples, the UE 215 may determine the default uplink beam based on a valid DCI message (e.g., the most recent DCI message 220) that meets one or more rules or conditions, as described in more detail with reference to FIGS. 4-5.

[0098]

[0109] FIG. 3 shows an example of a process flow 300 that supports default beam configuration selection for uplink transmission according to an aspect of the present disclosure. The process flow 300 may include a base station 305 and a UE 315, which may be examples of the corresponding devices described with reference to FIGS. 1-2.

[0099]

[0110] At 320, the base station 305 may transmit DCI to the UE 315. The DCI may include an uplink grant for a PUSCH (e.g., for transmitting an uplink message at 335). In some examples, the DCI may include a set of TCI state code points corresponding to a set of beam configurations (e.g., a TCI field 225 indicating one or more TCI states in one or more cases as described with reference to FIG. 2). The DCI message may include both the uplink grant for the PUSCH and a set of one or more code points. In some examples, the first DCI message may include an uplink grant but may not include a set of one or more code points (e.g., as shown and described with reference to FIGS. 4 and 5). In such an example, another DCI message may include one or more TCI state code points.

[0100]

[0111] At 330, the UE 315 may select a TCI state code point from a set of TCI state code points. The selected code point may correspond to a default uplink beam for transmitting an uplink message at 335. The UE 315 may select the code point based at least in part on beam configuration selection criteria for selecting a subset of valid beam configurations (e.g., valid cases) from a set of beam configurations as described herein.

[0101]

[0112] At 335, the UE 315 may transmit an uplink message to the base station 305 on the PUSCH according to the grant received in the DCI at 320 and using the default uplink beam (e.g., the uplink beam corresponding to the code point selected at 330).

[0102]

[0113] In some examples, the UE 315 may select a code point based on a code point identifier. For example, the UE 315 may select, at 325, a subset of valid beam configurations from a complete set of beam configurations. That is, the UE 315 may select a valid code point from a set of one or more code points configured in a DCI message. The UE 315 may determine that the uplink beam associated with the valid code point is a subset of valid beam configurations of the set of beam configurations. A valid beam configuration may meet beam configuration selection criteria. In some examples, multiple beam configurations may be valid. That is, multiple code points of the set of code points may correspond to an uplink TCI state. In such an example, the UE 315 may select one of the multiple code points based on comparing the code point identifiers of the code points corresponding to the subset of valid beam configurations. Based on the order of the code point identifiers, the UE 315 may select a code point at 330. For example, the UE 315 may select the valid code point with the highest or lowest identifier.

[0103]

[0114] In some examples, the beam selection criterion may include a restriction of a subset of valid beam configurations to a beam configuration having a single uplink beam option. For example, the DCI at 320 may schedule the transmission of an uplink message and may not include a beam indication (e.g., it may be fallback DCI0_0). For example, UE315 may select a code point having the lowest identifier, the highest identifier, the median identifier in the middle, etc. In such an example, UE315 may apply a default beam to the uplink transmission while referring to the spatial filter of the unified TCI state in the active BWP of the cell, and the unified TCI state may be determined by the TCI code point having the lowest or highest identifier including the valid TCI state. A single default beam may be selected based on the default TCI code point. Only a single TCI state may be considered valid under the restriction of the beam configuration selection criterion.

[0104]

[0115] In some examples, the valid TCI state may include only a single TCI state. The single TCI state may refer to only the uplink TCI state (e.g., only case 5 may be considered valid). The single TCI state may refer to only the common downlink / uplink TCI state (e.g., only case 4 may be considered valid). The single TCI state may refer to the uplink TCI state or the common downlink / uplink TCI state (e.g., both case 5 and case 4 may be considered valid). In some examples, either a single TCI state or a pair of a downlink TCI state and an uplink TCI state may be considered valid (e.g., case 1 may be considered valid).

[0105]

[0116] Thus, in cases where the beam configuration selection criterion restricts the subset of valid beam configurations to a beam configuration having a single uplink beam option, UE315 may determine which, if any, of the set of code points indicated in the DCI is valid. UE315 may consider a code point valid only if they meet the beam configuration selection criterion. For example, one or more DCI messages may include code points indicating one or more cases. For example, code point 1 may indicate case 1, code point 2 may indicate case 4, and code point 3 may indicate case 5. In some examples, the beam configuration selection criterion may restrict the valid beam configuration (e.g., the valid code points associated with the uplink TCI state) to a single uplink beam, e.g., only the uplink TCI state (e.g., case 5). In such an example, UE315 may determine that both code point 1 and code point 2 are invalid and that code point 3 is valid. In such an example, UE315 may select the code point (e.g., code point 3) at 330, thereby selecting the default uplink beam associated with the selected code point. UE315 may then transmit an uplink message at 335 using the selected default uplink beam. Similarly, a single valid TCI state refers to the uplink TCI state or the joint downlink / uplink TCI state (e.g., both case 5 and case 4 are considered valid). In such an example, at 325, UE315 may determine that both code point 2 and code point 3 are valid. At 330, UE315 may select one of the valid subset of beams (e.g., select both code point 2 and code point 3 as valid and code point 1 as invalid). For example, UE315 may determine which of code point 2 and code point 3 has the lowest or highest identifier.

[0106]

[0117] In some examples, a single valid TCI state may refer to a single uplink beam, e.g., the uplink TCI state only (e.g., case 5). Code point 1 in the DCI's TCI field may map to case 5, code point 2 in the TCI field may map to case 5, and code point 3 in the DCI field may map to case 5. UE315 may determine that any of the code points meets the beam configuration selection criteria and may select one of the valid code points based on the order of the identifiers (e.g., at 325). In some examples, UE315 may select a subset of valid beams based on a set of one or more code points included in a single DCI message. In some examples, UE315 may select a subset of valid beams based on a set of one or more code points included in multiple DCI messages as shown with reference to FIG. 4. For example, a DCI message containing a grant may sometimes not contain a code point or may not contain a valid code point. In such examples, UE315 may identify one or more valid code points in a previous DCI message as further described in more detail with reference to FIGS. 4 - 5.

[0107]

[0118] In some examples, the beam selection criteria may include a restriction of the valid beam configuration subset to a beam configuration having a single uplink beam option, multiple uplink beam options, or both. That is, UE 315 may select a valid code point, and two default beams may be associated with the default TCI code point. For example, the DCI received at 320 may schedule UE 315 having uplink transmission, and the DCI message including the grant may not include a beam indication (e.g., the DCI message may be a fallback DCI0_0). UE 315 may apply the default beam to the uplink transmission while referring to the spatial transmission filter of the unified TCI state in the active BWP of the cell. The unified TCI state may be at the TCI code point having the lowest or highest identifier of the pair of TCI states. The pair of TCI states may include at least an uplink TCI state (e.g., Case 1 and Case 2 may be considered valid). The pair of TCI states may include at least one common downlink / uplink TCI state (e.g., Case 3 may be considered valid). The pair of TCI states may include at least one common downlink / uplink TCI state or one uplink TCI state (e.g., Case 1, Case 2, and Case 3 may be considered valid).

[0108]

[0119] Thus, based on the limitations of the beam configuration selection criteria (e.g., supporting two default beams associated with the default TCI code point), UE 315 may select the code points associated with the two TCI states. For example, a DCI message (e.g., the current DCI message including uplink grant, or the previous DCI message, or any combination thereof) may include one or more code points. Code point 1 may be mapped to case 2, code point 2 may be mapped to case 5, and code point 3 may be mapped to case 5. In such an example, at 325, UE 315 may select code point 1 as a valid code point and determine that code point 2 and code point 3 are not valid code points. Thus, UE 315 may select the uplink beam or pair of uplink beams associated with code point 1 as a subset of the valid beams (e.g., case 2) (e.g., and may determine that the uplink beams associated with code point 2 and code point 3 are not associated with valid uplink beams). At 330, UE 315 may select a valid code point from the set of valid code points (e.g., may select code point 1, which may be the only valid code point in such an example).

[0109]

[0120] In some examples, the selected code point may include a pair of valid uplink beams. For example, the selected code point may indicate two uplink TCI states or two combined downlink / uplink TCI states. In such examples, the UE 315 may determine which of the two uplink beams associated with the two uplink TCI states to use, or may use both TCI states for the repetition. For example, the UE 315 may determine which uplink beam to use based on a predetermined rule. Such a predetermined rule may be included in beam configuration selection criteria, may be indicated in a downlink message (e.g., upper layer signaling, DCI message, etc.), may be included in one or more standards, or any combination thereof may be made. For example, the rule may indicate that the UE 315 will select the uplink beam with the lower or higher identifier of the first or pair of uplink beams from the two uplink beams associated with the selected code point. In some examples, the UE 315 may use both uplink beams associated with the selected code point for uplink repetition. For example, the UE 315 may determine an uplink transmission that is to be sent with pain / beam repetition. In such examples, the UE 315 may send the first repetition of the uplink message at 335 using the first beam and may send the second repetition of the uplink message at 340 using the second beam. In some examples, the base station 305 may explicitly indicate which of the two valid beams to use to send the uplink message at 335. For example, the UE 315 may determine one uplink transmission that is to be sent on one or more beams selected by an uplink DCI message (e.g., including an uplink grant or a set of code points or both). For example, the DCI message scheduling the uplink transmission may include a dedicated field that can be applied for dynamic panel switching or beam switching.The field may include an indication of which of the two valid beams the UE 315 is to use to transmit the scheduled uplink message.

[0110]

[0121] In some examples, the base station 305 may indicate beam configuration selection criteria to the UE 315 (e.g., at 310). The beam configuration selection criteria may be included in a DCI message, a higher layer signaling message (e.g., an RRC information element (IE), a MAC-CE, etc.). The beam configuration selection criteria may be included in one or more standard documents, etc., and pre-configured at the UE 315.

[0111]

[0122] In some examples, any of the beam selection procedures described with reference to FIG. 3 may be utilized to select a valid code point from a DCI message including an uplink grant, or from a previous DCI message, as described with reference to FIGS. 4 and 5.

[0112]

[0123] FIG. 4 shows an example of a timeline 400 that supports default beam configuration selection for uplink transmission according to an aspect of the present disclosure. The timeline 400 may implement, or be implemented by, one or more UEs 415, and one or more base stations, which may be examples of the corresponding devices described with reference to FIGS. 1-3.

[0113]

[0124] The base station may schedule one or more uplink transmissions from the UE415 that transmits one or more DCI messages. In some examples, the DCI message may be a unicast DCI message (e.g., DCI405 for UE415-a and UE415-b). In some examples, the DCI message may be a group common (GC) DCI410 addressed to a plurality of UEs (e.g., both the first UE and the second UE). Some DCI405 or GC DCI410 may include a TCI field that may include one or more code points indicating a TCI state. For example, the TCI field in DCI405-a may indicate code point 2, the TCI field in DCI405-b may indicate code point 3, and the TCI field in DCI405-a may indicate code point 1, etc. Similarly, the TCI field in DCI405-d may indicate code point 2, the TCI field in DCI405-e may indicate code point 3, and the TCI field in DCI405-f may indicate code point 1, or any other code point. The GC DCI410 may or may not include one or more code points for various UEs.

[0114]

[0125] In some examples, the UE415 may determine a default beam based on the most recently received DCI message that meets one or more rules. Such rules may be included in beam configuration selection criteria, or may be configured individually, standardized, or otherwise known to the UE. The base station may configure the UE having an uplink transmission by DCI420. The DCI420 may include permission for an uplink message and may not include one or more code points or beam indications. In such an example, the UE may apply a default beam to the uplink transmission while referring to a spatial transmission filter of a unified TCI state indicated by the most recent DCI configured with a unified TCI code point. However, for the most recent DCI to be considered, the DCI may meet one or more rules.

[0115]

[0126] UE415-a may determine the most recent DCI that it will rely on to determine the default uplink beam based on different DCI CORESET identifiers. For example, the most recent DCI may be transmitted in a CORESET with the same CORESET pool index as DCI420. If DCI405-a is transmitted in a CORESET having the same identifier as the CORESET in which DCI420 is transmitted, then UE415-a may determine that DCI405-c is the most recent DCI405, and may determine whether one or more code points (e.g., code point 1) are considered valid based on beam configuration selection criteria. If so, UE415-a may select code point 1 as a valid code point and transmit the uplink message permitted in DCI420-a using the uplink beam associated with code point 1. Alternatively, UE415-a may determine that code point 1 is not a valid code point and may select a previously received DCI405. If DCI405-b is not received in the same CORESET as DCI420-a, then UE415-a may not rely on the code point (e.g., code point 3) indicated in DCI405-b for selecting the default uplink beam. If DCI405-a indicates a code point that is considered a valid code point (e.g., code point 2) and is received in the same CORESET as DCI420-a, then UE415 may select the uplink beam associated with code point 2 as the default uplink beam.

[0116]

[0127] UE415-a may determine the most recent DCI based on the timing of the previous DCI405. For example, the most recent DCI may be the GC DCI410. The GC DCI410 may indicate a unified TCI state to a plurality of panels (e.g., and a plurality of UEs415). For example, the DCI format of the GC DCI410 may be DCI2-x. In such an example, a minimum timing gap may be defined to determine which DCI is the most recent DCI. The minimum timing gap may also be referred to as beam application time, threshold timing gap, threshold time, etc. For the GC DCI410, the threshold timing gap may be defined by a new parameter (e.g., a higher layer parameter configurable by RRC or an updated MAC-CE or an updated DCI message). In some examples, the scheduling DCI (e.g., DCI420-a) may include an indication of the threshold timing gap. The threshold timing gap may be included in the beam configuration selection criteria, may be included in the standard, etc. In some examples, the threshold timing gap value may be derived from existing timing offsets. For example, UE415-a may select one of two existing timing offsets of the timing value (e.g., the maximum value). For example, UE415-a may select the maximum value of two minimum timing offsets or processing offsets (e.g., K0 that may refer to the offset between PDCCH and PDSCH, K2 that may refer to the time offset between PDCCH and PUSCH), or the time duration for QCL (e.g., timeDurationForQCL that may be defined as the minimum time offset required for TCI in DCI to act in the case of a single downlink TCI) and the maximum value of the timing offset (e.g., the maximum value of timeDurationForQCL and K2), etc.

[0117]

[0128] By determining a threshold timing gap, UE415-a may determine whether GC DCI410 meets the threshold timing gap. That is, the most recent DCI may be a DCI received before the beam application time (e.g., the threshold timing gap) ends before receiving DCI420-a (e.g., excluding DCI405 where the beam indication has not yet been applied). UE415-a may determine whether it received GC DCI410 at least a threshold timing gap before receiving DCI420-a. In such a case, UE415-a may then continue to determine whether the code point included in GC DCI410 meets the beam configuration selection criteria. If so, UE415-a may select a valid uplink beam associated with the valid code point indicated in GC DCI410 as described with reference to FIG. 3. That is, the most recent DCI may be a DCI that includes an applicable TCI state (e.g., a valid TCI state) as described in more detail with reference to FIG. 3.

[0118]

[0129] GC DCI410 may include an uplink grant, but may not include a code point or a valid code point. In such an example, UE415-a (e.g., or UE415-b) may, if any, determine which previously received DCI405 may be considered the most recent DCI. For example, UE415-a may determine whether DCI405-a meets the threshold timing gap before receiving GC DCI410, whether DCI405-a was received in the same CORESET as GC DCI410, whether DCI405-a indicates a valid code point as described with reference to FIG. 3, or any combination thereof.

[0119]

[0130] FIG. 5 shows an example of a process flow 500 that supports default beam configuration selection for uplink transmission according to an aspect of the present disclosure. The process flow 500 may include a base station 505 and a UE 515, which may be examples of corresponding devices described with reference to FIGS. 1-4.

[0120]

[0131] At 525, the base station 505 may transmit DCI to the UE 515. The DCI may include an uplink grant for the PUSCH (e.g., for transmitting an uplink message at 335). The base station 505 may transmit a first DCI message at 525-a and a second DCI message at 525-b. The first DCI message may include a set of one or more code points corresponding to a set of beam configurations (e.g., a TCI field 225 indicating one or more TCI states of one or more cases as described with reference to FIG. 2). In some examples, the second DCI message may include uplink grants for both the PUSCHs. In some examples, the second DCI message may not include an uplink beam indication. In such examples, the UE 515 may determine the default uplink beam on which the message is to be transmitted as described with reference to FIG. 4.

[0121]

[0132] To identify the default uplink beam, the UE 515 may identify a default code point from the set of code points. However, to identify the set of code points, the UE 515 may determine which previously transmitted DCI message (e.g., the first DCI message) is considered to be the most recent DCI.

[0122]

[0133] In some examples, the UE 515 may determine that the first DCI message is the most recent DCI message based on the CORESET pool index of two DCI messages (e.g., and may rely on the set of code points indicated in the first DCI message to determine the default uplink beam). For example, the UE 515 may compare the CORESET pool index of the CORESET where the base station 505 transmitted the first DCI message with the CORESET pool index of the CORESET where the base station 505 transmitted the second DCI message. The UE 515 may determine that the first CORESET pool index is the same as the second CORESET pool index, and thus, may determine that the first DCI message is the most recent DCI message that satisfies one or more rules (e.g., beam configuration selection criteria, or included in a separate set of rules). In such an example, at 530, the UE 515 may select the code points of the set of code points indicated in the first DCI message. The UE 515 may select code points based on beam configuration selection criteria as described with reference to FIGS. 3-4. The UE 515 may select the default uplink beam associated with the selected code points and may transmit an uplink message using the selected default uplink beam.

[0123]

[0134] In some examples, the UE 515 may determine that the first DCI message is the most recent DCI message based on determining whether a time period (e.g., a threshold timing gap) meets the threshold timing gap. The threshold timing gap may refer to the beam application time. At 540, the UE 515 may determine whether the time period between the reception of the first DCI message and the second DCI message meets the threshold timing gap (e.g., is not greater than the threshold timing gap). If the duration between previously received DCI messages does not meet the threshold timing gap (e.g., is less than the threshold timing gap duration), then the UE 515 may determine that such a DCI message is not the most recently received DCI message (e.g., may not attempt to utilize the TCI state code point indicated in the previously received DCI message). However, if the time period between the reception of the first DCI message and the second DCI message meets the threshold timing gap, the UE 515 may utilize the TCI state code point indicated in the first DCI message to determine the default uplink beam for transmitting the uplink message indicated in the second DCI message. In some examples, the first DCI message, or the second DCI message, or both may be GC DCI messages.

[0124]

[0135] The UE 515 may determine the threshold timing gap by comparing two time values or time offsets (e.g., may determine which has a greater duration). The UE 515 may select the larger of the two time offsets. In some examples, the base station 505 may transmit an indication of the threshold timing gap at 520. The indication of the threshold timing gap may be a DCI message, a MAC-CE, an RRC message, or any combination thereof.

[0125]

[0136] In some examples, the base station 505 may indicate beam configuration selection criteria to the UE 515 (e.g., at 510). The beam configuration selection criteria may be included in a DCI message, a higher layer signal message (e.g., an RRC information element (IE), a MAC-CE, etc.). The beam configuration selection criteria may be included in one or more standard documents, etc., and pre-configured in the UE 515.

[0126]

[0137] FIG. 6 shows a block diagram 600 of a device 605 that supports default beam configuration selection for uplink transmission according to an aspect of the present disclosure. The device 605 may be an example of an aspect of the UE 115 described herein. The device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0127]

[0138] The receiver 610 may provide means for receiving information such as packets, user data, control information, or any combination thereof, associated with various information channels (e.g., control channels, data channels, information channels related to default beam configuration selection for uplink transmission). The information may be passed to other components of the device 605. The receiver 610 may utilize a single antenna or a set of multiple antennas.

[0128]

[0139] The transmitter 615 may provide means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information such as packets, user data, control information, or any combination thereof, associated with various information channels (e.g., control channels, data channels, information channels related to default beam configuration selection for uplink transmission). In some examples, the transmitter 615 may be collocated with the receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a set of multiple antennas.

[0129]

[0140] The communication manager 620, the receiver 610, the transmitter 615, or various combinations or various components thereof can be examples of means for implementing various aspects of the default beam configuration selection for uplink transmission described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof can support a method for implementing one or more of the functions described herein.

[0130]

[0141] In some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof can be implemented in hardware (e.g., in a communication management circuit). The hardware can include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gates or transistor logic, discrete hardware components, or any combination thereof, configured as or otherwise supporting the means for implementing the functions described in this disclosure. In some examples, a processor and a memory coupled to the processor can be configured to implement one or more of the functions described herein (e.g., by the processor executing instructions stored in the memory).

[0131]

[0142] Additionally or alternatively, in some examples, the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be implemented in code executed by a processor (e.g., as communication management software or firmware). When implemented in code executed by a processor, the functions of the communication manager 620, the receiver 610, the transmitter 615, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination thereof or other programmable logic device configured as (e.g., configured as means for performing the functions described in the present disclosure or otherwise supporting such means).

[0132]

[0143] In some examples, the communication manager 620 may be configured to perform various operations (e.g., receive, monitor, transmit) using, or in cooperation with, the receiver 610, the transmitter 615, or both. For example, the communication manager 620 may be incorporated in combination with the receiver 610, the transmitter 615, or both to receive information from the receiver 610, send information to the transmitter 615, or perform various other operations described herein.

[0133]

[0144] The communication manager 620 may support wireless communication in a UE according to the examples disclosed herein. For example, the communication manager 620 may be configured as or support means for receiving downlink control information including an uplink grant for a physical uplink shared channel from a base station, where the downlink control information indicates a set of code points corresponding to a set of beam configurations. The communication manager 620 may be configured as or support means for selecting a code point from a set of code points corresponding to a default uplink beam for transmitting an uplink message on a physical uplink shared channel based on a beam configuration selection criterion indicating a criterion for selecting a subset of valid beam configurations from the set of beam configurations. The communication manager 620 may be configured as or support means for transmitting an uplink message on a physical uplink shared channel in accordance with an uplink grant using the default uplink beam.

[0134]

[0145] By including or configuring the communication manager 620 according to the examples described herein, a device 605 (e.g., a processor that controls or is otherwise coupled to a receiver 610, a transmitter 615, the communication manager 620, or a combination thereof) may support techniques for selecting a default uplink beam that may result in a reduction in system latency, a more efficient use of available resources, more efficient communication, a more efficient use of computing resources, an increase in battery life, and an improved user experience.

[0135]

[0146] FIG. 7 shows a block diagram 700 of a device 705 that supports default beam configuration selection for uplink transmission according to an aspect of the present disclosure. The device 705 can be an example of the device 605 or UE115 described herein. The device 705 can include a receiver 710, a transmitter 715, and a communication manager 720. The device 705 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).

[0136]

[0147] The receiver 710 can provide means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to default beam configuration selection for uplink transmission). The information can be passed to other components of the device 705. The receiver 710 can utilize a single antenna or a set of multiple antennas.

[0137]

[0148] The transmitter 715 can provide means for transmitting signals generated by other components of the device 705. For example, the transmitter 715 can transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to default beam configuration selection for uplink transmission). In some examples, the transmitter 715 can be collocated with the receiver 710 within a transceiver module. The transmitter 715 can utilize a single antenna or a set of multiple antennas.

[0138]

[0149] Device 705, or its various components, can be an example of means for implementing various aspects of the default beam configuration selection for uplink transmission described herein. For example, communication manager 720 can include a DCI manager 725, a beam configuration selection criteria manager 730, an uplink message manager 735, or any combination thereof. Communication manager 720 can be an example of the aspects of communication manager 620 described herein. In some examples, communication manager 720, or its various components, can be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise in cooperation with receiver 710, transmitter 715, or both. For example, communication manager 720 can receive information from receiver 710, send information to transmitter 715, or be incorporated in combination with receiver 710, transmitter 715, or both to perform various other operations described herein, such as receiving information, transmitting information, or performing various other operations.

[0139]

[0150] The communication manager 720 may support wireless communication in a UE according to the examples disclosed herein. The DCI manager 725 is configured as or may support means for receiving downlink control information including an uplink grant for a physical uplink shared channel from a base station, where the downlink control information indicates a set of code points corresponding to a set of beam configurations. The beam configuration selection criterion manager 730 is configured as or may support means for selecting a code point from a set of code points corresponding to a default uplink beam for transmitting an uplink message on a physical uplink shared channel based on a beam configuration selection criterion indicating a criterion for selecting a subset of valid beam configurations from a set of beam configurations. The uplink message manager 735 is configured as or may support means for transmitting an uplink message on a physical uplink shared channel in accordance with an uplink grant using a default uplink beam.

[0140]

[0151] FIG. 8 shows a block diagram 800 of a communication manager 820 that supports default beam configuration selection for uplink transmission according to an aspect of the present disclosure. The communication manager 820 may be an example of an aspect of the communication manager 620, the communication manager 720, or both, as described herein. The communication manager 820, or its various components, may be an example of means for implementing various aspects of default beam configuration selection for uplink transmission described herein. For example, the communication manager 820 may include a DCI manager 825, a beam configuration selection criterion manager 830, an uplink message manager 835, a code point selection manager 840, a beam configuration rule manager 845, a beam switching instruction manager 850, a CORESET index manager 855, a DCI timing manager 860, an iteration manager 865, or any combination thereof. Each of these components may communicate with each other (e.g., via one or more buses), either directly or indirectly.

[0141]

[0152] The communication manager 820 may support wireless communication in a UE according to the examples disclosed herein. The DCI manager 825 is configured as or may support means for receiving downlink control information including an uplink grant for a physical uplink shared channel from a base station, where the downlink control information indicates a set of code points corresponding to a set of beam configurations. The beam configuration selection criterion manager 830 is configured as or may support means for selecting a code point from a set of code points corresponding to a default uplink beam for transmitting an uplink message on a physical uplink shared channel based on a beam configuration selection criterion indicating a criterion for selecting a subset of valid beam configurations from a set of beam configurations. The uplink message manager 835 is configured as or may support means for transmitting an uplink message on a physical uplink shared channel in accordance with an uplink grant using a default uplink beam.

[0142]

[0153] In some examples, the code point selection manager 840 is configured as or may support means for comparing code point identifiers of code points corresponding to a subset of valid beam configurations, where selecting a code point from a set of code points may be based on the order of the compared code point identifiers.

[0143]

[0154] In some examples, the beam configuration selection criterion manager 830 is configured as or may support means for selecting a subset of valid beam configurations based on a beam configuration selection criterion, where the beam configuration selection criterion includes a restriction of the subset of valid beam configurations to beam configurations having a single uplink beam option.

[0144]

[0155] In some examples, the beam configuration selection criteria manager 830 may be configured as or support means for selecting a subset of valid beam configurations based on beam configuration selection criteria, where the beam configuration selection criteria includes a restriction of the subset of valid beam configurations to a beam configuration having a single uplink beam option, a plurality of uplink beam options, or both.

[0145]

[0156] In some examples, the beam configuration rule manager 845 may be configured as or support means for applying the rules indicated in the beam configuration selection criteria, where the rules include an indication of which of the plurality of uplink beam options should be selected to transmit an uplink message, and where selecting a code point from a set of code points is based on applying the rules.

[0146]

[0157] In some examples, the code point selection manager 840 may be configured as or support means for selecting a second code point from a set of code points corresponding to a second default uplink beam of a subset of valid beam configurations based on beam configuration selection criteria.

[0147]

[0158] In some examples, to support transmitting an uplink message, the iteration manager 865 may be configured as or support means for transmitting a first iteration of the uplink message using a default uplink beam. In some examples, to support transmitting an uplink message, the iteration manager 865 may be configured as or support means for transmitting a second iteration of the uplink message using a second default uplink beam.

[0148]

[0159] In some examples, the beam switching instruction manager 850 may be configured as or support means for receiving, in downlink control information, a beam switching instruction indicating which of a plurality of uplink beam options to select for transmitting an uplink message, where selecting a code point from a set of code points is based on receiving the beam switching instruction.

[0149]

[0160] In some examples, to support receiving downlink control information, the DCI manager 825 may be configured as or support means for receiving a first downlink control information message including an uplink grant for a physical uplink shared channel. In some examples, to support receiving downlink control information, the DCI manager 825 may be configured as or support means for receiving a second downlink control information message including a set of code points before receiving the first downlink control information message.

[0150]

[0161] In some examples, the CORESET index manager 855 may be configured as or support means for comparing a first control resource set pool index associated with a first downlink control information message with a second control resource set pool index associated with a second downlink control information message. In some examples, the CORESET index manager 855 may be configured as or support means for determining, based on the comparison, that the first control resource set pool index and the second control resource set pool index are the same, where selecting a code point is based on the first control resource set pool index and the second control resource set pool index being the same.

[0151]

[0162] In some examples, the DCI timing manager 860 is configured as or may support means for determining that a time period between receiving a second downlink control information message and receiving a first downlink control information message meets a threshold timing gap, where selecting a code point is based on the determining.

[0152]

[0163] In some examples, at least one of the first downlink control information message or the second downlink control information message includes a group common downlink control information message.

[0153]

[0164] In some examples, the DCI timing manager 860 is configured as or may support means for receiving an indication of a threshold timing gap from a base station, where determining that the time period meets the threshold timing gap is based on receiving the indication of the threshold timing gap.

[0154]

[0165] In some examples, the DCI timing manager 860 is configured as or may support means for comparing a first time offset value with a second time offset value. In some examples, the DCI timing manager 860 is configured as or may support means for selecting a first time offset value based on the comparison, where the first time offset value includes a threshold timing gap, and where determining that the time period meets the threshold timing gap is based on selecting the first time offset value.

[0155]

[0166] In some examples, the beam configuration selection criterion manager 830 is configured as or may support means for receiving an indication of a beam configuration selection criterion from a base station, where selecting a code point is based on receiving the indication of the beam configuration selection criterion.

[0156]

[0167] Figure 9 shows a diagram of a system 900 that includes a device 905 that supports default beam configuration selection for uplink transmission according to an aspect of the present disclosure. The device 905 may be an example of or include components of the device 605, the device 705, or the UE 115 described herein. The device 905 may wirelessly communicate with one or more base stations 105, UEs 115, or any combination thereof. The device 905 may include components for bidirectional voice and data communication, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, a memory 930, code 935, and a processor 940. These components may be electronically communicating or otherwise coupled (e.g., operably, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 945).

[0157]

[0168] The I / O controller 910 may manage input and output signals for the device 905. The I / O controller 910 may also manage peripheral devices not incorporated in the device 905. In some cases, the I / O controller 910 may represent a physical connection or port to an external peripheral device. In some cases, the I / O controller 910 may utilize an operating system, such as iOS (registered trademark), ANDROID (registered trademark), MS-DOS (registered trademark), MS-WINDOWS (registered trademark), OS / 2 (registered trademark), UNIX (registered trademark), LINUX (registered trademark), or another known operating system. Additionally or alternatively, the I / O controller 910 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, the I / O controller 910 may be implemented as part of a processor, such as the processor 940. In some cases, a user may interact with the device 905 via the I / O controller 910 or via hardware components controlled by the I / O controller 910.

[0158]

[0169] In some cases, device 905 may include a single antenna 925. However, in some other cases, device 905 may have two or more antennas 925 that may be capable of simultaneously transmitting or receiving multiple wireless transmissions. Transceiver 915 may communicate bidirectionally via one or more antennas 925, wired links, or wireless links, as described herein. For example, transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 915 may also include a modem for modulating packets and providing the modulated packets to one or more antennas 925 for transmission and for demodulating packets received from one or more antennas 925. Transceiver 915, or transceiver 915 and one or more antennas 925, may be an example of transmitter 615, transmitter 715, receiver 610, receiver 710, or any combination thereof or components thereof, as described herein.

[0159]

[0170] Memory 930 may include random access memory (RAM) and read only memory (ROM). Memory 930 may store computer-readable, computer-executable code 935 that includes instructions that, when executed by processor 940, cause device 905 to perform various functions described herein. Code 935 may be stored on a non-transitory computer-readable medium, such as a system memory or another type of memory. In some cases, code 935 may not be directly executable by processor 940 but may cause a computer to perform functions described herein when (e.g., when compiled and executed). In some cases, memory 930 may especially include a basic input / output system (BIOS) that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0160]

[0171] Processor 940 may include an intelligent hardware device (e.g., a general-purpose processor, DSP, CPU, microcontroller, ASIC, FPGA, programmable logic device, discrete gate or transistor logic component, discrete hardware component, or any combination thereof). In some cases, processor 940 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 940. Processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 930) to cause the device 905 to perform various functions (e.g., functions or tasks that support default beam configuration selection for uplink transmission). For example, device 905 or components of device 905 may include processor 940 and memory 930 coupled to processor 940, and processor 940 and memory 930 are configured to perform the various functions described herein.

[0161]

[0172] Communication manager 920 may support wireless communication in a UE according to the examples disclosed herein. For example, communication manager 920 may be configured as or support means for receiving downlink control information including an uplink grant for a physical uplink shared channel from a base station, where the downlink control information indicates a set of code points corresponding to a set of beam configurations. Communication manager 920 may be configured as or support means for selecting a code point from a set of code points corresponding to a default uplink beam for transmitting an uplink message on a physical uplink shared channel based on a beam configuration selection criterion indicating a criterion for selecting a subset of valid beam configurations from a set of beam configurations. Communication manager 920 may be configured as or support means for transmitting an uplink message on a physical uplink shared channel in accordance with an uplink grant using the default uplink beam.

[0162]

[0173] By including or being configured to include the communication manager 920 according to the examples described herein, the device 905 may support techniques for selecting a default uplink beam that can result in a reduction in system latency, more efficient use of available resources, more efficient communication, more efficient use of computing resources, increased battery life, and an improved user experience.

[0163]

[0174] In some examples, the communication manager 920 may be configured to use or otherwise cooperate with the transceivers 915, one or more antennas 925, or any combination thereof to perform various operations (e.g., receive, monitor, transmit). Although the communication manager 920 is shown as a separate component, in some examples, one or more of the functions described with reference to the communication manager 920 may be supported by or implemented by the processor 940, the memory 930, the code 935, or any combination thereof. For example, the code 935 may include instructions executable by the processor 940 to cause the device 905 to perform various aspects of the default beam configuration selection for uplink transmission described herein, or the processor 940 and the memory 930 may be otherwise configured to perform or support such operations.

[0164]

[0175] FIG. 10 shows a block diagram 1000 of a device 1005 that supports default beam configuration selection for uplink transmission according to an aspect of the present disclosure. The device 1005 may be an example of an aspect of the base station 105 described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. The device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0165]

[0176] The receiver 1010 may provide means for receiving information such as packets, user data, control information, or any combination thereof, associated with various information channels (e.g., control channels, data channels, information channels related to default beam configuration selection for uplink transmission). The information may be passed on to other components of the device 1005. The receiver 1010 may utilize a single antenna or a set of multiple antennas.

[0166]

[0177] The transmitter 1015 may provide means for transmitting signals generated by other components of the device 1005. For example, the transmitter 1015 may transmit information such as packets, user data, control information, or any combination thereof, associated with various information channels (e.g., control channels, data channels, information channels related to default beam configuration selection for uplink transmission). In some examples, the transmitter 1015 may be collocated with the receiver 1010 in a transceiver module. The transmitter 1015 may utilize a single antenna or a set of multiple antennas.

[0167]

[0178] The communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be examples of means for implementing various aspects of the default beam configuration selection for uplink transmission described herein. For example, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may support a method for implementing one or more of the functions described herein.

[0168]

[0179] In some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit). The hardware may include a processor, a DSP, an ASIC, an FPGA, or other programmable logic device, discrete gates or transistor logic, discrete hardware components, or any combination thereof, configured as or otherwise supporting means for performing the functions described in this disclosure. In some examples, a processor and a memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by the processor executing instructions stored in the memory).

[0169]

[0180] Additionally or alternatively, in some examples, the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) executed by a processor. When implemented in code executed by a processor, the functions of the communication manager 1020, the receiver 1010, the transmitter 1015, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, or any combination thereof or other programmable logic device configured as or otherwise supporting means for performing the functions described in this disclosure.

[0170]

[0181] In some examples, the communication manager 1020 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the receiver 1010, the transmitter 1015, or both. For example, the communication manager 1020 may be incorporated in combination with the receiver 1010, the transmitter 1015, or both to receive information from the receiver 1010, send information to the transmitter 1015, or perform various other operations described herein, such as receiving or transmitting information.

[0171]

[0182] The communication manager 1020 may support wireless communication in a base station according to the examples disclosed herein. For example, the communication manager 1020 may be configured as or support means for transmitting downlink control information, including an uplink grant for a physical uplink shared channel, to a UE, where the downlink control information indicates a set of code points corresponding to a set of beam configurations. The communication manager 1020 may be configured as or support means for selecting a default uplink beam for receiving an uplink message on a physical uplink shared channel based on a beam configuration selection criterion indicating a criterion for selecting a subset of valid beam configurations from a set of beam configurations. The communication manager 1020 may be configured as or support means for receiving an uplink message on a physical uplink shared channel in accordance with an uplink grant using the default uplink beam.

[0172]

[0183] By including or comprising the communication manager 1020 according to the examples described herein, a device 1005 (e.g., a processor that controls or is otherwise coupled to a receiver 1010, a transmitter 1015, a communication manager 1020, or a combination thereof) may support techniques for selecting a default uplink beam that may result in a reduction in system latency, more efficient use of available resources, more efficient communication, more efficient use of computing resources, an increase in battery life, and an improved user experience.

[0173]

[0184] FIG. 11 shows a block diagram 1100 of a device 1105 that supports selecting a default beam configuration for uplink transmission according to an aspect of the present disclosure. The device 1105 may be an example of an aspect of the device 1005 or the base station 105 described herein. The device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. The device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0174]

[0185] The receiver 1110 may provide means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to selecting a default beam configuration for uplink transmission). The information may be passed to other components of the device 1105. The receiver 1110 may utilize a single antenna or a set of multiple antennas.

[0175]

[0186] The transmitter 1115 may provide means for transmitting signals generated by other components of the device 1105. For example, the transmitter 1115 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to default beam configuration selection for uplink transmission). In some examples, the transmitter 1115 may be collocated with the receiver 1110 in the transceiver module. The transmitter 1115 may utilize a single antenna or a set of multiple antennas.

[0176]

[0187] The device 1105, or its various components, may be an example of means for implementing various aspects of the default beam configuration selection for uplink transmission described herein. For example, the communication manager 1120 may include a DCI manager 1125, a beam configuration selection criterion manager 1130, an uplink message manager 1135, or any combination thereof. The communication manager 1120 may be an example of an aspect of the communication manager 1020 described herein. In some examples, the communication manager 1120, or its various components, may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise in cooperation with the receiver 1110, the transmitter 1115, or both. For example, the communication manager 1120 may be incorporated to receive information from the receiver 1110, send information to the transmitter 1115, or perform various other operations described herein in combination with the receiver 1110, the transmitter 1115, or both.

[0177]

[0188] The communication manager 1120 may support wireless communication in a base station according to the examples disclosed herein. The DCI manager 1125 is configured as or may support means for transmitting downlink control information, including uplink grants for the physical uplink shared channel, to a UE, where the downlink control information indicates a set of code points corresponding to a set of beam configurations. The beam configuration selection criterion manager 1130 is configured as or may support means for selecting a default uplink beam for receiving an uplink message on a physical uplink shared channel based on a beam configuration selection criterion indicating a criterion for selecting a subset of valid beam configurations from a set of beam configurations. The uplink message manager 1135 is configured as or may support means for receiving an uplink message on a physical uplink shared channel according to an uplink grant using the default uplink beam.

[0178]

[0189] FIG. 12 shows a block diagram 1200 of a communication manager 1220 that supports default beam configuration selection for uplink transmission according to an aspect of the present disclosure. The communication manager 1220 may be an example of the communication manager 1020, the communication manager 1120, or both aspects described herein. The communication manager 1220, or its various components, may be an example of means for implementing various aspects of default beam configuration selection for uplink transmission described herein. For example, the communication manager 1220 may include a DCI manager 1225, a beam configuration selection criterion manager 1230, an uplink message manager 1235, an iteration manager 1240, a CORESET index manager 1245, a DCI timing manager 1250, or any combination thereof. Each of these components may communicate with each other, directly or indirectly (e.g., via one or more buses).

[0179]

[0190] The communication manager 1220 may support wireless communication in a base station according to the examples disclosed herein. The DCI manager 1225 is configured as means for transmitting downlink control information including uplink grants for the physical uplink shared channel to the UE, or may support such means, where the downlink control information indicates a set of code points corresponding to a set of beam configurations. The beam configuration selection criterion manager 1230 is configured as means for selecting a default uplink beam for receiving an uplink message on the physical uplink shared channel based on a beam configuration selection criterion indicating a criterion for selecting a subset of valid beam configurations from a set of beam configurations, or may support such means. The uplink message manager 1235 is configured as means for receiving an uplink message on the physical uplink shared channel in accordance with an uplink grant using the default uplink beam, or may support such means.

[0180]

[0191] In some examples, the beam configuration selection criterion includes a restriction of the subset of valid beam configurations to beam configurations having a single uplink beam option.

[0181]

[0192] In some examples, the beam configuration selection criterion includes a restriction of the subset of valid beam configurations to beam configurations having a single uplink beam option, multiple uplink beam options, or both.

[0182]

[0193] In some examples, to support receiving an uplink message, the iteration manager 1240 may be configured as or support means for receiving a first iteration of the uplink message using a default uplink beam associated with a first uplink beam option of a plurality of uplink beam options. In some examples, to support receiving an uplink message, the iteration manager 1240 may be configured as or support means for receiving a second iteration of the uplink message using a second default uplink beam associated with a second uplink beam option of the plurality of uplink beam options.

[0183]

[0194] In some examples, to support transmitting downlink control information, the DCI manager 1225 may be configured as or support means for transmitting a first downlink control information message including an uplink grant for a physical uplink shared channel. In some examples, to support transmitting downlink control information, the DCI manager 1225 may be configured as or support means for transmitting a second downlink control information message including a set of code points before transmitting the first downlink control information message.

[0184]

[0195] In some examples, the CORESET index manager 1245 may be configured as or support means for receiving an uplink message on a default uplink beam based on the first control resource set pool index associated with a first downlink control information message being the same as the second control resource set pool index associated with a second downlink control information message.

[0185]

[0196] In some examples, the DCI timing manager 1250 may be configured as or support means for receiving an uplink message on a default uplink beam based on a time period between transmitting a second downlink control information message and transmitting a first downlink control information message satisfying a threshold timing gap.

[0186]

[0197] In some examples, the beam configuration selection criterion manager 1230 may be configured as or support means for transmitting an indication of beam configuration selection criteria to a UE, where receiving an uplink message on a default uplink beam is based on transmitting the indication of beam configuration selection criteria.

[0187]

[0198] FIG. 13 shows a diagram of a system 1300 including a device 1305 that supports default beam configuration selection for uplink transmission according to an aspect of the present disclosure. The device 1305 can be or include an example of a component of the device 1005, the device 1105, or the base station 105 described herein. The device 1305 can wirelessly communicate with one or more base stations 105, UE 115, or any combination thereof. The device 1305 can include components for transmitting and receiving communications, such as a communication manager 1320, a network communication manager 1310, a transceiver 1315, an antenna 1325, a memory 1330, a code 1335, a processor 1340, and an inter-station communication manager 1345, including components for two-way voice and data communication. These components can communicate electronically via one or more buses (e.g., bus 1350) or otherwise (e.g., operably, communicably, functionally, electronically, electrically) coupled.

[0188]

[0199] The network communication manager 1310 may manage communication with the core network 130 (e.g., via one or more wired backhaul links). For example, the network communication manager 1310 may manage the transfer of data communication of client devices, such as one or more UEs 115.

[0189]

[0200] In some cases, the device 1305 may include a single antenna 1325. However, in some other cases, the device 1305 may have multiple antennas 1325 that may have the ability to simultaneously transmit or receive multiple wireless transmissions. The transceiver 1315 may communicate bidirectionally via one or more antennas 1325, wired, or wireless links as described herein. For example, the transceiver 1315 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1315 may also include a modem for modulating packets, providing modulated packets to one or more antennas 1325 for transmission, and demodulating packets received from one or more antennas 1325. The transceiver 1315, or the transceiver 1315 and one or more antennas 1325, may be an example of a transmitter 1015, a transmitter 1115, a receiver 1010, a receiver 1110, or any combination thereof or components thereof as described herein.

[0190]

[0201] Memory 1330 may include RAM and ROM. When executed by processor 1340, memory 1330 may store computer-readable, computer-executable code 1335 that includes instructions to cause device 1305 to perform the various functions described herein. Code 1335 may be stored on a non-transitory computer-readable medium such as a system memory or another type of memory. In some cases, code 1335 may not be directly executable by processor 1340, but may cause a computer to perform the functions described herein (e.g., when compiled or executed). In some cases, memory 1330 may include a BIOS that can control basic hardware or software operations, particularly interactions with peripheral components or devices.

[0191]

[0202] Processor 1340 may include an intelligent hardware device (e.g., a general-purpose processor, DSP, CPU, microcontroller, ASIC, FPGA, programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1340 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into processor 1340. Processor 1340 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1330) to cause device 1305 to perform various functions (e.g., functions or tasks that support default beam configuration selection for uplink transmission). For example, device 1305 or components of device 1305 may include processor 1340 and memory 1330 coupled to processor 1340, and processor 1340 and memory 1330 are configured to perform the various functions described herein.

[0192]

[0203] The inter-site communication manager 1345 may manage communication with other base stations 105 and may include a controller or scheduler for controlling communication with the UE 115 in cooperation with other base stations 105. For example, the inter-site communication manager 1345 may coordinate a schedule for transmission to the UE 115 for various interference mitigation techniques such as beamforming or joint transmission. In some examples, the inter-site communication manager 1345 may provide an X2 interface within the LTE / LTE-A wireless communication network technology to provide communication between the base stations 105.

[0193]

[0204] The communication manager 1320 may support wireless communication in a base station according to the examples disclosed herein. For example, the communication manager 1320 may be configured as or otherwise support means for transmitting downlink control information, including uplink grants for a physical uplink shared channel, to a UE, where the downlink control information indicates a set of code points corresponding to a set of beam configurations. The communication manager 1320 may be configured as or otherwise support means for selecting a default uplink beam for receiving an uplink message on a physical uplink shared channel based on a beam configuration selection criterion indicating a criterion for selecting a subset of valid beam configurations from a set of beam configurations. The communication manager 1320 may be configured as or otherwise support means for receiving an uplink message on a physical uplink shared channel in accordance with an uplink grant using the default uplink beam.

[0194]

[0205] By including or configuring the device 1305 with the communication manager 1320 according to the examples described herein, techniques for selecting a default uplink beam may be supported that may result in a reduction in system latency, more efficient use of available resources, more efficient communication, more efficient use of computing resources, increased battery life, and an improved user experience.

[0195]

[0206] In some examples, communication manager 1320 may be configured to use transceiver 1315, one or more antennas 1325, or any combination thereof, or otherwise cooperate therewith, to perform various operations such as receiving, monitoring, and transmitting. Although communication manager 1320 is shown as a separate component, in some examples, one or more functions described with reference to communication manager 1320 may be supported or otherwise performed by processor 1340, memory 1330, code 1335, or any combination thereof. For example, code 1335 may include instructions executable by processor 1340 to cause device 1305 to perform various aspects of default beam configuration selection for uplink transmission as described herein, or processor 1340 and memory 1330 may otherwise be configured to perform or support such operations.

[0196]

[0207] FIG. 14 shows a flowchart illustrating a method 1400 for supporting default beam configuration selection for uplink transmission according to aspects of the present disclosure. The operations of method 1400 may be implemented by a UE or components thereof described herein. For example, the operations of method 1400 may be performed by UE 115 described with reference to FIGS. 1-9. In some examples, the UE may execute a set of instructions for controlling the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0197]

[0208] At 1405, the method may include receiving, from a base station, downlink control information including an uplink grant for a physical uplink shared channel, where the downlink control information indicates a set of code points corresponding to a set of beam configurations. The operation at 1405 may be performed according to the examples disclosed herein. In some examples, aspects of the operation at 1405 may be performed by DCI manager 825 described with reference to FIG. 8.

[0198]

[0209] At 1410, the method may include selecting a code point from a set of code points corresponding to a default uplink beam for transmitting an uplink message on a physical uplink shared channel based on a beam configuration selection criterion that indicates a criterion for selecting a subset of valid beam configurations from a set of beam configurations. The operation of 1410 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1410 may be performed by the beam configuration selection criterion manager 830 described with reference to FIG. 8.

[0199]

[0210] At 1415, the method may include transmitting an uplink message on a physical uplink shared channel according to an uplink grant using a default uplink beam. The operation of 1415 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1415 may be performed by the uplink message manager 835 described with reference to FIG. 8.

[0200]

[0211] FIG. 15 shows a flowchart illustrating a method 1500 for supporting default beam configuration selection for uplink transmission according to an aspect of the present disclosure. The operation of method 1500 may be implemented by the UE or a component thereof described herein. For example, the operation of method 1500 may be performed by the UE 115 described with reference to FIGS. 1-9. In some examples, the UE may execute a set of instructions for controlling the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0201]

[0212] At 1505, the method may include receiving, from a base station, downlink control information including an uplink grant for a physical uplink shared channel, where the downlink control information indicates a set of code points corresponding to a set of beam configurations. The operations at 1505 may be performed according to the examples disclosed herein. In some examples, aspects of the operations at 1505 may be performed by the DCI manager 825 described with reference to FIG. 8.

[0202]

[0213] At 1510, the method may include comparing code point identifiers of code points corresponding to a subset of valid beam configurations. The operations at 1510 may be performed according to the examples disclosed herein. In some examples, aspects of the operations at 1510 may be performed by the code point selection manager 840 described with reference to FIG. 8.

[0203]

[0214] At 1515, the method may include selecting a code point from a set of code points corresponding to a default uplink beam for transmitting an uplink message on a physical uplink shared channel based on an order of the compared code point identifiers, based on a beam configuration selection criterion indicating a criterion for selecting a subset of valid beam configurations from a set of beam configurations. The operations at 1515 may be performed according to the examples disclosed herein. In some examples, aspects of the operations at 1515 may be performed by the beam configuration selection criterion manager 830 described with reference to FIG. 8.

[0204]

[0215] At 1520, the method may include transmitting an uplink message on a physical uplink shared channel according to an uplink grant using a default uplink beam. The operations at 1520 may be performed according to the examples disclosed herein. In some examples, aspects of the operations at 1520 may be performed by the uplink message manager 835 described with reference to FIG. 8.

[0205]

[0216] FIG. 16 shows a flowchart of a method 1600 that supports default beam configuration selection for uplink transmission according to an aspect of the present disclosure. The operations of method 1600 may be implemented by a UE or a component thereof described herein. For example, the operations of method 1600 may be performed by UE 115 described with reference to FIGS. 1-9. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described functions.

[0206]

[0217] At 1605, the method may include receiving an indication of beam configuration selection criteria from a base station. The operation of 1605 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1605 may be performed by the beam configuration selection criteria manager 830 described with reference to FIG. 8.

[0207]

[0218] At 1610, the method may include receiving downlink control information including an uplink grant for a physical uplink shared channel from a base station, the downlink control information indicating a set of code points corresponding to a set of beam configurations. The operation of 1610 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 1610 may be performed by the DCI manager 825 described with reference to FIG. 8.

[0208]

[0219] At 1615, the method may include selecting a code point from a set of code points corresponding to a default uplink beam for transmitting an uplink message on a physical uplink shared channel based at least in part on a beam configuration selection criterion indicating criteria for selecting a subset of valid beam configurations from a set of beam configurations, where selecting the code point is based at least in part on receiving an indication of the beam configuration selection criterion. The operation of 1615 may be implemented according to the examples disclosed herein. In some examples, the manner of operation of 1615 may be implemented by the beam configuration selection manager 830 described with reference to FIG. 8.

[0209]

[0220] At 1620, the method may include transmitting an uplink message on a physical uplink shared channel according to an uplink grant using a default uplink beam. The operation of 1620 may be implemented according to the examples disclosed herein. In some examples, the manner of operation of 1620 may be implemented by the uplink message manager 835 described with reference to FIG. 8.

[0210]

[0221] FIG. 17 shows a flowchart illustrating a method 1700 for supporting default beam configuration selection for uplink transmission according to an aspect of the present disclosure. The operation of method 1700 may be implemented by the base station or a component thereof described herein. For example, the operation of method 1700 may be performed by the base station 105 described with reference to FIGS. 1 - 5 and FIGS. 10 - 13. In some examples, the base station may execute a set of instructions for controlling the functional elements of the base station to perform the functions described. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functions described.

[0211]

[0222] In 1705, the method may include transmitting downlink control information including an uplink grant for a physical uplink shared channel to a UE, where the downlink control information indicates a set of code points corresponding to a set of beam configurations. The operations of 1705 may be implemented according to the examples disclosed herein. In some examples, aspects of the operations of 1705 may be implemented by the DCI manager 1225 described with reference to FIG. 12.

[0212]

[0223] In 1710, the method may include selecting a default uplink beam for receiving an uplink message on a physical uplink shared channel based on a beam configuration selection criterion indicating a criterion for selecting a subset of valid beam configurations from a set of beam configurations. The operations of 1710 may be implemented according to the examples disclosed herein. In some examples, aspects of the operations of 1710 may be implemented by the beam configuration selection criterion manager 1230 described with reference to FIG. 12.

[0213]

[0224] In 1715, the method may include receiving an uplink message on a physical uplink shared channel according to an uplink grant using the default uplink beam. The operations of 1715 may be implemented according to the examples disclosed herein. In some examples, aspects of the operations of 1715 may be implemented by the uplink message manager 1235 described with reference to FIG. 12.

[0214]

[0225] Aspect 1: A method for wireless communication in a UE, comprising: receiving, from a base station, downlink control information comprising an uplink grant for a physical uplink shared channel; selecting a code point from a set of code points corresponding to a default uplink beam for transmitting an uplink message on the physical uplink shared channel based at least in part on a beam configuration selection criterion indicating a criterion for selecting a subset of valid beam configurations from a set of beam configurations, wherein the downlink control information indicates a set of code points corresponding to a set of beam configurations; and transmitting the uplink message on the physical uplink shared channel in accordance with the uplink grant using the default uplink beam.

[0215]

[0226] Aspect 2: The method according to aspect 1, further comprising comparing code point identifiers of code points corresponding to a subset of valid beam configurations, wherein selecting a code point from the set of code points is based at least in part on the order of the compared code point identifiers.

[0216]

[0227] Aspect 3: The method according to any one of aspects 1 to 2, further comprising selecting a subset of valid beam configurations based at least in part on the beam configuration selection criterion, wherein the beam configuration selection criterion comprises a restriction of the subset of valid beam configurations to beam configurations having a single uplink beam option.

[0217]

[0228] Aspect 4: The method according to any one of aspects 1 to 3, further comprising selecting a subset of valid beam configurations based at least in part on the beam configuration selection criterion, wherein the beam configuration selection criterion comprises a restriction of the subset of valid beam configurations to beam configurations having a single uplink beam option, a plurality of uplink beam options, or both. The method according to any one of aspects 1 to 3, further comprising.

[0218]

[0229] Aspect 5: Applying the rules indicated in the beam configuration selection criteria, where the rules comprise an instruction on which of a plurality of uplink beam options to select for transmitting an uplink message, and where selecting a code point from a set of code points is at least partially based on applying the rules, the method according to aspect 4, further comprising this.

[0219]

[0230] Aspect 6: Further comprising selecting a second code point from a set of code points corresponding to a second default uplink beam of a subset of valid beam configurations, at least partially based on the beam configuration selection criteria, the method according to any one of aspects 4 to 5.

[0220]

[0231] Aspect 7: Transmitting an uplink message comprises transmitting a first iteration of the uplink message using a default uplink beam and transmitting a second iteration of the uplink message using a second default uplink beam, the method according to aspect 6.

[0221]

[0232] Aspect 8: Receiving, in downlink control information, a beam switching instruction indicating which of a plurality of uplink beam options to select for transmitting an uplink message, and where selecting a code point from a set of code points is at least partially based on receiving the beam switching instruction, the method according to any one of aspects 4 to 7, further comprising this.

[0222]

[0233] Aspect 9: Receiving downlink control information comprises receiving a first downlink control information message comprising an uplink grant for a physical uplink shared channel and receiving a second downlink control information message comprising a set of code points, before receiving the first downlink control information message, the method according to any one of aspects 1 to 8.

[0223]

[0234] Aspect 10: Comparing a first control resource set pool index associated with a first downlink control information message with a second control resource set pool index associated with a second downlink control information message, and determining, at least in part based on the comparison, that the first control resource set pool index and the second control resource set pool index are the same, wherein selecting a code point is at least in part based on the first control resource set pool index and the second control resource set pool index being the same, the method according to aspect 9, further comprising this.

[0224]

[0235] Aspect 11: Determining that a time period between receiving a second downlink control information message and receiving a first downlink control information message meets a threshold timing gap, wherein selecting a code point is at least in part based on the determination, the method according to any one of aspects 9 to 10, further comprising this.

[0225]

[0236] Aspect 12: The method according to aspect 11, wherein at least one of the first downlink control information message or the second downlink control information message comprises a group common downlink control information message.

[0226]

[0237] Aspect 13: Receiving an indication of a threshold timing gap from a base station, wherein determining that the time period meets the threshold timing gap is at least in part based on receiving the indication of the threshold timing gap, the method according to any one of aspects 11 to 12, further comprising this.

[0227]

[0238] Aspect 14: Comparing a first time offset value with a second time offset value and selecting the first time offset value at least in part based on the comparison, where the first time offset value has a threshold timing gap, and where determining that a time period meets the threshold timing gap is at least in part based on selecting the first time offset value, the method according to any of Aspects 11 to 13, further comprising.

[0228]

[0239] Aspect 15: Receiving an indication of beam configuration selection criteria from a base station, where selecting a code point is at least in part based on receiving the indication of beam configuration selection criteria, the method according to any of Aspects 1 to 14, further comprising.

[0229]

[0240] Aspect 16: A method for wireless communication at a base station, comprising transmitting downlink control information comprising an uplink grant for a physical uplink shared channel to a UE, and selecting a default uplink beam for receiving an uplink message on the physical uplink shared channel at least in part based on beam configuration selection criteria indicating a criterion for selecting a subset of valid beam configurations from a set of beam configurations, where the downlink control information indicates a set of code points corresponding to a set of beam configurations, and receiving the uplink message on the physical uplink shared channel according to the uplink grant using the default uplink beam.

[0230]

[0241] Aspect 17: The method according to Aspect 16, where the beam configuration selection criteria comprise a restriction of the subset of valid beam configurations to beam configurations having a single uplink beam option.

[0231]

[0242] Aspect 18: The method according to any one of Aspects 16 to 17, wherein the beam configuration selection criterion comprises a restriction of a subset of valid beam configurations to a beam configuration having a single uplink beam option, a plurality of uplink beam options, or both.

[0232]

[0243] Aspect 19: Receiving an uplink message further comprises receiving a first iteration of the uplink message using a default uplink beam associated with a first uplink beam option among a plurality of uplink beam options, and receiving a second iteration of the uplink message using a second default uplink beam associated with a second uplink beam option among the plurality of uplink beam options. The method according to Aspect 18.

[0233]

[0244] Aspect 20: Transmitting downlink control information comprises transmitting a first downlink control information message comprising an uplink grant for a physical uplink shared channel, and transmitting a second downlink control information message comprising a set of code points before transmitting the first downlink control information message. The method according to any one of Aspects 16 to 19.

[0234]

[0245] Aspect 21: Receiving an uplink message on a default uplink beam is further based at least in part on the first control resource set pool index associated with the first downlink control information message being the same as the second control resource set pool index associated with the second downlink control information message. The method according to Aspect 20.

[0235]

[0246] Aspect 22: The method according to any one of Aspects 20 to 21, further comprising that receiving an uplink message on a default uplink beam is at least partially based on that a time period between transmitting a second downlink control information message and transmitting a first downlink control information message satisfies a threshold timing gap.

[0236]

[0247] Aspect 23: The method according to any one of Aspects 16 to 22, further comprising transmitting an indication of beam configuration selection criteria to a UE, wherein receiving an uplink message on a default uplink beam is at least partially based on transmitting the indication of beam configuration selection criteria.

[0237]

[0248] Aspect 24: An apparatus for wireless communication in a UE, comprising a processor, a memory coupled to the processor, and instructions stored in the memory, the instructions being executable by the processor to cause the apparatus to perform the method according to any one of Aspects 1 to 15.

[0238]

[0249] Aspect 25: An apparatus for wireless communication in a UE, comprising at least one means for performing the method according to any one of Aspects 1 to 15.

[0239]

[0250] Aspect 26: A non-transitory computer-readable medium storing code for wireless communication in a UE, the code comprising instructions executable by a processor to perform the method according to any one of Aspects 1 to 15.

[0240]

[0251] Aspect 27: An apparatus for wireless communication in a base station, comprising a processor, a memory coupled to the processor, and instructions stored in the memory, the instructions being executable by the processor to cause the apparatus to perform the method according to any one of Aspects 16 to 23.

[0241]

[0252] Aspect 28: An apparatus for wireless communication at a base station, the apparatus comprising at least one means for implementing the method according to any of Aspects 16 to 23.

[0242]

[0253] Aspect 29: A non-transitory computer-readable medium storing code for wireless communication at a base station, the code comprising instructions executable by a processor to implement the method according to any of Aspects 16 to 23.

[0243]

[0254] Note that the methods described herein are to illustrate possible implementations, and that operations and steps can be reordered or otherwise modified in some cases, and that other implementations are possible. Further, aspects from two or more of the methods can be combined.

[0244]

[0255] Aspects of LTE, LTE-A, LTE-A Pro, or NR systems can be described by way of example, and the terms LTE, LTE-A, LTE-A Pro, or NR can be used in most of the description, but the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques can be applicable to various other wireless communication systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0245]

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

[0246]

[0257] With respect to the disclosure of this specification, the various exemplary blocks and components described can be implemented or carried out using a general-purpose processor, DSP, ASIC, CPU, FPGA, or other programmable logic device, discrete gates or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor can be a microprocessor, but alternatively, the processor can be any processor, controller, microcontroller, or state machine. The processor can 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 cooperating with a DSP core, or any other such configuration).

[0247]

[0258] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions can be stored on a computer-readable medium as one or more instructions or code, or can be transmitted via a computer-readable medium. Other examples and implementations fall within the scope of the present 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 thereof. The features implementing the functions can also be physically located at various positions, including being distributed such that portions of the functions are implemented at different physical locations.

[0248]

[0259] A computer-readable medium includes both non-transitory computer storage media and communication media that facilitate transfer of a computer program from one location to another. The non-transitory storage media can be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM (registered trademark)), flash memory, compact disc (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory media that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer, or a general purpose or special purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. As used herein, disk and disc include CD, laser disc (registered trademark) (disc), optical disc (disc), digital versatile disc (disc) (DVD), floppy (registered trademark) disk (disk) and Blu-ray (registered trademark) disc (disc), where disk typically magnetically reproduces data and disc optically reproduces data with a laser. Combinations of the above are also included within the scope of computer-readable media.

[0249]

[0260] Throughout this specification, including within the claims, the term "or" as used in a list of items (e.g., a list of items that ends with a phrase such as "at least one of" or "one or more of") is intended to mean a non-exclusive list. For example, the listing of "at least one of A, B, or C" is intended to mean A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, the phrase "based on" as used in this specification is not to be construed as referring to a closed set of conditions. For example, an exemplary step described as "based on condition A" may, without departing from the scope of this disclosure, be based on both condition A and condition B. In other words, the phrase "based on" as used in this specification is to be construed in the same manner as the phrase "at least partially based on."

[0250]

[0261] The term "determine" or "determining" encompasses a variety of actions, and thus "determining" can include calculating, computing, processing, deriving, investigating, retrieving (such as via a search in a table, database, or other data structure), ascertaining, and the like. Also, "determining" can include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. Further, "determining" can include resolving, selecting, choosing, establishing, and other such similar actions.

[0251]

[0262] In the accompanying figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label with a dash and a second label that differentiates those similar components. If only the first reference label is used in this specification, the description applies to any of the similar components having the same first reference label, regardless of the second reference label or any other subsequent reference labels.

[0252]

[0263] The description set forth in this specification with respect to the accompanying drawings describes exemplary configurations and is not intended to represent all examples that may be implemented or fall within the scope of the claims. The term "exemplary" as used herein means "serving as an example, instance, or illustration" and does not mean "preferred" or "advantageous over other examples." The detailed description includes specific details to provide an understanding of the techniques described. However, these techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the examples being described.

[0253]

[0264] The description of this specification is provided so that those skilled in the art can make or use the present disclosure. Various modifications to the present disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Accordingly, the present disclosure should not be limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein. The invention described in the claims of the present application at the time of filing is appended below. [C1] A method for wireless communication in a user equipment (UE), comprising: receiving, from a base station, downlink control information comprising an uplink grant for a physical uplink shared channel, wherein the downlink control information indicates a set of code points corresponding to a set of beam configurations; selecting a code point from the set of code points corresponding to a default uplink beam for transmitting an uplink message on the physical uplink shared channel, based at least in part on a beam configuration selection criterion indicating a criterion for selecting a subset of valid beam configurations from the set of beam configurations; transmitting the uplink message on the physical uplink shared channel according to the uplink grant using the default uplink beam. A method comprising the above. [C2] comparing code point identifiers of code points corresponding to the subset of valid beam configurations, wherein selecting the code point from the set of code points is based at least in part on the order of the compared code point identifiers; The method according to C1, further comprising the above. [C3] selecting a subset of valid beam configurations based at least in part on the beam configuration selection criterion, wherein the beam configuration selection criterion comprises a restriction of the subset of valid beam configurations to a beam configuration having a single uplink beam option; The method according to C1, further comprising the above. [C4] selecting a subset of valid beam configurations based at least in part on the beam configuration selection criterion, wherein the beam configuration selection criterion comprises a restriction of the subset of valid beam configurations to a beam configuration having a single uplink beam option, a plurality of uplink beam options, or both; The method according to C1, further comprising the above. [C5] Applying the rules indicated in the beam configuration selection criteria, the rules comprising an instruction as to which of the plurality of uplink beam options to select for transmitting the uplink message, wherein selecting the code point from the set of code points is at least partially based on applying the rules. The method according to C4, further comprising. [C6] Selecting a second code point from the set of code points corresponding to a second default uplink beam of the subset of the valid beam configurations, at least partially based on the beam configuration selection criteria. The method according to C4, further comprising. [C7] Transmitting the uplink message. Transmitting a first repetition of the uplink message using the default uplink beam. Transmitting a second repetition of the uplink message using the second default uplink beam. The method according to C6, comprising. [C8] Receiving, in the downlink control information, a beam switching instruction indicating which of the plurality of uplink beam options to select for transmitting the uplink message, wherein selecting the code point from the set of code points is at least partially based on receiving the beam switching instruction. The method according to C4, further comprising. [C9] Receiving the downlink control information. Receiving a first downlink control information message comprising the uplink grant of the physical uplink shared channel. Receiving a second downlink control information message comprising the set of code points, before receiving the first downlink control information message. The method according to C1, comprising. [C10] Comparing a first control resource set pool index associated with the first downlink control information message with a second control resource set pool index associated with the second downlink control information message. Determining, at least in part based on said comparing, that the first control resource set pool index and the second control resource set pool index are the same, wherein selecting said code point is at least in part based on the first control resource set pool index and the second control resource set pool index being the same, The method according to C9, further comprising: [C11] Determining that a time period between receiving the second downlink control information message and receiving the first downlink control information message meets a threshold timing gap, wherein selecting said code point is at least in part based on said determining, The method according to C9, further comprising: [C12] The method according to C11, wherein at least one of the first downlink control information message or the second downlink control information message comprises a group common downlink control information message. [C13] Receiving an indication of the threshold timing gap from the base station, wherein determining that the time period meets the threshold timing gap is at least in part based on receiving the indication of the threshold timing gap, The method according to C11, further comprising: [C14] Comparing a first time offset value with a second time offset value; Selecting the first time offset value, at least in part based on said comparing, wherein the first time offset value comprises the threshold timing gap, and wherein determining that the time period meets the threshold timing gap is at least in part based on selecting the first time offset value, The method according to C11, further comprising: [C15] Receiving an indication of the beam configuration selection criterion from the base station, wherein selecting said code point is at least in part based on receiving the indication of the beam configuration selection criterion, The method according to C1, further comprising: [C16] A method for wireless communication at a base station, comprising: Transmitting downlink control information with an uplink grant for a physical uplink shared channel to a user equipment (UE), and the downlink control information indicates a set of code points corresponding to a set of beam configurations. Selecting a default uplink beam for receiving an uplink message on the physical uplink shared channel, at least partially based on a beam configuration selection criterion indicating a criterion for selecting a subset of valid beam configurations from the set of beam configurations. Receiving the uplink message on the physical uplink shared channel in accordance with the uplink grant using the default uplink beam. A method comprising the above. [C17] The method according to C16, wherein the beam configuration selection criterion comprises a restriction of the subset of valid beam configurations to a beam configuration having a single uplink beam option. [C18] The method according to C16, wherein the beam configuration selection criterion comprises a restriction of the subset of valid beam configurations to a beam configuration having a single uplink beam option, a plurality of uplink beam options, or both. [C19] Receiving the uplink message. Receiving a first repetition of the uplink message using the default uplink beam associated with a first uplink beam option among the plurality of uplink beam options. Receiving a second repetition of the uplink message using a second default uplink beam associated with a second uplink beam option among the plurality of uplink beam options. The method according to C18, further comprising the above. [C20] Transmitting the downlink control information. Transmitting a first downlink control information message with the uplink grant for the physical uplink shared channel. Transmitting a second downlink control information message comprising the set of code points before transmitting the first downlink control information message. The method according to C16, comprising the above. [C21] Receiving the uplink message on the default uplink beam is at least partially based on the first control resource set pool index associated with the first downlink control information message being the same as the second control resource set pool index associated with the second downlink control information message The method according to C20, further comprising this [C22] Receiving the uplink message on the default uplink beam is at least partially based on the time period between transmitting the second downlink control information message and transmitting the first downlink control information message satisfying a threshold timing gap The method according to C20, further comprising this [C23] Transmitting an indication of the beam configuration selection criterion to the UE, wherein receiving the uplink message on the default uplink beam is at least partially based on transmitting the indication of the beam configuration selection criterion The method according to C16, further comprising this [C24] An apparatus for wireless communication in a user equipment (UE), comprising a processor; a memory coupled to the processor; instructions stored in the memory; and the instructions cause the apparatus to receive, from a base station, downlink control information comprising an uplink grant for a physical uplink shared channel, the downlink control information indicating a set of code points corresponding to a set of beam configurations; select a code point from the set of code points corresponding to the default uplink beam for transmitting an uplink message on the physical uplink shared channel, based at least in part on a beam configuration selection criterion indicating a criterion for selecting a subset of valid beam configurations from the set of beam configurations; transmit the uplink message on the physical uplink shared channel in accordance with the uplink grant using the default uplink beam; An apparatus executable by the processor to cause the above [C25] The instructions cause the apparatus to Comparing code point identifiers of code points corresponding to a subset of the effective beam configurations, wherein selecting the code points from the set of code points is at least partially based on the order of the compared code point identifiers. The apparatus according to C24, further executable by the processor to cause the above to be performed. [C26] The instructions cause the apparatus to Select a subset of the effective beam configurations based at least in part on the beam configuration selection criteria, wherein the beam configuration selection criteria comprise a restriction of the subset of the effective beam configurations to beam configurations having a single uplink beam option. The apparatus according to C24, further executable by the processor to cause the above to be performed. [C27] The instructions cause the apparatus to Select a subset of the effective beam configurations based at least in part on the beam configuration selection criteria, wherein the beam configuration selection criteria comprise a restriction of the subset of the effective beam configurations to beam configurations having a single uplink beam option, a plurality of uplink beam options, or both. The apparatus according to C24, further executable by the processor to cause the above to be performed. [C28] The instructions for receiving the downlink control information cause the apparatus to Receive a first downlink control information message comprising the uplink grant of the physical uplink shared channel; and Receive a second downlink control information message comprising the set of code points before receiving the first downlink control information message. The apparatus according to C24, executable by the processor to cause the above to be performed. [C29] The instructions cause the apparatus to Receive an indication of the beam configuration selection criteria from the base station, wherein selecting the code points is at least partially based on receiving the indication of the beam configuration selection criteria. The apparatus according to C24, further executable by the processor to cause the above to be performed. [C30] An apparatus for wireless communication in a base station, comprising A processor; A memory coupled to the processor; and Instructions stored in the memory, wherein the instructions cause the apparatus to Transmitting downlink control information with an uplink grant for a physical uplink shared channel to a user equipment (UE), wherein the downlink control information indicates a set of code points corresponding to a set of beam configurations, selecting a default uplink beam for receiving an uplink message on the physical uplink shared channel based at least in part on a beam configuration selection criterion indicating a criterion for selecting a subset of valid beam configurations from the set of beam configurations, receiving the uplink message on the physical uplink shared channel in accordance with the uplink grant using the default uplink beam A device executable by the processor to cause the above to be performed.

Claims

1. A method for wireless communication in a user equipment (UE), comprising: receiving, from a base station, downlink control information comprising an uplink grant for a physical uplink shared channel, wherein the downlink control information indicates a set of code points corresponding to a set of beam configurations; selecting, from the set of code points, a code point corresponding to a default uplink beam for transmitting an uplink message on the physical uplink shared channel based on a beam configuration selection criterion indicating a criterion for selecting a subset of valid beam configurations from the set of beam configurations; transmitting the uplink message on the physical uplink shared channel according to the uplink grant using the default uplink beam; wherein receiving the downlink control information comprises receiving a first downlink control information message comprising the uplink grant for the physical uplink shared channel, and receiving a second downlink control information message comprising the set of code points prior to receiving the first downlink control information message.

2. comparing code point identifiers of code points corresponding to the subset of valid beam configurations, wherein selecting the code point from the set of code points is based on an order of the compared code point identifiers; The method according to claim 1, further comprising.

3. selecting the subset of valid beam configurations based on the beam configuration selection criterion, wherein the beam configuration selection criterion comprises a restriction of the subset of valid beam configurations to a beam configuration having a single uplink beam option, a plurality of uplink beam options, or both; The method according to claim 1, further comprising.

4. applying a rule indicated in the beam configuration selection criterion, the rule comprising an indication of which one of the plurality of uplink beam options to select for transmitting the uplink message, wherein selecting the code point from the set of code points is based on applying the rule; The method according to claim 3, further comprising.

5. Selecting, based on the beam configuration selection criteria, a second code point corresponding to a second default uplink beam of the subset of the effective beam configurations from the set of code points The method according to claim 3, further comprising.

6. Transmitting the uplink message is Transmitting a first repetition of the uplink message using the default uplink beam; and Transmitting a second repetition of the uplink message using the second default uplink beam The method according to claim 5, comprising.

7. Receiving, in the downlink control information, a beam switching indication indicating which one of the plurality of uplink beam options to select for transmitting the uplink message, wherein selecting the code point from the set of code points is based on receiving the beam switching indication. The method according to claim 3, further comprising.

8. Comparing a first control resource set pool index associated with the first downlink control information message with a second control resource set pool index associated with the second downlink control information message; Determining, based on the comparing, that the first control resource set pool index and the second control resource set pool index are the same, wherein selecting the code point is based on the first control resource set pool index and the second control resource set pool index being the same. The method according to claim 1, further comprising.

9. Determining that a time period between receiving the second downlink control information message and receiving the first downlink control information message meets a threshold timing gap, wherein selecting the code point is based on the determining. The method according to claim 1, further comprising.

10. The method according to claim 9, wherein at least one of the first downlink control information message or the second downlink control information message comprises a group common downlink control information message.

11. Receiving an indication of the threshold timing gap from the base station, wherein determining that the time period meets the threshold timing gap is based on receiving the indication of the threshold timing gap, The method according to claim 9, further comprising.

12. Comparing a first time offset value with a second time offset value, Selecting the first time offset value based on the comparing, wherein the first time offset value comprises the threshold timing gap, and wherein determining that the time period meets the threshold timing gap is based on selecting the first time offset value, The method according to claim 9, further comprising.

13. Receiving an indication of the beam configuration selection criterion from the base station, wherein selecting the code point is based on receiving the indication of the beam configuration selection criterion, The method according to claim 1, further comprising.

14. A method for wireless communication at a base station, Transmitting downlink control information comprising an uplink grant for a physical uplink shared channel to a user equipment (UE), wherein the downlink control information indicates a set of code points corresponding to a set of beam configurations, Selecting a default uplink beam for receiving an uplink message on the physical uplink shared channel based on a beam configuration selection criterion indicating a criterion for selecting a subset of valid beam configurations from the set of beam configurations, Receiving the uplink message on the physical uplink shared channel according to the uplink grant using the default uplink beam Comprising, Transmitting the downlink control information is, Transmitting a first downlink control information message comprising the uplink grant for the physical uplink shared channel, Transmitting a second downlink control information message comprising the set of code points before transmitting the first downlink control information message, A method comprising.

15. The method according to claim 14, wherein the beam configuration selection criterion comprises a restriction of a subset of the valid beam configurations to a beam configuration having a single uplink beam option, a plurality of uplink beam options, or both.

16. Receiving the uplink message comprises receiving a first repetition of the uplink message using the default uplink beam associated with a first uplink beam option among the plurality of uplink beam options; and receiving a second repetition of the uplink message using a second default uplink beam associated with a second uplink beam option among the plurality of uplink beam options. The method according to claim 15, further comprising the above.

17. Receiving the uplink message with the default uplink beam is based on that a first control resource set pool index associated with the first downlink control information message is the same as a second control resource set pool index associated with the second downlink control information message. The method according to claim 14, further comprising the above.

18. Receiving the uplink message with the default uplink beam is based on that a time period between transmitting the second downlink control information message and transmitting the first downlink control information message satisfies a threshold timing gap. The method according to claim 14, further comprising the above.

19. transmitting an indication of the beam configuration selection criterion to the UE, wherein receiving the uplink message with the default uplink beam is based on transmitting the indication of the beam configuration selection criterion. The method according to claim 14, further comprising the above.

20. An apparatus for wireless communication in a user equipment (UE), comprising a processor; a memory coupled to the processor; and instructions stored in the memory, wherein the instructions cause the apparatus to receive, from a base station, downlink control information comprising an uplink grant for a physical uplink shared channel, the downlink control information indicating a set of code points corresponding to a set of beam configurations. Based on beam configuration selection criteria indicating criteria for selecting a subset of valid beam configurations from the set of beam configurations, select, from the set of code points, a code point corresponding to a default uplink beam for transmitting an uplink message on the physical uplink shared channel; Transmit the uplink message on the physical uplink shared channel in accordance with the uplink grant using the default uplink beam which is executable by the processor to cause; Receiving the downlink control information, Receiving a first downlink control information message comprising the uplink grant for the physical uplink shared channel; Receiving a second downlink control information message comprising the set of code points, prior to receiving the first downlink control information message, a device comprising.

21. The instructions cause the device to Compare the code point identifiers of the code points corresponding to the subset of valid beam configurations, wherein selecting the code point from the set of code points is based on the order of the compared code point identifiers; The apparatus according to claim 20, which is further executable by the processor to cause.

22. The instructions cause the device to Select a subset of valid beam configurations based on the beam configuration selection criteria, wherein the beam configuration selection criteria comprises a restriction of the subset of valid beam configurations to a beam configuration having a single uplink beam option, a plurality of uplink beam options, or both; The apparatus according to claim 20, which is further executable by the processor to cause.

23. The instructions cause the device to Receive an indication of the beam configuration selection criteria from the base station, wherein selecting the code point is based on receiving the indication of the beam configuration selection criteria; The apparatus according to claim 20, which is further executable by the processor to cause.

24. An apparatus for wireless communication at a base station, A processor; A memory coupled to the processor; Instructions stored in the memory comprising, the instruction causes the apparatus to transmit downlink control information comprising an uplink grant for a physical uplink shared channel to a user equipment (UE), and the downlink control information indicates a set of code points corresponding to a set of beam configurations select a default uplink beam for receiving an uplink message on the physical uplink shared channel based on a beam configuration selection criterion indicating a criterion for selecting a subset of valid beam configurations from the set of beam configurations receive the uplink message on the physical uplink shared channel in accordance with the uplink grant using the default uplink beam is executable by the processor to cause the above to be performed, transmitting the downlink control information comprises transmitting a first downlink control information message comprising the uplink grant for the physical uplink shared channel transmitting a second downlink control information message comprising the set of code points before transmitting the first downlink control information message An apparatus comprising.

Images