Transmitter beam selection for pucch and pusch

Abstract

An exemplary implementation involves determining which instance of control information should be used for transmitter beam selection. The user equipment (UE) may receive a Media Access Control (MAC) element (CE) including first control information associated with transmitter beam selection, transmit an acknowledgment (ACK) to the network in response to receiving the MAC CE, and receive a downlink signal scheduled for uplink transmission via the Physical Downlink Control Channel (PDCCH). The downlink signal is received before the expiration of a predetermined duration relative to transmitting the ACK, and the downlink signal includes second control information associated with transmitter beam selection. The UE may also transmit an uplink signal based on the scheduled uplink transmission. The UE selects the transmitter beam for the uplink signal based on either the first or the second control information.

Description

Background Technology

[0001] User equipment (UE) can establish connections with at least one of several different networks or network types. In some networks, signaling between the UE and the network's cells can be achieved through beamforming, an antenna technique used to transmit or receive directional signals. On the transmitting side, beamforming may include propagating directional signals. The beamforming signal may be referred to as the transmitter beam.

[0002] During operation, the UE can select the transmitter beam for uplink transmission based at least in part on control information received from the cell. Under normal circumstances, the UE may receive multiple instances of control information. Each instance of control information may be applicable to the same uplink transmission but corresponds to a different transmitter beam. Therefore, a mechanism is needed that is configured to determine which instance of control information the UE should use to select the transmitter beam. Summary of the Invention

[0003] According to an exemplary embodiment, a method is performed at a user equipment (UE). The method includes receiving a Media Access Control (MAC) element (CE) including first control information associated with transmitter beam selection; transmitting an acknowledgment (ACK) to the network in response to receiving the MAC CE; and receiving a downlink signal scheduled for uplink transmission via a Physical Downlink Control Channel (PDCCH). The downlink signal is received before the expiration of a predetermined duration relative to the transmitted ACK, and the downlink signal includes second control information associated with transmitter beam selection. The method also includes transmitting the uplink signal based on the scheduled uplink transmission. The UE selects a transmitter beam for the uplink signal based on either the first or the second control information.

[0004] Another exemplary embodiment includes a transceiver configured to communicate with a network and a processor configured to perform operations. These operations include receiving a Media Access Control (MAC) element (CE) including first control information associated with transmitter beam selection, transmitting an acknowledgment (ACK) to the network in response to receiving the MAC CE, and receiving a downlink signal scheduled for uplink transmission via a Physical Downlink Control Channel (PDCCH). The downlink signal is received before the expiration of a predetermined duration relative to the transmitted ACK, and the downlink signal includes second control information associated with transmitter beam selection. The operations also include transmitting an uplink signal based on the scheduled uplink transmission. The UE selects the transmitter beam for the uplink signal based on either the first or second control information.

[0005] Another exemplary embodiment includes an integrated circuit. This integrated circuit includes circuitry configured to: receive a Media Access Control (MAC) element (CE) including first control information associated with a user equipment (UE) performing transmitter beam selection; transmit an acknowledgment (ACK) to the network in response to receiving the MAC CE; and receive a downlink signal scheduled for uplink transmission via a Physical Downlink Control Channel (PDCCH). The downlink signal, including second control information associated with transmitter beam selection, is received before the predetermined duration expires relative to the transmitted ACK. The integrated circuit also includes circuitry configured to transmit the uplink signal based on the scheduled uplink transmission. The UE selects the transmitter beam for the uplink signal based on either the first or second control information. Attached Figure Description

[0006] Figure 1 Exemplary network arrangements according to various exemplary implementations are shown.

[0007] Figure 2 Exemplary UEs according to various exemplary implementations are shown.

[0008] Figure 3 An exemplary scenario is shown in which the UE receives multiple instances of control information applicable to the same uplink transmission.

[0009] Figure 4 An exemplary scenario is shown according to various exemplary implementations, in which the UE selects a transmitter beam for aperiodic PUCCH transmission.

[0010] Figure 5 An exemplary scenario is shown according to various exemplary implementations, in which the UE selects a transmitter beam for aperiodic PUCCH transmission.

