Beam failure processing method and device, terminal, network side equipment and storage medium

Abstract

The invention discloses a beam failure processing method and device, a terminal, network side equipment and a storage medium, and belongs to the technical field of communication, and the beam failure processing method comprises the steps that the terminal determines a hypothetical beam failure; the terminal sends first information; wherein the first information comprises at least one of the following items: hypothetical beam failure related information; the first indication information is used for indicating to postpone to send or receive the second information; the first request information is used for requesting to adjust beam related information; another beam failure processing method provided by the embodiment of the invention comprises the following steps: the network side equipment determines the assumed beam failure; the network side equipment sends fifth information; wherein the fifth information comprises at least one of the following items: hypothetical beam failure related information; and the second indication information is used for indicating postponing sending or postponing receiving of the sixth information.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a beam failure processing method, apparatus, terminal, network-side equipment, and storage medium. Background Art

[0002] Currently, artificial intelligence (AI) technology is gaining widespread application in the communications field. For example, in beam prediction, beam information or beam quality information for some beam pairs is obtained through beam measurement. By inputting this information into an AI unit, it is possible to predict the beam information or beam quality information for more beam pairs, or even all beam pairs, in the current or future time. Therefore, the inference results of the AI unit can be used to implement beam failure detection (BFD) or an auxiliary beam failure detection reference signal (BFDRS).

[0003] In related technologies, when a beam fails, a search is performed on the original candidate beam to make a beam failure recovery request (BFRQ). However, if the AI unit's reasoning results have determined that the candidate beam will fail in the future, a suitable beam cannot be found for beam failure recovery (BFR). If the related BFR process is still performed, communication resources will be wasted. Summary of the Invention

[0004] The embodiments of the present application provide a beam failure processing method, apparatus, terminal, network-side equipment, and storage medium, which can reduce the waste of communication resources.

[0005] In a first aspect, a beam failure processing method is provided, comprising:

[0006] The terminal determines a hypothetical beam failure, where the hypothetical beam failure includes a hypothetical beam failure event or a hypothetical beam failure instance;

[0007] The terminal sends first information based on the assumed beam failure;

[0008] The first information includes at least one of the following:

[0009] Information about assumed beam failures;

[0010] first indication information, where the first indication information is used to instruct to postpone sending or receiving the second information;

[0011] First request information, where the first request information is used to request adjustment of beam-related information.

[0012] In a second aspect, a beam failure processing method is provided, including:

[0013] The network side device receives the first information;

[0014] The first information includes at least one of the following:

[0015] Information related to a hypothetical beam failure, wherein the hypothetical beam failure includes a hypothetical beam failure event or a hypothetical beam failure instance;

[0016] first indication information, where the first indication information is used to instruct to postpone sending or receiving the second information;

[0017] First request information, where the first request information is used to request adjustment of beam-related information.

[0018] In a third aspect, a beam failure processing method is provided, including:

[0019] The network-side device determines a hypothetical beam failure, where the hypothetical beam failure includes a hypothetical beam failure event or a hypothetical beam failure instance;

[0020] The network-side device sends fifth information based on the assumed beam failure;

[0021] The fifth information includes at least one of the following:

[0022] Information about assumed beam failures;

[0023] Second indication information, where the second indication information is used to indicate to postpone sending or receiving sixth information.

[0024] In a fourth aspect, a beam failure processing method is provided, including:

[0025] The terminal receives the fifth information;

[0026] The fifth information includes at least one of the following:

[0027] Information related to a hypothetical beam failure, wherein the hypothetical beam failure includes a hypothetical beam failure event or a hypothetical beam failure instance;

[0028] Second indication information, where the second indication information is used to indicate to postpone sending or receiving sixth information.

[0029] In a fifth aspect, a beam failure processing device is provided, including:

[0030] A first determining module is configured to determine a hypothetical beam failure, wherein the hypothetical beam failure includes a hypothetical beam failure event or a hypothetical beam failure instance;

[0031] A first sending module, configured to send first information based on the assumed beam failure;

[0032] The first information includes at least one of the following:

[0033] Information about assumed beam failures;

[0034] first indication information, where the first indication information is used to instruct to postpone sending or receiving the second information;

[0035] First request information, where the first request information is used to request adjustment of beam-related information.

[0036] In a sixth aspect, a beam failure processing device is provided, including:

[0037] A first receiving module, configured to receive first information;

[0038] The first information includes at least one of the following:

[0039] Information related to a hypothetical beam failure, wherein the hypothetical beam failure includes a hypothetical beam failure event or a hypothetical beam failure instance;

[0040] first indication information, where the first indication information is used to instruct to postpone sending or receiving the second information;

[0041] First request information, where the first request information is used to request adjustment of beam-related information.

[0042] In a seventh aspect, a beam failure processing device is provided, including:

[0043] a second determining module, configured to determine a hypothetical beam failure, wherein the hypothetical beam failure includes a hypothetical beam failure event or a hypothetical beam failure instance;

[0044] A second sending module, configured to send fifth information based on the assumed beam failure;

[0045] The fifth information includes at least one of the following:

[0046] Information about assumed beam failures;

[0047] Second indication information, where the second indication information is used to indicate to postpone sending or receiving sixth information.

[0048] In an eighth aspect, a beam failure processing device is provided, including:

[0049] A second receiving module, configured to receive fifth information;

[0050] The fifth information includes at least one of the following:

[0051] Information related to a hypothetical beam failure, wherein the hypothetical beam failure includes a hypothetical beam failure event or a hypothetical beam failure instance;

[0052] Second indication information, where the second indication information is used to indicate to postpone sending or receiving sixth information.

[0053] In the ninth aspect, a terminal is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, the steps of the method described in the first aspect or the fourth aspect are implemented.

[0054] In the tenth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method described in the first aspect or the fourth aspect.

[0055] In the eleventh aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the second aspect or the third aspect are implemented.

[0056] In the twelfth aspect, a network side device is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the steps of the method described in the second aspect or the third aspect.

[0057] In the thirteenth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect, the second aspect, the third aspect, or the fourth aspect are implemented.

[0058] In the fourteenth aspect, a wireless communication system is provided, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the method described in the first aspect or the fourth aspect, and the network side device can be used to execute the steps of the method described in the second aspect or the third aspect.

[0059] In the fifteenth aspect, a chip is provided, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the steps of the method described in the first aspect, the second aspect, the third aspect, or the fourth aspect.

[0060] In the sixteenth aspect, a computer program / program product is provided, which is stored in a storage medium and executed by at least one processor to implement the steps of the method described in the first aspect, the second aspect, the third aspect, or the fourth aspect.

[0061] In an embodiment of the present application, after the terminal determines that a hypothetical beam failure has occurred, the terminal sends a first message based on the hypothetical beam failure, where the first message includes at least one of information related to the hypothetical beam failure, first indication information, and first request information. By interacting with information related to the hypothetical beam failure, it is convenient for the first information recipient to perform relevant operations based on the information related to the hypothetical beam failure, such as determining a hypothetical beam failure based on information related to the hypothetical beam failure, or determining a hypothetical beam failure event based on information related to the hypothetical beam failure, not sending or receiving relevant information within a time unit corresponding to the hypothetical beam failure event, or performing a beam failure recovery process based on information related to the hypothetical beam failure. That is, through the interaction of information related to the hypothetical beam failure, it may be possible to intervene in the beam failure in advance, reduce the probability of beam failure, reduce the waste of communication resources, and ensure communication stability. By instructing the postponement of sending or receiving the second information through the first indication information, communication resources can be saved. This is because if it is determined that a beam failure will occur in the future, then continuing to send or receive some channels or signals within the time unit corresponding to the assumed beam failure event is considered meaningless and will result in a waste of communication resources. The first indication information can indicate the postponement of sending or receiving the second information, such as not sending or receiving the second information within the time unit corresponding to the assumed beam failure event, to save communication resources. Requesting adjustment of beam-related information through the first request information can reduce the waste of communication resources. This is because if it is determined that a beam failure will occur in the future, then adjusting the beam-related information in advance may avoid or reduce the beam failure, thereby enhancing communication stability, effectively utilizing communication resources, and reducing the waste of communication resources.

[0062] Alternatively, after the network-side device determines the assumed beam failure, it sends fifth information based on the assumed beam failure, where the fifth information includes information related to the assumed beam failure or second indication information. By interacting with information related to the assumed beam failure, the fifth information recipient can conveniently perform relevant operations based on the information related to the assumed beam failure, such as determining the assumed beam failure based on information related to the assumed beam failure, or determining the assumed beam failure event based on information related to the assumed beam failure, not sending or receiving relevant information within the time unit corresponding to the assumed beam failure event, or performing a beam failure recovery process based on information related to the assumed beam failure. That is to say, through the interaction of information related to the assumed beam failure, it may be possible to intervene in the beam failure in advance, reduce the probability of beam failure, reduce the waste of communication resources, and ensure communication stability. By instructing the postponement of sending or receiving the sixth information through the second indication information, communication resources can be saved. Because if it is determined that a beam failure will occur in the future, then continuing to send or receive some channels or signals within the time unit corresponding to the assumed beam failure event is considered meaningless and will cause a waste of communication resources. The second indication information can indicate the postponement of sending or receiving the sixth information, such as not sending or receiving the sixth information within the time unit corresponding to the assumed beam failure event, so as to save communication resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] Figure 1 A block diagram of a wireless communication system applicable to embodiments of the present application is shown;

[0064] Figure 2 A schematic diagram of a possible method of beam prediction in related art;

[0065] Figure 3 A schematic diagram of another possible method of beam prediction in the related art;

[0066] Figure 4 A schematic diagram of another possible method of beam prediction in the related art;

[0067] Figure 5 This is a flowchart of the implementation of the first beam failure processing method in the embodiment of the present application;

[0068] Figure 6 This is a flowchart of the implementation of the second beam failure processing method in the embodiment of the present application;

[0069] Figure 7 This is a flowchart of the implementation of the third beam failure processing method in the embodiment of the present application;

[0070] Figure 8 This is a flowchart of the implementation of the fourth beam failure processing method in the embodiment of the present application;

[0071] Figure 9 In the embodiment of this application Figure 5 A schematic structural diagram of the corresponding beam failure processing device;

[0072] Figure 10 In the embodiment of this application Figure 6 A schematic structural diagram of the corresponding beam failure processing device;

[0073] Figure 11 In the embodiment of this application Figure 7 A schematic structural diagram of the corresponding beam failure processing device;

[0074] Figure 12 In the embodiment of this application Figure 8 A schematic structural diagram of the corresponding beam failure processing device;

[0075] Figure 13 This is a schematic diagram of the structure of a communication device in an embodiment of the present application;

[0076] Figure 14 This is a schematic diagram of the structure of a terminal in an embodiment of the present application;

[0077] Figure 15 This is a structural diagram of a network-side device in an embodiment of the present application. DETAILED DESCRIPTION

[0078] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0079] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0080] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0081] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. th Generation, 6G) communication system.

[0082] Figure 1The block diagram of a wireless communication system applicable to the embodiments of the present application is shown. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (flight vehicle), a vehicle user equipment (VUE), a ship-borne device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture, etc.), a game console, a personal computer (PC), a teller machine, or a self-service machine, etc., and other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (Wireless Local Area Network, WLAN) access point (Access Point, AS) or a wireless fidelity (Wireless Fidelity, WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home Evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0083] To facilitate understanding, the relevant technologies and concepts involved in the embodiments of this application are first introduced.

[0084] 1. Using AI Unit for Beam Prediction

[0085] One possible way to use AI units for beam prediction is as follows: Figure 2 As shown in Figure 2, the Reference Signal Received Power (RSRP) of a subset of beam pairs is used as input to the AI unit, and the output of the AI unit is the RSRP results for all beam pairs. A beam pair consists of a transmit beam and a receive beam. The number of inputs to the AI unit is equal to the number of selected beam pairs, and the number of outputs is equal to the number of all beam pairs.

[0086] Another possible way to use AI unit for beam prediction is as follows Figure 3 As shown, context information is added to the AI unit's input. This context information contains information related to the input beam pairs, such as angle information and beam identification (ID) information. The number of inputs to this AI unit is still equal to the number of selected beam pairs, and the number of outputs from this AI unit is still equal to the number of all beam pairs. Adding this context information helps enhance beam prediction performance.

[0087] Another possible way to use AI unit for beam prediction is as follows Figure 4 As shown, this method mainly affects the output of the AI unit by changing the expected information through the AI unit, such as changing the expected receiving angle information, the expected sending angle information, or the expected prediction time related information, and then cyclically using the AI unit for prediction. The input type of the AI unit can include at least one of the following:

[0088] Information related to beam quality;

[0089] Beam information;

[0090] End A sends beam information;

[0091] End B receives beam information;

[0092] The beam information expected by the B-side;

[0093] The B-side receiving beam information expected by the B-side;

[0094] The beam information that the B-side expects the A-side to send;

[0095] Time-dependent information related to beam quality;

[0096] Information about the expected forecast time.

[0097] 2. Beam Failure Recovery

