Method for beam fault procedure of sidelink

Abstract

The present application describes a method for sidelink beam failure indication in which a sidelink BFI is triggered based on a PSFCH carrying a sidelink HARQ feedback, and the BFI is declared at the transmitter side, unicast communication is established, and the reception of HARQ feedback with ACK or NACK is expected at the transmitter side, characterized in that the BFI is declared at the receiver side, and the HARQ feedback with ACK or NACK is received at the receiver side. Parameters NLAST (the number of feedbacks to be considered), RBFI (the ratio of NACK to ACK triggering BFI), and NBFI (the number of NACKs triggering BFI) are used to verify the ratio (C1) between NACK to ACK and / or the number (C2) of NACKs within a variable time window defined by the last N received feedbacks.

Description

Technical Field

[0001] This disclosure relates to wireless communication, and more specifically, to technologies and equipment for indicating sidelink beam faults in vehicle-to-everything (V2X) communications. Background Technology

[0002] LTE Vehicle-to-Everything (V2X) Transport Modes: Release 14 introduces two new V2X communication modes (Modes 3 and 4) specifically designed for vehicle-to-vehicle (V2V) communication. In Mode 3, the cellular network selects and manages the radio resources used by vehicles for direct V2V communication. In Mode 4, the V2X User Equipment (UE) autonomously selects the radio resources for its direct V2V communication. LTE V2X Mode 4 can operate without cellular coverage and is therefore considered the baseline V2V mode, as security applications cannot depend on cellular coverage availability. Mode 4 includes a distributed scheduling scheme for vehicles to select their radio resources and includes support for distributed congestion control. In LTE V2X, only broadcast V2X communication is supported.

[0003] Wireless communication systems may include or provide support for various types of communication systems, such as vehicle-related communication systems (e.g., vehicle-to-everything (V2X) communication systems). Vehicles can use vehicle-related communication systems to improve safety and help prevent collisions. Information about severe weather, nearby accidents, road conditions, and / or other information can be transmitted to the driver via vehicle-related communication systems. In some cases, side-link user equipment (UEs) of vehicles can communicate directly with each other using D2D communication via device-to-device (D2D) wireless links. These communications may be referred to as side-link communications.

[0004] New Radio (NR) V2X Transmission Modes: Similar to LTE V2X transmission modes 3 and 4, NR supports two modes: Mode 1 and Mode 2 for V2X transmission in Release 16. In NR V2X, sidelink resource allocation modes 1 and 2 are supported. In Mode 1, the network (e.g., gNB) schedules sidelink resources for V2X UEs for sidelink transmission. In Mode 2, the V2X UE determines its sidelink resources for sidelink transmission within sidelink resources configured by the base station or pre-configured sidelink resources. Mode 1 allows the network (e.g., gNB) to assign sidelink resources via the Uu interface for both dedicated sidelink carriers and shared licensed carriers between the Uu and the sidelink. Resources for sidelink transmission can be dynamically allocated or pre-configured by Radio Resource Control (RRC), or based on activation and deactivation. Section 9 of 3GPP TS 36.211 V15.5.0 concerning sidelinks and Section 14 of 3GPP TS 36.213 V15.5.0 concerning sidelink-related UE procedures are incorporated herein by reference in their entirety.

[0005] With the increasing demand for sidelink communication, different V2X communication systems compete for the same wireless communication resources. Furthermore, some sidelink UEs may be power-limited. Therefore, there is a need to improve the efficiency of sidelink wireless communication.

[0006] US 2022 / 0399927 A1 describes methods, systems, and apparatus for implementing BFR, SL-RS for BFD, radio link monitoring, or frequency-assisted beam fault recovery, etc. Link recovery and side-link beamforming are described. BFI criteria are determined using N NACKs and no responses. No information is provided regarding adaptive signal transmission mechanisms.

