Scheduling request-based beam fault recovery

Abstract

To provide a scheduling request based beam failure recovery.SOLUTION: A wireless device transmits a first scheduling request (SR) based on a buffer status reporting procedure. A second SR is triggered in response to initiating a beam failure recovery. The second SR is transmitted via an uplink control channel resource configured for the second SR. First downlink control information is received via a downlink control channel, as a response to the second SR. Based on receiving the first downlink control information, the first SR is kept pending, and the second SR is cancelled for the beam failure recovery.SELECTED DRAWING: Figure 21

Description

Background Art

[0001] Cross - reference to related applications This application claims priority to U.S. Provisional Patent Application No. 62 / 650,733, filed Mar. 30, 2018, which is hereby incorporated by reference in its entirety.

Summary of the Invention

Means for Solving the Problems

[0002] Exemplary embodiments of the present disclosure enable the operation of a beam failure recovery procedure. Embodiments of the techniques disclosed herein may be used in the technical field of multi - carrier communication systems. More specifically, embodiments of the techniques disclosed herein may relate to a beam failure recovery procedure in a multi - carrier communication system. The present invention provides, for example, the following. (Item 1) A method comprising: transmitting, by a wireless device, a first scheduling request (SR) based on a buffer status report procedure; triggering a second SR in response to starting beam failure recovery; transmitting the second SR via an uplink control channel resource configured for the second SR; receiving, via a downlink control channel, first downlink control information as a response to the second SR; based on receiving the first downlink control information, holding the first SR in a pending state and canceling the second SR for the beam failure recovery. (Item 2) The uplink control channel resource comprises a frequency radio resource and an uplink control channel format. The basic sequence cyclic shift and The method according to item 1, comprising at least one of the following: a time-based wireless resource and (Item 3) The method according to item 1, wherein the first downlink control information includes downlink assignment. (Item 4) The method according to item 1, wherein the first downlink control information includes uplink permission. (Item 5) The method according to item 1, further comprising completing the beam fault recovery in response to canceling the second SR. (Item 6) The first configuration parameters of the first plurality of SRs, including the first SR, The method according to item 1, further comprising receiving one or more messages containing at least one of the second configuration parameters of the second SR. (Item 7) The method according to item 6, wherein the wireless device triggers the second SR based on the second configuration parameter. (Item 8) The method according to item 6, wherein the second configuration parameter indicates the uplink control channel resource for the second SR. (Item 9) The method according to item 1, wherein the wireless device initiates beam fault recovery in response to detecting the number of beam fault instances. (Item 10) The method according to item 9, wherein the wireless device detects the number of beam fault instances in response to the channel quality of one or more reference signal resources being lower than one or more first thresholds. (Item 11) The method according to item 9, further comprising selecting a first reference signal from a plurality of reference signals based on one or more second thresholds in response to initiating beam fault recovery. (Item 12) The method according to item 11, wherein the second SR indicates the reference signal received power value of the first reference signal. (Item 13) The second SR mentioned above is The number of beam fault instances is detected, The method according to item 11, wherein at least one of the following is selected: the first reference signal is selected. (Item 14) The method according to item 1, further comprising monitoring the downlink control channel with respect to the first downlink control information. (Item 15) The aforementioned wireless device The downlink control channel comprises at least one set of control resources, The method according to item 14, wherein the downlink control channel is monitored with respect to at least one search space of the downlink control channel. (Item 16) The method according to item 14, wherein the downlink control channel is associated with the second SR. (Item 17) The downlink control channel is associated with the second SR. Based on the second SR, at least one set of control resources for the downlink control channel is determined, The method according to item 16, comprising at least one of the following: determining at least one search space for the downlink control channel based on the second SR. (Item 18) The method according to item 1, further comprising transmitting the first SR via a second uplink control channel resource configured for the first SR in response to holding the first SR in a pending state. (Item 19) The method according to item 18, further comprising receiving one or more second downlink control pieces of information, including one or more uplink permissions, via a second downlink control channel. (Item 20) The method according to item 19, further comprising canceling the first SR in response to the one or more uplink grants corresponding to data available for uplink transmission. (Item 21) A method comprising: transmitting, by a wireless device, a first scheduling request (SR) based on a buffer status report procedure; triggering a second SR based on starting beam failure recovery; transmitting the second SR; receiving first downlink control information in response to the second SR; based on receiving the first downlink control information, holding the first SR in a pending state and canceling the second SR. (Item 22) A wireless device comprising: one or more processors; and a memory storing instructions that, when executed by the one or more processors, cause the wireless device to transmit, by the wireless device, a first scheduling request (SR) based on a buffer status report procedure; trigger a second SR in response to starting beam failure recovery; transmit the second SR via an uplink control channel resource configured for the second SR; receive first downlink control information as a response to the second SR via a downlink control channel; based on the first downlink control information, hold the first SR in a pending state and cancel the second SR for the beam failure recovery. (Item 23) A method comprising: The base station transmits one or more radio resource control messages including cell configuration parameters, where the configuration parameters are a first scheduling request (SR) configuration associated with a logical channel, a second SR configuration associated with beam failure recovery, and transmits, receiving a first SR based on the first SR configuration via a first uplink control resource based on a buffer status report procedure, receiving a second SR based on the second SR configuration via a second uplink control resource for beam failure recovery, determining a control resource set for transmission of downlink control information as a response to the second SR, transmitting the downlink control information including one or more uplink grants via a downlink control channel on the control resource set based on the first SR and the second SR. A method including. (Item 24) The method according to item 23, wherein the first SR configuration includes the first uplink control resource. (Item 25) The method according to item 23, wherein the second SR configuration includes the second uplink control resource. (Item 26) The first uplink control resource is a first frequency radio resource, a first uplink control channel format, a first cyclic shift of a basic sequence, a first time radio resource, and includes at least one of the methods according to item  23. (Item 27) The second uplink control resource is a second frequency radio resource, a second uplink control channel format, a second cyclic shift of a basic sequence, The method described in item 23, comprising a second time-based radio resource and at least one of the following. (Item 28) The method according to item 23, wherein the second SR indicates the reference signal received power value of the first reference signal. (Item 29) The second SR mentioned above is The number of beam failure instances is detected, The method of item 23, which indicates that a first reference signal is selected, and at least one of the following. (Item 30) The method according to item 23, further comprising the wireless device initiating beam fault recovery in response to detecting the number of beam fault instances. (Item 31) The method according to item 30, wherein the wireless device detects the number of beam fault instances in response to the channel quality of one or more reference signal resources being lower than one or more first thresholds. (Item 32) The method according to item 30, further comprising selecting a first reference signal from a plurality of reference signals based on one or more second thresholds in response to initiating beam fault recovery. (Item 33) The method according to item 32, wherein the second SR indicates the reference signal received power value of the first reference signal. (Item 34) The second SR mentioned above is The number of beam fault instances is detected, The method according to item 32, wherein at least one of the following is selected: the first reference signal is selected. (Item 35) It is a method, Receiving a first SR based on a first SR configuration associated with a logical channel via a first uplink control resource based on a buffer status report procedure, Receiving a second SR based on a second SR configuration associated with beam fault recovery via a second uplink control resource for beam fault recovery, In response to the second SR, a control resource set for transmitting downlink control information is determined, A method comprising transmitting downlink control information, including uplink permission, based on the first SR and the second SR, and via the control resource set. (Item 36) It is a method, The wireless device triggers a scheduling request in response to initiating beam fault recovery, Determining a reference signal from multiple reference signals, Transmitting uplink control information for the scheduling request via an uplink control channel resource, wherein the uplink control information is A reference signal identifier indicating the aforementioned reference signal, To transmit, which includes at least one of the following: the reference signal and the reference signal received power value of the reference signal; Receiving downlink control information as a response to uplink control information via a downlink control channel on the control resource set associated with beam fault recovery, Based on the downlink control information, the scheduling request is canceled. A method comprising completing beam fault recovery in response to canceling the scheduling request. (Item 37) The method according to item 36, wherein the wireless device determines the reference signal based on one or more thresholds. (Item 38) The method of item 36, further comprising receiving one or more messages containing a first configuration parameter of a scheduling request configuration associated with beam fault recovery, wherein the first configuration parameter indicates the uplink control channel resource for the scheduling request. (Item 39) One or more configuration parameters of the uplink control channel resource are, Frequency radio resources and Uplink control Channel format and The basic sequence cyclic shift and The method described in item 36, which includes at least one of the following: a time-based wireless resource and (Item 40) One or more configuration parameters of the control resource set are Control resource set index and, Number of symbols and, A set of resource blocks, The method of item 36, comprising at least one of the following: a control channel element versus resource element group mapping display. (Item 41) The method according to item 36, wherein the downlink control information includes downlink radio resource allocation for downlink transport block transmission. (Item 42) The method according to item 36, wherein the downlink control information includes uplink permission for uplink transport block transmission. (Item 43) The method according to item 36, wherein the wireless device initiates beam fault recovery in response to detecting the number of beam fault instances. (Item 44) The wireless device detects the number of beam fault instances in response to the channel quality of one or more reference signal resources being lower than one or more thresholds, according to the method of item 43. (Item 45) The method of item 36, further comprising receiving one or more messages containing a first configuration parameter of a scheduling request configuration associated with beam fault recovery, wherein the first configuration parameter indicates the control resource set for beam fault recovery. (Item 46) The method according to item 45, wherein the one or more messages further include a second configuration parameter of at least a second scheduling request configuration associated with a logical channel, the second configuration parameter indicating a second uplink control channel resource. (Item 47) The method according to item 46, further comprising transmitting a second scheduling request based on the at least second scheduling request configuration for the buffer status reporting procedure of the logical channel. (Item 48) The method according to item 47, wherein the wireless device transmits the second scheduling request via the second uplink control channel resource. (Item 49) The method according to item 36, further comprising monitoring the downlink control channel on the control resource set in a response window in response to transmitting the uplink control information for beam fault recovery. (Item 50) The method according to item 49, wherein the duration of the response window is configured in the wireless resource control message. (Item 51) The method according to item 49, wherein the response window includes a timer having a timer value. (Item 52) The method of item 49, further comprising initiating the response window in response to transmitting the uplink control information. (Item 53) The method of item 52, further comprising retransmitting the uplink control information in response to not receiving the response within the response window. (Item 54) The method according to item 52, further comprising incrementing a request counter in response to not receiving the response within the response window. (Item 55) The method according to item 54, further comprising canceling the scheduling request in response that the request counter is greater than or equal to a first value. (Item 56) The method of item 55, further comprising completing beam fault recovery in response to canceling the scheduling request. (Item 57) It is a method, The wireless device triggers a scheduling request based on initiating beam fault recovery, Determining a reference signal from multiple reference signals, Transmitting uplink control information for the scheduling request via the uplink control channel resource, Receiving downlink control information based on the uplink control information via the control resource set associated with beam fault recovery, Based on the downlink control information, the scheduling request is canceled. A method comprising completing beam fault recovery in response to canceling the scheduling request. (Item 58) It is a method, The wireless device transmits a first scheduling request (SR) based on a buffer status report procedure, In response to initiating beam fault recovery, a second SR is triggered, Transmitting the second SR via the uplink resources configured for the second SR, Receiving first downlink control information in response to the second SR, Based on the fact that the first downlink control information includes uplink permission, The first SR is canceled, and A method comprising canceling the second SR for beam fault recovery. (Item 59) The aforementioned uplink resource, Frequency radio resources and Uplink control Channel format and The basic sequence cyclic shift and The method described in item 58, which includes at least one of the following: a time-based radio resource and (Item 60) The method of item 58, further comprising completing the beam fault recovery in response to canceling the second SR. (Item 61) The first configuration parameters of the first plurality of SRs, including the first SR, The method according to item 58, further comprising receiving one or more messages containing at least one of the second configuration parameters of the second SR. (Item 62) The method according to item 61, wherein the wireless device triggers the second SR based on the second configuration parameter. (Item 63) The method according to item 61, wherein the second configuration parameter indicates the uplink resource of the uplink control channel for the second SR. (Item 64) The method according to item 58, wherein the wireless device initiates beam fault recovery in response to detecting the number of beam fault instances. (Item 65) The method according to item 64, wherein the wireless device detects the number of beam fault instances in response to the channel quality of one or more reference signal resources being lower than one or more first thresholds. (Item 66) The method according to item 64, further comprising selecting a first reference signal from a plurality of reference signals based on one or more second thresholds in response to initiating beam fault recovery. (Item 67) The method according to item 66, wherein the second SR indicates the reference signal received power value of the first reference signal. (Item 68) The second SR mentioned above is The number of beam fault instances is detected, The method of item 66, wherein at least one of the following is selected: the first reference signal is selected. (Item 69) The method according to item 58, further comprising monitoring a downlink control channel for the first downlink control information. (Item 70) The aforementioned wireless device The downlink control channel comprises at least one set of control resources, The method according to item 69, wherein the downlink control channel is monitored with respect to at least one search space of the downlink control channel. (Item 71) The method according to item 70, wherein the downlink control channel is associated with the second SR. (Item 72) The downlink control channel is associated with the second SR. Based on the second SR, at least one set of control resources for the downlink control channel is determined, The method according to item 71, comprising at least one of the following: that at least one of the search spaces for the downlink control channel is determined based on the second SR. (Item 73) It is a method, The wireless device transmits a first scheduling request (SR) based on a buffer status report procedure, In response to initiating beam fault recovery, a second SR is triggered, Transmitting the second SR via the uplink resources configured for the second SR, Receiving first downlink control information in response to the second SR, Based on the fact that the first downlink control information includes downlink assignment, The first SR is kept in a pending state, and A method comprising canceling the second SR for beam fault recovery. (Item 74) The aforementioned uplink resource, Frequency radio resources and Uplink control Channel format and The basic sequence cyclic shift and The method described in item 73, which includes at least one of the following: a time-based radio resource and (Item 75) The method according to item 73, further comprising completing the beam fault recovery in response to canceling the second SR. (Item 76) The first configuration parameters of the first plurality of SRs, including the first SR, The method according to item 73, further comprising receiving one or more messages containing at least one of the second configuration parameters of the second SR. (Item 77) The method according to item 76, wherein the wireless device triggers the second SR based on the second configuration parameter. (Item 78) The method according to item 76, wherein the second configuration parameter indicates the uplink resource of the uplink control channel for the second SR. (Item 79) The method according to item 73, wherein the wireless device initiates beam fault recovery in response to detecting the number of beam fault instances. (Item 80) The method according to item 79, wherein the wireless device detects the number of beam fault instances in response to the channel quality of one or more reference signal resources being lower than one or more first thresholds. (Item 81) The method according to item 79, further comprising selecting a first reference signal from a plurality of reference signals based on one or more second thresholds in response to initiating beam fault recovery. (Item 82) The method according to item 81, wherein the second SR indicates the reference signal received power value of the first reference signal. (Item 83) The second SR mentioned above is The number of beam fault instances is detected, The method according to item 81, wherein at least one of the following is selected: the first reference signal is selected. (Item 84) The method according to item 73, further comprising monitoring a downlink control channel for the first downlink control information. (Item 85) The aforementioned wireless device The downlink control channel comprises at least one set of control resources, The method according to item 84, wherein the downlink control channel is monitored with respect to at least one search space of the downlink control channel. (Item 86) The method according to item 84, wherein the downlink control channel is associated with the second SR. (Item 87) The downlink control channel is associated with the second SR. At least one set of control resources for the downlink control channel is determined based on the second SR, The method according to item 86, comprising at least one of the following: the search space of the downlink control channel is determined based on the second SR. (Item 88) The method according to item 73, further comprising transmitting the first SR via a second uplink control channel resource configured for the first SR in response to holding the first SR in a pending state. (Item 89) The method according to item 88, further comprising receiving one or more second downlink control pieces of information, including one or more uplink permissions, via a second downlink control channel. (Item 90) The method according to item 89, further comprising canceling the first SR in response that one or more of the uplink permissions correspond to data available for uplink transmission. (Item 91) It is a method, The wireless device triggers a first scheduling request (SR) based on the buffer status report procedure, Based on initiating beam fault recovery, a second SR is triggered, Transmitting the second SR via an uplink resource associated with the second SR, Monitoring the downlink control channel for the response to the second SR, Based on the SR counter being greater than or equal to the first value, the second SR is canceled. The first SR is kept in a pending state, and A method comprising initiating a random access procedure for beam fault recovery. (Item 92) The aforementioned uplink resource, Frequency radio resources and Uplink control Channel format and The basic sequence cyclic shift and The method described in item 91, comprising at least one of the following: a time-based radio resource and (Item 93) The method according to item 91, further comprising completing the beam fault recovery in response to canceling the second SR. (Item 94) The first configuration parameters of the first plurality of SRs, including the first SR, The method according to item 91, further comprising receiving one or more messages containing at least one of the second configuration parameters of the second SR. (Item 95) The method according to item 94, wherein the wireless device triggers the second SR based on the second configuration parameter. (Item 96) The method according to item 94, wherein the second configuration parameter indicates the uplink resource of the uplink control channel for the second SR. (Item 97) The method according to item 91, wherein the wireless device initiates beam fault recovery in response to detecting the number of beam fault instances. (Item 98) The method according to item 97, wherein the wireless device detects the number of beam fault instances in response to the channel quality of one or more reference signal resources being lower than one or more first thresholds. (Item 99) The method according to item 97, further comprising selecting a first reference signal from a plurality of reference signals based on one or more second thresholds in response to initiating beam fault recovery. (Item 100) The method according to item 99, wherein the second SR indicates the reference signal received power value of the first reference signal. (Item 101) The second SR mentioned above is The number of beam fault instances is detected, The method according to item 99, wherein at least one of the following is selected: the first reference signal is selected. (Item 102) The method according to item 91, further comprising monitoring a downlink control channel for the response. (Item 103) The aforementioned wireless device The downlink control channel comprises at least one set of control resources, The method according to item 102, wherein the downlink control channel is monitored with respect to at least one search space of the downlink control channel. (Item 104) The method according to item 102, wherein the downlink control channel is associated with the second SR. (Item 105) The downlink control channel is associated with the second SR. At least one set of control resources for the downlink control channel is determined based on the second SR, The method according to item 104, comprising at least one of the following: the search space of the downlink control channel is determined based on the second SR. (Item 106) The method according to item 91, wherein the wireless device monitors the downlink control channel in a response window. (Item 107) The method according to item 106, wherein the size of the response window is configured in the RRC message. (Item 108) The method according to item 107, further comprising incrementing the SR counter based on the absence of the response in the response window. (Item 109) The method according to item 91, further comprising transmitting the first SR via a second uplink control channel resource configured for the first SR in response to holding the first SR in a pending state. (Item 110) The method according to item 109, further comprising receiving one or more second downlink control pieces of information, including one or more uplink permissions, via a second downlink control channel. (Item 111) The method according to item 110, further comprising canceling the first SR in response that one or more of the uplink permissions correspond to data available for uplink transmission. (Item 112) It is a method, Based on the detection of the number of beam fault instances by a wireless device, beam fault recovery is initiated. Transmitting a preamble via a random access channel resource in response to initiating beam fault recovery, In response to not receiving a first response to the preamble, the request transmission counter is incremented. Transmitting uplink control information for beam fault recovery via the uplink control channel resource, In response to not receiving a second response to the uplink control information, the request transmission counter is incremented. A method comprising completing beam fault recovery in response to the request transmission counter being greater than or equal to a first value. (Item 113) The method according to item 112, wherein the wireless device detects the number of beam fault instances in response to the channel quality of one or more reference signal resources being lower than one or more first thresholds. (Item 114) The uplink control channel resource is Frequency radio resources and Uplink control Channel format and The basic sequence cyclic shift and The method described in item 112, which includes at least one of the following: a time-based radio resource and (Item 115) The method according to item 112, further comprising selecting a first reference signal from a plurality of reference signals based on one or more second thresholds in response to initiating beam fault recovery. (Item 116) The method according to item 115, wherein the random access channel resource is associated with the first reference signal. (Item 117) The method according to item 112, further comprising initiating a response window at a first time value based on the transmission of the preamble. (Item 118) The method according to item 117, wherein the wireless device increments the request transmission counter in response to not receiving the first response to the preamble when the response window has expired. (Item 119) The method according to item 112, further comprising initiating a response window with a time value in response to transmitting the uplink control information. (Item 120) The method according to item 119, wherein the wireless device increments the request transmission counter in response to not receiving the second response to the uplink control information when the response window has expired. (Item 121) It is a method, Transmitting a preamble based on initiating beam fault recovery via a random access channel resource, Based on the failure to receive a first response to the aforementioned preamble, the request transmission counter is incremented. Transmitting uplink control information for beam fault recovery via the uplink control channel resource, A method comprising completing beam fault recovery based on the request transmission counter being greater than or equal to a first value. (Item 122) It is a method, Transmitting a preamble for beam fault recovery via a first random access channel resource, based on the fact that the first random access channel resource is faster than the first uplink control channel resource, If no response to the preamble is received during the response window, A method comprising transmitting uplink control information for beam fault recovery via the second uplink control channel resource, based on the fact that the second uplink control channel resource is faster than the second random access channel resource. (Item 123) The first uplink control channel resource is Frequency radio resources and Uplink control Channel format and The basic sequence cyclic shift and The method described in item 122, comprising at least one of the following: a time-based wireless resource and (Item 124) The method according to item 122, further comprising initiating the response window in response to transmitting the preamble. (Item 125) The method of item 122, further comprising initiating the response window in response to transmitting the uplink control information. (Item 126) The method according to item 122, further comprising initiating beam fault recovery based on the detection of the number of beam fault instances. (Item 127) The method according to item 126, wherein a wireless device detects the number of beam fault instances in response to the channel quality of one or more reference signal resources being lower than one or more first thresholds. (Item 128) The method according to item 126, further comprising selecting a first reference signal from a plurality of reference signals based on one or more second thresholds in response to initiating beam fault recovery. (Item 129) The method according to item 128, wherein the first random access channel resource is associated with the first reference signal. (Item 130) The method according to item 129, wherein the first uplink control channel resource is associated with the first reference signal. (Item 131) It is a method, Based on the detection of the number of beam fault instances by a wireless device, beam fault recovery is initiated. In response to initiating the beam fault recovery, it is determined that the first random access channel resource is faster than the first uplink control channel resource, Transmitting the preamble for beam fault recovery via the first random access channel resource, Monitoring the downlink control channel for the response to the aforementioned preamble, In response to not receiving the aforementioned response, it is determined that the second uplink control channel resource is faster than the second random access channel resource, A method comprising transmitting uplink control information for beam fault recovery via the second uplink control channel resource. [Brief explanation of the drawing]

[0003] Several examples of various embodiments of this disclosure are described herein with reference to the drawings. [Figure 1] This is a schematic diagram of an exemplary RAN architecture based on one embodiment of the present disclosure. [Figure 2A] This is a schematic diagram of an exemplary user-plane protocol stack based on one embodiment of the present disclosure. [Figure 2B] This is a schematic diagram of an exemplary control plane protocol stack based on one embodiment of the present disclosure. [Figure 3] This is a schematic diagram of an exemplary wireless device and two base stations based on one embodiment of the present disclosure. [Figure 4] This is a schematic diagram illustrating uplink signal transmission and downlink signal transmission according to one embodiment of the present disclosure. [Figure 5A] This is a schematic diagram of exemplary uplink channel mapping and exemplary uplink physical signals based on one embodiment of the present disclosure. [Figure 5B] This is a schematic diagram of an exemplary downlink channel mapping and an exemplary downlink physical signal based on one embodiment of the present disclosure. [Figure 6] This is a schematic diagram illustrating the transmission and reception times of an exemplary carrier, based on one embodiment of the present disclosure. [Figure 7A] This is a schematic diagram illustrating an exemplary set of OFDM subcarriers based on one embodiment of the present disclosure. [Figure 7B] This is a schematic diagram illustrating an exemplary set of OFDM subcarriers based on one embodiment of the present disclosure. [Figure 8] This is a schematic diagram illustrating an exemplary OFDM radio resource based on one embodiment of the present disclosure. [Figure 9A] This is a schematic diagram illustrating an example of CSI-RS and / or SS block transmission in a multibeam system. [Figure 9B] This is a schematic diagram illustrating an exemplary downlink beam management procedure based on one embodiment of the present disclosure. [Figure 10] This is an illustrative schematic diagram of a configured BWP based on one embodiment of the present disclosure. [Figure 11A] This is an exemplary schematic diagram of multi-connectivity based on one embodiment of the present disclosure. [Figure 11B] This is an exemplary schematic diagram of multi-connectivity based on one embodiment of the present disclosure. [Figure 12] This is a schematic diagram of an exemplary random access procedure based on one embodiment of the present disclosure. [Figure 13] This is an exemplary MAC entity structure based on one embodiment of the present disclosure. [Figure 14] This is a schematic diagram of an exemplary RAN architecture based on one embodiment of the present disclosure. [Figure 15] This is a schematic diagram illustrating an exemplary RRC state based on one embodiment of the present disclosure. [Figure 16A] This is an example of a downlink beam failure scenario based on one embodiment of the present disclosure. [Figure 16B] This is an example of a downlink beam failure scenario based on one embodiment of the present disclosure. [Figure 17] This is an example of a downlink beam fault recovery procedure based on one embodiment of the embodiments of the present disclosure. [Figure 18] This is an example of a scheduling request procedure based on one embodiment of the present disclosure. [Figure 19] This is an example of a BFR procedure requirements configuration based on one embodiment of the embodiments of the present disclosure. [Figure 20] This is an example of a flowchart with an example of a required configuration, based on one embodiment of the present disclosure. [Figure 21] This is an example of a BFR procedure based on one embodiment of the embodiments of the present disclosure. [Figure 22] This is an example of a BFR procedure based on one embodiment of the embodiments of the present disclosure. [Figure 23] This is an exemplary flowchart based on one embodiment of the present disclosure. [Figure 24] This is an exemplary flowchart based on one embodiment of the present disclosure. [Figure 25] This is an exemplary flowchart based on one embodiment of the present disclosure. [Figure 26] This is an exemplary flowchart based on one embodiment of the present disclosure. [Figure 27] This is an exemplary flowchart based on one embodiment of the present disclosure. [Figure 28] This is an exemplary flowchart based on one embodiment of the present disclosure. [Figure 29] This is an exemplary flowchart based on one embodiment of the present disclosure. [Figure 30] This is an exemplary flowchart based on one embodiment of the present disclosure. [Figure 31] This is an exemplary flowchart based on one embodiment of the present disclosure. [Figure 32] This is an exemplary flowchart based on one embodiment of the present disclosure. [Figure 33] This is an exemplary flowchart based on one embodiment of the present disclosure. [Figure 34] This is an exemplary flowchart based on one embodiment of the present disclosure. [Figure 35]This is an exemplary flowchart based on one embodiment of the present disclosure. [Modes for carrying out the invention]

