Scheduling request transmitting method and terminal

Abstract

Embodiments of this disclosure provide a scheduling request transmitting method and a terminal. The scheduling request transmitting method includes: in a case that a first trigger condition is met, transmit a scheduling request SR to a network device (201); and in a case that a second trigger condition is met, cancel transmission of the SR, or skip transmission of the SR for N times, where N is an integer greater than 1 (202).

Description

Scheduling request sending method, scheduling request receiving method, terminal and network device

[0001] Cross-references to related applications

[0002] This application claims priority to Chinese Patent Application No. 201910626768.2, filed in China on July 11, 2019, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This disclosure relates to the field of communication technology, and in particular to a scheduling request sending method, a scheduling request receiving method, a terminal, and a network device. Background Technology

[0004] In high-frequency communication systems, due to the short wavelength of wireless signals, signal propagation is more easily obstructed, leading to signal interruption. If wireless link reconstruction is employed using related technologies, it is time-consuming; therefore, a beam failure recovery mechanism is introduced. The beam failure recovery (BFR) mechanism in related technologies includes the following four steps:

[0005] First, beam failure detection. The terminal measures the beam failure detection reference signal at the physical layer and determines whether a beam failure event has occurred based on the measurement results.

[0006] Second, new candidate beam identification. The terminal physical layer measures the beam identification reference signal to search for new candidate beams. This step is not mandatory after a beam failure event occurs; it can also be performed beforehand.

[0007] Third, transmit beam failure recovery request (BFRQ) information.

[0008] Fourth, the UE monitors the gNB response for beam failure recovery request.

[0009] During secondary cell beam failure recovery (SCell BFR), a scheduling request (SR) can be used to trigger network devices to configure or instruct uplink grant resources for the terminal, on which BFRQ information is transmitted. However, in related technologies, after the triggering conditions of the SR are met, the terminal will periodically send SRs, which will result in a large resource overhead for SRs.

[0010] Summary of the Invention

[0011] This disclosure provides a scheduling request sending method, a scheduling request receiving method, a terminal, and a network device to solve the problem in related technologies where periodically sending scheduling requests after the triggering conditions of a scheduling request (SR) are met leads to high resource overhead for SRs.

[0012] In a first aspect, embodiments of this disclosure provide a scheduling request sending method, applied to a terminal, comprising:

[0013] If the first triggering condition is met, a scheduling request (SR) is sent to the network device;

[0014] If the second triggering condition is met, the transmission of the SR is canceled or N SR transmissions are skipped, where N is an integer greater than 1.

[0015] Secondly, embodiments of this disclosure also provide a scheduling request receiving method, applied to a network device, comprising:

[0016] The receiving terminal sends a scheduling request (SR) when the first triggering condition is met.

[0017] If the second trigger condition is met, the reception of the SR is stopped or the reception of the SR is skipped N times, where N is an integer greater than 1.

[0018] Thirdly, embodiments of this disclosure also provide a terminal, including:

[0019] The sending module is used to send a scheduling request (SR) to the network device when a first triggering condition is met; and to cancel the sending of the SR or skip the sending of N SRs when a second triggering condition is met, where N is an integer greater than 1.

[0020] Fourthly, embodiments of this disclosure also provide a network device, including:

[0021] The receiving module is used to receive a scheduling request (SR) sent by the terminal when a first triggering condition is met; and to stop receiving the SR or skip receiving the SR N times when a second triggering condition is met, where N is an integer greater than 1.

[0022] Fifthly, embodiments of this disclosure also provide a terminal, including: a memory, a processor, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps in the scheduling request sending method described above.

[0023] In a sixth aspect, embodiments of this disclosure also provide a network device, including: a memory, a processor, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps in the scheduling request receiving method described above.

[0024] In a seventh aspect, embodiments of this disclosure also provide a computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor, it implements the steps of the scheduling request sending method described above, or when the computer program is executed by a processor, it implements the steps of the scheduling request receiving method described above.

[0025] In this embodiment, by setting a second trigger condition, the transmission of the SR (Signal Sending) is canceled or N SR transmissions are skipped when the second trigger condition is met. This reduces the number of SR transmissions, thereby reducing the resource overhead of the SR. At the same time, it reduces terminal power consumption and extends the terminal's standby time. Attached Figure Description

[0026] Figure 1 is a structural diagram of a network system that can be applied to an embodiment of this disclosure;

[0027] Figure 2 is a flowchart of a scheduling request sending method provided in an embodiment of this disclosure;

[0028] Figure 3 is a flowchart of a scheduling request receiving method provided in an embodiment of this disclosure;

[0029] Figure 4 is a structural diagram of a terminal provided in an embodiment of this disclosure;

[0030] Figure 5 is a structural diagram of a network device provided in an embodiment of this disclosure;

[0031] Figure 6 is a structural diagram of another terminal provided in an embodiment of this disclosure;

[0032] Figure 7 is a structural diagram of another network device provided in an embodiment of this disclosure. Detailed Implementation

[0033] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this disclosure. Based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this disclosure.

[0034] The term "comprising," and any variations thereof, used in the specification and claims of this application, is intended to cover a non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not necessarily limited to those explicitly listed, but may include other steps or units not explicitly listed or inherent to such process, method, product, or apparatus. Furthermore, the use of "and / or" in the specification and claims indicates at least one of the connected objects, such as A and / or B, indicating the inclusion of A alone, B alone, or both A and B.

