DEFAULT BEAMS FOR PDSCH, CSI-RS, PUCCH AND SRS

A method and apparatus configuring default beams are described. In some embodiments, the method of wireless communication at a User Equipment (UE) comprises: receiving, from a base station, configuration information for configuring a default beam for the physical downlink shared channel (PDSCH) to use on condition that an offset between reception of downlink control information (DCI) in the scheduling physical downlink control channel (PDCCH) and corresponding PDSCH is less than a threshold and at least one Transmission Configuration Indicator (ICI) states includes spatial receiving parameters for configuring a quasi-co-location; configuring, by the UE, a default beam configuration for the PDSCH based on the configuration information and a monitored control resource set (CORESET) with a lowest CORESET identifier (ID) from among a set of CORESETs in a latest slot in a same bandwidth part (BWP), wherein at least one CORSET of the set of CORESETs includes more than one TCI state; and receiving a transmission using the default beam.

FIELD OF INVENTION

Embodiments described herein relate generally to wireless technology and more particularly to default beams in new radio (NR).

BACKGROUND

Fifth generation mobile network (5G) is a wireless standard that aims to improve upon data transmission speed, reliability, availability, and more. This standard, while still developing, includes numerous details relating to various aspects of wireless communication, for example, NR and NR in a spectrum greater than 52.6 GHz.

SUMMARY OF THE DESCRIPTION

A method and apparatus configuring default beams are described. In some embodiments, the method of wireless communication at a User Equipment (II E) comprises: receiving, from a base station, configuration information for configuring a default beam for the physical downlink shared channel (PDSCH) to use on condition that an offset between reception of downlink control information (DCI) in the scheduling physical downlink control channel (PDCCH) and corresponding PDSCH is less than a threshold and at least one Transmission Configuration Indicator (TCI) states includes spatial receiving parameters for configuring a quasi-co-location; configuring, by the UE, a default beam configuration for the PDSCH based on the configuration information and a monitored control resource set (CORESET) with a lowest CORESET identifier (ID) from among a set of CORESETs in a latest slot in a same bandwidth part (BWP), wherein at least one CORSET of the set of CORESETs includes more than one TCI state; and receiving a transmission using the default beam.

A method of wireless communication at a User Equipment (UE) comprising: receiving, from a base station, configuration information for a default Physical Uplink Control Channel/Sounding Reference Signal (PUCCH/SRS) beam and pathloss reference signal (RS); configuring, by the UE, the default PUCCH/SRS beam and pathloss RS based on the configuration information and a monitored control resource set (CORESET) with a lowest CORESET identifier (ID) from among a set of CORESETs in a same bandwidth part (BWP); and sending a transmission using the default PUCCH/SRS beam.

A method for use in a base station, the method comprising: determining a configuration for a wireless device, wherein the configuration is included in configuration information that specifies one or more of: a default beam configuration for the physical downlink shared channel (PDSCH) to use on condition that an offset between reception of downlink control information (DCI) in the scheduling physical downlink control channel (PDCCH) and corresponding PDSCH is less than a threshold and at least one Transmission Configuration Indicator (TCI) states includes spatial receiving parameters for configuring a quasi-co-location, and a default PUCCH/SRS beam and pathloss reference signal (RS); and transmitting, to a UE, the configuration information identifying a default configuration for one or more of the default PUCCH/SRS beam and pathloss reference signal (RS) and the default PUCCH/SRS beam and pathloss reference signal (RS), wherein the default PDSCH beam configuration is based on the configuration information and a monitored control resource set (CORESET) with a lowest CORESET identifier (ID) from among a set of CORESETs in a latest slot in a same bandwidth part (BWP), wherein at least one CORSET of the set of CORESETs includes more than one TCI state; and wherein the default PUCCH/SRS beam and pathloss RS based on the configuration information and a monitored CORESET with a lowest CORESET identifier (ID) from among a set of CORESETs in a same BWP.

Other methods and apparatuses are also described.

DETAILED DESCRIPTION

A method and apparatus of a device that determines default beams is described. In the following description, numerous specific details are set forth to provide thorough explanation of embodiments of the present disclosure. It will be apparent, however, to one skilled in the art, that embodiments of the present disclosure may be practiced without these specific details. In other instances, well-known components, structures, and techniques have not been shown in detail in order not to obscure the understanding of this description.

Reference in the specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the disclosure. The appearances of the phrase “in one embodiment” in various places in the specification do not necessarily all refer to the same embodiment.

The terms “server,” “client,” and “device” are intended to refer generally to data processing systems rather than specifically to a particular form factor for the server, client, and/or device.

A method and apparatus of a device (e.g., a UE) that determines default beams to use for communication between a base station and a UE. In some embodiments, these default beams are for a default beam for the physical downlink shared channel (PDSCH), a default aperiodic Channel Status Information-Reference Signal (CSI-RS) beam, and/or a default PUCCH/SRS beam and pathloss reference signal (RS). The device may determine the default beams to use based on configuration information. In one embodiment, the configuration information is from a gNB (e.g., a base station). In some embodiments, the default beams are determined when there are two Transmission Configuration Indicator (TCI) states configured in a selected or monitored control resource set (CORESET). In some embodiments, the default beams are determined based on one or more (e.g., two) of the TCI states of a CORESET.