[0011] Figure 6 Exemplary scenarios according to various exemplary embodiments are shown, wherein when at least one PUCCH resource is configured in the same bandwidth portion (BWP), the UE selects the transmitter beam for PUSCH transmission scheduled by downlink control information (DCI) format 0_0.

[0012] Figure 7 Exemplary scenarios according to various exemplary embodiments are shown, wherein when no PUCCH resources are configured in the same BWP and at least one CORESET is configured, the UE selects a transmitter beam for PUSCH transmission scheduled by downlink control information (DCI) format 0_0.

[0013] Figure 8Exemplary scenarios according to various exemplary embodiments are shown, in which the UE selects a transmitter beam for PUSCH transmission scheduled by downlink control information (DCI) format 0_0 when no PUCCH resources are configured in the same BWP and no CORESET is configured. Detailed Implementation

[0014] The exemplary embodiments can be further understood with reference to the following description and related figures, wherein similar elements have the same reference numerals. The exemplary embodiments relate to a user equipment (UE) determining which instance of control information should be used for transmitter beam selection.

[0015] The exemplary embodiments are described with reference to beamforming, an antenna technique for transmitting and receiving directional signals. From the perspective of a transmitting device, beamforming can refer to the propagation of a directional signal. Throughout this specification, the beamforming signal may be referred to as the transmitter beam. Those skilled in the art will understand that the transmitter beam can vary in width and can propagate in any of a number of different directions.

[0016] Exemplary embodiments are also described with reference to cell communication between the UE and the network using a transmitter beam. However, the reference to the UE is provided for illustrative purposes only. The exemplary embodiments can be used with any electronic components capable of establishing a connection with the network and configured with hardware, software, and / or firmware for exchanging information and data with the network. Therefore, the UE described herein represents any electronic component capable of beamforming.

[0017] The network can be a 5G New Radio (NR) network, and the cell can be a next-generation node B (gNB). 5G NR networks can utilize millimeter-wave (mmWave) spectrum. The mmWave spectrum consists of frequency bands, each with a wavelength of 1-10 millimeters. mmWave frequency bands can be located between approximately 10 GHz and 300 GHz. However, references to 5G NR networks and gNBs are provided for illustrative purposes only. Exemplary implementations are applicable to any type of network and any type of cell within a corresponding network capable of beamforming.

[0018] The various examples described in this article involve scenarios where a cell transmits control information to a UE in multiple instances. Under normal circumstances, each instance of the control information may be applicable to the same uplink transmission, but corresponds to a different transmitter beam. For example, at the first moment, the UE may receive a downlink signal that includes control information applicable to subsequent uplink transmissions.

[0019] At a second time, prior to uplink transmission, the UE may receive additional downlink signals, including control information that is also applicable to the same uplink transmission. Specific examples of the types of downlink signals, control information, and uplink transmissions will be described in more detail below. Exemplary implementations relate to how the UE can determine which instance of control information to utilize to select the transmitter beam for uplink transmission.

[0020] Figure 1 A network arrangement 100 according to various exemplary embodiments is illustrated. This network arrangement 100 includes a UE 110. Those skilled in the art will understand that the UE 110 can be any type of electronic component capable of beamforming and configured to communicate via a network, such as a mobile phone, tablet, smartphone, phablet, embedded device, wearable device, Cat-M device, Cat-M1 device, MTC device, eMTC device, other types of Internet of Things (IoT) devices, etc. A practical network arrangement can include any number of UEs used by any number of users. Therefore, the example of a single UE 110 is provided merely for illustrative purposes.

[0021] UE 110 can be configured to communicate directly with one or more networks. In the example of network deployment 100, UE 110 can wirelessly communicate with a 5G New Radio (NR) radio access network (5G NR RAN) 120 and a wireless local access network (WLAN) 122. However, UE 110 can also communicate with other types of networks (e.g., LTE RAN, legacy RAN, etc.). UE 110 can also communicate with networks via a wired connection. Therefore, UE 110 may include a 5G NR chipset for communicating with the 5G NR RAN 120 and an ISM chipset for communicating with the WLAN 122.

