Patent ID: 12262414

DETAILED DESCRIPTION

Overview

Beam determination refers to a set of procedures for an access node (AN) and a user equipment (UE) to select from among downlink communication beams and/or uplink communication beams for downlink and/or uplink communications, respectively. The downlink communication beams can provide downlink reference signals, such as channel-state information reference signals (CSI-RSs), to the UE. In some embodiments, the downlink communication beams can include one or more downlink control channels, for example, a Physical Downlink Control Channel (PDCCH), a Physical Downlink Shared Channel (PDSCH), one or more Synchronization Signal Blocks (SSBs), and/or a Physical Broadcasting Channel (PBCH). In these embodiments, the downlink reference signals can be transmitted concurrently with these downlink control channels or by themselves as stand-alone reference signals. The detailed description to follow describes various exemplary downlink beam scheduling procedures to control the transmission of the downlink reference signals, such as the CSI-RSs to provide an example, over the downlink communication beams. In some embodiments, the UE can utilize the CSI-RSs to perform beamforming failure detection (BFD) and beamforming failure recovery (BFR) in the wireless networks.

Exemplary Wireless Network

FIG.1graphically illustrates an exemplary wireless network in accordance with various embodiments. A wireless network100as illustrated inFIG.1is provided for the purpose of illustration only and does not limit the disclosed embodiments. In the exemplary embodiment illustrated inFIG.1, the wireless network100can include, but are not limited to, an access node (AN)102and a user equipment (UE)104. The UE104can include, but are not limited to, a Wireless Local Area Network (WLAN) station such as a wireless communication device, a smart phone, a laptop computing device, a desktop computing device, a tablet computing device, a monitor, a television, a wearable device, and the like. As used herein, the terms “access node,” “access point,” or the like can describe equipment that provides the radio baseband functions for data and/or voice connectivity between a network and one or more UEs or stations. These access node102can be referred to as wireless router, Base Stations (BSs), Next Generation NodeBs (gNBs), Radio Access Network (RAN) nodes, evolved NodeBs (eNBs), NodeBs, Road Side Units (RSUs), Transmission Reception Point (TRxPs or TRPs), and so forth, and can include ground stations, such as terrestrial access points, or satellite stations providing coverage within a geographic area, also referred to a serving cell. As used herein, the term “downlink” refers to the direction from the AN102to the UE104. The term “uplink” refers to the direction from the UE104to the AN102.

Beam determination refers to a set of procedures for the AN102and the UE104to select from among downlink communication beams106.1through106.mand/or uplink communication beams108.1through108.nfor downlink and/or uplink communications. In some embodiments, the downlink communication beams106.1through106.mcan provide downlink reference signals, such as channel-state information reference signals (CSI-RSs), to the UE104. In some embodiments, the downlink communication beams106.1through106.mcan include one or more downlink control channels, for example, a Physical Downlink Control Channel (PDCCH), a Physical Downlink Shared Channel (PDSCH), one or more Synchronization Signal Blocks (SSBs), and/or a Physical

Broadcasting Channel (PBCH). In these embodiments, the AN102can transmit the downlink reference signals concurrently with these downlink control channels or by themselves as stand-alone reference signals. In some embodiments, the AN102can perform a downlink beam scheduling procedure to control the transmission of the downlink reference signals, such as the CSI-RSs to provide an example, over the downlink communication beams106.1through106.m. As part of this downlink beam scheduling procedure, the AN102can selectively control which downlink communication beams from among the downlink communication beams106.1through106.mare to be used to transmit the one or more downlink reference signals to the UE104.

In the exemplary embodiment illustrated inFIG.1, the UE104can identify the downlink communication beams106.1through106.mthat are to be used to by the AN102to transmit the downlink reference signals. Once a corresponding reference signal has been recovered by the UE104from a downlink communication beam from among the downlink communication beams106.1through106.m, the UE104can utilize the corresponding reference signal as part of a beamforming failure detection (BFD) procedure to assess a radio link quality of the downlink communication beam. In some embodiments, the UE104can monitor the radio link quality of the downlink communication beam and can thereafter provide an indication, referred as a beam failure indication (BFI), when the radio link quality of the downlink communication beam indicates the downlink communication beam is failing. In these embodiments, when the number of BFIs reaches a certain value or threshold, for example, a maximum number of beam failure indications, MBFI, the UE104determines that the downlink communication beam has failed.

Once the UE104has determined the downlink communication beam has failed, the UE104undergoes a beamforming failure recovery (BFR) procedure. As part of this BFR procedure, the UE104identifies one or more new candidate downlink communication beams from among the downlink communication beams106.1through106.mfrom a candidate beam list and thereafter identifies the one or more new candidate downlink communication beams in a beam failure recovery request (BFRQ) provided to the AN102over one or more uplink channels, such as a physical random access channel (PRACH) and/or one or more uplink control channels, such as a Physical Uplink Control Channel (PUCCH) and/or a Physical Uplink Shared Channel (PUSCH), to provide some examples. In some embodiments, the BFRQ identifies an identifier of the UE104and the one or more new candidate downlink communication beams. Thereafter, the UE104monitors downlink control channels, for example, a Physical Downlink Control Channel (PDCCH) and/or a Physical Downlink Shared Channel (PDSCH), corresponding to the one or more new candidate downlink communication beams for a response from the AN102to the BFRQ, and can thereafter utilize the one or more new candidate downlink communication beams upon receiving the response from the AN102.

Exemplary Scheduling Procedures for Licensed Operation

As described above, the AN102can perform a downlink beam scheduling procedure to selectively control which downlink communication beams from among the downlink communication beams106.1through106.mare to be used to transmit the channel-state information reference signals (CSI-RSs). In some embodiments, the AN102can utilize one or more time-frequency resources to transmit the CSI-RSs over the downlink communication beams106.1through106.m. . . In some embodiments, the one or more time frequency resources can be structured using downlink resource grids, such as a time-frequency grids, also called resource grids or time-frequency resource grids, which are utilized for downlink transmissions between the UE104and the AN102. Each column and each row of these resource grids corresponds to one Orthogonal Frequency Domain Multiplexed (OFDM) symbol and one OFDM subcarrier, respectively. In some embodiments, the configuration of waveform parameters for these OFDM symbols is defined by one or more numerology sets. These waveform parameters define the placement of the CSI-RSs into the downlink resource grid and the structures, for example, pulse shapes and/or filters, that are utilized to map information symbols to these resources. These numerology sets can include pre-defined numbers of subcarriers, subcarrier spacings (SCSs), slot durations, cyclic prefix (CP) durations, and/or maximum bandwidth (BW) allocations to provide some examples. Rel-15 and Rel-16 provide for numerology sets for the range of frequencies between 4.1 GHz to 7.125 GHz, referred to as FR1, which is primarily used for traditional cellular mobile communications traffic, and for the range of frequencies between 24.25 GHz to 52.6 GHz, referred to as FR2, which is primarily used for short-range, high data rate capabilities.

The discussion to follow is to describe exemplary downlink beam scheduling procedures that can be utilized within the range of frequencies between 52.6 GHz and 71 GHz and beyond. The range of frequencies between 52.6 GHz and 71 GHz can include licensed spectrum and unlicensed spectrum. Generally, the licensed spectrum represents portions of the radio spectrum designated by a governing authority, such as the Federal Communication Commission (FCC) to provide an example, to be reserved for one or more organizations that have been granted exclusive rights to utilize these portions of the radio spectrum. In some embodiments, the exemplary downlink beam scheduling procedures as to be described in further detail below inFIG.2AthroughFIG.2Ecan be utilized to schedule transmission in the licensed spectrum and/or the exemplary downlink beam scheduling procedures as to be described in further detail below inFIG.3AthroughFIG.3C,FIG.4,FIG.5,FIG.6A,FIG.6B, andFIG.6Ccan be utilized to schedule transmission in the unlicensed spectrum. Although, the discussion ofFIG.2AthroughFIG.2Eto follow is to be described in terms of licensed operation and the discussion ofFIG.3AthroughFIG.3C,FIG.4,FIG.5,FIG.6A,FIG.6B, andFIG.6Cto follow is to be described in terms of unlicensed operation, those skilled in the relevant art(s) will recognize that the exemplary downlink beam scheduling procedures described in these figures can be utilized in the licensed spectrum and the unlicensed spectrum without departing from the spirit and scope of the present disclosure.