[0007] US 2022 / 0006505 A1 describes a method for wireless communication. This method of wireless communication by a first sidelink UE measures multiple reference signals periodically transmitted by a second sidelink UE using multiple receive beams corresponding to reference signals in response to a beam fault declared by the first UE. The method also selects one of the reference signals that meets certain conditions. The method further includes notifying the second sidelink UE of the selected reference signal using a beam corresponding to the selected reference signal. Another method of wireless communication by a first sidelink UE includes periodically transmitting a multi-beam fault recovery (BFR) reference signal to the second sidelink UE via multiple transmit beams. The method also includes receiving from the second sidelink UE an indication of the selected beam for communication between the first and second sidelink UEs. The method notifies the second sidelink UE of successful beam fault recovery. The application describes that if the received signal strength of the BFD reference signal drops below a threshold a certain number (N) times before the BFD timer expires, UE2 declares a beam fault (BF) and triggers beam fault recovery.

[0008] Support for sidelink beam management is well-known. The reuse of existing sidelink CSI frameworks and Uu beam management concepts is also defined as much as possible. Based on the definition provided for NR Uu in 3GPP TR 38.802, SL beam management is "acquiring and maintaining a set of [UE] beams that can be used for [SL] transmission / reception". The general procedures are those for initial beam pairing, and those for initial beam pairing and sidelink beam failure indication. Furthermore, the information provided by the PHY layer to the MAC layer related to sidelink beam failure instances is investigated. Summary of the Invention

[0009] This application addresses the criteria problem for efficiently triggering sidelink BFI. This problem is solved by verifying the ratio (C1) between NACK and ACK and / or the number of NACKs (C2) within a variable time window defined by the last N received feedbacks.

[0010] This problem is solved by a method for beam fault indication of a side link in a wireless communication system, wherein the side link beam fault indication / instance (side link BFI) is triggered based on parameters of a PSFCH carrying side link HARQ feedback, and the BFI is declared on the transmitter side, unicast communication is established, and feedback with ACK or NACK is expected to be received on the transmitter side, characterized by the use of parameter N LAST (Number of feedbacks to consider), R BFI (The ratio of NACK to ACK that triggers BFI) and N BFI (Number of NACKs that trigger BFI) in order to verify the ratio (C1) between NACKs and ACKs and / or the number of NACKs (C2) within a variable time window defined by the last N received feedbacks.

[0011] In some embodiments of the method according to the first aspect, the method is characterized in that the parameter N LAST (Number of feedbacks to consider), R BFI (The ratio of NACK to ACK that triggers BFI) and N BFI The value of (number of NACKs that trigger BFI) is (pre-)configured.

[0012] In some embodiments of the method according to the first aspect, the method is characterized in that the parameter N used to trigger the BFI is... LAST (Number of feedbacks to consider), R BFI (The ratio of NACK to ACK that triggers BFI) and N BFI The value of (the number of NACKs that trigger BFI) is encoded.

[0013] In some embodiments of the method according to the first aspect, the method is characterized in that the encoding is a table that depends on the service type and / or QoS and / or mobility conditions and / or load conditions.

[0014] In some embodiments of the method according to the first aspect, the method is characterized in that the parameter N LAST (Number of feedbacks to consider), R BFI (The ratio of NACK to ACK that triggers BFI) and N BFI The value of (NACK number that triggers BFI) is negotiated between the transmitter (TX) and receiver (RX) during the initial beam pairing process and is indicated and adjusted by the network or by the user equipment (UE).

[0015] In some embodiments of the method according to the first aspect, the method is characterized in that, if necessary, the criteria for changing these parameters depend on the implementation within the wireless communication system.

[0016] In some embodiments of the method according to the first aspect, the method is characterized in that the parameter can be configured / associated with one or more unicast transmissions.

[0017] In some embodiments of the method according to the first aspect, the method is characterized in that the parameter is a cell-specific configuration / association.

[0018] In some embodiments of the method according to the first aspect, the method is characterized in that the parameter is configured / associated based on UE pairs / groups.