[0022] The 5G NR RAN 120 can be part of a cellular network that can be deployed by network operators (e.g., Verizon, AT&T, Sprint, T-Mobile, etc.). The 5G NR RAN 120 may, for example, include cells or base stations (Node B, eNodeB, HeNB, eNBS, gNB, gNodeB, macrocell base stations, microcell base stations, small cell base stations, femtocell base stations, etc.) configured to send and receive communication traffic from UEs equipped with appropriate cellular chipsets. The WLAN 122 can include any type of wireless local area network (WiFi, hotspot, IEEE 802.11x network, etc.).

[0023] UE 110 can connect to 5G NR RAN 120 via Next-Generation Node B (gNB) 120A. Those skilled in the art will understand that any relevant procedures can be performed for UE 110 to connect to 5G NR RAN 120. For example, as described above, 5G NR RAN 120 can be associated with a specific network operator where UE 110 and / or its user have protocol and credential information (e.g., stored on a SIM card). Upon detecting the presence of 5G NR RAN 120, UE 110 can transmit the corresponding credential information to associate with 5G NR RAN 120. More specifically, UE 110 can be associated with a specific cell (e.g., gNB 120A of 5G NR RAN 120). As described above, the use of 5G NR RAN 120 is for illustrative purposes and any type of network can be used. For example, UE 110 can also connect to LTE-RAN (not shown) or legacy RAN (not shown).

[0024] In addition to networks 120 and 122, network deployment 100 also includes a cellular core network 130. Cellular core network 130 can be viewed as an interconnected set of components that manage the operation and traffic of the cellular network. Network deployment 100 also includes the Internet 140, an IP Multimedia Subsystem (IMS) 150, and a network services backbone 160. Cellular core network 130 also manages the traffic flowing between the cellular network and the Internet 140. IMS 150 can generally be described as an architecture for delivering multimedia services to UE 110 using IP protocols. IMS 150 can communicate with cellular core network 130 and Internet 140 to provide multimedia services to UE 110. Network services backbone 160 communicates directly or indirectly with Internet 140 and cellular core network 130. Network services backbone 160 can generally be described as a set of components (e.g., servers, network storage deployments, etc.) that implement a set of services that can be used to extend the functionality of UE 110 to communicate with various networks.

[0025] Figure 2 An exemplary UE 110 according to various exemplary embodiments is shown. Reference will be made to... Figure 1 The network layout 100 is used to describe UE 110. UE 110 can represent any electronic device and may include processor 205, memory layout 210, display device 215, input / output (I / O) device 220, transceiver 225, and other components 230. Other components 230 may include, for example, audio input devices, audio output devices, batteries providing a limited power source, data acquisition devices, ports for electrically connecting UE 110 to other electronic devices, sensors for detecting the status of UE 110, etc.

[0026] Processor 205 may be configured to execute multiple engines of UE 110. For example, an engine may include transmitter beam selection engine 235. Transmitter beam selection engine 235 may perform various operations related to selecting the transmitter beam to be used by UE 110 for uplink transmission.

[0027] The engine described above, as an application (e.g., a program) executed by processor 205, is merely exemplary. The functionality associated with the engine may also be represented as a separate, integrated component of UE 110, or as a modular component coupled to UE 110, such as an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry for receiving signals and processing circuitry for processing signals and other information. The engine may also be embodied as one application or multiple separate applications. Furthermore, in some UEs, the functionality described for processor 205 is distributed among two or more processors, such as a baseband processor and an application processor. Exemplary implementations can be implemented according to any of these or other configurations of the UE.

[0028] Memory 210 may be a hardware component configured to store data related to operations performed by UE 110. Display device 215 may be a hardware component configured to display data to a user, while I / O device 220 may be a hardware component enabling user input. Display device 215 and I / O device 220 may be separate components or may be integrated together (such as a touchscreen). Transceiver 225 may be a hardware component configured to establish connections with 5G NR-RAN 120 and WLAN 122. Therefore, transceiver 225 may operate on various frequencies or channels (e.g., a set of consecutive frequencies).