FIG.2AthroughFIG.2Egraphically illustrate exemplary downlink beam scheduling procedures that can be utilized by the exemplary wireless network for licensed operation in accordance with various embodiments. As described above inFIG.1, the AN102can perform a downlink beam scheduling procedure to selectively control which downlink communication beams from among the downlink communication beams106.1through106.mare to be used to transmit the channel-state information reference signals (CSI-RSs) to the UE104. In the exemplary embodiments illustrated inFIG.2AthroughFIG.2E, the AN102can perform the exemplary downlink beam scheduling procedures to be described in further detail below to periodically and/or aperiodically transmit at least CSI-RS1through CSI-RS3over the downlink communication beams106.1through106.3. ThroughoutFIG.2AthroughFIG.2E, the CSI-RS1is illustrated using dark shading, the CSI-RS2is illustrated using medium shading, and the CSI-RS3is illustrated using light shading. It should be noted that the various exemplary downlink beam scheduling procedures illustrated inFIG.2A through2Eare not limited to the CSI-RS1through the CSI-RS3. Those skilled in the relevant art(s) will recognize that these exemplary downlink beam scheduling procedures can be utilized to schedule transmission of any suitable number of CSI-RSs over any suitable number of downlink communication beams from among the downlink communication beams106.1through106.mthat will be apparent to those skilled in the relevant art(s) without departing from the spirit and scope of the present disclosure.

FIG.2Agraphically illustrates a first downlink beam scheduling procedure200to selectively control transmission of the CSI-RS1through the CSI-RS3over the downlink communication beams106.1through106.3. In the exemplary embodiment illustrated inFIG.2A, the AN102can perform the first downlink beam scheduling procedure200to selectively control which downlink communication beams from among the downlink communication beams106.1through106.3are to be used to transmit the CSI-RS1through the CSI-RS3to the UE104. In the exemplary embodiment illustrated inFIG.2A, the AN102can configure the CSI-RSs in accordance with one or more waveform parameters, such as number of subcarriers, subcarrier spacing (SCS), slot duration, cyclic prefix (CP) duration, and/or maximum bandwidth (BW) allocation to provide some examples, that are defined in accordance with a first exemplary numerology set. For example, the CSI-RS1through the CSI-RS3as illustrated inFIG.2Acan be characterized as having a SCS of two hundred forty (240) kHz.

As illustrated inFIG.2A, the AN102can perform the first downlink beam scheduling procedure200to schedule a periodic transmission and/or an aperiodic transmission of the CSI-RS1through the CSI-RS3over the downlink communication beams106.1through106.3in accordance with a CSI-RS transmission duty cycle, denoted as TCSI-RSinFIG.2A. In some embodiments, the CSI-RS transmission duty cycle TCSI-RShas a maximum periodicity, without discontinuous reception (DRX), of two (2) milliseconds (ms) which provides thirty-two (32) slots per two (2) ms period and four hundred forty-eight (448) symbols per two (2) ms period for a SCS of two hundred forty (240) kHz. In the exemplary embodiment illustrated inFIG.2A, the AN can periodically transmit at least two (2) instances, or periods, of the CSI-RS1through the CSI-RS3over the downlink communication beams106.1through106.3while maintaining the maximum periodicity of two (2) ms for the transmission duty cycle TCSI-RS. In these exemplary embodiments, the CSI-RS1through the CSI-RS3occupy, for each of these periodic transmissions, the first three (3) slots from among the sixteen (16) slots and other CSI-RSs, not illustrated inFIG.2A, can occupy the remaining slots from among the sixteen (16) slots such that a maximum of sixteen (16) candidate downlink communication beams can be utilized by the UE when performing beamforming failure recovery (BFR) as described above inFIG.1.

FIG.2BthroughFIG.2Egraphically illustrate a second downlink beam scheduling procedure202through a fifth downlink beam scheduling procedure208to selectively control transmission of the CSI-RS1through the CSI-RS3over the downlink communication beams106.1through106.3. In the exemplary embodiment illustrated inFIG.2B through2E, the AN102can perform the second downlink beam scheduling procedure202through the fifth downlink beam scheduling procedure208to selectively control which downlink communication beams from among the downlink communication beams106.1through106.3are to be used to transmit the CSI-RS1through the CSI-RS3to the UE104. In the exemplary embodiment illustrated inFIG.2BthroughFIG.2E, the AN102can configure the CSI-RSs in accordance with one or more waveform parameters, such as number of subcarriers, subcarrier spacing (SCS), slot duration, cyclic prefix (CP) duration, and/or maximum bandwidth (BW) allocation to provide some examples, that are defined in accordance with a second exemplary numerology set. For example, the CSI-RS1through the CSI-RS3as illustrated inFIG.2BthroughFIG.2Ecan be characterized as having a SCS of four hundred eighty (480) kHz.

As illustrated inFIG.2B, the AN102can perform the second downlink beam scheduling procedure202to schedule a periodic transmission and/or an aperiodic transmission of the CSI-RSi through the CSI-RS3over the downlink communication beams106.1through106.3in accordance with the CSI-RS transmission duty cycle TCSI-RSas described above inFIG.2A. In the exemplary embodiment illustrated inFIG.2B, the second downlink beam scheduling procedure202can schedule the periodicity of the CSI-RS1through the CSI-RS3to be less than the periodicity of the CSI-RS1through the CSI-RS3as described above inFIG.2A, while maintaining the same overhead as inFIG.2A, to accommodate for the greater number of slots for the increased SCS of four hundred eighty (480) kHz as illustrated inFIG.2Bwhen compared to the SCS of two hundred forty (240) kHz as illustrated inFIG.2A. In the exemplary embodiment illustrated inFIG.2B, the second downlink beam scheduling procedure202can schedule the periodic and/or the aperiodic transmission of at least four (4) instances, or periods, of the CSI-RS1through the CSI-RS3over the downlink communication beams106.1through106.3while maintaining the maximum periodicity of two (2) ms for the transmission duty cycle TCSI-RS. In these exemplary embodiments, the second downlink beam scheduling procedure202can schedule the CSI-RS1through the CSI-RS3to occupy, for each of these periodic transmissions, the first three (3) slots from among the sixteen (16) slots and other CSI-RSs, not illustrated inFIG.2B, can occupy the remaining slots from among the sixteen (16) slots such that a maximum of sixteen (16) candidate downlink communication beams can be utilized by the UE104when performing beamforming failure recovery (BFR) as described above inFIG.1.

As illustrated inFIG.2C, the AN102can perform the third downlink beam scheduling procedure204to schedule a periodic transmission and/or an aperiodic transmission of the CSI-RSi through the CSI-RS3over the downlink communication beams106.1through106.3in accordance with the CSI-RS transmission duty cycle TCSI-RSas described above inFIG.2A. In the exemplary embodiment illustrated inFIG.2C, the third downlink beam scheduling procedure204can schedule the periodicity of the CSI-RS1through the CSI-RS3to be the same as the periodicity of the CSI-RS1through the CSI-RS3as described above inFIG.2A, while maintaining the same overhead as inFIG.2A. In the exemplary embodiment illustrated inFIG.2C, the third downlink beam scheduling procedure204can schedule the periodic and/or the aperiodic transmission of at least two (2) instances, or periods, of the CSI-RS1through the CSI-RS3over the downlink communication beams106.1through106.3while maintaining the maximum periodicity of two (2) ms for the transmission duty cycle TCSI-RS. In these exemplary embodiments, the third downlink beam scheduling procedure204can schedule the CSI-RS1through the CSI-RS3to occupy, for each of these periodic transmissions, the first three (3) slots from among the thirty-two (32) and other CSI-RSs, not illustrated inFIG.2C, can occupy the remaining slots from among the thirty-two (32) such that a maximum of thirty-two (32) candidate downlink communication beams can be utilized by the UE104when performing beamforming failure recovery (BFR) as described above inFIG.1.

