CN112771954B

CN112771954B - Carrier selection for beam failure recovery

Info

Publication number: CN112771954B
Application number: CN201880098109.XA
Authority: CN
Inventors: S·图尔蒂南; 吴春丽; T·科斯克拉; D·科齐奥尔
Original assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy
Current assignee: Nokia Communications (Shanghai) Co., Ltd.; Nokia Solutions and Networks Oy
Priority date: 2018-09-28
Filing date: 2018-09-28
Publication date: 2024-02-23
Anticipated expiration: 2038-09-28
Also published as: WO2020062085A1; CN112771954A

Abstract

A method includes: selecting an uplink carrier for a random access procedure; and using the uplink carrier for a random access procedure, wherein when a random access procedure is initiated for beam failure recovery, selecting The uplink carrier is performed according to the first condition, and when the random access procedure is initiated but not initiated for beam failure recovery, the selection of the uplink carrier is performed according to the second condition, which second condition is different from the first condition .

Description

Carrier selection for beam fault recovery

Technical Field

Embodiments of the present disclosure relate to carrier selection for beam fault recovery. Some embodiments relate to controlling selection of supplemental uplink carriers for beam fault recovery.

Background

It is desirable to optimize beam fault recovery. Beam fault recovery uses a standard random access procedure.

The inventors have realized that it is desirable to optimize the random access procedure, and in particular the random access procedure for beam fault recovery.

The selection of the correct carrier helps to optimise the random access procedure and in particular the random access procedure for beam fault recovery.

Disclosure of Invention

According to various, but not necessarily all, embodiments there is provided a method comprising:

selecting an uplink carrier for a random access procedure; and

the uplink carrier is used for a random access procedure,

wherein the selection of the uplink carrier is performed according to a first condition when a random access procedure is initiated for beam fault recovery and the selection of the uplink carrier is performed according to a second condition different from the first condition when the random access procedure is initiated but not initiated for beam fault recovery.

In some, but not all examples, the first condition compares the measured downlink carrier characteristic to a first threshold when the first threshold is configured.

In some, but not all examples, the first condition compares the measured downlink carrier characteristic to a threshold different from the first threshold when the first threshold is not configured.

In some, but not all examples, the second condition compares the measured downlink carrier characteristic to a second threshold different from the first threshold.

In some, but not all examples, the second condition is independent of the first threshold.

In some, but not all examples, the first condition compares the measured downlink carrier characteristic to a second threshold different from the first threshold when the first threshold is not configured.

In some, but not all examples, selecting the uplink carrier is performed according to a comparison of the measured downlink carrier characteristics to a first threshold when a random access procedure is initiated for beam fault recovery, and selecting the uplink carrier is performed according to a comparison of the measured downlink carrier characteristics to a second threshold when a random access procedure is initiated but not initiated for beam fault recovery.

In some, but not all examples, the method further comprises: the first threshold is determined using a threshold parameter that at least partially determines the first threshold.

In some, but not all examples, the threshold parameter is an offset from a second threshold value, which is added to the second threshold value to create the first threshold value.

In some, but not all examples, when the threshold parameter is not configured, the offset is assumed to be zero.

In some, but not all examples, the threshold parameter defines the first threshold independent of the second threshold.

In some, but not all examples, the measured downlink carrier characteristics depend on received signal power and/or received signal quality.

In some, but not all examples, the measured carrier characteristic is a Reference Signal Received Power (RSRP) for the selected downlink channel, e.g., a downlink pathloss reference.

In some, but not all examples, the first condition depends on a comparison of the measured downlink carrier characteristic to a first threshold and additional conditions.

In some, but not all examples, the additional condition depends on the availability of contention-free random access resources.

In some, but not all examples, the additional condition depends on the availability of a beam fault recovery configuration for the currently active portion of bandwidth.

In some, but not all examples, the first condition depends on a comparison of the measured downlink carrier characteristic to a first threshold value in the case where there is already a configuration of the first threshold value, and the first condition depends on a comparison of the measured downlink carrier characteristic to a different threshold value in the case where there is no configuration of the first threshold value.

In some, but not all examples, the first condition and the second condition provide separate logical paths, each supporting selection between a normal uplink carrier (NUL) and a supplementary uplink carrier (SUL).

In some, but not all examples, an apparatus includes means for performing, or means for causing to perform, the method.

According to various, but not necessarily all, embodiments there is provided an apparatus comprising means for:

selecting an uplink carrier for a random access procedure; and

the uplink carrier is used for a random access procedure,

In some, but not all examples, the apparatus includes means for determining the first threshold using a threshold parameter that at least partially determines the first threshold.

In some, but not all examples, the threshold parameter is an offset from a second threshold value, the offset being added to the second threshold value to create the first threshold value, or wherein the threshold parameter defines the first threshold value independent of the second threshold value.

In some, but not all examples, the apparatus includes means for selecting a carrier in dependence on a comparison of the measured downlink carrier characteristic with a first threshold and an additional condition.

In some, but not all examples, the additional condition depends on the availability of contention-free random access resources and/or on the availability of beam-failure recovery resources for the currently active portion of bandwidth.

In some, but not all examples, the apparatus is configured to select a carrier that is either an uplink normal carrier or an uplink supplemental carrier, wherein the supplemental carrier is a borrowed downlink carrier that is less frequent than the uplink normal carrier.

In some, but not all examples, the apparatus is configured as a mobile device or as a user equipment.

According to various, but not necessarily all, embodiments there is provided an apparatus comprising:

At least one processor; and

at least one memory including computer program code,

the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform:

selecting an uplink carrier for a random access procedure; and

the uplink carrier is used for a random access procedure,

wherein the selecting of the uplink carrier is performed according to a comparison of the measured downlink carrier characteristics with a first threshold when a random access procedure is initiated for beam fault recovery, and the selecting of the uplink carrier is performed according to a comparison of the measured downlink carrier characteristics with a second threshold when the random access procedure is initiated but not initiated for beam fault recovery.

According to various, but not necessarily all, embodiments there is provided a computer program that, when run on a computer, performs:

selecting an uplink carrier for a random access procedure; and

the uplink carrier is used for a random access procedure,

According to various, but not necessarily all, embodiments there is provided a data structure comprising data defining threshold parameters, the threshold parameters being specifically used to distinguish between: a comparison of the measured downlink carrier characteristics with a first threshold when a random access procedure is initiated for beam fault recovery and a comparison of the measured downlink carrier characteristics with a second, different threshold when a random access procedure is initiated but not initiated for beam fault recovery.

detecting a beam fault; and

recovering from beam failure by:

selecting a carrier for random access; and

the carrier is used for random access,

wherein the selection of carriers is based on a comparison of the measured carrier characteristics with a first threshold value (when configured for beam fault recovery) and a second, different threshold value (when not configured for beam fault recovery).

In some, but not all examples, the configuration for beam fault recovery at least partially determines a threshold parameter of the first threshold.

In some, but not all examples, the threshold parameter is provided in an information element.

In some, but not all examples, when configured for beam fault recovery, selecting the carrier is based on a comparison of the measured carrier characteristics to a first threshold and additional conditions.

In some, but not all examples, the additional condition depends on the availability of beam fault recovery resources for the currently active portion of bandwidth.

In some, but not all examples, the measured carrier characteristic depends on the received signal power and/or the received signal quality.

In some, but not all examples, the first threshold and the second threshold are used to select between a normal uplink carrier (NUL) and a supplementary uplink carrier (SUL).

In some, but not all examples, the method includes modifying the measurements depending on whether the SUL or NUL has been assigned a beam fault recovery configuration.

In some, but not all examples, the selected carrier is an uplink normal carrier or an uplink supplemental carrier, where the supplemental carrier is a borrowed downlink carrier that is less frequent than the uplink normal carrier.

detecting a beam fault; and

recovering from beam failure by:

selecting a carrier for random access; and

the carrier is used for random access,

In some, but not all examples, the apparatus includes means for selecting a carrier when configured for beam fault recovery based on a comparison of the measured carrier characteristic to a first threshold and additional conditions.

In some, but not all examples, the additional condition depends on the availability of contention-free random access resources and/or the availability of beam-failure recovery resources for the currently active bandwidth portion.

at least one processor; and

at least one memory including computer program code,

detecting a beam fault; and

recovering from beam failure by:

Selecting a carrier for random access; and

the carrier is used for random access,

According to various, but not necessarily all, embodiments there is provided an apparatus configured as a mobile device or as a user equipment.

According to various, but not necessarily all, embodiments there is provided a computer program that, when run on a computer, performs: a carrier is selected for random access during beam fault recovery, wherein the selection of the carrier is based on a comparison of the measured carrier characteristics with a first threshold value (when configured for beam fault recovery) and a second, different threshold value (when not configured for beam fault recovery).

According to various, but not necessarily all, embodiments there is provided a data structure comprising data defining a threshold value for comparison with measured carrier characteristics to cause selection of carriers to which a beam fault recovery configuration has been assigned for random access during recovery from a beam fault, the carriers to which the beam fault recovery configuration has been assigned having precedence over carriers to which the beam fault recovery configuration has not been assigned.

determining which carrier is configured for beam fault recovery; and

the threshold used in controlling the selection of carriers for random access is different depending on which carrier is configured for beam fault recovery.

In some, but not all examples, the method includes: leading to a preference for carriers that have been assigned a beam fault recovery configuration.