[0004] The following acronyms will be used throughout this disclosure. 3GPP Third Generation Partnership Project 5GC 5G Core Network ACK (Affirmative Response) AMF access and mobility management functions ARQ Automated Recurring Request AS Access Layer ASIC (Application-Specific Integrated Circuit) BA bandwidth adaptive BCCH Broadcast Control Channel BCH Broadcast Channel BPSK 2-phase phase modulation BWP bandwidth portion BSR Buffer Status Report CA Career Aggregation CC Component Carrier CCCH Common Control Channel CDMA code division multiple access CN Core Network CP cyclic prefix CP-OFDM cyclic prefix orthogonal frequency division multiplexing C-RNTI Cell Radio Network Temporary Identifier CS Configuration Scheduling CSI Channel Status Information CSI-RS Channel Status Information - Reference Signal CQI Channel Quality Indicator CSS common search space CU Integration Unit DC Dual Connection DCCH Dedicated Control Channel DCI Downlink Control Information DL Downlink DL-SCH Downlink Shared Channel DM-RS demodulation reference signal DRB Data Wireless Bearer DRX intermittent reception Dedicated DTCH traffic channel DU Distributed Unit EPC Advanced Packet Core E-UTRA Advanced UMTS Terrestrial Wireless Access E-UTRAN: Evolved Universal Terrestrial Wireless Access Network FDD Frequency Division Duplex FPGA Field-Programmable Gate Array F1-C F1-Control Plane F1-U F1-User Plane gNB Next Generation Node B HARQ Hybrid Automated Repetitive Request HDL Hardware Description Language IE Information Elements IP Internet Protocol LCID (Logical Channel Identifier) LTE Long-Term Evolution MAC Media Access Control MCG Mastercell Group MCS Modulation and Coding Scheme MeNB Master Evolution Node B MIB Master Information Block MME Mobility Management Entity MN Master Node NACK Negative / Affirmative Response NAS Non-Access Layer NG CP Next-Generation Control Plane NGC Next Generation Core NG-C NG-Control Plane ng-eNB Next-generation evolved node B NG-U NG-User Plane NR new radio NR MAC New wireless MAC NR PDCP New wireless PDCP NR PHY New Radio Physics NR RLC New Wireless RLC NR RRC New Radio RRC NSSAI Network Slice Selection Support Information O&M Operation and Maintenance OFDM (Orthogonal Frequency Division Multiplexing) PBCH Physical Broadcast Channel PCC Primary Component Carrier PCCH Paging Control Channel PCell Primary Cell PCH Paging Channel PDCCH Physical Downlink Control Channel PDCP Packet Data Convergence Protocol PDSCH Physical Downlink Shared Channel PDU Protocol Data Unit PHICH Physical HARQ Indicator Channel PHY physics PLMN Public Land Mobile Network PMI Precoding Matrix Indicator PRACH Physical Random Access Channel PRB (Physical Resource Block) PSCell Primary Secondary Cell PSS Primary Sync Signal pTAG Primary Timing Advanced Group PT-RS Phase Tracking Reference Signal PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel QAM (Quaternary Amplitude Modulation) QFI (Quality of Service Indicator) QoS (Quality of Service) QPSK 4-phase phase modulation RA (Random Access) RACH Random Access Channel RAN (Radio Access Network) RAT (Radio Access Technology) RA-RNTI Random Access Radio Network Temporary Identifier RB Resource Block RBG Resource Block Group RI Rank Indicator RLC Wireless Link Control RRC (Radio Resource Control) RS reference signal RSRP Reference Signal Received Power SCC Secondary Component Carrier SCell Secondary Cell SCG Secondary Cell Group SC-FDMA Single Carrier Frequency Division Multiple Access SDAP Service Data Adaptive Protocol SDU Service Data Unit SeNB Secondary Evolutionary Node B SFN System Frame Number S-GW Serving Gateway SI System Information SIB System Information Block SMF session management function SN Secondary Node SpCell Special Cell SR scheduling request SRB Signaling Radio Bearer SRS Sounding Reference Signal SS synchronization signal SSS Secondary Synchronization Signal sTAG Secondary Timing Advance Group TA Timing Advance TAG Timing Advance Group TAI Tracking Area Identifier TAT Time Alignment Timer TB transport block TC-RNTI Temporary Cell Wireless Network Temporary Identifier TDD (Time-Defined Duplex) TDMA (Time Division Multiple Access) TTI (Time Time Interval) UCI Uplink Control Information UE User Equipment UL Uplink UL-SCH Uplink Sharing Channel UPF User Plane Functionality UPGW User Plane Gateway VHDL (VHSIC) Hardware Description Language Xn-C Xn-Control Plane Xn-U Xn-User Plane

[0005] The exemplary embodiments of this disclosure can be implemented using a variety of physical layer modulation and transmission mechanisms. Exemplary transmission mechanisms may include, but are not limited to, code division multiple access (CDMA), quadrature frequency division multiple access (OFDMA), time division multiple access (TDMA), wavelet techniques, and / or similar. Hybrid transmission mechanisms such as TDMA / CDMA and OFDM / CDMA may also be used. Various modulation schemes can be applied to signal transmission at the physical layer. Examples of modulation schemes may include, but are not limited to, phase, amplitude, code, combinations thereof, and / or similar. Exemplary wireless transmission methods can implement quadrature amplitude modulation (QAM) using two-phase phase modulation (BPSK), four-phase phase modulation (QPSK), 16-QAM, 64-QAM, 256-QAM, and / or similar. Physical wireless transmission can be enhanced by dynamically or semi-dynamically changing the modulation and coding scheme depending on the transmission requirements and wireless conditions.

[0006] Figure 1 shows an exemplary radio access network (RAN) architecture based on one embodiment of the present disclosure. As illustrated in this example, RAN nodes may be next-generation nodes B (gNBs) (e.g., 120A, 120B) that can provide new radio (NR) user plane and control plane protocol terminations to a first radio device (e.g., 110A). In one example, RAN nodes may also be next-generation evolved nodes B (ng-eNBs) (e.g., 120C, 120D) that can provide evolved UMTS terrestrial radio access (E-UTRA) user plane and control plane protocol terminations to a second radio device (e.g., 110B). The first radio device can communicate with the gNB via a Uu interface. The second radio device can communicate with the ng-eNB via a Uu interface.

[0007] gNB or ng-eNB may host functions such as radio resource management and scheduling, IP header compression, data encryption and integrity protection, selection of access and mobility management functions (AMF) on user equipment (UE) attachments, routing of user plane data and control plane data, connection setup and release, scheduling and transmission of paging messages (originating from AMF), scheduling and transmission of system broadcast information (originating from AMF or operation and maintenance (O&M)), measurement and measurement report configuration, transport level packet marking in uplinks, session management, support for network slicing, quality of service (QoS) flow management, and mapping to data radio bearers, support for UEs in the RRC_INACTIVE state, distribution functions for non-access layer (NAS) messages, RAN sharing, dual connectivity, or tight interworking between NR and E-UTRA.

[0008] In one example, one or more gNBs and / or one or more ng-eNBs can be interconnected with each other by an Xn interface. A gNB or ng-eNB can be connected to a 5G core network (5GC) by an NG interface. In one example, a 5GC may have one or more AMF / User Planning Function (UPF) functions (e.g., 130A or 130B). A gNB or ng-eNB can be connected to a UPF by an NG-User Plane (NG-U) interface. The NG-U interface can provide the distribution of User Plane Protocol Data Units (PDUs) between RAN nodes and UPFs (e.g., unguaranteed distribution). A gNB or ng-eNB may be connected to an AMF by an NG-Control Plane (NG-C) interface. The NG-C interface can provide functions such as NG interface management, UE context management, UE mobility management, NAS message transport, paging, PDU session management, configuration transfer, or warning message sending.

[0009] In one example, UPF can act as a host providing functions such as an anchor point for intra / inter-radio access technology (RAT) mobility (where applicable), an external PDU session point for interconnection with data networks, packet routing and forwarding, packet inspection and user plane components for policy rule enforcement, traffic usage reporting, an uplink classifier to support routing of traffic flows to data networks, a branching point to support multi-homed PDU sessions, QoS processing for the user plane, e.g., packet filtering, gating, uplink (UL) / downlink (DL) rate enforcement, uplink traffic validation (e.g., Service Data Flow (SDF) to QoS flow mapping), downlink packet buffering, and / or downlink data notification triggering.

[0010] In one example, AMF can host functions such as NAS signaling termination, NAS signaling security, access layer (AS) security control, intercore network (CN) node signaling for mobility between 3rd Generation Partnership Project (3GPP) access networks, idle mode UE reachability (e.g., control and execution of paging retransmission), enrolled area management, support for intra-system and inter-system mobility, access authentication, access authorization including roaming rights checks, mobility management control (enrollment and policy), network slicing support, and / or session management function (SMF) selection.

[0011] Figure 2A shows an exemplary user-plane protocol stack, where the Service Data Adaptive Protocol (SDAP) (e.g., 211 and 221), Packet Data Convergence Protocol (PDCP) (e.g., 212 and 222), Radio Link Control (RLC) (e.g., 213 and 223), and Media Access Control (MAC) (e.g., 214 and 224) sublayers, as well as the Physical (PHY) (e.g., 215 and 225) layer, can be terminated at radio devices (e.g., 110) and gNBs (e.g., 120) on the network side. In one example, the PHY layer provides transport services to higher layers (e.g., MAC, RRC, etc.). In one example, the services and functions of the MAC sublayer may include mapping between logical channels and transport channels, multiplexing / splitting of MAC service data units (SDUs) belonging to one or more logical channels to / from transport blocks (TBs) delivered to / from the PHY layer, scheduling information reporting, error correction via hybrid automatic iterative requests (HARQ) (e.g., one HARQ entity per carrier in the case of carrier aggregation (CA)), prioritization between UEs by dynamic scheduling, prioritization between logical channels of a single UE by logical channel prioritization, and / or padding. A MAC entity may support one or more numerologies and / or transmission timings. In one example, mapping restrictions in logical channel prioritization can control which numerologies and / or transmission timings a logical channel can use. In one example, the RLC sublayer may support transparent mode (TM), unaffirmative mode (UM), and affirmative mode (AM) transmission modes. This RLC configuration can be per logical channel, independent of the numerology and / or transmission time interval (TTI) duration. For example, an automatic repeating request (ARQ) can operate with respect to any numerology and / or TTI duration in which the logical channel is configured.In one example, the PDCP layer services and functions for the user plane may include sequence numbering, header compression and decompression, user data transfer, reordering and duplicate detection, PDCP PDU routing (e.g., for split bearers), PDCP SDU retransmission, encryption, decryption and integrity protection, PDCP SDU discard, PDCP re-establishment and data recovery for RLC AM, and / or PDCP PDU duplication. In one example, the services and functions of the SDAP may include mapping between QoS flows and data radio bearers. In one example, the services and functions of the SDAP may include mapping Quality of Service Indicators (QFI) in DL packets and UL packets. In one example, the protocol entities of the SDAP may be configured for individual PDU sessions.

[0012] Figure 2B shows an exemplary control plane protocol stack, where the PDCP (e.g., 233 and 242), RLC (e.g., 234 and 243), and MAC (e.g., 235 and 244) sublayers, as well as the PHY (e.g., 236 and 245) layer, can be terminated at a radio device (e.g., 110) and a gNB (e.g., 120) on the network side, and can perform the services and functions described above. In one example, the RRC (e.g., 232 and 241) may be terminated at the radio device and the gNB on the network side. In one example, RRC services and functions may include broadcasting system information about the AS and NAS, paging initiated by 5GC or RAN, establishing, maintaining, and releasing RRC connections between the UE and RAN, security functions including key management, establishment, configuration, maintenance, and release of signaling radio bearers (SRBs) and data radio bearers (DRBs), mobility functions, QoS management functions, UE measurement reporting and control of that reporting, detection and recovery from radio link failures, and / or forwarding NAS messages from / to / from the UE to the NAS. In one example, NAS control protocols (e.g., 231 and 251) may be terminated at the radio device and an AMF on the network side (e.g., 130), and can perform functions such as mobility management between the UE and the AMF for 3GPP and non-3GPP access, and session management between the UE and the SMF for 3GPP and non-3GPP access.

[0013] In one example, a base station can configure multiple logical channels for a radio device. Logical channels within the multiple logical channels can correspond to radio bearers, which can be associated with QoS requirements. In one example, a base station can configure a logical channel mapped to one or more TTI / numerology within a multiple TTI / numerology. A radio device can receive downlink control information (DCI) via a physical downlink control channel (PDCCH) indicating uplink authorization. In one example, uplink authorization may be for a first TTI / numerology and may indicate uplink resources for the transmission of a transport block. The base station can configure each logical channel within a multiple logical channels, each having one or more parameters used by a logical channel prioritization procedure at the MAC layer of the radio device. These one or more parameters may include priority, preferred bitrate, etc. Each logical channel within the multiple logical channels can correspond to one or more buffers containing data associated with that logical channel. A logical channel prioritization procedure can assign uplink resources to multiple logical channels and / or one or more first logical channels within one or more MAC control elements (CEs). These one or more first logical channels can be mapped to a first TTI / numerology. The MAC layer in a wireless device can multiplex one or more MAC CEs and / or one or more MAC SDUs (e.g., logical channels) within a MAC PDU (e.g., a transport block). In one example, a MAC PDU may contain a MAC header containing multiple MAC subheaders. MAC subheaders within multiple MAC subheaders can correspond to one or more MAC CEs and / or MAC CEs or MAC SUDs (logical channels) within one or more MAC SDUs. In one example, a MAC CE or logical channel may be configured using a Logical Channel Identifier (LCID). In one example, the LCID for a logical channel or MAC CE may be fixed / preconfigured.In one example, an LCID for a logical channel or MAC CE may be configured by the base station for a radio device. A MAC subheader corresponding to a MAC CE or MAC SDU may include an LCID associated with the MAC CE or MAC SDU.

[0014] In one example, a base station can activate and / or deactivate and / or affect one or more processes in a radio device by using one or more MAC commands (for example, the setting of one or more parameters in one or more processes causes one or more timers in one or more processes to start and / or stop). This one or more MAC commands may include one or more MAC control elements. In one example, one or more processes may include activating and / or deactivating PDCP packet replication for one or more radio bearers. The base station can transmit a MAC CE containing one or more fields, the values ​​of the fields indicating the activation and / or deactivation of PDCP replication for one or more radio bearers. In one example, one or more processes may include channel state information (CSI) transmission on one or more cells. The base station can transmit one or more MAC CEs indicating the activation and / or deactivation of CSI transmission on one or more cells. In one example, one or more processes may include activating or deactivating one or more secondary cells. In one example, the base station can transmit a MAC CE indicating the activation or deactivation of one or more secondary cells. In one example, a base station may transmit one or more MAC CEs indicating the start and / or termination of one or more intermittent receive (DRX) timers in a radio device. In one example, a base station may transmit one or more MAC CEs indicating one or more timing advance values ​​for one or more timing advance groups (TAGs).

[0015] Figure 3 is a block diagram of base stations (base stations 1, 120A, and base stations 2, 120B) and a radio device 110. The radio device is sometimes referred to as a UE. The base stations are sometimes referred to as NBs, eNBs, gNBs, and / or ng-eNBs. In one example, the radio device and / or base stations can function as relay nodes. Base stations 1, 120A may comprise at least one communication interface 320A (e.g., a wireless modem, antenna, wired modem, and / or similar), at least one processor 321A, and at least one set of program code instructions 323A stored in non-transient memory 322A and executable by at least one processor 321A. The base station 2, 120B may include at least one communication interface 320B, at least one processor 321B, and at least one set of program code instructions 323B stored in non-transient memory 322B and executable by at least one processor 321B.

[0016] A base station can have multiple sectors, for example, 1, 2, 3, 4, or 6 sectors. A base station can have multiple cells, for example, ranging from 1 to 50 or more. Cells can be categorized, for example, as primary cells or secondary cells. In Radio Resource Control (RRC) connection establishment / re-establishment / handover, one serving cell can provide NAS (Non-Access Layer) mobility information (e.g., Tracking Area Identifier (TAI)). In RRC connection re-establishment / handover, one serving cell can provide security input. This cell is sometimes called a primary cell (PCell). Downlink, the carrier corresponding to the PCell may be a DL primary component carrier (PCC), while uplink, the carrier may be a UL PCC. Depending on the capabilities of the radio device, secondary cells (SCells) can be configured to form a set of serving cells together with the PCell. In the downlink, the carrier corresponding to the SCell can be a downlink secondary component carrier (DL SCC), while in the uplink, the carrier can be an uplink secondary component carrier (UL SCC). An SCell may or may not have an uplink carrier.

[0017] A cell containing a downlink carrier and an optional uplink carrier may be assigned a physical cell ID and a cell index. A carrier (downlink or uplink) may belong to a single cell. The cell ID or cell index may also identify the downlink carrier or uplink carrier of a cell (as it is used in that context). In this disclosure, the cell ID may also be referred to as the carrier ID, and the cell index may also be referred to as the carrier index. In one embodiment, a physical cell ID or cell index may be assigned to a cell. The cell ID may be determined using a synchronization signal transmitted over the downlink carrier. The cell index may be determined using an RRC message. For example, if this disclosure refers to a first physical cell ID for a first downlink carrier, this disclosure may mean that the first physical cell ID is for a cell containing the first downlink carrier. The same concept may apply, for example, to carrier activation. If this disclosure indicates that a first carrier is activated, this specification may similarly mean that the cell containing the first carrier is activated.

[0018] A base station can transmit one or more messages (e.g., RRC messages) containing multiple configuration parameters for one or more cells to a radio device. One or more cells may include at least one primary cell and at least one secondary cell. In one example, the RRC message may be broadcast or unicast to the radio device. In one example, the configuration parameters may include common parameters and specific parameters.

[0019] The services and / or functions of the RRC sublayer may include broadcasting system information relating to the AS and NAS, paging initiated by 5GC and / or NG-RAN, establishing, maintaining, and / or releasing RRC connections between radio devices and NG-RAN, which may include at least one of adding, modifying, and releasing carrier aggregation, or releasing dual connections within NR or between E-UTRA and NR. The services and / or functions of the RRC sublayer may further include at least one security function, including key management, establishing, configuring, maintaining, and / or releasing signaling radio bearers (SRBs) and / or data radio bearers (DRBs), mobility functions, which may include at least one of handover (e.g., within NR mobility or between RATs) and context transfer, or radio device cell selection and reselection, as well as control of cell selection and reselection. The services and / or functions of the RRC sublayer may further include at least one of the following: QoS management functions, wireless device measurement configuration / reporting, wireless link failure detection and / or recovery from there, or NAS message forwarding to / from core network entities (e.g., AMF, Mobility Management Entity (MME)).

[0020] The RRC sublayer can support the RRC_Idle, RRC_Inactive, and / or RRC_Connected states for wireless devices. In the RRC_Idle state, a wireless device can perform at least one of the following: Public Land Mobile Network (PLMN) selection, reception of broadcasted system information, cell selection / reselection, monitoring / reception of paging for mobile termination data initiated by 5GC, paging for a mobile termination data area managed by 5GC, or DRX for CN paging configured via NAS. In the RRC_Inactive state, a wireless device can perform at least one of the following: reception of broadcasted system information, cell selection / reselection, monitoring / reception of RAN / CN paging initiated by NG-RAN / 5GC, RAN-based notification area (RNA) managed by NG-RAN, or DRX for RAN / CN paging configured by NG-RAN / NAS. In the RRC_Idle state of a radio device, the base station (e.g., NG-RAN) can maintain a 5GC-NG-RAN connection (both C / U-plane) to the radio device and / or store the UE AS context for the radio device. In the RRC_Connected state of a radio device, the base station (e.g., NG-RAN) can perform at least one of the following: establish a 5GC-NG-RAN connection (both C / U-plane) to the radio device, store the UE AS context for the radio device, transmit / receive unicast data to / from the radio device, or perform network-controlled mobility based on measurements received from the radio device. In the RRC_Connected state of a radio device, the NG-RAN can know the cell to which the radio device belongs.

[0021] System information (SI) can be divided into minimum SI and other SI. Minimum SI can be broadcast periodically. Minimum SI can include basic information required for initial access, and information for periodically obtaining any other SI broadcasts, or information prepared on request, i.e., scheduling information. Other SI can be broadcast or configured in a dedicated format and can be triggered by requests from either the network or wireless devices. Minimum SI can be transmitted over two different downlink channels using different messages (e.g., MasterInformationBlock and SystemInformationBlockType1). Other SI can be transmitted over SystemInformationBlockType2. For wireless devices in the RRC_Connected state, dedicated RRC signaling can be used for requesting and delivering other SI. For wireless devices in the RRC_Idle state and / or RRC_Inactive state, requests can trigger a random access procedure.

[0022] A wireless device can report its wireless access capability information, which may be static. A base station can request information on the extent of the capability that a wireless device reports based on bandwidth information. Where permitted by the network, a wireless device can send a temporary capability limitation request to inform the base station that the availability of some capability is limited (e.g., due to hardware sharing, interference, or overheating). The base station can acknowledge or reject the request. Temporary capability limitations may be transparent to the 5GC (e.g., static capability may be stored in the 5GC).

[0023] When a CA is configured, a wireless device can have an RRC connection to the network. In the RRC connection establishment / re-establishment / handover procedure, one serving cell may provide NAS mobility information, and in RRC connection re-establishment / handover, one serving cell may provide security input. This cell is sometimes called a PCell. Depending on the capabilities of the wireless device, SCells may be configured to form a set of serving cells together with PCells. The set of serving cells configured for a wireless device may include one PCell and one or more SCells.

[0024] SCell reconfiguration, addition, and deletion can be performed by the RRC. During an NR handover, the RRC can also add, remove, or reconfigure SCells for use with a target PCell. When adding a new SCell, all necessary system information for the SCell can be transmitted using dedicated RRC signaling; that is, while in connected mode, the radio device does not need to directly obtain broadcasted system information from the SCell.

[0025] The purpose of the RRC Connection Reconfiguration procedure may be to modify an RRC connection (e.g., establish, modify, and / or release an RB, perform a handover, set up, modify, and / or release measurements, add, modify, and / or release SCells and cell groups). As part of the RRC Connection Reconfiguration procedure, NAS-specific information can be transferred from the network to the wireless device. The RRCConnectionReconfiguration message may be a command to modify an RRC connection. It can convey information for measurement configuration, mobility control, and wireless resource configuration (e.g., primary configuration and physical channel configuration of RBs and MACs), including any associated dedicated NAS information and security configuration. If the received RRC Connection Reconfiguration message contains sCellToReleaseList, the wireless device can perform SCell release. If the received RRC Connection Reconfiguration message contains sCellToAddModList, the wireless device can perform SCell addition or modification.