As illustrated inFIG.2D, the AN102can perform the fourth downlink beam scheduling procedure206to schedule a periodic transmission and/or an aperiodic transmission of the CSI-RS1through the CSI-RS3over the downlink communication beams106.1through106.3in accordance with the CSI-RS transmission duty cycle TCSI-RSas described above inFIG.2A. In the exemplary embodiment illustrated inFIG.2D, the fourth downlink beam scheduling procedure206can schedule the periodicity of the CSI-RS1through the CSI-RS3to be the same as the periodicity of the CSI-RS1through the CSI-RS3as described above inFIG.2Awhile additional overhead is added to account for limitations in beam switching time i.e. the time needed by the UE to switch from one beam to another in the case that the time exceeds the duration of the cyclic prefix of the symbol and cannot be performed transparently within the cyclic prefix, by providing the UE104with extra symbols between the CSI-RS1through the CSI-RS3to switch from among the downlink communication beams106.1through106.3. In the exemplary embodiment illustrated inFIG.2D, the fourth downlink beam scheduling procedure206can schedule the periodic and/or the aperiodic transmission of at least two (2) instances, or periods, of the CSI-RS1through the CSI-RS3over the downlink communication beams106.1through106.3while maintaining the maximum periodicity of two (2) ms for the transmission duty cycle TCSI-RS. In these exemplary embodiments, the second downlink beam scheduling procedure202can schedule the CSI-RS1through the CSI-RS3to occupy, for each of these periodic transmissions, the first, the third, and the fifth slots, respectively from among the thirty two (32) slots and other CSI-RSs, not illustrated inFIG.2D, can similarly occupy the remaining slots with similar overhead from among the thirty two (32) slots such that a maximum of sixteen (16) candidate downlink communication beams can be utilized by the UE when performing beamforming failure recovery (BFR) as described above inFIG.1. In these exemplary embodiments, even slots, such as the second, the fourth, and the sixth, etc., represent the additional overhead which is introduced by the fourth downlink beam scheduling procedure206to account for limitations in beam switching time.

As illustrated inFIG.2E, the AN102can perform the fifth downlink beam scheduling procedure208to schedule a periodic transmission and/or an aperiodic transmission of the CSI-RS1through the CSI-RS3over the downlink communication beams106.1through106.3in accordance with the CSI-RS transmission duty cycle TCSI-RSas described above inFIG.2A. In the exemplary embodiment illustrated inFIG.2E, the fifth downlink beam scheduling procedure208can schedule the periodicity of the CSI-RS1through the CSI-RS3to be the same as the periodicity of the CSI-RS1through the CSI-RS3as described above inFIG.2Awhile additional overhead is added to account for limitations in beam switching time by providing the UE104with extra symbols between the CSI-RS1through the CSI-RS3to switch from among the downlink communication beams106.1through106.3. In the exemplary embodiment illustrated inFIG.2E, the fifth downlink beam scheduling procedure208can schedule the periodic and/or the aperiodic transmission of at least two (2) instances, or periods, of the CSI-RS1through the CSI-RS3over the downlink communication beams106.1through106.3while maintaining the maximum periodicity of two (2) ms for the transmission duty cycle TCSI-RS. In these exemplary embodiments, the second downlink beam scheduling procedure202can schedule the CSI-RS1through the CSI-RS3to occupy, for each of these periodic transmissions, the first, the third, and the fifth slots, respectively from among the thirty sixteen (16) slots and other CSI-RSs, not illustrated inFIG.2E, can similarly occupy the remaining slots with similar overhead from among the sixteen (16) slots such that a maximum of eight (8) candidate downlink communication beams can be utilized by the UE when performing beamforming failure recovery (BFR) as described above inFIG.1. In these exemplary embodiments, even slots, such as the second, the fourth, and the sixth, etc., represent the additional overhead which is introduced by the fifth downlink beam scheduling procedure208to account for limitations in beam switching time.

Although the first downlink beam scheduling procedure200through the fifth downlink beam scheduling procedure208have been described as scheduling the transmission of the CSI-RS1through the CSI-RS3over the downlink communication beams106.1through106.3, those skilled in the relevant art(s) will recognize that these beam scheduling procedures can alternatively, or additionally, schedule more than one of the CSI-RS1through the CSI-RS3to be transmitted over a single downlink communication beam from among the downlink communication beams106.1through106.3to increase coverage of the AN102. In some embodiments, the AN102can signal a decimation and/or a sampling factor to the UE which indicates which periodic instances of this single CSI-RS are to be used or not used by the UE.

Exemplary Scheduling Procedures for Unlicensed Operation

As discussed above, the range of frequencies between 52.6 GHz and 71 GHz can include licensed spectrum and unlicensed spectrum. Generally, the unlicensed spectrum represents portions of the radio spectrum that are available to general public with a governing authority, such as the Federal Communication Commission (FCC) to provide an example, promulgating rules on their usage. The operation in the unlicensed spectrum can involve adhering to various regulatory rules which facilitate fair and equal usage of the unlicensed spectrum for different devices and radio access technologies. In some embodiments, the AN102can perform a Listen before talk (LBT) procedure to monitor a portion, or portions, of the unlicensed spectrum for a short period of time to sense whether the portion, or the portions, of the unlicensed spectrum is occupied by other transmissions from other devices. In these embodiments, the AN102is permitted to use the portion, or the portions, of the unlicensed spectrum for transmission when it senses that the portion, or the portions, of the unlicensed spectrum are free of other transmissions. Often times, these various regulatory rules specify a channel occupancy time (COT) upon with the AN102is permitted to use the portion, or the portions, of the unlicensed spectrum for transmission. Otherwise, the AN102is prohibiting from transmitting when it senses that the portion, or the portions, of the unlicensed spectrum are occupied by other transmissions. Various exemplary downlink beam scheduling procedures for use within the unlicensed spectrum are to be described in further detail below inFIG.3AthroughFIG.3C,FIG.4,FIG.5,FIG.6A,FIG.6B, andFIG.6C.

FIG.3AthroughFIG.3Cgraphically illustrate exemplary downlink beam scheduling procedures that can be utilized by the exemplary wireless network for unlicensed operation in accordance with various embodiments. As described above inFIG.1, the AN102can perform a downlink beam scheduling procedure to selectively control which downlink communication beams from among the downlink communication beams106.1through106.mare to be used to transmit the channel-state information reference signals (CSI-RSs) to the UE104. In the exemplary embodiments illustrated inFIG.3AthroughFIG.3C, the AN102can perform the exemplary downlink beam scheduling procedures to be described in further detail below to periodically and/or aperiodically transmit at least CSI-RS1through CSI-RS3over the downlink communication beams106.1through106.3. ThroughoutFIG.3AthroughFIG.3C, the CSI-RS1is illustrated using dark shading, the CSI-RS2is illustrated using medium shading, and the CSI-RS3is illustrated using light shading. It should be noted that the various exemplary downlink beam scheduling procedures illustrated inFIG.3AthroughFIG.3Care not limited to the CSI-RS1through the CSI-RS3. Those skilled in the relevant art(s) will recognize that these exemplary downlink beam scheduling procedures can be utilized to schedule transmission of any suitable number of CSI-RSs over any suitable number of downlink communication beams from among the downlink communication beams106.1through106.mthat will be apparent to those skilled in the relevant art(s) without departing from the spirit and scope of the present disclosure.

