Side chain fault detection and recovery

Abstract

The invention relates to side chain fault detection and recovery. Apparatuses, methods, and systems for side chain fault detection and recovery are disclosed. A method (1200) includes receiving (1202) information indicating a set of side chain fault detection resources corresponding to at least one configured side chain bandwidth portion. The method (1200) includes determining (1204) a radio link quality for the at least one configured sidechain bandwidth portion based on the set of sidechain fault detection resources. The method (1200) includes detecting (1206) a side chain failure based on radio link quality. The method (1200) includes initiating (1208) a side chain fault recovery process based on the side chain fault.

Description

[0001] The application is a divisional application of the application which entered the Chinese national phase on July 27, 2021, with PCT application number PCT / IB2020 / 000187, international application date February 3, 2020, Chinese application number 202080011057.5, and invention name “Sidechain Fault Detection and Recovery”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims priority to U.S. Patent Application Serial No. 62 / 800,031, filed on February 1, 2019, for Karthikeyan Ganesan, entitled “PROCEDURES FOR FAST SIDELINK LINK AND BEAM RECOVERY,” which is incorporated herein by reference in its entirety. Technical Field

[0004] The subject matter disclosed herein relates generally to wireless communications and, more particularly, to sidelink failure detection and recovery. Background Art

[0005] The following abbreviations are defined herein, at least some of which are referred to in the following description: 3rd Generation Partnership Project (“3GPP”), 5th Generation (“5G”), positive acknowledgement (“ACK”), aggregation level (“AL”), access and mobility management function (“AMF”), access point (“AP”), access stratum (“AS”), beam failure detection (“BFD”), beam failure recovery (“BFR”), binary phase shift keying (“BPSK”), base station (“BS”), buffer status report (“BSR”), bandwidth (“BW”), bandwidth part (“BWP”), cell RNTI (“C-RNTI”), carrier aggregation (“CA”), contention-based random access (“CBR”). A”), Clear Channel Assessment (“CCA”), Common Control Channel (“CCCH”), Control Channel Element (“CCE”), Cyclic Delay Diversity (“CDD”), Code Division Multiple Access (“CDMA”), Control Element (“CE”), Contention Free Random Access (“CFRA”), Closed Loop (“CL”), Coordinated Multipoint (“CoMP”), Channel Occupancy Time (“COT”), Cyclic Prefix (“CP”), Cyclic Redundancy Check (“CRC”), Channel State Information (“CSI”), Channel State Information-Reference Signal (“CSI-RS”), Common Search Space (“CSS”), Control Resource Set (“CORESET”), Discrete Fourier Transform Spread Spectrum (“DFTS”), Downlink Control Information (“DCI”), Downlink (“DL”), Demodulation Reference Signal (“DMRS”), Data Radio Bearer (“DRB”), Discontinuous Reception (“DRX”), Downlink Pilot Time Slot (“DwPTS”), Enhanced Clear Channel Assessment (“eCCA”), Enhanced Mobile Broadband (“eMBB”), Evolved Node B (“eNB”), Effective Isotropic Radiated Power (“EIRP”), European Telecommunications Standards Institute (“ETSI”), Frame-based Equipment (“FBE”), Frequency Division Duplexing (“FDD”), Frequency Division Multiplexing (“FDM”), Frequency Division Multiple Access (“FDMA”), Frequency Division Orthogonal Cover Codes (“FD-OCC”), Frequency Range 1–6G Hz and / or 410 MHz to 7125 MHz (“FR1”), frequency range 2 – 24.25 GHz to 52.6 GHz (“FR2”), 5G Node B or Next Generation Node B (“gNB”), Global Navigation Satellite System (“GNSS”), General Packet Radio Service (“GPRS”), Guard Period (“GP”), Global Positioning System (“GPS”), Global System for Mobile Communications (“GSM”), Globally Unique Temporary UE Identifier (“GUTI”), Home AMF (“hAMF”), Hybrid Automatic Repeat Request (“HARQ”), Home Location Register (“HLR”), Handover (“HO”), Home PLMN (“HPLMN”),Home Subscriber Server (“HSS”), Identity or Identifier (“ID”), Information Element (“IE”), International Mobile Equipment Identity (“IMEI”), International Mobile Subscriber Identity (“IMSI”), International Mobile Telecommunications (“IMT”), Internet of Things (“IoT”), Layer 1 (“L1”), Layer 2 (“L2”), Layer 3 (“L3”), Authorization Assisted Access (“LAA”), Load-based Equipment (“LBE”), Listen Before Talk (“LBT”), Logical Channel (“LCH”), Logical Channel Priority (“LCP”), Log-Likelihood Ratio (“LLR”), Long Term Evolution (“LTE”), Multiple Access (“MA”), Medium Access Control (“MAC”), Multimedia Broadcast Multicast Service (“MBMS”), Modulation and Coding Scheme (“MCS”), Master Information Block (“MIB”), Multiple Input Multiple Output (“MIMO”), Mobility Management (“MM”), Mobility Management Entity (“MME”), Mobile Network Operator (“MNO”), Massive MTC (“mMTC”), Maximum Power Reduction (“MPR”), Machine Type Communication (“MTC”), Multi-User Shared Access (“MUSA”), Non-Access Stratum (“NAS”), Narrowband (“NB”), Negative Acknowledgement (“NACK”) or (“NAK”), Network Entity (“NE”), Network Function (“NF”), Non-Orthogonal Multiple Access (“NOMA”), New Radio (“NR”), Unlicensed NR ("NR-U"), Network Storage Function ("NRF"), Network Slice Instance ("NSI"), Network Slice Selection Assistance Information ("NSSAI"), Network Slice Selection Function ("NSSF"), Network Slice Selection Policy ("NSSP"), Operation and Maintenance System ("OAM"), Orthogonal Frequency Division Multiplexing ("OFDM"), Open Loop ("OL"), Other System Information ("OSI"), Power Angle Spectrum ("PAS"), Physical Broadcast Channel ("PBCH"), Power Control ("PC"), UE to UE Interface ("PC5"), Primary Cell ("PCell"), Policy Control Function ("PCF"), Physical Cell ID ("PCID"), Physical Downlink Control channel ("PDCCH"), Packet Data Convergence Protocol ("PDCP"), Packet Data Network Gateway ("PGW"), Physical Downlink Shared Channel ("PDSCH"), Graph Division Multiple Access ("PDMA"), Packet Data Unit ("PDU"), Physical Hybrid ARQ Indicator Channel ("PHICH"), Power Headroom ("PH"), Power Headroom Report ("PHR"), Physical Layer ("PHY"), Public Land Mobile Network ("PLMN"), Physical Random Access Channel ("PRACH"), Physical Resource Block ("PRB"), Physical Sidelink Control Channel ("PSCCH"), Primary and Secondary Cell ("PSCell"), Physical Sidelink Feedback Channel ("PSFCH"),Physical uplink control channel ("PUCCH"), physical uplink shared channel ("PUSCH"), quasi co-location ("QCL"), quality of service ("QoS"), quadrature phase shift keying ("QPSK"), registration area ("RA"), RA RNTI ("RA-RNTI"), radio access network ("RAN"), radio access technology ("RAT"), random access procedure ("RACH"), random access preamble identifier ("RAPID"), random access response ("RAR"), resource element group ("REG"), radio link control ("RLC"), RLC acknowledged mode ("RLC-AM"), RLC unacknowledged mode / transparent mode ("RLC-UM / TM"), radio link monitoring ("RLM"), radio network temporary identifier ("RNTI"), reference signal ("RS"), remaining minimum system information ("RMSI") ”), Radio Resource Control (“RRC”), Radio Resource Management (“RRM”), Resource Extension Multiple Access (“RSMA”), Reference Signal Received Power (“RSRP”), Round Trip Time (“RTT”), Reception (“RX”), Sparse Code Division Multiple Access (“SCMA”), Scheduling Request (“SR”), Channel Sounding Reference Signal (“SRS”), Single Carrier Frequency Division Multiple Access (“SC-FDMA”), Secondary Cell (“SCell”), Secondary Cell Group (“SCG”), Shared Channel (“SCH”), Subcarrier Spacing (“SCS”), Service Data Unit (“SDU”), Serving Gateway (“SGW”), System Information Block (“SIB”), System Information Block Type 1 (“SIB1”), System Information Block Type 2 (“SIB2”), Subscriber Identity Module (“SIM”), Signal to Interference and Noise Ratio (“SINR”), Sidelink (“SL”), Service Level Agreement (“SLA”), Sidelink Synchronization Signal (“SLSS”), Session Management Function (“SMF”), Special Cell (“SpCell”), Single Network Slice Selection Assistance Information (“S-NSSAI”), Scheduling Request (“SR”), Signaling Radio Bearer (“SRB”), Shortened TTI (“sTTI”), Synchronization Signal (“SS”), Sidelink SS B ("S-SSB"), synchronization signal block ("SSB"), supplementary uplink ("SUL"), user permanent identifier ("SUPI"), timing advance ("TA"), timing alignment timer ("TAT"), transport block ("TB"), transport block size ("TBS"), time division duplex ("TDD"), time division multiplexing ("TDM"), time division orthogonal cover code ("TD-OCC"), transmission power control ("TPC"), transmission reception point ("TRP"), transmission time interval ("TTI"), transmission ("TX"), uplink control information ("UCI"), unified data management function ("UDM"),Unified Data Repository (“UDR”), User Entity / Equipment (Mobile Terminal) (“UE”), Uplink (“UL”), UL SCH (“UL-SCH”), Universal Mobile Telecommunications System (“UMTS”), User Plane (“UP”), UP Function (“UPF”), Uplink Pilot Time Slot (“UpPTS”), Ultra-Reliable and Low Latency Communications (“URLLC”), UE Routing Policy (“URSP”), Vehicle-to-Vehicle (“V2V”), Access AMF (“vAMF”), Access NSSF (“vNSSF”), Access PLMN (“vPLMN”), and Worldwide Interoperability for Microwave Access (“WiMAX”).