FIG.1illustrates a simplified example wireless communication system, according to some embodiments. It is noted that the system ofFIG.1is merely one example of a possible system, and that features of this disclosure may be implemented in any of various systems, as desired.

The base station (BS)102A may be a base transceiver station (BTS) or cell site (a “cellular base station”) and may include hardware that enables wireless communication with the UEs106A through106N.

As shown, the base station102A may also be equipped to communicate with a network100(e.g., a core network of a cellular service provider, a telecommunication network such as a public switched telephone network (PSTN), and/or the Internet, among various possibilities). Thus, the base station102A may facilitate communication between the user devices and/or between the user devices and the network100. In particular, the cellular base station102A may provide UEs106with various telecommunication capabilities, such as voice, SMS and/or data services.

In some embodiments, base station102A may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In some embodiments, a gNB may be connected to a legacy evolved packet core (EPC) network and/or to a NR core (NRC) network. In addition, a gNB cell may include one or more transition and reception points (TRPs). In addition, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.

FIG.2illustrates user equipment106(e.g., one of the devices106A through106N) in communication with a base station102, according to some embodiments. The UE106may be a device with cellular communication capability such as a mobile phone, a hand-held device, a computer or a tablet, or virtually any type of wireless device.

FIG.3—Block Diagram of a UE

FIG.3illustrates an example simplified block diagram of a communication device106, according to some embodiments. It is noted that the block diagram of the communication device ofFIG.3is only one example of a possible communication device. According to embodiments, communication device106may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet and/or a combination of devices, among other devices. As shown, the communication device106may include a set of components300configured to perform core functions. For example, this set of components may be implemented as a system on chip (SOC), which may include portions for various purposes. Alternatively, this set of components300may be implemented as separate components or groups of components for the various purposes. The set of components300may be coupled (e.g., communicatively; directly or indirectly) to various other circuits of the communication device106.

For example, the communication device106may include various types of memory (e.g., including NAND flash310), an input/output interface such as connector I/F320(e.g., for connecting to a computer system; dock; charging station; input devices, such as a microphone, camera, keyboard; output devices, such as speakers; etc.), the display360, which may be integrated with or external to the communication device106, and cellular communication circuitry330such as for 5G NR, LTE, GSM, etc., and short to medium range wireless communication circuitry329(e.g., Bluetooth™ and WLAN circuitry). In some embodiments, communication device106may include wired communication circuitry (not shown), such as a network interface card, e.g., for Ethernet.

The cellular communication circuitry330may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas335and336as shown. The short to medium range wireless communication circuitry329may also couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas337and338as shown. Alternatively, the short to medium range wireless communication circuitry329may couple (e.g., communicatively; directly or indirectly) to the antennas335and336in addition to, or instead of, coupling (e.g., communicatively; directly or indirectly) to the antennas337and338. The short to medium range wireless communication circuitry329and/or cellular communication circuitry330may include multiple receive chains and/or multiple transmit chains for receiving and/or transmitting multiple spatial streams, such as in a multiple-input multiple output (MIMO) configuration.

The communication device106may further include one or more smart cards345that include SIM (Subscriber Identity Module) functionality, such as one or more UICC(s) (Universal Integrated Circuit Card(s)) cards345.

As shown, the SOC300may include processor(s)302, which may execute program instructions for the communication device106and display circuitry304, which may perform graphics processing and provide display signals to the display360. The processor(s)302may also be coupled to memory management unit (MMU)340, which may be configured to receive addresses from the processor(s)302and translate those addresses to locations in memory (e.g., memory306, read only memory (ROM)350, NAND flash memory310) and/or to other circuits or devices, such as the display circuitry304, short range wireless communication circuitry229, cellular communication circuitry330, connector I/F320, and/or display360. The MMU340may be configured to perform memory protection and page table translation or set up. In some embodiments, the MMU340may be included as a portion of the processor(s)302.

As noted above, the communication device106may be configured to communicate using wireless and/or wired communication circuitry. The communication device106may be configured to receive configuration information to enable communication device106to be configured to use default beams. The configuration information may sent by and received from a gNB (e.g., a base station). In some embodiments, these default beams are for a default beam for the physical downlink shared channel (PDSCH), a default aperiodic Channel Status Information-Reference Signal (CSI-RS) beam, and/or a default PUCCH/SRS beam and pathloss reference signal (RS).

As described herein, the communication device106may include hardware and software components for implementing the above features for receiving configuration information to configure a device to use default beams as described herein. The processor302of the communication device106may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor302may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor302of the communication device106, in conjunction with one or more of the other components300,304,306,310,320,329,330,340,345,350,360may be configured to implement part or all of the features described herein.

Further, as described herein, cellular communication circuitry330and short-range wireless communication circuitry329may each include one or more processing elements. In other words, one or more processing elements may be included in cellular communication circuitry330and, similarly, one or more processing elements may be included in short range wireless communication circuitry329. Thus, cellular communication circuitry330may include one or more integrated circuits (ICs) that are configured to perform the functions of cellular communication circuitry330. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of cellular communication circuitry230. Similarly, the short-range wireless communication circuitry329may include one or more ICs that are configured to perform the functions of short-range wireless communication circuitry32. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of short-range wireless communication circuitry329.