[0098] Because high-frequency beams are easily affected by factors such as moving objects and terminal rotation, transmission may fail using the original transmit / receive beam pair. This necessitates beam failure recovery. This requires a mechanism to quickly restore beam connections at the physical layer to avoid frequent cell handovers.

[0099] Terminal beam failure recovery mechanisms may include:

[0100] Beam failure detection, identification of new candidate beams, transmission of beam failure recovery request, and terminal monitoring of network-side equipment, such as the gNB's response to the beam failure recovery request.

[0101] 3. Beam Failure Detection

[0102] For a serving cell, the terminal monitors the BFDRS on all serving beams and evaluates whether a preset beam failure trigger condition is met.

[0103] If it is detected that the metrics of all service beams meet the preset conditions, the count of beam failure instances (BFI) is increased by 1.

[0104] After determining a BFI, the terminal physical layer reports an indication to the terminal upper layer (Media Access Control (MAC) layer). The reporting process is periodic. Conversely, if the terminal physical layer determines that no BFI has occurred, no indication is sent to the terminal upper layer.

[0105] In addition, each time the terminal upper layer receives a BFI indication, the BFD timer is restarted and the BFI count is incremented by 1. If the BFD timer expires, the BFI count is cleared. If a BFI indication is received before the BFD timer expires, the BFI count continues to increment by 1 and the BFD timer is restarted. In other words, the BFD timer is reset.

[0106] When the number of detected BFIs exceeds the configured maximum number, a beam failure (BF) is determined (all service beams fail).

[0107] The metric mentioned above may be a hypothetical physical downlink control channel (PDCCH) block error rate (BLER).

[0108] The terminal measures the performance of the reference signal (RS) in the same beam as the downlink control channel and infers the BLER of the PDCCH based on the measured RS signal to interference plus noise ratio (SINR). Actual demodulation and decoding of the PDCCH is not required.

[0109] The preset condition mentioned above may be higher than a certain threshold, and the threshold may be reused as the default BLER threshold of Radio Link Monitoring (RLM) in an out-of-sync declaration.

[0110] 4. New candidate beam identification

[0111] When the terminal's higher layer (MAC layer) fails to determine the beam, the terminal's physical layer measures the candidate beam reference signal (candidate beam RS) to find a new candidate beam.

[0112] This step is not mandatory to be performed after a beam failure event occurs, and can also be performed before.

[0113] When the terminal physical layer receives a request, instruction, or notification from the terminal upper layer (MAC layer), it reports the measurement results that meet the preset conditions to the terminal upper layer. The reported content is {beam reference signal index (beam RS index), layer 1 RSRP (L1-RSRP)}. The terminal upper layer selects the candidate beam based on the report from the terminal physical layer.

[0114] 5. Hypothetical Beam Failure Instance (BFI)

[0115] The BFI is determined based on each AI unit inference or based on the predicted occasion of the AI unit inference.

[0116] If the total beam quality information of each of the M1 moments that meet the preset conditions predicted by the AI unit reasoning result is less than or equal to the threshold, or the maximum N2 beam quality information in any moment is less than or equal to the threshold, the terminal counts the assumed BFI + x1, where x1 is the set first value.

[0117] Among them, the preset condition may be related to the time interval requirement between opportunities, or related to the periodic interval requirement between opportunities, or greater than or equal to the AI unit measurement resource period, or greater than or equal to the configuration period of BFD RS, or greater than or equal to the protocol agreed / pre-configured periodic interval, etc.

[0118] For a timing, starting from the first time that the total beam quality information of the timing predicted by the AI unit reasoning result or the maximum N1 beam quality information of the predicted timing is less than or equal to the threshold, within a preset time window, if the total beam quality information of the same timing predicted by the AI unit reasoning result or the maximum N1 beam quality information of the same timing is less than or equal to the first value of the threshold is greater than the preset value, then the terminal counts the BFI assumed for the timing + x2, where x2 is the set second value.

[0119] The preset time window may be agreed upon by a protocol, configured by a network device, or reported by a terminal. The first value is determined based on the sum of weights corresponding to different inference moments detected within the time window that are less than or equal to a threshold.

[0120] For a moment, starting from the first time that the total beam quality information of the moment predicted by the AI unit inference result or the maximum N1 beam quality information of the predicted moment is less than or equal to the threshold, within a preset time window, if the total beam quality information of the same moment predicted by the last N5 AI unit inference results or the maximum N1 beam quality information of the same moment is less than or equal to the threshold, the terminal counts the BFI assumed for the moment + x3, where x3 is the third value set.

[0121] The preset time window may be agreed upon by a protocol, configured by a network-side device, or reported by a terminal.

[0122] The above-mentioned assumed BFI corresponds to determining a beam failure indicator (beam failure indicator) through prediction information. When the beam failure condition is met within the corresponding timer, it is determined that a beam failure event has occurred or will occur in the future. The specific method for determining the assumed BFI is referred to the relevant technology, and the embodiments of this application will not be repeated here.

[0123] 6. Beam Quality Information and Beam Information

[0124] Beam quality information includes but is not limited to at least one of the following types: layer 1 signal to interference plus noise ratio (Signal to Interference plus Noise Ratio, SINR) (L1-SINR), L1-RSRP, layer 1 reference signal receiving quality (Reference Signal Receiving Quality, RSRQ) (L1-RSRQ), layer 3 SINR (L3-SINR), layer 3 RSRP (L3-RSRP), layer 3 reference signal receiving quality (Reference Signal Receiving Quality, RSRQ) (L3-RSRQ), etc.

[0125] The beam information includes but is not limited to at least one of the following: beam ID information, beam angle information, beam gain information, beam width information, expectation information, beam quality information, etc.

[0126] The beam ID information is used to characterize the relevant information of the beam identification, including but not limited to at least one of the following: transmit beam ID, receive beam ID, beam ID, reference signal set ID corresponding to the beam, reference signal resource ID corresponding to the beam, uniquely identified random ID, coded value processed by the additional AI unit, beam angle information, resource index information, resource ID, resource set ID, channel state information reference signal resource indicator (Channel State Information-Reference Signal Resource Indicator, CRI), synchronization signal block resource indicator (Synchronization Signal Block Resource Indicator, SSBRI), transmission configuration indication (Transmission Configuration Indication, TCI) state (TCI state), etc.;

[0127] The beam angle information is used to characterize the angle information corresponding to the beam, including but not limited to at least one of the following: angle-related information, transmission angle-related information, and reception angle-related information;

[0128] Angle information is related information used to represent angles or identities, such as angles, radians, index coding values, ID values, coding values processed by additional AI units, etc.

[0129] The above introduces the relevant technologies and concepts involved in the embodiments of the present application. Now, in combination with the accompanying drawings, the beam failure processing method provided in the embodiments of the present application is described in detail through some embodiments and their application scenarios.

[0130] First of all, it should be noted that in the embodiments of the present application, the AI unit may also be referred to as an AI model, AI structure, etc., or the AI unit may also be understood as a processing unit that can implement specific AI-related algorithms, formulas, processing flows, capabilities, etc., or the AI unit may be understood as a processing method, algorithm, function, module or unit for a specific data set, or the AI unit may be understood as a processing method, algorithm, function, module or unit running on AI-related hardware such as a graphics processing unit (GPU), a neural network processing unit (NPU), a tensor processing unit (TPU), an application-specific integrated circuit (ASIC), etc. The embodiments of the present application do not make specific limitations on this.

[0131] Optionally, a particular data set may include input or output of an AI unit.

[0132] Optionally, the identifier of the AI unit can be an AI model identifier, or an AI structure identifier, or an AI algorithm identifier, or an AI unit identifier, or an identifier of a specific data set associated with the AI unit, or an identifier of a specific AI-related scenario, environment, channel feature, or device, or an identifier of an AI-related function, feature, capability, or module. The embodiments of the present application do not specifically limit this.

[0133] See also Figure 5 FIG. 1 is a flowchart of a beam failure processing method according to an embodiment of the present application, and the method includes the following steps:

[0134] S510: The terminal determines an assumed beam failure, where the assumed beam failure includes an assumed beam failure event or an assumed beam failure instance.

[0135] S520: The terminal sends first information based on the assumed beam failure.

[0136] The first information includes at least one of the following:

[0137] Information about assumed beam failures;

[0138] first indication information, the first indication information is used to instruct to postpone sending or receiving the second information;

[0139] First request information, the first request information is used to request adjustment of beam-related information.

[0140] By applying the method provided in the embodiment of the present application, after the terminal determines that a hypothetical beam failure has occurred, the terminal sends a first message based on the hypothetical beam failure, and the first message includes at least one of the hypothetical beam failure related information, the first indication information, and the first request information. By interacting with the hypothetical beam failure related information, it is convenient for the first information receiver to perform related operations based on the hypothetical beam failure related information, such as determining the hypothetical beam failure based on the hypothetical beam failure related information, or determining the hypothetical beam failure event based on the hypothetical beam failure related information, not sending or receiving related information within the time unit corresponding to the hypothetical beam failure event, or performing a beam failure recovery process based on the hypothetical beam failure related information. That is to say, through the interaction of the hypothetical beam failure related information, it may be possible to intervene in the beam failure in advance, reduce the probability of beam failure, reduce the waste of communication resources, and ensure communication stability. By instructing the postponement of sending or receiving the second information through the first indication information, communication resources can be saved. This is because if the terminal determines that a beam failure will occur in the future, then continuing to send or receive some channels or signals within the time unit corresponding to the assumed beam failure event is considered meaningless and will result in a waste of communication resources. The first indication information can indicate the postponement of sending or receiving the second information, such as not sending or receiving the second information within the time unit corresponding to the assumed beam failure event, to save communication resources. Requesting adjustment of beam-related information through the first request information can reduce the waste of communication resources. This is because if the terminal determines that a beam failure will occur in the future, then adjusting the beam-related information in advance may avoid or reduce the beam failure, thereby enhancing communication stability, effectively utilizing communication resources, and reducing the waste of communication resources.

[0141] In an embodiment of the present application, the terminal may determine a hypothetical beam failure, where the hypothetical beam failure may include a hypothetical beam failure instance or a hypothetical beam failure event.

[0142] Optionally, the AI unit is located on the terminal side, and the terminal performs AI unit reasoning to predict beam information or beam quality information in the future, thereby determining whether beam failure will occur, or the duration of beam failure in the future, etc.

[0143] The terminal may send first information based on an assumed beam failure, and the first information may include information related to the assumed beam failure. It clarifies how to interact with information related to the assumed beam failure, and by interacting with information related to the assumed beam failure, it is convenient for the first information receiver to perform relevant operations based on the information related to the assumed beam failure, such as determining an assumed beam failure based on information related to the assumed beam failure, or determining an assumed beam failure event based on information related to the assumed beam failure, not sending or receiving relevant information within the time unit corresponding to the assumed beam failure event, or performing a beam failure recovery process based on information related to the assumed beam failure. That is to say, through the interaction of information related to the assumed beam failure, it may be possible to intervene in the beam failure in advance, reduce the probability of beam failure, reduce the waste of communication resources, and ensure communication stability.

[0144] The first information may include first indication information, and the first indication information is used to instruct to postpone sending or receiving the second information. It is understandable that if the terminal determines that a beam failure will occur in the future, then continuing to send or receive some channels or signals within the time unit corresponding to the assumed beam failure event is considered meaningless and causes a waste of communication resources. Therefore, the first indication information may be used to instruct to postpone sending or receiving the second information. For example, the second information may not be sent or received within the time unit corresponding to the assumed beam failure event to save communication resources.

[0145] Optionally, the second information may include at least one of the following:

[0146] Physical Downlink Control Channel (PDCCH), Physical Uplink Control Channel (PUCCH), Physical Downlink Shared Channel (PDSCH), Physical Uplink Shared Channel (PUSCH), Channel State Information-Reference Signal (CSI-RS), Sounding Reference Signal (SRS).

[0147] Of course, the second information may also include other uplink reference signals or downlink reference signals.

[0148] The first information may include first request information for requesting adjustment of beam-related information. It is understood that if the terminal determines that beam failure will occur in the future, adjusting the beam-related information in advance may avoid or reduce the beam failure, thereby avoiding or reducing communication interruption, improving communication stability, and enabling efficient utilization of communication resources, thereby reducing waste of communication resources.

[0149] In some embodiments of the present application, when the assumed beam failure includes an assumed beam failure event, the terminal determines the assumed beam failure, which may include the following steps:

[0150] The terminal determines a hypothetical beam failure event based on at least one of the following:

[0151] the number of assumed beam failure instances;

[0152] the number of indications of assumed beam failure instances;

[0153] The beam failure instance indication information is associated with the number of assumed beam failure instances.

[0154] In an embodiment of the present application, the terminal may determine a hypothetical beam failure event based on at least one of the above items.

[0155] The greater the number of assumed beam failure instances, the greater the probability of beam failure. Optionally, a assumed beam failure event may be determined when the number of assumed beam failure instances is greater than or equal to a first threshold.

[0156] The greater the number of indication information of the assumed beam failure instances, the greater the probability of beam failure. Optionally, when the number of indication information of the assumed beam failure instances is greater than or equal to a second threshold, a assumed beam failure event may be determined.