In some, but not all examples, the method includes: resulting in an alternative selection of carriers that have not been assigned a beam fault recovery configuration.

In some, but not all examples, the method includes: causing the measured carrier characteristics and/or thresholds used in the comparison to select a carrier to be modified depending on which carrier has been assigned the beam fault recovery configuration.

In some, but not all examples, a threshold is used to select between a normal uplink carrier (NUL) and a supplementary uplink carrier (SUL).

In some, but not all examples, the method includes:

causing the first offset to be applied to the threshold when the SUL has been assigned a beam fault recovery configuration; and

When the NUL has been assigned a beam fault recovery configuration, causing a second offset to be applied to the threshold, wherein one of the first offset and the second offset is positive and the other is negative.

In some, but not all examples, the method includes:

causing use of a first threshold when the SUL has been assigned a beam fault recovery configuration; and

the use of a different second threshold is caused when NUL has been assigned a beam fault recovery configuration.

In some, but not all examples, the method includes: causing the measured carrier characteristics used in the comparison to be modified for the selected carrier depending on whether the SUL or NUL has been assigned a beam fault recovery configuration.

In some, but not all examples, assignment of a preamble for contention-free random access can only occur on one of the associated uplink normal carrier and uplink supplemental carrier, and assignment of a preamble for contention-free random access cannot occur for both the associated uplink normal carrier and uplink supplemental carrier.

Determining which carrier is configured for beam fault recovery; and

In some, but not all examples, the apparatus includes: leading to a preference for carriers that have been assigned a beam fault recovery configuration.

In some, but not all examples, the apparatus includes: means for causing an alternative selection of carriers for which a beam fault recovery configuration has not been assigned.

In some, but not all examples, the apparatus includes: means for causing an alternative selection of carriers that have not been assigned a beam fault recovery configuration.

In some, but not all examples, the apparatus includes: means for causing the measured carrier characteristics and/or thresholds used in the comparison to be modified for selecting a carrier depending on which carrier has been assigned a beam fault recovery configuration.

In some, but not all examples, the apparatus includes: the components used for:

In some, but not all examples, the apparatus includes means for:

causing the measured carrier characteristics used in the comparison to be modified for the selected carrier depending on whether the SUL or NUL has been assigned a beam fault recovery configuration.

In some, but not all examples, a network includes a plurality of network nodes, the network including the described apparatus.

determining which carrier is configured for beam fault recovery; and

detecting a beam fault; and

recovering from beam failure by:

selecting a carrier for random access; and

the carrier is used for random access,

wherein the selection of the carrier is dependent on a comparison of the measured carrier characteristics with a threshold value,

wherein the measured carrier characteristics and/or the threshold value are modified depending on whether the carrier has been assigned a beam fault recovery configuration.

a random access procedure is initiated and a random access procedure is initiated,

a carrier is selected for the random access procedure, wherein the selection of the carrier is based on a comparison of the measured carrier characteristics with a first threshold value (when beam fault recovery is performed) and a second, different threshold value (when beam fault recovery is not performed).

detecting a beam fault; and

recovering from beam failure by:

selecting a carrier for random access; and

the carrier is used for random access,

wherein selecting the carrier is based on whether the carrier is configured to perform beam fault recovery.

In some, but not all examples, the method includes:

preferentially selecting carriers that have been assigned a beam fault recovery configuration and that are sufficient for radio access; and

the carrier is used for random access by performing random access using the selected carrier.

In some, but not all examples, the method includes:

alternatively, selecting a carrier that has not been assigned a beam fault recovery configuration and is sufficient for radio access; and

the carrier is used for random access by performing contention-based random access using the selected carrier.

In some, but not all, examples, selecting carriers for random access depends on

(i) The carrier has not yet been assigned a beam fault recovery configuration; and

(ii) Whether the carrier is sufficient for radio access.

In some, but not all examples, the method includes:

Determining whether a carrier has or has not been assigned a beam fault recovery configuration; and

it is determined whether the carrier is sufficient for radio access.

In some, but not all examples, the method includes:

depending on whether one or more measured characteristics of the carrier are sufficient to determine whether the carrier is sufficient for radio access.

In some, but not all examples, the method includes: it is determined whether the carrier is sufficient for radio access depending on whether the carrier is in use or not, and if the carrier is not in use, it is determined whether one or more measurement characteristics of the carrier are sufficient or not.

In some, but not all examples, selecting the carrier includes comparing the measured carrier characteristic to a threshold.

In some, but not all examples, the method includes: the measured carrier characteristics and/or thresholds used in the comparison are modified depending on which carrier has been assigned a beam fault recovery configuration and which sufficient carriers are preferred for radio access.

In some, but not all examples, the method includes: whether the carrier is sufficient or whether the carrier is in use is determined depending on whether the one or more measurement characteristics of the carrier are sufficient for radio access and if the carrier is not in use is determined whether the one or more measurement characteristics of the carrier are sufficient.

In some, but not all examples, the characteristic depends on the received signal power and/or the received signal quality.

In some, but not all examples, the characteristic is a Reference Signal Received Power (RSRP) for the selected downlink channel, such as a downlink pathloss reference.

In some, but not all examples, the threshold is received in a BFR config IE.

In some, but not all examples, a threshold is used to select between a normal uplink carrier and a supplemental uplink carrier.

In some, but not all examples, the method includes:

applying a first offset to the threshold when the SUL has been assigned a beam fault recovery configuration; and

when NUL has been assigned a beam fault recovery configuration, a second offset is applied to the threshold, wherein one of the first and second offsets is positive and the other is negative.

In some, but not all examples, the method includes:

using a first threshold when the SUL has been assigned a beam fault recovery configuration; and

a second, different threshold is used when NUL has been assigned a beam fault recovery configuration.

In some, but not all examples, the method includes:

Using a first threshold for random access for beam fault recovery configuration; and

otherwise, a second threshold is used for random access.

In some, but not all examples, the method includes: the measurements are modified depending on whether the SUL or NUL has been assigned a beam fault recovery configuration.

In some, but not all examples, the method includes: if a beam fault recovery configuration has been assigned, the currently in-use carrier is preferentially used.

In some, but not all examples, the method includes: if a beam fault recovery configuration has been assigned, the carrier currently in use is used.

In some, but not all examples, selecting carriers for random access is a selection from a subset of candidate sets defined by the telecommunications specification, wherein the subset is more likely to be available for beam fault recovery.

In some, but not all examples, the carrier is an uplink normal carrier or an uplink supplemental carrier, where the supplemental carrier is a borrowed downlink carrier that is less frequent than the uplink normal carrier.

In some, but not all examples, the carrier is assigned a beam fault recovery configuration by assignment of a preamble for contention-free random access.

In some, but not all examples, assignment of a preamble for contention-free random access may only occur on one of the associated uplink normal carrier and uplink supplemental carrier, and assignment of a preamble for contention-free random access may not occur for both the associated uplink normal carrier and uplink supplemental carrier.

In some, but not all examples, the carrier is assigned a beam fault recovery configuration by configuring the carrier to perform beam fault recovery.

In some, but not all examples, configuring the carrier to perform beam fault recovery may only occur on one of the associated uplink normal carrier and uplink supplemental carrier, and configuring the carrier to perform beam fault recovery may not occur for both the associated uplink normal carrier and uplink supplemental carrier.

In some, but not all examples, the method includes:

the BFR config IE is used to configure the carrier to perform beam fault recovery.

detecting a beam fault; and

Recovering from beam failure by:

selecting a carrier for random access; and

the carrier is used for random access,

wherein selecting the carrier is based on whether the carrier has been assigned a beam fault recovery configuration.

In some, but not all examples, the apparatus includes means for:

the carrier is used for random access by performing contention-free random access using the selected carrier.

In some, but not all examples, the apparatus includes means for:

In some, but not all, examples, selecting carriers for random access depends on

(ii) Whether the carrier is sufficient for radio access.

In some, but not all examples, the apparatus includes means for:

it is determined whether the carrier is sufficient for radio access.

In some, but not all examples, the apparatus includes: means for determining whether the carrier is sufficient for radio access depending on whether one or more measurement characteristics of the carrier are sufficient.

In some, but not all examples, the apparatus includes means for: it is determined whether the carrier is sufficient for radio access depending on whether the carrier is in use, and if the carrier is not in use, it is determined whether one or more measurement characteristics of the carrier are sufficient.

In some, but not all examples, the apparatus includes: means for modifying the measured carrier characteristics and/or thresholds used in the comparison depending on which carrier has been assigned a beam fault recovery configuration and which sufficient carriers are preferred for radio access.

In some, but not all examples, the apparatus includes means for: whether the carrier is sufficient or whether the carrier is in use is determined depending on whether the one or more measurement characteristics of the carrier are sufficient for radio access and if the carrier is not in use is determined whether the one or more measurement characteristics of the carrier are sufficient.

In some, but not all examples, the feature is a Reference Signal Received Power (RSRP) for the selected downlink channel, e.g., a downlink pathloss reference.

In some, but not all examples, the threshold is received in a BFR config IE.

In some, but not all examples, the threshold is rsrp_threshold ssb-SUL.

In some, but not all examples, the apparatus includes means for:

In some, but not all examples, the apparatus includes means for modifying the measurements depending on whether the SUL or NUL has been assigned a beam fault recovery configuration.

In some, but not all examples, the apparatus includes: means for prioritizing use of the carrier currently in use if a beam fault recovery configuration has been assigned.