FIG.4—Block Diagram of a Base Station

In addition, as described herein, processor(s)404may be comprised of one or more processing elements. In other words, one or more processing elements may be included in processor(s)404. Thus, processor(s)404may include one or more integrated circuits (ICs) that are configured to perform the functions of processor(s)404. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processor(s)404.

Further, as described herein, radio430may be comprised of one or more processing elements. In other words, one or more processing elements may be included in radio430. Thus, radio430may include one or more integrated circuits (ICs) that are configured to perform the functions of radio430. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of radio430.

FIG.5: Block Diagram of Cellular Communication Circuitry

The cellular communication circuitry330may couple (e.g., communicatively; directly or indirectly) to one or more antennas, such as antennas335a-b and336as shown (inFIG.3). In some embodiments, cellular communication circuitry330may include dedicated receive chains (including and/or coupled to, e.g., communicatively; directly or indirectly. dedicated processors and/or radios) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, as shown inFIG.5, cellular communication circuitry330may include a modem510and a modem520. Modem510may be configured for communications according to a first RAT, e.g., such as LTE or LTE-A, and modem520may be configured for communications according to a second RAT, e.g., such as 5G NR.

In some embodiments, a switch570may couple transmit circuitry534to uplink (UL) front end572. In addition, switch570may couple transmit circuitry544to UL front end572. UL front end572may include circuitry for transmitting radio signals via antenna336. Thus, when cellular communication circuitry330receives instructions to transmit according to the first RAT (e.g., as supported via modem510), switch570may be switched to a first state that allows modem510to transmit signals according to the first RAT (e.g., via a transmit chain that includes transmit circuitry534and UL front end572). Similarly, when cellular communication circuitry330receives instructions to transmit according to the second RAT (e.g., as supported via modem520), switch570may be switched to a second state that allows modem520to transmit signals according to the second RAT (e.g., via a transmit chain that includes transmit circuitry544and UL front end572).

As described herein, the modem510may include hardware and software components for implementing the above features or for receiving configuration information to configure a device to communicate using default beams (e.g., receive information, transmit information), as well as the various other techniques described herein. The configuration information may sent by and received from a gNB (e.g., a base station) or other device or system. The processors512may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor512may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor512, in conjunction with one or more of the other components530,532,534,550,570,572,335and336may be configured to implement part or all of the features described herein.

In addition, as described herein, processors512may include one or more processing elements. Thus, processors512may include one or more integrated circuits (ICs) that are configured to perform the functions of processors512. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processors512.

As described herein, the modem520may include hardware and software components for implementing the above features for receiving configuration information to configure a device to communicate using default beams (e.g., receive information, transmit information), as well as the various other techniques described herein. The processors522may be configured to implement part or all of the features described herein, e.g., by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), processor522may be configured as a programmable hardware element, such as an FPGA (Field Programmable Gate Array), or as an ASIC (Application Specific Integrated Circuit). Alternatively (or in addition) the processor522, in conjunction with one or more of the other components540,542,544,550,570,572,335and336may be configured to implement part or all of the features described herein.

In addition, as described herein, processors522may include one or more processing elements. Thus, processors522may include one or more integrated circuits (ICs) that are configured to perform the functions of processors522. In addition, each integrated circuit may include circuitry (e.g., first circuitry, second circuitry, etc.) configured to perform the functions of processors522.

In some embodiments, the techniques described herein are for configuring a UE to use a default beam in 5G. In some embodiments, the default beam is the default beam for the PDSCH. In another embodiment, the default beam is the default beam for the PUCCH and SRS. In another embodiment, the default beam is the default beam for the CSI-RS.

As defined in NR release 15 and 16, the default beam for PDSCH and aperiodic CSI-RS when scheduling offset is below a threshold UE reported has been defined as follows in sections 5.1.5 and 5.2.1.5.1 of 3GPP TS 38.214: for single-TRP operation, the default beam for PDSCH and aperiodic CSI-RS is based on the beam of CORESET with lowest ID in latest slot when multiple CORESETs are configured in the same BWP, for single-DCI based multi-TRP operation, the default beam for PDSCH is based on the beam corresponding to the 2 active TCI States corresponding to the lowest TCI codepoint in the same BWP and the default beam for aperiodic CSI-RS is based on the first TCI State applied for PDSCH default beam in the same BWP, and for multi-DCI based multi-TRP operation, the default beam for PDSCH and aperiodic CSI-RS is based on the TCI State applied for the CORESET with lowest ID in latest slot when multiple CORESETs are configured with the same CORESETPoolIndex configured as the CORESET with scheduling PDCCH in the same BWP. If there is any known signal in the slot, the beam for the known signal can be applied for PDSCH and CSI-RS.

Also, in NR release 15 and 16, the default beam for PUCCH/SRS when spatial relation and pathloss reference signal is not configured is defined as follows in sections 7.2.1, 7.3.1, and 9.2.2 of 3GPP TS 38.213 and in section 6.2.1 of 3GPP TS 38.214: the default beam and pathloss is based on the downlink signal configured as QCL-typeD in the TCI State for CORESET with lowest ID in the same BWP, where for SRS, if there is no CORESET configured in the BWP, the active TCI with lowest ID should be applied. Also, in these sections, NR release 15 and 16 states that for FR1, where QCL-TypeD is not applicable, the default pathloss reference signal could be the downlink signal configured as QCL-typeA for the CORESET with lowest ID.