[0157] The indication information of a beam failure instance may be associated with one or more hypothetical beam failure instances. The more hypothetical beam failure instances associated with the indication information of the beam failure instance, the greater the probability of beam failure. Optionally, a hypothetical beam failure event may be determined when the number of hypothetical beam failure instances associated with the indication information of the beam failure instance is greater than or equal to a third threshold.

[0158] The first threshold, the second threshold, and the third threshold may be agreed upon by a protocol or configured by a network-side device.

[0159] The terminal may determine the assumed beam failure event based on any one of the above items alone, or may determine the assumed beam failure event based on a combination of the above items. The terminal may accurately determine the assumed beam failure event based on at least one of the above items.

[0160] In some embodiments of the present application, the method may further include the following steps:

[0161] The terminal does not send or receive third information within a time unit corresponding to the assumed beam failure event;

[0162] Alternatively, the terminal suspends sending or receiving the third information within a time unit corresponding to the assumed beam failure event.

[0163] Optionally, the third information may include at least one of the following:

[0164] Physical downlink control channel, physical uplink control channel, physical downlink shared channel, physical uplink shared channel, channel state information reference signal, channel sounding reference signal.

[0165] Of course, the third information may also include other uplink reference signals or downlink reference signals.

[0166] The time unit corresponding to the assumed beam failure event may be understood as the location where the assumed beam failure event occurs.

[0167] It is understandable that the terminal or network side equipment cannot send or receive relevant channels or signals when the beam fails. If the relevant channels or signals are continuously sent or received, it will lead to waste of communication resources. Therefore, the terminal does not send or receive at least one of the above channels or signals within the time unit corresponding to the assumed beam failure event, which can effectively avoid waste of communication resources.

[0168] In some embodiments of the present application, the method may further include the following steps:

[0169] The terminal sends or receives a reference signal for beam failure detection within a time unit corresponding to the assumed beam failure event.

[0170] Optionally, the reference signal used for beam failure detection may be a BFD RS.

[0171] The terminal continues to send or receive reference signals for beam failure detection within the time unit corresponding to the assumed beam failure event to obtain accurate information.

[0172] In some embodiments of the present application, when the first information includes information related to assumed beam failure, the terminal sends the first information, which may include at least one of the following:

[0173] The terminal sends information related to the assumed beam failure to the network side device;

[0174] The terminal sends information related to the assumed beam failure to the upper layer of the terminal.

[0175] In an embodiment of the present application, one implementation method is that the terminal can send first information, such as beam failure related information, first indication information, and first request information, to the network device to exchange beam failure related information with the network device, or to instruct the network device to postpone sending or receiving second information, or to request the network device to adjust beam related information. This facilitates the network device to promptly obtain information related to the assumed beam failure and perform related operations.

[0176] Optionally, when the first information includes information related to an assumed beam failure, the network-side device receives the first information and does not send or receive the fourth information within the time unit corresponding to the assumed beam failure. The fourth information may include a physical downlink control channel, a physical uplink control channel, a physical downlink shared channel, a physical uplink shared channel, a channel state information reference signal, and a channel sounding reference signal. Of course, the fourth information may also include other uplink reference signals or downlink reference signals.

[0177] Optionally, when the first information includes information related to the assumed beam failure, the network side device sends or receives a reference signal for beam failure detection within a time unit corresponding to the assumed beam failure.

[0178] Optionally, when the first information includes first indication information, the network side device postpones sending or receiving the second information according to the first indication information.

[0179] Optionally, when the first information includes first request information, the network-side device may perform at least one of the following according to the first request information:

[0180] Switching the beam prediction range or instructing to switch the beam prediction range;

[0181] Switching the beam prediction range of the beam prediction model or indicating switching the beam prediction range of the beam prediction model;

[0182] Switching a beam prediction model or instructing to switch a beam prediction model;

[0183] Switching beams or instructing beam switching;

[0184] Indicates beams outside the measurement beam prediction range;

[0185] indicating a beam outside a beam prediction range of a measurement beam prediction model;

[0186] Indicates measurement of standby beam;

[0187] Deactivating a beam prediction model or instructing deactivation of the beam prediction model;

[0188] reactivating a beam prediction model or instructing to reactivate a beam prediction model;

[0189] Fallback beam failure recovery monitoring mode or indication of fallback beam failure recovery monitoring mode;

[0190] Activate the reference signal resources used for beam failure detection.

[0191] Another implementation method is that the terminal or the terminal physical layer can send information related to the assumed beam failure to the higher layer of the terminal, so that the higher layer of the terminal determines the beam failure based on the information related to the assumed beam failure.

[0192] In some embodiments of the present application, the assumed beam failure related information may include at least one of the following:

[0193] 1) Indication of a hypothetical beam failure instance;

[0194] There may be one or more indication information of the assumed beam failure instance, each indication information is associated with one or more assumed beam failure instances, and different indication information may correspond to different time units.

[0195] For example, the AI unit is located on the terminal side. If the terminal determines that a beam failure instance will occur in the future based on the model inference results of the AI unit, the terminal can send indication information of the assumed beam failure instance to the higher layer of the terminal for the terminal to determine the beam failure.

[0196] 2) Information on the number of hypothetical beam failure instances;

[0197] There may be one or more pieces of information on the number of assumed beam failure instances, and different pieces of information on the number of assumed beam failure instances may be for different time units. The information on the number of assumed beam failure instances may be used to determine the number of increments of the beam failure instance counter.

[0198] 3) Temporal information of hypothetical beam failure instances;

[0199] There may be one or more time information of a hypothetical beam failure instance, and the time information of different hypothetical beam failure instances may correspond to different time units. The time information of the hypothetical beam failure instance may be used to determine the time when the hypothetical beam failure instance occurs.

[0200] Optionally, the time information of the assumed beam failure instance may include at least one of the following:

[0201] The starting time unit of the hypothetical beam failure instance;

[0202] The end time unit of the hypothetical beam failure instance;

[0203] Duration units of a hypothetical beam failure instance.

[0204] 4) Indication of a hypothetical beam failure event;

[0205] There may be one or more indication information of the assumed beam failure event, and each indication information is used to indicate the assumed beam failure event.

[0206] For example, the AI unit is located on the network-side device side. The network-side device determines that a beam failure instance will occur in the terminal in the future based on the model inference results of the AI unit. The network-side device can send a hypothetical beam failure instance indication to the terminal. The terminal determines that a beam failure will occur in the future based on the beam failure instance indication or the result of BFD RS monitoring, and can report the hypothetical beam failure event to the network-side device through the indication information of the hypothetical beam failure event.

[0207] For another example, the AI unit is located on the terminal side. The terminal determines that a beam failure will occur in the future based on the model inference results of the AI unit. The terminal can then send an assumed beam failure event to the terminal's upper layer through the indication information of the assumed beam failure event, or report the assumed beam failure event to the network side device.

[0208] 5) Time information of the hypothetical beam failure event;

[0209] There may be one or more pieces of time information of the assumed beam failure event, and the time information of different assumed beam failure events may correspond to different time units. The time information of the assumed beam failure event may be used to determine the time when the assumed beam failure event occurs.

[0210] Optionally, the time information of the assumed beam failure event may include at least one of the following:

[0211] The starting time unit of the assumed beam failure event;

[0212] The end time unit of the assumed beam failure event;

[0213] Duration units of a hypothetical beam failure event.

[0214] 6) Hypothetical Radio Link Failure (RLF) event;

[0215] There may be one or more assumed radio link failure events, and different assumed radio link failure events may correspond to different time units. The assumed radio link failure event is used to indicate a radio link failure.

[0216] 7) Indication information of beam failure recovery;

[0217] The beam failure recovery indication information is used to trigger a beam failure recovery process.

[0218] The information related to the assumed beam failure includes at least one of the above items. The terminal and the network side device or the terminal's high-level interaction of at least one of the above information enables both parties to clearly understand the information related to the assumed beam failure, which helps both parties to perform relevant operations in a timely manner.

[0219] In some embodiments of the present application, the first indication information may include at least one of the following:

[0220] 1) information indicating that the second information should be sent later;

[0221] There may be one or more indication information, which is used to indicate the postponement of sending the second information.

[0222] 2) information indicating that the second information should be received later;

[0223] There may be one or more indication information, which is used to indicate the postponement of receiving the second information.

[0224] 3) postponing the start time unit of sending the second information;

[0225] There may be one or more starting time units, which are used to indicate at which time unit or time units the sending of the second information is postponed.

[0226] 4) postponing the end time unit of sending the second information;

[0227] There may be one or more end time units, which are used to indicate at which time unit or time units the postponement of sending the second information ends.

[0228] The end time unit for postponing the sending of the second information and the start time unit for postponing the sending of the second information may be used in combination to clearly indicate the time units for postponing the sending of the second information.

[0229] 5) a duration unit for postponing sending the second information;

[0230] The duration unit may be one or more, and is used to indicate the time unit for delaying the sending of the second information, and may be represented by the number of time units or by a time unit identifier.

[0231] The duration unit for postponing the sending of the second information may be used in combination with the start time unit for postponing the sending of the second information or the end time unit for postponing the sending of the second information to clearly indicate the time units for postponing the sending of the second information.

[0232] 6) postponing the start time unit of receiving the second information;

[0233] There may be one or more starting time units, which are used to indicate at which time unit or time units the reception of the second information is postponed.

[0234] 7) postponing the end time unit of receiving the second information;

[0235] There may be one or more end time units, which are used to indicate at which time unit or time units the postponement of receiving the second information ends.

[0236] The end time unit for postponing the reception of the second information and the start time unit for postponing the reception of the second information may be used in combination to clearly indicate the time units for postponing the reception of the second information.

[0237] 8) a duration unit for postponing receiving the second information;

[0238] The duration unit may be one or more, and is used to indicate the time unit for delaying the reception of the second information, and may be represented by the number of time units or by a time unit identifier.

[0239] The duration unit for postponing the reception of the second information may be used in combination with the start time unit for postponing the reception of the second information or the end time unit for postponing the reception of the second information to clearly indicate the time units for postponing the sending of the second information.

[0240] The above-mentioned postponement of sending can also be understood as suspension of sending, and postponement of receiving can be understood as suspension of receiving. For example, the first indication information may include at least one of the following:

[0241] Instruction information for suspending sending of the second information;

[0242] Instruction information for suspending reception of second information;

[0243] a starting time unit for pausing sending the second information;

[0244] an end time unit for pausing sending of the second information;

[0245] A duration unit for pausing the sending of the second information;

[0246] a start time unit for pausing reception of the second information;

[0247] an end time unit for pausing reception of the second information;

[0248] A duration unit for pausing reception of the second information.

[0249] In an embodiment of the present application, the terminal sends first indication information based on an assumed beam failure, to indicate a postponement of sending or receiving second information.

[0250] Optionally, the terminal may send first indication information to the network device. Upon receiving the first indication information, the network device may postpone sending or receiving the second information based on the first indication information. For example, the network device may determine, based on the start time unit for postponing sending the second information and the duration unit for postponing sending the second information, the time units for postponing sending the second information, and postpone sending the second information in the corresponding time units.

[0251] The first indication information sent by the terminal includes at least one of the above contents, which helps to clarify the postponement of sending or receiving the second information.

[0252] In some embodiments of the present application, the first request information may include at least one of the following:

[0253] 1) A first request, where the first request is used to request switching of the beam prediction range;

[0254] The terminal may send a first request to the network device to switch the beam prediction range. If the beam prediction range changes, other valid beam information may be obtained, thereby adjusting the beam based on the valid beam information to avoid beam failure. Based on the first request, the network device may switch the beam prediction range or instruct the terminal to switch the beam prediction range.

[0255] 2) a second request, the second request being used to request switching of the beam prediction range of the beam prediction model;

[0256] The beam prediction model can be understood as the above-mentioned AI unit.

[0257] The terminal can send a second request to the network side device, requesting to switch the beam prediction range of the beam prediction model. If the beam prediction range of the beam prediction model changes, it is possible to obtain other valid beam information, thereby adjusting the beam based on the valid beam information to avoid beam failure.

[0258] Based on the second request, the network-side device may switch the beam prediction range of the beam prediction model or instruct the terminal to switch the beam prediction range of the beam prediction model.

[0259] 3) a third request, the third request being used to request switching of the beam prediction model;

[0260] The terminal can send a third request to the network device to switch the beam prediction model. Different beam prediction models may have different beam prediction ranges. If the beam prediction model changes, it may be possible to obtain other valid beam information, thereby adjusting the beam based on the valid beam information to avoid beam failure.

[0261] The network side device can switch the beam prediction model or instruct the terminal to switch the beam prediction model according to the third request.

[0262] 4) A fourth request, where the fourth request is used to request beam switching;

[0263] The terminal may send a fourth request to the network side device to request beam switching. If the beam changes, beam failure can be effectively avoided.

[0264] The network side device can switch the beam or instruct the terminal to switch the beam according to the fourth request.

[0265] 5) A fifth request, which is used to request measurement of a beam outside the beam prediction range;