In some, but not all examples, the apparatus includes: means for using the carrier currently in use if a beam fault recovery configuration has been assigned.

In some, but not all examples, the selection of carriers for random access is a selection from a subset of candidate sets defined by the telecommunications specifications, wherein the subset is more likely to be available for beam fault recovery.

In some, but not all examples, the apparatus includes: means for using the BFR config IE to configure a carrier to perform beam fault recovery.

In some, but not all examples, the apparatus includes: means for performing the described methods or means for causing performance of the described methods.

at least one processor; and

at least one memory including computer program code,

detecting a beam fault; and

Recovering from beam failure by;

selecting a carrier for random access; and

the carrier is used for random access,

According to various, but not necessarily all, embodiments there is provided an apparatus comprising: means for selecting a carrier for random access during beam fault recovery, wherein selecting the carrier depends on whether an available carrier has been assigned a beam fault recovery configuration.

According to various, but not necessarily all, embodiments there is provided a network comprising a plurality of network nodes, including the described apparatus.

According to various, but not necessarily all, embodiments there is provided a computer program that, when run on a computer, performs: a carrier is selected for random access during beam fault recovery, wherein the selection of the carrier depends on whether an available carrier has been assigned a beam fault recovery configuration.

According to various, but not necessarily all, embodiments there is provided a data structure comprising data defining a threshold value for comparison with measured carrier characteristics to select carriers that have been assigned a beam fault recovery configuration for random access during recovery from a beam fault.

In some, but not all examples, the data structure is configured to enable: the supplemental uplink is preferably selected over the normal uplink when the supplemental uplink has been assigned a beam fault recovery configuration and the normal uplink has not been assigned a beam fault recovery configuration, and the normal uplink is preferably selected over the supplemental uplink when the normal uplink has been assigned a beam fault recovery configuration and the supplemental uplink has not been assigned a beam fault recovery configuration.

selecting a carrier for random access, wherein selecting a carrier for random access depends on (i) whether the carrier has or has not been assigned a beam fault recovery configuration; and

(ii) Whether the carrier is sufficient for radio access.

In some, but not all examples, the method includes: the carriers that have been assigned a beam fault recovery configuration and are sufficient for radio access are preferentially selected.

In some, but not all examples, the method includes: alternatively, carriers are selected that have not been assigned a beam fault recovery configuration and are sufficient for radio access.

detecting a beam fault; and

recovering from beam failure by:

selecting a carrier for random access; and

random access using carrier

detecting a beam fault; and

recovering from beam failure by:

selecting a carrier for random access; and

the carrier is used for random access,

wherein selecting carriers favors carriers that have been assigned resources for contention-free random access.

detecting a beam fault; and

recovering from beam failure by:

selecting a carrier for random access; and

the carrier is used for random access,

At least one processor; and

at least one memory including computer program code,

detecting a beam fault; and

recovering from beam failure by:

selecting a carrier for random access; and

the carrier is used for random access,

According to various, but not necessarily all, embodiments there is provided a computer program that, when run on a computer, performs: a carrier is selected for random access during beam fault recovery, wherein the selected carrier favors an available carrier that has been assigned resources for contention-free random access.

According to various, but not necessarily all, embodiments there is provided a data structure comprising data defining a threshold value used for comparison with measured carrier characteristics to select carriers that have been assigned resources for contention-free random access for use in random access during recovery from a beam failure.

According to various, but not necessarily all, embodiments, examples are provided as claimed in the appended claims.

Drawings

Some example embodiments will now be described with reference to the accompanying drawings, in which:

FIG. 1 illustrates an example embodiment of the subject matter described herein;

FIG. 2 illustrates another example embodiment of the subject matter described herein;

FIG. 3 illustrates another example embodiment of the subject matter described herein;

FIG. 4 illustrates another example embodiment of the subject matter described herein;

FIG. 5 illustrates another example embodiment of the subject matter described herein;

FIG. 6 illustrates another example embodiment of the subject matter described herein;

FIG. 7 illustrates another example embodiment of the subject matter described herein;

FIG. 8 illustrates another example embodiment of the subject matter described herein;

FIG. 9 illustrates another example embodiment of the subject matter described herein;

FIG. 10 illustrates another example embodiment of the subject matter described herein;

FIG. 11 illustrates another example embodiment of the subject matter described herein;

fig. 12 illustrates another example embodiment of the subject matter described herein.

Detailed Description

Fig. 1 shows an example of a method 10.

At block 12, the method 10 includes selecting a carrier for random access. The choice of carrier for random access depends on:

(i) The carrier has not yet been assigned contention-free random access resources; and

(ii) Whether the carrier is sufficient for radio access.

The method 10 preferentially selects carriers that have been assigned contention-free random access resources and are sufficient for radio access at sub-block 14 and performs contention-free random access using the selected carriers at block 18.

The method 10 alternatively selects a carrier that has not been assigned contention-free random access resources and is sufficient for radio access at sub-block 16, and performs contention-free random access using the selected carrier at block 18.

In some, but not all examples, a carrier is sufficient for radio access if one or more measured characteristics (e.g., path power loss) of the carrier are sufficient for use.

In some, but not all examples, a carrier is sufficient for radio access if it is already in use; and if the carrier is not in use, one or more measured characteristics (e.g., path power loss) of the carrier are sufficient for use.

In some, but not all examples, the method 10 includes determining at block 12 whether a carrier has been assigned contention-free random access resources and determining whether the carrier is sufficient for radio access.

The method 10 may be used to recover from a detected beam failure by performing random access using the selected carrier. The selection of a carrier depends on whether the carrier has been assigned contention-free random access resources. In some examples, selection of carriers favors carriers that have been assigned contention-free random access resources.

Fig. 2 shows an example of a method 20.

The method at block 24 includes: selecting a carrier for random access at block 26; and using the carrier for random access at block 28.

In one example, the method 20 includes initiating random access at block 22 and enabling a random access procedure at block 24.

When a random access procedure is initiated for beam fault recovery, and when a random access procedure is initiated but not initiated for beam fault recovery, block 26 (selecting a carrier for random access) and block 28 (using the selected carrier for random access) are performed in different ways.

Thus, in some examples, the method 20 includes:

at block 26, an uplink carrier for a random access procedure is selected; and

at block 28, the uplink carrier is used for a random access procedure,

In some examples, the first condition compares the measured downlink carrier characteristic to a first threshold when the first threshold is configured.

In some examples, the second condition compares the measured downlink carrier characteristic to a second threshold different from the first threshold.

In some examples, when the first threshold is not configured, the first condition compares the measured downlink carrier characteristic to a threshold (e.g., a second threshold) different from the first threshold.

Thus, when a random access procedure is initiated for beam fault recovery, the selection of the uplink carrier is based on a comparison of the measured downlink carrier characteristics with a first threshold, and when a random access procedure is initiated but not initiated for beam fault recovery, the selection of the uplink carrier is dependent on a comparison of the measured downlink carrier characteristics with a different second threshold.

In another example, the method 20 includes: detecting a beam fault at block 22; and recovering from beam failure at block 24.

Recovery from beam failure is achieved by:

at subframe 26, a carrier for random access is selected; and

at sub-block 28, the carrier is used for random access.

In some examples, selecting the carrier depends on whether the carrier has been assigned resources for contention-free random access. For example, selecting a carrier may favor a carrier that has been assigned resources for contention-free random access.

In some examples, selecting the carrier is based on whether the carrier is configured to perform beam fault recovery. For example, selecting a carrier may favor a carrier configured to perform beam fault recovery or a carrier having a configured threshold.

The carrier configured to perform beam fault recovery may have prioritized random access because, for example, it has been assigned resources for contention-free random access, or because it has a different faster power ramping (power ramping).

In some examples, selecting a carrier depends on whether the carrier is configured to perform both beam fault recovery and resources that have been assigned for contention-free random access.

In some, but not all examples, subframe 26 includes a preference for carriers that have been assigned a beam fault recovery configuration and are sufficient for radio access; and sub-block 28 includes using the carrier for random access by performing contention-free random access using the selected carrier, or alternatively, selecting, at sub-block 26, a carrier that has not been assigned a beam fault recovery configuration and is sufficient for radio access; and then at sub-block 28, the carrier is used for random access by performing contention-based random access using the selected carrier.

In some, but not all examples, block 26 includes: determining whether a carrier has or has not been assigned a beam fault recovery configuration; and determining whether the carrier is sufficient for radio access.

In some, but not all, examples, selecting carriers for random access depends on

(ii) Whether the carrier is sufficient for radio access.

In some, but not all examples, if a carrier has been used by the user equipment, the carrier is sufficient for radio access; or if the carrier is not in use, one or more measured characteristics of the carrier (e.g., path power loss) are sufficient for use. Fig. 3 shows an example of a method 30 for selecting carriers that may be used, for example, in block 12 of method 10 or block 24 of method 30.

The method 30 of selecting carriers includes comparing the measured downlink carrier characteristics 31 with a threshold 33 at block 32.

In some, but not all examples, the method 30 includes modifying the measured carrier characteristic(s) 31 used in the comparison 32 at block 34. For example, the modification may depend on which carrier has been assigned a beam fault recovery configuration; and which of the sufficient carriers are preferred for radio access.