[0019] In some embodiments of the method according to the first aspect, the method is characterized in that the parameter is configured / associated based on the value of a parameter corresponding to a UE-related factor, wherein the UE-related factor is parameter N. LAST (Number of feedbacks to consider), R BFI (The ratio of NACK to ACK that triggers BFI) and N BFI The value of (the number of NACKs that trigger BFI).

[0020] In some embodiments of the method according to the first aspect, the method is characterized in that the parameter is configured / associated based on the service type and / or QoS.

[0021] In some embodiments of the method according to the first aspect, the method is characterized in that the parameter is configured / associated based on a geographic region.

[0022] In some embodiments of the method according to the first aspect, the method is characterized in that the parameter is configured / associated based on mobility conditions.

[0023] The method according to any of the preceding claims is characterized in that the parameter is configured / associated based on the UE type and / or the UE's capabilities.

[0024] In some embodiments of the method according to the first aspect, the method is characterized in that the parameter is configured / associated based on multiple downlink schemes, wherein the multiple downlink schemes may be SIB and / or RRC within the FR2 licensed spectrum.

[0025] In some embodiments of the method according to the first aspect, the method is characterized in that, during unicast link establishment, the parameter is configured and / or associated by negotiation from a predefined set.

[0026] According to a second aspect, this disclosure relates to an apparatus for beam fault indication of a side link, comprising a wireless transceiver and a processor coupled to a memory storing computer program instructions configured to implement the steps of the method described in the first aspect.

[0027] According to a third aspect, this disclosure relates to a user equipment (UE) including the equipment according to the second aspect, wherein the value of the timer (T) BFI ) and the ratio of NACK to ACK used to trigger BFI (R BFI (Instructed and adjusted by the UE)

[0028] According to the fourth aspect, this disclosure relates to a base station gNB, which includes the equipment of the second aspect, wherein parameter N LAST (Number of feedbacks to consider), R BFI (The ratio of NACK to ACK that triggers BFI) and N BFI The value of (number of NACKs that trigger BFI) is indicated and adjusted by the base station gNB.

[0029] According to a fourth aspect, this disclosure relates to a wireless communication system, wherein a base station gNB according to the fourth aspect includes a processor coupled to a memory storing computer program instructions configured to implement the steps of the method according to the first aspect, wherein a user equipment (UE) according to the second aspect includes a processor coupled to a memory storing computer program instructions configured to implement the steps of the method according to the first aspect. Attached Figure Description

[0030] Figure 1 This illustrates a mobility management scenario.

[0031] Figure 2 The BFI determination process is illustrated.

[0032] Figure 3 The flow of this method is shown. Detailed Implementation

[0033] Some embodiments of the examples contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are also included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0034] Generally, all terms used herein should be interpreted according to their common meaning in the relevant art, unless the context in which the term is used explicitly gives and / or implies a different meaning. Unless otherwise expressly stated, all references to a / an / element, apparatus, component, element, step, etc., are openly interpreted as referring to at least one instance of that element, apparatus, component, step, etc. The steps of any method disclosed herein need not be performed in the exact order disclosed, unless a step is explicitly described as occurring after or before another step and / or where an implicit step must occur after or before another step. Where appropriate, any feature of any embodiment of the embodiments disclosed herein may be applied to any other embodiment. Similarly, any advantage of any embodiment of this embodiment may be applied to any other embodiment, and vice versa. Other objects, features, and advantages of the appended embodiments will be apparent from the following description.