[0266] The terminal may send a fifth request to the network device to request measurement of beams outside the beam prediction range. Measuring beams outside the beam prediction range can obtain more beam information, which can then be used to adjust the beam and avoid beam failure.

[0267] The network side device can instruct the terminal to measure beams outside the beam prediction range based on the fifth request.

[0268] 6) A sixth request, which is used to request measurement of a beam outside the beam prediction range of the beam prediction model;

[0269] The terminal may send a sixth request to the network device, requesting measurement of beams outside the beam prediction range of the beam prediction model. Measuring beams outside the beam prediction range of the beam prediction model can obtain more beam information, which can then be used to adjust the beam and avoid beam failure.

[0270] The network side device can instruct the terminal to measure beams outside the beam prediction range of the beam prediction model based on the sixth request.

[0271] 7) A seventh request, the seventh request is used to request measurement of a standby beam;

[0272] The terminal can send a seventh request to the network device to measure a backup beam. A backup beam is a beam that is not within the range of the current transmit beam. Measuring the backup beam provides more information, allowing for beam adjustment based on this information to avoid beam failure.

[0273] The network side device can send a backup beam or instruct the terminal to measure the backup beam according to the seventh request.

[0274] 8) An eighth request, the eighth request is used to request deactivation of the beam prediction model;

[0275] The terminal may send an eighth request to the network side device to request deactivation of the beam prediction model, thereby terminating the activation state of the beam prediction model and not using the beam prediction model to predict beam information or beam quality information.

[0276] The network-side device may deactivate the beam prediction model or instruct the terminal to deactivate the beam prediction model according to the eighth request.

[0277] 9) A ninth request, which is used to request reactivation of the beam prediction model;

[0278] The terminal may send a ninth request to the network side device, requesting to reactivate the beam prediction model, so that the beam prediction model is reactivated and beam information or beam quality information is predicted using the beam prediction model.

[0279] The network-side device may reactivate the beam prediction model or instruct the terminal to reactivate the beam prediction model according to the ninth request.

[0280] 10) The tenth request is used to request to return to the beam failure recovery monitoring mode;

[0281] The terminal can send a tenth request to the network side device, requesting to fall back to the beam failure recovery monitoring method, such as falling back to the traditional beam failure recovery monitoring method, and only using BFD RS to monitor beam failure.

[0282] For example, using network-side equipment to assist the terminal in beam failure monitoring includes three methods: one method uses AI unit prediction combined with traditional BFDRS monitoring, another method uses only AI unit prediction to implement beam failure monitoring, and another method uses only traditional BFD RS monitoring. When the terminal determines that the assumed beam failure has occurred, the terminal can report a tenth request to the network-side equipment, requesting a fallback to the beam failure recovery monitoring method, such as falling back to using only traditional BFD RS monitoring.

[0283] The network side device can return to the fallback beam failure recovery monitoring mode or instruct to return to the fallback beam failure recovery monitoring mode according to the tenth request.

[0284] 11) an eleventh request, the eleventh request being used to request activation of a reference signal resource for beam failure detection;

[0285] The terminal may send an eleventh request to the network side device, requesting activation of reference signal resources for beam failure detection, such as BFD RS resources.

[0286] For example, BFD RS resources are periodic resources (even if they are periodic resources, it is assumed that they need to be activated twice before they can be used in the case of BFD RS). They are configured in advance, but cannot be sent before activation. After the terminal determines that the assumed beam has failed, it requests activation of the BFD RS resources.

[0287] For another example, the BFD RS resource is a semi-persistent resource that is configured in advance and needs to be activated by the network-side device. After the terminal determines that the assumed beam fails, it requests to activate the BFD RS resource.

[0288] The network side device can activate the resources of the reference signal used for beam failure detection according to the eleventh request.

[0289] The above-mentioned beam prediction range may include a beam identification range, a beam angle range, a data set identification, etc.

[0290] The first request information includes at least one of the above items, which helps to effectively deal with the assumed beam failure and improve communication stability.

[0291] In some embodiments of the present application, the first request information may be associated with at least one of the following:

[0292] Recommended beam prediction range;

[0293] The beam prediction range of the recommended beam prediction model;

[0294] Recommended measurement beam;

[0295] Recommended measurement beam range.

[0296] The beam prediction range or the measurement beam range may include a beam identification range, a beam angle range, a data set identification, and the like.

[0297] The first request information sent by the terminal to the network side device is associated with at least one of the above contents, which helps the network side device to adjust the beam-related information according to the relevant information recommended by the terminal to effectively deal with the assumed beam failure.

[0298] It should be noted that in the embodiments of the present application, postponing sending can be understood as temporarily pausing sending, pausing sending, postponing sending, postponing sending, etc., and postponing receiving can be understood as temporarily pausing receiving, pausing receiving, postponing receiving, postponing receiving, etc.

[0299] The start time unit and the end time unit can be absolute time, or relative to the time unit carrying the corresponding information, or relative to the last time slot or frame (frame) or symbol (symbol) of the time unit carrying the corresponding information, or relative to the first time slot or frame or symbol after the time unit carrying the corresponding information.

[0300] Optionally, the time unit of the time unit can be seconds (s), milliseconds (ms), nanoseconds (ns), time slots (slots), symbols (symbols), subframes (subframes), frames, specific time intervals, etc. The specific time interval can be agreed upon by the protocol, configured by the network-side device, or reported by the terminal. For example, it can be the cycle length of the BFD RS, the cycle length of the AI unit reasoning, the time length of the AI unit prediction result, etc. The units of the time length represented by the time units in the above different descriptions can be different and are not limited here.

[0301] Corresponding to the above method embodiment, the embodiment of the present application also provides a beam failure processing method, such as Figure 6 As shown, the method includes the following steps:

[0302] S610: The network-side device receives first information;

[0303] The first information includes at least one of the following:

[0304] Information related to a hypothetical beam failure, where the hypothetical beam failure includes a hypothetical beam failure event or a hypothetical beam failure instance;

[0305] first indication information, the first indication information is used to instruct to postpone sending or receiving the second information;

[0306] First request information, the first request information is used to request adjustment of beam-related information.

[0307] Applying the method provided in the embodiment of the present application, a network-side device receives first information, which includes at least one of information related to a hypothetical beam failure, first indication information, and first request information. By interacting with information related to the hypothetical beam failure, it is convenient for the first information receiver to perform relevant operations based on the information related to the hypothetical beam failure, such as determining a hypothetical beam failure based on information related to the hypothetical beam failure, or determining a hypothetical beam failure event based on information related to the hypothetical beam failure, not sending or receiving relevant information within a time unit corresponding to the hypothetical beam failure event, or performing a beam failure recovery process based on information related to the hypothetical beam failure. That is, through the interaction of information related to the hypothetical beam failure, it may be possible to intervene in the beam failure in advance, reduce the probability of beam failure, reduce the waste of communication resources, and ensure communication stability. By instructing the postponement of sending or receiving the second information through the first indication information, communication resources can be saved. This is because if it is determined that a beam failure will occur in the future, then continuing to send or receive some channels or signals within the time unit corresponding to the assumed beam failure event is considered meaningless and will result in a waste of communication resources. The first indication information can indicate the postponement of sending or receiving the second information, such as not sending or receiving the second information within the time unit corresponding to the assumed beam failure event, to save communication resources. Requesting adjustment of beam-related information through the first request information can reduce the waste of communication resources. This is because if it is determined that a beam failure will occur in the future, then adjusting the beam-related information in advance may avoid or reduce the beam failure, thereby enhancing communication stability, effectively utilizing communication resources, and reducing the waste of communication resources.

[0308] In some embodiments of the present application, when the first information includes information related to assumed beam failure, the method may further include the following steps:

[0309] The network-side device does not send or receive the fourth information within a time unit corresponding to the assumed beam failure;

[0310] Alternatively, the network-side device sends or receives a reference signal for beam failure detection within a time unit corresponding to the assumed beam failure.

[0311] In some embodiments of the present application, when the first information includes first indication information, the method may further include the following steps:

[0312] The network side device postpones sending or receiving the second information according to the first instruction information.

[0313] In some embodiments of the present application, when the first information includes first request information, the method may further include the following steps:

[0314] The network side device adjusts the beam-related information according to the first request information.

[0315] In some embodiments of the present application, the assumed beam failure related information includes at least one of the following:

[0316] Indication of hypothetical instances of beam failure;

[0317] Information on the number of assumed beam failure instances;

[0318] Temporal information of hypothesized beam failure instances;

[0319] an indication of a hypothetical beam failure event;

[0320] Timing information of hypothetical beam failure events;

[0321] Hypothetical radio link failure event;

[0322] Indication of beam failure recovery.

[0323] In some embodiments of the present application, the time information of the assumed beam failure instance includes at least one of the following:

[0324] The starting time unit of the hypothetical beam failure instance;

[0325] The end time unit of the hypothetical beam failure instance;

[0326] Duration units of a hypothetical beam failure instance.

[0327] In some embodiments of the present application, the time information of the assumed beam failure event includes at least one of the following:

[0328] The starting time unit of the assumed beam failure event;

[0329] The end time unit of the assumed beam failure event;

[0330] Duration units of a hypothetical beam failure event.

[0331] In some embodiments of the present application, the first indication information includes at least one of the following:

[0332] Instruction information for postponing sending of the second information;

[0333] Instruction information for postponing reception of the second information;

[0334] Postponing the start time unit of sending the second information;

[0335] Postponing the end time unit of sending the second information;

[0336] A duration unit for postponing sending the second information;

[0337] Postponing the start time unit of receiving the second information;

[0338] Postponing the end time unit of receiving the second information;

[0339] A duration unit for delaying receiving the second information.

[0340] In some embodiments of the present application, the first request information includes at least one of the following:

[0341] A first request, where the first request is used to request switching of the beam prediction range;

[0342] A second request, where the second request is used to request switching of a beam prediction range of the beam prediction model;

[0343] A third request, the third request is used to request switching of the beam prediction model;

[0344] A fourth request, where the fourth request is used to request beam switching;

[0345] A fifth request, where the fifth request is used to request measurement of a beam outside the beam prediction range;

[0346] A sixth request is used to request measurement of a beam outside the beam prediction range of the beam prediction model;

[0347] A seventh request is used to request measurement of a standby beam;

[0348] An eighth request is used to request deactivation of the beam prediction model;

[0349] A ninth request is used to request reactivation of the beam prediction model;

[0350] The tenth request is used to request to return to the beam failure recovery monitoring mode;

[0351] The eleventh request is used to request activation of resources of a reference signal for beam failure detection.

[0352] In some embodiments of the present application, the first request information is associated with at least one of the following:

[0353] Recommended beam prediction range;

[0354] The beam prediction range of the recommended beam prediction model;

[0355] Recommended measurement beam;

[0356] Recommended measurement beam range.

[0357] The beam failure processing method provided in the embodiment of the present application can achieve Figure 5 The various processes implemented in the illustrated method embodiments achieve the same technical effects, and to avoid repetition, they will not be described again here.

[0358] Corresponding to the above method embodiment, the embodiment of the present application also provides a beam failure processing method, such as Figure 7 As shown, the method includes the following steps:

[0359] S710: The network-side device determines an assumed beam failure, where the assumed beam failure includes an assumed beam failure event or an assumed beam failure instance.

[0360] S720: The network-side device sends fifth information based on the assumed beam failure.

[0361] The fifth information includes at least one of the following:

[0362] Information about assumed beam failures;

[0363] The second indication information is used to indicate the postponement of sending or receiving the sixth information.

[0364] By applying the method provided in the embodiments of the present application, after the network side device determines the assumed beam failure, it sends fifth information based on the assumed beam failure, where the fifth information includes information related to the assumed beam failure or second indication information. By interacting with information related to the assumed beam failure, the fifth information receiver can conveniently perform relevant operations based on the information related to the assumed beam failure, such as determining the assumed beam failure based on information related to the assumed beam failure, or determining the assumed beam failure event based on information related to the assumed beam failure, not sending or receiving relevant information within the time unit corresponding to the assumed beam failure event, or performing a beam failure recovery process based on information related to the assumed beam failure. That is to say, through the interaction of information related to the assumed beam failure, it may be possible to intervene in the beam failure in advance, reduce the probability of beam failure, reduce the waste of communication resources, and ensure communication stability. By instructing the postponement of sending or receiving the sixth information through the second indication information, communication resources can be saved. Because if it is determined that a beam failure will occur in the future, then continuing to send or receive some channels or signals within the time unit corresponding to the assumed beam failure event is considered meaningless and will cause a waste of communication resources. The second indication information can indicate the postponement of sending or receiving the sixth information, such as not sending or receiving the sixth information within the time unit corresponding to the assumed beam failure event, so as to save communication resources.

[0365] In an embodiment of the present application, the network-side device may determine a hypothetical beam failure, and the hypothetical beam failure may include a hypothetical beam failure instance or a hypothetical beam failure event.

[0366] Optionally, the AI unit is located on the network side device side. The network side device performs AI unit inference based on the historical measurement results reported by the terminal, and can predict the beam information or beam quality information in the future time, thereby determining whether a beam failure will occur, or the duration of the beam failure in the future.