Additionally or alternatively, the method 30 includes modifying the threshold 33 used in the comparison 32 at block 36. The modification may depend on whether the random access procedure is initiated by beam fault recovery (using a first threshold) or whether the random access procedure is initiated by other means than beam fault recovery (using a different threshold, e.g. a second threshold). When the random access procedure is initiated by beam fault recovery, then the threshold may depend on the beam fault recovery configuration. For example, if a beam fault recovery configuration has occurred and a first threshold has been configured, a first threshold may be used, and if a beam fault recovery configuration has not occurred and a first threshold has not been configured, a second threshold may be used.

The comparison may be used to favor the selection of one sufficient carrier over another carrier via a threshold.

In some, but not all examples, if one or more measured characteristics (e.g., path power loss) of a carrier are sufficient for use, then the carrier is determined to be sufficient for radio access.

In some, but not all examples, a carrier is determined to be sufficient for radio access if the carrier is already in use; and if the carrier is not in use, determining that one or more measured characteristics (e.g., path power loss) of the carrier are sufficient for use.

In some, but not all examples, the one or more measured characteristics depend on received signal power and/or received signal quality.

In some, but not all examples, the measurement characteristic is a Reference Signal Received Power (RSRP) for the selected downlink channel, such as a downlink pathloss reference.

In some, but not all examples, the threshold used in the comparison is received from the network, e.g., via a BFR config IE. For example, the threshold may be or depend on RSRP_Threshold SSB-SUL.

In some, but not all examples, the threshold used in the comparison is used to select between a normal uplink carrier (NUL) and a supplemental uplink carrier (SUL), where the supplemental carrier is a borrowed downlink carrier that is lower in frequency than the uplink normal carrier.

The method may select any of the normal uplink carriers and supplemental uplink carriers that have been assigned a beam fault recovery configuration and are available. This favors CFRA, which is faster than CBRA and avoids wasting available and usable contention-free resources.

In some, but not all examples, when beam fault recovery is performed using a random access procedure, the modification block 36 includes:

applying a first offset to a threshold used in the comparison when the SUL has been assigned a beam fault recovery configuration; and when the NUL has been assigned a beam fault recovery configuration, applying a second offset to the threshold used in the comparison, wherein one of the first offset and the second offset is positive and the other is negative.

In some, but not all examples, when beam fault recovery is performed using a random access procedure, method 30 includes: when the SUL has been assigned a beam fault recovery configuration, a first threshold is used in comparison 32; and a different second threshold is used in comparison 32 when NUL has been assigned a beam fault recovery configuration.

In some, but not all examples, when beam fault recovery is performed using a random access procedure, method 30 includes:

The measurements 31 used in the comparison 32 have been modified 34 depending on whether the SUL or NUL has been assigned a beam fault recovery configuration.

In some, but not all examples, when beam fault recovery is performed using a random access procedure, the method includes: if a beam fault recovery configuration is assigned, the currently in-use carrier is preferentially used.

In some, but not all examples, when beam fault recovery is performed using a random access procedure, the method includes: if a beam fault recovery configuration is assigned, the carrier currently in use is used.

In some, but not all examples, when beam fault recovery is performed using a random access procedure, selecting carriers for random access is a selection from a subset of a set of candidates defined by a telecommunications specification, wherein candidates of the subset are more likely to be available for beam fault recovery.

In some, but not all examples, when beam fault recovery is performed using a random access procedure, the carrier is assigned a beam fault recovery configuration by assignment of a dedicated preamble for contention-free random access. The assignment of the preamble for contention-free random access may only occur on one of the associated uplink normal carrier and uplink supplemental carrier, and the assignment of the preamble for contention-free random access cannot occur for both the associated uplink normal carrier and uplink supplemental carrier.

In some, but not all examples, when beam fault recovery is performed using a random access procedure, the carrier is assigned a beam fault recovery configuration by configuring the carrier to perform beam fault recovery. Configuring the carrier to perform beam fault recovery may only occur on one of the associated uplink normal carrier and uplink supplemental carrier, and configuring the carrier to perform beam fault recovery may not occur for both the associated uplink normal carrier and uplink supplemental carrier. In some, but not all examples, configuring the carrier to perform beam fault recovery uses a BFR config IE.

The above-described method may be performed by apparatus 200 (e.g., an apparatus configured as a mobile device or as a user equipment).

The apparatus 200 may operate as part of a network 100, the network 100 comprising a plurality of network nodes 110, the network 100 comprising the apparatus 200.

The above-described method may be enabled by a computer program which, when run on a computer, performs:

selecting an uplink carrier for a random access procedure; and

the uplink carrier is used for a random access procedure,

The above-described method may be enabled by a computer program which, when run on a computer, performs: a carrier for random access during beam fault recovery (random access procedure initiated for beam fault recovery) is selected, wherein the selection carrier favors an available carrier to which contention-free random access resources have been assigned.

The above-described method may be enabled by a computer program which, when run on a computer, performs: a carrier is selected for random access during beam fault recovery (a random access procedure initiated for beam fault recovery), wherein the selection of a carrier depends on whether an available carrier has been assigned a beam fault recovery configuration. In some examples, selecting a carrier favors an available carrier that has been assigned a beam failure recovery configuration, such as resources for contention-free random access.

The above method may be enabled by a data structure defining a threshold parameter that is exclusively used to distinguish between a comparison of a measured downlink carrier characteristic with a first threshold when a random access procedure is initiated for beam fault recovery and a comparison of a measured downlink carrier characteristic with a different second threshold when a random access procedure is initiated but not initiated for beam fault recovery.

The above method may be enabled by a data structure defining a threshold parameter that is exclusively used to distinguish between a comparison of a measured downlink carrier characteristic with a first threshold when a random access procedure is initiated for beam fault recovery and the first threshold is configured, and a comparison of a measured downlink carrier characteristic with a different threshold when a random access procedure is initiated for beam fault recovery and the first threshold is not configured.

Fig. 4 shows an example of a network 100, the network 100 comprising a plurality of network nodes including a terminal node 110, an access node 120 and one or more core nodes 130. Terminal node 110 and access node 120 communicate with each other. One or more core nodes 130 communicate with access node 120.

In some examples, one or more core nodes 130 may communicate with each other. In some examples, one or more access nodes 120 may communicate with each other.

Network 100 may be a cellular network including a plurality of cells 122, each cell 122 being served by an access node 120. In this example, the interface between the terminal node 110 and the access node 120 defining the cell 122 is a wireless interface 124. The access node 120 is a cellular radio transceiver. End node 110 is a cellular radio transceiver.

In the illustrated example, the cellular network 100 is a third generation partnership project (3 GPP) network, wherein the terminal node 110 is a User Equipment (UE) and the access node 120 is a base station.

In the particular example shown, the network 100 is an evolved universal terrestrial radio access network (E-UTRAN). The E-UTRAN includes an E-UTRAN NodeB (eNB) 120, and the E-UTRAN NodeB (eNB) 120 provides the UE 110 with E-UTRA user plane and control plane (RRC) protocol terminations. The enbs 120 are interconnected to each other by an X2 interface 126. The eNB is also connected to a Mobility Management Entity (MME) 130 through an S1 interface 128.

3GPP examples

Definition of the definition

Bandwidth: the difference between the limiting frequencies of the successive bands.

And (3) a base station: the base station is an access node. It may be a network element in a radio access network that is responsible for radio transmission to and/or radio reception from user equipment in one or more cells.

Beam: the beam (of the antenna) is the main lobe of the radiation pattern of the antenna array.

BFR: beam fault recovery. Beam recovery in case the UE loses the current serving beam.

BFR config：BeamFailureRecoveryConfig IE。

BFR resource: resources dedicated to BFR, such as BFR specific thresholds or contention-free random access resources/preambles. BFR configuration may configure such resources.

BWP: bandwidth portion. A subset of the total cell bandwidth of the cell.

BWP IE: bandwidth part information element. This is used to configure the bandwidth part.

Carrier wave: modulating waveforms, e.g. conveying physical channels

CBRA: contention-based random access

Cell: a "cell" is a geographical area into which the radio coverage of a single base station extends.

CFRA: contention-free random access

CFRA resource: resources assigned for CFRA, such as random access preambles or occasions

CSI-RS: channel state information reference signal

DL: downlink link

FDD: frequency division duplexing. A duplexing technique in which traffic for a bi-directional telecommunications link in each direction is carried on two different carrier frequencies, each carrier frequency being dedicated to traffic in one direction.

gNB：gNodeB、NR NodeB

IE: information element. A data structure containing a single or multiple fields.

MAC: media access control

MAC entity: logical entities that perform MAC.

ME: the mobile device may be, for example, a cell phone.

Network element: discrete telecommunication entities, e.g. devices or systems, which can be managed through specific interfaces

Node B: a logical node responsible for radio transmission/reception to/from a UE in one or more cells. References to Node bs also include references to physical entities or entities hosting logical nodes, such as base stations.

NR: new radio (3 GPP name for 5G technology)

NUL: generic uplink (which may also be referred to as uplink)

PCell: a primary cell. A cell operating on the primary frequency, wherein the UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure, or is a cell indicated as the primary cell in a handover procedure.

Physical channel: a carrier wave modulated with or to be modulated with the information bits of the burst. The physical channels use a combination of frequency division multiplexing and time division multiplexing and are defined in terms of a sequence of radio frequency channels and a sequence of time slots. In FDD mode, the physical channel is defined by the code, frequency and relative phase (I/Q) in the uplink. In TDD mode, the physical channel is defined by code, frequency and time slot