[0035] In this disclosure, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" or "for example" in this disclosure should not be construed as being more alternative or advantageous than other embodiments or designs. Rather, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0036] The embodiments of this disclosure are described below with reference to the accompanying drawings. The scheduling request sending method, scheduling request receiving method, terminal, and network device provided in the embodiments of this disclosure can be applied to a wireless communication system. This wireless communication system can be a fifth-generation (5G) wireless communication system. th This can be a generation (5G) system, or an evolved long term evolution (eLTE) system, or a subsequent evolution communication system.

[0037] Please refer to Figure 1. Figure 1 is a structural diagram of a network system applicable to an embodiment of this disclosure. As shown in Figure 1, it includes a terminal 11 and a network device 12. The terminal 11 can be a user terminal or other terminal-side device, such as a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), mobile internet device (MID), or wearable device. It should be noted that the specific type of terminal 11 is not limited in this embodiment. The network device 12 can be a 5G base station, or a later version of a base station, or a base station in other communication systems, or referred to as a Node B, evolved Node B, Transmission Reception Point (TRP), or Access Point (AP), or other terms in the field, as long as the same technical effect is achieved, the network device is not limited to specific technical terms. In addition, the network device 12 can be a master node (MN) or a secondary node (SN). It should be noted that this embodiment only uses a 5G base station as an example, but does not limit the specific type of network equipment.

[0038] Please refer to Figure 2, which is a flowchart of a scheduling request sending method provided in an embodiment of this disclosure. The method is applied to a terminal, and as shown in Figure 2, includes the following steps:

[0039] Step 201: If the first triggering condition is met, send a scheduling request (SR) to the network device;

[0040] Step 202: If the second triggering condition is met, cancel the transmission of the SR or skip the transmission of N SRs, where N is an integer greater than 1.

[0041] The aforementioned SR can be used to trigger network device configuration or indicate uplink authorized resources, on which BFRQ information can be transmitted. The size of N can be set according to actual needs. In this embodiment, the size of N can be agreed upon through a protocol or notified by the network device.

[0042] In this embodiment of the disclosure, when a beam failure event occurs, SR and BFRQ information can be triggered. The transmission of SR can be restricted by a pre-set second trigger condition. For example, when the second trigger condition is met, the transmission of SR can be canceled, or the transmission of N SRs can be skipped directly. The size of N can be set according to actual needs and is not further limited here.

[0043] Optionally, after the SR is generated, it is in a pending state. In this pending state, the terminal can send the SR.

[0044] In this embodiment, by setting a second trigger condition, the transmission of the SR (Signal Sending) is canceled or N SR transmissions are skipped when the second trigger condition is met. This reduces the number of SR transmissions, thereby reducing the resource overhead of the SR. At the same time, it reduces terminal power consumption and extends the terminal's standby time.

[0045] Optionally, the aforementioned SR can be a dedicated SR for beam failure recovery (hereinafter referred to as a dedicated SR) or other SRs (hereinafter referred to as related technology SRs). The dedicated SR is used to notify the network device that BFRQ information will be sent to the network device; that is, the dedicated SR triggers the first uplink grant resource indicated by the network device, which is dedicated to transmitting BFRQ information. The related technology SR can be used to notify the network device that other uplink information exists to be sent. The network device can configure or indicate a second uplink grant resource for the terminal according to the related technology SR, and the aforementioned BFRQ information can be multiplexed with other uplink information for transmission on the second uplink grant resource.

[0046] Optionally, in one embodiment, after step 201 above, the method further includes:

[0047] Send BFRQ information to the network device on the uplink authorized resources configured or indicated by the network device.

[0048] In this embodiment, the uplink grant resource configured or indicated by the network device may include the first uplink grant resource described above or the most recently available second uplink grant resource. Optionally, the second uplink grant resource includes at least one of the following:

[0049] Configure the uplink grant resources;

[0050] Uplink granting of resources using dynamic granting;

[0051] Uplink authorized resources during the Random Access (RA) process.

[0052] Optionally, the random access procedure can specifically refer to a 2-step random access procedure or a 4-step random access procedure. Correspondingly, the second uplink authorized resource refers to the PUSCH of either the 2-step random access (RA) procedure or the 4-step random access (RA) procedure.

[0053] Furthermore, the aforementioned BFRQ information can be carried by a Medium Access Control Element (MAC CE).

[0054] In this embodiment, different BFRQ messages may be on different MAC CEs, and one MAC CE may be used to transmit part or all of the information of one BFRQ message, or one MAC CE may transmit multiple or all BFRQ messages.

[0055] Furthermore, in an optional embodiment, when the second triggering condition is met, the method further includes:

[0056] Cancel the sending of the BFRQ information.

[0057] In this embodiment, by setting the second trigger condition as the trigger condition for canceling BFRQ information transmission, the number of times BFRQ information is repeatedly transmitted can be reduced. This further reduces the amount of data transmitted, thereby reducing resource overhead, lowering terminal power consumption, and extending the terminal's standby time.