As illustrated inFIG.3A, the AN102can perform a first downlink beam scheduling procedure300to schedule a periodic transmission and/or an aperiodic transmission of the CSI-RS1through the CSI-RS3over the downlink communication beams106.1through106.3. In some embodiments, the downlink beam scheduling procedure300can schedule the periodic and/or the aperiodic transmission of the CSI-RS1through the CSI-RS3to be substantially similar to one or more of the beam scheduling procedures as described above inFIG.2AthroughFIG.2E. In the exemplary embodiment illustrated inFIG.3A, the AN102can process and/or transmit a first instance of the CSI-RS1through the CSI-RS3as scheduled by the first downlink beam scheduling procedure300during a first channel occupancy time (COT1). However, as illustrated inFIG.3A, while the AN102is processing and/or transmitting a second instance of the CSI-RS1through the CSI-RS3, the LBT procedure indicates that the spectrum, for example, the unlicensed spectrum as described above, carrying the downlink communication beams106.1through106.3is now occupied by other transmissions which is denoted as an LBT Failure inFIG.3A. In the exemplary embodiment illustrated inFIG.3AthroughFIG.3C, the LBT procedure can generate an indication of the LBT Failure when the portion, or the portions, of the unlicensed spectrum is occupied by other transmissions from other devices. In some embodiments, the AN102can ignore or skip those CSI-RSs from among the CSI-RSi through the CSI-RS3which the first downlink beam scheduling procedure300has scheduled to process and/or transmit during the LBT Failure. For example, as illustrated inFIG.3A, the AN102can ignore or skip the second instance of the CSI-RS3, which is denoted using an “X” inFIG.3A, which occurs during the LBT Failure. As another example, as illustrated inFIG.3A, the AN102can ignore or skip a third instance of the CSI-RS1and a third instance of the CSI-RS2, which are also denoted using an “X” inFIG.3A, which occur during the LBT Failure. In this other example, the AN102can process and/or transmit a third instance of the CSI-RS3which occurs during a second channel occupancy time (COT2) when the spectrum carrying the downlink communication beams106.1through106.3is not occupied by other transmissions.

In some embodiments, for example, operation in the unlicensed spectrum, the AN102can provide one or more channel occupancy time (COT) indicators to the UE104to allow the UE104to indicate the scheduling of the CSI-RSi through the CSI-RS3on the downlink communication beams106.1through106.3. In some embodiments, the one or more channel occupancy time (COT) indicators can be formatted according to the following structure: <Frequency Domain Structure> <Duration> <Specific Beam Schedule> to signal the time at which the CSI-RSs will be periodically transmitted on a specific beam, wherein the field <Frequency Domain Structure> describes the one or more time-frequency resources to be used to transmit the CSI-RS1through the CSI-RS3, the field <Duration> describes a duration in time of the CSI-RS1through the CSI-RS3, and the field <Specific Beam Schedule> describes which downlink communication beams from among the downlink communication beams106.1through106.3are to transmit the CSI-RS1through the CSI-RS3. In these embodiments, the AN102can provide one or more channel occupancy time (COT) indicators on any suitable number of downlink communication beams from among the downlink communication beams106.1through106.mthat will be apparent to those skilled in the relevant art(s). In some embodiments, for example, aperiodic transmission in the unlicensed spectrum, the one or more channel occupancy time (COT) indicators can be formatted according to the following structure: <Frequency Domain Structure> <Duration> <Specific Beam Schedule> <CSI-RS schedule> to signal the time at which the CSI-RSs will be aperiodically transmitted on a specific beam, wherein the field <CSI-RS schedule> describes the timing of the CSI-RS1through the CSI-RS3.

In some embodiments, for example, operation in the licensed spectrum, the AN102can utilize a periodic or Semi-Persistent (SP) CSI-RS resource that is activated by a Downlink Control Information (DCI) message and/or a Group Common Physical Downlink Control (GC-PDCCH) to communication one or more beam indicators to the UE104to indicate the scheduling of the CSI-RS1through the CSI-RS3on the downlink communication beams106.1through106.3. In some embodiments, the one or more beam indicators can be formatted according to the following structure: <Frequency Domain Structure> <Duration> <Specific Beam Schedule> to signal the time at which the CSI-RSs will be periodically transmitted on a specific beam, wherein the field <Frequency Domain Structure> describes the one or more time-frequency resources to be used to transmit the CSI-RS1through the CSI-RS3, the field <Duration> describes a duration in time of the CSI-RS1through the CSI-RS3, and the field <Specific Beam Schedule> describes which downlink communication beams from among the downlink communication beams106.1through106.3are to transmit the CSI-RS1through the CSI-RS3. In these embodiments, the AN102can provide one or more beam indicators on any suitable number of downlink communication beams from among the downlink communication beams106.1through106.mthat will be apparent to those skilled in the relevant art(s). In some embodiments, for example, aperiodic transmission in the unlicensed spectrum, the one or more beam indicators can be formatted according to the following structure: <Frequency Domain Structure> <Duration> <Specific Beam Schedule> <CSI-RS schedule> to signal the time at which the CSI-RSs will be aperiodically transmitted on a specific beam, wherein the field <CSI-RS schedule> describes the timing of the CSI-RS1through the CSI-RS3.

As illustrated inFIG.3BandFIG.3C, the AN102can perform a second downlink beam scheduling procedure302and a third downlink beam scheduling procedure304, respectively, to schedule the periodic and/or the aperiodic transmission of the CSI-RS1through the CSI-RS3over the downlink communication beams106.1through106.3. In the exemplary embodiments illustrated inFIG.3BandFIG.3C, the second downlink beam scheduling procedure302and the third downlink beam scheduling procedure304, respectively, can decrease the periodicity of the CSI-RS1through the CSI-RS3over the downlink communication beams106.1through106.3as compared to periodicity of the transmission of the CSI-RS1through the CSI-RS3as illustrated inFIG.3A. In some embodiments, this decrease in the periodicity of the CSI-RS1through the CSI-RS3can effectively increase coverage of the AN102. In some embodiments, the second downlink beam scheduling procedure302and the third downlink beam scheduling procedure304, respectively, can schedule the periodic and/or the aperiodic transmission of the CSI-RS1through the CSI-RS3in accordance with a nominal period PNand an actual period PAas illustrated inFIG.3BandFIG.3C. In these embodiments, the nominal period PNrepresents a period of time of potential CSI-RS transmissions and the actual period PArepresents a period of time of actual CSI-RS transmissions. For example, the second downlink beam scheduling procedure302and the third downlink beam scheduling procedure304can schedule the periodic and/or the aperiodic transmission of an instance of the CSI-RS1through the CSI-RS3over the nominal period PN. In this example, the AN102can process the instance of the CSI-RS1through the CSI-RS3within the nominal period PNto extend the instance of the CSI-RS1through the CSI-RS3to multiple instances of the CSI-RS1through the CSI-RS3and can thereafter transmit the multiple instances of the CSI-RS1through the CSI-RS3over the actual period PA.

As illustrated inFIG.3B, the AN102can ignore or skip those CSI-RSs from among the CSI-RS1through the CSI-RS3which the second downlink beam scheduling procedure302has scheduled to process and/or transmit during the LBT Failure. For example, as illustrated inFIG.3B, the AN102can ignore or skip a third instance of the CSI-RS3, which is denoted using an “X” inFIG.3B, which occurs during the LBT Failure. As another example, as illustrated inFIG.3B, the AN102can ignore or skip a fourth instance of the CSI-RS1and a fourth instance of the CSI-RS2, which are also denoted using an “X” inFIG.3B, which occur during the LBT Failure but processes and/or transmits a fourth instance of the CSI-RS3which occurs during a second channel occupancy time (COT2) when the spectrum carrying the downlink communication beams106.1through106.3is not occupied by other transmissions.

As illustrated inFIG.3C, the AN102can ignore or skip multiple CSI-RSs from among the CSI-RS1through the CSI-RS3which the third downlink beam scheduling procedure304has scheduled to process and/or transmit during the LBT Failure. For example, as illustrated inFIG.3B, the AN102can ignore or skip a third instance of the CSI-RS3in its entirety, which is denoted using an “X” inFIG.3B, which occurs during the LBT Failure. As another example, as illustrated inFIG.3B, the AN102can ignore or skip a fourth instance of the CSI-RS1through CSI-RS3, which are also denoted using an “X” inFIG.3B, as a result of the fourth instance of the CSI-RS1and fourth instance of the CSI-RS2occur during the LBT Failure. In this other example, the AN102can process and/or transmit a fifth instance of the CSI-RS1through CSI-RS3which occurs during a second channel occupancy time (COT2) when the spectrum carrying the downlink communication beams106.1through106.3is not occupied by other transmissions.