[0006] In certain wireless communication networks, sidelink failures may occur. Summary of the invention

[0007] Methods for sidelink fault detection and recovery are disclosed. Devices and systems also perform the functions of the method. One embodiment of the method includes receiving information indicating a sidelink fault detection resource set corresponding to at least one configured sidelink bandwidth portion. In some embodiments, the method includes determining a radio link quality of at least one configured sidelink bandwidth portion based on the sidelink fault detection resource set. In certain embodiments, the method includes detecting a sidelink fault based on the radio link quality. In various embodiments, the method includes initiating a sidelink fault recovery procedure based on the sidelink fault.

[0008] An apparatus for sidelink fault detection and recovery includes a receiver that receives information indicating a sidelink fault detection resource set corresponding to at least one configured sidelink bandwidth portion. In some embodiments, the apparatus includes a processor that: determines a radio link quality of at least one configured sidelink bandwidth portion based on the sidelink fault detection resource set; detects a sidelink fault based on the radio link quality; and initiates a sidelink fault recovery procedure based on the sidelink fault. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] A more particular description of the embodiments briefly described above will be presented by reference to specific embodiments illustrated in the accompanying drawings. Understanding that these drawings depict only some embodiments and are therefore not to be considered limiting in scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

[0010] Figure 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for sidelink failure detection and recovery;

[0011] Figure 2 is a schematic block diagram illustrating one embodiment of an apparatus that may be used for side chain failure detection and recovery;

[0012] Figure 3 is a schematic block diagram illustrating one embodiment of an apparatus that may be used to send information;

[0013] Figure 4 is a schematic diagram illustrating one embodiment of sidelink unicast link blocking;

[0014] Figure 5 is a schematic diagram illustrating one embodiment of downlink beam loss;

[0015] Figure 6 is a schematic diagram illustrating one embodiment of uplink beam loss;

[0016] Figure 7 is a communication diagram illustrating one embodiment of side chain communication;

[0017] Figure 8 is a communication schematic diagram illustrating another embodiment of side chain communication;

[0018] Fig. 9 is a communication schematic diagram illustrating yet another embodiment of side chain communication;

[0019] Fig.10 is a communication schematic diagram illustrating another embodiment of side chain communication;

[0020] Fig.11 is a communication schematic diagram illustrating yet another embodiment of side chain communication; and

[0021] Fig.12 is a flow chart illustrating one embodiment of a method for side chain failure detection and recovery. DETAILED DESCRIPTION

[0022] As will be appreciated by those skilled in the art, aspects of the embodiments may be embodied as systems, devices, methods, or program products. Therefore, the embodiments may take the form of a complete hardware embodiment, a complete software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects, which may be collectively referred to herein as a "circuit," "module," or "system." In addition, the embodiments may take the form of a program product embodied in one or more computer-readable storage devices that store machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage device may be tangible, non-temporary, and / or non-transmitting. The storage device may not embody a signal. In a certain embodiment, the storage device uses only a signal for accessing the code.

[0023] Certain functional units described in this specification may be labeled as modules to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising a custom very large scale integrated ("VLSI") circuit or gate array, an off-the-shelf semiconductor such as a logic chip, a transistor, or other discrete components. A module may also be implemented in a programmable hardware device such as a field programmable gate array, programmable array logic, a programmable logic device, or the like.

[0024] Modules may also be implemented in code and / or software for execution by various types of processors. An identified module of code may, for example, include one or more physical or logical executable code blocks, which may, for example, be organized as objects, procedures, or functions. However, the executables identifying the modules need not be physically placed together, but may include different instructions stored in different locations, which, when logically connected together, comprise the module and achieve the stated purpose of the module.

[0025] In fact, a code module can be a single instruction, or it can be many instructions, and can even be distributed on several different code segments, different programs and multiple storage devices. Similarly, operating data can be identified and illustrated in this article within the module, and can be embodied in any suitable form and organized in the data structure of any suitable type. Operating data can be collected as a single data set, or can be distributed in different locations including different computer-readable storage devices. When a module or part of a module is implemented as software, the software part is stored on one or more computer-readable storage devices.