[0058] It should be understood that the aforementioned first triggering condition can be set according to actual needs. For example, in an optional embodiment, the aforementioned first triggering condition may include at least one of the following:

[0059] Beam failure detected;

[0060] A beam failure was detected, and a new beam was identified;

[0061] There is a Beam Failure Recovery Request (BFRQ) message to be transmitted, but there are no available uplink resources to transmit the BFRQ message.

[0062] The detection of beam failure includes at least one of the following:

[0063] Beam failure detected in the cell;

[0064] Beaming failure detected in the Bandwidth Part (BWP);

[0065] Beam failure detected at the transmit / receive point (TRP).

[0066] The above-mentioned detection of beam failure and identification of a new beam includes at least one of the following:

[0067] A beam failure was detected in a cell, and a new beam was identified on the cell where the beam failure was detected.

[0068] A beam failure was detected in a portion of the bandwidth of the BWP, and a new beam was identified on the BWP where the beam failure was detected.

[0069] A beam failure was detected at the transmit / receive point (TRP), and a new beam was identified on the TRP where the beam failure was detected.

[0070] In this embodiment, the terminal can measure the Beam Failure Detection Reference Signal (BFD RS). Based on the measurement result, it determines whether a beam failure event has occurred at at least one target object, which can be a cell, BWP, or TRP. Furthermore, the terminal can determine whether a new beam has been found on the cell, BWP, or TRP where the beam failure occurred by measuring the downlink reference signal used for new candidate beam identification.

[0071] In this embodiment, the existence of BFRQ information to be sent and the lack of available uplink resources to send the BFRQ information to be sent can be specifically understood as follows: when there is a MAC CE for BFRQ for transmitting BFRQ information, there is no Physical uplink shared channel (PUSCH) resource for new transmission, or even if there is uplink resource, the MAC CE for BFRQ has a lower priority according to the logical channel priority relationship and cannot use the uplink resource.

[0072] Furthermore, before sending the scheduling request (SR) to the network device, the method further includes:

[0073] In the event of beam failure, the first MAC CE is triggered, which is used to transmit BFRQ information;

[0074] Alternatively, if a beam failure is detected and a new beam is identified, a first MAC CE is triggered, which is used to transmit BFRQ information.

[0075] In this embodiment of the disclosure, the SR corresponding to different first MAC CEs (MAC CEs for transmitting BFRQ information, i.e., MAC CE for BFRQ) may be different. For example, the MAC CE for BFRQ of different secondary cell SCells may correspond to different SRs.

[0076] Optionally, after the first MAC CE is generated, it is in a pending state. In this pending state, the terminal can send the first MAC CE.

[0077] It should be understood that in this embodiment, after the generation of the first MAC CE is triggered, it can be understood that there is BFRQ information to be sent.

[0078] Furthermore, the specific content of the aforementioned second triggering condition can be set according to actual needs. In an optional embodiment, the second triggering condition includes any one of the following:

[0079] Send BFRQ information to the network device;

[0080] Complete beam failure recovery;

[0081] Receive at least one of the following from the network device: Radio Resource Control (RRC), Media Access Control (MAC) CE, and Downlink Control Information (DCI);

[0082] Release or deactivate the cell where beam failure occurred;

[0083] Release or deactivate the bandwidth portion of the BWP where beam failure occurred;

[0084] Release or deactivate the transmit / receive point (TRP) where beam failure has occurred;

[0085] Switch to a new neighborhood;

[0086] Switch to the new bandwidth portion BWP;

[0087] Switch to the new transmit / receive point (TRP);

[0088] Switch to the new beam.

[0089] In this embodiment of the disclosure, receiving at least one of RRC, MAC CE, and DCI sent by the network device can be understood as the network device sending scheduling signaling, beam training-related signaling, release or deactivation signaling, handover signaling, etc., to the terminal through at least one of RRC signaling, MAC CE command, and DCI signaling. Specifically, the RRC signaling, MAC CE command, and DCI signaling can be transmitted on the target object where beam failure has occurred, or on the target object where beam failure has not occurred.

[0090] To better understand this disclosure, the following example uses a cell as the target object associated with BFRQ information, and the BFRQ information is carried by a MAC CE, to illustrate the specific implementation process of this disclosure in detail. Specifically, it may include the following steps:

[0091] Step 1: The terminal measures the BFD RS and determines whether a beam failure event has occurred at at least one target object based on the measurement results.

[0092] Step 2: The terminal measures the downlink reference signal (DL RS) used for new beam identification to determine whether a new beam has been found. Step 2 is independent of step 1.

[0093] Step 3: The terminal triggers the generation of a MAC CE (i.e., MAC CE for BFRQ) for transmitting BFRQ information.

[0094] The MAC CE used to transmit BFRQ information can be a dedicated MAC CE for BFRQ transmission (this MAC CE is different from the MAC CE in related technologies), for example, identified using a new logical channel header. The MAC CE used to transmit BFRQ information can also be a MAC CE used to transmit other uplink information, with a newly defined value for a reserved bit in the MAC CE used to identify whether the MAC CE is used to transmit BFRQ information.

[0095] Furthermore, if a beam failure is detected in the target object, a MAC CE for BFRQ is also triggered, and the MAC CE for BFRQ is also in a pending state; or, if a beam failure is detected in the target object and a new beam is identified in the target object, a MAC CE for BFRQ is also triggered, and the MAC CE for BFRQ is also in a pending state.