[0367] The network-side device may send fifth information based on the assumed beam failure, and the fifth information may include information related to the assumed beam failure. It clarifies how to interact with information related to the assumed beam failure, so as to facilitate the first information recipient to perform relevant operations based on the information related to the assumed beam failure, such as determining the assumed beam failure based on the information related to the assumed beam failure, or determining the assumed beam failure event based on the information related to the assumed beam failure, and delaying the sending or receiving of relevant information within the time unit corresponding to the assumed beam failure event.

[0368] The fifth information may include second indication information for instructing to postpone sending or receiving the sixth information. It is understood that if the network-side device determines that a beam failure will occur in the future, then continuing to send or receive some channels or signals within the time unit corresponding to the assumed beam failure event is considered meaningless. Therefore, the second indication information may be used to instruct to postpone sending or receiving the sixth information to save communication resources.

[0369] Optionally, the sixth information may include at least one of the following:

[0370] Physical downlink control channel, physical uplink control channel, physical downlink shared channel, physical uplink shared channel, channel state information reference signal, channel sounding reference signal.

[0371] Of course, the sixth information may also include other uplink reference signals or downlink reference signals.

[0372] In some embodiments of the present application, when the assumed beam failure includes a assumed beam failure event, the network-side device determines the assumed beam failure, which may include the following steps:

[0373] The network-side device determines a hypothetical beam failure event based on at least one of the following:

[0374] the number of assumed beam failure instances;

[0375] the number of indications of assumed beam failure instances;

[0376] The beam failure instance indication information is associated with the number of assumed beam failure instances.

[0377] In an embodiment of the present application, the network-side device may determine a hypothetical beam failure event based on at least one of the above items.

[0378] The greater the number of assumed beam failure instances, the greater the probability of beam failure. Optionally, a assumed beam failure event may be determined when the number of assumed beam failure instances is greater than or equal to a first threshold.

[0379] The greater the number of indication information of the assumed beam failure instances, the greater the probability of beam failure. Optionally, when the number of indication information of the assumed beam failure instances is greater than or equal to a second threshold, a assumed beam failure event may be determined.

[0380] The indication information of a beam failure instance may be associated with one or more hypothetical beam failure instances. The more hypothetical beam failure instances associated with the indication information of the beam failure instance, the greater the probability of beam failure. Optionally, a hypothetical beam failure event may be determined when the number of hypothetical beam failure instances associated with the indication information of the beam failure instance is greater than or equal to a third threshold.

[0381] The network side device can determine the assumed beam failure event based on any one of the above items alone, or can combine the above items to determine the assumed beam failure event. The terminal can accurately determine the assumed beam failure event based on at least one of the above items.

[0382] In some embodiments of the present application, the method may further include the following steps:

[0383] The network-side device postpones sending or receiving the seventh information within a time unit corresponding to the assumed beam failure event.

[0384] Optionally, the seventh information may include at least one of the following:

[0385] Physical downlink control channel, physical uplink control channel, physical downlink shared channel, physical uplink shared channel, channel state information reference signal, channel sounding reference signal.

[0386] Of course, the seventh information may also include other uplink reference signals or downlink reference signals.

[0387] The time unit corresponding to the assumed beam failure event may be understood as the location where the assumed beam failure event occurs.

[0388] It is understandable that the terminal or network side device cannot send or receive relevant channels or signals when the beam fails. If the relevant channels or signals are continuously sent or received, it will lead to waste of communication resources. Therefore, the network side device delays sending or receiving at least one of the above channels or signals within the time unit corresponding to the assumed beam failure event, which can effectively avoid waste of communication resources.

[0389] In some embodiments of the present application, the method may further include the following steps:

[0390] The network-side device sends or receives a reference signal for beam failure detection within a time unit corresponding to the assumed beam failure event.

[0391] Optionally, the reference signal used for beam failure detection may be a BFD RS.

[0392] The network-side device continues to send or receive reference signals for beam failure detection within the time unit corresponding to the assumed beam failure event to obtain accurate information.

[0393] In some embodiments of the present application, the assumed beam failure related information includes at least one of the following:

[0394] 1) Indication of a hypothetical beam failure instance;

[0395] There may be one or more indication information of the assumed beam failure instance, each indication information is associated with one or more assumed beam failure instances, and different indication information may correspond to different time units.

[0396] For example, the AI unit is located on the network side device side. If the network side device determines that the terminal will have a beam failure instance in the future based on the model inference results of the AI unit, the network side device can send indication information of the assumed beam failure instance to the terminal for the terminal to determine the beam failure.

[0397] 2) Information on the number of hypothetical beam failure instances;

[0398] There may be one or more pieces of information on the number of assumed beam failure instances, and different pieces of information on the number of assumed beam failure instances may be for different time units. The information on the number of assumed beam failure instances may be used to determine the number of increments of the beam failure instance counter.

[0399] 3) Temporal information of hypothetical beam failure instances;

[0400] There may be one or more time information of a hypothetical beam failure instance, and the time information of different hypothetical beam failure instances may correspond to different time units. The time information of the hypothetical beam failure instance may be used to determine the time when the hypothetical beam failure instance occurs.

[0401] Optionally, the time information of the assumed beam failure instance may include at least one of the following:

[0402] The starting time unit of the hypothetical beam failure instance;

[0403] The end time unit of the hypothetical beam failure instance;

[0404] Duration units of a hypothetical beam failure instance.

[0405] 4) Indication of a hypothetical beam failure event;

[0406] There may be one or more indication information of the assumed beam failure event, and each indication information is used to indicate the assumed beam failure event.

[0407] For example, the AI unit is located on the network side device side. If the network side device determines that the terminal will have a beam failure in the future based on the model inference results of the AI unit, the network side device can indicate the assumed beam failure event to the terminal through the indication information of the assumed beam failure event, so that the terminal can determine the beam failure.

[0408] 5) Time information of the hypothetical beam failure event;

[0409] There may be one or more pieces of time information of the assumed beam failure event, and the time information of different assumed beam failure events may correspond to different time units. The time information of the assumed beam failure event may be used to determine the time when the assumed beam failure event occurs.

[0410] Optionally, the time information of the assumed beam failure event may include at least one of the following:

[0411] The starting time unit of the assumed beam failure event;

[0412] The end time unit of the assumed beam failure event;

[0413] Duration units of a hypothetical beam failure event.

[0414] 6) Hypothetical radio link failure event;

[0415] There may be one or more assumed radio link failure events, and different assumed radio link failure events may correspond to different time units. The assumed radio link failure event is used to indicate a radio link failure.

[0416] 7) Indication information of beam failure recovery;

[0417] The beam failure recovery indication information is used to trigger beam failure recovery.

[0418] The information related to the assumed beam failure includes at least one of the above items. The network side device and the terminal interact with at least one of the above information, so that both parties can clearly understand the information related to the assumed beam failure, which helps both parties to perform relevant operations in a timely manner.

[0419] In some embodiments of the present application, the second indication information includes at least one of the following:

[0420] 1) information indicating that the sixth information should be sent later;

[0421] There may be one or more indication information, which is used to indicate the postponement of sending the sixth information.

[0422] 2) information indicating that the sixth information should be received later;

[0423] There may be one or more indication information, which is used to indicate the postponement of receiving the sixth information.

[0424] 3) postponing the start time unit of sending the sixth information;

[0425] There may be one or more starting time units, which are used to indicate at which time unit or time units the sending of the sixth information is postponed.

[0426] 4) postponing the end time unit of sending the sixth information;

[0427] There may be one or more end time units, which are used to indicate at which time unit or time units the postponement of sending the second information ends.

[0428] The end time unit for postponing the sending of the sixth information and the start time unit for postponing the sending of the sixth information may be used in combination to clearly indicate the time units for postponing the sending of the sixth information.

[0429] 5) a duration unit for postponing sending the sixth information;

[0430] There may be one or more duration units, which are used to indicate the time units for delaying the sending of the sixth information, and may be represented by the number of time units or by time unit identifiers.

[0431] The duration unit for postponing sending the sixth information may be used in combination with the start time unit for postponing sending the sixth information or the end time unit for postponing sending the sixth information to clearly indicate the time units for postponing sending the sixth information.

[0432] 6) postponing the start time unit of receiving the sixth information;

[0433] There may be one or more starting time units, which are used to indicate at which time unit or time units the sixth information is to be deferred.

[0434] 7) Postponing the end time unit of receiving the sixth information;

[0435] There may be one or more end time units, which are used to indicate at which time unit or time units the postponement of receiving the sixth information ends.

[0436] The end time unit for postponing the reception of the sixth information and the start time unit for postponing the reception of the sixth information may be used in combination to clearly indicate the time units for postponing the reception of the sixth information.

[0437] 8) A duration unit for postponing reception of the sixth information.

[0438] There may be one or more duration units, which are used to indicate the time units for delaying the reception of the sixth information, and may be represented by the number of time units or by time unit identifiers.

[0439] The duration unit for postponing the reception of the sixth information may be used in combination with the start time unit for postponing the reception of the sixth information or the end time unit for postponing the reception of the sixth information to clearly indicate the time units for postponing the sending of the sixth information.

[0440] In an embodiment of the present application, the network side device sends second indication information based on the assumed beam failure, which is used to instruct to postpone sending or postponing receiving the sixth information.

[0441] Optionally, the network-side device may send second indication information to the terminal. Upon receiving the second indication information, the terminal may postpone sending or receiving the sixth information based on the second indication information. For example, the terminal may determine, based on a start time unit for postponing sending the sixth information and a duration unit for postponing sending the sixth information, which time units to postpone sending the sixth information, and postpone sending the sixth information in the corresponding time units.

[0442] The second indication information sent by the network side device includes at least one of the above-mentioned contents, which helps to clarify the postponement of sending or receiving the sixth information.

[0443] Corresponding to the above method embodiment, the embodiment of the present application also provides a beam failure processing method, such as Figure 8 As shown, the method includes the following steps:

[0444] S810: The terminal receives fifth information;

[0445] The fifth information includes at least one of the following:

[0446] Information related to a hypothetical beam failure, where the hypothetical beam failure includes a hypothetical beam failure event or a hypothetical beam failure instance;

[0447] The second indication information is used to indicate the postponement of sending or receiving the sixth information.

[0448] By applying the method provided in the embodiment of the present application, the terminal receives fifth information, which includes information related to an assumed beam failure or second indication information. By interacting with information related to the assumed beam failure, the fifth information receiver is facilitated to perform relevant operations based on the information related to the assumed beam failure, such as determining a assumed beam failure based on information related to the assumed beam failure, or determining a assumed beam failure event based on information related to the assumed beam failure, not sending or receiving relevant information within the time unit corresponding to the assumed beam failure event, or performing a beam failure recovery process based on information related to the assumed beam failure. That is to say, through the interaction of information related to the assumed beam failure, it may be possible to intervene in the beam failure in advance, reduce the probability of beam failure, reduce the waste of communication resources, and ensure communication stability. By instructing the postponement of sending or receiving the sixth information through the second indication information, communication resources can be saved. Because if it is determined that a beam failure will occur in the future, then continuing to send or receive some channels or signals within the time unit corresponding to the assumed beam failure event is considered meaningless and will cause a waste of communication resources. The second indication information can indicate the postponement of sending or receiving the sixth information, such as not sending or receiving the sixth information within the time unit corresponding to the assumed beam failure event, so as to save communication resources.

[0449] In some embodiments of the present application, when the fifth information includes information related to assumed beam failure, the method further includes:

[0450] The terminal does not send or receive the eighth information within a time unit corresponding to the assumed beam failure;

[0451] Alternatively, the terminal sends or receives a reference signal for beam failure detection within a time unit corresponding to the assumed beam failure.

[0452] In some embodiments of the present application, when the fifth information includes second indication information, the method further includes:

[0453] The terminal postpones sending or receiving the sixth information according to the second instruction information.

[0454] In some embodiments of the present application, the assumed beam failure related information includes at least one of the following:

[0455] Indication of hypothetical instances of beam failure;

[0456] Information on the number of assumed beam failure instances;

[0457] Temporal information of hypothesized beam failure instances;

[0458] an indication of a hypothetical beam failure event;

[0459] Timing information of hypothetical beam failure events;

[0460] Hypothetical radio link failure event;

[0461] Indication of beam failure recovery.

[0462] In some embodiments of the present application, the time information of the assumed beam failure instance includes at least one of the following:

[0463] The starting time unit of the hypothetical beam failure instance;

[0464] The end time unit of the hypothetical beam failure instance;

[0465] Duration units of a hypothetical beam failure instance.

[0466] In some embodiments of the present application, the time information of the assumed beam failure event includes at least one of the following:

[0467] The starting time unit of the assumed beam failure event;

[0468] The end time unit of the assumed beam failure event;

[0469] Duration units of a hypothetical beam failure event.

[0470] In some embodiments of the present application, the second indication information includes at least one of the following:

[0471] Instruction information for postponing the sending of the sixth information; instruction information for postponing the receiving of the sixth information; starting time unit for postponing the sending of the sixth information; ending time unit for postponing the sending of the sixth information; duration unit for postponing the sending of the sixth information; starting time unit for postponing the receiving of the sixth information; ending time unit for postponing the receiving of the sixth information; duration unit for postponing the receiving of the sixth information.