[0026] Any combination of one or more computer readable media may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical or semiconductor system, apparatus or device, or any suitable combination of the foregoing.

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

[0028] The code for performing the operation of the embodiment 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. and / or machine languages ​​such as assembly languages, and conventional procedural programming languages ​​such as the "C" programming language, etc. The code can be executed entirely on the user's computer, partially on the user's computer, as a stand-alone 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 case, the remote computer can be connected to the user's computer through any type of network including a local area network ("LAN") or a wide area network ("WAN"), or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0029] References throughout the specification to "an embodiment," "an embodiment," or similar language mean that a particular feature, structure, or characteristic described in conjunction with the embodiment is included in at least one embodiment. Therefore, the phrases "in one embodiment," "in an embodiment," and similar language appearing throughout the specification may, but do not necessarily, refer to the same embodiment, but rather mean "one or more but not all embodiments," unless expressly provided otherwise. The terms "comprise," "comprising," "having," and variations thereof mean "including but not limited to," unless expressly provided otherwise. An enumerated list of items does not mean that any or all of the items are mutually exclusive, unless expressly provided otherwise. The terms "one," "an," and "the" also mean "one or more," unless expressly provided otherwise.

[0030] In addition, the features, structures or characteristics of the described embodiments may be combined in any suitable manner. In the following description, a large number of specific details, such as programming examples, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., are provided to provide a thorough understanding of the embodiments. However, those skilled in the relevant art will recognize that the embodiments may be practiced without one or more of the specific details or using other methods, components, materials, etc. In other cases, well-known structures, materials or operations are not shown or described in detail to avoid confusing aspects of the embodiments.

[0031] Aspects of the embodiments are described below with reference to schematic flow charts and / or schematic block diagrams of methods, devices, systems, and program products according to the embodiments. It will be understood that each block in the schematic flow charts and / or schematic block diagrams, as well as the combination of blocks in the schematic flow charts and / or schematic block diagrams, can be implemented by code. The code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, so that instructions executed by a processor of a computer or other programmable data processing device create a device for implementing the functions / actions specified in the schematic flow charts and / or schematic block diagram blocks.

[0032] The code may also be stored in a storage device that is capable of directing a computer, other programmable data processing device, or other device to operate in a specific manner so that the instructions stored in the storage device produce an article of manufacture including instructions for implementing the functions / actions specified in the schematic flowchart and / or schematic block diagram blocks.

[0033] The code may also be loaded onto a computer, other programmable data processing device, or other device to cause a series of operational steps to be performed on the computer, other programmable device, or other device to generate a computer-implemented process, so that the code executed on the computer or other programmable device provides a process for implementing the functions / actions specified in the flowchart and / or block diagram blocks.

[0034] The schematic flow charts and / or schematic block diagrams in the figures illustrate the possible implementation architectures, functions and operations of the devices, systems, methods and program products according to various embodiments. In this regard, each block in the schematic flow charts and / or schematic block diagrams may represent a module, a segment or a portion of code, which includes one or more executable instructions of the code for implementing the specified logical function.

[0035] It should also be noted that in some alternative embodiments, the functions annotated in the blocks may not appear in the order annotated in the figure. For example, depending on the functions involved, two blocks shown in succession may actually be executed substantially simultaneously, or blocks may sometimes be executed in reverse order. Other steps and methods that are equivalent in function, logic or effect to one or more blocks or portions thereof of the illustrated figures may be envisioned.

[0036] Although various arrow types and line types can be adopted in flow charts and / or block diagrams, they are understood to not limit the scope of corresponding embodiments. In fact, some arrows or other connectors can be used to indicate only the logical flow of the depicted embodiment. For example, an arrow can indicate a waiting or monitoring period of unspecified duration between the enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagram and / or flow chart, and the combination of the blocks in the block diagram and / or flow chart, can be implemented by a system based on dedicated hardware that performs a specified function or action, or a combination of dedicated hardware and code.

[0037] The description of elements in each figure may refer to elements of previous figures. In all figures, the same reference numerals represent the same elements, including alternative embodiments of the same elements.

[0038] Figure 1 An embodiment of a wireless communication system 100 for sidelink failure detection and recovery is depicted. In one embodiment, the wireless communication system 100 includes a remote unit 102 and a network unit 104. Even if Figure 1 A specific number of remote units 102 and network units 104 are depicted in FIG. 1 , but one skilled in the art will appreciate that any number of remote units 102 and network units 104 may be included in the wireless communication system 100 .

[0039] In one embodiment, the remote unit 102 may include a computing device such as a desktop computer, a laptop computer, a personal digital assistant ("PDA"), a tablet computer, a smart phone, a smart TV (e.g., a TV connected to the Internet), a set-top box, a game console, a security system (including a security camera), a vehicle computer, a network device (e.g., a router, a switch, a modem), an aircraft, a drone, etc. In some embodiments, the remote unit 102 includes a wearable device such as a smart watch, a fitness band, an optical head-mounted display, etc. In addition, the remote unit 102 may be referred to as a user unit, a mobile device, a mobile station, a user, a terminal, a mobile terminal, a fixed terminal, a user station, a UE, a user terminal, a device, or by other terms used in the art. The remote unit 102 may communicate directly with one or more network units 104 via UL communication signals. In some embodiments, the remote unit 102 may communicate directly with other remote units 102 via sidelink communication.

[0040] The network elements 104 may be distributed over a geographic area. In some embodiments, the network elements 104 may also be referred to as access points, access terminals, base stations, base stations, node Bs, eNBs, gNBs, home node Bs, relay nodes, devices, core networks, air servers, wireless access nodes, APs, NRs, network entities, AMFs, UDMs, UDRs, UDM / UDRs, PCFs, RANs, NSSFs, or by any other terminology used in the art. The network elements 104 are typically part of a radio access network that includes one or more controllers communicatively coupled to one or more corresponding network elements 104. The radio access network is typically communicatively coupled to one or more core networks that may be coupled to other networks, such as the Internet and public switched telephone networks among other networks. These and other elements of the radio access and core networks are not illustrated, but are well known to those of ordinary skill in the art.

[0041] In one embodiment, the wireless communication system 100 complies with the NR protocol standardized in 3GPP, wherein the network unit 104 transmits using an OFDM modulation scheme on the DL and the remote unit 102 transmits using an SC-FDMA scheme or an OFDM scheme on the UL. However, more generally, the wireless communication system 100 may implement some other open or proprietary communication protocol, such as WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA2000, ZigBee, Sigfoxx, etc. The present disclosure is not intended to be limited to any particular wireless communication system architecture or protocol implementation.

[0042] The network unit 104 can serve multiple remote units 102 within a service area (eg, a cell or cell sector) via wireless communication links. The network unit 104 sends DL communication signals to serve the remote units 102 in the time, frequency, and / or spatial domains.