[0096] Step 4: If the first triggering condition is met, the terminal sends an SR to the network device.

[0097] The SR can be an SR in related technologies; or, the SR can be a dedicated SR for beam failure recovery, such as a dedicated SR. The dedicated SR is used to notify the network that BFRQ information will be sent to the network, that is, the dedicated SR is used to trigger the uplink resource (PUSCH) used to send MAC CE for BFRQ.

[0098] Optionally, the SR is in a pending state.

[0099] Optionally, the SR is periodically and continuously sent to the network by the terminal.

[0100] Step 5: The terminal sends a MAC CE for BFRQ to the network device.

[0101] Optionally, MAC CE for BFRQ can be sent on uplink resources triggered by dedicated SR; that is, after receiving dedicated SR, the network device indicates the uplink resource via DCI.

[0102] Optionally, MAC CE for BFRQ can be sent on the most recently available uplink resource, such as the uplink resource corresponding to the most recently available configured grant, dynamic grant, or RA procedure.

[0103] Furthermore, the RA procedure can refer to a 2-step RA procedure or a 4-step RA procedure. Correspondingly, the most recently available uplink resource refers to either the PUSCH of a 2-step RA procedure or the PUSCH of a 4-step RA procedure.

[0104] Step 6: When the second triggering condition is met, cancel the SR transmission or skip N SR transmissions.

[0105] Optionally, the second triggering condition includes any of the following:

[0106] Send BFRQ information to the network device;

[0107] Complete beam failure recovery;

[0108] Receive at least one of the following from the network device: Radio Resource Control (RRC), Media Access Control (MAC) CE, and Downlink Control Information (DCI);

[0109] Release or deactivate the cell where beam failure occurred;

[0110] Release or deactivate the bandwidth portion of the BWP where beam failure occurred;

[0111] Release or deactivate the transmit / receive point (TRP) where beam failure has occurred;

[0112] Switch to a new neighborhood;

[0113] Switch to the new bandwidth portion BWP;

[0114] Switch to the new transmit / receive point (TRP);

[0115] Switch to the new beam.

[0116] It should be understood that when the first trigger condition is met again, the SR will be sent again.

[0117] Furthermore, when the second triggering condition mentioned above is met, the terminal can also cancel the transmission of MAC CE for BFRQ.

[0118] Please refer to Figure 3, which is a flowchart of a scheduling request receiving method provided in an embodiment of this disclosure. The method is applied to a network device, and as shown in Figure 3, includes the following steps:

[0119] Step 301: The receiving terminal sends a scheduling request SR when the first triggering condition is met;

[0120] Step 302: If the second triggering condition is met, stop receiving the SR or skip receiving the SR N times, where N is an integer greater than 1.

[0121] Optionally, the first triggering condition includes at least one of the following:

[0122] The terminal detected a beam failure.

[0123] The terminal detected a beam failure and identified a new beam;

[0124] The terminal has a Beam Failure Recovery Request (BFRQ) message to be sent, but there are no available uplink resources to send the BFRQ message.

[0125] Optionally, the terminal detecting a beam failure includes at least one of the following:

[0126] The terminal detected a beam failure in the cell.

[0127] The terminal detected a beam failure in the bandwidth portion of the BWP.

[0128] The terminal detected a beam failure at the transmit / receive point (TRP).

[0129] Optionally, the terminal detects a beam failure and identifies a new beam, including at least one of the following:

[0130] The terminal detects a beam failure in a cell and identifies a new beam on the cell where the beam failure was detected.

[0131] The terminal detects a beam failure in the bandwidth portion of the BWP and identifies a new beam on the BWP where the beam failure was detected.

[0132] The terminal detects a beam failure at the transmit / receive point (TRP) and identifies a new beam on the TRP where the beam failure was detected.

[0133] Optionally, the second triggering condition includes any one of the following:

[0134] Received BFRQ information sent by the terminal;

[0135] Complete beam failure recovery;

[0136] Send at least one of Radio Resource Control (RRC), Media Access Control (MAC) CE, and Downlink Control Information (DCI) to the terminal;

[0137] Release or deactivate the cell where beam failure occurred;

[0138] Release or deactivate the bandwidth portion of the BWP where beam failure occurred;

[0139] Release or deactivate the transmit / receive point (TRP) where beam failure has occurred;

[0140] Switch to a new neighborhood;

[0141] Switch to the new bandwidth portion BWP;

[0142] Switch to the new transmit / receive point (TRP);

[0143] Switch to the new beam.

[0144] Optionally, after the receiving terminal sends the scheduling request SR when the first triggering condition is met, the method further includes:

[0145] On the uplink authorized resources configured or indicated by the network device, receive BFRQ information sent by the terminal.

[0146] Optionally, the BFRQ information is carried by a MAC CE.

[0147] Optionally, if the second triggering condition is met, the reception of the BFRQ information may be stopped.

[0148] Optionally, the SR is a dedicated SR for beam failure recovery.

[0149] It should be noted that this embodiment is an implementation method of the network device corresponding to the embodiment shown in Figure 2. The specific implementation method can be found in the relevant description of the embodiment shown in Figure 2, and the same beneficial effects can be achieved. In order to avoid repeated description, it will not be repeated here.