FIG.4graphically illustrates another exemplary downlink beam scheduling procedure that can be utilized by the exemplary wireless network for unlicensed operation in accordance with various embodiments. As described above inFIG.1, the AN102can perform a downlink beam scheduling procedure to selectively control which downlink communication beams from among the downlink communication beams106.1through106.mare to be used to transmit the channel-state information reference signals (CSI-RSs) to the UE104. In the exemplary embodiment illustrated inFIG.4, the AN102can perform the exemplary downlink beam scheduling procedures to be described in further detail below to periodically and/or aperiodically transmit at least a CSI-RS1over one or more of the downlink communication beams106.1through106.m. ThroughoutFIG.4, the CSI-RS1is illustrated using medium shading. It should be noted that the various exemplary downlink beam scheduling procedures illustrated inFIG.4are not limited to the CSI-RS1. Those skilled in the relevant art(s) will recognize that these exemplary downlink beam scheduling procedures can be utilized to schedule transmission of any suitable number of CSI-RSs over any suitable number of downlink communication beams from among the downlink communication beams106.1through106.mthat will be apparent to those skilled in the relevant art(s) without departing from the spirit and scope of the present disclosure.

As illustrated inFIG.4, the AN102can perform a downlink beam scheduling procedure400to schedule a periodic transmission and/or an aperiodic transmission of the CSI-RS1over the downlink communication beams106.1through106.mas illustrated by a CSI-RS schedule402. Thereafter, the AN102can identify valid beam pairings between the AN102and the UE104for the downlink communication beams106.1through106.m. In the exemplary embodiment illustrated inFIG.4, the AN102can store a listing of slots404that are associated with valid beam pairings between the AN102and the UE104. In the exemplary embodiment illustrated inFIG.4, those slots, for example, a first slot, a fifth slot, a ninth slot, that are shaded in the listing of slots404are associated with valid beam pairings between the AN102and the UE104. Thereafter, the AN102can identify instances of the CSI-RSi from the CSI-RS schedule402that coincide with the valid beam pairings from the listing of slots404. In some embodiments, the AN102can process and/or transmit those instances of the CSI-RS1that coincide with valid beam pairings between the AN102and the UE104as indicated by shading in a CSI-RS schedule406and can ignore or skip instances of the CSI-RS1that do not coincide with valid beam pair which are denoted using an “X” in the CSI-RS schedule406. In some embodiments, the AN102can provide the CSI-RS schedule406in the one or more channel occupancy time (COT) indicators and/or the one or more beam indicators as described above inFIG.3Ato the UE104to allow the UE104to determine which instances of the CSI-RS1have been ignored or skipped by the AN102.

FIG.5graphically illustrates a further exemplary downlink beam scheduling procedure that can be utilized by the exemplary wireless network for unlicensed operation in accordance with various embodiments. As described above inFIG.1, the AN102can perform a downlink beam scheduling procedure to selectively control which downlink communication beams from among the downlink communication beams106.1through106.mare to be used to transmit the channel-state information reference signals (CSI-RSs) to the UE104. In the exemplary embodiment illustrated inFIG.5, the AN102can perform the exemplary downlink beam scheduling procedures to be described in further detail below to periodically and/or aperiodically transmit at least CSI-RS1through CSI-RS3over the downlink communication beams106.1through106.3. ThroughoutFIG.5, the CSI-RS1is illustrated using dark shading, the CSI-RS2is illustrated using medium shading, and the CSI-RS3is illustrated using light shading. It should be noted that the various exemplary downlink beam scheduling procedures illustrated inFIG.5are not limited to the CSI-RS1through the CSI-RS3. Those skilled in the relevant art(s) will recognize that these exemplary downlink beam scheduling procedures can be utilized to schedule transmission of any suitable number of CSI-RSs over any suitable number of downlink communication beams from among the downlink communication beams106.1through106.mthat will be apparent to those skilled in the relevant art(s) without departing from the spirit and scope of the present disclosure.

As illustrated inFIG.5, the AN102can perform a downlink beam scheduling procedure500to schedule a periodic transmission and/or an aperiodic transmission of the CSI-RS1through the CSI-RS3over the downlink communication beams106.1through106.3. In some embodiments, the downlink beam scheduling procedure300can schedule the periodic and/or the aperiodic transmission of the CSI-RS1through the CSI-RS3to be substantially similar to one or more of the beam scheduling procedures as described above inFIG.2AthroughFIG.2E. In the exemplary embodiment illustrated inFIG.5, the AN102can process and/or transmit a first instance of the CSI-RS1through the CSI-RS3as scheduled by the downlink beam scheduling procedure500during a first channel occupancy time (COL). However, as illustrated inFIG.5, while the AN102is processing and/or transmitting a second instance of the CSI-RS1through the CSI-RS3, the LBT procedure indicates that the spectrum, for example, the unlicensed spectrum as described above, carrying the downlink communication beams106.1through106.3is now occupied by other transmissions which is denoted as an LBT Failure inFIG.5. In the exemplary embodiment illustrated inFIG.5, the LBT procedure can generate an indication of the LBT Failure when the portion, or the portions, of the unlicensed spectrum is occupied by other transmissions from other devices. In some embodiments, the AN102can ignore or skip those CSI-RSs from among the CSI-RS1through the CSI-RS3which the downlink beam scheduling procedure500has scheduled to process and/or transmit during the LBT Failure. For example, as illustrated inFIG.5, the AN102can ignore or skip the second instance of the CSI-RS3, which is denoted using an “X” inFIG.5, which occurs during the LBT Failure. In some embodiments, the AN102can process and/or transmit a third instance of the CSI-RSi through the CSI-RS3during a second channel occupancy time (COT2) when the spectrum carrying the downlink communication beams106.1through106.3is not occupied by other transmissions. As illustrated inFIG.5, the AN102can begin to process and/or transmit the third instance of the CSI-RS1through the CSI-RS3during a start of the second channel occupancy time (COT2) with the periodicity of the CSI-RS1through the CSI-RS3starting from the start of the second channel occupancy time (COT2). In some embodiments, the AN102can provide the one or more channel occupancy time (COT) indicators and/or the one or more beam indicators as described above inFIG.3Ato the UE104to allow the UE104to determine which instances of the CSI-RS1through the CSI-RS3have been ignored or skipped by the AN102and/or the start of the second channel occupancy time (COT2).

FIG.6AthroughFIG.6Cgraphically illustrate yet further exemplary downlink beam scheduling procedures that can be utilized by the exemplary wireless network for unlicensed operation in accordance with various embodiments. As described above inFIG.1, the AN102can perform a downlink beam scheduling procedure to selectively control which downlink communication beams from among the downlink communication beams106.1through106.mare to be used to transmit the channel-state information reference signals (CSI-RSs) to the UE104. In the exemplary embodiments illustrated inFIG.6AthroughFIG.6C, the AN102can perform the exemplary downlink beam scheduling procedures to be described in further detail below to periodically and/or aperiodically transmit at least the CSI-RS1over the downlink communication beams106.1through106.m. ThroughoutFIG.6AthroughFIG.6C, the CSI-RS is illustrated using medium shading. It should be noted that the various exemplary downlink beam scheduling procedures illustrated inFIG.6AthroughFIG.6Care not limited to the CSI-RS1. Those skilled in the relevant art(s) will recognize that these exemplary downlink beam scheduling procedures can be utilized to schedule transmission of any suitable number of CSI-RSs over any suitable number of downlink communication beams from among the downlink communication beams106.1through106.mthat will be apparent to those skilled in the relevant art(s) without departing from the spirit and scope of the present disclosure.

As illustrated inFIG.6A, the AN102can perform a first downlink beam scheduling procedure600to schedule a periodic transmission and/or an aperiodic transmission of the CSI-RS1over the downlink communication beams106.1through106.m. In some embodiments, the first downlink beam scheduling procedure600can schedule the periodic and/or the aperiodic transmission of the CSI-RS1to be substantially similar to one or more of the beam scheduling procedures as described above inFIG.2AthroughFIG.2E. In the exemplary embodiment illustrated inFIG.6A, the AN102can process and/or transmit the periodic transmission and/or the aperiodic transmission of the CSI-RS1as scheduled by the first downlink beam scheduling procedure600to be within a blind CSI-RS range. In the exemplary embodiment illustrated inFIG.6A, the blind CSI-RS range represents a tolerance range that the UE104is expected to blindly search for the CSI-RS1. In some embodiments, the tolerance range can be based upon the periodicity of the CSI-RS1.