[0043] In one embodiment, the remote unit 102 may receive information indicating a sidelink fault detection resource set corresponding to at least one configured sidelink bandwidth portion. In some embodiments, the remote unit 102 may determine a radio link quality of the at least one configured sidelink bandwidth portion based on the sidelink fault detection resource set. In some embodiments, the remote unit 102 may detect a sidelink fault based on the radio link quality. In various embodiments, the remote unit 102 may initiate a sidelink fault recovery process based on the sidelink fault. Thus, the remote unit 102 may be used for sidelink fault detection and recovery.

[0044] Figure 2An embodiment of an apparatus 200 that can be used for side chain failure detection and recovery is depicted. The apparatus 200 includes an embodiment of a remote unit 102. In addition, the remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device such as a touch screen. In some embodiments, the remote unit 102 may not include any input device 206 and / or display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, the memory 204, the transmitter 210, and the receiver 212, and may not include the input device 206 and / or the display 208.

[0045] In one embodiment, the processor 202 may include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, the processor 202 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or a similar programmable controller. In some embodiments, the processor 202 executes instructions stored in the memory 204 to perform the methods and routines described herein. In various embodiments, the processor 202 may: determine the radio link quality of at least one configured side link bandwidth portion based on the side link failure detection resource set; detect the side link failure based on the radio link quality; and initiate a side link failure recovery process based on the side link failure. The processor 202 is communicatively coupled to the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212.

[0046] In one embodiment, memory 204 is a computer-readable storage medium. In some embodiments, memory 204 includes volatile computer storage media. For example, memory 204 may include RAM, including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and / or static RAM ("SRAM"). In some embodiments, memory 204 includes non-volatile computer storage media. For example, memory 204 may include a hard drive, flash memory, or any other suitable non-volatile computer storage device. In some embodiments, memory 204 includes volatile and non-volatile computer storage media. In some embodiments, memory 204 also stores program code and related data, such as an operating system or other controller algorithm running on remote unit 102.

[0047] In one embodiment, input device 206 may include any known computer input device, including a touch panel, button, keyboard, stylus, microphone, etc. In some embodiments, input device 206 may be integrated with display 208, for example, as a touch screen or similar touch-sensitive display. In some embodiments, input device 206 includes a touch screen so that text can be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, input device 206 includes two or more different devices, such as a keyboard and a touch panel.

[0048] In one embodiment, display 208 may include any known electronically controllable display or display device. Display 208 may be designed to output visual, auditory and / or tactile signals. In some embodiments, display 208 includes an electronic display capable of outputting visual data to a user. For example, display 208 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, display 208 may include a wearable display such as a smart watch, smart glasses, a head-up display, etc. In addition, display 208 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0049] In some embodiments, the display 208 includes one or more speakers for generating sounds. For example, the display 208 can generate an audible alarm or notification (e.g., a beep or a prompt tone). In some embodiments, the display 208 includes one or more tactile devices for generating vibration, motion, or other tactile feedback. In some embodiments, all or part of the display 208 can be integrated with the input device 206. For example, the input device 206 and the display 208 can form a touch screen or similar touch-sensitive display. In other embodiments, the display 208 can be located near the input device 206.

[0050] The transmitter 210 is used to provide UL communication signals to the Network element 104 and the receiver 212 is used to receive DL communication signals from the Network element 104, as described herein.

[0051] In some embodiments, the receiver 212 may receive information indicating a set of sidelink failure detection resources corresponding to at least one configured sidelink bandwidth portion. Although only one transmitter 210 and one receiver 212 are illustrated, the remote unit 102 may have any suitable number of transmitters 210 and receivers 212. The transmitter 210 and receiver 212 may be any suitable type of transmitter and receiver. In one embodiment, the transmitter 210 and receiver 212 may be part of a transceiver.

[0052] Figure 3 One embodiment of an apparatus 300 that may be used to transmit information is depicted. The apparatus 300 includes one embodiment of the network unit 104. In addition, the network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. It is understood that the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 may be substantially similar to the processor 202, the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212 of the remote unit 102, respectively.

[0053] In various embodiments, the transmitter 310 can transmit information. Although only one transmitter 310 and one receiver 312 are illustrated, the network unit 104 can have any suitable number of transmitters 310 and receivers 312. The transmitter 310 and receiver 312 can be any suitable type of transmitter and receiver. In one embodiment, the transmitter 310 and receiver 312 can be part of a transceiver.

[0054] In certain configurations, links and / or beam-pair links used for sidelink non-beamformed and / or beamformed transmissions of unicast data may experience radio link or beam failures due to congestion or mobility.

[0055] Figure 4 4 is a schematic diagram 400 illustrating one embodiment of a sidelink unicast link blocking. Schematic diagram 400 is illustrated over a time period 402 including a first time 404, a second time 406, and a third time 408. At the first time 404, a first vehicle 410 and a second vehicle 412 communicate with each other, while a third vehicle 414 begins to move toward the space between the first vehicle 410 and the second vehicle 412 without interfering with the communication between the first vehicle 410 and the second vehicle 412. At the second time 406, the third vehicle 414 causes complete interference (e.g., beam blocking) of the communication between the first vehicle 410 and the second vehicle 412, thereby interrupting the unicast transmission. At the third time 408, the third vehicle 414 causes partial interference with the communication between the first vehicle 410 and the second vehicle 412.

[0056] Understandably, Figure 4 In the illustrated embodiment, the vehicle may be synchronized with GPS and / or GNSS, the vehicle may be synchronized with LTE SLSS or NR FR1 SLSS, and / or the vehicle may be synchronized with NR FR2 SLSS only.

[0057] In certain configurations, the UE monitors the downlink radio link quality by indicating a synchronization indication and / or an out-of-sync indication to a higher layer for a configured (e.g., active) BWP. In this configuration, if the DL BWP is the initial BWP of the UE, or if the UE is configured with a resource index set, which is an SSB or CSI-RS index, the UE performs radio link monitoring using SS / PBCH blocks by a corresponding higher layer parameter set (e.g., RadioLinkMonitoringRS) for radio link monitoring by a higher layer parameter (e.g., failureDetectionResources).

[0058] In some embodiments, if a beam failure is detected on the serving SSB / CSI-RS, the MAC entity may be configured by the RRC with a beam failure recovery procedure for indicating a new SSB or CSI-RS to the serving gNB.

[0059] Figure 5 5 is a schematic diagram 500 illustrating one embodiment of a downlink beam loss. Schematic diagram 500 includes a network 502 and a vehicle 504 experiencing a downlink beam loss.

[0060] Figure 6 6 is a schematic diagram illustrating one embodiment of uplink beam loss. Schematic diagram 600 includes a network 502 and a vehicle 504 in which there is an uplink beam loss.

[0061] In some embodiments, if Figure 4 If the uplink and downlink beams of the primary cell are lost as shown, the beam failure indication can be received by the MAC layer and compared with the configured maximum value.