[0472] The beam failure processing method provided in the embodiment of the present application can achieve Figure 7 The various processes implemented in the illustrated method embodiments achieve the same technical effects, and to avoid repetition, they will not be described again here.

[0473] The beam failure processing method provided in the embodiment of the present application can be executed by a beam failure processing device. In the embodiment of the present application, the beam failure processing device performing the beam failure processing method is taken as an example to illustrate the beam failure processing device provided in the embodiment of the present application.

[0474] like Figure 9As shown, the beam failure processing device 900 includes the following modules:

[0475] A first determining module 910 is configured to determine a hypothetical beam failure, where the hypothetical beam failure includes a hypothetical beam failure event or a hypothetical beam failure instance;

[0476] A first sending module 920 is configured to send first information based on an assumed beam failure;

[0477] The first information includes at least one of the following:

[0478] Information about assumed beam failures;

[0479] first indication information, the first indication information is used to instruct to postpone sending or receiving the second information;

[0480] First request information, the first request information is used to request adjustment of beam-related information.

[0481] By using the apparatus provided in the embodiments of the present application, by exchanging information related to a hypothetical beam failure, a first information receiver can facilitate performing related operations based on the hypothetical beam failure related information. For example, the apparatus can determine a hypothetical beam failure based on the hypothetical beam failure related information, or determine a hypothetical beam failure event based on the hypothetical beam failure related information, and not send or receive related information within a time unit corresponding to the hypothetical beam failure event, or perform a beam failure recovery process based on the hypothetical beam failure related information. In other words, by exchanging information related to the hypothetical beam failure, it is possible to intervene in the beam failure in advance, reduce the probability of beam failure, reduce communication resource waste, and ensure communication stability. By instructing the first indication information to postpone the sending or receiving of the second information, communication resources can be saved. Because if a beam failure is determined to occur in the future, continuing to send or receive some channels or signals within the time unit corresponding to the hypothetical beam failure event is considered meaningless and will result in a waste of communication resources. The first indication information can indicate the postponement of the sending or receiving of the second information, such as not sending or receiving the second information within the time unit corresponding to the hypothetical beam failure event, to save communication resources. By requesting to adjust beam-related information through the first request information, the waste of communication resources can be reduced. If it is determined that beam failure will occur in the future, then by adjusting the beam-related information in advance, the beam failure may be avoided or reduced, thereby enhancing communication stability, effectively utilizing communication resources, and reducing the waste of communication resources.

[0482] In some embodiments of the present application, when the assumed beam failure includes a assumed beam failure event, the first determining module 910 is specifically configured to:

[0483] Identify a hypothetical beam failure event based on at least one of the following:

[0484] the number of assumed beam failure instances;

[0485] the number of indications of assumed beam failure instances;

[0486] The beam failure instance indication information is associated with the number of assumed beam failure instances.

[0487] In some embodiments of the present application, the beam failure processing apparatus 900 further includes a first processing module configured to:

[0488] Not sending or receiving third information within a time unit corresponding to the assumed beam failure event;

[0489] Alternatively, a reference signal for beam failure detection is sent or received within a time unit corresponding to the assumed beam failure event.

[0490] In some embodiments of the present application, when the first information includes information related to assumed beam failure, the first sending module 920 is specifically configured to perform at least one of the following:

[0491] Send information related to the assumed beam failure to the network side device;

[0492] Send information related to the assumed beam failure to the terminal's upper layer.

[0493] In some embodiments of the present application, the assumed beam failure related information includes at least one of the following:

[0494] Indication of hypothetical instances of beam failure;

[0495] Information on the number of assumed beam failure instances;

[0496] Temporal information of hypothesized beam failure instances;

[0497] an indication of a hypothetical beam failure event;

[0498] Timing information of hypothetical beam failure events;

[0499] Hypothetical radio link failure event;

[0500] Indication of beam failure recovery.

[0501] In some embodiments of the present application, the time information of the assumed beam failure instance includes at least one of the following:

[0502] The starting time unit of the hypothetical beam failure instance;

[0503] The end time unit of the hypothetical beam failure instance;

[0504] Duration units of a hypothetical beam failure instance.

[0505] In some embodiments of the present application, the time information of the assumed beam failure event includes at least one of the following:

[0506] The starting time unit of the assumed beam failure event;

[0507] The end time unit of the assumed beam failure event;

[0508] Duration units of a hypothetical beam failure event.

[0509] In some embodiments of the present application, the first indication information includes at least one of the following:

[0510] Instruction information for postponing the sending of the second information; instruction information for postponing the receiving of the second information; starting time unit for postponing the sending of the second information; ending time unit for postponing the sending of the second information; duration unit for postponing the sending of the second information; starting time unit for postponing the receiving of the second information; ending time unit for postponing the receiving of the second information; duration unit for postponing the receiving of the second information.

[0511] In some embodiments of the present application, the first request information includes at least one of the following:

[0512] A first request, where the first request is used to request switching of the beam prediction range;

[0513] A second request, where the second request is used to request switching of a beam prediction range of the beam prediction model;

[0514] A third request, the third request is used to request switching of the beam prediction model;

[0515] A fourth request, where the fourth request is used to request beam switching;

[0516] A fifth request, where the fifth request is used to request measurement of a beam outside the beam prediction range;

[0517] A sixth request is used to request measurement of a beam outside the beam prediction range of the beam prediction model;

[0518] A seventh request is used to request measurement of a standby beam;

[0519] An eighth request is used to request deactivation of the beam prediction model;

[0520] A ninth request is used to request reactivation of the beam prediction model;

[0521] The tenth request is used to request to return to the beam failure recovery monitoring mode;

[0522] The eleventh request is used to request activation of resources of a reference signal for beam failure detection.

[0523] In some embodiments of the present application, the first request information is associated with at least one of the following:

[0524] Recommended beam prediction range;

[0525] The beam prediction range of the recommended beam prediction model;

[0526] Recommended measurement beam;

[0527] Recommended measurement beam range.

[0528] The beam failure processing device 900 provided in the embodiment of the present application can achieve Figure 5 The various processes implemented in the illustrated method embodiments achieve the same technical effects, and to avoid repetition, they will not be described again here.

[0529] like Figure 10 As shown, the beam failure processing device 1000 includes the following modules:

[0530] A first receiving module 1010 is configured to receive first information;

[0531] The first information includes at least one of the following:

[0532] Information related to a hypothetical beam failure, where the hypothetical beam failure includes a hypothetical beam failure event or a hypothetical beam failure instance;

[0533] first indication information, the first indication information is used to instruct to postpone sending or receiving the second information;

[0534] First request information, the first request information is used to request adjustment of beam-related information.

[0535] The device provided in the embodiment of the present application is used to receive first information, which includes at least one of information related to a hypothetical beam failure, first indication information, and first request information. By interacting with information related to the hypothetical beam failure, it is convenient for the first information receiver to perform relevant operations based on the information related to the hypothetical beam failure, such as determining a hypothetical beam failure based on information related to the hypothetical beam failure, or determining a hypothetical beam failure event based on information related to the hypothetical beam failure, not sending or receiving relevant information within a time unit corresponding to the hypothetical beam failure event, or performing a beam failure recovery process based on information related to the hypothetical beam failure. That is to say, through the interaction of information related to the hypothetical beam failure, it may be possible to intervene in the beam failure in advance, reduce the probability of beam failure, reduce the waste of communication resources, and ensure communication stability. By instructing the postponement of sending or receiving the second information through the first indication information, communication resources can be saved. This is because if it is determined that a beam failure will occur in the future, then continuing to send or receive some channels or signals within the time unit corresponding to the assumed beam failure event is considered meaningless and will result in a waste of communication resources. The first indication information can indicate the postponement of sending or receiving the second information, such as not sending or receiving the second information within the time unit corresponding to the assumed beam failure event, to save communication resources. Requesting adjustment of beam-related information through the first request information can reduce the waste of communication resources. This is because if it is determined that a beam failure will occur in the future, then adjusting the beam-related information in advance may avoid or reduce the beam failure, thereby enhancing communication stability, effectively utilizing communication resources, and reducing the waste of communication resources.

[0536] In some embodiments of the present application, the beam failure processing apparatus 1000 further includes a second processing module configured to:

[0537] In a case where the first information includes information related to an assumed beam failure, not sending or receiving fourth information within a time unit corresponding to the assumed beam failure;

[0538] or, in a case where the first information includes information related to an assumed beam failure, sending or receiving a reference signal for beam failure detection within a time unit corresponding to the assumed beam failure;

[0539] or, in a case where the first information includes first indication information, postponing sending or postponing receiving the second information according to the first indication information;

[0540] Alternatively, when the first information includes first request information, at least one of the following is performed according to the first request information:

[0541] Switching the beam prediction range or instructing to switch the beam prediction range;

[0542] Switching the beam prediction range of the beam prediction model or indicating switching the beam prediction range of the beam prediction model;

[0543] Switching a beam prediction model or instructing to switch a beam prediction model;

[0544] Switching beams or instructing beam switching;

[0545] Indicates beams outside the measurement beam prediction range;

[0546] indicating a beam outside a beam prediction range of a measurement beam prediction model;

[0547] Indicates measurement of standby beam;

[0548] Deactivating a beam prediction model or instructing deactivation of the beam prediction model;

[0549] reactivating a beam prediction model or instructing to reactivate a beam prediction model;

[0550] Fallback beam failure recovery monitoring mode or indication of fallback beam failure recovery monitoring mode;

[0551] Activate the reference signal resources used for beam failure detection.

[0552] In some embodiments of the present application, the assumed beam failure related information includes at least one of the following:

[0553] Indication of hypothetical instances of beam failure;

[0554] Information on the number of assumed beam failure instances;

[0555] Temporal information of hypothesized beam failure instances;

[0556] an indication of a hypothetical beam failure event;

[0557] Timing information of hypothetical beam failure events;

[0558] Hypothetical radio link failure event;

[0559] Indication of beam failure recovery.

[0560] In some embodiments of the present application, the time information of the assumed beam failure instance includes at least one of the following:

[0561] The starting time unit of the hypothetical beam failure instance;

[0562] The end time unit of the hypothetical beam failure instance;

[0563] Duration units of a hypothetical beam failure instance.

[0564] In some embodiments of the present application, the time information of the assumed beam failure event includes at least one of the following:

[0565] The starting time unit of the assumed beam failure event;

[0566] The end time unit of the assumed beam failure event;

[0567] Duration units of a hypothetical beam failure event.

[0568] In some embodiments of the present application, the first indication information includes at least one of the following:

[0569] Instruction information for postponing the sending of the second information; instruction information for postponing the receiving of the second information; starting time unit for postponing the sending of the second information; ending time unit for postponing the sending of the second information; duration unit for postponing the sending of the second information; starting time unit for postponing the receiving of the second information; ending time unit for postponing the receiving of the second information; duration unit for postponing the receiving of the second information.

[0570] In some embodiments of the present application, the first request information includes at least one of the following:

[0571] A first request, where the first request is used to request switching of the beam prediction range;

[0572] A second request, where the second request is used to request switching of a beam prediction range of the beam prediction model;

[0573] A third request, the third request is used to request switching of the beam prediction model;

[0574] A fourth request, where the fourth request is used to request beam switching;

[0575] A fifth request, where the fifth request is used to request measurement of a beam outside the beam prediction range;

[0576] A sixth request is used to request measurement of a beam outside the beam prediction range of the beam prediction model;

[0577] A seventh request is used to request measurement of a standby beam;

[0578] An eighth request is used to request deactivation of the beam prediction model;

[0579] A ninth request is used to request reactivation of the beam prediction model;

[0580] The tenth request is used to request to return to the beam failure recovery monitoring mode;

[0581] The eleventh request is used to request activation of resources of a reference signal for beam failure detection.

[0582] In some embodiments of the present application, the first request information is associated with at least one of the following:

[0583] Recommended beam prediction range; recommended beam prediction range of the beam prediction model; recommended measurement beam; recommended measurement beam range.

[0584] The beam failure processing device 1000 provided in the embodiment of the present application can achieve Figure 6 The various processes implemented in the illustrated method embodiments achieve the same technical effects, and to avoid repetition, they will not be described again here.

[0585] like Figure 11 As shown, the beam failure processing device 1100 includes the following modules:

[0586] A second determining module 1110 is configured to determine a hypothetical beam failure, where the hypothetical beam failure includes a hypothetical beam failure event or a hypothetical beam failure instance;

[0587] A second sending module 1120 is configured to send fifth information based on an assumed beam failure;

[0588] The fifth information includes at least one of the following:

[0589] Information about assumed beam failures;

[0590] The second indication information is used to indicate the postponement of sending or receiving the sixth information.