[0026] The RRC connection establishment (or re-establishment, restart) procedure can be the process of establishing (or re-establishing, restarting) an RRC connection, and the RRC connection establishment procedure can include SRB1 establishment. The RRC connection establishment procedure can be used to transfer initial NAS-specific information / messages from a wireless device to E-UTRAN. The RRCConnectionReestablishment message can be used to re-establish SRB1.

[0027] A measurement report procedure may involve transferring measurement results from a wireless device to the NG-RAN. The wireless device can initiate the measurement report procedure after successful security activation. Measurement results can be transmitted using measurement report messages.

[0028] The wireless device 110 may comprise at least one communication interface 310 (e.g., a wireless modem, antenna, and / or similar), at least one processor 314, and at least one set of program code instructions 316 stored in non-transient memory 315 and executable by at least one processor 314. The wireless device 110 may further comprise at least one of the following: at least one speaker / microphone 311, at least one keypad 312, at least one display / touchpad 313, at least one power supply 317, at least one Global Positioning System (GPS) chipset 318, and other peripheral devices 319.

[0029] The processor 314 of the wireless device 110, the processor 321A of base station 1, 120A, and / or the processor 321B of base station 2, 120B may comprise at least one of the following: a general-purpose processor, a digital signal processor (DSP), a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) and / or other programmable logic device, a discrete gate and / or transistor logic circuit, a discrete hardware component, and the like. The processor 314 of the wireless device 110, the processor 321A in base station 1, 120A, and / or the processor 321B in base station 2, 120B may perform at least one of the following: signal coding / processing, data processing, power control, input / output processing, and / or any other functionality that enables the wireless device 110, base station 1, 120A, and / or base station 2, 120B to operate in a wireless environment.

[0030] The processor 314 of the wireless device 110 can be connected to a speaker / microphone 311, a keypad 312, and / or a display / touchpad 313. The processor 314 can receive user input data from the speaker / microphone 311, the keypad 312, and / or the display / touchpad 313, and / or provide user output data to them. The processor 314 in the wireless device 110 can receive power from a power supply 317 and / or be configured to distribute that power to other components in the wireless device 110. The power supply 317 may comprise at least one of one or more dry cell batteries, solar cells, fuel cells, and the like. The processor 314 can be connected to a GPS chipset 318. The GPS chipset 318 may be configured to provide geographic location information for the wireless device 110.

[0031] The processor 314 of the wireless device 110 can be further connected to other peripheral devices 319, which may comprise one or more software and / or hardware modules that provide additional features and / or functionality. For example, the peripheral device 319 may comprise at least one of the following: an accelerometer, a satellite transceiver, a digital camera, a Universal Serial Bus (USB) port, a hands-free headset, a frequency modulation (FM) radio unit, a media player, an internet browser, and the like.

[0032] The communication interface 320A of base station 1, 120A, and / or the communication interface 320B of base station 2, 120B, can be configured to communicate with the communication interface 310 of wireless device 110 via radio links 330A and / or 330B, respectively. In one example, the communication interface 320A of base station 1, 120A can communicate with the communication interface 320B of base station 2, as well as with other RAN and core network nodes.

[0033] Radio link 330A and / or radio link 330B may include at least one of a bidirectional link and / or a directional link. The communication interface 310 of the radio device 110 may be configured to communicate with the communication interface 320A of base station 1, 120A and / or the communication interface 320B of base station 2, 120B. Base stations 1, 120A and radio device 110, and / or base stations 2, 120B and radio device 110 may be configured to transmit and receive transport blocks via radio link 330A and / or radio link 330B, respectively. Radio links 330A and / or radio link 330B may use at least one frequency carrier. According to several different aspects of the embodiment, a transceiver(s) may be used. A transceiver may be a device that includes both a transmitter and a receiver. A transceiver may be used in a device such as a radio device, base station, relay node, and / or equivalent. Exemplary embodiments of the wireless technology implemented in communication interfaces 310, 320A, 320B and wireless links 330A, 330B are illustrated in Figures 4A, 4B, 4C, 4D, 6, 7A, 7B, 8, and related contexts.

[0034] In one example, other nodes in the wireless network (e.g., AMF, UPF, SMF, etc.) may have one or more communication interfaces, one or more processors, and memory for storing instructions.

[0035] A node (e.g., a radio device, base station, AMF, SMF, UPF, server, switch, antenna, and / or similar) may include one or more processors and memory that stores instructions that, when executed by one or more processors, cause the node to perform a particular process and / or function. An exemplary embodiment may enable single-carrier and / or multi-carrier communication operation. Another exemplary embodiment may include a non-transient, tangible, computer-readable medium containing instructions that can be executed by one or more processors to produce single-carrier and / or multi-carrier communication operation. Yet another exemplary embodiment may include a product comprising a non-transient, tangible, computer-readable, machine-accessible medium having instructions encoded therein for programmable hardware to enable a node to perform single-carrier and / or multi-carrier communication operation. A node may comprise processors, memory, interfaces, and / or similar.

[0036] An interface may comprise at least one of a hardware interface, a firmware interface, or a software interface, and / or a combination thereof. A hardware interface may comprise electronic devices such as connectors, wires, and drivers, amplifiers, and / or similar. A software interface may include code stored in a memory device to implement protocols, protocol layers, communication drivers, device drivers, combinations thereof, and / or similar. A firmware interface may comprise embedded hardware and code stored in a memory device and / or communicating with it, and may implement connectivity, electronic device operation, protocols, protocol layers, communication drivers, device drivers, hardware operation, combinations thereof, and / or similar.

[0037] Figures 4A, 4B, 4C, and 4D are exemplary schematic diagrams of uplink and downlink signal transmissions based on one embodiment of the present disclosure. Figure 4A shows an exemplary uplink transmitter for at least one physical channel. A baseband signal representing a physical uplink shared channel can perform one or more functions. These one or more functions may include at least one of the following: scrambling, modulating scrambled bits to generate complex-valued symbols, mapping complex-valued modulated symbols onto one or more transmission layers, convert precoding to generate complex-valued symbols, precoding complex-valued symbols, mapping precoded complex-valued symbols to resource elements, generating complex-valued time-domain single-carrier frequency division multiple access (SC-FDMA) or CP-OFDM signals to antenna ports, and / or similar. In one example, if convert precoding is enabled, an SC-FDMA signal for uplink transmission may be generated. In one example, if convert precoding is not enabled, a CP-OFDM signal for uplink transmission may be generated by Figure 4A. These features are illustrated as examples, and it is assumed that other mechanisms may be implemented in various embodiments.

[0038] An exemplary structure for the modulation and upconversion of complex-valued SC-FDMA or CP-OFDM baseband signals and / or complex-valued physical random access channel (PRACH) baseband signals to the carrier frequency of an antenna port is shown in Figure 4B. Filtering can be used before transmission.

[0039] An exemplary structure for downlink transmission is shown in Figure 4C. The baseband signal representing the downlink physical channel can perform one or more functions. These one or more functions may include scrambling the encoded bits in the codeword to be transmitted over the physical channel, modulating the scrambled bits to generate a complex-valued modulation symbol, mapping the complex-valued modulation symbol to one or more transmission layers, precoding the complex-valued modulation symbol on each layer for transmission over the antenna port, mapping the complex-valued modulation symbol to resource elements at the antenna port, generating a complex-valued time-domain OFDM signal for each antenna port, and / or similar. These functions are illustrated as examples, and it is assumed that other mechanisms may be implemented in various embodiments.

[0040] In one example, a gNB can transmit a first symbol and a second symbol on an antenna port to a wireless device. This wireless device can infer the channel for transmitting the second symbol on the antenna port (e.g., fading gain, multipath delay, etc.) from the channel for transmitting the first symbol on the antenna port. In one example, the first and second antenna ports can be located in approximately the same place if one or more large-scale characteristics of the channel through which the first symbol on the first antenna port is transmitted can be inferred from the channel through which the second symbol on the second antenna port is transmitted. One or more large-scale characteristics may include at least one of delay spread, Doppler spread, Doppler shift, mean gain, mean delay, and / or spatial receive (Rx) parameters.

[0041] Figure 4D shows exemplary modulation and upconversion of a complex-valued OFDM baseband signal from an antenna port to the carrier frequency. Filtering can be used before transmission.

[0042] Figure 5A is a schematic diagram of an exemplary uplink channel mapping and exemplary uplink physical signals. Figure 5B is a schematic diagram of an exemplary downlink channel mapping and downlink physical signals. In one example, the physical layer may provide one or more information transfer services to the MAC and / or one or more higher layers. For example, the physical layer may provide one or more information transfer services to the MAC over one or more transport channels. Information transfer services may indicate how and with what characteristic data is transferred across the radio interface.

[0043] In exemplary embodiments, a wireless network may include one or more downlink and / or uplink transport channels. For example, the schematic diagram in Figure 5A shows an exemplary uplink transport channel including an uplink shared channel (UL-SCH) 501 and a random access channel (RACH) 502. The schematic diagram in Figure 5B shows an exemplary downlink transport channel including a downlink shared channel (DL-SCH) 511, a paging channel (PCH) 512, and a broadcast channel (BCH) 513. Transport channels can be mapped to one or more corresponding physical channels. For example, UL-SCH 501 can be mapped to a physical uplink shared channel (PUSCH) 503. RACH 502 can be mapped to PRACH 505. DL-SCH 511 and PCH 512 can be mapped to a physical downlink shared channel (PDSCH) 514. BCH 513 can be mapped to a physical broadcast channel (PBCH) 516.

[0044] There may be one or more physical channels that do not have a corresponding transport channel. These one or more physical channels can be used for uplink control information (UCI) 509 and / or downlink control information (DCI) 517. For example, a physical uplink control channel (PUCCH) 504 can carry UCI 509 from the UE to the base station. For example, a physical downlink control channel (PDCCH) 515 can carry DCI 517 from the base station to the UE. The NR can support UCI 509 multiplexing in PUSCH 503 if the UCI 509 and PUSCH 503 transmissions can at least partially coincide within the slot. UCI 509 may include at least one of CSI, acknowledgment (ACK) / negative acknowledgment (NACK), and / or scheduling requests. DCI 517 on PDCCH 515 may indicate at least one of the following: one or more downlink assignments and / or one or more uplink scheduling permissions.

[0045] On the uplink, the UE can transmit one or more reference signals (RS) to the base station. For example, one or more RS could be at least one of demodulation-RS (DM-RS) 506, phase tracking-RS (PT-RS) 507, and / or sounding RS (SRS) 508. On the downlink, the base station can transmit one or more RS to the UE (e.g., unicast, multicast, and / or broadcast). For example, one or more RS could be at least one of primary synchronization signal (PSS) / secondary synchronization signal (SSS) 521, CSI-RS 522, DM-RS 523, and / or PT-RS 524.

[0046] In one example, the UE may transmit one or more uplink DM-RS506 to the base station for channel estimation, for example, for coherent demodulation of one or more uplink physical channels (e.g., PUSCH503 and / or PUCCH504). For example, the UE may transmit at least one uplink DM-RS506 to the base station using PUSCH503 and / or PUCCH504, and at least one uplink DM-RS506 may extend to the same frequency range as the corresponding physical channel. In one example, the base station may configure a UE having one or more uplink DM-RS configurations. At least one DM-RS configuration may support a preceding DM-RS pattern. A preceding DM-RS may be mapped onto one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more additional uplink DM-RS may be configured to transmit on one or more symbols of PUSCH and / or PUCCH. A base station can quasi-statistically configure an UE using the maximum number of preceding DM-RS symbols for PUSCH and / or PUCCH. For example, an UE can schedule single-symbol DM-RS and / or dual-symbol DM-RS based on the maximum number of preceding DM-RS symbols, and a base station can configure an UE using one or more additional uplink DM-RS for PUSCH and / or PUCCH. A new radio network may support a common DM-RS structure for DL ​​and UL, for example, at least in the case of CP-OFDM, where the DM-RS locations, DM-RS patterns, and / or scrambling sequences may be the same or different.

[0047] In one example, the presence or absence of an uplink PT-RS507 may depend on the RRC configuration. For example, the presence of an uplink PT-RS can be configured specifically for the UE. For example, the presence and / or pattern of uplink PT-RS507s in a scheduled resource can be configured specifically for the UE by a combination of associations with one or more parameters used for RRC signaling and / or other purposes that may be indicated by DCI (e.g., modulation and coding scheme (MCS)). The dynamic presence of an uplink PT-RS507, if configured, can be associated with one or more DCI parameters, including at least the MCS. A wireless network can support multiple uplink PT-RS densities defined in the time / frequency domain. The frequency domain density, if present, can be associated with at least one configuration of the scheduled bandwidth. A UE may assume the same precoding for DMRS ports and PT-RS ports. The number of PT-RS ports may be less than the number of DMRS ports in a scheduled resource. For example, an uplink PT-RS507 may be limited to a scheduled time / frequency duration for the UE.

[0048] In one example, a UE can transmit an SRS508 to a base station for channel state estimation that supports uplink channel-dependent scheduling and / or link adaptation. For example, an SRS508 transmitted by a UE can enable the base station to estimate uplink channel states at one or more different frequencies. The base station scheduler can use the uplink channel states to allocate one or more good quality resource blocks from the UE for uplink push transmission. The base station can quasi-statistically configure a UE using one or more SRS resource sets. In the case of an SRS resource set, the base station can configure a UE using one or more SRS resources. The applicability of an SRS resource set can be configured by higher-layer (e.g., RRC) parameters. For example, if higher-layer parameters indicate beam management, SRS resources in each of one or more SRS resource sets can be transmitted at once. A UE can transmit one or more SRS resources simultaneously within different SRS resource sets. Newer radio networks can support aperiodic, periodic, and / or semi-persistent SRS transmissions. A UE can transmit SRS resources based on one or more trigger types, which may include higher-layer signaling (e.g., RRC) and / or one or more DCI formats (e.g., using at least one DCI format, the UE can select at least one of one or more configured sets of SRS resources). SRS trigger type 0 may refer to an SRS triggered based on higher-layer signaling. SRS trigger type 1 may refer to an SRS triggered based on one or more DCI formats. In one example, if PUSCH503 and SRS508 are transmitted in the same slot, the UE can be configured to transmit SRS508 after PUSCH503 and the corresponding uplink DM-RS506.

[0049] In one example, a base station can quasi-statistically configure a UE using one or more SRS configuration parameters that indicate at least one of the following: the SRS resource configuration identifier, the number of SRS ports, the time-domain behavior of the SRS resource configuration (e.g., the display of periodic, semi-persistent, or aperiodic SRS), the slot (mini-slot, and / or subframe) level periodicity and / or offset for periodic and / or aperiodic SRS resources, the number of OFDM symbols in the SRS resource, the OFDM symbol start of the SRS resource, the SRS bandwidth, the frequency-hopping bandwidth, the cyclic shift, and / or the SRS sequence ID.

[0050] In one example, in a given time domain, an SS / PBCH block may contain one or more OFDM symbols (e.g., four OFDM symbols numbered sequentially from 0 to 3). An SS / PBCH block may include PSS / SSS521 and PBCH516. In one example, in the frequency domain, an SS / PBCH block may contain one or more continuous subcarriers (e.g., 240 continuous subcarriers with subcarriers numbered sequentially from 0 to 239). For example, PSS / SSS521 may occupy one OFDM symbol and 127 subcarriers. For example, PBCH516 may span three OFDM symbols and 240 subcarriers. The UE can assume that one or more SS / PBCH blocks transmitted using the same block index may be located in approximately the same position with respect to, for example, Doppler spread, Doppler shift, mean gain, mean delay, and spatial Rx parameters. The UE cannot assume roughly the same placement for other SS / PBCH block transmissions. The periodicity of the SS / PBCH block can be configured by the radio network (e.g., by RRC signaling), and the one or more time locations in which the SS / PBCH block can be transmitted can be determined by the subcarrier interval. In one example, unless the radio network is configured to assume a different subcarrier interval, the UE can assume a bandwidth-specific subcarrier interval for the SS / PBCH block.

[0051] In one example, a UE can obtain channel status information using downlink CSI-RS522. A wireless network can support periodic, aperiodic, and / or semi-persistent transmission of downlink CSI-RS522. For example, a base station can quasi-statistically configure and / or reconfigure a UE using periodic transmission of downlink CSI-RS522. Configured CSI-RS resources can be activated and / or deactivated. In the case of semi-persistent transmission, the activation and / or deactivation of CSI-RS resources can be dynamically triggered. In one example, a CSI-RS configuration may include one or more parameters indicating at least the number of antenna ports. For example, a base station can configure a UE with 32 ports. A base station can quasi-statistically configure a UE with one or more sets of CSI-RS resources. One or more CSI-RS resources can be assigned to one or more UEs from one or more sets of CSI-RS resources. For example, a base station can quasi-statistically configure one or more parameters that indicate CSI-RS resource mapping, such as the time-domain location of one or more CSI-RS resources, the bandwidth of the CSI-RS resources, and / or periodicity. In one example, if the downlink CSI-RS522 and the core set are located in approximately the same spatial location, the UE can be configured to use the same OFDM symbols for the downlink CSI-RS522 and the control resource set (core set), and the resource elements associated with the downlink CSI-RS522 are outside the PRB configured for the core set. In another example, if the downlink CSI-RS522 and the SSB / PBCH are located in approximately the same spatial location, the UE can be configured to use the same OFDM symbols for the downlink CSI-RS522 and the SSB / PBCH, and the resource elements associated with the downlink CSI-RS522 are outside the PRB configured for the SSB / PBCH.

[0052] In one example, the UE may transmit one or more downlink DM-RS523s to the base station for channel estimation, for example, to perform coherent demodulation of one or more downlink physical channels (e.g., PDSCH514). For example, a wireless network may support one or more variable and / or configurable DM-RS patterns for data demodulation. At least one downlink DM-RS configuration may support a leading DM-RS pattern. A leading DM-RS can be mapped onto one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station may quasi-statistically configure the UE using the maximum number of leading DM-RS symbols for the PDSCH514. For example, a DM-RS configuration may support one or more DM-RS ports. For example, in the case of single-user MIMO, a DM-RS configuration may support at least eight orthogonal downlink DM-RS ports. For example, in the case of multi-user MIMO, a DM-RS configuration may support twelve orthogonal downlink DM-RS ports. A wireless network may support a common DM-RS structure for DL ​​and UL, for example, in the case of CP-OFDM, where the DM-RS positions, DM-RS patterns, and / or scrambling sequences may be the same or different.

[0053] In one example, the presence or absence of a downlink PT-RS524 may depend on the RRC configuration. For example, the presence of a downlink PT-RS524 can be configured specifically for the UE. For example, the presence and / or pattern of downlink PT-RS524s in a scheduled resource can be configured specifically for the UE by a combination of association with RRC signaling and / or one or more parameters used for other purposes (e.g., MCS) that may be indicated by DCI. The dynamic presence of a downlink PT-RS524, if configured, can be associated with one or more DCI parameters, including at least MCS. A wireless network can support multiple PT-RS densities defined in the time / frequency domain. The frequency domain density, if present, can be associated with at least one configuration of the scheduled bandwidth. A UE may assume the same precoding for DMRS ports and PT-RS ports. The number of PT-RS ports may be less than the number of DMRS ports in a scheduled resource. For example, downlink PT-RS524s may be limited to the scheduled time / frequency duration for the UE.

[0054] Figure 6 is a schematic diagram illustrating exemplary carrier transmission and reception times based on one embodiment of the present disclosure. A multi-carrier OFDM communication system can include one or more carriers, for example, 1 to 32 carriers in the case of carrier aggregation, or 1 to 64 carriers in the case of dual connection. Different radio frame structures can be supported (e.g., for FDD mechanisms and TDD duplex mechanisms). Figure 6 shows exemplary frame timing. Downlink and uplink transmissions can be organized within a radio frame 601. In this example, the radio frame duration is 10 milliseconds. In this example, the 10-millisecond radio frame 601 can be divided into 10 equally sized subframes 602, each with a duration of 1 millisecond. A subframe(s) can include one or more slots (e.g., slots 603 and 605), depending on the subcarrier spacing and / or CP length. For example, subframes with subcarrier intervals of 15kHz, 30kHz, 60kHz, 120kHz, 240kHz, and 480kHz can contain 1, 2, 4, 8, 16, and 32 slots, respectively. In Figure 6, a subframe can be divided into two equally sized slots 603 with a duration of 0.5 milliseconds. For example, 10 subframes may be available for downlink transmission, and 10 subframes may be available for uplink transmission with a time interval of 10 milliseconds. Uplink and downlink transmissions can be separated in the frequency domain. A slot(s) can contain multiple OFDM symbols 604. The number of OFDM symbols 604 in a slot 605 may depend on the cyclic prefix length. For example, one slot may contain 14 OFDM symbols with the same subcarrier interval up to 480kHz, with a normal CP. Another slot may contain 12 OFDM symbols with the same subcarrier interval of 60kHz, with an extended CP. A single slot may include a downlink, an uplink, or a downlink section and an uplink section, and / or similar.

[0055] Figure 7A is a schematic diagram illustrating an exemplary OFDM subcarrier set based on one aspect of an embodiment of the present disclosure. In this example, the gNB can communicate with a radio device having a carrier having an exemplary channel bandwidth 700. The arrows in the schematic diagram may represent subcarriers in a multicarrier OFDM system. The OFDM system may use techniques such as OFDM technology, SC-FDMA technology, and / or similar. In one example, arrow 701 indicates a subcarrier that transmits an information symbol. In one example, the subcarrier spacing 702 between two adjacent subcarriers in the carrier may be any one of 15KHz, 30KHz, 60KHz, 120KHz, 240KHz, etc. In one example, different subcarrier spacings may correspond to different transmission numerologies. In one example, the transmission numerology may include at least a numerology index, a subcarrier spacing value, and a cyclic prefix (CP) type. In one example, a gNB can be transmitted to / received from a UE on a number of subcarriers 703 within the carrier. In one example, the bandwidth occupied by the number of subcarriers 703 (transmission bandwidth) may be smaller than the carrier's channel bandwidth 700 due to the protection bandwidths 704 and 705. In one example, the protection bandwidths 704 and 705 can be used to reduce interference to / from one or more neighboring carriers. The number of subcarriers (transmission bandwidth) within a carrier may depend on the carrier's channel bandwidth and subcarrier spacing. For example, for a carrier with a 20 MHz channel bandwidth and a 15 kHz subcarrier spacing, the transmission bandwidth may be 1024 subcarriers.

[0056] In one example, a gNB and a wireless device can communicate with multiple CCs when configured with CA. In one example, different component carriers may have different bandwidths and / or subcarrier spacings, provided CA is supported. In one example, a gNB can transmit a first type of service to a UE on a first component carrier. A gNB can transmit a second type of service to a UE on a second component carrier. Different types of services may have different service requirements (e.g., data rate, latency, reliability), which may be better suited to transmission over different component carriers having different subcarrier spacings and / or bandwidths. Figure 7B shows an exemplary embodiment. A first component carrier may include a first number of subcarriers 706 having a first subcarrier spacing 709. A second component carrier may include a second number of subcarriers 707 having a second subcarrier spacing 710. A third component carrier may include a third number of subcarriers 708 having a third subcarrier spacing 711. In a multi-carrier OFDM communication system, the carriers may be continuous carriers, discontinuous carriers, or a combination of both continuous and discontinuous carriers.

[0057] Figure 8 is a schematic diagram illustrating an OFDM radio resource based on one embodiment of the present disclosure. In one example, the carrier may have a transmission bandwidth 801. In one example, the resource grid may be in a structure in the frequency domain 802 and the time domain 803. In one example, the resource grid may include a first number of OFDM symbols and a second number of resource blocks in a subframe, starting with a common resource block indicated by upper-layer signaling (e.g., RRC signaling) for the transmission numerology and the carrier. In one example, in the resource grid, resource units identified by subcarrier indexes and symbol indices may be resource elements 805. In one example, a subframe may include a first number of OFDM symbols 807 depending on the numerology associated with the carrier. For example, if the subcarrier spacing of the carrier numerology is 15 kHz, the subframe may have 14 OFDM symbols for the carrier. If the subcarrier spacing of the numerology is 30 kHz, a subframe can have 28 OFDM symbols. If the subcarrier spacing of the numerology is 60 kHz, a subframe can have 56 OFDM symbols, and so on. In one example, the second number of resource blocks included in the carrier's resource grid may depend on the carrier's bandwidth and numerology.

[0058] As shown in Figure 8, resource block 806 can contain 12 subcarriers. In one example, multiple resource blocks can be grouped into a resource block group (RBG) 804. In one example, the size of the RBG may depend on at least one of the following: an RRC message indicating the RBG size configuration, the size of the carrier bandwidth, or the bandwidth portion of the carrier. In one example, a carrier can contain multiple bandwidth portions. The first bandwidth portion of the carrier may have a different frequency position and / or bandwidth than the second bandwidth portion of the carrier.