[0062] In various embodiments, there may be at least the following two SL resource allocation modes: Mode 1: BS schedules SL resources to be used by UE for SL transmission; Mode 2: UE determines (e.g., BS does not schedule) SL transmission resources within SL resources configured by BS and / or network or there are pre-configured SL resources. The definition of SL resource allocation mode 2 may cover: a) UE autonomously selects SL resources for transmission; b) UE assists other UEs in selecting SL resources; c) UE is configured with a grant of NR configuration for SL transmission (similar to type-1); and / or d) UE schedules SL transmission of other UEs.

[0063] In some embodiments, the sidelink radio link monitoring process includes configuring SL-radiolinkmonitoringRS and SL-failureDetectionRS for unicast data transmission between the TX UE and the RX UE. The configuration may be provided as part of the AS level information exchange between the TX UE and the RX UE via the NR PC5 RRC message exchange. If the TX UE is a synchronization reference UE, the SSB transmission may be used for RLM measurements.

[0064] Figure 7 700 is a communication diagram illustrating an embodiment of a sidelink communication 700 between a first UE 702 (e.g., TX UE, car A) and a second UE 704 (e.g., RX UE, car B). It will be appreciated that the communications as part of the sidelink communication 700 may each include one or more messages. The sidelink communication 700 includes a first communication 706 sent from the first UE 702 to the second UE 704, wherein the first UE 702 sends information for NR PC5RRC configuration (e.g., SL-radiolinkmonitoringRS, SL-failureDetectionRS, SL-BeamFailureRecoveryConfig) to the second UE 704.

[0065] In some embodiments, the sidelink radio link and / or beam restoration process for unicast data links may be used for V2V communications within the access layer. As used herein, the sidelink radio link and / or beam restoration process for unicast transmissions may consider both FR1 and FR2. It will be appreciated that the various embodiments described herein may be applicable to link management for multicast transmissions.

[0066] In various embodiments, a single sidelink beam failure recovery may be triggered if one or more active BWPs belonging to the same or different carriers experience a beam failure. The sidelink beam failure recovery may include sending a message indicating a BWP ID corresponding to the beam failure of one or more active BWPs.

[0067] In some embodiments, if the UE maintains one or more unicast or multicast AS-level links with one or more UEs in its vicinity, one or more beam failure recovery messages may be triggered by the UE. The one or more beam failure recovery messages may contain destination IDs, BWP IDs, candidate beam lists, and / or other parameters for different unicast and / or multicast links. It is understood that the embodiments described herein for sidelink beam failures may also be applied to sidelink radio link failures.

[0068] In a first embodiment, there may be a UE SL MAC process enhancement for a sidelink link recovery message (e.g., which also includes SL-Beam failure recovery) to recover a sidelink unicast link or beam. In such an embodiment, the SL-BeamFailureRecoveryConfig for SL unicast data transmission may include possible candidate SL beam configuration information, such as CSI-RS scheduling information, source and / or destination IDs, BWP IDs, panel IDs, and / or various ways of sending a sidelink link recovery message.

[0069] Figure 8 800 is a communication diagram illustrating another embodiment of a side chain communication 800. It can be appreciated that the communications as part of the side chain communication 800 can each include one or more messages. The side chain communication 800 is illustrated between a first UE 802 (e.g., a TX UE) and a second UE 804 (e.g., a RX UE).

[0070] In a first communication 806 sent between a first UE 802 and a second UE 804 , a unicast data transmission is performed between the first UE 802 and the second UE 804 .

[0071] In a second communication 808 sent from the second UE 804 to the first UE 802, the second UE 804 sends a sidelink L1 indication for reporting link loss or beam loss to the first UE 802. The sidelink L1 indication may be similar to an SR and / or RACH transmission, or it may be a PSCCH or PSFCH based transmission. In addition, the sidelink L1 indication may be a multicast or broadcast message such that it includes the UE ID and a notification message notifying other UEs of the failure. In some embodiments, such as for embodiments within coverage, the first UE 802 or the second UE 804 may request resources from the eNB / gNB for sending a SL L1 indication of radio link loss or beam failure message, while for embodiments outside of coverage, the resources may be pre-configured or provided by the scheduling UE. As used herein, within coverage may mean that the sidelink UE is within the coverage of the gNB and / or eNB, which may mean that it receives a signal or message from the gNB and / or eNB. Furthermore, as used herein, out-of-coverage may mean that the sidechain UE is out of the coverage of the gNB and / or eNB, which may mean that it does not receive any signal or message from the gNB and / or eNB.

[0072] After the first UE 802 detects a radio link or beam link failure message from the second UE 804, in a third communication 810 sent from the first UE 802 to the second UE 804, the first UE 802 sends a SL recovery message (e.g., an SLBFR message). The SL recovery message may include a candidate beam information list in L1, L2, and / or L3 signaling, the candidate beam information list containing information about a UE ID (e.g., source and destination ID) or a unicast link ID that uniquely identifies a source-destination ID pair, a SL BWP, and / or CSI RS scheduling information (e.g., time slot, period, etc.). The SL BFR message may be a multicast or broadcast transmission sent over the same sidelink carrier on which the radio link was lost or any other configured active sidelink carrier with better coverage, wherein, in one example, the sidelink recovery message for sidelink FR2 (e.g., mmWave frequency) may be sent using a low frequency such as NR FR1, and in another example, may be sent using another sidelink RAT such as LTE SL.

[0073] The third communication 810 may be sent using L1, L2, and / or L3 signaling using one or more of the following: in one example, PSCCH may be used to send a sidelink recovery message in a multicast transmission using a lower frequency such as FR1 or another RAT such as LTE SL; in a second example, a discovery message may be initiated to send the sidelink recovery message, where the discovery message may be sent via L1 or higher layer signaling. In a third example, SL MAC CE may be used to send a sidelink recovery message in a multicast transmission using a lower frequency such as FR1 or another RAT such as LTE SL; in a fourth example, PDCP control information may be used to send a sidelink recovery message and may be sent using a different low frequency carrier or a different SL RAT; in a fifth example, a sidelink recovery message for FR2 may be sent using the same FR2 carrier; in a sixth example, a group or broadcast transmission includes partial or full beam scanning utilizing different distributed antenna panels; and / or in another example, a combination of one or more of the above examples may be used to send a SL recovery message.

[0074] In some embodiments, if there is a beamforming transmission (e.g., NR FR2 is enabled), a link recovery and / or beam recovery request containing candidate beam information is sent via a SL MAC CE, PSCCH, and / or a discovery message in a multicast or broadcast transmission and with repeated partial or full beam scans. In some embodiments, a partial or full beam scan configuration may include a time slot and / or repetition period for the SL link recovery message. The beam recovery request message may be pre-configured as part of the SL-BeamFailureRecoveryConfig.

[0075] For embodiments within coverage, the first UE 802 or the second UE 804 may request resources from the eNB / gNB for sending an SL beam failure request message, while for embodiments outside coverage, the resources may be pre-configured, autonomously selected by the UE, or provided by a scheduling UE.

[0076] Fig. 9 is a communication diagram illustrating another embodiment of side chain communication 900. It can be understood that the communication as part of the side chain communication 900 can each include one or more messages. The illustrated side chain communication 900 is between a first UE 902 (e.g., a TX UE) and a second UE 904 (e.g., a RX UE).