As illustrated inFIG.6BandFIG.6C, the AN102can perform a second downlink beam scheduling procedure602and a third downlink beam scheduling procedure604, respectively, to schedule a periodic transmission and/or an aperiodic transmission of the CSI-RSi over the downlink communication beams106.1through106.m. In some embodiments, the downlink beam scheduling procedure600can schedule the periodic and/or the aperiodic transmission of the CSI-RSi to be substantially similar to one or more of the beam scheduling procedures as described above inFIG.2AthroughFIG.2E. In the exemplary embodiment illustrated inFIG.6BandFIG.6C, the AN102can process and/or transmit the periodic transmission and/or the aperiodic transmission of the CSI-RSi as scheduled by the second downlink beam scheduling procedure602and/or the third downlink beam scheduling procedure604to be within a CSI-RS range with indication. In the exemplary embodiment illustrated inFIG.6BandFIG.6C, the AN102can provide one or more discoverable indicators, such as the one or more channel occupancy time (COT) indicators and/or the one or more beam indicators as described above inFIG.3A, to signal presence of CSI-RSi in a specific position within the CSI-RS range with indication. In the exemplary embodiment illustrated inFIG.6B, the AN102can provide the one or more discoverable indicators within the tolerance range, namely, within the CSI-RS range with indication. In the exemplary embodiment illustrated inFIG.6B, the AN102can provide the one or more discoverable indicators before the tolerance range, namely, before the CSI-RS range with indication. In some embodiments, the one or more discoverable indicators can indicate parameters for a single CSI tolerance range or more than one CSI-RS tolerance range, for example, semi-persistent signaling. In these embodiments, the parameters can include time and/or frequency location, for example, as an offset within variable period, and/or a number of periods for which indicator is valid. In some embodiments, the one or more discoverable indicators can be combined with beam-scheduling information, for example, as described above inFIG.5, in one or more Downlink Control Information (DCI) messages. In some embodiments, the one or more DCI messages can indicate that CSI-RSi is frequency division multiplexed with data and is Quasi Co-Located with specific Synchronization Signal Blocks (SSBs), CSI-RSi is Quasi Co-Located with specific specific Synchronization Signal Blocks (SSBs) and can be used for BFR, and/or CSI-RSi is to be used for beam failure recovery (BFR).

Exemplary Beam Failure Detection (BFD) Procedures

As describe above inFIG.1, the UE104can utilize the channel-state information reference signal (CSI-RS) within a downlink communication beam from among the downlink communication beams106.1through106.mas described above inFIG.1to assess a radio link quality of the downlink communication beam. In some embodiments, the UE104can monitor the radio link quality of the downlink communication beam and can thereafter provide an indication, referred as a beam failure indication (BFI), when the radio link quality of the downlink communication beam indicates the downlink communication beam is failing. In some embodiments, the UE104can monitor a predetermined PDCCH block error rate (BLER) of the CSI-RS to determine whether the downlink communication beam is failing. In some embodiments, the UE104can be configured with a set of CSI-RS resources, referred to as set q0, for beam failure detection (BFD). In these embodiments, the UE104can measure the radio link quality of the downlink communication beam in the CSI-RS resource set q0. When the measured radio link quality for the CSI-RS resources in set q0is worse than a pre-defined threshold, the UE104can identify the downlink communication beam as failing. The UE104can generate a beam failure indication (BFI) when the downlink communication beam is identified as failing. When the number of BFIs reaches a certain value or threshold, for example, a maximum number of beam failure indications, MBH, the UE104can begin a beam failure recovery (BFR) procedure as to be described in further detail.

FIG.7illustrates a flowchart of an exemplary beam failure detection (BFD) procedure that can be utilized by the exemplary wireless network in accordance with various embodiments. The disclosure is not limited to this operational description. Rather, it will be apparent to ordinary persons skilled in the relevant art(s) that other operational control flows are within the scope and spirit of the present disclosure. The following discussion describes an exemplary operational control flow700which executes the exemplary BFD procedure to identify a downlink communication beam within the exemplary wireless network that is failing. In the exemplary embodiment illustrated inFIG.7, the exemplary operational control flow700can be performed by a UE, such as the UE104as described above inFIG.1, to detect a downlink communication beam from among the downlink communication beams106.1through106.mthat has failed.

At operation702, the exemplary operational control flow700initializes the exemplary beam failure detection (BFD) procedure as to be described in further detail below in operation704through716. As part of this initialization, the exemplary operational control flow700sets a beam failure indication counter to an initial value, such as zero (0) to provide an example. As to be described in further detail below, the exemplary operational control flow700accumulates the number of the beam failure indications (BFIs) that are generated during a beam failure detection (BFD) window as indicated by a beam failure detection timer. In some embodiments, the exemplary operational control flow700can additionally, or alternatively, start, or re-start, the beam failure detection timer at operation702. As to be described in further detail below, the exemplary operational control flow700can accumulate the beam failure indications (BFIs) before expiration of the beam failure detection timer to determine whether the downlink communication beam has failed.

At operation704, the exemplary operational control flow700determines whether the beam failure detection timer from operation702has expired. If the exemplary operational control flow700determines the beam failure detection timer from operation702has expired, the operational control flow700reverts to operation702to once again set the beam failure indication counter from operation702to the initial value and to start, or re-start, the beam failure detection timer from operation702. Otherwise, the operational control flow700proceeds to operation706when the beam failure detection timer from operation702has not expired.

At operation706, the exemplary operational control flow700monitors a radio link quality of the downlink communication beam and can thereafter generate an indication, referred as a beam failure indication (BFI), when the radio link quality of the downlink communication beam indicates the downlink communication beam is failing. In some embodiments, the exemplary operational control flow700can monitor a block error rate (BLER) of a channel-state information reference signal (CSI-RS) within the downlink communication beam to determine whether the downlink communication beam is failing. In these embodiments, the exemplary operational control flow700can determine that the downlink communication beam is failing when the BLER of the CSI-RS meets or exceeds a predetermined PDCCH BLER target, also referred to as an out-of-sync (OOS) threshold Qout,LR. In some embodiments, predetermined PDCCH BLER target can represent a percentage of a predetermined PDCCH BLER of a predetermined PDCCH transmission.

In some embodiments, an access node (AN), such as the AN102to provide an example, can configure the predetermined PDCCH BLER target for use by the exemplary operational control flow700and can thereafter provide the predetermined PDCCH BLER target to the exemplary operational control flow700in one or more Downlink Control Information (DCI) messages. In some embodiments, the predetermined PDCCH BLER target can be based upon properties of the CSI-RS, for example, a periodicity of the CSI-RS and/or on the type of environment, for example, licensed or unlicensed access. In some embodiments, the predetermined PDCCH BLER target is selected based on a periodicity of the CSI-RS, for example, the periodicity of the CSI-RS as illustrated inFIG.2AthroughFIG.2Eabove. For example, the periodicity of the CSI-RS can be set to a value of one (1) to generate a predetermined PDCCH BLER target of 10%, for example, 10% BLER of PDCCH transferring DCI format 1_0 having a Control Channel Element(CCE) Aggregation Length of eight (8) 8 and a Control Resource Set (CORESET) length of two (2), in a licensed access environment or a Rel-15 or Rel-16 environment. In another example, the periodicity of the CSI-RS can be set to a value of two (2) to generate a predetermined PDCCH BLER target less than 10%, for example 5%, to allow for more sensitivity to beam failure and/or greater than 10%, for example, 15%, to account for losses from listen before talk (LBT) skipping and/or from random beam scheduling. Alternatively, or in addition to, the predetermined PDCCH BLER target can be set to a single value for all periodicities of the CSI-RS and can be dynamically adjusted to account for scenarios, such as a LBT scenario to provide an example, where the AN102does not transmit the CSI-RS to the UE. In some embodiments, the exemplary operational control flow700can modify the predetermined PDCCH BLER target in response to indications of non-scheduling and/or non-transmission of the CSI-RS by the AN102, for example, the one or more channel occupancy time (COT) indicators and/or the one or more beam indicators as described above inFIG.3A.