[0029] Figure 3 An exemplary scenario 300 is illustrated, in which UE 110 receives multiple instances of control information applicable to the same uplink transmission. Exemplary scenario 300 provides a general overview of the type of problem that the exemplary implementation aims to address.

[0030] Exemplary scenario 300 illustrates a timeline from the perspective of UE 110. In 305, UE 110 receives a Media Access Control (MAC) control element (CE). Generally, a MAC CE may include control information indicating to UE 110 the transmitter beam to be used for subsequent uplink transmissions. In 310, UE 110 transmits an acknowledgment (ACK) to the network, indicating that UE 110 has successfully received the MAC CE in 305. Depending on various standards and / or to ensure that the cell is configured to receive the transmitter beam indicated in 305, UE 110 may be configured to apply the control information to transmissions performed after a predetermined duration 315 (e.g., 3 milliseconds (MS)) has elapsed.

[0031] In step 320, UE 110 receives a signal via the Physical Downlink Control Channel (PDCCH) before the predetermined duration 315 expires. This signal can schedule subsequent uplink transmissions via either the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH). Furthermore, this signal may also include an indication of the transmitter beams available for scheduling uplink transmissions.

[0032] The uplink transmission is scheduled to occur at 325 after a predetermined duration 315 has ended. Therefore, from the perspective of UE 110, both the transmitter beam indicated via MAC CE in 305 and the transmitter beam indicated via PDCCH in 320 are applicable to the scheduled uplink transmission 325. An exemplary implementation involves UE 110 determining which transmitter beam should be used for the uplink transmission in 325.

[0033] Figure 4 An exemplary scenario 400 is illustrated according to various exemplary embodiments, wherein UE 110 selects a transmitter beam for aperiodic PUCCH transmission. Exemplary scenario 400 relates to UE 110 performing aperiodic PUCCH transmission. Exemplary scenario 400 illustrates a timeline from the perspective of UE 110.

[0034] In step 405, UE 110 receives a MAC CE. In this example, the MAC CE may include a beam indication for a specific PUCCH resource (x) or a group of PUCCH resources including PUCCH resource (x). The beam indication may include spatial relationship information indicating the correlation between the downlink signal received in step 405 and a specific transmitter beam. Therefore, UE 110 may select a transmitter beam based on the spatial relationship information included in the beam indication.

[0035] In 410, UE 110 transmits an ACK to indicate to the cell that UE 110 has successfully received the MAC CE in 405. Depending on various standards and / or to ensure that the cell is configured to receive the transmitter beam selected by UE 110 based on the spatial relation information received in 405, UE 110 may be configured to apply the spatial relation information to PUCCH transmissions performed after a predetermined duration 415 has ended.

[0036] In 420, UE 110 receives a signal via PDCCH. This signal can trigger an uplink transmission on PUCCH resource (x) and includes spatial relation information. The uplink transmission on PUCCH resource (x) is scheduled to occur at 425. At this time, UE 110 has two options for transmitter beam selection. The first option for UE 110 is to select the transmitter beam for the scheduled aperiodic PUCCH transmission in 425 based on the spatial relation information indicated in the signal received via PDCCH in 420. The second option for UE 110 is to select the transmitter beam for the scheduled aperiodic PUCCH transmission in 425 based on the spatial relation information indicated in the MAC CE received in 405.

[0037] In some exemplary implementations, UE 110 may be pre-configured to use either the first option or the second option in this scenario. UE 110 may indicate to the cell in a UE Capability Information message whether UE 110 is pre-configured to use the spatial relationship information indicated in the MAC CE or the spatial relationship information indicated in the PDCCH. In other exemplary implementations, the network may configure UE 110 to either the first option or the second option in this scenario. The network may, for example, use a MAC CE or Radio Resource Control (RRC) message to configure UE 110 with either the first or second option.

[0038] Figure 5 An exemplary scenario 500 according to various exemplary embodiments is shown, in which UE 110 selects a transmitter beam for aperiodic PUCCH transmission. Unlike exemplary scenario 400, spatial relationship information is not explicitly indicated to UE 110 in exemplary scenario 500, as will be described in more detail below.