[0591] By applying the device provided in the embodiment of the present application, after determining the assumed beam failure, fifth information is sent based on the assumed beam failure, and the fifth information includes information related to the assumed beam failure or second indication information. By interacting with information related to the assumed beam failure, the fifth information recipient is facilitated to perform relevant operations based on the information related to the assumed beam failure, such as determining the assumed beam failure based on information related to the assumed beam failure, or determining the assumed beam failure event based on information related to the assumed beam failure, not sending or receiving relevant information within the time unit corresponding to the assumed beam failure event, or performing a beam failure recovery process based on information related to the assumed beam failure. That is to say, through the interaction of information related to the assumed beam failure, it may be possible to intervene in the beam failure in advance, reduce the probability of beam failure, reduce the waste of communication resources, and ensure communication stability. By instructing the postponement of sending or receiving the sixth information through the second indication information, communication resources can be saved. Because if it is determined that a beam failure will occur in the future, then continuing to send or receive some channels or signals within the time unit corresponding to the assumed beam failure event is considered meaningless and will cause a waste of communication resources. The second indication information can indicate the postponement of sending or receiving the sixth information, such as not sending or receiving the sixth information within the time unit corresponding to the assumed beam failure event, so as to save communication resources.

[0592] In some embodiments of the present application, when the assumed beam failure includes a assumed beam failure event, the second determining module 1110 is specifically configured to:

[0593] Identify a hypothetical beam failure event based on at least one of the following:

[0594] the number of assumed beam failure instances;

[0595] the number of indications of assumed beam failure instances;

[0596] The beam failure instance indication information is associated with the number of assumed beam failure instances.

[0597] In some embodiments of the present application, the beam failure processing apparatus 1100 further includes a third processing module configured to:

[0598] Delaying sending or receiving seventh information within a time unit corresponding to the assumed beam failure event;

[0599] Alternatively, a reference signal for beam failure detection is sent or received within a time unit corresponding to the assumed beam failure event.

[0600] In some embodiments of the present application, the assumed beam failure related information includes at least one of the following:

[0601] Indication of hypothetical instances of beam failure;

[0602] Information on the number of assumed beam failure instances;

[0603] Temporal information of hypothesized beam failure instances;

[0604] an indication of a hypothetical beam failure event;

[0605] Timing information of hypothetical beam failure events;

[0606] Hypothetical radio link failure event;

[0607] Indication of beam failure recovery.

[0608] In some embodiments of the present application, the time information of the assumed beam failure instance includes at least one of the following:

[0609] The starting time unit of the hypothetical beam failure instance;

[0610] The end time unit of the hypothetical beam failure instance;

[0611] Duration units of a hypothetical beam failure instance.

[0612] In some embodiments of the present application, the time information of the assumed beam failure event includes at least one of the following:

[0613] The starting time unit of the assumed beam failure event;

[0614] The end time unit of the assumed beam failure event;

[0615] Duration units of a hypothetical beam failure event.

[0616] In some embodiments of the present application, the second indication information includes at least one of the following:

[0617] Instruction information for postponing the sending of the sixth information; instruction information for postponing the receiving of the sixth information; starting time unit for postponing the sending of the sixth information; ending time unit for postponing the sending of the sixth information; duration unit for postponing the sending of the sixth information; starting time unit for postponing the receiving of the sixth information; ending time unit for postponing the receiving of the sixth information; duration unit for postponing the receiving of the sixth information.

[0618] The beam failure processing device 1100 provided in the embodiment of the present application can achieve Figure 7 The various processes implemented in the illustrated method embodiments achieve the same technical effects, and to avoid repetition, they will not be described again here.

[0619] like Figure 12As shown, the beam failure processing device 1200 includes the following modules:

[0620] The second receiving module 1210 is configured to receive fifth information;

[0621] The fifth information includes at least one of the following:

[0622] Information related to a hypothetical beam failure, where the hypothetical beam failure includes a hypothetical beam failure event or a hypothetical beam failure instance;

[0623] The second indication information is used to indicate the postponement of sending or receiving the sixth information.

[0624] The device provided in the embodiment of the present application is used to receive fifth information, which includes information related to a hypothetical beam failure or second indication information. By interacting with information related to the hypothetical beam failure, the fifth information receiver is able to perform relevant operations based on the information related to the hypothetical beam failure, such as determining a hypothetical beam failure based on information related to the hypothetical beam failure, or determining a hypothetical beam failure event based on information related to the hypothetical beam failure, not sending or receiving relevant information within a time unit corresponding to the hypothetical beam failure event, or performing a beam failure recovery process based on information related to the hypothetical beam failure. That is to say, through the interaction of information related to the hypothetical beam failure, it may be possible to intervene in the beam failure in advance, reduce the probability of beam failure, reduce the waste of communication resources, and ensure communication stability. By instructing the postponement of sending or receiving the sixth information through the second indication information, communication resources can be saved. Because if it is determined that a beam failure will occur in the future, then continuing to send or receive some channels or signals within the time unit corresponding to the assumed beam failure event is considered meaningless and will cause a waste of communication resources. The second indication information can indicate the postponement of sending or receiving the sixth information, such as not sending or receiving the sixth information within the time unit corresponding to the assumed beam failure event, so as to save communication resources.

[0625] In some embodiments of the present application, the beam failure processing apparatus further includes a fourth processing module configured to:

[0626] In a case where the fifth information includes information related to an assumed beam failure, not sending or receiving the eighth information within a time unit corresponding to the assumed beam failure;

[0627] or, when the fifth information includes information related to an assumed beam failure, sending or receiving a reference signal for beam failure detection within a time unit corresponding to the assumed beam failure;

[0628] Alternatively, when the fifth information includes the second indication information, the sending or receiving of the sixth information is postponed according to the second indication information.

[0629] In some embodiments of the present application, the assumed beam failure related information includes at least one of the following:

[0630] Indication information of a hypothetical beam failure instance; information on the number of hypothetical beam failure instances; time information of a hypothetical beam failure instance; indication information of a hypothetical beam failure event; time information of a hypothetical beam failure event; hypothetical wireless link failure event; indication information of beam failure recovery.

[0631] In some embodiments of the present application, the time information of the assumed beam failure instance includes at least one of the following:

[0632] The starting time unit of the hypothetical beam failure instance;

[0633] The end time unit of the hypothetical beam failure instance;

[0634] Duration units of a hypothetical beam failure instance.

[0635] In some embodiments of the present application, the time information of the assumed beam failure event includes at least one of the following:

[0636] The starting time unit of the assumed beam failure event;

[0637] The end time unit of the assumed beam failure event;

[0638] Duration units of a hypothetical beam failure event.

[0639] In some embodiments of the present application, the second indication information includes at least one of the following:

[0640] Instruction information for postponing the sending of the sixth information; instruction information for postponing the receiving of the sixth information; starting time unit for postponing the sending of the sixth information; ending time unit for postponing the sending of the sixth information; duration unit for postponing the sending of the sixth information; starting time unit for postponing the receiving of the sixth information; ending time unit for postponing the receiving of the sixth information; duration unit for postponing the receiving of the sixth information.

[0641] The beam failure processing device 1200 provided in the embodiment of the present application can achieve Figure 8 The various processes implemented in the illustrated method embodiments achieve the same technical effects, and to avoid repetition, they will not be described again here.

[0642] like Figure 13As shown, the embodiment of the present application further provides a communication device 1300, including a processor 1301 and a memory 1302, wherein the memory 1302 stores a program or instruction that can be run on the processor 1301. For example, when the communication device 1300 is a terminal, the program or instruction is executed by the processor 1301 to implement the above Figure 5 or Figure 8 When the communication device 1300 is a network side device, the program or instruction is executed by the processor 1301 to implement the above Figure 6 or Figure 7 The various steps of the method embodiment shown can achieve the same technical effect, and to avoid repetition, they will not be described again here.

[0643] The embodiment of the present application also provides a terminal, including a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run a program or instruction to implement the following Figure 5 or Figure 8 The steps in the method embodiment shown. This terminal embodiment corresponds to the above-mentioned terminal side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this terminal embodiment and can achieve the same technical effect. Specifically, Figure 14 A schematic diagram of the structure of a terminal for implementing an embodiment of the present application.

[0644] The terminal 1400 includes but is not limited to: a radio frequency unit 1401, a network module 1402, an audio output unit 1403, an input unit 1404, a sensor 1405, a display unit 1406, a user input unit 1407, an interface unit 1408, a memory 1409 and at least some of the components of the processor 1410.

[0645] Those skilled in the art will understand that the terminal 1400 may also include a power supply (such as a battery) to power each component, and the power supply may be logically connected to the processor 1410 through a power management system, thereby implementing functions such as charging, discharging, and power consumption management through the power management system. Figure 14 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be repeated here.

[0646] It should be understood that in an embodiment of the present application, the input unit 1404 may include a graphics processing unit (GPU) 14041 and a microphone 14042, and the graphics processor 14041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1406 may include a display panel 14061, and the display panel 14061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1407 includes a touch panel 14071 and at least one of the other input devices 14072. The touch panel 14071 is also called a touch screen. The touch panel 14071 may include two parts: a touch detection device and a touch controller. Other input devices 14072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and an operating stick, which will not be repeated here.

[0647] In the embodiment of the present application, after receiving downlink data from a network-side device, the radio frequency unit 1401 may transmit the data to the processor 1410 for processing. Furthermore, the radio frequency unit 1401 may send uplink data to the network-side device. Typically, the radio frequency unit 1401 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0648] The memory 1409 can be used to store software programs or instructions and various data. The memory 1409 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 1409 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 1409 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0649] Processor 1410 may include one or more processing units. Optionally, processor 1410 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 1410.

[0650] The processor 1410 is configured to determine a hypothetical beam failure, where the hypothetical beam failure includes a hypothetical beam failure event or a hypothetical beam failure instance;

[0651] The radio frequency unit 1401 is configured to send first information;

[0652] The first information includes at least one of the following:

[0653] Information about assumed beam failures;

[0654] first indication information, the first indication information is used to instruct to postpone sending or receiving the second information;

[0655] First request information, the first request information is used to request adjustment of beam-related information.

[0656] Alternatively, the radio frequency unit 1401 is configured to receive fifth information;

[0657] The fifth information includes at least one of the following:

[0658] Information related to a hypothetical beam failure, where the hypothetical beam failure includes a hypothetical beam failure event or a hypothetical beam failure instance;

[0659] The second indication information is used to indicate the postponement of sending or receiving the sixth information.

[0660] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment and achieve the same or corresponding technical effects. To avoid repetition, it will not be described here.

[0661] The embodiment of the present application further provides a network side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the following Figure 6 or Figure 7 The network side device embodiment corresponds to the above network side device method embodiment, and each implementation process and implementation method of the above method embodiment are applicable to the network side device embodiment and can achieve the same technical effect.

[0662] Specifically, the embodiment of the present application also provides a network side device. Figure 15 As shown, network-side device 1500 includes an antenna 1501, a radio frequency device 1502, a baseband device 1503, a processor 1504, and a memory 1505. Antenna 1501 is connected to radio frequency device 1502. In the uplink direction, radio frequency device 1502 receives information via antenna 1501 and sends the received information to baseband device 1503 for processing. In the downlink direction, baseband device 1503 processes the information to be transmitted and sends it to radio frequency device 1502. Radio frequency device 1502 processes the received information and then sends it through antenna 1501.

[0663] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 1503 , which includes a baseband processor.

[0664] The baseband device 1503 may include, for example, at least one baseband board on which a plurality of chips are arranged, such as Figure 15 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 1505 through a bus interface to call the program in the memory 1505 to execute the network side device operations shown in the above method embodiment.

[0665] The network side device may further include a network interface 1506 , which is, for example, a Common Public Radio Interface (CPRI).

[0666] Specifically, the network side device 1500 of the embodiment of the present application further includes: instructions or programs stored in the memory 1505 and executable on the processor 1504, and the processor 1504 calls the instructions or programs in the memory 1505 to execute. Figure 10 or Figure 11 The methods executed by the modules shown achieve the same technical effects, so they will not be described here to avoid repetition.

[0667] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0668] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0669] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned method embodiment and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0670] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0671] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0672] The embodiment of the present application also provides a wireless communication system, including: a terminal and a network side device, the terminal can be used to perform the above Figure 5 The steps of the method embodiment shown above, the network side device can be used to perform the above Figure 6 Steps of the method embodiment are shown.

[0673] The embodiment of the present application also provides a wireless communication system, including: a terminal and a network side device, the terminal can be used to perform the above Figure 8 The steps of the method embodiment shown above, the network side device can be used to perform the above Figure 7 Steps of the method embodiment are shown.

[0674] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0675] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0676] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A beam failure processing method, characterized in that: include: The terminal determines a hypothetical beam failure, where the hypothetical beam failure includes a hypothetical beam failure event or a hypothetical beam failure instance; The terminal sends first information based on the assumed beam failure; The first information includes at least one of the following: Information about assumed beam failures; first indication information, where the first indication information is used to instruct to postpone sending or receiving the second information; First request information, where the first request information is used to request adjustment of beam-related information.

2. The method according to claim 1, characterized in that In a case where the assumed beam failure includes an assumed beam failure event, the terminal determines the assumed beam failure, including: The terminal determines a hypothetical beam failure event according to at least one of the following: the number of assumed beam failure instances; the number of indications of assumed beam failure instances; The beam failure instance indication information is associated with the number of assumed beam failure instances.