At operation706, the exemplary operational control flow700reverts to operation704to once again determine whether the beam failure detection timer from operation702has expired when the beam failure indication (BFI) has not been generated. Otherwise, the operational control flow700proceeds to operation708when the beam failure indication (BFI) has been generated.

At operation708, the exemplary operational control flow700increments the beam failure indication counter from operation702in response to the beam failure indication (BFI) being generated at operation708.

At operation710, the exemplary operational control flow700determines whether the AN102is scheduled to transmit or transmits the CSI-RS within the downlink communication beam at various instances in time. In some embodiments, the exemplary operational control flow700evaluates a CSI-RS transmission indication, such as the one or more channel occupancy time (COT) indicators and/or the one or more channel occupancy time (COT) indicators and/or the one or more beam indicators as described above inFIG.3A, to determine whether the AN102is to transmit the CSI-RS within the downlink communication beam. In some embodiments, the AN102can provide the CSI-RS transmission indication to the exemplary operational control flow700in one or more Downlink Control Information (DCI) messages. In some embodiments, the exemplary operational control flow700can generate the beam failure indication (BFI) at operation706even when the AN102does not transmit, for example, is not scheduled to transmit, the CSI-RS within the downlink communication beam. In these situations, the exemplary operational control flow700evaluates the CSI-RS transmission indication to determine whether the AN102is to transmit the CSI-RS within the downlink communication beam for every beam failure indication (BFI) generated by the exemplary operational control flow700at operation708. However, in some embodiments, the exemplary operational control flow700can perform operation710and operation712, which is to be described in further detail below, prior to operation706.

At operation710, the exemplary operational control flow700proceeds to operation712when the CSI-RS transmission indication indicates that the AN102is not to transmit the CSI-RS within the downlink communication beam. Otherwise, the exemplary operational control flow700proceeds to operation714when the CSI-RS transmission indication indicates that the AN102is to transmit the CSI-RS within the downlink communication beam.

At operation712, the exemplary operational control flow700decrements the beam failure indication counter from operation702in response to the CSI-RS transmission indication indicating that the AN102is to transmit the CSI-RS within the downlink communication beam.

At operation714, the exemplary operational control flow700compares the beam failure indication counter from operation702which has accumulated the beam failure indications (BFIs) generated before the expiration of the beam failure detection timer from operation702with a maximum number of beam failure indications, MBFI. The exemplary operational control flow700reverts to operation704to once again determine whether the beam failure detection timer from operation702has expired when the beam failure indication counter from operation702is less than the maximum number of beam failure indications MBFI. Otherwise, the operational control flow700proceeds to operation716when the beam failure indication counter from operation702is greater than or equal to the maximum number of beam failure indications MBFI.

At operation716, the exemplary operational control flow700determines that the downlink communication beam has failed. In some embodiments, the UE executing the exemplary operational control flow700can begin a beam failure recovery (BFR) procedure, as to be described in further detail below, once the exemplary operational control flow700determines that the downlink communication beam has failed.

Exemplary Beam Failure Recovery Procedures

Once the UE104has determined the downlink communication beam has failed as described above, the UE104undergoes a beamforming failure recovery (BFR) procedure as to be described in further detail below. As part of this BFR procedure, the UE104identifies one or more new candidate downlink communication beams from among the downlink communication beams106.1through106.mfrom a candidate beam list and thereafter identifies the one or more new candidate downlink communication beams in a beam failure recovery request (BFRQ) provided to the AN102over one or more contention free uplink channels, such as a physical random access channel (PRACH) and/or one or more contention uplink control channels, such as a Physical Uplink Control Channel (PUCCH) and/or a Physical Uplink Shared Channel (PUSCH), to provide some examples. In some embodiments, the PRACH, the PUCCH, and/or the PUSCH can represent uplink control channels associated with the downlink communication beam that has failed. In some embodiments, the UE104can identify a corresponding PRACH when there is a change to the periodic CSI-RS. In some embodiments, the AN102can configure an increased number of PRACH resources per possible CSI-RS resource whereby the UE104can identify closest PRACH occasion to the one or more new candidate downlink communication beams. In some embodiments, these of PRACH resources can be shifted relative to the start of the COT when the CSI-RS is similarly shifted relatively to the start of the COT. In some embodiments the one or more Downlink Control Information (DCI) messages can include contains resources for the associated RACH, for example, can indicate one or more of k3 (relative slot from CSI-RS resource), frequency resource and/or time resource within the relative slot. In some embodiments, the BFRQ identifies an identifier of the UE104and the one or more new candidate downlink communication beams. Thereafter, the UE104monitors downlink control channels, for example, a Physical Downlink Control Channel (PDCCH) and/or a Physical Downlink Shared Channel (PDSCH), corresponding to the one or more new candidate downlink communication beams for a response from the AN102to the BFRQ, and can thereafter utilize the one or more new candidate downlink communication beams upon receiving the response from the AN102.

Exemplary Embodiments for Access Nodes and/or User Equipment (UE) Within the Exemplary Wireless Network

FIG.8illustrates a block diagram of exemplary wireless systems of electronic devices according to some embodiments of the disclosure. In the exemplary embodiment illustrated inFIG.8, a wireless system800of the electronic device can include processor circuitry802, physical layer (PHY) circuitry804, an antenna array806, a communication infrastructure808, and a memory subsystem810. The wireless system800as illustrated inFIG.8can be implemented as a standalone, or a discrete device, and/or can be incorporated within or coupled to another electrical device, or host device, such as a wireless communication device, a smart phone, a laptop computing device, a desktop computing device, a tablet computing device, a personal assistants, a monitor, a television, a wearable device, and/or any other suitable electronic device that will be apparent to those skilled in the relevant art(s). The wireless system800as illustrated inFIG.8can represent an exemplary embodiment of the AN102and/or the UE104as described above inFIG.1and/or can be incorporated within or coupled to the AN102and/or the UE104as described above inFIG.1.

In the exemplary embodiment illustrated inFIG.8, the processor circuitry802can include, or can be, any of a microprocessor, graphics processing unit, or digital signal processor, and their electronic processing equivalents, such as an Application Specific Integrated Circuit (ASIC) or Field Programmable Gate Array (FPGA). The processor circuitry802signifies one or more tangible data and information processing devices that physically transform data and information, typically using sequence transformations, also referred to as an operational control flow. Data and information can be physically represented by an electrical, magnetic, optical or acoustical signal that is capable of being stored, accessed, transferred, combined, compared, or otherwise manipulated by the processor circuitry802. The processor circuitry802can signify a singular processor and multi-core systems or multi-processor arrays, including graphic processing units, digital signal processors, digital processors or combinations of these elements. In some embodiments, the processor circuitry802can execute one or more elements of a protocol stack, for example one or more elements of a 5G protocol stack as to be described below in further detail.

The PHY circuitry804includes circuitry and/or control logic to carry out various radio/network protocol and radio control functions that enable communication with one or more radio networks. The radio control functions can include, but are not limited to, signal modulation/demodulation, encoding/decoding, and/or radio frequency shifting to provide some examples. In some embodiments, the PHY circuitry804can perform Fast-Fourier Transform (FFT), pre-coding, and/or constellation mapping/de-mapping functionality. In some embodiments, the PHY circuitry804can perform convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoding/decoding. In the exemplary embodiment illustrated inFIG.8, the PHY circuitry804can process baseband signals received from the communication infrastructure808and to generate baseband signals for the communication infrastructure808. In some embodiments, the PHY circuitry804can connect to and communicate on wireline and/or wireless networks. For example, the PHY circuitry804can include a wireless subsystem, for example, cellular subsystem, a WLAN subsystem, and/or a Bluetooth™ subsystem, having various wireless radio transceiver and wireless protocol(s) as will be understood by those skilled in the relevant art(s) without departing from the sprit and scope of the disclosure. The wireless subsystem can include circuitry and/or control logic for connecting to and communicating on wireless networks. The wireless networks can include cellular networks such as, but are not limited to, 3G/4G/5G wireless networks, Long-Term Evolution (LTE) wireless networks, and the like to provide some examples.