In NR release 17, to support Single Frequency Network (SFN) operation, one CORESET can be configured with two TCI States with at least one of the following options. In a first option, one of the TCI states can be associated with {average delay, delay spread} and another TCI states can be associated with {average delay, delay spread, Doppler shift, Doppler spread} (i.e., QCL-TypeA). In a second option, one the TCI state can be associated with {average delay, delay spread} and another TCI state with {Doppler shift, Doppler spread} (i.e., QCL-TypeB). In a third option, one of the TCI state can be associated with {delay spread} and another TCI states can be associated with {average delay, delay spread, Doppler shift, Doppler spread} (i.e., QCL-TypeA). In a fourth option, both TCI states can be associated with {average delay, delay spread, Doppler shift, Doppler spread} (i.e., QCL-TypeA). For these four options, each TCI state may be additionally associated with {Spatial Rx parameter} (i.e., QCL-TypeD).

However, if two TCI States are configured for a CORESET, there is an issue as to how to determine the default beam for the following cases: 1) PDSCH with scheduling offset below a threshold; aperiodic CSI-RS with scheduling offset below a threshold; Physical Uplink Control Channel (PUCCH) beam and pathloss reference signal when spatial relation and pathloss reference signal are not configured; and a sounding reference signal (SRS) beam and pathloss reference signal when spatial relation and pathloss reference signal are not configured.

To overcome this issue, in some embodiments, the UE may be configured by the gNB (e.g., base station) with a default beam configuration for the PDSCH. In some embodiments, the configuration process includes identifying which CORESET is used for default PDSCH beam selection when two TCI states are configured for at least one CORESET and then using one or more of the TCI states of the CORESET to determine the default PDSCH beam. Note that in some embodiments, the default PDSCH beam is only applied when one of the TCI states in the TCI state list configured by RRC signaling is configured with QCL-typeD. In other words, the default PDSCH beam is only applied when at least one of the TCI states of a CORESET is configured with quasi-co-location with spatial receiving parameters (or information indicative of such parameters).

There are a number of options for configuring the UE to select the CORESET (from among the CORESETs that are sent) to determine the default PDSCH beam when an offset between reception of downlink control information (DCI) in the scheduling physical downlink control channel (PDCCH) and corresponding PDSCH is less than a threshold the UE reported. In other words, based on the configuration, the UE is configured to monitor a CORESET sent from the gNB to determine the default PDSCH beam.

In some embodiments for CORESET selection, as option1, the default PDSCH beam is based on the monitored CORESET with lowest ID in latest slot in the same BWP and two TCI states are configured for this CORESET. That is, the CORESET with lowest ID in latest slot in the same BWP and configured with two TCI states is selected. If no CORESET is configured for the current active BWP in RRC, then the two TCI states corresponding to the lowest TCI codepoint is selected.

In another embodiment for CORESET selection, as option2, the default PDSCH beam is based on the monitored CORESET with lowest ID in latest slot in the same BWP and configured with only one TCI State. That is, the CORESET with lowest ID in latest slot in the same BWP and configured with only one TCI state is selected. If no CORESET is configured for the current active BWP in RRC, the TCI State corresponding to the lowest TCI codepoint can be selected, with the TCI codepoint corresponding to one TCI State being precluded.

In yet another embodiment for CORESET selection, as option3, the default PDSCH beam is based on the monitored CORESET with lowest ID in latest slot in the same BWP regardless of whether the monitored CORESET is configured with one TCI state or two TCI states. In such a case, in some embodiments, the UE may expect the number of TCI states configured in all CORESETs in a BWP to be the same.

In still yet another embodiment for CORESET selection, as option4, whether the default PDSCH beam is based on the monitored CORESET with lowest ID in latest slot in the same BWP and configured with two TCI states or whether the default PDSCH beam is based on the monitored CORESET with lowest ID in latest slot in the same BWP and configured with only 1 TCI State is configured by higher layer signaling (e.g., RRC signaling, MAC CE signaling, etc.) and reported by the UE to the gNB as part of its UE capability information.

In some embodiments, an RRC parameter is used to enable the new default PDSCH beam behavior.

FIG.6illustrates an example of selecting a CORESET to determine default PDSCH beam. Referring toFIG.6, if option1is used for selecting the CORESET described above, then the candidate CORESETs should be CORESET2only to determine the default PDSCH beam as it's the only CORESET with two TCIs. If option2is used for selecting the CORESET described above, then candidate CORESETs to determine the default PDSCH beam should be CORESET1only as CORESET1only has one TCI. If option3is used for selecting the CORESET described above, then candidate CORESETs should be CORESET1and2as they are both part of slot1. However, in this case, CORESET1is selected for use in determining the default PDSCH beam since it is with lowest ID.