PUCCH: physical uplink control channel

PUSCH: physical uplink shared channel

RACH: random access channel

A radio access network: a telecommunications network in which access to the network (connection between user equipment and the network) is achieved over an air interface.

Random access: several transmitters may access the medium access method of the same part of the resource concurrently. It provides the function of receiving services from any point in its time axis.

Random access resource: resources such as random access preambles and occasions assigned to random access.

RRC: and radio resource control. A set of control functions responsible for handling radio resources.

RSRP: reference signal received power.

SIM: a subscriber identity module. Also referred to as USIM.

SSB: synchronous signal block

Subcarrier: one of a number of closely spaced or overlapping orthogonal narrowband data signals within an OFDM channel.

SUL: the uplink is supplemented.

TDD: time division duplexing. A duplexing technique in which traffic in each direction on a bi-directional telecommunications link is carried on a single carrier radio frequency in discrete time intervals, each discrete time interval being dedicated to traffic in one direction.

UE: the reference to the UE may refer to a valid combination of ME and SIM, or to ME with or without battery and with or without SIM.

UL: an uplink.

The following examples relate to beam fault recovery processing when both NUL and SUL have been configured for a UE for cells in an NR system.

Supplemental Uplink (SUL)

Supplemental Uplink (SUL) is introduced in NR to improve UL coverage for high frequency scenarios. It provides uplink coverage extension.

For each serving cell, the network configuration includes at least an initial bandwidth portion including at least a downlink bandwidth portion and one uplink bandwidth portion (if the serving cell is configured with an uplink) or two uplink bandwidth portions (if a Supplementary Uplink (SUL) is used). With the SUL, for example, 2 UL carriers are configured for the UE for one DL carrier of the same cell, as shown in fig. 5.

Uplink transmissions on both UL are controlled by the network to avoid overlapping PUSCH/PUCCH transmissions in time. Overlapping transmissions on PUSCH are avoided by scheduling, while overlapping transmissions on PUCCH (PUCCH is configured for only one of the two UL of the cell) are avoided by configuration. In addition, initial access is supported in each uplink.

Currently, NR operating bands for SUL include:

beam Fault Recovery (BFR)

Network-controlled mobility is applicable to UEs in rrc_connected and is classified into two types of mobility: cell level mobility and beam level mobility.

Cell level mobility requirements trigger explicit RRC signaling, i.e. handover. RRC signaling includes signaling between source gNB and target gNB, source gNB and UE (handover command), and UE and target gNB (handover complete).

Beam level mobility does not require explicit RRC signaling to be triggered. The gNB provides measurement configuration to the UE via RRC signaling. Beam level mobility is then handled at the lower layers through physical layer and MAC layer control signaling and the RRC is not required to know which beam is being used at a given point in time.

Beam Fault Recovery (BFR) is introduced in NR to provide fast UE-based beam recovery in the event of current serving beam loss.

For beam fault detection, when the number of beam fault instance indications from the physical layer reaches a configured threshold within a configured time period, the gNB configures a beam fault detection reference signal for the UE and the UE declares a beam fault.

After the beam failure is detected, the UE: beam failure recovery is triggered by initiating a random access procedure on the PCell and selecting the appropriate beam to perform beam failure recovery. After the random access procedure is completed, beam fault recovery is considered to be complete.

The random access procedure takes two different forms: contention-based random access (CBRA) shown in fig. 6 and contention-free random access (CFRA) shown in fig. 7. The normal DL/UL transmission may be performed after the random access procedure. CFRA is a two-step process that is faster than CBRA (four steps and step) and has a potential collision risk.

Bandwidth portion (BWP)

A bandwidth part (BWP) concept is introduced in the NR to provide system flexibility and enhanced UE power saving possibilities by being able to dynamically adapt to the UE operating channel bandwidth.

With Bandwidth Adaptation (BA), the reception and transmission bandwidths of the UE do not have to be as large as the bandwidths of the cells, and can be adjusted: a change in width may be commanded (e.g., to shrink during periods of low activity to save power); the location may be moved in the frequency domain (e.g., to increase scheduling flexibility); and may command a change in subcarrier spacing (e.g., to allow for different services). A subset of the total cell bandwidth of the cell is referred to as bandwidth part (BWP), and BA is implemented by configuring the BWP(s) to the UE and telling the UE which configured BWP is currently active BWP. BWP is defined by a width (e.g., 10, 20, 40MHz, … …) and a subcarrier spacing (e.g., 15, 60kHz, … …).

BWP Information Element (IE)

BWP IE for configuring bandwidth part

For each serving cell, the network configuration includes at least an initial bandwidth portion that includes at least a downlink bandwidth portion and one (if the serving cell is configured with an uplink) or two (if a Supplementary Uplink (SUL) is used) uplink bandwidth portions. Furthermore, the network may configure additional uplink and downlink bandwidth portions for the serving cell.

The locationandband field of the BWP IE defines the frequency domain location and bandwidth of the bandwidth part.

The subsearrierspace field of the BWP IE defines the subcarrier spacing to be used for all channels and reference signals in the BWP, unless explicitly configured elsewhere. For example, the values may be 15, 30 or 60kHz (< 6 GHz) and 60 or 120kHz (> 6 GHz).

The rach-ConfigCommon field of the BWP IE defines the configuration of cell-specific random access resources (parameters) used by the UE in the BWP for contention-based and contention-free random access and contention-based beam-fault recovery. The random access resource may comprise a CFRA resource, e.g. a CFRA (contention free random access) preamble. CFRA (contention free random access) preambles of BFRs can only be configured on UL or SUL carriers.

The beamFailureRecoveryConfig field (BFR config) of the BWP IE defines how the UE performs beam fault recovery after detecting a beam fault. If there is a Supplementaryuplink, this field is only present (configured) in one of the uplink carriers (UL or SUL).

When BFR is performed on a carrier without BFR config, the UE can only use CBRA (contention-based random access).

BeamFailureRecoveryConfig IE

BeamFailureRecoveryConfig IE is used to configure RACH resources and candidate beams for the UE to recover from beam failure in case of beam failure detection.

The rach-configcfr field defines the configuration of contention-free random access opportunities for BFRs.

The rsrp-threshold ssb field defines a threshold for determining whether the UE can attempt contention-free random access using the candidate beam to recover from the beam failure. This is a threshold for beam fault recovery;

the candidatebeam rslist field defines a reference signal list that identifies candidate beams and associated RA parameters for recovery.

The ra-priority field defines parameters of a prioritized random access procedure applicable to BFR.

rsrp-ThresholdSSB-SUL: an RSRP threshold for selecting between NUL carriers and SUL carriers;

random access procedure initialization

According to section 9.2.6 of TS 38.300, initiating a random access procedure is initiated due to any of a number of different events, such as:

-initial access from rrc_idle;

-RRC connection re-establishment procedure;

-a handover;

-DL or UL data arrives during rrc_connected when the UL synchronization status is "unsynchronized";

-a transition from rrc_inactive;

-establishing a time alignment at SCell addition;

-requests for other SIs (see section 7.3);

beam Fault Recovery (BFR).

BFR uses a random access procedure for beam fault recovery. The best carrier needs to be selected for this random access procedure. In the following example, this is achieved, for example, by comparing the RSRP of the downlink path loss reference to a threshold to select either SUL or NUL.

Example implementation

When beam fault recovery is triggered after beam fault detection, it depends on which carrier (NUL or SUL) the BFR config is configured for.

Additional selection logic/prioritization is applied to UL carrier selection based on which carrier (NUL or SUL) BFR config is configured for. This may be achieved by either:

1. configuring the offset parameter as a path loss reference or as a configured RSRP threshold to prioritize the carrier for which the BFR config (beamFailureRecoveryConfig IE) is configured;

2. Configuring separate RSRP thresholds for beam fault recovery situations to prioritize carriers for which BFR config (beamFailureRecoveryConfig IE) is configured;

application prioritization may be conditional and subject to:

being able to use CFRA resources (i.e. available configured candidate beams with CFRA resources);

-have BFR config on UL BWP currently active on SUL or NUL.

Thus, an example implementation is an example of the method, the method comprising:

detecting a beam fault; and

recovering from beam failure by:

selecting a carrier for random access; and

the carrier is used for random access,

wherein selecting the carrier is performed according to whether the carrier is configured to perform beam fault recovery and/or whether the carrier has been assigned a beam fault recovery configuration. In some examples, selecting carriers favors carriers configured to perform beam fault recovery and/or carriers to which beam fault recovery configurations have been assigned.

In some, but not all examples, the offset parameter is a new field in beamFailureRecoveryConfig IE.

In some, but not all examples, the separate RSRP threshold is a new field in beamFailureRecoveryConfig IE.

Thus, the new beamFailureRecoveryConfig IE is a data structure comprising data defining a threshold value for comparison with measured carrier characteristics to select carriers that have been assigned a beam fault recovery configuration for random access during recovery from a beam fault. The new data structure enables: the supplemental uplink is preferably selected over the normal uplink when the supplemental uplink has been assigned a beam fault recovery configuration and the normal uplink has not been assigned a beam fault recovery configuration, and the normal uplink is preferably selected over the supplemental uplink when the normal uplink has been assigned a beam fault recovery configuration and the supplemental uplink has not been assigned a beam fault recovery configuration.

A method, comprising:

(ii) Whether the carrier is sufficient for radio access.

1.Realization of offset_bfr (offset zero, negative or positive)

Referring to fig. 8, method 60 includes determining whether the UE has triggered a BFR and determining whether BFR config is configured on a SUL carrier or a NUL carrier at block 62. The method 60 includes prioritizing carriers that have been configured with beamFailureRecoveryConfig in carrier selection at block 64, either by an offset value or by application of a dedicated RSRP threshold, based on the determination at block 62.

Referring to the example method 70 shown in fig. 9, in this example, if the UE has triggered a BFR (block 71) and determines that BFR config is to be configured on the SUL carrier (blocks 72, 73), then:

at the point of the block 74A,

if (the RSRP of the downlink pathloss reference is less than RSRP-threshold ssb-SUL + offset bfr),

the UE should use the SUL to perform a random access procedure for beam recovery (block 75A).

Otherwise

The UE should use NUL to perform a random access procedure for beam recovery (block 76A).

offset_bfr is positive. offset_bfr may be a new field in BFR config.

This is beneficial because using offset values allows the network to configure the priorities of the SUL carriers with BFR config for beam recovery. For higher offset values, the UE is more likely to select the SUL with BFR config.

If the UE has triggered a BFR (block 71) and the BFR config is determined to be configured on the SUL carrier (blocks 72, 73), then:

if the UE has triggered a BFR (block 71) and the BFR config is determined to be configured on a NUL carrier (blocks 72, 73), then:

at the point of the block 74B,

if (the RSRP of the downlink pathloss reference is less than RSRP-threshold ssb-SUL + offset _ bf),

the UE should use the SUL to perform a random access procedure for beam recovery (block 75B)

Otherwise

The UE should use NUL to perform a random access procedure for beam recovery (block 76B).

offset_bfr is negative. offset_bfr may be a new field in BFR config.

This is beneficial because using a negative offset value allows the network to configure the priority of NUL carriers with BFR config for beam recovery. For higher negative offset values, the UE is more likely to select NUL with BFR config.

In another implementation example, the offset may be included in a new SUL/NUL selection RSRP threshold (e.g., rsrp_Threshold SSB-SUL_bfr.) as a field in BFR config. When BFR is configured for SUL, there may be a new threshold, and when BFR is configured for NUL, there may be a different new threshold. When the UE is configured with BFR config, the network may configure the UE to apply different thresholds rsrp_threshold ssb-sul_bfr when running the selection logic of SUL/NUL.

Thus, the condition "if (RSRP of the downlink pathloss reference is less than RSRP-threshold ssb-sul+offset_bfr)" in method 70 becomes "if (RSRP of the downlink pathloss reference is less than RSRP-threshold ssb-sul_bfr)".

2.Prioritized implementation of active ULBWP

Referring to fig. 10, method 80 includes determining whether the UE has triggered a BFR and determining whether BFR config is configured on a SUL carrier or a NUL carrier at block 82.

Method 60 includes determining at block 84 whether BFR config is configured on the currently active BWP of the SUL carrier or the NUL carrier:

the method 60 includes prioritizing carriers that have been configured with beamFailureRecoveryConfig in carrier selection at block 64, either by an offset value or by application of a dedicated RSRP threshold, based on the determination at blocks 82, 84.

If the UE has triggered BFR and BFR config is on the currently active BWP of the NUL carrier:

if (RSRP + offset _ bfr of the downlink pathloss reference is less than RSRP-threshold ssb-SUL),

the UE should use the SUL to perform a random access procedure for beam recovery.

Otherwise

The UE should perform a random access procedure for beam restoration using the current active BWP.

offset_bfr is positive. offset_bfr may be a new field in BFR config.

In one example, if the UE has triggered a BFR and BFR config is not on the currently active BWP, the configured offset value is not applied, but only rsrp-threshold ssb-SUL is used.

In an alternative example, when a random access procedure is triggered due to beam failure recovery, a specific rsrp_threshold for selecting the SUL is used: rsrp_Threshold SSB-SUL_bfr. This may be a new field in BFR config.

3.Implementation of prioritizing active uplink carriers

In one example:

if the UE has triggered a BFR and BFR config is on the currently active UL carrier:

the UE should perform a random access procedure for beam restoration using the currently active uplink carrier.

Otherwise

If ((BFR config on inactive UL carrier) and (RSRP of downlink pathloss reference is less than RSRP-ThresholdSSB-SUL+offset_bfr)):

the UE should use the SUL for BFR.

Otherwise:

the UE should use NUL for BFR.

In general

In the foregoing example, if the offset parameter (offset_bfr) is not provided to the UE by a higher layer configuration (e.g., BFR IE), it should use a default offset value of XdB (defined in the specification). By way of example, X may be, for example, M … -6, -3, 0, 3, 6 … NdB.

In another example, the offset_bfr parameter may be an agreed upon constant value (e.g., 3 dB) defined in the specification.

In another example, the invention is not limited to SSB-based thresholds (rsrp_threshold SSB-SUL) and may operate in a similar manner as rsrp_threshold csirs-SUL, where the CSI-RS signal is used to estimate the path loss.

In one example, the offset_bfr or rsrp_threshold ssb-sul_bfr may be configurable by the network through RRC signaling or via broadcast signaling. In another example, these parameters are configured in BFR config.

Additional examples

These and other examples disclose a method comprising:

detecting a beam fault; and

recovering from beam failure by

Selecting a carrier for random access; and

the carrier is used for random access,

wherein the selection of carriers is made based on a comparison between the measured carrier characteristics and a first threshold value (when configured for beam fault recovery) and a second, different threshold value (when not configured for beam fault recovery).

In at least some examples, "configured for beam fault recovery" means that the BW threshold parameter has been configured to the UE by the NW, i.e., the network may have the option to configure it and not configure it.

When configured, a first threshold value is used that is determined at least in part by the BFR threshold parameter. When it is not configured, a second threshold is used.

It does not matter in which IE the BFR threshold parameter is provided to the UE, but it is e.g. part of the NUL or SUL configuration. The UE knows whether it is configured or not, but does not need to consider in which IE the BFR parameters are configured.

In some examples, the measured carrier characteristic depends on the received signal power and/or the received signal quality. In the following example, the measured carrier characteristic is a Reference Signal Received Power (RSRP) for the selected downlink channel, e.g., a downlink pathloss reference.

The first and second thresholds are used to select between a normal uplink carrier (NUL) and a supplementary uplink carrier (SUL). Thus, the selected carrier is an uplink normal carrier or an uplink supplemental carrier, where the supplemental carrier is a borrowed downlink carrier that is lower in frequency than the uplink normal carrier.

More examples

In the following example:

process 1 differs from process 2. It uses different conditions.

In procedure 1, condition 1 is used to control the selection between the use of SUL or NUL for random access.

In procedure 2, condition 2 is used to control the selection between the use of SUL or NUL for random access.

If it is determined at 2> that the "random access procedure is initiated for beam fault recovery" is true, then an example of procedure 1 performed is:

if it is determined at 2> that the "random access procedure is initiated for beam failure recovery" is false (because random access has been initiated but not used for beam failure recovery), then an example of step 2 performed is:

Thus, the method comprises:

selecting an uplink carrier for a random access procedure; and

the uplink carrier is used for a random access procedure,

Condition 1 and condition 2 are different. Different thresholds are used for condition 1 and condition 2.

Both condition 1 and condition 2 depend on the comparison of the measured downlink carrier characteristics to a threshold. However, different thresholds are used.

Thus, the method comprises:

selecting an uplink carrier for a random access procedure; and

the uplink carrier is used for a random access procedure,

In the following example, [ condition 1] uses at least a comparison of the measured carrier characteristic with a first threshold value.

In the following example, [ condition 2] uses a comparison of the measured carrier characteristic with a second threshold (different from the first threshold). In the following example, [ condition 2] does not use a comparison of the measured carrier characteristic with the first threshold value.

The threshold and/or the difference between the thresholds may be controlled by one or more information elements. Thus, in some examples, the configuration for beam fault recovery at least partially determines a threshold parameter of the first threshold. The threshold parameter may be provided in an information element.

Thus, the data structure may include data defining threshold parameters that are specifically used to distinguish between: a comparison of the measured downlink carrier characteristics with a first threshold when a random access procedure is initiated for beam fault recovery and a comparison of the measured downlink carrier characteristics with a second, different threshold when a random access procedure is initiated but not initiated for beam fault recovery.

Thus, the whole process is:

condition 1

In the following example, [ condition 1] uses at least a comparison of the measured downlink carrier characteristic with a first threshold.

In these but not all examples, condition 1 is satisfied by either satisfying sub-condition 1 or satisfying sub-condition 2.

Sub-condition 1 is based on a comparison of the measured carrier characteristic with a first threshold. Sub-condition 1 requires that there is already a configuration for beam fault recovery. Thus, sub-condition 1 requires that there already be a configuration for beam fault recovery and that the carrier is sufficient for use based at least on a comparison with the first threshold.

Alternative sub-condition 2 is based on a comparison of the measured carrier characteristics with a different threshold value (in these examples, the second threshold value). Sub-condition 2 requires no configuration for beam fault recovery. Thus, sub-condition 2 requires that there is no configuration for beam fault recovery and that the carrier is sufficient for use based at least on a comparison with a threshold (e.g., a second threshold) different from the first threshold.