In some embodiments, the processor circuitry802and/or the PHY circuitry804can execute the 5G protocol stack having at least a 5G layer-1, a 5G layer-2, and a 5G layer-3. The 5G layer-1 can include a physical (PHY) layer. The PHY layer can transmit and/or receive physical layer signals over one or more physical channels that may be received from and/or transmitted to the one or more radio networks. The PHY layer can further perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (for example, initial synchronization and handover purposes), and other measurements used by higher layers, such as the RRC layer. The PHY layer can further perform error detection on one or more transport channels, forward error correction (FEC) coding/decoding of the one or more transport channels, modulation/demodulation of the one or more physical channels, interleaving, rate matching, mapping onto the one or more physical channels, and Multiple Input Multiple Output (MIMO) antenna processing. In some embodiments, the PHY layer can process requests from and provide indications to the MAC layer over one or more transport channels.

The 5G layer-2 can include a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer, and a Packet Data Convergence Protocol (PDCP) layer. The MAC layer processes requests from, and provides indications to, the RLC layer over one or more logical channels. The MAC layer can perform mapping between the one or more logical channels and the one or more transport channels, multiplexing of MAC Service Data Units (SDUs) from one or more logical channels onto Transport Blocks (TBs) to be delivered to the PHY layer via the one or more transport channels, de-multiplexing the MAC SDUs to one or more logical channels from TBs delivered from the PHY layer via the one or more transport channels, multiplexing the MAC SDUs onto TBs, scheduling information reporting, error correction through HARQ, and logical channel prioritization. The RLC layer processes requests from and provides indications to the PDCP layer over one or more RLC channels. The RLC930may operate in a plurality of modes of operation, including: Transparent Mode (TM), Unacknowledged Mode (UM), and

Acknowledged Mode (AM). The RLC930may execute transfer of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transfers, and concatenation, segmentation and reassembly of RLC SDUs for UM and AM data transfers. The RLC930may also execute re-segmentation of RLC data PDUs for AM data transfers, reorder RLC data PDUs for UM and AM data transfers, detect duplicate data for UM and AM data transfers, discard RLC SDUs for UM and AM data transfers, detect protocol errors for AM data transfers, and perform RLC re-establishment.

The PDCP layer processes requests from and provides indications to the RRC layer over one or more radio bearers. The PDCP layer may execute header compression and decompression of Internet Protocol (IP) data, maintain PDCP Sequence Numbers (SNs), perform in-sequence delivery of upper layer PDUs at re-establishment of lower layers, eliminate duplicates of lower layer SDUs at re-establishment of lower layers for radio bearers mapped on RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, control timer-based discard of data, and perform security operations such as ciphering, deciphering, integrity protection, and/or integrity verification to provide some examples.

The 5G layer-3 can include the Radio Resource Control (RRC) layer. The RRC layer configures aspects of the 5G layer-1, the 5G layer-2, and/or the 5G layer-3. The RRC layer can include broadcast of system information, broadcast of system information related to the access stratum (AS), paging, establishment, maintenance and release of RRC connection between UEs and access nodes, for example, RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release, establishment, configuration, maintenance and release of point to point Radio Bearers, security functions including key management, inter-RAT mobility, and measurement configuration for UE measurement reporting.

The antenna array806can include one or more antenna elements, each of which is capable of converting electrical signals into radio waves to travel through the air through communication beams, such as the communication beams106.1through106.mand/or the communication beams108.1through108.nas described above inFIG.1. The one or more antenna elements can be omnidirectional, direction, or a combination thereof.

The memory subsystem810includes a number of memories including a main random-access memory (RAM), or other volatile storage device, for storage of instructions and data during program execution and/or a read only memory (ROM) in which instructions are stored. The memory subsystem810can provides persistent storage for program and data files, and may include a hard disk drive, a floppy disk drive along with associated removable media, a CD-ROM drive, an optical drive, a flash memory, or removable media cartridges. In the exemplary embodiment illustrated inFIG.8, the memory subsystem810can optionally include an operating system812and an application814. The operating system812can be Microsoft's Windows, Sun Microsystems's Solaris, Apple Computer's MacOs, Linux or UNIX to provide some examples. The computer system also typically can include a Basic Input/Output System (BIOS) and processor firmware. The operating system, the BIOS, and/or the firmware can be used by the processor circuitry802to control the PHY circuitry804, the antenna array806, the communication infrastructure808, and/or the memory subsystem810. In some embodiments, the operating system812maintains one or more network protocol stacks, such as an Internet Protocol (IP) stack, and/or a cellular protocol stack to provide some examples, that can include a number of logical layers. At corresponding layers of the protocol stack, the operating system812includes control mechanism and data structures to perform the functions associated with that layer. The application814can include applications, for example, used by the wireless system800and/or a user of wireless system800. The applications in application254can include applications such as, but not limited to, Siri™, FaceTime™, radio streaming, video streaming, remote control, and/or other user applications which will be recognized by those skilled in the relevant art(s).

CONCLUSION

It is to be appreciated that the Detailed Description section, and not the Summary and Abstract sections, is intended to be used to interpret the claims. The Summary and

Abstract sections may set forth one or more but not all exemplary embodiments of the disclosure as contemplated by the inventor(s), and thus, are not intended to limit the disclosure and the appended claims in any way.

The disclosure has been described above with the aid of functional building blocks illustrating the implementation of specified functions and relationships thereof. The boundaries of these functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternate boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed.

The foregoing description of the specific embodiments will so fully reveal the general nature of the disclosure that others can, by applying knowledge within the skill of the art, readily modify and/or adapt for various applications such specific embodiments, without undue experimentation, without departing from the general concept of the disclosure. Therefore, such adaptations and modifications are intended to be within the meaning and range of equivalents of the disclosed embodiments, based on the teaching and guidance presented herein. It is to be understood that the phraseology or terminology herein is for the purpose of description and not of limitation, such that the terminology or phraseology of the present specification is to be interpreted by the skilled artisan in light of the teachings and guidance.

The breadth and scope of the disclosure should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.

As described above, aspects of the present technology may include the gathering and use of data available from various sources, e.g., to improve or enhance functionality. The present disclosure contemplates that in some instances, this gathered data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, Twitter ID's, home addresses, data or records relating to a user's health or level of fitness (e.g., vital signs measurements, medication information, exercise information), date of birth, or any other identifying or personal information. The present disclosure recognizes that the use of such personal information data, in the present technology, may be used to the benefit of users.

The present disclosure contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. Such policies should be easily accessible by users, and should be updated as the collection and/or use of data changes. Personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection/sharing should only occur after receiving the informed consent of the users. Additionally, such entities should consider taking any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices. In addition, policies and practices should be adapted for the particular types of personal information data being collected and/or accessed and adapted to applicable laws and standards, including jurisdiction-specific considerations. For instance, in the US, collection of, or access to, certain health data may be governed by federal and/or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); whereas health data in other countries may be subject to other regulations and policies and should be handled accordingly. Hence different privacy practices should be maintained for different personal data types in each country.

Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, the present technology may be configurable to allow users to selectively “opt in” or “opt out” of participation in the collection of personal information data, e.g., during registration for services or anytime thereafter. In addition to providing “opt in” and “opt out” options, the present disclosure contemplates providing notifications relating to the access or use of personal information. For instance, a user may be notified upon downloading an app that their personal information data will be accessed and then reminded again just before personal information data is accessed by the app.

Moreover, it is the intent of the present disclosure that personal information data should be managed and handled in a way to minimize risks of unintentional or unauthorized access or use. Risk can be minimized by limiting the collection of data and deleting data once it is no longer needed. In addition, and when applicable, including in certain health related applications, data de-identification can be used to protect a user's privacy. De-identification may be facilitated, when appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of data stored (e.g., collecting location data a city level rather than at an address level), controlling how data is stored (e.g., aggregating data across users), and/or other methods.

Therefore, although the present disclosure may broadly cover use of personal information data to implement one or more various disclosed embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data.