[0039] Exemplary scenario 500 involves UE 110 performing aperiodic PUCCH transmissions. Exemplary scenario 500 illustrates a timeline from the perspective of UE 110.

[0040] In 505, UE 110 receives a MAC CE. In this example, the MAC CE may indicate a specific Transport Configuration Indicator (TCI) for a Control Resource Set (CORESET). UE 110 may apply the TCI indicated in this MAC CE for a specific PUCCH resource (x) or a group of PUCCH resources including PUCCH resource (x).

[0041] In step 510, UE 110 transmits an ACK to indicate to the cell that UE 110 has successfully received the MAC CE in step 505. Depending on various standards and / or to ensure the cell is configured to receive the transmitter beam selected by UE 110 based on the TCI state indicated in the MAC CE received in step 505, UE 110 may be configured to apply this control information to PUCCH transmissions performed after a predetermined duration 515 has ended.

[0042] In 520, UE 110 receives a signal via PDCCH. This signal can trigger an uplink transmission on PUCCH resource (x) and can also indicate a TCI for the CORESET. The uplink transmission on PUCCH resource (x) is scheduled to occur at 525. At this time, UE 110 has two options for transmitter beam selection. The first option for UE 110 is: based on the TCI indicated in the signal received via PDCCH in 520 for the CORESET with the lowest ID in the same bandwidth portion (BWP) of the time slot with scheduled PDCCH, select the transmitter beam for the scheduled aperiodic PUCCH transmission in 525. The second option for UE 110 is: based on the TCI indicated in the MAC CE received in 505 for the CORESET with the lowest ID in the same BWP of the time slot with scheduled PUCCH, select the transmitter beam for the scheduled aperiodic PUCCH transmission in 525.

[0043] In some implementations, UE 110 may be pre-configured to use either the first option or the second option in this scenario. UE 110 may indicate to the cell in a UE Capability Information message whether UE 110 is pre-configured to use the TCI indicated in the MAC CE or the TCI indicated in the PDCCH. In other implementations, the network may configure UE 110 to use either the first option or the second option in this scenario. The network may use, for example, MAC CE or RRC messages to configure UE 110 with either the first or second option.

[0044] Figure 6 An exemplary scenario 600 according to various exemplary embodiments is shown, wherein when at least one PUCCH resource is configured in the same BWP as the PUSCH, the UE 110 selects a transmitter beam for PUSCH transmission scheduled by downlink control information (DCI) format 0_0.

[0045] Exemplary scenario 600 involves UE 110 performing a PUSCH transmission. Exemplary scenario 600 illustrates a timeline from the perspective of UE 110.

[0046] In step 605, UE 110 receives a MAC CE. In this example, the MAC CE may include a beam indication for a specific PUCCH resource (x) or a group of PUCCH resources including PUCCH resource (x). The beam indication may include spatial relationship information indicating the correlation between the downlink signal received in step 605 and a specific transmitter beam. Therefore, UE 110 may select the transmitter beam for PUSCH transmission based on the spatial relationship information included in the beam indication for the PUCCH resource.

[0047] In step 610, UE 110 transmits an ACK to indicate to the cell that UE 110 has successfully received the MAC CE in step 605. Depending on various standards and / or to ensure the cell is configured to receive the transmitter beam selected by UE 110 based on the spatial relation information received in step 605, UE 110 may be configured to apply the spatial relation information to PUSCH transmissions performed after a predetermined duration 615 has ended.

[0048] At 620, UE 110 receives a signal via the PDCCH. This signal can trigger an uplink transmission via the PUSCH and includes spatial relation information. The uplink transmission via the PUSCH is scheduled to occur at 625. At this point, UE 110 has two options for transmitter beam selection. The first option for UE 110 is: based on the spatial relation information for the PUCCH with the lowest resource ID in the time slot where the PDCCH is scheduled, select the transmitter beam for the scheduled PUSCH transmission at 625.