[0077] In a first communication 906 sent between a first UE 902 and a second UE 904 , unicast data transmission is performed between the first UE 902 and the second UE 904 .

[0078] The second UE 904 determines 908 that there is a radio link loss or beam loss.

[0079] In a second communication 910 sent from the second UE 904 to the first UE 902, the second UE 904 initiates transmission of a SL recovery message that is substantially similar to the SL recovery message regarding Figure 8 It can be understood that in other embodiments, the first UE 902 can determine that there is a radio link loss or a beam loss, and the first UE 902 can send a SL recovery message to the second UE 904.

[0080] Understandably, Figure 8 and Fig. 9 An embodiment is described in which a UE (e.g., car, vehicle) is synchronized with a GNSS or SLSS in another carrier (e.g., LTE SL or NR FR1 SL), and a radio link loss or beam loss occurs in NR FR2.

[0081] Fig.10 An embodiment is illustrated where SLSS is being transmitted or received on the same carrier or BWP as data and if a radio link or beam failure occurs.

[0082] Fig.10 1 is a communication diagram illustrating another embodiment of a side chain communication 1000. It can be understood that the communication as part of the side chain communication 1000 can each include one or more messages. The illustrated side chain communication 1000 is between a first UE 1002 (e.g., a TX UE) and a second UE 1004 (e.g., a RX UE).

[0083] In a first communication 1006 sent between a first UE 1002 and a second UE 1004 , unicast data transmission is performed between the first UE 1002 and the second UE 1004 .

[0084] The second UE 1004 determines 1008 that there is a radio link loss or beam loss.

[0085] In the second communication 1010 sent from the second UE 1004 to the first UE 1002, the second UE 1004 initiates the transmission of SLSS or S-SSB in the same carrier or another carrier that may be configured with a partial beam scanning mode to achieve fast recovery. It is understood that in other embodiments, the first UE 1002 may determine that there is a radio link loss or beam loss, and the first UE 1002 may initiate the transmission of SLSS or S-SSB. In another example, the second UE 1004 may also initiate the sidelink recovery message explained in the first embodiment.

[0086] Fig.11 1 is a communication diagram illustrating another embodiment of a side chain communication 1100. It can be understood that the communication as part of the side chain communication 1100 can each include one or more messages. The illustrated side chain communication 1100 is between a first UE 1102 (e.g., a TX UE) and a second UE 1104 (e.g., a RX UE).

[0087] In a first communication 1106 sent between the first UE 1102 and the second UE 1104, unicast data transmission is performed between the first UE 1102 and the second UE 1104.

[0088] In a second communication 1108 sent from the second UE 1104 to the first UE 1102, the second UE 1104 sends periodic updates of the candidate beam information list based on the received signal strength. It will be appreciated that the periodic exchange of information lists related to services and / or candidate beams for measurements between the first UE 1102 and the second UE 1104 in the PSFCH / PC5 RRC may facilitate the candidate list updates in the SL-beamFailureRecoveryConfig. In one example, as explained in the first embodiment, periodic measurement reports for FR2 (e.g., millimeter wave frequencies) may be sent in the same carrier / BWP where the measurements were performed or in a different carrier / BWP with better coverage such as FR1. The measurement report may include information associating the report with a specific unicast link ID that uniquely identifies the source-destination ID pair, the SL BWP ID, and may be sent in L1, L2, or L3 signaling.

[0089] In certain embodiments, the SL MAC entity may:

[0090] 1> If an SL beam failure instance indication has been received from a lower layer:

[0091] 2> Start or restart SL-beamFailureDetectionTimer;

[0092] 2>SL_BFI_COUNTER increases by 1;

[0093] 2> if BFI_COUNTER>= SL-beamFailureInstanceMaxCount:

[0094] 3> If SL-beamFailureRecoveryConfig is configured for the activated UL BWP:

[0095] 4> Start SL-beamFailureRecoveryTimer, if configured;

[0096] 4> Initiate the SL beam failure recovery procedure on the activated SL BWP by applying the parameters configured in SL-beamFailureRecoveryConfig.

[0097] 3> Otherwise:

[0098] 4> Initiate SL synchronous transmission (partial or full beam scanning configuration)

[0099] 1>If SL-beamFailureDetectionTimer times out; or

[0100] 1> If SL-beamFailureDetectionTimer, SL-beamFailureInstanceMaxCount or any reference signal for beam failure detection is reconfigured by upper layers:

[0101] 2> Set SL_BFI_COUNTER to 0.

[0102] 1> If the SL beam failure recovery process is successfully completed

[0103] 2> Set BFI_COUNTER to 0;

[0104] 2> Stop SL-beamFailureRecoveryTimer, if configured;

[0105] 2> The SL beam failure recovery process is considered to be successfully completed.

[0106] Fig.12is a flow chart illustrating one embodiment of a method 1200 for sidelink fault detection and recovery. In some embodiments, the method 1200 is performed by a device such as the remote unit 102. In certain embodiments, the method 1200 may be performed by a processor executing program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0107] The method 1200 may include receiving 1202 information indicating a sidelink failure detection resource set corresponding to at least one configured sidelink bandwidth portion. In some embodiments, the method 1200 includes determining 1204 a radio link quality of the at least one configured sidelink bandwidth portion based on the sidelink failure detection resource set. In certain embodiments, the method 1200 includes detecting 1206 a sidelink failure based on the radio link quality. In various embodiments, the method 1200 includes initiating 1208 a sidelink failure recovery procedure based on the sidelink failure.

[0108] In some embodiments, the radio link quality indicates a radio link loss, a beam loss, or a combination thereof. In some embodiments, the information indicates a plurality of sidelink fault detection resource sets, each of the plurality of sidelink fault detection resource sets corresponding to a unicast session. In various embodiments, each of the plurality of sidelink fault detection resource sets is used for a corresponding configured sidelink bandwidth portion of the plurality of configured sidelink bandwidth portions.

[0109] In one embodiment, in response to radio link quality being below a predetermined threshold in a predetermined number of instances, a sidelink failure recovery procedure is initiated. In some embodiments, determining radio link quality includes receiving hybrid automatic repeat request feedback. In some embodiments, detecting a sidelink failure based on radio link quality includes detecting a sidelink failure in response to hybrid automatic repeat request feedback including a negative acknowledgement.

[0110] In various embodiments, initiating a sidelink fault recovery procedure includes sending a sidelink fault report. In one embodiment, the sidelink fault report includes information indicating a candidate reference signal for beam measurement, a candidate reference signal for link measurement, a candidate beam identifier, a candidate antenna panel identifier, or some combination thereof. In some embodiments, transmission parameters for sending the sidelink fault report are preconfigured or dynamically signaled.

[0111] In some embodiments, the transmission parameters are preconfigured via radio resource control signaling. In various embodiments, the transmission parameters are sent via layer 1 signaling, layer 2 signaling, or layer 3 signaling. In one embodiment, the transmission parameters indicate a multicast transmission or a broadcast transmission.