[0150] Please refer to Figure 4, which is a structural diagram of a terminal provided in an embodiment of this disclosure. As shown in Figure 4, the terminal 400 includes:

[0151] The sending module 401 is used to send a scheduling request SR to the network device when a first triggering condition is met; and to cancel the sending of the SR or skip the sending of N SRs when a second triggering condition is met, where N is an integer greater than 1.

[0152] Optionally, the first triggering condition includes at least one of the following:

[0153] Beam failure detected;

[0154] A beam failure was detected, and a new beam was identified;

[0155] There is a Beam Failure Recovery Request (BFRQ) message to be transmitted, but there are no available uplink resources to transmit the BFRQ message.

[0156] Optionally, the terminal 400 further includes:

[0157] The first triggering module is used to trigger a first MAC CE in the event of a beam failure, the first MAC CE being used to transmit BFRQ information; or, in the event of detecting a beam failure and identifying a new beam, the first MAC CE being triggered, the first MAC CE being used to transmit BFRQ information.

[0158] Optionally, the detection of beam failure includes at least one of the following:

[0159] Beam failure detected in the cell;

[0160] Beam failure was detected in the bandwidth portion of the BWP.

[0161] Beam failure detected at the transmit / receive point (TRP).

[0162] The detection of beam failure and the identification of a new beam include at least one of the following:

[0163] A beam failure was detected in a cell, and a new beam was identified on the cell where the beam failure was detected.

[0164] A beam failure was detected in a portion of the bandwidth of the BWP, and a new beam was identified on the BWP where the beam failure was detected.

[0165] A beam failure was detected at the transmit / receive point (TRP), and a new beam was identified on the TRP where the beam failure was detected.

[0166] Optionally, the first MAC CE is in a pending state.

[0167] Optionally, the second triggering condition includes any one of the following:

[0168] Send BFRQ information to the network device;

[0169] Complete beam failure recovery;

[0170] Receive at least one of the following from the network device: Radio Resource Control (RRC), Media Access Control (MAC) CE, and Downlink Control Information (DCI);

[0171] Release or deactivate the cell where beam failure occurred;

[0172] Release or deactivate the bandwidth portion of the BWP where beam failure occurred;

[0173] Release or deactivate the transmit / receive point (TRP) where beam failure has occurred;

[0174] Switch to a new neighborhood;

[0175] Switch to the new bandwidth portion BWP;

[0176] Switch to the new transmit / receive point (TRP);

[0177] Switch to the new beam.

[0178] Optionally, the sending module 401 is further configured to send BFRQ information to the network device on uplink authorization resources configured or indicated by the network device.

[0179] Optionally, the BFRQ information is carried by a MAC CE.

[0180] Optionally, the sending module 401 is further configured to cancel the sending of the BFRQ information if the second triggering condition is met.

[0181] Optionally, the SR is a dedicated SR for beam failure recovery.

[0182] The terminal provided in this embodiment can implement the various processes implemented by the terminal in the method embodiment of FIG2. To avoid repetition, they will not be described again here.

[0183] Please refer to Figure 5, which is a structural diagram of a network device provided in an embodiment of this disclosure. As shown in Figure 5, the network device 500 includes:

[0184] The receiving module 501 is used to receive a scheduling request SR sent by the terminal when a first triggering condition is met; and to stop receiving the SR or skip receiving the SR N times when a second triggering condition is met, where N is an integer greater than 1.

[0185] Optionally, the first triggering condition includes at least one of the following:

[0186] The terminal detected a beam failure.

[0187] The terminal detected a beam failure and identified a new beam;

[0188] The terminal has a Beam Failure Recovery Request (BFRQ) message to be sent, but there are no available uplink resources to send the BFRQ message.

[0189] Optionally, the terminal detecting a beam failure includes at least one of the following:

[0190] The terminal detected a beam failure in the cell.

[0191] The terminal detected a beam failure in the bandwidth portion of the BWP.

[0192] The terminal detected a beam failure at the transmit / receive point (TRP).

[0193] Optionally, the terminal detects a beam failure and identifies a new beam, including at least one of the following:

[0194] The terminal detects a beam failure in a cell and identifies a new beam on the cell where the beam failure was detected.

[0195] The terminal detects a beam failure in the bandwidth portion of the BWP and identifies a new beam on the BWP where the beam failure was detected.

[0196] The terminal detects a beam failure at the transmit / receive point (TRP) and identifies a new beam on the TRP where the beam failure was detected.

[0197] Optionally, the second triggering condition includes any one of the following:

[0198] Received BFRQ information sent by the terminal;

[0199] Complete beam failure recovery;

[0200] Send at least one of Radio Resource Control (RRC), Media Access Control (MAC) CE, and Downlink Control Information (DCI) to the terminal;

[0201] Release or deactivate the cell where beam failure occurred;

[0202] Release or deactivate the bandwidth portion of the BWP where beam failure occurred;

[0203] Release or deactivate the transmit / receive point (TRP) where beam failure has occurred;

[0204] Switch to a new neighborhood;

[0205] Switch to the new bandwidth portion BWP;

[0206] Switch to the new transmit / receive point (TRP);