After the CORESET to determine the default beam has been selected, the default PDSCH beam is determined using information in the selected (monitored) CORESET. Options1and3described above for using a selected CORESET with 2 TCI states are to determine the default beam, one or the following embodiments may be used to determine the default PDSCH beam from the selected CORESET. In a first embodiment (option1), the PDSCH beam is determined based on both TCI states in the CORESET. This implies that the PDSCH is also based on SFN scheme.

In a second embodiment (option2), the default PDSCH beam is determined based on one of the two TCI states of the selected CORESET. In such a case, in a first sub-option of this embodiment, the selected TCI from the two TCE states to use to determine the default PDSCH beam is predefined. For example, in some embodiments, the first TCI stat is used, or in another embodiment, the TCI state with the lowest ID is used.

In another, second sub-option of the embodiment in which the default PDSCH beam is determined based on one of the two TCI states of the selected CORESET, the selected TCI is configured by higher layer signaling (e.g., RRC signaling, MAC CE signaling, etc.) to indicate to the UE which one of the two TCI states is to be used to determine the default PDSCH beam.

In yet another, third sub-option of the embodiment in which the default PDSCH beam is determined based on one of the two TCI states of the selected CORESET, the selected TCI is determined by the indicated QCL types if options1-3described above for CORESET selection are used. In such a case, in some embodiments, the TCI to provide QCL-TypeA information is selected to determine the default PDSCH beam, in another example, the TCI to provide information other than QCL-TypeA is selected to determine the default PDSCH beam, an in yet another embodiment, the TCI to provide QCL-TypeB information is selected.

In another, fourth sub-option of the embodiment in which the default PDSCH beam is determined based on one of the two TCI states of the selected CORESET, the selected TCI from the two TCI states to use to determine the default beam is determined by one or more of a slot, a subframe, and/or a frame index. In such a case, in one example embodiment, the first TCI is applied for the odd slot and the second TCI is applied for the even slot.

In a third embodiment (option3), the default PDSCH beam is determined based on either one or two of the TCI states of the two TCI states of the selected CORESET and whether the UE is configured to use one or both of the TCI states to determine the default PDSCH beam is configured by the gNB using higher layer signaling (e.g., RRC signaling, MAC CE signaling, etc.), or reported by the UE to the gNB as part of its UE capability information. Note that configuring for option1(i.e., based on both TCI states) implies the configuration supports a SFN scheme, while configuring for option2(i.e., based on one of both TCI states) implies the configuration supports a non-SFN scheme.

Also, in some embodiments, when there is a known CORESET with 2 TCI states configured in overlapped symbols, any of the three embodiments (options1-3) for determining the default PDSCH beam from a CORESET having two TCI states described above can be used to determine the default PDSCH beam.

FIG.7illustrates an example for TCI selection from a selected CORESET to determine default PDSCH beam. Referring toFIG.7, in option1where the default PDSCH beam is determined based on both TCI states, both TCI states1and2of CORESET2are applied and PDSCH is assumed to be based on the SFN manner. In option2where the default PDSCH beam is determined based on one of the two TCI states, either TCI states1or2of CORESET2is selected to determine the default PDSCH beam and it may be based on first through fourth sub-options described above. In this example, whether TCI states1or2is selected is determined by TCI ID, higher layer signaling, QCL type, or slot index. In option3, whether to select both TCI states1and2, or only TCI state1or only TCI state2states is configured by the gNB and determined by higher layer signaling (e.g., RRC signaling, MAC CE signaling, etc.).

In some embodiments, the UE is also configured with configuration information from the gNB as to the selection of a default aperiodic Channel State Information—Reference Signal (CSI-RS) beam. In some embodiments, the default PDSCH beam and the aperiodic CSI-RS beam are aligned with each other. In other words, the UE is configured with configuration information from the gNB to determine the default PDSCH beam and the aperiodic CSI-RS beam using the same information. This is because the UE has no information as to whether a PDSCH or CSI-RS exists.

In some embodiments, if two TCI States are configured for a CORESET, the default aperiodic CSI-RS beam is determined as follows. Since the default aperiodic CSI-RS beam is selected based on the default PDSCH beam, if one TCI is selected to determine the default PDSCH beam based on the options described above for selecting the CORESET and using one TCI state in the selected/monitored CORESET, then that same TCI state is applied for determining the default aperiodic CSI-RS beam. Similarly, if two TCI states are selected to determine the default PDSCH beam based on the options described above for selecting the CORESET and using the two TCI states in the selected/monitored CORESET, then the options depicted inFIG.7are also used to determine the default aperiodic CSI-RS beam. When there is a known CORESET configured with 2 TCI states in overlapped symbols, the solutions inFIG.7are used to determine the default aperiodic CSI-RS beam. Note that in some embodiments the default aperiodic CSI-RS beam is applied for CSI-RS without TRS-Info (information) configured, and is applied when one of the TCI states in TCI State list configured by RRC signaling from the gNB is configured with QCL-typeD.