Based at least on a comparison of the measured same carrier characteristics with different thresholds, different requirements are placed on the sufficiency of the carrier for use.

In the following example, the threshold parameter is an offset from a second threshold value, which is added to the second threshold value to create the first threshold value. Condition 1 =

3> if the offset-BFR is configured and the RSRP of the downlink pathloss reference is less than the RSRP-threshold ssb-sul+offset-BFR; or alternatively

3> if the offset-BFR is not configured and the RSRP of the downlink pathloss reference is less than the RSRP-threshold ssb-SUL:

thus, when the threshold parameter is not configured, the offset is assumed to be zero.

In the following example, the threshold parameter defines the first threshold value independently of the second threshold value.

Condition 1 =

3> if RSRP-threshold ssb-SUL-bfr is configured and the RSRP of the downlink path loss reference is less than RSRP-threshold ssb-SUL-bfr; or alternatively

3> if RSRP-threshold ssb-SUL-bfr is not configured and the RSRP of the downlink path loss reference is less than RSRP-threshold ssb-SUL:

in the following example, when configured for beam fault recovery, the selection of the carrier is dependent on a comparison of the measured downlink carrier characteristics to a first threshold and additional conditions. The additional condition depends on the availability of contention-free random access resources.

Condition 1 =

If the offset-BFR is configured and the RSRP of the downlink pathloss reference is less than the RSRP-threshold SSB-sul+offset-BFR, and if contention-free random access resources for beam-failure recovery associated with any SSB and/or CSI-RS have been explicitly provided by RRC; or alternatively

In the following example, when configured for beam fault recovery, the selection of the carrier is dependent on a comparison of the measured downlink carrier characteristics to a first threshold and additional conditions. The additional condition depends on the availability of beam fault recovery resources for the currently active bandwidth portion.

Condition 1 =

If offset-BFR is configured and the RSRP of the downlink pathloss reference is less than RSRP-threshold ssb-sul+offset-BFR, if beamFailureRecoveryConfig is available in the currently active UL BWP; or alternatively

condition 2

When not configured for beam fault recovery, [ condition 2] depends on a comparison of the measured downlink carrier characteristics to a second threshold different from the first threshold.

Condition 2 =

Otherwise if the RSRP of the downlink pathloss reference is less than RSRP-threshold ssb-SUL:

in this example, the comparison in sub-condition 2 of condition 1 (RSRP for the downlink pathloss reference is less than RSRP-threshold ssb-SUL) is the same as the comparison in condition 2 (RSRP for the downlink pathloss reference is less than RSRP-threshold ssb-SUL), but the routes to the same comparison are different.

From the foregoing, it should be appreciated that condition 1 compares the measured downlink carrier characteristics to the first threshold in sub-condition 1 when the first threshold is configured. The first threshold may be configured during a beam fault recovery configuration.

In the foregoing example, when the first threshold is not configured, condition 1 compares the measured downlink carrier characteristic with a threshold (e.g., a second threshold) different from the first threshold in sub-condition 2. The comparison depends on a first threshold. The comparison compares only the measured downlink carrier characteristics with a second threshold,

in the foregoing example, condition 2 compares the measured downlink carrier characteristic to a second threshold value different from the first threshold value. The comparison is independent of the first threshold. The comparison compares only the measured downlink carrier characteristics with a second threshold,

it should be appreciated from the foregoing that the network may control BFR through assignment of threshold parameters.

The network comprises an apparatus comprising means for performing a method comprising:

determining which carrier is configured for beam fault recovery; and

The network may cause a preference for carriers that have been assigned a beam fault recovery configuration and an alternative selection for carriers that have not been assigned a beam fault recovery configuration.

The network may cause the measured carrier characteristics and/or thresholds used in the comparison to select a carrier to be modified depending on which carrier has been assigned the beam fault recovery configuration.

A threshold value for selecting between a normal uplink carrier (NUL) and a supplementary uplink carrier (SUL), the method comprising:

(i) Causing the first offset to be applied to the threshold when the SUL has been assigned a beam fault recovery configuration; and causing a second offset to be applied to the threshold when the NUL has been assigned a beam fault recovery configuration, wherein one of the first offset and the second offset is positive and the other is negative, or

(ii) Causing use of a first threshold when the SUL has been assigned a beam fault recovery configuration; and when NUL has been assigned a beam fault recovery configuration, causing a different second threshold to be used.

The method may additionally cause the measured carrier characteristics used in the comparison to be modified for the selected carrier depending on whether the SUL or NUL has been assigned a beam fault recovery configuration.

As previously described, assignment of a preamble for contention-free random access may only occur on one of the associated uplink normal carrier and uplink supplemental carrier, and assignment of a preamble for contention-free random access may not occur for both the associated uplink normal carrier and uplink supplemental carrier.

Fig. 11 shows an example of the controller 50 of the apparatus 200. The controller 50 may be implemented as controller circuitry. The controller 50 may be implemented solely in hardware, some aspects employing solely software including firmware, or may be a combination of hardware and software (including firmware).

As shown in fig. 11, the controller 50 may be implemented using hardware-function-enabled instructions, for example, by using executable instructions of a computer program 56 in a general-purpose or special-purpose processor 52, which computer program 56 may be stored in a computer-readable storage medium (disk, memory, etc.) for execution by such processor 52.

The processor 52 is configured to read from the memory 54 and write to the memory 54. The processor 52 may further include: an output interface via which the processor 52 outputs data and/or commands; and an input interface via which data and/or commands are input to the processor 52.

The memory 54 stores a computer program 56, the computer program 56 comprising computer program instructions (computer program code) that, when loaded into the processor 52, control the operation of the apparatus 200. The computer program instructions of the computer program 56 provide the logic and routines that enables the apparatus to perform the methods illustrated in fig. 1-3 and 8-10. The processor 52 is capable of loading and executing a computer program 56 by reading the memory 54.

Accordingly, the apparatus 200 comprises:

at least one processor 52; and

at least one memory 54, including computer program code,

the at least one memory 54 and the computer program code are configured to, with the at least one processor 52, cause the apparatus 200 at least to perform:

detecting a beam fault; and

recovering from beam failure by:

selecting a carrier for random access; and

the carrier is used for random access,

In some examples, selecting a carrier favors a carrier that has been assigned a beam fault recovery configuration.

As shown in fig. 12, the computer program 56 may arrive at the apparatus 200 via any suitable delivery mechanism 60. The delivery mechanism 60 may be, for example, a machine-readable medium, a computer-readable medium, a non-transitory computer-readable storage medium, a computer program product, a memory device, a recording medium such as a compact disc read only memory (CD-ROM) or a Digital Versatile Disc (DVD) or a solid state memory, an article of manufacture that includes or tangibly embodies the computer program 56. The delivery mechanism may be a signal configured to reliably transfer the computer program 56. The apparatus 200 may propagate or transmit the computer program 56 as a computer data signal.

Computer program instructions for causing an apparatus to perform at least the following or for performing at least the following: a carrier is selected for random access during beam fault recovery, wherein the selection of the carrier depends on whether an available carrier has been assigned a beam fault recovery configuration.

In some examples, selecting a carrier favors an available carrier that has been assigned a beam fault recovery configuration.

The computer program instructions may be embodied in a computer program, a non-transitory computer readable medium, a computer program product, a machine readable medium. In some, but not all examples, computer program instructions may be distributed over more than one computer program.

Although the memory 54 is shown as a single component/circuitry, it may be implemented as one or more separate components/circuitry, some or all of which may be integrated/removable and/or may provide permanent/semi-permanent/dynamic/cached storage.

Although processor 52 is shown as a single component/circuitry, it may be implemented as one or more separate components/circuitry, some or all of which may be integrated/removable. Processor 52 may be a single-core or multi-core processor.

References to "computer-readable storage medium", "computer program product", "tangibly embodied computer program", etc., or "controller", "computer", "processor", etc., should be understood to include not only computers having different architectures such as single/multiprocessor architectures and sequential (von neumann)/parallel architectures, but also special-purpose circuits such as field-programmable gate arrays (FPGA), application specific circuits (ASIC), signal processing devices, and other processing circuitry. References to computer programs, instructions, code etc. should be understood to include software for a programmable processor or firmware, such as the programmable content of a hardware device (whether instructions for a processor or configuration settings for a fixed-function device, gate array or programmable logic device, etc.).

As used in this application, the term "circuitry" may refer to one or more or all of the following:

(a) Hardware-only circuitry implementations (such as implementations in analog and/or digital circuitry only), and

(b) A combination of hardware circuitry and software, such as (as applicable):

(i) Combination of analog and/or digital hardware circuit(s) and software/firmware, and

(ii) Any portion of a hardware processor (including digital signal processor (s)), software, and memory(s) having software that work together to cause a device such as a mobile phone or server to perform various functions, and

(c) Hardware circuit(s) and/or processor(s), such as microprocessor(s) or a portion of microprocessor(s), that require software (e.g., firmware) to operate, but may not exist when operation is not required.

This definition of circuitry applies to all uses of this term in this application, including in any claims. As another example, as used in this application, the term circuitry also encompasses an implementation of only hardware circuitry or a processor and its (or their) accompanying software and/or firmware. The term circuitry also encompasses (e.g., and if applicable to the particular claim element) a baseband integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