[0207] Switch to the new beam.

[0208] Optionally, after the receiving terminal sends the scheduling request SR when the first triggering condition is met, the method further includes:

[0209] On the uplink authorized resources configured or indicated by the network device, receive BFRQ information sent by the terminal.

[0210] Optionally, the BFRQ information is carried by a MAC CE.

[0211] Optionally, if the second triggering condition is met, the reception of the BFRQ information may be stopped.

[0212] Optionally, the SR is a dedicated SR for beam failure recovery.

[0213] The network device provided in this embodiment can implement the various processes implemented by the network device in the method embodiment of FIG3. To avoid repetition, it will not be described again here.

[0214] Figure 6 is a schematic diagram of the hardware structure of a terminal implementing various embodiments of the present disclosure.

[0215] The terminal 600 includes, but is not limited to, components such as: a radio frequency unit 601, a network module 602, an audio output unit 603, an input unit 604, a sensor 605, a display unit 606, a user input unit 607, an interface unit 608, a memory 609, a processor 610, and a power supply 611. Those skilled in the art will understand that the terminal structure shown in FIG6 does not constitute a limitation on the terminal; the terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements. In the embodiments of this disclosure, the terminal includes, but is not limited to, mobile phones, tablet computers, laptop computers, PDAs, in-vehicle terminals, wearable devices, and pedometers.

[0216] The radio frequency unit 601 is used to: send a scheduling request SR to the network device when a first trigger condition is met; and cancel the transmission of the SR or skip N SR transmissions when a second trigger condition is met, where N is an integer greater than 1.

[0217] In this embodiment, by setting a second trigger condition, the transmission of the SR (Signal Sending) is canceled or N SR transmissions are skipped when the second trigger condition is met. This reduces the number of SR transmissions, thereby reducing the resource overhead of the SR. At the same time, it reduces terminal power consumption and extends the terminal's standby time.

[0218] It should be understood that in this embodiment of the disclosure, the radio frequency unit 601 can be used for receiving and transmitting signals during information transmission or calls. Specifically, it receives downlink data from the base station and processes it with the processor 610; additionally, it transmits uplink data to the base station. Typically, the radio frequency unit 601 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc. Furthermore, the radio frequency unit 601 can also communicate with networks and other devices through a wireless communication system.

[0219] The terminal provides users with wireless broadband internet access through network module 602, such as helping users send and receive emails, browse web pages, and access streaming media.

[0220] The audio output unit 603 can convert audio data received by the radio frequency unit 601 or the network module 602 or stored in the memory 609 into audio signals and output them as sound. Furthermore, the audio output unit 603 can also provide audio output related to specific functions performed by the terminal 600 (e.g., call signal reception sound, message reception sound, etc.). The audio output unit 603 includes a speaker, a buzzer, and a receiver, etc.

[0221] Input unit 604 is used to receive audio or video signals. Input unit 604 may include a graphics processing unit (GPU) 6041 and a microphone 6042. GPU 6041 processes image data of still images or videos acquired by an image capture device (such as a camera) in video capture mode or image capture mode. The processed image frames can be displayed on display unit 606. The image frames processed by GPU 6041 can be stored in memory 609 (or other storage medium) or transmitted via radio frequency unit 601 or network module 602. Microphone 6042 can receive sound and process such sound into audio data. The processed audio data can be converted into a format that can be transmitted to a mobile communication base station via radio frequency unit 601 in telephone call mode.

[0222] The terminal 600 also includes at least one sensor 605, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor and a proximity sensor. The ambient light sensor can adjust the brightness of the display panel 6061 according to the ambient light level, and the proximity sensor can turn off the display panel 6061 and / or backlight when the terminal 600 is moved to the ear. As a type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes). When stationary, it can detect the magnitude and direction of gravity and can be used to identify the terminal's posture (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc. The sensor 605 may also include a fingerprint sensor, pressure sensor, iris sensor, molecular sensor, gyroscope, barometer, hygrometer, thermometer, infrared sensor, etc., which will not be described in detail here.

[0223] The display unit 606 is used to display information input by the user or information provided to the user. The display unit 606 may include a display panel 6061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0224] User input unit 607 can be used to receive input numerical or character information, and generate key signal inputs related to user settings and function control of the terminal. Specifically, user input unit 607 includes a touch panel 6071 and other input devices 6072. Touch panel 6071, also known as a touch screen, can collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near touch panel 6071). Touch panel 6071 may include two parts: a touch detection device and a touch controller. The touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, and sends it to the processor 610, which receives and executes commands from the processor 610. In addition, touch panel 6071 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. Besides touch panel 6071, user input unit 607 may also include other input devices 6072. Specifically, other input devices 6072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, joysticks, etc., which will not be described in detail here.

[0225] Furthermore, the touch panel 6071 can cover the display panel 6061. When the touch panel 6071 detects a touch operation on or near it, it transmits the information to the processor 610 to determine the type of touch event. Subsequently, the processor 610 provides corresponding visual output on the display panel 6061 according to the type of touch event. Although in Figure 6, the touch panel 6071 and the display panel 6061 are shown as two separate components to implement the input and output functions of the terminal, in some embodiments, the touch panel 6071 and the display panel 6061 can be integrated to implement the input and output functions of the terminal. Specific details are not limited here.