[0059] In one example, a gNB can transmit downlink control information, including downlink or uplink resource block allocation, to a radio device. The base station can transmit or receive scheduled and transmitted data packets (e.g., transport blocks) to or from a radio device via one or more resource blocks and one or more slots, according to parameters in the downlink control information and / or RRC messages. In one example, a start symbol for the first slot of one or more slots can be shown to the radio device. In one example, a gNB can transmit or receive scheduled data packets for one or more RBGs and one or more slots to or from a radio device.

[0060] In one example, a gNB can transmit downlink control information, including downlink assignments, to a radio device via one or more PDCCHs. Downlink assignments may include parameters indicating at least the modulation and coding format, resource assignments, and / or HARQ information relating to the DL-SCH. In one example, resource assignments may include parameters for resource block assignments and / or slot assignments. In one example, a gNB can dynamically assign resources to a radio device via a Cell Radio Network Temporary Identifier (C-RNTI) on one or more PDCCHs. A radio device can monitor one or more PDCCHs to find possible assignments when downlink reception is available for the radio device. Upon successful detection of one or more PDCCHs, the radio device can receive one or more downlink data packages on one or more PDSCHs scheduled by the one or more PDCCHs.

[0061] In one example, a gNB may allocate a configuration scheduling (CS) resource for downlink transmission to a wireless device. The gNB may transmit one or more RRC messages indicating the periodicity of CS authorization. The gNB may transmit a DCI via a PDCCH addressed to a configuration scheduling-RNTI (CS-RNTI) that activates the CS resource. The DCI may include parameters indicating that the downlink authorization is a CS authorization. A CS authorization can be implicitly reused until terminated, according to the periodicity defined by one or more RRC messages.

[0062] In one example, a gNB can transmit downlink control information, including uplink authorization, to a radio device via one or more PDCCHs. Uplink authorization may include at least parameters indicating the modulation and coding format, resource allocation, and / or HARQ information regarding the UL-SCH. In one example, resource allocation may include parameters for resource block allocation and / or slot allocation. In one example, a gNB can dynamically allocate resources to a radio device via C-RNTIs on one or more PDCCHs. The radio device can monitor one or more PDCCHs to find possible resource allocations. If the radio device successfully detects one or more PDCCHs, it can transmit one or more uplink data packages via one or more PUSCHs scheduled by the one or more PDCCHs.

[0063] In one example, a gNB may allocate a CS resource for uplink data transmission to a wireless device. The gNB may transmit one or more RRC messages indicating the periodicity of CS authorization. The gNB may transmit a DCI via a PDCCH addressed to the CS-RNTI that activates the CS resource. The DCI may include parameters indicating that the uplink authorization is a CS authorization. The CS authorization can be implicitly reused until terminated, according to the periodicity defined by one or more RRC messages.

[0064] In one example, a base station can transmit DCI / control signaling via PDCCH. DCI can take one of several formats. DCI may include downlink and / or uplink scheduling information (e.g., resource allocation information, HARQ-related parameters, MCS), CSI requests (e.g., aperiodic CQI reports), SRS requests, uplink power control commands for one or more cells, and one or more timing information (e.g., TB transmission / reception timing, HARQ feedback timing, etc.). In one example, DCI may indicate uplink permission including transmission parameters for one or more transport blocks. In one example, DCI may indicate downlink allocation indicating parameters for receiving one or more transport blocks. In one example, DCI can be used by a base station to initiate contention-free random access in a radio device. In one example, a base station can transmit DCI including a slot format indicator (SFI) that indicates the slot format. In one example, a base station may transmit a DCI that includes a preemption indication notifying PRB(or PRB) and / or OFDM(or OFDM) symbols(or OFDM) where the UE can assume that the transmission for the UE is not intended. In one example, a base station may transmit a DCI for group power control of PUCCH or PUSCH or SRS. In one example, a DCI may correspond to an RNTI. In one example, a radio device may acquire an RNTI in response to completing an initial access (e.g., C-RNTI). In one example, a base station may configure RNTIs for radios (e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI). In one example, a radio device may calculate an RNTI (e.g., a radio device may calculate an RA-RNTI based on the resources used for transmitting the preamble).In one example, the RNTI may have a pre-configured value (e.g., P-RNTI or SI-RNTI). In one example, a wireless device may monitor a group common search space, which is used by the base station to transmit a DCI intended for a group of UEs. In one example, the group common DCI may correspond to an RNTI configured in common for a group of UEs. In one example, a wireless device may monitor a UE-specific search space. In one example, the UE-specific DCI may correspond to an RNTI configured for the wireless device.

[0065] NR systems can support single-beam and / or multi-beam operation. In multi-beam operation, the base station can perform a downlink beam sweep to provide coverage of the common control channel and / or downlink SS blocks, which may include at least PSS, SSS, and / or PBCH. A radio device can use one or more RSs to measure the quality of a beampair link. One or more SS blocks, or one or more CSI-RS resources associated with a CSI-RS resource index (CRI), or one or more DM-RSs of a PBCH can be used as RSs to measure the quality of a beampair link. The quality of a beampair link can be defined as a reference signal received power (RSRP) value, or a reference signal received quality (RSRQ) value, and / or a CSI value measured on the RS resource. The base station can indicate whether the RS resource used to measure the quality of the beampair link is located in approximately the same location as the DM-RS of the control channel (QCLed). The RS resources and DM-RS of the control channel may be referred to as QCL-ed when the channel characteristics from transmission on RS to the wireless device, and from transmission on the control channel to the wireless device, are similar or identical under configured criteria. In multibeam operation, the wireless device can perform uplink beam sweep to access the cell.

[0066] In one example, a radio device can be configured to simultaneously monitor PDCCHs on one or more beampair links, depending on the capabilities of the radio device. This can improve robustness against beampair link blocking. A base station can configure a radio device to monitor PDCCHs on one or more beampair links for different PDCCH OFDM symbols by transmitting one or more messages. For example, a base station can transmit upper-layer signaling (e.g., RRC signaling) or MAC CEs containing parameters related to the radio device's Rx beam configuration for monitoring PDCCHs on one or more beampair links. A base station can transmit a representation of spatial QCL assumptions between DL RS antenna ports (e.g., cell-specific CSI-RS, radio device-specific CSI-RS, SS block, or PBCH with or without DM-RS for PBCH) and DL RS antenna ports (or multiple ports) for demodulation of the DL control channel. Signaling for beam indication of PDCCH may be MAC CE signaling, or RRC signaling, or DCI signaling, or specification transparent and / or implicit methods, or a combination of these signaling methods.

[0067] When receiving a unicast DL data channel, the base station will use the DL data channel's DL Spatial QCL parameters can be indicated between RS antenna ports(s) and DM-RS antenna ports(s). A base station can transmit a DCI (e.g., Downlink Clear) that includes information indicating RS antenna ports(s). This information can indicate RS antenna ports that can be QCL'd using DM-RS antenna ports(s). Different sets of DM-RS antenna ports(s) on a DL data channel can be indicated as QCL using different sets of RS antenna ports(s).

[0068] Figure 9A shows an example of beam sweeping in a DL channel. In the RRC_INACTIVE or RRC_IDLE state, the radio device may assume that SS blocks form SS bursts 940 and SS burst sets 950. The SS burst sets 950 may have a predetermined periodicity. For example, in multi-beam operation, the base station 120 can transmit SS blocks that together form SS bursts 940 over multiple beams. One or more SS blocks may be transmitted over a single beam. If multiple SS bursts 940 are transmitted over multiple beams, the SS bursts can together form SS burst sets 950.

[0069] A wireless device can further use CSI-RS in multi-beam operation to estimate the beam quality of the link between the wireless device and the base station. Beams can be associated with CSI-RS. For example, a wireless device can report a beam index, indicated by the CRI of downlink beam selection and associated with the RSRP value of the beam, based on RSRP measurements over CSI-RS. CSI-RS can be transmitted over a CSI-RS resource that includes one or more time-radio resources or frequency-radio resources, at least one of one or more antenna ports. The CSI-RS resource can consist of a cell-specific scheme with common RRC signaling, or a wireless device-specific scheme with dedicated RRC signaling and / or L1 / L2 signaling. Multiple wireless devices covered by a cell can measure cell-specific CSI-RS resources. A dedicated subset of wireless devices covered by a cell can measure wireless device-specific CSI-RS resources.

[0070] CSI-RS resources can be transmitted periodically, using aperiodic transmission, or using multi-shot or semi-persistent transmission. For example, in periodic transmission as shown in Figure 9A, base station 120 can periodically transmit configured CSI-RS resources 940 using periodicity configured in the time domain. In aperiodic transmission, configured CSI-RS resources can be transmitted in dedicated time slots. In multi-shot or semi-persistent transmission, configured CSI-RS resources can be transmitted within a configured period. The beam used for CSI-RS transmission may have a different beamwidth than the beam used for SS block transmission.

[0071] Figure 9B shows an example of a beam management procedure in an exemplary new radio network. A base station 120 and / or radio device 110 can perform downlink L1 / L2 beam management procedures. One or more of the following downlink L1 / L2 beam management procedures may be performed within one or more radio devices 110 and one or more base stations 120. In one example, the P-1 procedure 910 may be used to allow a radio device 110 to measure one or more transmission (Tx) beams associated with a base station 120 to support the selection of a first set of Tx beams associated with the base station 120 and a first set of Rx beams associated with the radio device 110. For beamforming at the base station 120, the base station 120 may sweep different sets of TX beams. For beamforming at the radio device 110, the radio device 110 may sweep different sets of Rx beams. In one example, the P-2 procedure 920 may be used to allow the radio device 110 to measure one or more Tx beams associated with the base station 120, and optionally modify a first set of Tx beams associated with the base station 120. Unlike the P-1 procedure 910, the P-2 procedure 920 may optionally be performed on a smaller set of beams for beam refinement. The P-2 procedure 920 may be a special case of the P-1 procedure 910. In one example, the P-3 procedure 930 may be used to allow the radio device 110 to measure at least one Tx beam associated with the base station 120, and optionally modify a first set of Rx beams associated with the radio device 110.

[0072] The wireless device 110 can transmit one or more beam management reports to the base station 120. In one or more beam management reports, the wireless device 110 may indicate several beam pair quality parameters, including at least one beam identifier, RSRP, and precoding matrix indicator (PMI) / channel quality indicator (CQI) / rank indicator (RI) for a subset of the configured beams. Based on one or more beam management reports, the base station 120 can transmit signals to the wireless device 110 indicating that one or more beam pair links are one or more serving beams. The base station 120 can transmit the PDCCH and PDSCH of the wireless device 110 using one or more serving beams.

[0073] In exemplary embodiments, the new wireless network may support bandwidth adaptation (BA). In one example, the receive and / or transmit bandwidth configured by the UE using BA may not be large. For example, the receive and / or transmit bandwidth may not be as large as the cell bandwidth. The receive and / or transmit bandwidth may be adjustable. For example, the UE may vary the receive and / or transmit bandwidth to conserve power, for example, by reducing it during periods of low activity. For example, the UE may change the position of the receive and / or transmit bandwidth within the frequency domain, for example, to increase scheduling flexibility. For example, the UE may vary the subcarrier spacing to enable different services, for example.

[0074] In exemplary embodiments, a subset of the cell's total bandwidth may be referred to as a bandwidth portion (BWP). A base station can use one or more BWPs to configure a UE and achieve a base station (BA). For example, the base station can indicate to the UE which of the one or more (configured) BWPs is the active BWP.

[0075] FIG. 10 is an exemplary schematic diagram of three BWPs, namely BWP1 (1010 and 1050) having a width of 40 MHz and a subcarrier spacing of 15 kHz, BWP2 (1020 and 1040) having a width of 10 MHz and a subcarrier spacing of 15 kHz, and BWP3 1030 having a width of 20 MHz and a subcarrier spacing of 60 kHz.

[0076] In one example, the UE is configured to operate within one or more BWPs of one cell, and is composed of one or more upper layers (e.g., RRC layer) per cell, a set of one or more BWPs (e.g., up to four BWPs) for reception by the UE (DL BWP set) within the DL bandwidth with at least one parameter DL-BWP per cell, and a set of one or more BWPs (e.g., up to four BWPs) for reception by the UE (UL BWP set) within the UL bandwidth with at least one parameter UL-BWP per cell.

[0077] To enable BA in the PCell, the base station can configure the UE using one or more UL and DL BWP pairs. To enable BA in the SCell (e.g., in the case of CA), the base station can configure the UE using at least one DL BWP (e.g., there may be nothing in the UL).

[0078] In one example, the initial active DL BWP can be defined by at least one of the position and number of consecutive PRBs, subcarrier spacing, or cyclic prefix with respect to the control resource set for at least one common search space. For operation in the PCell, one or more upper layer parameters can indicate at least one initial UL BWP for the random access procedure. If the UE is configured using a secondary carrier in the primary cell, the UE can be configured using the initial BWP for the random access procedure in the secondary carrier.

[0079] In one example, in the case of unpaired spectrum operations, the UE may expect that the center frequency in the case of the DL BWP can be the same as the center frequency in the case of the UL BWP.

[0080] For example, for each DL BWP or UL BWP within one or more sets of DL BWPs or one or more sets of UL BWPs, the base station can quasi-statically configure the UE for the cell using one or more parameters indicating at least one of the following, and those parameters are the subcarrier spacing, cyclic prefix, number of consecutive PRBs, index within one or more sets of DL BWPs and / or one or more sets of UL BWPs, the link between the DL BWP and the UL BWP from the configured set of DL BWPs and UL BWPs, DCI detection for PDSCH reception timing, PDSCH reception for HARQ-ACK transmission timing value, DCI detection for PUSCH transmission timing value, the offset of the first PRB of the bandwidth to the first PRB of the DL bandwidth or UL bandwidth, respectively. [[ID=I6]]

[0081] In one example, for the DL BWP within one or more sets of DL BWPs in the PCell, the base station can configure the UE using one or more control resource sets for at least one type of common search space and / or one UE-specific search space. For example, in the active DL BWP, the base station cannot configure the UE without a common search space on the PCell or on the PSCell.

[0082] If there is a UL BWP within one or more sets of UL BWPs, the base station can configure the UE using one or more resource sets for one or more PUCCH transmissions.

[0083] For example, if the DCI includes a BWP indicator field, the BWP indicator field value may indicate an active DL BWP from a set of DL BWPs configured for one or more DL receptions. If the DCI includes a BWP indicator field, the BWP indicator field value may indicate an active UL BWP from a set of UL BWPs configured for one or more UL transmissions.

[0084] In one example, in the case of PCell, the base station can quasi-statistically configure the UE using the default DL BWP between the configured DL BWPs. If no BWP is provided, the default BWP may be the initial active DL BWP.

[0085] In one example, a base station can configure a UE using a PCell timer value. For example, if the UE detects a DCI indicating an active DL BWP other than the default DL BWP for a paired spectral operation, or if the UE detects a DCI indicating an active DL BWP or UL BWP other than the default DL BWP or UL BWP for an unpaired spectral operation, the UE can start a timer called a BWP stop timer. If the UE does not detect a DCI during the period for a paired or unpaired spectral operation, the UE can increment the timer for a period of a first value (for example, the first value may be 1 millisecond or 0.5 milliseconds). In one example, the timer may expire when the timer has equaled its timer value. When the timer expires, the UE can start an active DL BWP. You can switch from BWP to default DL BWP.

[0086] In one example, a base station can quasi-statistically configure a UE using one or more BWPs. The UE can switch the active BWP from the first BWP to the second BWP in response to receiving a DCI indicating the second BWP as the active BWP, and / or in response to the expiration of a BWP stop timer (e.g., the second BWP may become the default BWP). For example, Figure 10 is an illustrative schematic of three configured BWPs: BWP1 (1010 and 1050), BWP2 (1020 and 1040), and BWP3 (1030). BWP2 (1020 and 1040) may be the default BWP. BWP1 (1010) may be the initial active BWP. In one example, the UE can switch the active BWP from BWP1 1010 to BWP2 1020 in response to the expiration of a BWP stop timer. For example, the UE may switch the active BWP from BWP2 1020 to BWP3 1030 in response to receiving a DCI indicating BWP3 1030 as the active BWP. Switching the active BWP from BWP3 1030 to BWP2 1040, and / or from BWP2 1040 to BWP1 1050 may be in response to receiving a DCI indicating the active BWP and / or in response to the expiration of the BWP stop timer.

[0087] In one example, the UE defaults DL between the configured DL BWP and timer values. When configured for a secondary cell using BWP, the UE procedure in the secondary cell may be the same as that of the primary cell, using the secondary cell's timer value and the secondary cell's default DL BWP.

[0088] In one example, if a base station configures a UE using a first active DL BWP and a first active UL BWP on a secondary cell or carrier, the UE can use the displayed DL BWP and displayed UL BWP on the secondary cell as the respective first active DL BWP and first active UL BWP on the secondary cell or carrier.

[0089] Figures 11A and 11B illustrate packet flows using multi-connectivity (e.g., dual-connectivity, multi-connectivity, tight interworking, and / or similar). Figure 11A is an exemplary schematic diagram of the protocol structure of a radio device 110 (e.g., UE) having CA and / or multi-connectivity, based on one aspect of the embodiment. Figure 11B is an exemplary schematic diagram of the protocol structure of multiple base stations having CA and / or multi-connectivity, based on one aspect of the embodiment. The multiple base stations may include a master node, MN1130 (e.g., master node, master base station, master gNB, master eNB, and / or similar), and secondary nodes, SN1150 (e.g., secondary node, secondary base station, secondary gNB, secondary eNB, and / or similar). The master node 1130 and secondary nodes 1150 can cooperate to communicate with the radio device 110.

[0090] When a multi-connection is configured for a radio device 110, the radio device 110 may support multiple receive / transmit functions with the RRC connected and may be configured to utilize radio resources provided by multiple schedulers of multiple base stations. Multiple base stations may be interconnected via non-ideal or ideal backhaul (e.g., Xn interface, X2 interface, and / or similar). The base stations required for a multi-connection to a particular radio device may perform at least one of two different roles, namely, a base station may function as either a master base station or a secondary base station. In a multi-connection, a radio device may be connected to one master base station and one or more secondary base stations. In one example, a master base station (e.g., MN1130) may provide a master cell group (MCG) to a radio device (e.g., radio device 110) which includes one primary cell and / or one or more secondary cells. A secondary base station (e.g., SN1150) can provide a wireless device (e.g., wireless device 110) with one primary-secondary cell (PSCell) and / or a secondary cell group (SCG) containing one or more secondary cells.

[0091] In a multi-connection, the radio protocol architecture used by the bearer may depend on how the bearer is configured. In one example, three different types of bearer configuration options can be supported: MCG bearer, SCG bearer, and / or split bearer. A radio device may receive / transmit packets of an MCG bearer through one or more cells of an MCG, and / or receive / transmit packets of an SCG bearer through one or more cells of an SCG. A multi-connection can also be described as having at least one bearer configured to use radio resources provided by a secondary base station. A multi-connection may or may not be configured / implemented in some exemplary embodiments.

[0092] In one example, a wireless device (e.g., wireless device 110) receives MCG bearer packets via the SDAP layer (e.g., SDAP1110), PDCP layer (e.g., NR PDCP1111), RLC layer (e.g., MN RLC1114), and MAC layer (e.g., MN MAC1118), a split bearer packet via the SDAP layer (e.g., SDAP1110), PDCP layer (e.g., NR PDCP1112), master or secondary RLC layer (e.g., MN RLC1115, SN RLC1116), and master or secondary MAC layer (e.g., MN MAC1118, SN MAC1119), and / or via the SDAP layer (e.g., SDAP1110), PDCP layer (e.g., NR PDCP1113), RLC layer (e.g., SN RLC1117), and MAC layer (e.g., MN SCG bearer packets can be transmitted and / or received via MAC1119).