The blocks shown in fig. 1-3 and 8-10 may represent steps in a method and/or portions of code in the computer program 56. The illustration of a particular order of the blocks does not necessarily indicate a required or preferred order for the blocks, and the order and arrangement of the blocks may be varied. In addition, some blocks may be omitted.

It should be appreciated that, at least in some examples, the threshold parameter, threshold, and offset are non-zero.

Where a structural feature has been described, the structural feature may be replaced by means for performing one or more functions of the structural feature, whether the function or functions are explicitly or implicitly described.

Thus, the apparatus 200 comprises means for:

detecting a beam fault; and

recovering from beam failure by:

selecting a carrier for random access; and

the carrier is used for random access,

The apparatus 200 may be part of the internet of things forming part of a larger distributed network.

As used herein, "module" refers to a unit or device that does not include some parts/components added by the end manufacturer or user.

The IE may be encoded as an electromagnetic signal.

The above examples may find application as enabling components for: an automotive system; a telecommunications system; electronic systems, including consumer electronics; a distributed computing system; media systems for generating or rendering media content, including audio, visual and audiovisual content, as well as mixed, intermediate, virtual and/or augmented reality; personal systems, including personal wellness systems or personal fitness systems; a navigation system; user interfaces, also known as human-machine interfaces; networks, including cellular, non-cellular and optical networks; a temporary network; the Internet; the Internet of things; a virtual network; related software and services.

The term "comprising" as used in this document has an inclusive rather than exclusive meaning. That is, any reference to X including Y means that X may include only one Y or may include more than one Y. If "comprising" is to be used in an exclusive sense, the context is explicitly indicated by the reference "comprising only one … …" or the use "consisting of … …".

In this specification, various examples have been referred to. The description of features or functions with respect to an example indicates that the features or functions are present in the example. The use of the term "example" or "e.g." or "may" herein, whether or not explicitly stated, means that such features or functions are present at least in the described examples, whether or not described as examples, and that they may be, but are not necessarily, present in some or all other examples. Thus, "example," e.g., "may," or "may" refer to a particular instance in a class of examples. The attributes of an instance are the attributes of the instance only, the attributes of the class, or the attributes of a subclass of the class that includes some, but not all, instances of the class. Thus, it is implicitly disclosed that features described with reference to one example but not with reference to another example may, where possible, be used as part of a combination of operations in that other example, but are not necessarily used in that other example.

Although the embodiments have been described in the preceding paragraphs with reference to various examples, it should be appreciated that modifications to the examples given can be made without departing from the scope of the claims.

The features described in the previous description may be used in other combinations than those explicitly described above.

Although functions have been described with reference to some features, such functions can be performed by other features whether described or not.

Although features have been described with reference to some embodiments, these features can also be present in other embodiments, whether described or not.

The terms "a" or "an" as used in this document have an inclusive rather than exclusive meaning. That is, any reference to X including a/the Y means that X may include only one Y or may include more than one Y, unless the context clearly indicates to the contrary. If an exclusive meaning of "a" or "an" is to be used, that context will be clearly indicated. In some instances, the use of "at least one" or "one or more" may be employed to emphasize an inclusive meaning, but such terms should not be used in an inferred or exclusive sense.

The presence of a feature (or combination of features) in a claim is a reference to that feature (or combination of features) itself, also means that the feature (equivalent feature) achieves substantially the same technical result. Equivalent features include, for example, features that are variants and that achieve substantially the same result in substantially the same way. Equivalent features include, for example, features that perform substantially the same function in substantially the same way to achieve substantially the same result.

In this specification, the features of examples have been described with reference to various examples using adjectives or adjective phrases. This description of the features with respect to the examples indicates that the features are, in some examples, identical to those described, and in other examples are, in other examples, substantially identical to those described.

The use of the term "example" or "e.g." or "may" herein, whether explicitly stated or not, means that such features or functions are present at least in the described examples, whether or not described as examples, and that they may be, but are not necessarily, present in some or all other examples. Thus, "example," e.g., "may," or "may" refer to a particular instance in a class of examples. The attributes of an instance are the attributes of the instance only, the attributes of the class, or the attributes of a subclass of the class that includes some, but not all, instances of the class. Thus, it is implicitly disclosed that features described with reference to one example but not with reference to another example may be used in that other example as part of a combination of operations where possible, but are not necessarily used in that other example.

Whilst endeavoring in the foregoing specification to draw attention to those features of the invention believed to be of importance it should be understood that the applicant claims protection in respect of any patentable feature or combination of features hereinbefore referred to and/or shown in the drawings whether or not particular emphasis has been placed thereon.

Claims

1. A method of communication, comprising:

data defining threshold parameters that are used exclusively to distinguish between: a comparison of the measured downlink carrier characteristics with a first threshold when a random access procedure is initiated for beam fault recovery, and a comparison of the measured downlink carrier characteristics with a second, different threshold when the random access procedure is initiated but not initiated for beam fault recovery;

selecting an uplink carrier for a random access procedure between a normal uplink carrier NUL and a supplementary uplink carrier SUL;

wherein the threshold used in controlling the selection of carriers for random access is different depending on which carrier is configured for beam fault recovery,

wherein when the random access procedure is initiated for beam failure recovery, selecting an uplink carrier is performed according to a first condition and when the first threshold is configured, the first condition compares the measured downlink carrier characteristics with the first threshold,

When the random access procedure is initiated but not initiated for beam fault recovery, selecting an uplink carrier according to a second condition and the second condition compares the measured downlink carrier characteristic to a second threshold, the second condition being different from the first condition, the second threshold being different from the first threshold; and

the uplink carrier is used for a random access procedure.

2. The method of claim 1, wherein the first condition compares the measured downlink carrier characteristic to a threshold different from the first threshold when the first threshold is not configured.

3. The method of claim 1, wherein the second condition is independent of the first threshold.

4. The method of claim 1, wherein the first condition compares the measured downlink carrier characteristic to the second threshold that is different from the first threshold when the first threshold is not configured.

5. The method of claim 1, wherein selecting an uplink carrier occurs according to a comparison of the measured downlink carrier characteristic to a first threshold when the random access procedure is initiated for beam fault recovery, and selecting an uplink carrier occurs according to a comparison of the measured downlink carrier characteristic to a second threshold when the random access procedure is initiated but not initiated for beam fault recovery.

6. The method of any of claims 1, further comprising: the first threshold is determined at least in part using a threshold parameter that determines the first threshold.

7. The method of claim 6, wherein the threshold parameter is an offset from the second threshold to which the offset is added to create the first threshold.

8. The method of claim 7, the offset is assumed to be zero when the threshold parameter is not configured.

9. The method of claim 8, wherein the threshold parameter defines the first threshold independent of the second threshold.

10. The method according to claim 1, wherein the measured downlink carrier characteristic depends on a received signal power and/or a received signal quality.

11. The method of claim 1, wherein the measured carrier characteristic is a reference signal received power, RSRP, for the selected downlink channel.

12. The method of claim 1, wherein the first condition depends on a comparison of the measured downlink carrier characteristic with a first threshold and additional conditions.

13. The method of claim 12, wherein the additional condition depends on availability of contention-free random access resources.

14. The method of claim 12, wherein the additional condition depends on availability of a beam fault recovery configuration for a currently active bandwidth portion.

15. The method of claim 1, wherein the first condition and the second condition provide separate logical paths, each logical path supporting selection between a normal uplink carrier NUL and a supplemental uplink carrier SUL.

16. The method according to claim 1, comprising:

leading to a preference for carriers that have been assigned a beam fault recovery configuration.

17. The method of claim 16, comprising:

resulting in an alternative selection of carriers that have not been assigned a beam fault recovery configuration.

18. The method according to claim 1, comprising causing the measured carrier characteristics, the first threshold value and/or the second threshold value used in the comparison for selecting carriers to be modified depending on which carrier has been assigned a beam fault recovery configuration.

19. The method of claim 18, comprising:

causing a first offset to be applied to the threshold when the SUL has been assigned a beam fault recovery configuration; and

when NUL has been assigned a beam fault recovery configuration, causing a second offset to be applied to the threshold, wherein one of the first offset and the second offset is positive and the other is negative.

20. The method of claim 19, comprising:

when NUL has been assigned a beam fault recovery configuration, a different second threshold is caused to be used.

21. The method of claim 18, comprising causing the measured carrier characteristics for the selected carrier used in the comparison to be modified depending on whether a SUL or NUL has been assigned a beam fault recovery configuration.

22. The method of claim 18, wherein assignment of a preamble for contention-free random access can only occur on one of an associated uplink normal carrier and an uplink supplemental carrier, and assignment of a preamble for contention-free random access cannot occur for both the associated uplink normal carrier and uplink supplemental carrier.

23. An apparatus for communication comprising means for performing the method of any of claims 1-22.

24. The apparatus of claim 23, wherein the apparatus is configured as a mobile device or as a user equipment.

25. An apparatus for communication, comprising:

At least one processor; and

at least one memory including computer program code,

the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform the method of any one of claims 1-22.

26. The apparatus of claim 25, wherein the apparatus is configured as a mobile device or as a user equipment.

27. A computer program product comprising computer executable instructions which, when run on a computer, cause the computer to perform the method according to any one of claims 1-22.

28. A computer readable storage medium comprising a computer program comprising computer executable instructions which, when executed on a computer, cause the computer to perform the method according to any one of claims 1-22.

29. A network comprising a plurality of network nodes, a network node of the plurality comprising the apparatus of claim 23 or 25.