[0226] Interface unit 608 serves as an interface for connecting external devices to terminal 600. For example, external devices may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, and so on. Interface unit 608 can be used to receive input (e.g., data, power, etc.) from external devices and transmit the received input to one or more components within terminal 600, or it can be used to transmit data between terminal 600 and external devices.

[0227] The memory 609 can be used to store software programs and various data. The memory 609 may primarily include a program storage area and a data storage area. The program storage area may store the operating system, applications required for at least one function (such as sound playback, image playback, etc.), etc.; the data storage area may store data created based on the use of the mobile phone (such as audio data, phonebook, etc.). Furthermore, the memory 609 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0228] The processor 610 is the control center of the terminal, connecting various parts of the terminal through various interfaces and lines. It performs various functions and processes data by running or executing software programs and / or modules stored in the memory 609, and by calling data stored in the memory 609, thereby providing overall monitoring of the terminal. The processor 610 may include one or more processing units; optionally, the processor 610 may integrate an application processor and a modem processor. The application processor primarily handles the operating system, user interface, and applications, while the modem processor primarily handles wireless communication. It is understood that the modem processor may not be integrated into the processor 610.

[0229] Terminal 600 may also include a power supply 611 (such as a battery) to power various components. Optionally, the power supply 611 may be logically connected to the processor 610 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system.

[0230] In addition, terminal 600 includes some functional modules not shown, which will not be described in detail here.

[0231] Optionally, this disclosure also provides a terminal, including a processor 610, a memory 609, and a computer program stored in the memory 609 and executable on the processor 610. When the computer program is executed by the processor 610, it implements the various processes of the above-described scheduling request sending method embodiments and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0232] Referring to Figure 7, which is a structural diagram of another network device provided in an embodiment of this disclosure, the network device 700 includes: a processor 701, a transceiver 702, a memory 703, and a bus interface, wherein:

[0233] The transceiver 702 is used to: receive a scheduling request SR sent by the terminal when a first triggering condition is met; and stop receiving the SR or skip receiving the SR N times when a second triggering condition is met, where N is an integer greater than 1.

[0234] In this embodiment, by setting a second trigger condition, the transmission of the SR (Signal Sending) is canceled or N SR transmissions are skipped when the second trigger condition is met. This reduces the number of SR transmissions, thereby reducing the resource overhead of the SR. At the same time, it reduces terminal power consumption and extends the terminal's standby time.

[0235] In Figure 7, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 701 and memory represented by memory 703. The bus architecture may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. Transceiver 702 may be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium. For different user equipment, user interface 704 may also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc.

[0236] The processor 701 is responsible for managing the bus architecture and general processing, while the memory 703 can store the data used by the processor 701 when performing operations.

[0237] Optionally, this disclosure also provides a network device, including a processor 701, a memory 703, and a computer program stored in the memory 703 and executable on the processor 701. When the computer program is executed by the processor 701, it implements the various processes of the above-described scheduling request receiving method embodiments and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0238] This disclosure also provides a computer-readable storage medium storing a computer program. When executed by a processor, the computer program implements the various processes of the network device-side scheduling request receiving method embodiment provided in this disclosure, or when executed by a processor, it implements the various processes of the terminal-side scheduling request sending method embodiment provided in this disclosure, achieving the same technical effect. To avoid repetition, further details are omitted here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc.

[0239] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0240] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to the related technology, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or base station, etc.) to execute the methods described in the various embodiments of this disclosure.

[0241] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0242] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0243] In the embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0244] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0245] In addition, the functional units in the various embodiments of this disclosure can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0246] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this disclosure, or the part that contributes to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this disclosure. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0247] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program controlling related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

[0248] It is understood that the embodiments described in this disclosure can be implemented using hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, modules, units, and subunits can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described in this disclosure, or combinations thereof.

[0249] For software implementation, the techniques described in the embodiments of this disclosure can be implemented by modules (e.g., procedures, functions, etc.) that perform the functions described in the embodiments of this disclosure. The software code can be stored in memory and executed by a processor. The memory can be implemented in the processor or external to the processor.

[0250] The embodiments of this disclosure have been described above with reference to the accompanying drawings. However, this disclosure is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this disclosure without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this disclosure.

Claims

1. A scheduling request sending method, applied to a terminal, comprising: If the first triggering condition is met, a scheduling request (SR) is sent to the network device; If the second triggering condition is met, the transmission of the SR is canceled or N SR transmissions are skipped, where N is an integer greater than 1.

2. The method according to claim 1, wherein, The first triggering condition includes at least one of the following: Beam failure detected; A beam failure was detected, and a new beam was identified; There is a Beam Failure Recovery Request (BFRQ) message to be transmitted, but there are no available uplink resources to transmit the BFRQ message.

3. The method according to claim 1, wherein, Before sending the scheduling request (SR) to the network device, the method further includes: If a beam failure is detected, the first media access control element (MAC CE) is triggered. The first MAC CE is used to transmit BFRQ information. Alternatively, if a beam failure is detected and a new beam is identified, a first MAC CE is triggered, which is used to transmit BFRQ information.