[0112] In some embodiments, the multicast transmission or broadcast transmission includes a unicast link identifier that uniquely identifies the source-destination ID pair or the destination identifier. In some embodiments, the multicast transmission or broadcast transmission includes beam scanning using different distributed antenna panels, signaling sent in a carrier frequency or bandwidth portion with better coverage, sidelink transmission, or some combination thereof. In various embodiments, sending the sidelink fault report includes sending the sidelink fault report via a sidelink medium access control control element, a physical sidelink control channel, or a discovery message, where the discovery message transmission can be in L1 or higher layer signaling.

[0113] In one embodiment, initiating a sidelink fault recovery process includes receiving a sidelink fault report. In some embodiments, initiating a sidelink fault recovery process includes sending an indication of a sidelink fault, sending information for sidelink recovery, sending resynchronization information, not sending a reception confirmation, sending a non-confirmation, or some combination thereof. In some embodiments, the information for sidelink recovery includes a candidate beam information list, a candidate reference signal, an antenna panel identifier, a destination identifier, a source identifier, a bandwidth portion identifier, reference signal scheduling information, or some combination thereof.

[0114] In various embodiments, the method 1200 further includes sending candidate beam related information for measurement at predetermined time intervals, wherein the measurement report is sent in the same carrier, the same BWP, a carrier with a larger coverage, or a BWP with a larger coverage. In one embodiment, the sidelink failure detection resource set is used to detect a sidelink radio link failure, a sidelink beam failure, or a combination thereof. In some embodiments, the sidelink failure recovery process includes a sidelink radio link failure recovery process, a sidelink beam failure recovery process, or a combination thereof.

[0115] In one embodiment, a method includes: receiving information indicating a sidelink failure detection resource set corresponding to at least one configured sidelink bandwidth portion; determining a radio link quality of the at least one configured sidelink bandwidth portion based on the sidelink failure detection resource set; detecting a sidelink failure based on the radio link quality; and initiating a sidelink failure recovery process based on the sidelink failure.

[0116] In certain embodiments, the radio link quality indicates radio link loss, beam loss, or a combination thereof.

[0117] In some embodiments, the information indicates a plurality of sidelink failure detection resource sets, each sidelink failure detection resource set of the plurality of sidelink failure detection resource sets corresponding to a unicast session.

[0118] In various embodiments, each set of sidelink failure detection resources in the plurality of sets of sidelink failure detection resources is used for a corresponding configured sidelink bandwidth portion in the plurality of configured sidelink bandwidth portions.

[0119] In one embodiment, in response to the radio link quality being below a predetermined threshold for a predetermined number of instances, a sidelink failure recovery procedure is initiated.

[0120] In some embodiments, determining the radio link quality includes receiving hybrid automatic repeat request feedback.

[0121] In some embodiments, detecting the side chain failure based on the radio link quality comprises detecting the side chain failure in response to hybrid automatic repeat request feedback comprising a negative acknowledgement.

[0122] In various embodiments, initiating a sidelink failure recovery process includes sending a sidelink failure report.

[0123] In one embodiment, the sidelink fault report includes information indicating a candidate reference signal for beam measurement, a candidate reference signal for link measurement, a candidate beam identifier, a candidate antenna panel identifier, or some combination thereof.

[0124] In certain embodiments, transmission parameters for sending sidelink failure reports are preconfigured or dynamically signaled.

[0125] In some embodiments, the transmission parameters are pre-configured via radio resource control signaling.

[0126] In various embodiments, the transmission parameters are sent via layer 1 signaling, layer 2 signaling, or layer 3 signaling.

[0127] In one embodiment, the transmission parameter indicates a multicast transmission or a broadcast transmission.

[0128] In some embodiments, a multicast transmission or a broadcast transmission includes a unicast link identifier that uniquely identifies a source-destination ID pair or a destination identifier.

[0129] In some embodiments, the multicast transmission or broadcast transmission includes beam scanning utilizing different distributed antenna panels, signaling sent in a carrier frequency or bandwidth portion (eg, which improves coverage), sidelink transmissions, or some combination thereof.

[0130] In various embodiments, sending the sidelink fault report includes sending the sidelink fault report via a sidelink medium access control control element, a physical sidelink control channel, or a discovery message.

[0131] In one embodiment, initiating a sidelink failure recovery process includes receiving a sidelink failure report.

[0132] In some embodiments, initiating a sidelink failure recovery process includes sending an indication of a sidelink failure, sending information for sidelink recovery, sending resynchronization information, not sending a receipt confirmation, sending a non-confirmation, or some combination thereof.

[0133] In some embodiments, the information used for sidelink recovery includes a candidate beam information list, a candidate reference signal, an antenna panel identifier, a destination identifier, a source identifier, a bandwidth part identifier, reference signal scheduling information, or some combination thereof.

[0134] In various embodiments, the method further comprises sending candidate beam related information for measurement at predetermined time intervals, wherein the measurement report is sent in the same carrier, the same BWP, a carrier with a larger coverage, or a BWP with a larger coverage.

[0135] In one embodiment, the sidelink failure detection resource set is used to detect a sidelink radio link failure, a sidelink beam failure, or a combination thereof.

[0136] In certain embodiments, the sidelink failure recovery procedure includes a sidelink radio link failure recovery procedure, a sidelink beam failure recovery procedure, or a combination thereof.

[0137] In one embodiment, an apparatus includes: a receiver that receives information indicating a sidelink failure detection resource set corresponding to at least one configured sidelink bandwidth portion; a processor that: determines a radio link quality of at least one configured sidelink bandwidth portion based on the sidelink failure detection resource set; detects a sidelink failure based on the radio link quality; and initiates a sidelink failure recovery process based on the sidelink failure.

[0138] In certain embodiments, the radio link quality indicates radio link loss, beam loss, or a combination thereof.

[0139] In some embodiments, the information indicates a plurality of sidelink failure detection resource sets, each sidelink failure detection resource set of the plurality of sidelink failure detection resource sets corresponding to a unicast session.

[0140] In various embodiments, each sidelink failure detection resource set of the plurality of sidelink failure detection resource sets is used for a corresponding configured sidelink bandwidth portion of the plurality of configured sidelink bandwidth portions.

[0141] In one embodiment, in response to the radio link quality being below a predetermined threshold for a predetermined number of instances, a sidelink failure recovery procedure is initiated.

[0142] In certain embodiments, the processor that determines the radio link quality includes a receiver that receives hybrid automatic repeat request feedback.

[0143] In some embodiments, the processor detecting the side link failure based on the radio link quality comprises the processor detecting the side link failure in response to a hybrid automatic repeat request feedback comprising a negative acknowledgement.

[0144] In various embodiments, the apparatus further includes a transmitter, wherein the processor that initiates the sidelink failure recovery process includes the transmitter that sends the sidelink failure report.

[0145] In one embodiment, the sidelink fault report includes information indicating a candidate reference signal for beam measurement, a candidate reference signal for link measurement, a candidate beam identifier, a candidate antenna panel identifier, or some combination thereof.