In some embodiments, the UE is also configured with configuration information from the gNB as to the information to use to determine a default PUCCH/SRS beam and pathloss reference signal. In some embodiments, if two TCI states are configured for a CORESET, the following options use CORESET selection to determine the default PUCCH/SRS beam and pathloss reference signal. First, in some embodiments, referred to as option1, the default PUCCH/SRS beam is based on the CORESET with lowest ID in the same BWP and the two TCI states that are configured for this CORESET. In another embodiment, referred to as option2, the default PUCCH/SRS beam is based on the CORESET with lowest ID in the same BWP and only the 1 TCI state that is configured for this CORESET. In yet another embodiment, referred to as option3, the default PUCCH/SRS beam is based on the CORESET with lowest ID in the same BWP regardless of whether 1 or 2 TCI states are configured for this CORESET. In such a case, in some embodiments, the UE expects the number of TCI states configured in all CORESETs in a BWP to be the same. In still yet another embodiment, referred to as option4, whether to apply options1or2described above (e.g., using the CORESET with lowest ID in the same BWP and the two TCI states that are configured for this CORESET or using the CORESET with lowest ID in the same BWP and the only one TCI state that is configured for the CORESET) to determine the default PUCCH/SRS beam is based on higher layer signaling (e.g., RRC signaling, MAC CE signaling, etc.), or based on UE capability information reported by the UE to the gNB.

For the default SRS beam, in some embodiments, if there is no CORESET in the BWP, the UE is configured by configuration information from the gNB to select the default beam and pathloss RS selection. In some embodiments, referred to as option1, the TCI indicated by lowest TCI codepoint corresponding to the 1 TCI state activated by MAC CE is applied and used to determine the default SRS beam. In another embodiment, referred to as option2, the TCI indicated by lowest TCI codepoint corresponding to the 2 TCI states activated by MAC CE is applied and used to determine the default SRS beam. In yet another embodiment, referred to as option3, the TCI state indicated by lowest TCI codepoint activated by MAC CE is applied and used to determine the default SRS beam. In still yet another embodiment, referred to as option4, whether to apply option1(using the TCI indicated by lowest TCI codepoint corresponding to the 1 TCI state activated by MAC CE) or option2(using the TCI indicated by lowest TCI codepoint corresponding to the 2 TCI states activated by MAC CE) is configured by higher layer signaling (e.g., RRC or MAC CE signaling), or configured based on UE capability information reported by the UE to the gNB.

With respect to the default PUCCH/SRS beam and pathloss reference signal, in some embodiments, when a CORESET or TCI codepoint with 2 TCI states is selected, the default PUCCH/SRS beam and pathloss RS can be determined as follows. In some embodiments, the default beam and pathloss RS is determined, for PUCCH without repetition configured and SRS, using one TCI from the 2 TCI states applied for the CORESET. In various embodiments, the TCI selection may be made in the same way as using one of the first through fourth sub-options described above for determining the default PDSCH beam based on one of the two TCI states of a selected CORESET. In another embodiment, the default beam and pathloss RS is determined, for PUCCH with repetition configured, by applying one TCI state, similarly to the determination used for PUCCH without repetition configured. In yet another embodiment, the default beam and pathloss RS is determined, for PUCCH with repetition configured, by using both TCI states in a selected CORESET. In such a case, in some embodiments, the mapping between TCI and repetition is configured by higher layer signaling (e.g., RRC signaling, MAC CE signaling, etc.), DCI, or is predefined based on cyclic mapping and sequential mapping.FIGS.8A and8Billustrate examples of cyclic mapping and sequential mapping. In another embodiment, whether to apply one TCI or use both TCI states of a selected CORESET to determine the default PUCCH/SRS beam and pathloss RS is configured by higher layer signaling (e.g., RRC signaling, MAC CE signaling, etc.), DCI, or based on UE capability information reported by the UE to the gNB.

FIG.9is a flow diagram of one embodiment of a process for configuring a UE. The process is performed by processing logic that comprises hardware (circuitry, dedicated logic, etc.), software (e.g., software running on a chip, software run on a general-purpose computer system or a dedicated machine, etc.), firmware, or a combination of the three. In some embodiments, the operations in the process are performed by a UE in a 5G NR communication system. In some embodiments, the operations in the process are performed by baseband processor in a 5G NR communication system.

Referring toFIG.9, the process begins by processing logic receiving, from a base station, configuration information for configuring a default beam for the physical downlink shared channel (PDSCH) to use on condition that an offset between reception of downlink control information (DCI) in the scheduling physical downlink control channel (PDCCH) and corresponding PDSCH is less than a threshold and at least one Transmission Configuration Indicator (TCI) states includes spatial receiving parameters for configuring a quasi-co-location (processing block901).

Next, processing logic configures a default beam configuration for the PDSCH based on the configuration information and a monitored control resource set (CORESET) with a lowest CORESET identifier (ID) from among a set of CORESETs in a latest slot in a same bandwidth part (BWP), where at least one CORSET of the set of CORESETs includes more than one TCI state (processing block902).

In some embodiments, processing logic also selects a default aperiodic Channel Status Information-Reference Signal (CSI-RS) beam based on the default beam for the PDSCH and the two TCI states (processing block903). This is optional. In some embodiments, the selection is based on a configuration specified in the configuration information.

After configuring the default beam configuration for the PDSCH, processing logic sends or enables receiving a transmission using the default PDSCH beam (processing block904).

In some embodiments, the default beam configuration is based on two TCI states configured for the monitored CORESET. In some embodiments, if no CORESET is configured, the default beam configuration is based on two TCI states corresponding to a lowest TCI codepoint.