3. The method according to claim 1 or 2, characterized in that The method further comprises: The terminal does not send or receive third information within a time unit corresponding to the assumed beam failure event; The third information includes at least one of the following: Physical downlink control channel, physical uplink control channel, physical downlink shared channel, physical uplink shared channel, channel state information reference signal, channel sounding reference signal.

4. The method according to any one of claims 1 to 3, characterized in that The method further comprises: The terminal sends or receives a reference signal for beam failure detection within a time unit corresponding to the assumed beam failure event.

5. The method according to any one of claims 1 to 4, characterized in that In a case where the first information includes information related to assumed beam failure, the terminal sends the first information including at least one of the following: The terminal sends the assumed beam failure related information to the network side device; The terminal sends the assumed beam failure related information to a higher layer of the terminal.

6. The method according to any one of claims 1 to 5, characterized in that The information related to the assumed beam failure includes at least one of the following: Indication of hypothetical instances of beam failure; Information on the number of assumed beam failure instances; Temporal information of hypothesized beam failure instances; an indication of a hypothetical beam failure event; Timing information of hypothetical beam failure events; Hypothetical radio link failure event; Indication of beam failure recovery.

7. The method according to any one of claims 1 to 6, characterized in that The first indication information includes at least one of the following: Instruction information for postponing sending of the second information; Instruction information for postponing reception of the second information; Postponing the start time unit of sending the second information; Postponing the end time unit of sending the second information; a duration unit for postponing sending the second information; Postponing a start time unit for receiving the second information; Postponing the end time unit of receiving the second information; The duration unit for delaying receiving the second information.

8. The method according to any one of claims 1 to 7, characterized in that The first request information includes at least one of the following: A first request, wherein the first request is used to request switching of a beam prediction range; a second request, wherein the second request is used to request switching of a beam prediction range of the beam prediction model; a third request, wherein the third request is used to request switching of the beam prediction model; a fourth request, where the fourth request is used to request beam switching; a fifth request, the fifth request being used to request measurement of a beam outside a beam prediction range; a sixth request, the sixth request being used to request measurement of a beam outside a beam prediction range of the beam prediction model; a seventh request, the seventh request being used to request measurement of a standby beam; An eighth request, the eighth request being used to request deactivation of a beam prediction model; A ninth request, wherein the ninth request is used to request reactivation of the beam prediction model; A tenth request, the tenth request being used to request a fallback beam failure recovery monitoring mode; An eleventh request is used to request activation of resources of a reference signal for beam failure detection.

9. The method according to any one of claims 1 to 8, characterized in that The first request information is associated with at least one of the following: Recommended beam prediction range; The beam prediction range of the recommended beam prediction model; Recommended measurement beam; Recommended measurement beam range.

10. A beam failure processing method, characterized in that: include: The network side device receives the first information; The first information includes at least one of the following: Information related to a hypothetical beam failure, wherein the hypothetical beam failure includes a hypothetical beam failure event or a hypothetical beam failure instance; first indication information, where the first indication information is used to instruct to postpone sending or receiving the second information; First request information, where the first request information is used to request adjustment of beam-related information.

11. The method according to claim 10, characterized in that In a case where the first information includes the assumed beam failure related information, the method further includes: The network-side device does not send or receive fourth information within a time unit corresponding to the assumed beam failure; or, the network-side device sends or receives a reference signal for beam failure detection within a time unit corresponding to the assumed beam failure; The fourth information includes at least one of the following: Physical downlink control channel, physical uplink control channel, physical downlink shared channel, physical uplink shared channel, channel state information reference signal, channel sounding reference signal.

12. The method according to claim 10 or 11, characterized in that In a case where the first information includes the first indication information, the method further includes: The network side device postpones sending or receiving the second information according to the first instruction information.

13. The method according to any one of claims 10 to 12, characterized in that In a case where the first information includes the first request information, the method further includes: The network-side device performs at least one of the following according to the first request information: Switching the beam prediction range or instructing to switch the beam prediction range; Switching the beam prediction range of the beam prediction model or indicating switching the beam prediction range of the beam prediction model; Switching a beam prediction model or instructing to switch a beam prediction model; Switching beams or instructing beam switching; Indicates beams outside the measurement beam prediction range; indicating a beam outside a beam prediction range of a measurement beam prediction model; Indicates measurement of standby beam; Deactivating a beam prediction model or instructing deactivation of the beam prediction model; reactivating a beam prediction model or instructing to reactivate a beam prediction model; Fallback beam failure recovery monitoring mode or indication of fallback beam failure recovery monitoring mode; Activate the reference signal resources used for beam failure detection.

14. A beam failure processing method, characterized in that: include: The network-side device determines a hypothetical beam failure, where the hypothetical beam failure includes a hypothetical beam failure event or a hypothetical beam failure instance; The network-side device sends fifth information based on the assumed beam failure; The fifth information includes at least one of the following: Information about assumed beam failures; Second indication information, where the second indication information is used to indicate to postpone sending or receiving sixth information.

15. The method according to claim 14, characterized in that In a case where the assumed beam failure includes an assumed beam failure event, the network-side device determines the assumed beam failure, including: The network-side device determines a hypothetical beam failure event based on at least one of the following: the number of assumed beam failure instances; the number of indications of assumed beam failure instances; The beam failure instance indication information is associated with the number of assumed beam failure instances.

16. The method according to claim 14 or 15, characterized in that The method further comprises: The network side device does not send or receive the seventh information within the time unit corresponding to the assumed beam failure event.

17. The method according to any one of claims 14 to 16, characterized in that The method further comprises: The network-side device sends or receives a reference signal for beam failure detection within a time unit corresponding to the assumed beam failure event.

18. The method according to any one of claims 14 to 17, characterized in that The information related to the assumed beam failure includes at least one of the following: Indication of hypothetical instances of beam failure; Information on the number of assumed beam failure instances; Temporal information of hypothesized beam failure instances; an indication of a hypothetical beam failure event; Timing information of hypothetical beam failure events; Hypothetical radio link failure event; Indication of beam failure recovery.

19. The method according to any one of claims 14 to 18, characterized in that The second indication information includes at least one of the following: Instruction information for postponing sending of the sixth information; Instruction information for postponing reception of the sixth information; Postponing the start time unit of sending the sixth information; Postponing the end time unit of sending the sixth information; a duration unit for postponing sending the sixth information; Postponing a start time unit for receiving the sixth information; Postponing the end time unit of receiving the sixth information; The duration unit for delaying receiving the sixth information.

20. A beam failure processing method, characterized in that: include: The terminal receives the fifth information; The fifth information includes at least one of the following: Information related to a hypothetical beam failure, wherein the hypothetical beam failure includes a hypothetical beam failure event or a hypothetical beam failure instance; Second indication information, where the second indication information is used to indicate to postpone sending or receiving sixth information.

21. The method according to claim 20, characterized in that In a case where the fifth information includes the assumed beam failure related information, the method further includes: The terminal does not send or receive eighth information within a time unit corresponding to the assumed beam failure; or, the terminal sending or receiving a reference signal for beam failure detection within a time unit corresponding to the assumed beam failure; The eighth information includes at least one of the following: Physical downlink control channel, physical uplink control channel, physical downlink shared channel, physical uplink shared channel, channel state information reference signal, channel sounding reference signal.

22. The method according to claim 20 or 21, characterized in that In a case where the fifth information includes the second indication information, the method further includes: The terminal postpones sending or receiving the sixth information according to the second indication information.

23. A beam failure processing device, characterized in that: include: A first determining module is configured to determine a hypothetical beam failure, wherein the hypothetical beam failure includes a hypothetical beam failure event or a hypothetical beam failure instance; A first sending module, configured to send first information based on the assumed beam failure; The first information includes at least one of the following: Information about assumed beam failures; first indication information, where the first indication information is used to instruct to postpone sending or receiving the second information; First request information, where the first request information is used to request adjustment of beam-related information.

24. The device according to claim 23, characterized in that In a case where the assumed beam failure includes a assumed beam failure event, the first determining module is specifically configured to: Identify a hypothetical beam failure event based on at least one of the following: the number of assumed beam failure instances; the number of indications of assumed beam failure instances; The beam failure instance indication information is associated with the number of assumed beam failure instances.

25. The device according to claim 23 or 24, characterized in that The beam failure processing apparatus further includes a first processing module, configured to: Not sending or receiving third information within a time unit corresponding to the assumed beam failure event; Alternatively, a reference signal for beam failure detection is sent or received within a time unit corresponding to the assumed beam failure event.

26. The device according to any one of claims 23 to 25, characterized in that In a case where the first information includes information related to assumed beam failure, the first sending module is specifically configured to perform at least one of the following: Sending information related to the assumed beam failure to a network-side device; Send the assumed beam failure related information to a higher layer of the terminal.

27. A beam failure processing device, characterized in that: include: A first receiving module, configured to receive first information; The first information includes at least one of the following: Information related to a hypothetical beam failure, wherein the hypothetical beam failure includes a hypothetical beam failure event or a hypothetical beam failure instance; first indication information, where the first indication information is used to instruct to postpone sending or receiving the second information; First request information, where the first request information is used to request adjustment of beam-related information.

28. The device according to claim 27, characterized in that The beam failure processing apparatus further includes a second processing module, configured to: In a case where the first information includes the assumed beam failure related information, not sending or receiving fourth information within a time unit corresponding to the assumed beam failure; or, in a case where the first information includes the information related to the assumed beam failure, sending or receiving a reference signal for beam failure detection within a time unit corresponding to the assumed beam failure; or, in a case where the first information includes the first indication information, postponing sending or postponing receiving the second information according to the first indication information; Alternatively, when the first information includes the first request information, at least one of the following is performed according to the first request information: Switching the beam prediction range or instructing to switch the beam prediction range; Switching the beam prediction range of the beam prediction model or indicating switching the beam prediction range of the beam prediction model; Switching a beam prediction model or instructing to switch a beam prediction model; Switching beams or instructing beam switching; Indicates beams outside the measurement beam prediction range; indicating a beam outside a beam prediction range of a measurement beam prediction model; Indicates measurement of standby beam; Deactivating a beam prediction model or instructing deactivation of the beam prediction model; reactivating a beam prediction model or instructing to reactivate a beam prediction model; Fallback beam failure recovery monitoring mode or indication of fallback beam failure recovery monitoring mode; Activate the reference signal resources used for beam failure detection.

29. A beam failure processing device, characterized in that: include: a second determining module, configured to determine a hypothetical beam failure, wherein the hypothetical beam failure includes a hypothetical beam failure event or a hypothetical beam failure instance; A second sending module, configured to send fifth information based on the assumed beam failure; The fifth information includes at least one of the following: Information about assumed beam failures; Second indication information, where the second indication information is used to indicate to postpone sending or receiving sixth information.

30. The device according to claim 29, characterized in that In a case where the assumed beam failure includes a assumed beam failure event, the second determining module is specifically configured to: Identify a hypothetical beam failure event based on at least one of the following: the number of assumed beam failure instances; the number of indications of assumed beam failure instances; The beam failure instance indication information is associated with the number of assumed beam failure instances.

31. The device according to claim 29 or 30, characterized in that The beam failure processing apparatus further includes a third processing module, configured to: not sending or receiving seventh information within a time unit corresponding to the assumed beam failure event; Alternatively, a reference signal for beam failure detection is sent or received within a time unit corresponding to the assumed beam failure event.

32. A beam failure processing device, characterized in that: include: A second receiving module, configured to receive fifth information; The fifth information includes at least one of the following: Information related to a hypothetical beam failure, wherein the hypothetical beam failure includes a hypothetical beam failure event or a hypothetical beam failure instance; Second indication information, where the second indication information is used to indicate to postpone sending or receiving sixth information.

33. The device according to claim 32, characterized in that The beam failure processing apparatus further includes a fourth processing module, configured to: In a case where the fifth information includes the assumed beam failure related information, not sending or receiving eighth information within a time unit corresponding to the assumed beam failure; or, when the fifth information includes the assumed beam failure related information, sending or receiving a reference signal for beam failure detection within a time unit corresponding to the assumed beam failure; Or, in a case where the fifth information includes the second indication information, sending or receiving the sixth information is postponed according to the second indication information.

34. A terminal, characterized in that: It includes a processor and a memory, the memory storing a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, it implements the steps of the beam failure processing method as described in any one of claims 1 to 9, or implements the steps of the beam failure processing method as described in any one of claims 20 to 22.

35. A network side device, characterized in that: It includes a processor and a memory, the memory storing a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, it implements the steps of the beam failure processing method as described in any one of claims 10 to 13, or implements the steps of the beam failure processing method as described in any one of claims 14 to 19.

36. A readable storage medium, characterized in that The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, it implements the steps of the beam failure processing method as described in any one of claims 1 to 9, or implements the steps of the beam failure processing method as described in any one of claims 10 to 13, or implements the steps of the beam failure processing method as described in any one of claims 14 to 19, or implements the steps of the beam failure processing method as described in any one of claims 20 to 22.

Images