[0049] The second option for UE 110 is to select the transmitter beam for scheduled PUSCH transmission in 625 based on the spatial relationship information indicated in the MAC CE received in 605.

[0050] In some implementations, UE 110 may be pre-configured to use either the first option or the second option in this scenario. UE 110 may indicate to the cell in a UE Capability Information message whether UE 110 is pre-configured to use the spatial relationship information indicated in the MAC CE or the spatial relationship information indicated in the PDCCH. In other implementations, the network may configure UE 110 to use either the first option or the second option in this scenario. The network may configure UE 110 with the first option or the second option using MAC CE or RRC messages.

[0051] Figure 7An exemplary scenario 700 according to various exemplary embodiments is shown, wherein when no PUCCH resource is configured in the same BWP as the PUSCH and at least one CORESET is configured, UE 110 selects a transmitter beam for PUSCH transmission scheduled by downlink control information (DCI) format 0_0.

[0052] Exemplary scenario 700 involves UE 110 performing a PUSCH transmission. Exemplary scenario 700 illustrates a timeline from the perspective of UE 110.

[0053] In 705, UE 110 receives a MAC CE. In this example, the MAC CE can indicate a specific TCI for the CORESET with the lowest ID in the current BWP.

[0054] In 710, UE 110 transmits an ACK to indicate to the cell that UE 110 has successfully received the MAC CE in 705. Depending on various standards and / or to ensure the cell is configured to receive the transmitter beam selected by UE 110 based on the TCI state indicated in the MAC CE received in 705, UE 110 may be configured to apply this control information to PUSCH transmissions performed after a predetermined duration 715 has ended.

[0055] At 720, UE 110 receives a signal via the PDCCH. This signal can trigger an uplink transmission via the PUSCH and includes a TCI indication. The uplink transmission via the PUSCH is scheduled to occur at 725. At this point, UE 110 has two options for transmitter beam selection. The first option for UE 110 is to select the transmitter beam for the scheduled PUSCH transmission at 725 based on the TCI state of the lowest ID CORESEST in the same BWP within the time slot with the scheduled PDCCH. The second option for UE 110 is to select the transmitter beam for the scheduled PUSCH transmission at 725 based on the TCI state of the lowest ID CORESEST in the same BWP within the time slot with the scheduled PUSCH.

[0056] In some implementations, UE 110 may be pre-configured to use either the first option or the second option in this scenario. UE 110 may indicate to the cell in a UE Capability Information message whether UE 110 is pre-configured to use the TCI indicated in the MAC CE or the TCI indicated in the PDCCH. In other implementations, the network may configure UE 110 to use either the first option or the second option in this scenario. The network may configure UE 110 with the first option or the second option using a MAC CE or RRC message.

[0057] In some implementations, the CORSESET TCI update can also instruct the TCI to be updated via a random access procedure. In this configuration, the TCI can be updated after N symbols following the Physical Random Access Channel (PRACH). This is the opposite of the predetermined duration mentioned above.

[0058] Figure 8 An exemplary scenario 800 according to various exemplary embodiments is shown, wherein when no PUCCH resources are configured in the same BWP and no CORESET is configured, UE 110 selects a transmitter beam for PUSCH transmission scheduled by downlink control information (DCI) format 0_0.

[0059] Exemplary scenario 800 involves UE 110 performing a PUSCH transmission. Exemplary scenario 800 illustrates a timeline from the perspective of UE 110.

[0060] In 805, UE 110 receives a MAC CE. In this example, the MAC CE can indicate a specific TCI for the Physical Downlink Shared Channel (PDSCH). MAC CE-based TCI activation for the PDSCH can instruct the MAC CE to activate one or more TCI states for the PDSCH in an active BWP or to activate TCI states for the PDSCH in all serving cells.

[0061] In 810, UE 110 transmits an ACK to indicate to the cell that UE 110 has successfully received the MAC CE in 805. Depending on various standards and / or to ensure the cell is configured to receive the transmitter beam selected by UE 110 based on the TCI state indicated in the MAC CE received in 805, UE 110 may be configured to apply this control information to PUSCH transmissions performed after a predetermined duration 815 has ended.