In some embodiments, the default beam configuration is based on only one TCI state configured for the monitored CORESET. In some embodiments, in the case where the default beam configuration is based on two TCI states corresponding to a lowest TCI codepoint, the default beam configuration is based on a TCI state corresponding to a lowest TCI codepoint if no CORESET is configured. In another embodiment, in the case where the default beam configuration is based on two TCI states corresponding to a lowest TCI codepoint, the one TCI is predefined. In some embodiments, the one TCI state is predefined as the TCI state that is first among the TCI states or a TCI state with a lowest ID among the TCI states. In yet another embodiment, in the case where the default beam configuration is based on two TCI states corresponding to a lowest TCI codepoint, the one TCI is configured by Radio Resource Control (RRC) or MAC (Medium Access Control) CE (MAC Control Element) signaling. In still yet another embodiment, in the case where the default beam configuration is based on two TCI states corresponding to a lowest TCI codepoint, the one TCI is determined by QCL type. In still yet another embodiment, in the case where the default beam configuration is based on two TCI states corresponding to a lowest TCI codepoint, the one TCI is determined by one or more of a slot, a subframe, and a frame index.

In some embodiments, receiving the indication of at least one of a default beam from the base station comprises receiving, by the UE, RRC or MAC CE signaling.

In some embodiments, the default beam configuration is based on two TCI states being configured for the monitored CORESET or only one TCI state configured for the monitored CORESET, wherein whether the default beam configuration is based on one or two TCI states is specified by RRC or MAC CE signaling.

FIG.10is a flow diagram of another embodiment of a process for configuring a UE. The process is performed by processing logic that comprises hardware (circuitry, dedicated logic, etc.), software (e.g., software running on a chip, software run on a general-purpose computer system or a dedicated machine, etc.), firmware, or a combination of the three. In some embodiments, the operations in the process are performed by a UE in a 5G NR communication system. In some embodiments, the operations in the process are performed by baseband processor in a 5G NR communication system.

Referring toFIG.10, the process begins by processing logic receiving from a base station, configuration information for a default PUCCH/SRS beam and pathloss reference signal (RS) (processing block1001).

In response to receiving the configuration information, processing logic configures the default PUCCH/SRS beam and pathloss RS based on the configuration information and a monitored control resource set (CORESET) with a lowest CORESET identifier (ID) from among a set of CORESETs in a same bandwidth part (BWP) (processing block1002).

Once configured, processing logic sends or enable sending a transmission using the default PUCCH/SRS beam (processing block1003).

In some embodiments, at least one TCI state is configured for the monitored CORESET and the configuration specified in the configuration information for a default PUCCH/SRS beam and pathloss RS is based on at least one TCI state. In another embodiment, two TCI states are configured for the monitored CORESET and the configuration specified in the configuration information for a default PUCCH/SRS beam and pathloss RS is based on two TCI states.

In some embodiments, wherein whether the monitored CORESET that has one or two TCI states being used to configure the default PUCCH/SRS beam and pathloss RS is configured by received RRC or MAC CE signaling.

In some embodiments, if no CORESET is configured, the default PUCCH/SRS beam and pathloss RS is based on a TCI indicated by a lowest TCI codepoint corresponding to one TCI activated by MAC CE. In another embodiment, if no CORESET is configured, the default PUCCH/SRS beam and pathloss RS is based on a TCI indicated by a lowest TCI codepoint corresponding to two TCIs activated by MAC CE. In yet another embodiment, if no CORESET is configured, the default PUCCH/SRS beam and pathloss RS is based on a TCI indicated by a lowest TCI codepoint activated by MAC CE. In still yet another embodiment, if no CORESET is configured, the default PUCCH/SRS beam and pathloss RS is based on a TCI indicated by a lowest TCI codepoint corresponding to one TCI activated by MAC CE or based on a TCI indicated by a lowest TCI codepoint corresponding to two TCIs activated by MAC CE, wherein using the lowest TCI codepoint corresponding to one or two TCIs activated by MAC CE is configured by received RRC or MAC CE signaling.

In some embodiments, wherein, when a CORESET or TCI codepoint with two TCI states is selected, the default PUCCH/SRS beam and pathloss RS for PUCCH without repetition configured is based one TCI from the two TCI states. In another embodiment, wherein, when a CORESET or TCI codepoint with two TCI states is selected, the default PUCCH/SRS beam and pathloss RS for PUCCH with repetition configured is based the two TCI states for a PUCCH.

In some embodiments, wherein, when a CORESET or TCI codepoint with two TCI states is selected, the default PUCCH/SRS beam and pathloss RS for PUCCH with repetition configured is based the one or two TCI states for a PUCCH, and using one or two TCIs is configured by received RRC or MAC CE signaling.

FIG.11is a flow diagram of one embodiment of a process by which network equipment configures a UE. The process is performed by processing logic that comprises hardware (circuitry, dedicated logic, etc.), software (e.g., software running on a chip, software run on a general-purpose computer system or a dedicated machine, etc.), firmware, or a combination of the three. In some embodiments, the operations in the process are performed by network equipment operating in a 5G new radio a spectrum in 5G new radio (NR) above 52.6 GHz. In some embodiments, the operations in the process are performed by baseband processor in a 5G NR communication system.