[0093] In one example, the master base station (e.g., MN1130) and / or secondary base station (e.g., SN1150) receive MCG bearer packets via the master or secondary node SDAP layer (e.g., SDAP1120, SDAP1140), master or secondary node PDCP layer (e.g., NR PDCP1121, NR PDCP1142), master node RLC layer (e.g., MN RLC1124, MN RLC1125), and master node MAC layer (e.g., MN MAC1128), master or secondary node SDAP layer (e.g., SDAP1120, SDAP1140), master or secondary node PDCP layer (e.g., NR PDCP1122, NR PDCP1143), secondary node RLC layer (e.g., SN RLC1146, SN RLC1147), and secondary node MAC layer (e.g., SN SCG bearer packets can be transmitted / received via MAC1148, master or secondary node SDAP layer (e.g., SDAP1120, SDAP1140), master or secondary node PDCP layer (e.g., NR PDCP1123, NR PDCP1141), master or secondary node RLC layer (e.g., MN RLC1126, SN RLC1144, SN RLC1145, MN RLC1127), and master or secondary node MAC layer (e.g., MN MAC1128, SN MAC1148).

[0094] In a multi-connection, a wireless device can constitute multiple MAC entities: one MAC entity for the master base station (e.g., MN MAC1118) and other MAC entities for secondary base stations (e.g., SN MAC1119). In a multi-connection, the configured set of serving cells for a wireless device may include two subsets: an MCG containing the serving cells of the master base station, and an SCG containing the serving cells of the secondary base stations. In the case of an SCG, one or more of the following configurations may apply: namely, at least one cell of the SCG has a configured UL CC, at least one cell of the SCG called a primary secondary cell (a PSCell, PCell, or possibly PCell of the SCG) is configured with PUCCH resources, and if the SCG is configured, there may be at least one SCG bearer or one split bearer; the RRC connection re-establishment procedure may not be triggered when a physical layer problem or random access problem on the PSCell is detected, or when a number of NR RLC retransmissions arriving associated with the SCG is detected, or when an access problem with the PSCell is detected during SCG addition or SCG modification; UL transmissions toward the cells of the SCG may be stopped; the master base station may be notified by the radio device regarding the SCG failure type; and in the case of a split bearer, DL data transfer to the master base station may be maintained, NR An RLC affirmative mode (AM) bearer may be configured for a split bearer, the PCell and / or PSCell may not be stopped, the PSCell may be modified using an SCG modification procedure (e.g., using security key modification and RACH procedures), and / or bearer type changes between a split bearer and an SCG bearer, or simultaneous configuration of an SCG and a split bearer, may or may not be supported.

[0095] In the case of a multi-connection, the interaction between the master base station and secondary base stations may be one or more of the following: the master base station and / or secondary base stations may maintain the RRM measurement configuration of the radio device; the master base station may decide to request the secondary base station to provide additional resources (e.g., serving cells) for the radio device (based on, for example, received measurement reports, traffic conditions, and / or bearer type); and upon receiving a request from the master base station, the secondary base station may create / modify a container that can constitute an additional serving cell for the radio device (or the secondary base station may have the resources available to do so). (It can be determined that there is none), and for UE capability coordination, the master base station can provide the secondary base station with AS configuration and (part of) UE capability, the master and secondary base stations can exchange information about UE configuration by using RRC containers (internode messages) carried via Xn messages, the secondary base station can initiate the reconfiguration of an existing serving cell (e.g., a PUCCH directed to the secondary base station), the secondary base station can determine which cell is a PSCell in the SCG, the master base station may or may not modify the contents of the RRC configuration provided by the secondary base station, in the case of SCG addition and / or SCG SCell addition, the master base station can provide the most recent (or latest) measurement results for the SCG cell(s), and the master and secondary base stations can receive information about each other's SFN and / or subframe offset from the OAM and / or via the Xn interface (e.g., for the purpose of DRX adjustment and / or measurement gap identification). For example, when adding a new SCG SCell, dedicated RRC signaling can be used to transmit the cell's requested system information about the CA, excluding the SFN obtained from the SCG PSCell's MIB.

[0096] Figure 12 is an illustrative schematic of a random access procedure. One or more events can trigger a random access procedure. For example, one or more events could be at least one of the following: initial access from RRC_IDLE, RRC connection re-establishment procedure, handover, DL or UL data arrival during RRC_CONNECTED when the UL synchronization status is not synchronized, transition from RRC_Inactive, and / or requests for other system information. For example, a PDCCH instruction, MAC entity, and / or beam fault indication can initiate a random access procedure.

[0097] In exemplary embodiments, the random access procedure may be at least one of a competition-based random access procedure and a non-compete random access procedure. For example, a competition-based random access procedure may include one or more Msg1, 1220 transmissions, one or more Msg2, 1230 transmissions, one or more Msg3, 1240 transmissions, and a competition resolution 1250. For example, a non-compete random access procedure may include one or more Msg1, 1220 transmissions and one or more Msg2, 1230 transmissions.

[0098] In one example, a base station can transmit a RACH configuration 1210 to a UE via one or more beams (e.g., unicast, multicast, or broadcast). The RACH configuration 1210 may include one or more parameters indicating at least one of the following: an available set of PRACH resources for the transmission of random access preambles; initial preamble power (e.g., random access preamble initial receive target power); RSRP thresholds for selecting SS blocks and corresponding PRACH resources; power ramping factor (e.g., random access preamble power ramping step); random access preamble index; maximum number of preamble transmissions; preamble groups A and B; thresholds for determining the group of random access preambles (e.g., message size); a set of one or more random access preambles and corresponding PRACH resources for system information requests; if present, a set of one or more random access preambles and corresponding PRACH resources for beam fault recovery procedures; if present, a time window for monitoring RA responses; if present, a time window for monitoring responses in beam fault recovery procedures; and / or a conflict resolution timer.

[0099] In one example, Msg1, 1220 could be one or more transmissions of random access preambles. In the case of a competition-based random access procedure, the UE can select an SS block with an RSRP greater than the RSRP threshold. If a random access preamble group B exists, the UE can select one or more random access preambles from group A or group B, depending on the possible size of Msg3, 1240. If a random access preamble group B does not exist, the UE can select one or more random access preambles from group A. The UE can randomly select a random access preamble index from one or more random access preambles associated with the selected group (e.g., using equal probabilities or a normal distribution). If the base station quasi-statistically constructs the UE using the association between random access preambles and SS blocks, the UE can randomly select a random access preamble index from one or more random access preambles associated with the selected SS block and the selected group, using similar probabilities.

[0100] For example, a UE can initiate a no-contour random access procedure based on beam fault indications from lower layers. For instance, a base station can quasi-statistically configure a UE with one or more no-contour PRACH resources for a beam fault recovery procedure associated with at least one of the SS blocks and / or CSI-RS. If at least one of the associated SS blocks has an RSRP above a first RSRP threshold, or at least one of the associated CSI-RS has an RSRP above a second RSRP threshold, the UE can select a random access preamble index corresponding to the selected SS block or CSI-RS from a set of one or more random access preambles for the beam fault recovery procedure.

[0101] For example, the UE can receive a random access preamble index from the base station via PDCCH or RRC for a non-competing random access procedure. If the base station does not configure the UE with at least one non-competing PRACH resource associated with an SS block or CSI-RS, the UE can select a random access preamble index. If the base station configures the UE with one or more non-competing PRACH resources associated with an SS block and at least one SS block having an RSRP exceeding a first RSRP threshold in the associated SS block is available, the UE can select at least one SS block and select a random access preamble corresponding to the at least one SS block. If the base station configures the UE with one or more non-competing PRACH resources associated with CSI-RS and at least one CSI-RS having an RSRP exceeding a second RSPR threshold in the associated CSI-RS is available, the UE can select at least one CSI-RS and select a random access preamble corresponding to the at least one CSI-RS.

[0102] The UE can perform one or more Msg1,1220 transmissions by transmitting a selected random access preamble. For example, if the UE selects an SS block and configures it with one or more PRACH opportunities and associations between one or more SS blocks, the UE can determine a PRACH opportunity from one or more PRACH opportunities corresponding to the selected SS block. For example, if the UE selects a CSI-RS and configures it with one or more PRACH opportunities and associations between one or more CSI-RS, the UE can determine a PRACH opportunity from one or more PRACH opportunities corresponding to the selected CSI-RS. The UE can transmit a selected random access preamble to the base station via the selected PRACH opportunity. The UE can determine the transmission power for transmitting the selected random access preamble based on at least the initial preamble power and power ramping factor. The UE can determine the RA-RNTI associated with the selected PRACH opportunity on which the selected random access preamble is transmitted. For example, the UE does not have to determine the RA-RNTI for the beam fault recovery procedure. The UE can determine the RA-RNTI based on at least the index of the first OFDM symbol, the index of the first slot of the selected PRACH opportunity, and / or the uplink carrier index for the transmission of Msg1, 1220.

[0103] In one example, the UE may receive a random access response, Msg2, 1230, from the base station. The UE can start a time window (e.g., ra-ResponseWindow) to monitor the random access response. For beam fault recovery procedures, the base station can configure the UE with a different time window (e.g., bfr-ResponseWindow) to monitor the response to the beam fault recovery procedure. For example, the UE may start a time window (e.g., ra-ResponseWindow or bfr-ResponseWindow) from the end of a preamble transmission at the start of the first PDCCH opportunity after a fixed duration of one or more symbols. If the UE transmits multiple preambles, the UE may start a time window from the end of a first preamble transmission at the start of the first PDCCH opportunity after a fixed duration of one or more symbols. While the time window timer is running, the UE can monitor the cell's PDCCH for at least one random access response identified by RA-RNTI, or at least one response to a beam fault recovery procedure identified by C-RNTI.

[0104] In one example, if at least one random access response contains a random access preamble identifier corresponding to a random access preamble transmitted by the UE, the UE may consider the reception of the random access response to be successful. If the reception of the random access response is successful, the UE may consider the uncontested random access procedure to have completed successfully. If the uncontested random access procedure was triggered for a beam fault recovery procedure, the UE may consider the uncontested random access procedure to have completed successfully if the PDCCH transmission is addressed to C-RNTI. In one example, if at least one random access response contains a random access preamble identifier, the UE may consider the random access procedure to have completed successfully and may indicate the reception of an acknowledgment to a system information request to a higher layer. If the UE has sent multiple preamble transmissions, the UE may, in response to the successful reception of the corresponding random access response, stop transmitting any remaining preambles (if any).

[0105] In one example, a UE may perform one or more Msg3,1240 transmissions in response to the successful reception of a random access response (e.g., in the case of a competition-based random access procedure). The UE may adjust the uplink transmission timing based on the timing advanced command indicated by the random access response and transmit one or more transport blocks based on the uplink permission indicated by the random access response. The subcarrier spacing for the PUSCH transmission of Msg3,1240 can be provided by at least one higher-layer (e.g., RRC) parameter. The UE may transmit a random access preamble via PRACH and Msg3,1240 via PUSCH on the same cell. The base station may indicate the UL BWP for the PUSCH transmission of Msg3,1240 via a system information block. The UE may use HARQ for the retransmission of Msg3,1240.

[0106] In one example, multiple UEs can perform Msg1, 1220 by transmitting the same preamble to the base station and receive the same random access response (e.g., TC-RNTI) containing their identity from the base station. Conflict resolution 1250 can ensure that a UE does not mistakenly use the identity of another UE. For example, conflict resolution 1250 can be based on a C-RNTI on the PDCCH or a UE conflict resolution identity on the DL-SCH. For example, if the base station assigns a C-RNTI to a UE, the UE can perform conflict resolution 1250 based on receiving a PDCCH transmission addressed to the C-RNTI. In response to the detection of the C-RNTI on the PDCCH, the UE can consider conflict resolution 1250 to be successful and the random access procedure to have completed successfully. If a UE does not have a valid C-RNTI, conflict resolution can be addressed by using the TC-RNTI. For example, if the MAC PDU is successfully decrypted and contains a UE conflict resolution identity MAC CE that matches the CCCH SDU transmitted to Msg3, 1250, the UE can consider the conflict resolution 1250 to be successful and the random access procedure to have completed successfully.

[0107] Figure 13 shows an exemplary structure for a MAC entity based on one aspect of an embodiment of the present disclosure. In one example, a radio device can be configured to operate in multi-connection mode. An RRC_CONNECTED radio device having multiple RX / TX can be configured to utilize radio resources provided by multiple schedulers located in multiple base stations. These multiple base stations can be connected via an Xn interface through a non-ideal or ideal backhaul. In one example, a base station in the multiple base stations can function as a master base station or as a secondary base station. A radio device can be connected to one master base station and one or more secondary base stations. A radio device can be configured with multiple MAC entities, for example, one MAC entity for the master base station and one or more other MAC entities for the secondary base station(s). In one example, the set of serving cells configured for a radio device may include two subsets: an MCG containing the serving cells of the master base station, and one or more SCGs containing the serving cells of the secondary base station(s). Figure 13 shows an exemplary structure of a MAC entity when the MCG and SCG are configured for a radio device.

[0108] In one example, at least one cell within the SCG may have a configured UL CC, and one of the cells may be called the SCG's PSCell or PCell, or in some cases simply PCell. The PSCell can be configured using PUCCH resources. In one example, when the SCG is configured, there may be at least one SCG bearer or one split bearer. In one example, in response to detecting a physical layer problem or random access problem in the PSCell, or reaching the number of RLC retransmissions associated with the SCG, or detecting an access problem in the PSCell during SCG addition or modification, the RRC connection re-establishment procedure may not be triggered, UL transmissions toward the SCG's cells may be aborted, the master base station may be notified by the UE regarding the type of SCG failure, and DL data transfer may be maintained through the master base station.

[0109] In one example, a MAC sublayer can provide services such as data transfer and radio resource allocation to a higher layer (e.g., 1310 or 1320). A MAC sublayer can contain multiple MAC entities (e.g., 1350 and 1360). A MAC sublayer can provide data transfer services over logical channels. Multiple types of logical channels can be defined to accommodate different types of data transfer services. Logical channels can support the transfer of specific types of information. Logical channel types can be defined by the type of information (e.g., control or data) being transferred. For example, BCCH, PCCH, CCCH, and DCCH can be control channels, and DTCH can be a traffic channel. In one example, a first MAC entity (e.g., 1310) can provide services over PCCH, BCCH, CCCH, DCCH, DTCH, and MAC control elements. In one example, a second MAC entity (e.g., 1320) can provide services over BCCH, DCCH, DTCH, and MAC control elements.

[0110] The MAC sublayer can anticipate services from the physical layer (e.g., 1330 or 1340), such as data transfer services, HARQ feedback signaling, scheduling requests, or measurement signaling (e.g., CQI). In one example, in a dual connection, two MAC entities may be configured for the wireless device, namely, one for the MCG and one for the SCG. The MAC entity of the wireless device can handle multiple transport channels. In one example, the first MAC entity can handle a first transport channel including the PCCH of the MCG, the first BCH of the MCG, one or more first DL-SCHs of the MCG, one or more first UL-SCHs of the MCG, and one or more first RACHs of the MCG. In one example, the second MAC entity can handle a second transport channel including the second BCH of the SCG, one or more second DL-SCHs of the SCG, one or more second UL-SCHs of the SCG, and one or more second RACHs of the SCG.

[0111] In one example, if a MAC entity is composed of one or more SCells, there may be multiple DL-SCHs, multiple UL-SCHs, and multiple RACHs for each MAC entity. In one example, a SpCell may have one DL-SCH and one UL-SCH. In one example, a SCell may have one DL-SCH, zero or one UL-SCH, and zero or one RACH. A DL-SCH can support reception using different numerology and / or TTI durations within the MAC entity. Similarly, a UL-SCH can support transmission using different numerology and / or TTI durations within the MAC entity.

[0112] In one example, a MAC sublayer can support different functions, and these functions can be controlled using control elements (e.g., 1355 or 1365). Functions performed by a MAC entity may include mapping between logical channels and transport channels (e.g., on uplinks or downlinks), multiplexing MAC SDUs from one or more logical channels to transport blocks (TBs) to be delivered to the physical layer on a transport channel (e.g., on an uplink) (e.g., 1352 or 1362), partitioning MAC SDUs from transport blocks (TBs) delivered from the physical layer on a transport channel (e.g., on a downlink) to one or more logical channels (e.g., 1352 or 1362), scheduling information reporting (e.g., on uplinks), error correction via HARQ in uplinks or downlinks (e.g., 1363), and logical channel prioritization on uplinks (e.g., 1351 or 1361). A MAC entity can handle random access processes (e.g., 1354 or 1364).

[0113] Figure 14 is an illustrative schematic diagram of a RAN architecture including one or more base stations. In one example, a protocol stack (e.g., RRC, SDAP, PDCP, RLC, MAC, and PHY) may be supported at the node. A base station (e.g., gNB120A or 120B) may include a base station aggregation unit (CU) (e.g., gNB-CU1420A or 1420B) and, if a functional partition is configured, at least one base station distributed unit (DU) (e.g., gNB-DU1430A, 1430B, 1430C, or 1430D). The upper protocol layers of the base station may reside within the base station CU, and the lower layers of the base station may reside within the base station DU. The F1 interface connecting the base station CU and base station DU (e.g., CU-DU interface) may be ideal or non-ideal backhaul. F1-C may provide control plane connectivity via the F1 interface, and F1-U may provide user plane connectivity via the F1 interface. In one example, the Xn interface can be configured between base station CUs.

[0114] In one example, the base station CU may include RRC functionality, the SDAP layer, and the PDCP layer, while the base station DU may include the RLC layer, the MAC layer, and the PHY layer. In one example, various functional partitioning options between the base station CU and base station DU can be achieved by configuring different combinations of higher protocol layers (RAN functionality) within the base station CU and different combinations of lower protocol layers (RAN functionality) within the base station DU. Functional partitioning supports flexibility, allowing protocol layers to be moved between the base station CU and base station DU depending on service requirements and / or the network environment.

[0115] In one example, functional partitioning options can be configured per base station, per base station CU, per base station DU, per UE, per bearer, per slice, or using other granularities. In each base station CU partition, a base station CU may have a fixed partitioning option, and a base station DU may be configured to match the partitioning option of the base station CU. In each base station DU partition, a base station DU may be configured with different partitioning options, and a base station CU may provide different partitioning options for different base station DUs. In UE partitioning, a base station (base station CU, and at least one base station DU) may provide different partitioning options for different radio devices. In each bearer partition, different partitioning options may be available for different bearers. In slice-level splicing, different partitioning options may be applied to different slices.

[0116] Figure 15 is an illustrative schematic diagram showing the RRC state transitions of a wireless device. In one example, the wireless device may be in at least one of the following RRC states: RRC connected state (e.g., RRC connected 1530, RRC_Connected), RRC idle state (e.g., RRC idle 1510, RRC_Idle), and / or RRC stopped state (e.g., RRC stopped 1520, RRC_Inactive). In one example, in the RRC connected state, the wireless device may have at least one RRC connection with at least one base station (e.g., gNB and / or eNB), and those base stations may have the UE context of the wireless device. A UE context (e.g., a radio device context) may include at least one of the following: access layer context, one or more radio link configuration parameters, bearer (e.g., data radio bearer (DRB), signaling radio bearer (SRB), logical channel, QoS flow, PDU session, and / or similar) configuration information, security information, PHY / MAC / RLC / PDCP / SDAP layer configuration information, and / or similar configuration information for a radio device. In one example, in an RRC idle state, a radio device may not have an RRC connection with a base station, and the radio device's UE context may not be stored within the base station. In another example, in an RRC stopped state, a radio device may not have an RRC connection with a base station. The radio device's UE context may be stored within a base station, which may be called an anchor base station (e.g., a final serving base station).

[0117] In one example, a wireless device can transition its UE RRC state bidirectionally between an RRC idle state and an RRC connected state (e.g., connection release 1540 or connection establishment 1550, or connection re-establishment), and / or bidirectionally between an RRC stopped state and an RRC connected state (e.g., connection termination 1570 or connection reactivation 1580). In one example, a wireless device can transition its RRC state from an RRC stopped state to an RRC idle state (e.g., connection release 1560).

[0118] In one example, an anchor base station may be a base station capable of holding the UE context (radio device context) of a radio device for at least the duration of the time period during which the radio device remains in the anchor base station's RAN notification area (RNA) and / or the radio device remains in an RRC down state. In one example, an anchor base station may be the base station to which a radio device in an RRC down state was last connected in its most recent RRC connection state, or the base station to which the radio device last internally performed an RNA update procedure. In one example, an RNA may include one or more cells operated by one or more base stations. In one example, a base station may belong to one or more RNAs. In one example, a cell may belong to one or more RNAs.

[0119] In one example, a wireless device can cause the base station to transition the UE RRC state from an RRC connected state to an RRC stopped state. The wireless device can receive RNA information from the base station. The RNA information may include at least one RNA identifier, one or more cell identifiers of one or more cells of the RNA, a base station identifier, the base station's IP address, the wireless device's AS context identifier, a restart identifier, and / or similar.

[0120] In one example, an anchor base station can broadcast a message (e.g., a RAN paging message) to an RNA base station to cause a radio device to reach an RRC stop state, and / or a base station receiving a message from the anchor base station can broadcast and / or multicast another message (e.g., a paging message) through the air interface to radio devices in the base station's coverage area, cell coverage area, and / or beam coverage area that are associated with RNA.

[0121] In one example, when a radio device in an RRC-stopped state moves to a new RNA, the radio device can perform an RNA refresh (RNAU) procedure, which in turn allows the radio device and / or a UE context lookup procedure to perform a random access procedure. The UE context lookup may include the base station looking up a random access preamble from the radio device and the base station fetching the radio device's UE context from a previous anchor base station. Fetching may include sending a lookup UE context request message containing a restart identifier to the previous anchor base station and receiving a lookup UE context response message containing the radio device's UE context from the previous anchor base station.

[0122] In an exemplary embodiment, a radio device in an RRC-stopped state may select a cell to camp on based on measurement results for at least one cell, where the radio device can monitor RNA paging messages and / or core network paging messages from a base station. In one example, the radio device in an RRC-stopped state may select a cell to perform a random access procedure, reactivate the RRC connection, and / or transmit one or more packets to the base station (e.g., to the network). In one example, if the selected cell belongs to a different RNA than the RNA for the radio device in an RRC-stopped state, the radio device may initiate a random access procedure to perform an RNA refresh procedure. In one example, if the radio device in an RRC-stopped state has one or more packets in its buffer to transmit to the network, the radio device may initiate a random access procedure to transmit one or more packets to the base station of the cell selected by the radio device. The random access procedure may be performed between the radio device and the base station using two messages (e.g., two-stage random access) and / or four messages (e.g., four-stage random access).

[0123] In an exemplary embodiment, a base station receiving one or more uplink packets from a radio device in an RRC outage state can fetch the UE context of the radio device by transmitting a lookup UE context request message for the radio device to the radio device's anchor base station, based on at least one of the AS context identifier, RNA identifier, base station identifier, restart identifier, and / or cell identifier received from the radio device. In response to fetching the UE context, the base station can transmit a path switching request for the radio device to a core network entity (e.g., AMF, MME, and / or similar). The core network entity can update the downlink tunnel endpoint identifier for one or more bearers established for the radio device between a user plane core network entity (e.g., UPF, S-GW, and / or similar) and a RAN node (e.g., a base station), for example, by changing the downlink tunnel endpoint identifier from the anchor base station's address to the base station's address.

[0124] A gNB can communicate with wireless devices via a wireless network using one or more new wireless technologies. These one or more wireless technologies may include at least one of several technologies relating to the physical layer, several technologies relating to the medium access control layer, and / or several technologies relating to the wireless resource control layer. Exemplary embodiments that enhance these one or more wireless technologies can improve the performance of the wireless network. Exemplary embodiments can increase system throughput or data transmission rate. Exemplary embodiments can reduce battery consumption of wireless devices. Exemplary embodiments can improve data transmission latency between the gNB and wireless devices. Exemplary embodiments can improve network coverage of the wireless network. Exemplary embodiments can improve the transmission efficiency of the wireless network.

[0125] gNBs and / or radio devices may have multiple antennas to support high data rate transmission in an NR system. When configured with multiple antennas, the radio device can perform one or more beam management procedures, as shown in Figure 9B.

[0126] A wireless device can perform downlink beam management based on one or more CSI-RSs and / or one or more SSBs. In the beam management procedure, the wireless device can measure the channel quality of a beampair link. A beampair link may include a transmission beam from a gNB and a received beam in the wireless device. If it consists of multiple beams associated with multiple CSI-RSs or SSBs, the wireless device can measure multiple beampair links between the gNB and the wireless device.

[0127] In one example, a wireless device can transmit one or more beam management reports to a gNB. In the beam management report, the wireless device may indicate one or more beam pair quality parameters, including at least one or more beam identities, RSRP, and PMI / CQI / RI for at least a subset of the configured beams.

[0128] In one example, a gNB and / or a radio device may perform a downlink beam management procedure on one or more transmission and reception points (TRPs), as shown in Figure 9B. Based on the radio device's beam management report, the gNB may transmit a signal to the radio device indicating that a new beampair link is a serving beam. The gNB may then use the serving beam to transmit PDCCH and PDSCH to the radio device.

[0129] In one example, a wireless device or gNB can trigger a beam fault recovery mechanism. The wireless device can, for example, trigger a beam fault recovery (BFR) procedure when at least one beam fault occurs. In one example, a beam fault may occur if the quality of at least one beam pair link(s) of a PDCCH deteriorates below a threshold. The threshold may be an RSRP value (e.g., -140 dBm, -110 dBm) or a SINR value (e.g., -3 dB, -1 dB), which may be configured in an RRC message.

[0130] Figure 16A shows an example of a first beam fault scenario. In this example, the gNB can transmit PDCCH from the transmission (Tx) beam to the radio device's receiving (Rx) beam via the TRP. If the PDCCH on the beam pair link (between the gNB's Tx beam and the radio device's Rx beam) is below the threshold RSRP / SINR due to the beam pair link being blocked (e.g., by a moving vehicle or building), the gNB and the radio device can initiate a beam fault recovery procedure on the TRP.

[0131] Figure 16B shows an example of a second beam fault scenario. In this example, the gNB can transmit PDCCH from the beam to the wireless device from the first TRP. When PDCCH on the beam is blocked, the gNB and the wireless device can initiate a beam fault recovery procedure on a new beam on the second TRP.

[0132] In one example, a wireless device may measure the quality of a beampair link using one or more RSs. One or more RSs may be one or more SSBs or one or more CSI-RS resources. CSI-RS resources may be identified by a CSI-RS resource index (CRI). In one example, the quality of a beampair link may be defined as an RSRP value, or reference signal reception quality (e.g., RSRQ) value, and / or a CSI (e.g., SINR) value measured on the RS resource. In one example, a gNB may indicate whether the RS resources used to measure beampair link quality are QCLed (located approximately in the same place) with the DM-RS of the PDCCH. The RS resources and DM-RS of the PDCCH may be said to be QCLed when the channel characteristics from the transmission on the RS to the wireless device, and from the transmission on the PDCCH to the wireless device, are similar or identical under a configured criterion. For example, when the Doppler shift and / or Doppler shift of the channel from the RS transmission to the wireless device and from the PDCCH transmission to the wireless device are the same, the RS resource and DM-RS on the PDCCH may be said to be QCLed.

[0133] In one example, a wireless device can simultaneously monitor PDCCH on M beam (e.g., 2, 4, 8) pair links, where M ≥ 1, and the value of M may depend at least on the capabilities of the wireless device. In one example, monitoring PDCCH may include detecting DCI via PDCCH transmitted over a common search space and / or a wireless device-specific search space. In one example, monitoring multiple beam pair links may increase robustness against beam pair link blocking. In one example, a gNB may transmit one or more messages containing parameters indicating a wireless device to monitor PDCCH on different beam pair links in different OFDM symbols.

[0134] For example, a gNB can transmit one or more RRC messages or MAC CEs containing parameters indicating the Rx beam settings of a radio device for monitoring PDCCHs on multiple beampair links. For demodulation of the DL control channel, the gNB uses DL It is possible to transmit spatial QCL indications between RS antenna ports (or multiple) and DL RS antenna ports (or multiple). For example, the indication may be a MAC CE, or RRC message, or a parameter in DCI, and / or a combination of these signalings.

[0135] For example, to receive data packets on a PDSCH, a gNB can specify spatial QCL parameters between the DL RS antenna port(s) and DM-RS antenna port(s) of a DL data channel. The gNB can transmit a DCI containing parameters indicating the DM-RS antenna port(s) and the QCL-equipped RS antenna port(s).

[0136] In one example, when a gNB transmits a signal indicating the QCL parameter between the CSI-RS and DM-RS of the PDCCH, the wireless device can measure beam pair link quality based on the DM-RS of the PDCCH and the QCL-enhanced CSI-RS. In another example, when multiple adjacent beam faults occur, the wireless device can initiate a BFR procedure.

[0137] In one example, when a wireless device initiates a BFR procedure, it transmits a BFR signal to a gNB over the uplink physical channel. In response to receiving the BFR signal on the uplink physical channel, the gNB can transmit a DCI via the PDCCH in the core set. The wireless device can consider the BFR procedure to have completed successfully when it receives the DCI via the PDCCH in the core set.

[0138] In one example, a gNB can transmit one or more messages containing configuration parameters for an uplink physical channel or signal for transmitting a beam fault recovery request. The uplink physical channel or signal can be based on one of the following resources: non-conflict PRACH (BFR-PRACH), PUCCH (BFR-PUCCH), and / or conflict-based PRACH resource (CF-PRACH), which may be orthogonal to other PRACH transmission resources. These candidate signal / channel combinations may be configured by the gNB. In one example, when multiple resources are configured for a BFR signal, the radio device can autonomously select a first resource for transmitting the BFR signal. In one example, when BFR-PRACH resources, BFR-PUCCH resources, and CF-PRACH resources are configured, the radio device can select the BFR-PRACH resource for transmitting the BFR signal. In one example, when BFR-PRACH resources, BFR-PUCCH resources, and CF-PRACH resources are configured, the gNB can transmit a message to the radio device indicating which resource is for transmitting the BFR signal.

[0139] In one example, a gNB can transmit a response to a radio device after receiving one or more BFR signals. The response may include a CRI associated with the candidate beams indicated by the one or more BFR signals in the radio device.

[0140] For example, a gNB may transmit a DCI via the PDCCH for at least one of the following: scheduling assignment / authorization, slot format notification, preemption indication, and / or power control recommendation. More specifically, the DCI may include at least one of the following: a DCI format identifier, downlink scheduling assignment(s), uplink scheduling authorization(s), slot format indicator, preemption indication, PUCCH / PUSCH power control, and / or SRS power control.

[0141] For example, a downlink scheduling assignment DCI may include parameters indicating at least one of the following: a DCI format identifier, a PDSCH resource display, a transport format, HARQ information, control information related to multiple antenna schemes, and / or commands for PUCCH power control.

[0142] For example, an uplink scheduling permission DCI may include parameters that indicate at least one of the following: a DCI format identifier, a PUSCH resource display, a transport format, HARQ-related information, and / or a PUSCH power control command.

[0143] In one embodiment, different types of control information may correspond to different DCI payload sizes. For example, supporting multiple beams and / or spatial multiplexing in the spatial domain and discontinuous allocation of RBs in the frequency domain may require larger scheduling messages compared to uplink authorization which enables continuous frequency allocation. DCI may be classified into different DCI formats if the format corresponds to a particular message size and / or usage.

[0144] For example, a wireless device may monitor one or more PDCCHs to detect one or more DCIs having one or more DCI formats in a common search space or a wireless device-specific search space. Alternatively, a wireless device may monitor PDCCHs with a limited set of DCI formats to conserve power. The more DCI formats detected, the more power the wireless device will consume.

[0145] For example, DCI format information for downlink scheduling may include at least one of the following: DCI format identifier, carrier indicator, RB allocation, time resource allocation, bandwidth indicator, HARQ process count, one or more MCSs, one or more NDIs, one or more RVs, MIMO-related information, downlink allocation index (DAI), PUCCH TPC, SRS request, and padding as appropriate. For example, MIMO-related information may include at least one of the following: PMI, precoding information, transport block swap flag, power offset between PDSCH and reference signal, reference signal scramble sequence, number of layers, and / or antenna port for transmission, and / or transmission configuration indication (TCI).

[0146] For example, the DCI format information used for uplink scheduling may include at least one of the following: DCI format identifier, carrier indicator, bandwidth portion display, resource allocation type, RB allocation, time resource allocation, MCS, NDI, uplink DMRS phase rotation, precoding information, CSI request, SRS request, uplink index / DAI, PUSCH TPC, and / or padding as needed.

[0147] In one embodiment, the gNB may perform CRC scrambling on the DCI before transmitting the DCI over the PDCCH. The gNB may scramble at least one radio device identifier on the CRC bits of the DCI (e.g., C-RNTI, CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, SP CSI). CRC scrambling can be performed by binary summing multiple bits of a DCI (C-RNTI, SRS-TPC-RNTI, INT-RNTI, SFI-RNTI). When a radio device detects a DCI, it may examine the CRC bits of the DCI. A radio device may receive a DCI when its CRC is scrambled by a sequence of bits that are the same as at least one radio device identifier.

[0148] For example, to support high-bandwidth operation, a gNB can transmit one or more PDCCHs on different control resource sets (core sets). A gNB can transmit one or more RRC messages containing configuration parameters for one or more core sets. A core set may include at least one of the following: a first OFDM symbol, several consecutive OFDM symbols, a set of resource blocks, or a CCE vs. REG mapping. For example, a gNB can transmit PDCCHs on a dedicated core set for a specific purpose, such as verifying beam fault recovery.

[0149] For example, a wireless device may monitor PDCCH to detect DCI in one or more configured core sets in order to reduce power consumption.

[0150] In an NR system, if it consists of multiple beams, the gNB and / or radio device can perform one or more beam management procedures. For example, the radio device can perform a BFR procedure if one or more beam pair links between the gNB and the radio device fail.

[0151] Figure 17 shows an example of the BFR procedure for a cell (e.g., PCell or SCell). The radio device can receive one or more RRC messages containing BFR parameters (1701). One or more RRC messages may include RRC messages (e.g., RRC connection reconfiguration messages, or RRC connection re-establishment messages, or RRC connection setup messages). The radio device can detect at least one beam fault according to at least one of the BFR parameters (1702). The radio device can start a first timer if configured in response to detecting at least one beam fault. The radio device can select a selected beam in response to detecting at least one beam fault (1703). The selected beam may be a beam with good channel quality (e.g., RSRP, SINR, or BLER) from a set of candidate beams. Candidate beams may be identified by a set of reference signals (e.g., SSB, or CSI-RS). The radio device can transmit at least a first BFR signal to the gNB in ​​response to selecting the selected beam (1704). At least a first BFR signal may be associated with a selected beam. The at least first BFR signal may be a preamble transmitted over a PRACH resource, or an SR signal transmitted over a PUCCH resource, or a beam indication transmitted over a PUCCH / PUSCH resource. The radio device may transmit at least a first BFR signal on the transmission beam corresponding to the received beam associated with the selected beam. The radio device may initiate a response window in response to transmitting at least a first BFR signal. In one example, the response window may be a timer with a value configured by a gNB. While the response window is in operation, the radio device may monitor the PDCCH on a first core set (1705). The first core set may be associated with a BFR procedure. In one example, the radio device may monitor the PDCCH on a first core set under the condition that at least a first BFR signal is transmitted.The wireless device may receive a first DCI via the PDCCH on the first core set while the response window is in operation (1706). The wireless device may consider the BFR procedure to have completed successfully when it receives a first DCI via the PDCCH on the first core set before the response window expires (1707). The wireless device may stop the first timer if configured in response to the successful completion of the BFR procedure. The wireless device may stop the response window in response to the successful completion of the BFR procedure.

[0152] For example, if the response window expires and the radio device does not receive a DCI, the radio device may increment the transmission count, and the transmission count is initialized to a first number (e.g., 0) before the BFR procedure is triggered. If the transmission count is less than the configured maximum transmission count (1708), the radio device may repeat one or more actions, including at least one of the following: transmitting a BFR signal, initiating a response window, monitoring the PDCCH, or incrementing the transmission count if no response is received during the operation of the response window. If the transmission count is greater than or equal to the configured maximum transmission count, the radio device may declare that the BFR procedure has not completed successfully (1709).

[0153] In one example, a wireless device may trigger an SR to request UL-SCH resources when the wireless device has a new transmission. A gNB may transmit at least one message to the wireless device containing parameters indicating zero, one, or more SR configurations. An SR configuration may include a set of PUCCH resources for an SR on one or more BWPs and / or one or more cells. On a BWP, up to one PUCCH resource may be configured for an SR. Each SR configuration may correspond to one or more logical channels. Each logical channel may be mapped to zero or one SR configuration configured by at least one message. The SR configuration of a logical channel (LCH) that triggers a Buffer Status Report (BSR) may be considered the corresponding SR configuration for the triggered SR.

[0154] For example, for each SR configuration, at least one message may further include one or more parameters indicating at least one of the following: an SR prohibit timer, a maximum number of SR transmissions, parameters indicating the periodicity and offset of SR transmissions, and / or a PUCCH resource. For example, the SR prohibit timer may be the duration during which the radio device may not be permitted to transmit an SR. For example, the maximum number of SR transmissions may be the maximum number of transmissions that the radio device may be permitted to transmit an SR.

[0155] In one example, a PUCCH resource may be identified by a PUCCH format associated with at least a frequency position (e.g., start PRB), an initial cyclic shift of the basic sequence, and a time-domain position (e.g., start symbol index). In one example, the PUCCH format could be PUCCH format 0, or PUCCH format 1, or PUCCH format 2, or PUCCH format 3, or PUCCH format 4. PUCCH format 0 can have a length of 1 or 2 OFDM symbols and is 2 bits or less. PUCCH format 1 can occupy a number of OFDM symbols from 4 to 14 and is 2 bits or less. PUCCH format 2 can occupy 1 or 2 OFDM symbols and is larger than 2 bits. PUCCH format 3 can occupy a number of OFDM symbols from 4 to 14 and is larger than 2 bits. PUCCH format 4 can occupy a number of OFDM symbols from 4 to 14 and is larger than 2 bits.

[0156] For example, the PUCCH format for SR transmission may be PUCCH format 0 or PUCCH format 1. A wireless device can transmit a PUCCH with the PUCCH resource of the corresponding SR configuration only when the wireless device is transmitting a positive SR. In the case of positive SR transmission using PUCCH format 0, the wireless device can transmit a PUCCH by setting the cyclic shift to a first value (e.g., 0). In the case of positive SR transmission using PUCCH format 1, the wireless device can transmit a PUCCH by setting the first bit to a first value (e.g., 0) before the BPSK is modulated in sequence.

[0157] In one example, an SR may be multiplexed with a HARQ-ACK or CSI on the PUCCH format. When a positive SR is multiplexed with a HARQ-ACK, the radio device can determine the cyclic shift of the base sequence based on an initial cyclic shift and a first cyclic shift, based on one or more values ​​of one or more HARQ-ACK bits. When a negative SR is multiplexed with a HARQ-ACK, the radio device can determine the cyclic shift of the base sequence based on an initial cyclic shift and a second cyclic shift, based on one or more values ​​of one or more HARQ-ACK bits. The first cyclic shift is different from the second cyclic shift.

[0158] For example, a wireless device can maintain an SR transmission counter (e.g., SR_COUNTER) associated with the SR configuration.

[0159] For example, if an SR in an SR configuration is triggered and there are no other SRs in a pending state corresponding to the same SR configuration, the wireless device may set the SR_COUNTER of the SR configuration to a first value (e.g., 0).

[0160] In one example, when an SR is triggered, the wireless device may consider the SR to be in a pending state until it is canceled. In another example, all pending SRs may be canceled when one or more UL permissions correspond to all pending data available for transmission.

[0161] For example, a wireless device can determine one or more PUCCH resources on an active BWP as valid PUCCH resources when an SR transmission opportunity arises.

[0162] In one example, a wireless device can transmit a PUCCH using a PUCCH resource associated with the SR configuration when the wireless device transmits a positive SR. In another example, the wireless device can transmit a PUCCH using PUCCH format 0 or PUCCH format 1, depending on the PUCCH configuration.

[0163] Figure 18 shows an example of an embodiment. In this example, the wireless device can receive one or more RRC messages containing parameters for one or more SR configurations. In this example, for each of the one or more SR configurations, the parameters may include at least one of the following: an SR disable timer, a maximum number of SR transmissions, parameters indicating the periodicity and offset of SR transmissions, and / or a PUCCH resource identified by a PUCCH resource index. In this example, when an SR of an SR configuration is triggered (and therefore currently in a pending state) in response to a BSR being triggered on the LCH corresponding to the SR configuration, and there are no other pending SRs corresponding to the SR configuration, the wireless device may set SR_COUNTER to a first value (e.g., 0).

[0164] In one example, a wireless device can determine whether there is at least one valid PUCCH resource for a pending SR transmission opportunity. If no valid PUCCH resource exists for the pending SR, the wireless device can initiate a random access procedure on the PCell. In response to the lack of a valid PUCCH resource for the pending SR, the wireless device can cancel the pending SR.

[0165] For example, if there is at least one valid PUCCH resource for a pending SR, the radio device can determine an SR transmission opportunity on at least one valid PUCCH resource based on the periodicity and offset of the SR transmission. For example, if the SR prohibit timer is active, the radio device can wait for another SR transmission opportunity. For example, if the SR prohibit timer is not active and SR_COUNTER is less than the maximum number of SR transmissions, the radio device can increment SR_COUNTER (e.g., by 1) and instruct the radio device's physical layer to signal an SR on at least one valid PUCCH resource for the SR. The radio device's physical layer can then transmit a PUCCH on at least one valid PUCCH resource for the SR. In response to transmitting a PUCCH, the radio device can monitor PDCCH to detect a DCI for uplink permission.

[0166] For example, if a wireless device receives one or more uplink permissions that can accommodate all pending data available for transmission, the wireless device may cancel pending SRs and / or stop the SR prohibition timer.

[0167] For example, if a wireless device does not receive one or more uplink permissions that can accommodate all pending data available for transmission, the wireless device may repeat one or more actions, including determining at least one valid PUCCH resource, checking whether the SR ban timer is running, checking whether SR_COUNTER is equal to or greater than the maximum number of SR transmissions, incrementing SR_COUNTER, transmitting an SR, starting the SR ban timer, and monitoring PDCCH for uplink permissions.

[0168] For example, if SR_COUNTER indicates a number greater than or equal to the maximum number of SR transmissions, the wireless device may release PUCCH for one or more serving cells, and / or release SRS for one or more serving cells, and / or clear one or more configured downlink assignments and uplink permissions, initiate a random access procedure on the PCell, and / or cancel pending SRs.

[0169] In one example, a gNB and a radio device can perform a PRACH-based BFR procedure when at least one beam fault instance is identified, provided that beam correspondence exists between the gNB and the radio device. In one example, beam correspondence may exist when the radio device transmits an uplink signal using a transmission beam corresponding to a receive beam for receiving a downlink signal from the gNB. Once the radio device identifies the receive beam, for example by determining the RF and / or digital beamforming parameters for receiving a downlink signal from the gNB, the radio device can determine the transmission beam using the RF and / or digital beamforming parameters corresponding to the beamforming parameters of the receive beam. For example, the beamforming parameters of the transmission beam (e.g., beam weighting coefficients of antenna elements) may be the same as the beamforming parameters of the receive beam when beam correspondence exists. Because the radio device can determine the transmission beam based on the receive beam, the presence of beam correspondence can sometimes simplify transceiver design. In one example, beam correspondence may be used so that the gNB does not necessarily indicate which transmission beam is used for downlink or uplink transmission, thus reducing signaling overhead. In one example, beam matching may be used so that a wireless device avoids uplink beam sweeping in order to help the gNB find a suitable uplink beam, and thus reduce the power consumption of the wireless device. In one example, the suitable beam may be in the direction of the wireless device. Beam matching may exist in some scenarios, for example, in the case of TDD, or when the transmission and reception share the same set of physical antenna elements and / or when the transmission and reception have the same or similar beamwidths.

[0170] In one example, beam mapping may not be necessary if the transmission physical antenna is separated from the receiving physical antenna, and / or if the transmission beamwidth and the reception beamwidth are different. In one example, the radio device may not have to determine the transmission beam based on the received beam. The received beam may be used to receive downlink signals. In such cases, the gNB can explicitly indicate the transmission beam for PUCCH / PUSCH transmissions, for example, by an RRC message, MAC CE, or DCI. In one example, the gNB and radio device may not have to perform a PRACH-based BFR procedure if at least one beam fault instance is identified when beam mapping is not present.

[0171] In the absence of beam mapping, existing PRACH-based BFR procedures allow the radio device to determine, for PRACH preamble transmission, the receiving beam and associated transmission beam for receiving the candidate beam. However, because the gNB does not expect an uplink transmission to exist on the transmission beam on which the radio device transmits the PRACH preamble, the gNB may fail to detect the PRACH preamble due to the lack of beam mapping between the transmission beam and the receiving beam in the gNB and / or radio device. In this case, the PRACH-based BFR procedure may result in a failure of beam fault recovery. A failed beam fault recovery can further lead to a radio link failure.

[0172] In one example, if beam matching is not present, the wireless device may transmit a PUCCH signal to the gNB indicating that the BFR procedure has been triggered when at least one beam fault instance is identified. The transmission beam of the PUCCH signal may be indicated by an RRC message, or MAC CE, or DCI. In one example, HARQ is not supported in existing PUCCH transmissions. By implementing existing PUCCH-based transmission techniques, the wireless device may have difficulty determining whether the gNB has received the PUCCH signal for the BFR procedure. In one example, the wireless device may use an SR-based BFR procedure, which may be implemented based on the example in Figure 18. By implementing an SR-based BFR procedure, the wireless device can receive a response from the gNB after transmitting the SR for the BFR procedure.

[0173] In many scenarios, a wireless device can execute multiple PUCCH-based procedures that overlap in time. For example, a wireless device can trigger one or more first SRs based on a buffer status report procedure. Each of these first SRs may, for example, be associated with a logical channel. The wireless device can trigger a second SR when it initiates beam fault recovery (for example, by implementing the example in Figure 17). The wireless device can receive DCIs via PDCCH when executing multiple PUCCH-based procedures. By implementing existing SR techniques, the wireless device can cancel all pending SRs (e.g., one or more first and second SRs) together. For example, an uplink grant may be received in response to one of the SRs. For example, in legacy techniques, all SR procedures may be canceled when the wireless device receives a DCI containing one or more uplink grants (which may correspond to available uplink data transmissions). For example, DCI does not have to be a response to the transmission of a second SR (e.g., if DCI is not transmitted on a dedicated control resource set for beam fault recovery). Implementing existing techniques (e.g., canceling all SR procedures) can reduce uplink transmission spectral efficiency, increase beam fault recovery latency, increase uplink transmission power, and / or increase uplink transmission interference. In an example of implementing existing SR techniques, a radio device may cancel a second SR if DCI includes uplink permission or if DCI is not received on a dedicated control resource set. This can lead to a failure of the beam fault recovery procedure. By implementing existing SR techniques, a radio device may cancel one or more first SRs if DCI is a response to a second SR. The SR process may be terminated / cancelled, resulting in inefficient uplink scheduling. Existing SR techniques need to be improved for BFR procedures.Exemplary embodiments provide an extended mechanism for when multiple PUCCH-based procedures overlap in time. For example, the improved embodiment improves uplink and / or downlink radio link performance when one or more beam fault recovery procedures (e.g., PUCCH-based / SR-based beam fault recovery) and SR procedures overlap in time. Exemplary embodiments may include holding a first SR for a buffer status report procedure and / or canceling a second SR for beam fault recovery based on the receipt of a response to a second SR.

[0174] Existing SR (Signal Recovery) techniques may implement PUCCH-based beam fault recovery by transmitting SR requests. A radio device can transmit SRs based on a buffer status report procedure (e.g., with 1 or 2 bits of information via a PUCCH). For example, SRs may be transmitted based on On / Off Keying (OOK) techniques. In OOK techniques, a radio device can transmit a signal (indicating "on") via a configured PUCCH resource to indicate that uplink data is available for transmission. In OOK techniques, a radio device can skip transmitting a signal (indicating "off") via a configured PUCCH resource to indicate that no uplink data is available. For example, a base station can determine whether an uplink permission request is transmitted based on whether this signal is present on a configured PUCCH resource. Existing implementations of SR-based beam fault recovery techniques may not provide the base station with sufficient information to recover from a beam fault. For example, a radio device may not be able to provide the information the base station needs to resolve a beam fault. Implementing a PUCCH-based beam fault recovery procedure requires improvements to existing SR procedures and signal formats. Exemplary embodiments provide extended SR procedures and signal formats for implementing PUCCH-based beam fault recovery procedures. Exemplary embodiments may include transmitting candidate beam information (e.g., candidate beams and channel quality of the candidate beams) via a PUCCH resource for SR associated with beam fault recovery.

[0175] In legacy technology, a radio device may not receive a response from the base station for one or more first SRs (for uplink permission requests) or second SRs (for BFR procedures), and may reach the maximum number of SR transmissions. Existing SR technology allows a radio device to cancel all pending SRs (e.g., one or more first and second SRs) if the radio device reaches the maximum number of SR transmissions. By implementing existing SR technology, a radio device can cancel all pending SRs when the SR transmission counter reaches the maximum number of SR transmissions. For example, the SR transmission counter might be for a second SR in a beam fault recovery procedure, resulting in the cancellation of all SR procedures. The SR process may be terminated / cancelled, resulting in inefficient uplink scheduling. Implementing existing technology (e.g., canceling all SR procedures) can reduce uplink transmission spectral efficiency, increase beam fault recovery latency, increase uplink transmission power, and / or increase uplink transmission interference. This can lead to beam fault recovery procedure failure. SR processes may be terminated / cancelled, resulting in inefficient uplink scheduling. Existing SR techniques need to be improved for BFR procedures. Exemplary embodiments provide an extended mechanism when multiple PUCCH-based procedures overlap in time. For example, the improved embodiment improves uplink and / or downlink radio link performance when one or more beam fault recovery procedures (e.g., PUCCH-based / SR-based beam fault recovery) and SR procedures overlap in time. Exemplary embodiments may include canceling SRs for beam fault recovery and continuing to hold other SRs for buffer status report procedures when the radio device reaches the maximum number of SR transmissions for beam fault recovery.

[0176] In one example, a wireless device may consist of an SR for beam fault recovery and one or more RACH resources for beam fault recovery. In legacy technology, the wireless device can trigger the SR when the wireless device initiates beam fault recovery. Alternatively, the wireless device can initiate random access-based beam fault recovery on one of the one or more RACH resources. By implementing an existing beam fault recovery procedure, the wireless device can select one uplink resource, either an SR resource or a RACH resource, to perform beam fault recovery. For example, restricting uplink resources to one type (either SR or RACH) for beam fault recovery may reduce uplink transmission spectral efficiency, increase beam fault recovery latency, increase uplink transmission power, and / or increase uplink transmission interference. Therefore, if both SR and RACH resources are configured for a BFR procedure, the existing BFR procedure needs to be improved. Exemplary embodiments can implement an extended beam fault recovery procedure that includes selecting an SR resource or a RACH resource for transmitting or retransmitting beam fault recovery request messages. For example, the choice of transmitting or retransmitting a beam fault recovery request message may be based on the availability of SR resources and / or RACH resources for beam fault recovery. Exemplary embodiments may include performing the beam fault recovery procedure by treating SR-based beam fault recovery and RACH-based beam fault recovery as a single process (e.g., maintaining retransmission counters for both RACH-based and SR-based beam fault recovery).

[0177] Exemplary embodiments can improve upon existing SR techniques for beam fault recovery. Exemplary embodiments may include holding a first SR for a buffer status report procedure and / or canceling a second SR for beam fault recovery based on the receipt of a response to a second SR. Exemplary embodiments may include transmitting candidate beam information via a PUCCH resource for SRs associated with beam fault recovery. Exemplary embodiments may include monitoring a dedicated set of control resources for responses to the transmission of candidate beam information via the PUCCH resource. Exemplary embodiments may include canceling an SR for beam fault recovery and holding other SRs for the buffer status report procedure when the wireless device reaches the maximum number of SR transmissions for beam fault recovery. Exemplary embodiments may include performing a beam fault recovery procedure by selecting an SR resource or a RACH resource for transmitting or retransmitting beam fault recovery request messages. Exemplary embodiments may include performing a beam fault recovery procedure by treating SR-based beam fault recovery and RACH-based beam fault recovery as a single process (e.g., maintaining retransmission counters for both RACH-based and SR-based beam fault recovery). Exemplary embodiments can increase uplink transmission spectral efficiency, reduce beam fault recovery latency, reduce uplink transmission power, and / or reduce uplink transmission interference.

[0178] In an SR configuration, the SR configuration may correspond to at least one logical channel. The SR configuration may be associated with several parameters, including at least one of the following: an SR disable timer, a maximum number of SR transmissions, parameters indicating the periodicity and offset of SR transmissions, and / or a PUCCH resource.

[0179] In one example, when an SR procedure is used for a BFR procedure, the SR configuration for the BFR procedure may differ from the SR configuration associated with at least one logical channel. For example, a wireless device may transmit up to 64 pending SRs for an SR configuration associated with at least one logical channel. In one example, for example, a wireless device may transmit up to 200 SRs for an SR configuration for a BFR procedure, taking into account the possibility that beam-enabled signals may not be present. In one example, the response window for a BFR procedure may be shorter than the response window for an SR requesting a UL-SCH resource. For example, the response timer associated with a BFR procedure may have up to 80 slots. The SR ban timer for an SR configuration requesting a UL-SCH resource may have up to 128 milliseconds. Thus, the SR configuration for a BFR procedure may be configured separately or independently of the SR configuration requesting a UL-SCH resource. Exemplary embodiments can provide a method for defining an SR configuration for a BFR procedure.

[0180] For example, when an SR procedure is used in a BFR procedure, the SR procedure triggered by the BFR procedure may be different from the SR procedure triggered by requesting UL-SCH resources (e.g., triggered by a BSR). For example, if there are multiple pending SRs, including a pending SR for a BFR procedure and one or more pending SRs for requesting one or more UL-SCH resources, the existing SR procedure needs to be improved for the multiple pending SRs (including an SR for buffer status reporting and an SR for beam fault recovery). When the radio device and gNB implement the existing SR procedure, they may perform inconsistent actions with respect to multiple pending SRs. An exemplary embodiment can improve inconsistencies between the gNB and the radio device when multiple SRs (e.g., for a BFR procedure and for requesting UL-SCH resources) are pending.

[0181] Figure 19 shows an example of an embodiment. The gNB can transmit at least one message containing parameters indicating a first set of RS (e.g., RS0) and a second set of RS (e.g., RS1, RS2, and RS3). At least one message may be an RRC message (e.g., an RRC connection reconfiguration message, or an RRC connection re-establishment message, or an RRC connection setup message). The first set of RS can identify one or more beams that the gNB uses to transmit PDCCH / PDSCH and that have been QCL'd. The second set of RS can identify one or more candidate beams from which the radio device can select a candidate beam that has a quality better than a first threshold when one or more beams associated with the first set of RS fail. In one example, each of the first / second set of RS may be SSB or CSI-RS. The first threshold may be a value configured based on BLER, or SINR, or L1-RSRP. For example, if the measurements on the first set of RSs are worse than a configured second threshold (e.g., RSRP or BLER), one or more beams associated with the first set of RSs will fail.

[0182] In one example, at least one message may include configuration parameters. In one example, the configuration parameters may represent a first request (e.g., a scheduling request, or a beam failure request, or a beam request) configuration and at least a second SR (e.g., a scheduling request) configuration. The first request configuration may be associated with at least one of a first PUCCH resource, a first timer with a first value, a first transmission count, a first periodicity of the transmission of the first request, and / or a first offset of the transmission of the first request. In one example, at least a second SR configuration may be associated with at least one of a second PUCCH resource, a second timer with a second value, a second transmission count, a second periodicity, and / or a second offset. In one example, at least a second SR configuration may be associated with at least one logical channel.

[0183] In this specification, a radio device may transmit a request signal via PUCCH in response to initiating beam fault recovery. This process may be referred to as SR-based beam fault recovery. This process may also be referred to by different names, e.g., PUCCH-based beam fault recovery, control channel-based beam fault recovery, SR-based beam fault recovery, and / or similar. A request for beam fault recovery may be referred to as an SR request, beam fault request, PUCCH beam request, or beam request, and / or similar. For example, in this specification, if a base station transmits at least one message (e.g., RRC) to a radio device containing configuration parameters for SR for beam fault recovery, the configuration parameters may be referred to as PUCCH-based beam fault recovery configuration parameters, SR parameters for beam fault recovery, or PUCCH request parameters for beam fault recovery, and / or similar.

[0184] In one example, the first value of the first timer may be different from the second value of the second timer. In one example, the first transmission count may be different from the second transmission count. In one example, the first periodicity may be different from the second periodicity. In one example, the first offset may be different from the second offset. In one example, the first PUCCH resource may be different from the second PUCCH resource.

[0185] In one example, the wireless device may maintain a first counter for a first required configuration. In another example, the wireless device may maintain a second counter for each of at least two second sr configurations.

[0186] In one example, at least one message may include parameters indicating a first control resource set and at least a second control resource set. The first control resource set may be associated with a first request configuration. In one example, when a wireless device transmits a first request on a first PUCCH resource for a BFR procedure, the wireless device may monitor a first PDCCH on the first control resource set. In one example, when a wireless device transmits a second sr of at least a second sr configuration, the wireless device may monitor a second PDCCH on at least a second control resource set. By exemplary embodiments, the wireless device may determine, based on the control resource set from which the wireless device receives the DCI, whether the received DCI is for beam fault recovery or for an uplink permission request. By exemplary embodiments, uplink transmission spectral efficiency can be increased, beam fault recovery latency can be reduced, uplink transmission power can be reduced, and / or uplink transmission interference can be reduced.

[0187] Figure 20 shows an exemplary embodiment of a BFR procedure flowchart. In one example, the BFR procedure may be triggered when a radio device identifies at least one beam fault instance on a first set of RSs. The radio device may select a candidate beam from a second set of RSs. In response to selecting a candidate beam, the radio device may trigger a first request associated with a first request configuration. In one example, when a logical channel triggers a BSR, the radio device may trigger a second sr associated with at least a second sr configuration corresponding to the logical channel. In one example, the radio device may perform a normal sr procedure for the second sr based on the configuration parameters of at least a second sr configuration. In one example, the normal sr procedure may include requesting uplink permission for uplink transmission (e.g., PUSCH).

[0188] In one example, once the first request is triggered, the first request can remain on hold until it is canceled. In another example, once the second service request (SR) is triggered, the second service request (SR) can remain on hold until it is canceled.

[0189] In one example, when a wireless device triggers a first request of a first request configuration, the wireless device may determine that a first PUCCH resource is an active PUCCH resource at the time of the first request transmission opportunity. An active PUCCH resource may be a PUCCH resource on a BWP that is active at the time of the request transmission opportunity. The opportunity for the first request transmission may depend on a first periodicity and / or a first offset consisting of at least one message and / or the timing at which the first request is triggered.

[0190] Figure 21 shows an example of an embodiment. The wireless device can receive one or more RRC messages containing configuration parameters for a first SR associated with a buffer status report and a second SR associated with beam fault recovery on the cell. One or more RRC messages may include RRC connection reconfiguration messages, RRC connection re-establishment messages, and / or RRC connection setup messages. In one example, the cell may be a PCell or SCell. In one example, the wireless device may trigger a first request (e.g., a first SR as shown in Figure 21) based on the buffer status report. The wireless device may trigger a second SR (e.g., a second SR as shown in Figure 21) for the beam fault recovery procedure.

[0191] When the wireless device triggers a second request, it can set the first counter to a first value (e.g., 0). When the wireless device determines that there is an available PUCCH resource for the second request transmission, it can trigger the second request on the available PUCCH resource if the first counter shows a value less than a first transmission number.

[0192] In one example, a wireless device can transmit a PUCCH signal over an active PUCCH resource when triggering a second request. Unlike, for example, the PUCCH transmission (OOK) of existing SR techniques, the PUCCH signal for beam fault recovery may include at least one parameter, including either an RS index that identifies a candidate beam and / or the measured quality of the candidate beam (e.g., RSRP). In an exemplary embodiment, the wireless device can transmit candidate beam information over a PUCCH resource for SR associated with beam fault recovery. The exemplary embodiment can increase uplink transmission spectral efficiency, reduce beam fault recovery latency, reduce uplink transmission power, and / or reduce uplink transmission interference.

[0193] In one example, the second request may consist of multiple PUCCH resources in at least one message. Each PUCCH resource may be associated with one of the second set of RSs. When the BFR procedure is triggered, the radio device can select a candidate beam from the second set of RSs. The radio device can determine which PUCCH resource among the multiple PUCCH resources associated with the candidate beam. In one example, the radio device can transmit a PUCCH signal over the PUCCH resource. In one example, the PUCCH signal may be a bit. In one example, the bit may be set to a first value (e.g., 1) indicating that the BFR procedure is triggered and / or that a candidate beam associated with the PUCCH resource is identified.

[0194] In one example, the wireless device may, in response to transmitting a second request, increment a first counter (for example, by 1) and / or start a first timer with a first value. In one example, while the first timer is running, the wireless device may monitor a PDCCH on a first set of control resources. In one example, if the wireless device detects a DCI via the PDCCH while the first timer is running, the wireless device may successfully complete the BFR procedure. The wireless device may cancel the (pending) second request associated with the second request configuration. The wireless device may keep a first sr pending, at least associated with the first sr configuration. The first sr may be triggered based on a buffer status report. In response to the successful completion of the BFR procedure, the wireless device may stop the first timer and / or reset the first counter. In exemplary embodiments, the wireless device can keep a first SR pending for a buffer status report procedure and / or cancel a second SR for beam fault recovery based on the reception of a response to the second SR. Exemplary embodiments can increase uplink transmission spectral efficiency, reduce beam fault recovery latency, reduce uplink transmission power, and / or reduce uplink transmission interference.

[0195] In one example, a wireless device detects a DCI via a PDCCH on a first set of control resources distinct from a second set of control resources for beam fault recovery. A DCI may include an uplink permission. In response to receiving a DCI, the wireless device may continue to hold the request for beam fault recovery and / or cancel the SR for a buffer status report.

[0196] For example, if a DCI received on the PDCCH includes one or more uplink grants, the radio device may cancel a first (pending) request associated with a first request configuration and a second (pending) sr associated with at least a second sr configuration. For example, one or more uplink grants may correspond to pending data available for transmission. For example, if a DCI received on the PDCCH includes one or more downlink assignments, the radio device may cancel a first (pending) request associated with a first request configuration and keep a second sr associated with at least a second sr configuration pending. The first sr may be triggered based on a buffer status report.

[0197] For example, if the wireless device does not identify a valid PUCCH resource for the transmission of the second request according to the configuration parameters of the second request configuration, for example, if the first PUCCH resource is released, the wireless device may initiate a beam fault recovery or a random access procedure for the first random access procedure. The wireless device may continue to hold the first request associated with the first request configuration. The first SR may be triggered based on a buffer status report. The wireless device may cancel the second SR associated with at least the second SR configuration.

[0198] In one example, if the first counter shows a number greater than or equal to a first transmission count, the wireless device may complete the BFR procedure with failure. In one example, a lower layer of the wireless device (e.g., the MAC layer or PHY layer) may indicate the failure of the BFR procedure to a higher layer of the wireless device (e.g., the RRC layer). In one example, the wireless device may cancel a second request associated with a second request configuration. In one example, the wireless device may cancel a first (pending) sr associated with at least a first sr configuration. The first sr may be triggered based on a buffer status report.

[0199] In one example, if a first counter indicates a number greater than or equal to a first number of transmissions, the wireless device may initiate a random access procedure for beam fault recovery. For example, the random access procedure for beam fault recovery may be implemented as shown in the example in Figure 17. In one example, in response to the first counter indicating a number greater than or equal to a first number of transmissions, the wireless device may cancel a second request associated with a second request configuration. In one example, unlike existing SR techniques, the wireless device may, in response to the first counter indicating a number greater than or equal to a first number of transmissions, continue to hold a first SR associated with at least a first SR configuration. The first SR may be triggered based on a buffer status report. In an exemplary embodiment, the wireless device may continue to hold a first SR for a buffer status report procedure and / or cancel a second SR for beam fault recovery when the wireless device reaches the maximum number of SR transmissions for beam fault recovery. The exemplary embodiment can increase uplink transmission spectral efficiency, reduce beam fault recovery latency, reduce uplink transmission power, and / or reduce uplink transmission interference.

[0200] For example, if the first counter indicates a number greater than or equal to the first transmission count, the wireless device may notify its upper layer (e.g., RRC) to release the first PUCCH resource, and all PUCCH resources may include at least a second PUCCH resource for all serving cells. The wireless device may also notify its upper layer to release the SRS for all serving cells. The wireless device may also clear any configured downlink allocations and uplink permissions.

[0201] In one example, a gNB can transmit at least one message containing parameters indicating a first set of RS and a second set of RS. The first set of RS allows the gNB to identify the beam on which it transmits PDCCH / PDSCH and one or more beams that have been QCL'd. The second set of RS allows the radio device to identify one or more candidate beams that are of better quality than a threshold when one or more beams associated with the first set of RS fail.

[0202] In one example, at least one message may include configuration parameters for a first request configuration associated with a BFR procedure. The first request configuration may be associated with at least one of a first PUCCH resource, a first periodicity of the request transmission, and / or a first offset of the request transmission.

[0203] For example, at least one message may include configuration parameters for a PRACH configuration with a BFR procedure. The configuration parameters may include at least one of the following from a second set of RS: RS index, preamble index, time resource index, and frequency resource index.

[0204] In one example, at least one message may include at least one of a first timer having a first value, a first transmission count, or a first control resource set. In one example, a wireless device may maintain a first counter associated with a BFR procedure. The first counter may be initialized to a first value (e.g., zero).

[0205] In one example, once a wireless device identifies at least one beam fault instance on a first set of RSs, the wireless device can select a candidate beam from a second set of RSs. In another example, the wireless device can decide whether to (re)transmit the first request or PRACH based on the availability of a first PUCCH resource for the first request and PRACH resources for the PRACH configuration. PRACH resources may include a preamble index, a time resource index, and a frequency resource index.

[0206] Figure 22 shows an example of an embodiment in which, upon selection of a candidate beam in response to the triggering of the BFR procedure, the wireless device may decide to (re)transmit the first request of the first request configuration if, upon comparison with the PRACH resource associated with the candidate beam, the first PUCCH resource of the first request configuration is available first. For example, the wireless device may decide to (re)transmit the preamble via the PRACH resource if, upon comparison with the first PUCCH resource of the first request configuration, the PRACH resource associated with the candidate beam is available first. In the exemplary embodiment, the wireless device can perform the beam fault recovery procedure by selecting an SR resource or RACH resource for the transmission or retransmission of the beam fault recovery request message. The exemplary embodiment can increase uplink transmission spectral efficiency, reduce beam fault recovery latency, reduce uplink transmission power, and / or reduce uplink transmission interference.

[0207] In one example, when a wireless device transmits a first request or PRACH of a first request configuration, the wireless device may increment a first counter (for example, by 1) and start a first timer. In one example, while the first timer is running, the wireless device may monitor a PDCCH on a first control resource set. Upon detecting a DCI on the PDCCH, the wireless device may successfully complete the BFR procedure.

[0208] In one example, if no DCI is detected while the first timer is operating, the wireless device can determine the next transmission opportunity based on the availability of the first PUCCH resource and the PRACH resource in the PRACH configuration. For example, if the first PUCCH resource for the first request is available first when compared with the PRACH resource, the wireless device can decide to transmit the PUCCH signal at the next transmission opportunity. For example, if the PRACH resource is available first when compared with the first PUCCH resource for the first request, the wireless device can decide to transmit the PRACH at the next transmission opportunity. In one example, the wireless device can increment a first counter (e.g., one by one) in response to transmitting a PUCCH signal or a PRACH. In an exemplary embodiment, the wireless device can perform a beam fault recovery procedure by treating SR-based beam fault recovery and RACH-based beam fault recovery as a single process (e.g., by maintaining a single retransmission counter for both RACH-based beam fault recovery and SR-based beam fault recovery). Exemplary embodiments can increase uplink transmission spectral efficiency, reduce beam fault recovery latency, reduce uplink transmission power, and / or reduce uplink transmission interference.

[0209] In one example, if the first counter shows a value greater than or equal to a first transmission count, the wireless device may complete the BFR procedure with failure. The wireless device may cancel the pending request of the first request configuration. The wireless device may indicate the BFR failure to a higher layer (e.g., the RRC layer). By implementing the embodiment, the wireless device can improve the latency of the BFR procedure. The wireless device may select an uplink resource (e.g., a PUCCH resource or a PRACH resource) that is available at an earlier time to transmit the BFR signal.

[0210] In one example, a wireless device may receive at least one message from a base station containing configuration parameters for a cell (e.g., PCell or SCell). The configuration parameters may represent at least a first request configuration and at least a second sr configuration. In one example, the at least first request configuration may be identified by one or more first PUCCH resources. The at least second sr configuration may be identified by one or more second PUCCH resources. In one example, the at least first request configuration may be associated with a BFR procedure. In one example, the at least second sr configuration may be associated with a logical channel.

[0211] In one example, a wireless device may trigger a first request of at least a first sr configuration in response to a BFR procedure being initiated on a cell (e.g., a PCell or SCell). In another example, a wireless device may trigger a second sr of at least a second sr configuration associated with a logical channel triggering a BSR.

[0212] In one example, a wireless device may, in response to triggering a first request, transmit the first request through one or more first PUCCH resources. In another example, a wireless device may, in response to triggering a second sr, transmit a second sr through one or more second PUCCH resources.

[0213] In one example, the wireless device may cancel the first request in response to receiving the first downlink control information. In another example, the wireless device may hold the second sr in a pending state in response to receiving the first downlink control information.

[0214] In one example, at least one message may further include at least one or more first RS resources and / or one or more second RS resources. Each of the one or more second RS resources may be associated with each of the one or more first PUCCH resources.

[0215] In one example, at least a first request configuration may be associated with a first request resource configuration index identified by at least a first timer, a first transmission amber, a first periodicity, and a first offset. In another example, at least a second sr configuration may be associated with an associated second sr resource configuration index identified by at least a second timer, a second transmission amber, a second period, and a second offset.

[0216] For example, initiating a BFR procedure may include measuring at least one downlink control channel based on one or more first RS resources having a signal intensity lower than a first threshold, and selecting a preferred RS from one or more second RSs based on a second threshold.

[0217] In one example, the first PUCCH resource may be a PUCCH resource associated with the selected RS.

[0218] The embodiments may be configured to operate as needed. The disclosed mechanisms may be executed when certain criteria are met, for example, in a wireless device, base station, wireless environment, network, or a combination thereof. Illustrative criteria may be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system configuration, packet size, traffic characteristics, or a combination thereof. Various exemplary embodiments may be applied when one or more criteria are met. Therefore, it may be possible to implement exemplary embodiments that selectively implement the disclosed protocols.

[0219] A base station can communicate with various radio devices. Radio devices and / or base stations may support multiple technologies and / or multiple releases of the same technology. A radio device may have several specific capabilities depending on the category and / or capabilities of the radio device. A base station may include multiple sectors. Where this disclosure refers to a base station that communicates with multiple radio devices, this disclosure may refer to a subset of all radio devices in a coverage area. This disclosure may refer, for example, to multiple radio devices of a given LTE or 5G release that have a given capability and are located in a given sector of a base station. Multiple radio devices in this disclosure may refer to a subset of selected radio devices and / or all radio devices in a coverage area that operate according to the disclosed method, etc. For example, there may be multiple base stations or multiple radio devices in a coverage area that do not comply with the disclosed method because those radio devices or base stations operate based on an older release of LTE or 5G technology.

[0220] According to various embodiments, a device such as a wireless device, an off-network wireless device, a base station, and / or the like may comprise one or more processors and memory. The memory may store instructions that, when executed by one or more processors, cause the device to perform a series of actions. Exemplary embodiments of actions are shown in the accompanying figures and specification. Further embodiments can be created by combining features from various embodiments.

[0221] Figure 23 is an exemplary flowchart according to one embodiment of the present disclosure. In 2310, the wireless device may transmit a first scheduling request (SR) based on a buffer status report procedure. In 2330, a second SR may be triggered in response to initiating beam fault recovery (2320). In 2340, the second SR may be transmitted via an uplink control channel resource configured for the second SR. In 2350, first downlink control information may be received via the downlink control channel in response to the second SR. Based on the receipt of the first downlink control information, the first SR may remain pending in 2360, and the second SR for beam fault recovery may be canceled in 2370. According to the exemplary embodiment, in response to canceling the second SR (2370), beam fault recovery may be completed in 2380.

[0222] According to an exemplary embodiment, the uplink control channel resource includes a frequency radio resource. According to an exemplary embodiment, the uplink control channel resource includes an uplink control channel format. According to an exemplary embodiment, the uplink control channel resource includes a cyclic shift of the base sequence. According to an exemplary embodiment, the uplink control channel resource includes a time radio resource. According to an exemplary embodiment, the first downlink control information may include a downlink assignment. According to an exemplary embodiment, the first downlink control information may include an uplink grant. According to an exemplary embodiment, one or more messages may be received that include first configuration parameters for a first group of SRs, including a first SR. According to an exemplary embodiment, one or more messages may be received that include second configuration parameters for a second SR. According to an exemplary embodiment, the radio device can trigger a second SR based on the second configuration parameter. According to an exemplary embodiment, the second configuration parameter may indicate an uplink control channel resource for the second SR. According to an exemplary embodiment, the radio device can initiate beam fault recovery in response to detecting the number of beam fault instances. According to an exemplary embodiment, a wireless device can detect the number of beam fault instances in response to the channel quality of one or more reference signal resources being lower than one or more first thresholds. According to an exemplary embodiment, the wireless device can further select a first reference signal from a plurality of reference signals based on one or more second thresholds in response to initiating beam fault recovery. According to an exemplary embodiment, a second SR can indicate the reference signal received power value of the first reference signal. According to an exemplary embodiment, a second SR can indicate that the number of beam fault instances has been detected. According to an exemplary embodiment, a second SR can indicate that the first reference signal has been selected. According to an exemplary embodiment, a downlink control channel may be monitored for first downlink control information.According to exemplary embodiments, a wireless device can monitor a downlink control channel on at least one set of control resources of the downlink control channel. According to exemplary embodiments, a wireless device can monitor a downlink control channel on at least one search space of the downlink control channel. According to exemplary embodiments, a downlink control channel may be associated with a second SR. According to exemplary embodiments, a downlink control channel associated with a second SR may include the determination of at least one set of control resources of the downlink control channel based on the second SR. According to exemplary embodiments, a downlink control channel associated with a second SR may include the determination of at least one search space of the downlink control channel based on the second SR. According to exemplary embodiments, a first SR may be transmitted via a second uplink control channel resource configured for the first SR in response to holding the first SR in a pending state. According to exemplary embodiments, it further includes the reception of one or more second downlink control information, including one or more uplink permissions, via the second downlink control channel. According to an exemplary embodiment, the first SR may be canceled in response to one or more uplink permissions corresponding to data available for uplink transmission.

[0223] Figure 24 is an exemplary flowchart according to one embodiment of the present disclosure. At 2410, the wireless device may transmit a first scheduling request (SR) based on a buffer status report procedure. At 2430, a second SR may be triggered based on initiating beam fault recovery (2420). At 2440, the second SR may be transmitted. At 2450, in response to the second SR, first downlink control information may be received. Based on receiving the first downlink control information, the first SR may remain pending at 2460 and the second SR may be canceled at 2470.

[0224] Figure 25 is an exemplary flowchart based on one aspect of an embodiment of the present disclosure. In 2510, a base station may transmit one or more radio resource control messages. One or more radio resource control messages may include cell configuration parameters. A cell may be a PCell or SCell. The configuration parameters may indicate a first scheduling request (SR) configuration associated with a logical channel. The configuration parameters may indicate a second SR configuration associated with beam fault recovery. In 2520, a first SR based on the first SR configuration may be received via a first uplink control resource based on a buffer status report procedure. In 2530, a second SR based on a second SR configuration may be received via a second uplink control resource for beam fault recovery. In 2540, a control resource set up for the transmission of downlink control information may be determined in response to the second SR. In 2550, downlink control information, including one or more uplink permissions, may be transmitted via a downlink control channel on a control resource set based on the first and second SRs.

[0225] According to exemplary embodiments, a first SR configuration may include a first uplink control resource. According to exemplary embodiments, a second SR configuration may include a second uplink control resource. According to exemplary embodiments, a first uplink control resource may include a first frequency radio resource. According to exemplary embodiments, a first uplink control resource may include a first uplink control channel format. According to exemplary embodiments, a first uplink control resource may include a first cyclic shift of the basic sequence. According to exemplary embodiments, a first uplink control resource may include a first time radio resource. According to exemplary embodiments, a second uplink control resource may include a second frequency radio resource. According to exemplary embodiments, a second uplink control resource may include a second uplink control channel format. According to exemplary embodiments, a second uplink control resource may include a second cyclic shift of the basic sequence. According to exemplary embodiments, a second uplink control resource may include a second time radio resource. According to an exemplary embodiment, the second SR may indicate the reference signal received power value of the first reference signal. According to an exemplary embodiment, the second SR may indicate that a number of beam fault instances has been detected. According to an exemplary embodiment, the second SR may indicate that the first reference signal has been selected. According to an exemplary embodiment, the wireless device may initiate beam fault recovery in response to the detection of the number of beam fault instances. According to an exemplary embodiment, the wireless device may detect the number of beam fault instances in response that the channel quality of one or more reference signal resources is lower than one or more first thresholds. According to an exemplary embodiment, the first reference signal may be selected from a plurality of reference signals based on one or more second thresholds in response to initiating beam fault recovery. According to an exemplary embodiment, the second SR may indicate the reference signal received power value of the first reference signal.According to an exemplary embodiment, the second SR may indicate that the number of beam fault instances has been detected. According to an exemplary embodiment, the second SR may indicate that the first reference signal has been selected.

[0226] Figure 26 is an exemplary flowchart based on one aspect of an embodiment of the present disclosure. In 2610, a first SR based on a first SR configuration associated with a logical channel may be received via a first uplink control resource based on a buffer status report procedure. In 2620, a second SR based on a second SR configuration associated with beam fault recovery may be received via a second uplink control resource for beam fault recovery. In 2630, a control resource configured for the transmission of downlink control information may be determined in response to the second SR. In 2640, downlink control information, including uplink permission, may be transmitted via a set of control resources based on the first and second SRs.

[0227] Figure 27 is an exemplary flowchart based on one aspect of an embodiment of the present disclosure. In 2720, a wireless device may trigger a scheduling request in response to initiating beam fault recovery (2710). In 2730, a reference signal may be determined from a plurality of reference signals. In 2740, uplink control information for the scheduling request may be transmitted via an uplink control channel resource. The uplink control information may include a reference signal identifier indicating the reference signal. The uplink control information may include a reference signal received power value for the reference signal. In 2750, in response to the uplink control information, downlink control information may be received via a downlink control channel on a control resource set associated with beam fault recovery. In 2760, the scheduling request may be canceled based on the downlink control information. In 2785, beam fault recovery may be completed in response to the cancellation of the scheduling request.

[0228] According to exemplary embodiments, a wireless device can determine a reference signal based on one or more thresholds. According to exemplary embodiments, one or more messages may be received that include a first configuration parameter of a scheduling request configuration associated with beam fault recovery. The first configuration parameter may indicate an uplink control channel resource for the scheduling request. According to exemplary embodiments, one or more configuration parameters of the uplink control channel resource may include a frequency wireless resource. According to exemplary embodiments, one or more configuration parameters of the uplink control channel resource may include an uplink control channel format. According to exemplary embodiments, one or more configuration parameters of the uplink control channel resource may include a cyclic shift of the base sequence. According to exemplary embodiments, one or more configuration parameters of the uplink control channel resource may include a time wireless resource. According to exemplary embodiments, one or more configuration parameters of a control resource set may include a control resource set index. According to exemplary embodiments, one or more configuration parameters of a control resource set may include a symbol count. According to exemplary embodiments, one or more configuration parameters of a control resource set may include a set of resource blocks. According to exemplary embodiments, one or more configuration parameters of a control resource set may include a control channel element versus resource element group mapping representation. According to exemplary embodiments, downlink control information may include downlink radio resource allocation for downlink transport block transmission. According to exemplary embodiments, downlink control information may include uplink authorization for uplink transport block transmission. According to exemplary embodiments, a radio device may initiate beam fault recovery in response to detecting the number of beam fault instances. According to exemplary embodiments, a radio device may detect the number of beam fault instances in response to the channel quality of one or more reference signal resources being lower than one or more thresholds.According to an exemplary embodiment, one or more messages may be received that include a first configuration parameter of a scheduling request configuration associated with beam fault recovery, in which case the first configuration parameter indicates a control resource set for beam fault recovery. According to an exemplary embodiment, one or more messages may include a second configuration parameter of at least a second scheduling request configuration associated with a logical channel, in which case the second configuration parameter indicates a second uplink control channel resource. According to an exemplary embodiment, the second scheduling request may be transmitted based on at least a second scheduling request configuration for a buffer status reporting procedure of a logical channel. According to an exemplary embodiment, a wireless device can transmit the second scheduling request via a second uplink control channel resource. According to an exemplary embodiment, the downlink control channel may be monitored on the control resource set in a response window in response to the transmission of uplink control information for beam fault recovery. According to an exemplary embodiment, the duration of the response window may be configured in a wireless resource control message. According to an exemplary embodiment, the response window may include a timer having a timer value. According to an exemplary embodiment, the response window may be started in response to the transmission of uplink control information. According to exemplary embodiments, uplink control information may be retransmitted in response to not receiving a response within a response window. According to exemplary embodiments, a request counter may be incremented in response to not receiving a response within a response window. According to exemplary embodiments, a scheduling request may be canceled in response to the request counter being greater than or equal to a first value. According to exemplary embodiments, beam fault recovery may be completed in response to canceling a scheduling request.

[0229] Figure 28 is an exemplary flowchart based on one aspect of an embodiment of the present disclosure. In 2820, a wireless device may trigger a scheduling request based on initiating beam fault recovery (2810). In 2830, a reference signal may be determined from a plurality of reference signals. In 2840, uplink control information for the scheduling request may be transmitted via an uplink control channel resource. In 2850, downlink control information based on the uplink control information may be received via a set of control resources associated with beam fault recovery. In 2860, the scheduling request may be canceled based on the downlink control information. In 2870, beam fault recovery may be completed in response to the cancellation of the scheduling request.

[0230] Figure 29 is an exemplary flowchart based on one aspect of an embodiment of the present disclosure. At 2910, a wireless device may transmit a first scheduling request (SR) based on a buffer status report procedure. At 2930, a second SR may be triggered in response to initiating beam fault recovery (2920). At 2940, the second SR may be transmitted via an uplink resource configured for the second SR. At 2950, ​​first downlink control information may be received in response to the second SR. Based on the first downlink control information including uplink permission (2960), at 2970, the first SR may be canceled, and at 2980, the second SR for beam fault recovery may be canceled.

[0231] According to exemplary embodiments, the uplink resource may include a frequency radio resource. According to exemplary embodiments, the uplink resource may include an uplink control channel format. According to exemplary embodiments, the uplink resource may include a cyclic shift of the base sequence. According to exemplary embodiments, the uplink resource may include a time radio resource. According to exemplary embodiments, beam fault recovery may be completed in response to the cancellation of a second SR. According to exemplary embodiments, one or more messages may be received that include first configuration parameters for a first group of SRs, including a first SR. According to exemplary embodiments, one or more messages may be received that include second configuration parameters for a second SR. According to exemplary embodiments, the radio device may trigger a second SR based on the second configuration parameter. According to exemplary embodiments, the second configuration parameter may indicate an uplink resource for an uplink control channel for the second SR. According to exemplary embodiments, the radio device may initiate beam fault recovery in response to detecting the number of beam fault instances. According to exemplary embodiments, the radio device may detect the number of beam fault instances in response to the channel quality of one or more reference signal resources being lower than one or more first thresholds. According to an exemplary embodiment, the first reference signal may be selected from a plurality of reference signals based on one or more second thresholds in response to initiating beam fault recovery. According to an exemplary embodiment, the second SR may indicate the reference signal received power value of the first reference signal. According to an exemplary embodiment, the second SR may indicate that a number of beam fault instances has been detected. According to an exemplary embodiment, the second SR may indicate that the first reference signal has been selected. According to an exemplary embodiment, the downlink control channel may be monitored for first downlink control information. According to an exemplary embodiment, the wireless device may monitor the downlink control channel on at least one set of control resources of the downlink control channel.According to an exemplary embodiment, a wireless device can monitor a downlink control channel on at least one search space of the downlink control channel. According to an exemplary embodiment, a downlink control channel may be associated with a second SR. According to an exemplary embodiment, a downlink control channel may be associated with the second SR including the fact that at least one set of control resources for the downlink control channel is determined based on the second SR. According to an exemplary embodiment, a downlink control channel may be associated with the second SR including the fact that at least one search space for the downlink control channel is determined based on the second SR.

[0232] Figure 30 is an exemplary flowchart based on one aspect of an embodiment of the present disclosure. In 3010, a wireless device can transmit a first scheduling request (SR) based on a buffer status report procedure. In 3030, a second SR may be triggered in response to initiating beam fault recovery (3020). In 3040, the second SR may be transmitted via an uplink resource configured for the second SR. In 3050, first downlink control information may be received in response to the second SR. Based on the first downlink control information including a downlink allocation (3060), in 3070, the first SR may remain pending, and in 3080, the second SR for beam fault recovery may be canceled.

[0233] According to exemplary embodiments, the uplink resource may include a frequency radio resource. According to exemplary embodiments, the uplink resource may include an uplink control channel format. According to exemplary embodiments, the uplink resource may include a cyclic shift of the base sequence. According to exemplary embodiments, the uplink resource may include a time radio resource. According to exemplary embodiments, beam fault recovery may be completed in response to the cancellation of a second SR. According to exemplary embodiments, one or more messages may be received that include first configuration parameters for a first group of SRs, including a first SR. According to exemplary embodiments, one or more messages may be received that include second configuration parameters for a second SR. According to exemplary embodiments, the radio device may trigger a second SR based on the second configuration parameter. According to exemplary embodiments, the second configuration parameter may indicate an uplink resource for an uplink control channel for the second SR. According to exemplary embodiments, the radio device may initiate beam fault recovery in response to detecting the number of beam fault instances. According to exemplary embodiments, the radio device may detect the number of beam fault instances in response to the channel quality of one or more reference signal resources being lower than one or more first thresholds. According to exemplary embodiments, a first reference signal may be selected from a plurality of reference signals based on one or more second thresholds in response to initiating beam fault recovery. According to exemplary embodiments, a second SR may indicate the reference signal received power value of the first reference signal. According to exemplary embodiments, a second SR may indicate that a number of beam fault instances has been detected. According to exemplary embodiments, a second SR may indicate that the first reference signal has been selected. According to exemplary embodiments, a downlink control channel may be monitored for first downlink control information. According to exemplary embodiments, a wireless device may monitor the downlink control channel on at least one set of control resources of the downlink control channel.According to an exemplary embodiment, a wireless device can monitor a downlink control channel on at least one search space of downlink control channels. According to an exemplary embodiment, a downlink control channel may be associated with a second SR. According to an exemplary embodiment, it is determined based on the second SR that a downlink control channel associated with a second SR may include at least one set of control resources for downlink control channels. According to an exemplary embodiment, it is determined based on the second SR that a downlink control channel associated with a second SR may include at least one search space of downlink control channels. According to an exemplary embodiment, a first SR may be transmitted via a second uplink control channel resource configured for the first SR in response to holding the first SR in a pending state. According to an exemplary embodiment, one or more second downlink control pieces of information, including one or more uplink grants, may be received via the second downlink control channel. According to an exemplary embodiment, a first SR may be canceled in response to one or more uplink grants corresponding to data available for uplink transmission.

[0234] Figure 31 is an example of a flowchart according to one embodiment of the present disclosure. At 3110, a wireless device may trigger a first scheduling request (SR) based on a buffer status report procedure. At 3130, a second SR may be triggered based on initiating beam fault recovery (3120). At 3140, the second SR may be transmitted over an uplink resource associated with the second SR. At 3150, a downlink control channel may be monitored for responses to the second SR. Based on the SR counter being greater than or equal to a first value (3160), at 3170, the second SR may be canceled, at 3180, the first SR may remain pending, and at 3190, a random access procedure for beam fault recovery may be initiated.

[0235] According to exemplary embodiments, the uplink resource includes a frequency radio resource. According to exemplary embodiments, the uplink resource includes an uplink control channel format. According to exemplary embodiments, the uplink resource includes a cyclic shift of the base sequence. According to exemplary embodiments, the uplink resource includes a time radio resource. According to exemplary embodiments, beam fault recovery may be completed in response to canceling a second SR. According to exemplary embodiments, one or more messages may be received that include first configuration parameters for a first plurality of SRs, including a first SR. According to exemplary embodiments, one or more messages may be received that include second configuration parameters for a second SR. According to exemplary embodiments, the radio device can trigger a second SR based on the second configuration parameter. According to exemplary embodiments, the second configuration parameter may indicate an uplink resource for an uplink control channel for the second SR. According to exemplary embodiments, the radio device can initiate beam fault recovery in response to detecting a number of beam fault instances. According to exemplary embodiments, the radio device can detect a number of beam fault instances in response to the channel quality of one or more reference signal resources being lower than one or more first thresholds. According to an exemplary embodiment, the first reference signal may be selected from a plurality of reference signals based on one or more second thresholds in response to initiating beam fault recovery. According to an exemplary embodiment, the second SR may indicate the reference signal received power value of the first reference signal. According to an exemplary embodiment, the second SR may indicate that a number of beam fault instances has been detected. According to an exemplary embodiment, the second SR may indicate that the first reference signal has been selected. According to an exemplary embodiment, the downlink control channel may be monitored or responded to. According to an exemplary embodiment, the wireless device may monitor the downlink control channel on at least one set of control resources of the downlink control channel.According to an exemplary embodiment, a wireless device can monitor a downlink control channel on at least one search space of the downlink control channel. According to an exemplary embodiment, the downlink control channel may be associated with a second SR. According to an exemplary embodiment, it is determined based on the second SR that the downlink control channel may be associated with a second SR that includes at least one set of control resources for the downlink control channel. According to an exemplary embodiment, it is determined based on the second SR that the downlink control channel may be associated with a second SR that includes at least one search space of the downlink control channel. According to an exemplary embodiment, a wireless device can monitor a downlink control channel in a response window. According to an exemplary embodiment, the size of the response window may consist of RRC messages. According to an exemplary embodiment, an SR counter may be incremented based on not receiving a response in the response window. According to an exemplary embodiment, the first SR may be transmitted via a second uplink control channel resource configured for the first SR in response to holding the first SR in a pending state. According to an exemplary embodiment, one or more second downlink control information, including one or more uplink permissions, may be received via a second downlink control channel. According to an exemplary embodiment, the first SR may be canceled in response to one or more uplink permissions corresponding to data available for uplink transmission.

[0236] Figure 32 is an example of a flowchart according to one embodiment of the present disclosure. At 3220, the wireless device may initiate beam fault recovery based on detecting the number of beam fault instances (3210). At 3230, a preamble may be transmitted via a random access channel resource and in response to initiating beam fault recovery. At 3245, a request transmission counter may be incremented in response to not receiving a first response to the preamble (3240). At 3250, uplink control information for beam fault recovery may be transmitted via an uplink control channel resource. At 3270, the request transmission counter may be incremented in response to not receiving a second response to the uplink control information (3260). At 3290, beam fault recovery may be completed in response to the request transmission counter being greater than or equal to a first value (3280).

[0237] According to an exemplary embodiment, a wireless device can detect the number of beam fault instances in response to the channel quality of one or more reference signal resources being lower than one or more first thresholds. According to an exemplary embodiment, the uplink control channel resource may include a frequency wireless resource. According to an exemplary embodiment, the uplink control channel resource may include an uplink control channel format. According to an exemplary embodiment, the uplink control channel resource may include a cyclic shift of the base sequence. According to an exemplary embodiment, the uplink control channel resource may include a time wireless resource. According to an exemplary embodiment, the first reference signal, based on one or more second thresholds, may be selected from a plurality of reference signals in response to initiating beam fault recovery. According to an exemplary embodiment, a random access channel resource may be associated with the first reference signal. According to an exemplary embodiment, the response window may begin at a first time value based on transmitting a preamble. According to an exemplary embodiment, when the response window expires, the wireless device may increment a request transmission counter in response to not receiving a first response to the preamble. According to an exemplary embodiment, the response window may begin at a time value in response to the transmission of uplink control information. According to an exemplary embodiment, when the response window expires, the wireless device may increment a request transmission counter in response to not receiving a second response to the uplink control information.

[0238] Figure 33 is an example of a flowchart according to one embodiment of the present disclosure. At 3320, a preamble may be transmitted via a random access channel resource based on initiating beam fault recovery (3310). At 3340, a request transmission counter may be incremented based on not receiving a first response to the preamble (3330). At 3350, uplink control information for beam fault recovery may be transmitted via an uplink control channel resource. At 3370, beam fault recovery may be completed based on the request transmission counter being greater than or equal to a first value (3360).

[0239] Figure 34 is an example of a flowchart according to one embodiment of the present disclosure. In 3420, a preamble for beam fault recovery may be transmitted via the first random access channel resource, based on the fact that the first random access channel resource is faster than the first uplink control channel resource (3410). In 3450, uplink control information for beam fault recovery may be transmitted via the second uplink control channel resource, based on the fact that no response to the preamble is received during the response window (3430) and that the second uplink control channel resource is faster than the second random access channel resource (3440).

[0240] According to exemplary embodiments, the first uplink control channel resource may include a frequency radio resource. According to exemplary embodiments, the first uplink control channel resource may include an uplink control channel format. According to exemplary embodiments, the first uplink control channel resource may include a cyclic shift of the base sequence. According to exemplary embodiments, the first uplink control channel resource may include a time radio resource. According to exemplary embodiments, the response window may be initiated in response to the transmission of a preamble. According to exemplary embodiments, the response window may be initiated in response to the transmission of uplink control information. According to exemplary embodiments, beam fault recovery may be initiated based on the detection of the number of beam fault instances. According to exemplary embodiments, the radio device can detect the number of beam fault instances in response to the channel quality of one or more reference signal resources being lower than one or more first thresholds. According to exemplary embodiments, the first reference signal based on one or more second thresholds may be selected from a plurality of reference signals in response to initiating beam fault recovery. According to exemplary embodiments, the first random access channel resource may be associated with the first reference signal. According to an exemplary embodiment, the first uplink control channel resource may be associated with a first reference signal.

[0241] Figure 35 is an example of a flowchart according to one embodiment of the present disclosure. At 3520, the wireless device may initiate beam fault recovery based on detecting the number of beam fault instances (3510). At 3530, in response to initiating beam fault recovery (3520), a decision may be made that the first random access channel resource is faster than the first uplink control channel resource. At 3540, a preamble for beam fault recovery may be transmitted over the first random access channel resource. At 3550, the downlink control channel may be monitored for a response to the preamble. At 3570, in response to not receiving a response (3560), a decision may be made that the second uplink control channel resource is faster than the second random access channel resource. At 3580, uplink control information for beam fault recovery may be transmitted over the second uplink control channel resource.

[0242] In this disclosure, “a” and “an” and similar phrases should be interpreted as “at least one” and “one or more.” Similarly, any term ending in the suffix “(s)” should be interpreted as “at least one” and “one or more.” In this disclosure, the term “may” should be interpreted as “may, for example.” In other words, the term “may” implies that the phrase following the term “may” is one example of a number of preferred possibilities in which it may or may not be used in one or more of the various embodiments.

[0243] If A and B are a set, and every element of A is also an element of B, then A is called a subset of B. In this specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {cell 1, cell 2} are {cell 1}, {cell 2}, and {cell 1, cell 2}. The phrase "based on" (or equivalently "at least based on") indicates that the phrase following the term "based on" is one example of many preferred possibilities in which one or more of the various embodiments may or may not be used. The phrase "in response to" (or equivalently "at least in response to") indicates that the phrase following the phrase "in response to" is one example of many preferred possibilities in which one or more of the various embodiments may or may not be used. The phrase "according to" (or equivalently "at least in response to") indicates that the phrase following the phrase "according to" is one example of many preferred possibilities in which one or more of the various embodiments may or may not be used. The phrase “use” (or equivalently “at least use”) indicates that the phrase following “use” is one example of a multitude of preferred possibilities in which one or more of the various embodiments may or may not be used.

[0244] The term "configured" may relate to the capacity of a device, regardless of whether the device is operational or non-operational. "Configured" may also refer to specific settings of a device that affect its operational characteristics, regardless of whether the device is operational or non-operational. In other words, hardware, software, firmware, registers, memory values, etc., can be "configured" within a device, regardless of whether the device is operational or non-operational, in order for the device to provide certain characteristics. Terms such as "control messages generated in a device" may mean that control messages, regardless of whether the device is operational or non-operational, have parameters that can be used to configure certain characteristics in the device or to implement certain actions in the device.

[0245] This disclosure discloses various embodiments. Limitations, features, and / or elements from the disclosed exemplary embodiments can be combined to create further embodiments within the scope of this disclosure.

[0246] In this disclosure, a parameter (or equivalently referred to as a field, or information element: IE) may contain one or more information objects, and an information object may contain one or more other objects. For example, if parameter (IE)N contains parameter (IE)M, parameter (IE)M contains parameter (IE)K, and parameter (IE)K contains parameter (information element)J, then for example, N contains K and N contains J. In an exemplary embodiment, when one or more messages contain multiple parameters, it means that one of the multiple parameters is included in at least one of the one or more messages, but not each of the one or more messages.

[0247] Furthermore, many of the features presented above are described as optional by the use of "may" or parentheses. For the sake of brevity and readability, this disclosure does not explicitly describe all possible changes that may result from selecting from a set of optional features. However, this disclosure should be interpreted as explicitly disclosing all such changes. For example, a system described as having three optional features can be embodied in seven different ways: by just one of the three possible features, by any two of the three features, or by all three of the three features.

[0248] Many of the elements described in the disclosed embodiments may be implemented as modules, where a module is defined as an element that performs a defined function and has a defined interface to other elements. Modules described in this disclosure may be implemented in hardware, software combined with hardware, firmware, wetware (i.e., hardware with biological elements), or a combination thereof, all of which can be behaviorally equivalent. For example, a module may be implemented in a hardware machine (such as C, C++, Fortran, Java®, Basic, Matlab) or in software routines written in a computer language configured to run in Simulink, Stateflow, GNU Octave, or LabVIEWMathScript. Furthermore, modules may also be implemented using physical hardware that incorporates discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include computers, microcontrollers, microprocessors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and complex-programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, and C++. FPGAs, ASICs, and CPLDs are often programmed using hardware description languages ​​(HDLs) such as VHSIC (VHDL) or Verilog, which constitute connections between internal hardware modules with limited functionality in the programmable device. These techniques are often used in combination to achieve the results of the functional modules.

[0249] This patent document disclosure incorporates copyrighted material. The copyright holder reserves all other rights, except that anyone may facsimile the patent document or patent disclosure for the limited purposes required by law, as recorded in the patent files or records of the Patent and Trademark Office.

[0250] While various embodiments have been described above, it should be understood that these are presented as examples and are not limiting. It will be apparent to those skilled in the art that various modifications of form and detail can be made without departing from the scope. Indeed, after reading the above specification, methods for implementing alternative embodiments will become apparent to those skilled in the relevant art. Therefore, this embodiment should not be limited by any of the exemplary embodiments described above.

[0251] Furthermore, it should be understood that any diagrams emphasizing features and benefits are presented for illustrative purposes only. The disclosed architecture is sufficiently flexible and configurable to be used in ways other than those shown. For example, any actions listed in any flowchart may be rearranged in several embodiments or used only as optional.

[0252] Furthermore, the purpose of this summary is to enable the U.S. Patent and Trademark Office and the general public, in particular scientists, engineers, and practitioners in the relevant art who are not familiar with patent or legal terminology, to quickly grasp the nature and essence of the technical disclosure of this application at a glance. This summary is not intended to limit the scope in any way.

[0253] Finally, it is the applicant's intention that only claims containing the phrase “means for” or “steps for” should be interpreted under Section 112 of the United States Patent Act. Claims that do not explicitly contain the phrase “means for” or “steps for” should not be interpreted under Section 112 of the United States Patent Act.

Claims

1. It is a base station, One or more processors, Memory for storing instructions and The instruction is provided, and when it is executed by one or more processors, Receiving a first scheduling request (SR) based on the buffer status report procedure, Receiving a second SR from the wireless device, triggered in response to initiating beam fault recovery, Transmitting the first downlink control information (DCI) via the downlink control channel as a response to the second SR, In response to transmitting the first DCI, Having received another transmission of the first SR, To determine that no further transmission by the wireless device of the second SR for beam fault recovery is detected. A base station that causes the aforementioned base station to perform the above.

2. When the instruction is executed by one or more processors, The first configuration parameters of the first plurality of SRs, including the first SR, The second configuration parameter of the second SR and The base station according to claim 1, further causing the base station to transmit one or more messages including at least one of the following.

3. The base station according to claim 1, wherein the instruction, when executed by one or more processors, causes the base station to receive the first SR, includes, when executed by one or more processors, an instruction causing the base station to receive the first SR via a second uplink control channel resource configured for the first SR.

4. The base station according to claim 1, wherein the first DCI includes an uplink grant instruction, which, when executed by one or more processors, causes the base station to further receive a buffer status report via the uplink resource associated with the uplink grant.

5. The following steps are performed by the base station: The steps include receiving a first scheduling request (SR) based on a buffer status report procedure, The steps include receiving a second SR from a wireless device, which is triggered in response to initiating beam fault recovery, The steps include transmitting first downlink control information via the downlink control channel as a response to the second SR, In response to transmitting the first downlink control information, Having received another transmission of the first SR, The step of determining that no other transmission of the second SR by the wireless device for beam fault recovery is detected. A method that includes this.

6. The first configuration parameters of the first plurality of SRs, including the first SR, The second configuration parameter of the second SR and The method according to claim 5, further comprising transmitting one or more messages, each containing at least one of the following:

7. The method according to claim 5, wherein receiving the first SR includes receiving the first SR via a second uplink control channel resource configured for the first SR.

8. The method according to claim 5, wherein the first DCI includes uplink authorization and further includes receiving a buffer status report via the uplink resource associated with the uplink authorization.

Images