[0062] In step 820, UE 110 receives a signal via the PDCCH. This signal can trigger an uplink transmission via the PUSCH and includes a TCI indication for the PDSCH. The uplink transmission via the PUSCH is scheduled to occur at step 825. At this point, UE 110 has two options for transmitter beam selection. The first option for UE 110 is to select the transmitter beam for the scheduled PUSCH transmission in step 825 based on the TCI state of the PDSCH with the lowest ID in the same BWP within the time slot with the scheduled PDCCH. The second option for UE 110 is to select the transmitter beam for the scheduled PUSCH transmission in step 825 based on the TCI state of the PDSCH with the lowest ID in the same BWP within the time slot with the scheduled PUSCH.

[0063] In some implementations, UE 110 may be pre-configured to use either the first option or the second option in this scenario. UE 110 may indicate to the cell in a UE Capability Information message whether UE 110 is pre-configured to use the TCI indicated in the MAC CE or the TCI indicated in the PDCCH. In other implementations, the network may configure UE 110 to use either the first option or the second option in this scenario. The network may configure UE 110 with the first option or the second option using a MAC CE or RRC message.

[0064] Those skilled in the art will understand that the exemplary embodiments described above can be implemented with any suitable software or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, and mobile devices with operating systems such as iOS, Android, etc. In other examples, exemplary embodiments of the methods described above may be embodied as programs comprising lines of code stored on a non-transitory computer-readable storage medium, which, at compile time, can be executed on a processor or microprocessor.

[0065] Although this patent application describes various combinations of various embodiments, each with different features, those skilled in the art will understand that any feature of an embodiment can be combined with features of other embodiments or features that are not functionally or logically inconsistent with the operation or function of the device of the disclosed embodiment of the invention in any manner not explicitly denied.

[0066] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0067] It will be apparent to those skilled in the art that various modifications can be made to this disclosure without departing from its spirit or scope. Therefore, this disclosure is intended to cover all modifications and variations thereof, provided that such modifications and variations are within the scope of the appended claims and their equivalents.

Claims

1. A method for wireless communication, comprising: At the User Equipment (UE): Transmit UE capability information to the network, wherein the UE capability information indicates to the network which UE is configured to use either first control information or second control information as the basis for selecting the transmitter beam; Receive medium access control (MAC) control element (CE), wherein the MAC CE includes the first control information associated with transmitter beam selection; In response to receiving the MAC CE, an acknowledgment (ACK) is sent to the network. Downlink signals for scheduling uplink transmissions are received via the Physical Downlink Control Channel (PDCCH), wherein the downlink signals are received before the expiration of a predetermined duration relative to the transmission of the ACK, and wherein the downlink signals include the second control information associated with transmitter beam selection; as well as The UE transmits an uplink signal based on a scheduled uplink transmission, wherein the UE selects the transmitter beam for the uplink signal based on either the first control information or the second control information.

2. The method according to claim 1, further comprising: The system receives a signal from the network, wherein the signal instructs the UE which of the first control information or the second control information will be used as the basis for selecting the transmitter beam.

3. The method according to claim 1, wherein the first control information is a first spatial relationship indication, the second control information is a second spatial relationship indication, and the uplink transmission is scheduled for the Physical Uplink Control Channel (PUCCH).

4. The method of claim 1, wherein the first control information is a first transmission configuration indicator (TCI), the second control information is a second TCI, and the uplink transmission is scheduled for the physical uplink control channel (PUCCH).

5. The method of claim 1, wherein the first control information is a first spatial relationship indication, the second control information is a second spatial relationship indication, and the uplink transmission is scheduled for the Physical Uplink Shared Channel (PUSCH).

6. The method of claim 5, wherein the uplink transmission is scheduled by downlink control information (DCI) format 0_0, and at least one physical uplink control channel (PUCCH) resource is scheduled in the same bandwidth portion (BWP) as the PUSCH.