Referring toFIG.11, the process begins by processing logic determines a configuration for a wireless device, wherein the configuration is set forth in configuration information that specifies: a default beam configuration for the physical downlink shared channel (PDSCH) to use on condition that an offset between reception of downlink control information (DCI) in the scheduling physical downlink control channel (PDCCH) and corresponding PDSCH is less than a threshold and at least one Transmission Configuration Indicator (TCI) states includes spatial receiving parameters for configuring a quasi-co-location, optionally a default PUCCH/SRS beam and pathloss reference signal (RS), and optionally a default aperiodic Channel Status Information-Reference Signal (CSI-RS) beam based on the default beam for the PDSCH and the two TCI states (processing block1101).

In some embodiments, two TCI states are configured for the monitored CORESET. In some embodiments, at least one TCI state is configured for the monitored CORESET. In some embodiments, whether the monitored CORESET that has one or two TCI states being used to configure the default PUCCH/SRS beam and pathloss RS is configured by received RRC or MAC CE signaling.

In some embodiments, the default beam configuration is based on two TCI states configured for the monitored CORESET. In some embodiments, in such a case, if no CORESET is configured, the default beam configuration is based on two TCI states corresponding to a lowest TCI codepoint. In another embodiment, the default beam configuration is based on only one TCI state configured for the monitored CORESET.

In some embodiments, in the case that the default beam configuration is based on only one TCI state configured for the monitored CORESET, the default beam configuration is based on a TCI state corresponding to a lowest TCI codepoint if no CORESET is configured. In another embodiment, in the case that the default beam configuration is based on only one TCI state configured for the monitored CORESET, the one TCI is predefined. In some embodiments, in such a case, the one TCI is predefined as a TCI that is first among the TCI states or a TCI state with a lowest ID among the TCI states. In yet another embodiment, in the case that the default beam configuration is based on only one TCI state configured for the monitored CORESET, the one TCI is configured by Radio Resource Control (RRC) or MAC (Medium Access Control) CE (MAC Control Element) signaling. In still yet another embodiment, in the case that the default beam configuration is based on only one TCI state configured for the monitored CORESET, the one TCI is determined by QCL type. In even another embodiment, in the case that the default beam configuration is based on only one TCI state configured for the monitored CORESET, the one TCI is determined by one or more of a slot, a subframe, and a frame index.

In some embodiments, when a CORESET or TCI codepoint with two TCI states is selected, the default PUCCH/SRS beam and pathloss RS for PUCCH without repetition configured is based one TCI from the two TCI states. In another embodiment, when a CORESET or TCI codepoint with two TCI states is selected, the default PUCCH/SRS beam and pathloss RS for PUCCH with repetition configured is based the two TCI states for a PUCCH. In yet another embodiment, when a CORESET or TCI codepoint with two TCI states is selected, the default PUCCH/SRS beam and pathloss RS for PUCCH with repetition configured is based the one or two TCI states for a PUCCH, wherein using one or two TCIs is configured by received RRC or MAC CE signaling.

In another embodiment, if no CORESET is configured, the default PUCCH/SRS beam and pathloss RS is based on a TCI indicated by a lowest TCI codepoint corresponding to two TCIs activated by MAC CE. In yet another embodiment, if no CORESET is configured, the default PUCCH/SRS beam and pathloss RS is based on a TCI indicated by a lowest TCI codepoint activated by MAC CE. In still yet another embodiment, if no CORESET is configured, the default PUCCH/SRS beam and pathloss RS is based on a TCI indicated by a lowest TCI codepoint corresponding to one TCI activated by MAC CE or based on a TCI indicated by a lowest TCI codepoint corresponding to two TCIs activated by MAC CE, wherein using the lowest TCI codepoint corresponding to one or two TCIs activated by MAC CE is configured by received RRC or MAC CE signaling.

In some embodiments, if no CORESET is configured, the default PUCCH/SRS beam and pathloss RS is based on a TCI indicated by a lowest TCI codepoint corresponding to one TCI activated by MAC CE.

After determining the configuration, processing logic transmits, to a UE, the configuration information identifying the default beam configuration to the wireless device and the default PUCCH/SRS beam and pathloss reference signal (RS), wherein the default PDSCH beam configuration is based on the configuration information and a monitored control resource set (CORESET) with a lowest CORESET identifier (ID) from among a set of CORESETs in a latest slot in a same bandwidth part (BWP), wherein at least one CORSET of the set of CORESETs includes more than one TCI state; and wherein the default PUCCH/SRS beam and pathloss RS, if specified in the configuration information, is based on the configuration information and a monitored CORESET with a lowest CORESET identifier (ID) from among a set of CORESETs in a same BWP (processing block1102).

In some embodiments, sending the configuration information is performed using RRC or MAC CE signaling.

In some embodiments, the default aperiodic CSI-RS beam is selected based on the default beam for the PDSCH.

It should be kept in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the above discussion, it is appreciated that throughout the description, discussions utilizing terms such as “selecting,” “determining,” “receiving,” “forming,” “grouping,” “aggregating,” “generating,” “removing,” or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.