[0146] In certain embodiments, transmission parameters for sending sidelink failure reports are preconfigured or dynamically signaled.

[0147] In some embodiments, the transmission parameters are pre-configured via radio resource control signaling.

[0148] In various embodiments, the transmission parameters are sent via layer 1 signaling, layer 2 signaling, or layer 3 signaling.

[0149] In one embodiment, the transmission parameter indicates a multicast transmission or a broadcast transmission.

[0150] In some embodiments, a multicast transmission or a broadcast transmission includes a unicast link identifier or a destination identifier.

[0151] In some embodiments, the multicast transmission or broadcast transmission includes beam scanning using different distributed antenna panels, signaling sent in a carrier frequency or bandwidth portion (e.g., to improve coverage), sidelink transmissions, or some combination thereof.

[0152] In various embodiments, the transmitter that sends the sidelink fault report includes a transmitter that sends the sidelink fault report via a sidelink medium access control control element, a physical sidelink control channel, or a discovery message.

[0153] In one embodiment, the processor that initiates the sidelink failure recovery process includes a receiver that receives a sidelink failure report.

[0154] In some embodiments, the apparatus further comprises a transmitter, wherein the processor initiating the sidelink failure recovery process comprises sending an indication of the sidelink failure, sending information for sidelink recovery, sending resynchronization information, not sending a receipt confirmation, sending a non-confirmation, or some combination thereof.

[0155] In some embodiments, the information used for sidelink recovery includes a candidate beam information list, a candidate reference signal, an antenna panel identifier, a destination identifier, a source identifier, a bandwidth part identifier, reference signal scheduling information, or some combination thereof.

[0156] In various embodiments, the apparatus further includes a transmitter that transmits candidate beam related information for measurement at predetermined time intervals, wherein the measurement report is transmitted in the same carrier, the same BWP, a carrier with greater coverage, or a BWP with greater coverage. Periodic measurement reports for FR2 (e.g., mmWave frequencies) may be transmitted in the same carrier / BWP where the measurement is performed or in a different carrier / BWP such as FR1 that has better coverage. The measurement report may contain information associating the report with a specific unicast link ID that uniquely identifies the source-destination ID pair, the SL BWP ID, and may be transmitted in L1, L2, or L3 signaling.

[0157] In one embodiment, the sidelink failure detection resource set is used to detect a sidelink radio link failure, a sidelink beam failure, or a combination thereof.

[0158] In certain embodiments, the sidelink failure recovery procedure includes a sidelink radio link failure recovery procedure, a sidelink beam failure recovery procedure, or a combination thereof.

[0159] Embodiments may be practiced in other specific forms. The described embodiments should be considered in all respects as illustrative and not restrictive. Therefore, the scope of the present invention is indicated by the appended claims rather than by the foregoing description. All changes that fall within the equivalent meaning and range of the claims should be included within their scope.

Claims

1. A user equipment (UE), comprising: processor; as well as a memory coupled to the processor, the memory comprising instructions executable by the processor to cause the UE to: establishing a PC5-Radio Resource Control (PC5-RRC) connection for unicast communication with the second UE; Sending the unicast communication via the PC5-RRC connection; Detecting a sidechain failure for the PC5-RRC connection; as well as The sidelink failure is declared for the PC5-RRC connection based at least in part on not receiving hybrid automatic repeat request (HARQ) feedback during a feedback opportunity.

2. The UE according to claim 1, wherein: The sidelink failure comprises a radio link failure (RLF) for the PC5-RRC connection.

3. The UE according to claim 1, wherein: The instructions are further executable by the processor to cause the UE to: in response to non-receipt of the HARQ feedback, increment a value of a counter.

4. The UE according to claim 3, wherein: The instructions are further executable by the processor to cause the UE to: compare the value of the counter with a threshold.

5. The UE according to claim 4, wherein: The instructions are further executable by the processor to cause the UE to: in response to the value of the counter satisfying the threshold, declare the sidelink failure.

6. The UE according to claim 3, wherein: The instructions are further executable by the processor to cause the UE to: in response to receiving the HARQ feedback, set the value of the counter to zero.

7. The UE according to claim 1, wherein: The instructions are further executable by the processor to cause the UE to: in response to non-receipt of HARQ feedback for a corresponding PC5-RRC connection among a plurality of PC5-RRC connections including the PC5-RRC connection, increment a corresponding value of a corresponding counter.

8. The UE according to claim 1, wherein: Each PC5-RRC connection of the plurality of PC5-RRC connections corresponds to a separate unicast session including a unicast link identifier (ID), and each PC5-RRC connection uniquely identifies a source-destination ID pair or a destination ID.

9. A method at a first user equipment (UE), the method comprising: establishing a PC5-Radio Resource Control (PC5-RRC) connection for unicast communication with the second UE; Sending the unicast communication via the PC5-RRC connection; Detecting a sidechain failure for the PC5-RRC connection; as well as The sidelink failure is declared for the PC5-RRC connection based at least in part on not receiving hybrid automatic repeat request (HARQ) feedback during a feedback opportunity.

10. The method according to claim 9, wherein: The sidelink failure comprises a radio link failure (RLF) for the PC5-RRC connection.

11. The method according to claim 9, further comprising: In response to non-receipt of the HARQ feedback, a value of a counter is incremented.

12. The method according to claim 11, further comprising: The value of the counter is compared to a threshold value.

13. The method according to claim 12, further comprising: In response to the value of the counter satisfying the threshold, the side chain failure is declared.

14. The method according to claim 11, further comprising: In response to receiving the HARQ feedback, the value of the counter is set to zero.

15. The method according to claim 9, further comprising: In response to non-receipt of HARQ feedback for a corresponding PC5-RRC connection among a plurality of PC5-RRC connections including the PC5-RRC connection, incrementing a corresponding value of a corresponding counter.

16. The method according to claim 9, wherein: Each PC5-RRC connection of the plurality of PC5-RRC connections corresponds to a separate unicast session including a unicast link identifier (ID), and each PC5-RRC connection uniquely identifies a source-destination ID pair or a destination ID.

17. A user equipment (UE), comprising: processor; as well as a memory coupled to the processor, the memory comprising instructions executable by the processor to cause the UE to: establishing a PC5-Radio Resource Control (PC5-RRC) connection for unicast communication with the second UE; receiving the unicast communication via the PC5-RRC connection; Hybrid automatic repeat request (HARQ) feedback is sent during a feedback opportunity, wherein a sidelink failure for the PC5-RRC connection is declared based at least in part on the second UE not receiving the HARQ feedback during the feedback opportunity.

18. The UE according to claim 17, wherein: The sidelink failure comprises a radio link failure (RLF) for the PC5-RRC connection.

19. The UE according to claim 17, wherein: In response to the second UE receiving an indication of non-receipt of the HARQ feedback, a value of a counter is incremented.

20. The UE according to claim 17, wherein: Each PC5-RRC connection of the plurality of PC5-RRC connections corresponds to a separate unicast session including a unicast link identifier (ID), and each PC5-RRC connection uniquely identifies a source-destination ID pair or a destination ID.

Images