7. The method of claim 5, wherein the uplink transmission is scheduled by downlink control information (DCI) format 0_0, no physical uplink control channel (PUCCH) resources are configured in the same bandwidth portion (BWP) as the PUSCH, and at least one control resource set (CORESET) is configured.

8. The method of claim 5, wherein the uplink transmission is scheduled by downlink control information (DCI) format 0_0, no physical uplink control channel (PUCCH) resources are configured in the same bandwidth portion (BWP) as the PUSCH, and no control resource set (CORESET) is configured.

9. A user equipment (UE), comprising: A transceiver configured to communicate with a network; as well as A processor configured to perform operations including: Transmit UE capability information to the network, wherein the UE capability information indicates to the network which UE is configured to use either first control information or second control information as the basis for selecting the transmitter beam; Receive medium access control (MAC) control element (CE), wherein the MAC CE includes the first control information associated with transmitter beam selection; In response to receiving the MAC CE, an acknowledgment (ACK) is sent to the network. Downlink signals for scheduling uplink transmissions are received via the Physical Downlink Control Channel (PDCCH), wherein the downlink signals are received before the expiration of a predetermined duration relative to the transmission of the ACK, and wherein the downlink signals include the second control information associated with transmitter beam selection; and The UE transmits an uplink signal based on a scheduled uplink transmission, wherein the UE selects the transmitter beam for the uplink signal based on either the first control information or the second control information.

10. The UE of claim 9, wherein the first control information is a first spatial relationship indication, the second control information is a second spatial relationship indication, and the uplink transmission is scheduled for the Physical Uplink Control Channel (PUCCH).

11. The UE of claim 9, wherein the first control information is a first transmission configuration indicator (TCI), the second control information is a second TCI, and the uplink transmission is scheduled for the physical uplink control channel (PUCCH).

12. The UE of claim 9, wherein the first control information is a first spatial relationship indication, the second control information is a second spatial relationship indication, and the uplink transmission is scheduled for the Physical Uplink Shared Channel (PUSCH).

13. The UE of claim 12, wherein the uplink transmission is scheduled by downlink control information (DCI) format 0_0, and at least one physical uplink control channel (PUCCH) resource is scheduled in the same bandwidth portion (BWP) as the PUSCH.

14. The UE of claim 12, wherein the uplink transmission is scheduled by downlink control information (DCI) format 0_0, no physical uplink control channel (PUCCH) resources are configured in the same bandwidth portion (BWP) as the PUSCH, and at least one control resource set (CORESET) is configured.

15. The UE of claim 12, wherein the uplink transmission is scheduled by downlink control information (DCI) format 0_0, no physical uplink control channel (PUCCH) resources are configured in the same bandwidth portion (BWP) as the PUSCH, and no control resource set (CORESET) is configured.

16. An integrated circuit, comprising: A circuit configured to transmit user equipment (UE) capability information to a network, wherein the UE capability information indicates to the network which UE is configured to use either first control information or second control information as the basis for selecting a transmitter beam; A circuit configured to receive a medium access control (MAC) control element (CE), wherein the MAC CE includes the first control information associated with the UE performing transmitter beam selection; A circuit configured to respond to receiving an acknowledgment (ACK) sent to the network by the MAC CE; A circuit configured to receive downlink signals scheduled for uplink transmission via a physical downlink control channel (PDCCH), wherein the downlink signals are received prior to the expiration of a predetermined duration relative to the transmission of the ACK, and wherein the downlink signals include the second control information associated with transmitter beam selection; as well as A circuit configured to transmit uplink signals based on scheduled uplink transmissions, wherein the UE selects the transmitter beam for the uplink signal based on either the first control information or the second control information.

17. The integrated circuit according to claim 16, further comprising: A circuit configured to receive signals from the network, wherein the signals indicate to the UE which of the first control information or the second control information the UE will use as the basis for selecting the transmitter beam.

18. The integrated circuit of claim 16, wherein the first control information is a first spatial relationship indication, the second control information is a second spatial relationship indication, and the uplink transmission is scheduled for one of the Physical Uplink Control Channel (PUCCH) or the Physical Uplink Shared Channel (PUSCH).

Images