[0035] In some embodiments, the more general term "network node" may be used, and this term may correspond to any type of radio network node or any network node that communicates with the UE (directly or via another node) and / or with another network node. Examples of network nodes are NodeB, MeNB, ENB, network nodes belonging to MCG or SCG, base station (BS), multi-standard radio (MSR) radio nodes (such as MSR BS), eNodeB, gNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node control relay, base transceiver (BTS), access point (AP), transport point, transport node, RRU, RRH, nodes in distributed antenna system (DAS), core network nodes (e.g., mobile switching center (MSC), mobility management entity (MME), etc.), operation and maintenance (O&M), operations support system (OSS), self-optimizing network (SON), location node (e.g., evolved serving mobile location center (E-SMLC)), minimized drive test (MDT), test equipment (physical node or software), etc.

[0036] In some embodiments, the non-limiting terms User Equipment (UE) or Wireless Device may be used, and the term may refer to any type of wireless device that communicates with a network node and / or with another UE in a cellular or mobile communication system. Examples of UEs include target devices, device-to-device (D2D) UEs, machine-type UEs or UEs capable of machine-to-machine (M2M) communication, PDAs, PADs, tablet computers, mobile terminals, smartphones, laptop embedded devices (LEE), laptop mounted devices (LME), USB dongles, UE class M1, UE class M2, ProSe UE, V2V UE, V2X UE, etc.

[0037] Furthermore, terms such as base station / gNodeB and UE should be considered non-restrictive and, in particular, do not imply any hierarchical relationship between the two; generally speaking, "gNodeB" can be considered device 1 and "UE" can be considered device 2, and the two devices communicate with each other via a radio channel. And in the following text, the transmitter or receiver can be either a gNodeB (gNB) or a UE.

[0038] As those skilled in the art will understand, aspects of the embodiments may be embodied as systems, apparatus, methods, or program products. Therefore, embodiments may take the form of entirely hardware embodiments, entirely software embodiments (including firmware, resident software, microcode, etc.), or embodiments combining software and hardware aspects.

[0039] For example, the disclosed embodiments can be implemented as hardware circuitry, including custom-designed very large-scale integration (“VLSI”) circuitry or gate arrays, off-the-shelf semiconductors (such as logic chips, transistors, or other discrete components). The disclosed embodiments can also be implemented in programmable hardware devices such as field-programmable gate arrays, programmable array logic, programmable logic devices, etc. As another example, the disclosed embodiments may include one or more physical or logical blocks of executable code, which may, for example, be organized as objects, procedures, or functions.

[0040] Furthermore, embodiments may take the form of a program product embodied in one or more computer-readable storage devices, which store machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage device may be tangible, non-transitory, and / or non-transferable. The storage device may not contain signals. In one embodiment, the storage device uses only signals to access the code.

[0041] Any combination of one or more computer-readable media may be used. A computer-readable medium may be a computer-readable storage medium. A computer-readable storage medium may be a storage device for storing code. A storage device may be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor systems, apparatuses, or any suitable combination thereof.