4. The method according to claim 2 or 3, wherein, The detection of beam failure includes at least one of the following: Beam failure detected in the cell; Beam failure was detected in the bandwidth portion of the BWP. Beam failure detected at the transmit / receive point (TRP).

5. The method according to claim 2 or 3, wherein, The detection of beam failure and the identification of a new beam include at least one of the following: A beam failure was detected in a cell, and a new beam was identified on the cell where the beam failure was detected. A beam failure was detected in a portion of the bandwidth of the BWP, and a new beam was identified on the BWP where the beam failure was detected. A beam failure was detected at the transmit / receive point (TRP), and a new beam was identified on the TRP where the beam failure was detected.

6. The method according to claim 3, wherein, The first MAC CE is in a pending state.

7. The method according to claim 1, wherein, The second triggering condition includes any one of the following: Send BFRQ information to the network device; Complete beam failure recovery; Receive at least one of the following from the network device: Radio Resource Control (RRC), Media Access Control (MAC) CE, and Downlink Control Information (DCI); Release or deactivate the cell where beam failure occurred; Release or deactivate the bandwidth portion of the BWP where beam failure occurred; Release or deactivate the transmit / receive point (TRP) where beam failure has occurred; Switch to a new neighborhood; Switch to the new bandwidth portion BWP; Switch to the new transmit / receive point (TRP); Switch to the new beam.

8. The method according to claim 1, wherein, After sending a scheduling request (SR) to the network device, the method further includes: On the uplink authorized resources configured or indicated by the network device, send a Beam Failure Recovery Request (BFRQ) message to the network device.

9. The method according to claim 8, wherein, The BFRQ information is carried by MAC CE.

10. The method according to claim 8, wherein, If the second triggering condition is met, the method further includes: Cancel the sending of the BFRQ information.

11. The method according to claim 1, wherein, The SR mentioned is a dedicated SR for beam failure recovery.

12. A scheduling request receiving method, applied to a network device, comprising: The receiving terminal sends a scheduling request (SR) when the first triggering condition is met. If the second trigger condition is met, the reception of the SR is stopped or the reception of the SR is skipped N times, where N is an integer greater than 1.

13. The method according to claim 12, wherein, The first triggering condition includes at least one of the following: The terminal detected a beam failure. The terminal detected a beam failure and identified a new beam; The terminal has a Beam Failure Recovery Request (BFRQ) message to be sent, but there are no available uplink resources to send the BFRQ message.

14. The method according to claim 13, wherein, The terminal detects a beam failure, including at least one of the following: The terminal detected a beam failure in the cell. The terminal detected a beam failure in the bandwidth portion of the BWP. The terminal detected a beam failure at the transmit / receive point (TRP).

15. The method according to claim 13, wherein, The terminal detects a beam failure and identifies a new beam, including at least one of the following: The terminal detects a beam failure in a cell and identifies a new beam on the cell where the beam failure was detected. The terminal detects a beam failure in the bandwidth portion of the BWP and identifies a new beam on the BWP where the beam failure was detected. The terminal detects a beam failure at the transmit / receive point (TRP) and identifies a new beam on the TRP where the beam failure was detected.

16. The method according to claim 12, wherein, The second triggering condition includes any one of the following: Receives Beam Failure Recovery Request (BFRQ) information sent by the terminal; Complete beam failure recovery; Send at least one of Radio Resource Control (RRC), Media Access Control (MAC) CE, and Downlink Control Information (DCI) to the terminal; Release or deactivate the cell where beam failure occurred; Release or deactivate the bandwidth portion of the BWP where beam failure occurred; Release or deactivate the transmit / receive point (TRP) where beam failure has occurred; Switch to a new neighborhood; Switch to the new bandwidth portion BWP; Switch to the new transmit / receive point (TRP); Switch to the new beam.

17. The method according to claim 12, wherein, After the receiving terminal sends a scheduling request SR when the first triggering condition is met, the method further includes: On the uplink authorized resources configured or indicated by the network device, receive the beam failure recovery request (BFRQ) information sent by the terminal.

18. The method according to claim 17, wherein, The BFRQ information is carried by the Media Access Control (MAC) control element CE.

19. The method according to claim 18, wherein, If the second triggering condition is met, the reception of the BFRQ information will be stopped.

20. The method according to claim 12, wherein, The SR mentioned is a dedicated SR for beam failure recovery.

21. A terminal, comprising: The sending module is used to send a scheduling request (SR) to the network device when the first triggering condition is met. If the second triggering condition is met, the transmission of the SR is canceled or N SR transmissions are skipped, where N is an integer greater than 1.

22. A network device, comprising: The receiving module is used to receive the scheduling request SR sent by the terminal when the first triggering condition is met; If the second trigger condition is met, the reception of the SR is stopped or the reception of the SR is skipped N times, where N is an integer greater than 1.

23. A terminal, comprising: A memory, a processor, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the scheduling request sending method as claimed in any one of claims 1 to 11.

24. A network device, comprising: A memory, a processor, and a program stored in the memory and executable on the processor, wherein the program, when executed by the processor, implements the steps of the scheduling request receiving method as described in any one of claims 12 to 20.

25. A computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the scheduling request sending method as described in any one of claims 1 to 11, or when executed by a processor, implements the steps of the scheduling request receiving method as described in any one of claims 12 to 20.