[0042] More specific examples of storage devices (a non-exhaustive list) will include the following: electrical connections having one or more wires; portable computer floppy disks; hard disks; random access memory (“RAM”); read-only memory (“ROM”); erasable programmable read-only memory (“EPROM” or flash memory); portable optical disc read-only memory (“CD-ROM”); optical storage devices; magnetic storage devices; or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium can be any tangible medium that can contain or store programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0043] The code used to perform the operations of the embodiments can be any number of lines and can be written in any combination of one or more programming languages, including object-oriented programming languages ​​(such as Python, Ruby, Java, Smalltalk, C++, etc.), as well as conventional procedural programming languages ​​(such as the "C" programming language, etc.) and / or machine languages ​​(such as assembly language). The code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer via any type of network (including a local area network ("LAN"), a wireless LAN ("WLAN"), or a wide area network ("WAN"), or can be connected to an external computer (e.g., via the Internet through an Internet service provider ("ISP").

[0044] Furthermore, the features, structures, or characteristics described in the embodiments can be combined in any suitable manner. Numerous specific details, such as examples of programming, software modules, user selection, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., are provided in the following description to provide a thorough understanding of the embodiments. However, those skilled in the art will recognize that the embodiments can be practiced without one or more of these specific details or using other methods, components, materials, etc. In other instances, well-known structures, materials, or operations have not been shown or described in detail to avoid obscuring aspects of the embodiments. References to “an embodiment,” “embodiment,” or similar language throughout the specification mean that a particular feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment. Therefore, unless expressly specified otherwise, the phrases “in one embodiment,” “in an embodiment,” and similar language appearing throughout the specification may, but not necessarily all, refer to the same embodiment, but rather mean “one or more, but not all, embodiments.” Unless expressly specified otherwise, the terms “comprising,” “including,” “having,” and variations thereof mean “including, but not limited to,” “including.” Unless expressly specified otherwise, the enumeration of items does not imply that any or all items in the item are mutually exclusive. Unless otherwise expressly specified, the terms “a,” “an,” and “the” also mean “one or more.”

[0045] The following description refers to schematic flowcharts and / or block diagrams of methods, apparatus, systems, and program products according to embodiments. It should be understood that each block of the schematic flowcharts and / or block diagrams, and combinations of blocks in the schematic flowcharts and / or block diagrams, can be implemented by code. This code can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing equipment to produce a machine such that instructions executable via the processor of the computer or other programmable data processing equipment establish components for implementing the functions / actions specified in the flowcharts and / or block diagrams.

[0046] The code may also be stored in a storage device that can instruct a computer, other programmable data processing equipment or other device to operate in a particular manner, such that the instructions stored in the storage device produce an article of writing including instructions that implement the functions / actions specified in the flowchart and / or block diagram.

[0047] The code can also be loaded onto a computer, other programmable data processing equipment or other device, such that a series of operational steps to be performed on the computer, other programmable equipment or other device produce a computer-implemented process, and that the code executing on the computer or other programmable equipment provides a process for implementing the functions / actions specified in the flowchart and / or block diagram.

[0048] The flowcharts and / or block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products according to various embodiments. In this regard, each block in the flowcharts and / or block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of that code for implementing the specified logical function.

[0049] It should also be noted that in some alternative implementations, the functions indicated in the boxes may not occur in the order shown in the diagram. For example, depending on the functionality involved, two boxes shown consecutively may actually be executed substantially concurrently, or the boxes may sometimes be executed in reverse order. Other steps and methods that are functionally, logically, or effectically equivalent to one or more boxes or portions thereof in the diagram shown can be envisioned.

[0050] While various arrow and line types may be used in flowcharts and / or block diagrams, they are not intended to limit the scope of the corresponding embodiments. In practice, some arrows or other connecting symbols may be used to indicate only the logical flow of the depicted embodiment. For example, arrows may indicate waiting or monitoring periods of unspecified duration between enumerated steps of the depicted embodiment. It should also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, may be implemented by a system based on dedicated hardware or a combination of dedicated hardware and code that performs the specified function or action.

[0051] The description of the elements in each figure can be referenced to the elements in the preceding figures. Throughout all figures, the same numbers refer to the same elements, including alternative embodiments of the same elements.

[0052] The detailed description following with reference to the accompanying drawings is intended as a description of various configurations and is not intended to represent only configurations in which the concepts described herein can be practiced. The detailed description includes specific details and is intended to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. Although terms from 3GPP 5G NR may be used in this disclosure to exemplify embodiments herein, this should not be construed as limiting the scope of the invention.

[0053] This disclosure relates to a wireless communication system, which may be, for example, a 5G NR wireless communication system. More specifically, it refers to a RAN (Radio Access Network) within the wireless communication system for exchanging data with a UE via radio signals. For example, the RAN may transmit data to the UE (Downlink DL), such as data received from the core network (CN). The RAN may also receive data from the UE (Uplink UL), which may be forwarded to the CN.

[0054] In the example shown, the RAN includes a base station (BS). Of course, the RAN can include more than one BS to increase the coverage of the wireless communication system. Depending on the implemented wireless communication standard, each of these BSs can be referred to as an NB, eNodeB (or eNB), gNodeB (or gNB in ​​the case of a 5G NR wireless communication system), access point, etc.

[0055] The UE is located within the coverage of the BS. The coverage of the BS corresponds, for example, to an area where the UE can decode the PDCCH transmitted by the BS.

[0056] Examples of wireless devices suitable for implementing any of the methods discussed in this disclosure at the UE correspond to devices that provide wireless connectivity to a RAN (Radio Range) of a wireless communication system and can be used to exchange data with that RAN. Such wireless devices can be included in the UE. The UE can be, for example, a cellular phone, a wireless modem, a wireless communication device, a handheld device, a laptop computer, etc. The UE can also be an Internet of Things (IoT) device, such as a wireless camera, a smart sensor, a smart meter, smart glasses, a vehicle (manned or unmanned), a GPS device, etc., or any other device capable of running applications that require exchanging data with a remote receiver via a wireless device.

[0057] The wireless device includes one or more processors and one or more memories. The one or more processors may include, for example, a central processing unit (CPU), a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc. The one or more memories may include any type of computer-readable volatile and non-volatile memory (magnetic hard disk, solid-state disk, optical disk, electronic storage, etc.). The one or more memories may store a computer program product in the form of a set of program code instructions to be executed by the one or more processors to implement all or part of the steps of a method for exchanging data performed on the UE side according to any embodiment of the embodiments disclosed herein.

[0058] The wireless device may also include a main radio (MR) unit. The MR unit corresponds to the main wireless communication unit of the wireless device and is used to exchange data with the base station (BS) of the RAN using radio signals. The MR unit can implement one or more wireless communication protocols and may be, for example, a 3G, 4G, 5G, NR, WiFi, WiMax, or other transceivers. In a preferred embodiment, the MR unit corresponds to a 5G NR wireless communication unit.

[0059] Figure 1 The mobility management scenario that has already been described is shown.

[0060] Figure 2The BFI determination process is illustrated. Essentially, this process defines the (re)configuration of criteria. This reconfiguration determines the BFI criteria, which is central to this application. The event is the declaration of a Beam Failure Indication (BFI). The declaration of a Beam Failure Indication (BFI) is used in the beam recovery process, meaning that the recovery process is triggered when a beam failure is declared.

[0061] Figure 3 This indicates the flow of the method. According to this application, the solution is based on a side-link BFI triggered by a PSFCH carrying side-link HARQ feedback, meaning the BFI can be declared on the transmitter side. Unicast communication is established, and feedback (HARQ: ACK or NACK) is expected to be received on the transmitter side. The exact values ​​used for the parameters: N LAST (Number of feedbacks to consider), R BFI (The ratio of NACK to ACK that triggers BFI) and N BFI The number of NACKs that trigger BFI can be (pre-)configured and / or encoded in the specification—for example, a table depending on service type / QoS, mobility conditions, load conditions, etc.—and / or negotiated between TX and RX during initial beamp pairing, and may be indicated and adjusted by the network or by the UE. If necessary, the guidelines for changing these parameters pertain to the implementation. The aforementioned parameters can be configured / associated with one or more unicast transmissions.

[0062] Unicast transmission (PSSCH) is sent from TX to RX via one or more transmissions, as follows:

[0063] initialization :N NACK = 0, N TOTAL = 0.

[0064] Surveillance :

[0065] • If a NACK is received, then N NACK = N NACK +1

[0066] • If an ACK is received, then N ACK = N ACK +1

[0067] • N TOTAL = N TOTAL +1

[0068] • Calculate M (according to formula (e1)).

[0069] Therefore, (e1) is defined by the following equation.

[0070]

[0071] and

[0072] Conditional checkpoint: N is received at TX. LAST Feedback (N) TOTAL = N LAST )

[0073] RX sends a unicast / feedback transmission (PSFCH) with ACK or NACK.

[0074] HARQ burst: RX transmits multiple ACKs and / or NACKs.

[0075] • Yes: TX check (depending on the criteria to be used: C1 and / or C2, whether)

[0076] C1: M ≥ R BFI

[0077] C2: N NACK ≥ N BFI

[0078] • no: initialization and Surveillance

[0079] The previously mentioned criterion M(e1) is defined by the following equation:

[0080]

[0081] This formula captures the idea of ​​checking the ratio between ACK and NACK.

[0082] This formula captures the idea of ​​checking the ratio between NACK and ACK.

[0083] Only when N is received LAST Only after receiving feedback will M (C1) and / or N be checked. NACK (C2).

[0084] The combination of this ratio and timer provides a flexible and reliable way to control / monitor beam quality.

[0085] abbreviation

[0086] ACK confirmation

[0087] BFD Beam Fault Detection

[0088] BFI Beam Fault Indication / Example

[0089] BFR beam fault recovery

[0090] BFRQBFR Request

[0091] BFRRBFR response

[0092] BWP bandwidth portion

[0093] CBD candidate beam determination

[0094] CBG code block group

[0095] CLI Cross-Link Interference

[0096] CP loop prefix

[0097] CPUCSI processing unit

[0098] CQI Channel Quality Indicator

[0099] CRB Public Resource Block

[0100] CRC Cyclic Redundancy Check

[0101] CRICSI-RS resource indicator

[0102] CSI Channel Status Information

[0103] CSI-RS Channel State Information Reference Signal

[0104] CSI-RSRPCSI Reference Signal Received Power

[0105] CSI-RSRQCSI reference signal reception quality

[0106] CSI-SINRCSI Signal-to-Interference-Noise Ratio

[0107] CW code

[0108] DCI downlink control information

[0109] DL downlink

[0110] DM-RS demodulation reference signal

[0111] DRX discontinuous reception

[0112] EPRE Energy of each resource particle

[0113] HARQ Hybrid Automatic Repeat Request

[0114] IAB-MT Integrated Access and Backhaul - Mobile Terminal

[0115] L1-RSRP Layer 1 Reference Signal Received Power

[0116] LI layer indicator

[0117] MCS modulation and coding scheme

[0118] NACK (Negative Confirmation)

[0119] PDCCH Physical Downlink Control Channel

[0120] PDSCH Physical Downlink Shared Channel

[0121] PMI Precoding Matrix Indicator

[0122] PRB Physical Resource Block

[0123] PRG precoded resource block group

[0124] PRS positioning reference signal

[0125] PSS master synchronization signal

[0126] PT-RS phase tracking reference signal

[0127] PUCCH (Physical Uplink Control Channel)

[0128] QCL Quasi-co-addressable

[0129] RB resource blocks

[0130] RBG resource block group

[0131] RI rank indicator

[0132] RIV resource indicator value

[0133] RS reference signal

[0134] SCI sidelink control information

[0135] SLIV start and length indicators

[0136] SR scheduling request

[0137] SRS detection reference signal

[0138] SS synchronization signal

[0139] SS-RSRP SS reference signal received power

[0140] SS-RSRQSS reference signal reception quality

[0141] SSS auxiliary synchronization signal

[0142] SS-SINR (Signal-to-Interference-Ratio)

[0143] TB transport block

[0144] TCI Transport Configuration Indicator

[0145] TDM Time Division Multiplexing

[0146] UE User Equipment

[0147] UL uplink

Claims

1. A method for beam fault indication of a side link in a wireless communication system, wherein, The side-link beam fault indication / instance (side-link BFI) is triggered based on the PSFCH carrying side-link HARQ feedback, and the BFI is declared on the transmitter side to establish unicast communication. The transmitter side expects to receive HARQ feedback with ACK or NACK. The characteristic is that parameter N is used. LAST (Number of feedbacks to consider), R BFI (The ratio of NACK to ACK that triggers BFI) and N BFI (Number of NACKs that trigger BFI) in order to verify the ratio (C1) between NACKs and ACKs and / or the number of NACKs (C2) within a variable time window defined by the last N received feedbacks.

2. The method according to claim 1, wherein, The parameter N LAST (Number of feedbacks to consider), R BFI (The ratio of NACK to ACK that triggers BFI) and N BFI The value of (number of NACKs that trigger BFI) is (pre-)configured.

3. The method according to claim 1 or 2, wherein, The parameter N used to trigger BFI LAST (Number of feedbacks to consider), R BFI (The ratio of NACK to ACK that triggers BFI) and N BFI The value of (the number of NACKs that trigger BFI) is encoded.

4. The method according to claims 1 to 3, wherein the encoding is a table that depends on the service type and / or QoS and / or mobility conditions and / or load conditions.

5. The method according to claims 1 to 4, wherein, The parameter N LAST (Number of feedbacks to consider), R BFI (The ratio of NACK to ACK that triggers BFI) and N BFI The value of (NACK number that triggers BFI) is negotiated between the transmitter (TX) and receiver (RX) during the initial beam pairing process and is indicated and adjusted by the network or by the user equipment (UE).

6. The method according to any one of the preceding claims, characterized in that, If necessary, the criteria for changing these parameters depend on the implementation within the wireless communication system.

7. The method according to any one of the preceding claims, characterized in that, The parameters can be configured / associated with one or more unicast transmissions.

8. The method according to any one of the preceding claims, characterized in that, The parameters can be cell-specific configurations / associations.

9. The method according to any one of the preceding claims, characterized in that, The parameters are configured / associated based on UE pairs / groups.

10. The method according to any one of the preceding claims, characterized in that, The parameter is configured / associated based on the value of the parameter corresponding to the UE-related factors, wherein the UE-related factors are the parameter N. LAST (Number of feedbacks to consider), R BFI (The ratio of NACK to ACK that triggers BFI) and N BFI The value of (the number of NACKs that trigger BFI).

11. The method according to any one of the preceding claims, characterized in that, Configure / associate the parameters based on service type and / or QoS.

12. The method according to any one of the preceding claims, characterized in that, Configure / associate the parameters based on geographic region.

13. The method according to any one of the preceding claims, characterized in that, Configure / associate the parameters based on mobility conditions.

14. The method according to any one of the preceding claims, characterized in that, Configure / associate the parameters based on the UE type and / or the capabilities of the UE.

15. The method according to any one of the preceding claims, characterized in that, The parameters are configured / associated based on multiple downlink schemes, wherein the multiple downlink schemes can be SIBs and / or RRCs within the FR2 licensed spectrum.

16. The method according to any one of claims 1 to 14, characterized in that, During unicast link establishment, the parameters are configured and / or associated by negotiating from a predefined set.

17. An apparatus for beam fault indication of a side link, comprising a wireless transceiver and a processor coupled to a memory, the memory storing computer program instructions configured to implement the steps of the method as claimed in claims 1 to 16.

18. A user equipment (UE) comprising the apparatus of claim 17, wherein, The value of the timer (T) BFI ) and the ratio of NACK to ACK used to trigger BFI (R BFI (Instructed and adjusted by the UE) 19. A base station gNB, the base station gNB comprising the equipment according to claim 17, wherein, The parameter N LAST (Number of feedbacks to consider), R BFI (The ratio of NACK to ACK that triggers BFI) and N BFI The value of (number of NACKs that trigger BFI) is indicated and adjusted by the base station gNB.

20. A wireless communication system, wherein, The gNB of claim 19 includes a processor coupled to a memory storing computer program instructions configured to implement the steps of the method as described in claims 1 to 16. The user equipment (UE) of claim 18 includes a processor coupled to a memory storing computer program instructions configured to implement the steps of the method of claims 1 to 16.

Images