Radio link failure determination method and apparatus, and terminal, chip and storage medium

By determining whether RLF occurs in the side link between the first terminal and the second terminal in the multi-carrier system, it is solved that it is impossible to effectively judge RLF in the multi-carrier system. The problem of this achieves accurate link failure judgment.

WO2025030264A1PCT designated stage expired Publication Date: 2025-02-13GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2023/111233
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-08-04
Publication Date
2025-02-13

AI Technical Summary

Technical Problem

In multi-carrier systems, the prior art has not yet effectively determined whether a wireless link failure (RLF) occurs on the side link.

Method used

By determining the side link generation link RLF between the first terminal and the second terminal when all carriers in the first carrier set generate the carrier radio link RLF. The first set of carriers is used for side link transmission between the first terminal and the second terminal.

Benefits of technology

It is realized that the RLF occurs in the side link in a multi-carrier system is accurately determined, and the problem that cannot be effectively judged in the prior art is solved.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2023111233_13022025_PF_FP_ABST
    Figure CN2023111233_13022025_PF_FP_ABST
Patent Text Reader

Abstract

Provided in the embodiments of the present application is a radio link failure (RLF) determination method, which is applied to a first terminal. The method comprises: when a carrier RLF occurs in all carriers in a first carrier set, determining that a link RLF occurs in a sidelink between a first terminal and a second terminal, wherein the first carrier set is used for sidelink transmission between the first terminal and the second terminal. By means of the method, the problem of how to determine whether an RLF occurs in a sidelink in a multi-carrier system is solved.
Need to check novelty before this filing date? Find Prior Art

Description

Method, device, terminal, chip and storage medium for determining wireless link failure Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and in particular to a method, device, terminal, chip, and storage medium for determining wireless link failure. Background Art

[0002] In existing New Radio (NR) sidelink (SL) systems, a single-carrier-based Radio Link Failure (RLF) mechanism has been designed. In a single-carrier system, if a transmitting terminal fails to receive a Physical Sidelink Feedback Channel (PSFCH) signal from a receiving terminal at the receiving opportunity, and this event occurs a certain number of times, an RLF is triggered.

[0003] However, currently there is no solution that discloses how to determine whether RLF occurs in the sidelink in a multi-carrier system.

[0004] Summary of the Invention

[0005] Embodiments of the present application provide a method, device, terminal, chip, and storage medium for determining wireless link failure.

[0006] In a first aspect, an embodiment of the present application provides a method for determining a radio link failure, which is applied to a first terminal. The method includes: when a carrier radio link failure RLF occurs in all carriers in a first carrier set, determining that a link RLF occurs in a side link between the first terminal and the second terminal; wherein the first carrier set is used for side link transmission between the first terminal and the second terminal.

[0007] In the second aspect, an embodiment of the present application provides a radio link failure determination device, which includes: a first determination unit, used to determine that a side link RLF occurs between the device and a second terminal when a carrier radio link failure RLF occurs on all carriers in a first carrier set; wherein the first carrier set is used for side link transmission between the device and the second terminal.

[0008] In a third aspect, an embodiment of the present application provides a terminal including a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the above-mentioned method for determining radio link failure.

[0009] In a fourth aspect, an embodiment of the present application provides a chip for implementing the above-mentioned method for determining wireless link failure. Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes the above-mentioned method for determining wireless link failure.

[0010] In a fifth aspect, an embodiment of the present application provides a computer-readable storage medium for storing a computer program, which enables a computer to execute the above-mentioned wireless link failure determination method.

[0011] In a sixth aspect, an embodiment of the present application provides a computer program product, comprising computer program instructions, which enable a computer to execute the above-mentioned wireless link failure determination method.

[0012] In a seventh aspect, an embodiment of the present application provides a computer program, which, when running on a computer, enables the computer to execute the above-mentioned wireless link failure determination method.

[0013] The above technical solution solves the problem of how to determine whether RLF occurs in the side link in a multi-carrier system. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0015] FIG1 is a schematic diagram of resource selection corresponding to mode A provided in an embodiment of the present application;

[0016] FIG2 is a schematic diagram of resource selection corresponding to mode B provided in an embodiment of the present application;

[0017] FIG3 is a schematic flow chart of a method for determining a radio link failure according to an embodiment of the present application;

[0018] FIG4 is a schematic diagram of the structure of a device for determining a radio link failure according to an embodiment of the present application;

[0019] FIG5 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0020] FIG6 is a schematic structural diagram of a chip according to an embodiment of the present application. DETAILED DESCRIPTION

[0021] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0022] The technical solutions of the embodiments of the present application can be applied to various side communication systems. To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are explained below. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0023] 1. Device to Device (D2D) / Vehicle to Everything (V2X) in Long Term Evolution (LTE)

[0024] Device-to-device communication is a SL transmission technology based on D2D. Unlike traditional cellular systems, where communication data is received or transmitted via base stations, the IoV system uses direct end-to-end communication, resulting in higher spectrum efficiency and lower transmission latency. The 3rd Generation Partnership Project (3GPP) defines two transmission modes: Mode A and Mode B.

[0025] Mode A: The terminal's transmission resources are allocated by the base station (eNB), and the terminal transmits data on the sidelink based on the allocated resources. The base station can allocate resources for a single transmission or for semi-static transmission. As shown in Figure 1, the terminal's transmission resources are allocated by the base station. The base station allocates resources to the terminal via downlink based on grant signaling (Grant), and the terminal transmits data on the sidelink based on the allocated resources.

[0026] Mode B: The terminal selects a resource in the resource pool for data transmission. As shown in Figure 2, the terminal can select a resource in the resource pool for data transmission.

[0027] In 3GPP, D2D is divided into the following different phases for research:

[0028] 1) Proximity-based Service (ProSe): In Rel-12 / 13, device-to-device communication was studied for ProSe scenarios, primarily targeting public safety services.

[0029] In ProSe, by configuring the position of the resource pool in the time domain, for example, the resource pool is non-continuous in the time domain, the UE can transmit / receive data discontinuously on the sidelink, thereby achieving power saving.

[0030] 2) V2X: In Rel-14 / 15, the vehicle networking system conducted research on vehicle-to-vehicle communication scenarios, mainly targeting relatively high-speed vehicle-to-vehicle and vehicle-to-pedestrian communication services.

[0031] In V2X, since the on-board system has continuous power supply, power efficiency is not the main issue, but the delay of data transmission is the main issue. Therefore, the system design requires the terminal equipment to perform continuous transmission and reception.

[0032] 3) Wearable devices (FeD2D): In Rel-14, this scenario studies the scenario of wearable devices accessing the network through mobile phones, which is mainly aimed at scenarios with low mobile speed and low power access.

[0033] In FeD2D, during the pre-research phase, 3GPP concluded that a base station can configure the discontinuous reception (DRX) parameters of a remote terminal through a relay terminal, but did not provide a conclusion on the specific details of how to perform DRX configuration.

[0034] 2. NR V2X

[0035] Based on LTE V2X, NR V2X is not limited to broadcast scenarios, but has been further expanded to unicast and multicast scenarios, and the application of V2X is studied in these scenarios.

[0036] Similar to LTE V2X, NR V2X also defines two resource authorization modes: mode-1 / 2 (i.e., mode A and mode B mentioned above). In some scenarios, the user may be in a mixed mode, that is, mode-1 (mode A) can be used to acquire resources, and mode-2 (mode B) can be used to acquire resources at the same time. The resource acquisition is indicated by sidelink authorization, that is, the sidelink authorization indicates the time-frequency position of the corresponding physical sidelink control channel (PSCCH) and physical sidelink shared channel (PSSCH) resources.

[0037] Unlike LTE V2X, in addition to the feedback-free, UE-initiated Hybrid Automatic Repeat reQuest (HARQ) retransmission, NR V2X introduces feedback-based HARQ retransmission, which is not limited to unicast communication but also includes multicast communication.

[0038] 3. LTE-V2X Carrier Aggregation (CA)

[0039] Carrier selection in LTE-V2X carrier aggregation is accomplished by the following mechanisms:

[0040] The upper layer configures the mapping between service types and carriers. That is, for a certain service, the upper layer indicates to the access stratum (AS) the available carriers (sets);

[0041] Furthermore, the AS layer configures the set of available carriers for each logical channel and the Channel Busy Ratio (CBR) measurement threshold for each data priority in each resource pool. The UE measures the CBR value in the resource pool and compares it with the CBR threshold corresponding to the priority of the transmitted data. If the measured value is lower than the threshold, the carrier is considered available.

[0042] 4、NR Uu CA

[0043] CA is a bandwidth extension technology supported since the LTE-Advanced standard. This technology can aggregate multiple component carriers (CCs) together and be received or transmitted simultaneously by a UE. According to the range of the aggregated carriers, CA can be divided into intra-band CA (Intra-band CA) and inter-band CA (Inter-band CA). One of the main uses of intra-band CA is for scenarios where the cell carrier bandwidth is greater than the single carrier bandwidth capability of the UE. In this case, the UE can use CA to operate in a "wide carrier". For example, the base station supports a 300MHz carrier, while the UE only supports a maximum of 100MHz carrier. In this case, the UE can use CA to achieve broadband operation greater than 100MHz, where the aggregated carriers can be adjacent carriers or non-adjacent carriers.

[0044] Cross-carrier scheduling:

[0045] Cross-carrier scheduling with a Carrier Indicator Field (CIF) allows the Physical Downlink Control Channel (PDCCH) of one serving cell to schedule resources of a different serving cell, but with the following restrictions:

[0046] 1) The Primary Cell (PCell) cannot use cross-carrier scheduling, that is, the PCell is always scheduled through its own PDCCH;

[0047] 2) If a Secondary Cell (SCell) is configured with a PDCCH, the Physical Downlink Shared Channel (PDSCH) and Physical Uplink Shared Channel (PUSCH) of the cell are always scheduled through the PDCCH of the SCell;

[0048] 3) If a SCell is not configured with a PDCCH, the PDSCH and PUSCH of the SCell are always scheduled through the PDCCH of another serving cell.

[0049] It should be understood that a scheduled PDCCH and the scheduled PDSCH / PUSCH can use the same or different subcarrier spacing (SCS). Prior to R16, cross-carrier scheduling supported the same subcarrier spacing for the scheduled PDCCH and the scheduled PDSCH / PUSCH, but starting from R16, it can support the same or different subcarrier spacing configurations.

[0050] The above briefly explains the relevant technologies / terms involved in the embodiments of this application, which will not be repeated in the following embodiments.

[0051] It should be understood that the terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document is merely a description of the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the objects associated before and after are in an "or" relationship. It should also be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B. It should also be understood that the "correspondence" mentioned in the embodiments of this application can mean that there is a direct or indirect correspondence between the two, or it can mean that there is an association relationship between the two, or it can mean a relationship between indication and indication, configuration and configuration, etc. It should also be understood that the "predefined" or "predefined rules" mentioned in the embodiments of this application can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in devices (for example, including terminal devices and network devices). This application does not limit its specific implementation method.

[0052] It should also be understood that the embodiments of the present application do not limit the specific form of the terminal. As an example, the terminal in the embodiments of the present application may refer to an access terminal, a user equipment (UE), a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or a user device. The access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, an IoT device, a satellite handheld terminal, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network or a terminal device in a future evolution network, etc.

[0053] In the existing NR SL system, a single-carrier-based RLF mechanism is designed. In a single-carrier system, if the transmitting terminal (transmitting end) does not receive the PSFCH sent by the receiving terminal (receiving end) at the PSFCH reception timing, or if the transmitting terminal does not receive the HARQ feedback information sent by the receiving terminal, and this event occurs a certain number of times, an RLF is triggered.

[0054] For example, HARQ feedback information is carried in the PSFCH reception opportunity associated with the PSSCH. In one possible scenario, if the transmitting terminal does not receive the PSFCH at the PSFCH reception opportunity, the value of numConsecutiveDTX is increased by 1. When the value of numConsecutiveDTX reaches sl-maxNumConsecutiveDTX, an RLF is triggered. In another possible scenario, if the transmitting terminal receives the PSFCH at the PSFCH reception opportunity, the value of numConsecutiveDTX is reinitialized to 0.

[0055] However, there is currently no solution to determine whether RLF occurs in the sidelink in a multi-carrier system.

[0056] In view of this, the present application provides a method, apparatus, terminal, chip, and storage medium for determining a radio link failure. The method can be performed, for example, by a terminal (such as a first terminal), or can be performed by a chip, chip system, or circuit configured in the terminal, and the embodiments of the present application are not limited to this. For ease of description, the following description is based on an example of the method being performed by the first terminal.

[0057] In this method, if all carriers in a first carrier set experience carrier RLF, it can be determined that a sidelink RLF has occurred between the first terminal and the second terminal. The first carrier set is used for sidelink transmission between the first terminal and the second terminal. This method solves the problem of determining whether a sidelink RLF has occurred in a multi-carrier system.

[0058] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and all of them fall within the scope of protection of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0059] FIG3 is a flow chart of a method for determining a radio link failure according to an embodiment of the present application. As shown in FIG3 , the method for determining a radio link failure may include the following steps:

[0060] S301, when all carriers in a first carrier set have carrier RLF, the first terminal determines that a sidelink between the first terminal and the second terminal has link RLF; wherein the first carrier set is used for sidelink transmission between the first terminal and the second terminal.

[0061] As an example, the first carrier set may be configured / defined in any one of the following ways 1 to 4:

[0062] Method 1: Pre-configuration or network configuration.

[0063] In this approach, the first carrier set may be pre-configured or network-configured. The network configuration method may include, for example, configuration via system messages or proprietary signaling. For example, when configuring the first carrier set, the network may configure an appropriate carrier set (i.e., the first carrier set) for sidelink transmission between the first terminal and the second terminal based on, for example, traffic volume.

[0064] Method 2: Configuration is performed by the first terminal or the second terminal.

[0065] In this manner, the first carrier set may be configured by the first terminal or the second terminal.

[0066] As an implementation, the first carrier set is configured by the first terminal. In this case, the first terminal may send fourth indication information to the second terminal, where the fourth indication information is used to indicate the first carrier set. In other words, after configuring the first carrier set, the first terminal may notify / configure the first carrier set to the second terminal. Therefore, the first carrier set can also be understood as the carrier set configured by the first terminal for the other terminal (the second terminal).

[0067] As another implementation, the first carrier set is configured by the second terminal. In this case, the second terminal may send fifth indication information to the first terminal, where the fifth indication information is used to indicate the first carrier set. In other words, after configuring the first carrier set, the second terminal may notify / configure the first carrier set to the first terminal. Therefore, the first carrier set can also be understood as the carrier set configured by the other terminal (the second terminal) for the first terminal.

[0068] Taking the example of a first terminal configuring a first carrier set, during configuration of the first carrier set, the first terminal may, for example, determine the first carrier set based on the capabilities of the second terminal. For example, assuming the second terminal only supports simultaneous reception of data on two carriers, the first terminal may define two carriers in the multi-carrier system as carriers in the first carrier set.

[0069] Mode 3: The first carrier set is a carrier set determined by the first terminal for data transmission. That is, the first carrier set may be a carrier set selected by the first terminal for data transmission.

[0070] Mode 4: The first carrier set is a carrier set corresponding to a time-frequency resource (resource grant) used by the first terminal to send data.

[0071] Among them, the carrier set corresponding to the time-frequency resources used by the first terminal to send data can also be understood as the carrier set corresponding to the time-frequency resources actually used when the first terminal sends data to the second terminal, or it can also be understood as the carrier set corresponding to the time-frequency resources used by the first terminal for data sending.

[0072] It should be noted that the first carrier set in the embodiment of the present application can also be understood as a "carrier set that requires attention". Since in a multi-carrier system, link RLF cannot be triggered based on the occurrence of carrier RLF on one of the carriers, for a multi-carrier system, the embodiment of the present application configures / defines a carrier set that requires attention (a first carrier set), and determines whether a sidelink link RLF occurs (or triggers link RLF) when all carriers in the carrier set that requires attention occur carrier RLF. In this way, it is clarified which carriers in the multi-carrier system are the carriers that require attention when triggering link RLF, thereby solving the problem of how to determine whether a sidelink RLF occurs in a multi-carrier system.

[0073] In some embodiments, the occurrence of carrier RLF on any carrier in the first carrier set is determined based on the value of the counter (numConsecutiveDTX) corresponding to the carrier reaching a first threshold (sl-maxNumConsecutiveDTX). For the first terminal, if no PSFCH is received on the carrier at the PSFCH reception timing, the value of the counter corresponding to the carrier is increased by 1. Correspondingly, for the first terminal, if a PSFCH is received on the carrier at the PSFCH reception timing, the value of the counter corresponding to the carrier is initialized to 0.

[0074] For example, assuming that the first carrier set includes carrier #1, if the first terminal does not receive a PSFCH on carrier #1 during a PSFCH reception opportunity, the value of the counter corresponding to carrier #1 may be increased by 1. When the value of the counter corresponding to carrier #1 reaches a first threshold, it may be determined that carrier RLF has occurred on carrier #1. The first threshold may be pre-configured or network-configured, for example. Accordingly, if the first terminal receives a PSFCH on carrier #1 during a PSFCH reception opportunity, the value of the counter corresponding to carrier #1 may be initialized to 0.

[0075] It should be understood that the “carrier RLF occurs on a certain carrier” mentioned in the embodiments of the present application can also be understood as the carrier triggering the carrier RLF, or can also be understood as the carrier triggering the carrier RLF state.

[0076] Exemplarily, after determining the first carrier set, it may be determined that a link RLF occurs in the sidelink between the first terminal and the second terminal through the following scheme 1 or scheme 2.

[0077] Option 1:

[0078] In solution 1, when all carriers in the first carrier set experience carrier RLF, the Media Access Control (MAC) layer of the first terminal may send first indication information to the Radio Resource Control (RRC) layer, where the first indication information is used to indicate that all carriers in the first carrier set have experienced carrier RLF. In other words, when all carriers in the first carrier set experience carrier RLF, the first terminal may trigger the MAC layer to send an RLF report to the RRC layer to report that all carriers in the first carrier set have experienced carrier RLF.

[0079] Here, all carriers in the first carrier set experience carrier RLF, or it can also be understood that all carriers in the first carrier set are in a carrier RLF state.

[0080] That is to say, when carrier RLF occurs in a carrier in the first carrier set, the MAC layer of the first terminal may not need to send the first indication information to the RRC layer. However, when carrier RLF occurs in all carriers in the first carrier set, for example, when all carriers in the first carrier set are in the carrier RLF state, the MAC layer of the first terminal may send the first indication information to the RRC layer to indicate that carrier RLF occurs in all carriers in the current first carrier set.

[0081] As an implementation, the situation where all carriers in the first carrier set experience carrier RLF may include: when one of the carriers in the first carrier set experiences carrier RLF, the other carriers are all in a state where carrier RLF has occurred. That is, when one of the carriers in the first carrier set experiences carrier RLF, if the other carriers in the first carrier set are all in a state where carrier RLF has occurred, it can be considered that all carriers in the first carrier set have experienced carrier RLF, and the MAC layer of the first terminal can then send first indication information to the RRC layer.

[0082] For example, assuming that the first carrier set includes the first carrier, then when the value of the counter corresponding to the first carrier reaches the first threshold, if the values ​​of the counters corresponding to other carriers in the first carrier set do not reach the first threshold, there is no need to send the first indication information to the RRC layer (that is, do not trigger the RLF report to the RRC layer); otherwise, the first indication information is sent to the RRC layer (that is, trigger the RLF report to the RRC layer).

[0083] In scheme one, when carrier RLF occurs in all carriers in the first carrier set, determining that link RLF occurs in the side link between the first terminal and the second terminal may include: when the RRC layer receives first indication information, determining that link RLF occurs in the side link between the first terminal and the second terminal.

[0084] It can be understood that when the RRC layer receives the first indication information, it can indicate that carrier RLF has occurred in all carriers in the first carrier set. Therefore, in this case, it can be determined that link RLF has occurred in the sidelink between the first terminal and the second terminal.

[0085] Option 2:

[0086] In solution 2, for any carrier in the first carrier set, if carrier RLF occurs on that carrier, the MAC layer of the first terminal may send second indication information corresponding to the carrier to the RRC layer, where the second indication information is used to indicate that carrier RLF has occurred on that carrier. In other words, for any carrier in the first carrier set, if carrier RLF occurs on that carrier, the first terminal may trigger an RLF report from the MAC layer to the RRC layer to report the occurrence of carrier RLF on that carrier.

[0087] That is, when a carrier RLF occurs in a carrier in the first carrier set, the MAC layer of the first terminal may send second indication information corresponding to the carrier to the RRC layer to indicate that the carrier RLF currently occurs in the carrier.

[0088] For example, assuming that the first carrier set includes the first carrier, when the value of the counter corresponding to the first carrier reaches the first threshold, the MAC layer of the first terminal can send the second indication information corresponding to the carrier to the RRC layer (that is, triggering an RLF report to the RRC layer).

[0089] In scheme two, when carrier RLF occurs in all carriers in the first carrier set, determining that link RLF occurs in the side link between the first terminal and the second terminal may include: when the RRC layer receives second indication information corresponding to each carrier in the first carrier set, determining that link RLF occurs in the side link between the first terminal and the second terminal.

[0090] It can be understood that when the RRC layer receives the second indication information corresponding to each carrier in the first carrier set, it can indicate that carrier RLF has occurred in each carrier in the first carrier set. Therefore, in this case, it can be determined that link RLF has occurred in the side link between the first terminal and the second terminal.

[0091] It should be noted that the time when the carrier RLF occurs for each carrier in the first carrier set may be the same or different, and therefore, the time when the RRC layer receives the second indication information corresponding to each carrier may also be the same or different.

[0092] In some embodiments, when the RRC layer receives second indication information corresponding to each carrier in the first carrier set, determining that a link RLF occurs in the side link between the first terminal and the second terminal may include: when the RRC layer receives second indication information corresponding to each carrier in the first carrier set and the carrier RLF status of each carrier has not been released, determining that a link RLF occurs in the side link between the first terminal and the second terminal.

[0093] Considering that after a carrier RLF occurs (or after the carrier RLF state is triggered), it may return to normal (or the carrier RLF state is released) within a certain period of time. Therefore, after the RRC layer receives the second indication information corresponding to each carrier in the first carrier set, it is also necessary to meet the condition that the carrier RLF state of each carrier has not been released before it can determine that the sidelink between the first terminal and the second terminal has a link RLF.

[0094] As an implementation method, when carrier RLF occurs in all carriers in the first carrier set, determining that link RLF occurs in the side link between the first terminal and the second terminal may include: when the RRC layer receives second indication information corresponding to the first carrier in the first carrier set and the carrier RLF status of other carriers has been triggered and not released, determining that link RLF occurs in the side link between the first terminal and the second terminal.

[0095] It is understandable that when the RRC layer receives the second indication information corresponding to the first carrier in the first carrier set, it may indicate that carrier RLF has occurred on the first carrier, or that the carrier RLF state has been triggered on the first carrier. In this case, if the carrier RLF state of other carriers in the first carrier set has also been triggered, it may indicate that carrier RLF has occurred on all carriers in the first carrier set. Therefore, in this case, it can be determined that link RLF has occurred in the sidelink between the first terminal and the second terminal.

[0096] In some embodiments, the method may further include: for any carrier in the first carrier set, when the carrier meets the first condition, the MAC layer of the first terminal sends third indication information corresponding to the carrier to the RRC layer, and the third indication information is used to indicate that the carrier RLF state of the carrier is released.

[0097] In an embodiment of the present application, the carrier RLF state of a certain carrier is released, which can also be understood as the first terminal triggering the MAC layer to report the RLF release to the RRC layer, or it can also be understood as canceling the RLF report previously reported to the RRC layer, that is, canceling the content indicated by the second indication information corresponding to the carrier.

[0098] For example, the first condition may include the following condition A and / or condition B:

[0099] Condition A: PSFCH is received on the carrier at the PSFCH reception timing.

[0100] It can be understood that if the first terminal receives the PSFCH from the second terminal on a certain carrier at the PSFCH reception timing, it may indicate that the communication status on the carrier is normal. Therefore, in this case, the MAC layer of the first terminal may send the third indication information corresponding to the carrier to the RRC layer.

[0101] For example, if the first terminal receives a PSFCH from the second terminal on the first carrier in the first carrier set at the PSFCH reception timing (satisfying condition A), it indicates that the communication status on the first carrier is normal. Therefore, the MAC layer of the first terminal can send the third indication information corresponding to the first carrier to the RRC layer. The third indication information corresponding to the first carrier can be sent, for example, after carrier RLF occurs on the first carrier.

[0102] Condition B: The timer corresponding to the carrier times out.

[0103] Among them, the timer corresponding to the carrier can be started, for example, when carrier RLF occurs in the carrier, or when the MAC layer of the first terminal sends the second indication information corresponding to the carrier to the RRC layer, or when the RRC layer of the first terminal receives the second indication information corresponding to the carrier.

[0104] The timing duration of the timer corresponding to the carrier may be, for example, pre-configured or network-configured. The timing duration may be a configured fixed value or a dynamically configured value, which is not limited in the present embodiment.

[0105] It can be understood that if the timer corresponding to a carrier in the first carrier set times out, it means that the carrier may have recovered to normal from the carrier RLF state. Therefore, in this case, the MAC layer of the first terminal can send the third indication information corresponding to the carrier to the RRC layer.

[0106] For example, if the timer corresponding to the first carrier in the first carrier set times out (satisfying condition B), it means that the first carrier may have recovered from the carrier RLF state. Therefore, the MAC layer of the first terminal can send the third indication information corresponding to the first carrier to the RRC layer.

[0107] In some embodiments, for any carrier in the first carrier set, the third indication information corresponding to the carrier may be sent by the MAC layer of the first terminal to the RRC layer, for example, after the carrier RLF occurs in the carrier (that is, after the MAC layer of the first terminal sends the second indication information corresponding to the carrier to the RRC), and when the carrier meets the above-mentioned first condition. For example, after the first carrier in the first carrier set occurs in the carrier RLF, if the first carrier can meet the above-mentioned first condition at a certain moment, then in this case, the MAC layer of the first terminal may send the third indication information corresponding to the first carrier to the RRC layer. In this way, the RRC layer can know that the first carrier has recovered from the carrier RLF state by receiving the third indication information corresponding to the first carrier.

[0108] For ease of understanding, the above-mentioned solution 2 is illustrated below through two examples.

[0109] Example 1:

[0110] Assuming that the first carrier set includes the first carrier, when the value of the counter corresponding to the first carrier reaches the above-mentioned first threshold, the MAC layer of the first terminal may send second indication information corresponding to the first carrier to the RRC layer (or, may trigger an RLF report to the RRC layer) to indicate that the carrier RLF of the first carrier occurs; accordingly, when the counter corresponding to the first carrier is reset to 0 (for example, at the reception timing of the PSFCH, the PSFCH is received on the first carrier, so that the value of the counter corresponding to the first carrier is initialized to 0), the MAC layer of the first terminal may send third indication information corresponding to the first carrier to the RRC layer (or, may trigger an RLF release report to the RRC layer) to indicate that the carrier RLF state of the first carrier is released.

[0111] In some scenarios, the event that the counter corresponding to the first carrier is reset to 0 may occur after the counter corresponding to the first carrier reaches the first threshold. Therefore, the event that the MAC layer of the first terminal sends the third indication information corresponding to the first carrier to the RRC layer may occur after carrier RLF occurs on the first carrier.

[0112] In Example 1, when the RRC layer receives the second indication information corresponding to the first carrier, or in other words, when it receives the RLF report from the first carrier, if other carriers in the first carrier set also report RLF and the RLF report is not canceled (or in other words, the RLF release report is not triggered), it can be determined that a link RLF has occurred in the side link between the first terminal and the second terminal, that is, the RLF of the side link is triggered.

[0113] Example 2:

[0114] Assuming that the first carrier set includes the first carrier, when the value of the counter corresponding to the first carrier reaches the above-mentioned first threshold, the MAC layer of the first terminal may send the second indication information corresponding to the first carrier to the RRC layer (or, may trigger an RLF report to the RRC layer) to indicate that the first carrier has a carrier RLF.

[0115] When the RRC layer receives the second indication information corresponding to the first carrier, or in other words, receives the RLF report from the first carrier, it may start a timer corresponding to the first carrier. When the timer corresponding to the first carrier times out, it triggers the MAC layer to send third indication information corresponding to the first carrier to the RRC layer (or in other words, triggers an RLF release report to the RRC layer) to indicate that the carrier RLF state of the first carrier has been released.

[0116] In Example 2, when the RRC layer receives an RLF report from the first carrier, if other carriers in the first carrier set also report RLF, and the RLF report is not canceled (or, the RLF release report is not triggered), it can be determined that a link RLF has occurred in the sidelink between the first terminal and the second terminal, that is, the RLF of the sidelink is triggered.

[0117] According to the method of an embodiment of the present application, if carrier RLF occurs in all carriers in the first carrier set, the first terminal can determine that link RLF occurs in the side link between the first terminal and the second terminal, thereby clarifying the problem of how to determine whether RLF occurs in the side link in a multi-carrier system.

[0118] The preferred embodiments of the present application are described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above embodiments. Within the technical concept of the present application, the technical solution of the present application can be subjected to a variety of simple modifications, and these simple modifications all fall within the scope of protection of the present application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present application will no longer describe the various possible combinations separately. For another example, the various different embodiments of the present application can also be arbitrarily combined, as long as they do not violate the idea of ​​the present application, they should also be regarded as the contents disclosed in the present application. For another example, under the premise of no conflict, the various embodiments and / or the technical features in each embodiment described in the present application can be arbitrarily combined with the prior art, and the technical solution obtained after the combination should also fall within the scope of protection of the present application.

[0119] It should also be understood that in the various method embodiments of the present application, the sequence numbers of the above-mentioned processes do not imply a precedence in the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. In addition, in the embodiments of the present application, the terms "downlink," "uplink," and "sidelink" are used to indicate the transmission direction of signals or data, where "downlink" is used to indicate the first direction of transmission of signals or data from a site to a user equipment in a cell, "uplink" is used to indicate the second direction of transmission of signals or data from a user equipment in a cell to a site, and "sidelink" is used to indicate the third direction of transmission of signals or data from user equipment 1 to user equipment 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. In addition, in the embodiments of the present application, the term "and / or" is merely a description of the association relationship between associated objects, indicating that three relationships can exist. Specifically, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.

[0120] Based on the aforementioned embodiments, embodiments of the present application provide corresponding wireless link failure determination devices.

[0121] FIG4 is a schematic diagram of the structure of a radio link failure determination device provided in an embodiment of the present application, which is applied to a first terminal. As shown in FIG4 , the radio link failure determination device 400 includes:

[0122] The first determination unit 401 is used to determine whether a side link RLF occurs in the side link between the device 400 and the second terminal when a carrier radio link failure RLF occurs in all carriers in the first carrier set; wherein the first carrier set is used for side link transmission between the device 400 and the second terminal.

[0123] In some embodiments, the device 400 also includes: a first sending unit, which is used to, when all carriers in the first carrier set have carrier RLF, the media access control MAC layer of the device 400 sends first indication information to the radio resource control RRC layer, and the first indication information is used to indicate that all carriers in the first carrier set have carrier RLF.

[0124] In some embodiments, the first determining unit 401 is specifically configured to: determine that a link RLF occurs in the sidelink between the device 400 and the second terminal when the RRC layer receives the first indication information.

[0125] In some embodiments, the device 400 also includes: a second sending unit, which is used to send second indication information corresponding to any carrier in the first carrier set to the RRC layer of the MAC layer of the device 400 when carrier RLF occurs on the carrier, and the second indication information is used to indicate that carrier RLF occurs on the carrier.

[0126] In some embodiments, the first determining unit 401 is specifically configured to: determine that a link RLF occurs in the sidelink between the device 400 and the second terminal when the RRC layer receives second indication information corresponding to each carrier in the first carrier set.

[0127] In some embodiments, the first determination unit 401 is specifically used to: when the RRC layer receives second indication information corresponding to each carrier in the first carrier set and the carrier RLF status of each carrier has not been released, determine that a link RLF occurs in the side link between the device 400 and the second terminal.

[0128] In some embodiments, the first determination unit 401 is specifically used to: determine that a link RLF occurs in the side link between the first terminal and the second terminal when the RRC layer receives second indication information corresponding to the first carrier in the first carrier set and the carrier RLF status of other carriers has been triggered and not released.

[0129] In some embodiments, the device 400 also includes: a third sending unit, which is used to send third indication information corresponding to any carrier in the first carrier set to the RRC layer of the MAC layer of the device 400 when the carrier meets the first condition, and the third indication information is used to indicate that the carrier RLF state of the carrier is released.

[0130] In some embodiments, the third indication information corresponding to a carrier is sent by the MAC layer of the apparatus 400 to the RRC layer after a carrier RLF occurs on the carrier.

[0131] In some embodiments, the first condition includes: receiving the PSFCH on the carrier at the reception timing of the physical side feedback channel PSFCH; and / or the timer corresponding to the carrier times out; wherein the timer corresponding to the carrier is started when carrier RLF occurs on the carrier.

[0132] In some embodiments, the timing duration of the timer is pre-configured or network configured.

[0133] In some embodiments, the occurrence of carrier RLF in any carrier in the first carrier set is determined based on the value of the counter corresponding to the carrier reaching a first threshold; wherein, if PSFCH is not received on the carrier at the PSFCH reception timing, the value of the counter corresponding to the carrier increases by 1.

[0134] In some embodiments, the apparatus 400 further includes: a second determining unit, configured to determine that a carrier RLF occurs in the carrier when the value of the counter corresponding to the carrier reaches a first threshold.

[0135] In some embodiments, the first threshold is pre-configured or network configured.

[0136] In some embodiments, if a PSFCH is received on a carrier at a PSFCH reception opportunity, the value of a counter corresponding to the carrier is initialized to 0.

[0137] In some embodiments, the first carrier set is pre-configured or network configured; or, the first carrier set is configured by the device 400 or the second terminal; or, the first carrier set is a carrier set determined by the device 400 for data transmission; or, the first carrier set is a carrier set corresponding to the time-frequency resources used by the device 400 when sending data.

[0138] In some embodiments, the apparatus 400 further includes: a fourth sending unit, configured to send fourth indication information to the second terminal when the first carrier set is configured by the apparatus 400, where the fourth indication information is used to indicate the first carrier set.

[0139] Those skilled in the art should understand that the relevant description of the above-mentioned radio link failure determination device in the embodiment of the present application can be understood with reference to the relevant description of the radio link failure determination method in the embodiment of the present application.

[0140] Figure 5 is a schematic structural diagram of a communication device 500 provided in an embodiment of the present application. The communication device 500 shown in Figure 5 includes a processor 510, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0141] Optionally, as shown in Figure 5, the communication device 500 may further include a memory 520. The processor 510 may call and execute a computer program from the memory 520 to implement the method in the embodiment of the present application.

[0142] The memory 520 may be a separate device independent of the processor 510 , or may be integrated into the processor 510 .

[0143] Optionally, as shown in FIG5 , the communication device 500 may further include a transceiver 530 , and the processor 510 may control the transceiver 530 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

[0144] The transceiver 530 may include a transmitter and a receiver. The transceiver 530 may further include an antenna, and the number of antennas may be one or more.

[0145] The communication device 500 may specifically be a terminal (such as a first terminal) in an embodiment of the present application, and the communication device 500 may implement the corresponding processes implemented by the terminal (such as a first terminal) in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0146] Figure 6 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 600 shown in Figure 6 includes a processor 610, which can call and run a computer program from a memory to implement the method according to the embodiment of the present application.

[0147] Optionally, as shown in FIG6 , the chip 600 may further include a memory 620 , wherein the processor 610 may call and execute a computer program from the memory 620 to implement the method in the embodiment of the present application.

[0148] The memory 620 may be a separate device independent of the processor 610 , or may be integrated into the processor 610 .

[0149] Optionally, the chip 600 may further include an input interface 630. The processor 610 may control the input interface 630 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0150] Optionally, the chip 600 may further include an output interface 640. The processor 610 may control the output interface 640 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0151] The chip can be applied to the terminal (such as the first terminal) in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the terminal (such as the first terminal) in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

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

[0153] It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0154] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0155] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0156] The present application also provides a computer-readable storage medium for storing a computer program. This computer-readable storage medium can be applied to a terminal (e.g., the first terminal) in the present application, and the computer program causes a computer to execute the corresponding processes implemented by the terminal (e.g., the first terminal) in each method of the present application. For the sake of brevity, these are not further described here.

[0157] The present application also provides a computer program product including computer program instructions. This computer program product can be applied to a terminal (e.g., the first terminal) in the present application, and the computer program instructions cause a computer to execute the corresponding processes implemented by the terminal (e.g., the first terminal) in the various methods of the present application. For the sake of brevity, these instructions are not further described here.

[0158] The present application also provides a computer program. This computer program can be applied to a terminal (such as the first terminal) in the present application. When the computer program is executed on a computer, it causes the computer to execute the corresponding processes implemented by the terminal (such as the first terminal) in each method of the present application. For the sake of brevity, these are not further described here.

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

[0160] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0161] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0163] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0164] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0165] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for determining a radio link failure, applied to a first terminal, the method comprising: In the event that a carrier radio link failure RLF occurs in all carriers in a first carrier set, it is determined that a link RLF occurs in a sidelink between the first terminal and the second terminal; wherein the first carrier set is used for sidelink transmission between the first terminal and the second terminal.

2. The method according to claim 1, wherein: In a case where carrier RLF occurs in all carriers in the first carrier set, the method further includes: The media access control MAC layer of the first terminal sends first indication information to the radio resource control RRC layer, where the first indication information is used to indicate that carrier RLF occurs in all carriers in the first carrier set.

3. The method according to claim 2, wherein: In a case where carrier RLF occurs in all carriers in the first carrier set, determining that a link RLF occurs in a sidelink between the first terminal and the second terminal, comprises: When the RRC layer receives the first indication information, it is determined that a link RLF occurs in the sidelink between the first terminal and the second terminal.

4. The method according to claim 1, wherein: The method further comprises: For any carrier in the first carrier set, when carrier RLF occurs in the carrier, the MAC layer of the first terminal sends second indication information corresponding to the carrier to the RRC layer, where the second indication information is used to indicate that carrier RLF occurs in the carrier.

5. The method according to claim 4, wherein: In a case where carrier RLF occurs in all carriers in the first carrier set, determining that a link RLF occurs in a sidelink between the first terminal and the second terminal, comprises: When the RRC layer receives second indication information corresponding to each carrier in the first carrier set, it is determined that a link RLF occurs in the sidelink between the first terminal and the second terminal.

6. The method according to claim 5, wherein: The determining, when the RRC layer receives second indication information corresponding to each carrier in the first carrier set, that a link RLF occurs in a sidelink between the first terminal and the second terminal, includes: When the RRC layer receives second indication information corresponding to each carrier in the first carrier set and the carrier RLF state of each carrier is not released, it is determined that a link RLF occurs in the sidelink between the first terminal and the second terminal.

7. The method according to claim 4, wherein: In a case where carrier RLF occurs in all carriers in the first carrier set, determining that a link RLF occurs in a sidelink between the first terminal and the second terminal, comprises: When the RRC layer receives second indication information corresponding to the first carrier in the first carrier set and the carrier RLF status of other carriers has been triggered and not released, it is determined that link RLF occurs in the sidelink between the first terminal and the second terminal.

8. The method according to any one of claims 4 to 7, wherein: The method further comprises: For any carrier in the first carrier set, when the carrier meets the first condition, the MAC layer of the first terminal sends third indication information corresponding to the carrier to the RRC layer, and the third indication information is used to indicate that the carrier RLF state of the carrier is released.

9. The method according to claim 8, wherein: The third indication information corresponding to the carrier is sent by the MAC layer of the first terminal to the RRC layer after carrier RLF occurs on the carrier.

10. The method according to claim 8 or 9, wherein: The first condition includes: At a reception timing of a physical sidelink feedback channel PSFCH, the PSFCH is received on the carrier; and / or, The timer corresponding to the carrier times out; wherein the timer corresponding to the carrier is started when carrier RLF occurs on the carrier.

11. The method according to claim 10, wherein: The timing duration of the timer is pre-configured or network configured.

12. The method according to any one of claims 1 to 11, wherein: The occurrence of carrier RLF in any carrier in the first carrier set is determined based on the value of the counter corresponding to the carrier reaching a first threshold; wherein, if PSFCH is not received on the carrier at the reception timing of PSFCH, the value of the counter corresponding to the carrier increases by 1.

13. The method according to claim 12, wherein: The method further comprises: When the value of the counter corresponding to the carrier reaches the first threshold, it is determined that carrier RLF occurs in the carrier.

14. The method according to claim 12 or 13, wherein: The first threshold is pre-configured or network configured.

15. The method according to any one of claims 12 to 14, wherein: If the PSFCH is received on the carrier at the PSFCH reception timing, the value of the counter corresponding to the carrier is initialized to 0.

16. The method according to any one of claims 1 to 15, wherein: The first carrier set is pre-configured or network configured; or, The first carrier set is configured by the first terminal or the second terminal; or, The first carrier set is a carrier set determined by the first terminal for data transmission; or, The first carrier set is a carrier set corresponding to the time-frequency resources used by the first terminal to send data.

17. The method according to claim 16, wherein: In a case where the first carrier set is configured by the first terminal, the method further includes: Send fourth indication information to the second terminal, where the fourth indication information is used to indicate the first carrier set.

18. A wireless link failure determination device, the device comprising: The first determination unit is used to determine that a sidelink between the device and the second terminal has a link RLF when a carrier radio link failure RLF occurs in all carriers in a first carrier set; wherein the first carrier set is used for sidelink transmission between the device and the second terminal.

19. The device according to claim 18, wherein: The device also includes: The first sending unit is used to, when carrier RLF occurs in all carriers in the first carrier set, the media access control MAC layer of the device sends first indication information to the radio resource control RRC layer, wherein the first indication information is used to indicate that carrier RLF occurs in all carriers in the first carrier set.

20. The device according to claim 19, wherein The first determination unit is specifically used to determine that a link RLF occurs in the sidelink between the device and the second terminal when the RRC layer receives the first indication information.

21. The device according to claim 18, wherein The device also includes: The second sending unit is used for sending, for any carrier in the first carrier set, second indication information corresponding to the carrier by the MAC layer of the device to the RRC layer when carrier RLF occurs on the carrier, wherein the second indication information is used to indicate that carrier RLF occurs on the carrier.

22. The device according to claim 21, wherein The first determination unit is specifically used to determine that a link RLF occurs in the sidelink between the device and the second terminal when the RRC layer receives second indication information corresponding to each carrier in the first carrier set.

23. The device according to claim 22, wherein: The first determination unit is specifically used to determine that link RLF occurs in the side link between the device and the second terminal when the RRC layer receives second indication information corresponding to each carrier in the first carrier set and the carrier RLF state of each carrier has not been released.

24. The method according to claim 21, wherein: The first determination unit is specifically used to determine that a link RLF occurs in the sidelink between the first terminal and the second terminal when the RRC layer receives second indication information corresponding to the first carrier in the first carrier set and the carrier RLF status of other carriers has been triggered and not released.

25. The device according to any one of claims 21 to 24, wherein The device also includes: The third sending unit is used for, for any carrier in the first carrier set, when the carrier meets the first condition, the MAC layer of the device sends third indication information corresponding to the carrier to the RRC layer, and the third indication information is used to indicate that the carrier RLF state of the carrier is released.

26. The device according to claim 25, wherein The third indication information corresponding to the carrier is sent by the MAC layer of the device to the RRC layer after the carrier RLF occurs on the carrier.

27. The device according to claim 25 or 26, wherein: The first condition includes: At a reception timing of a physical sidelink feedback channel PSFCH, the PSFCH is received on the carrier; and / or, The timer corresponding to the carrier times out; wherein the timer corresponding to the carrier is started when carrier RLF occurs on the carrier.

28. The device according to claim 27, wherein The timing duration of the timer is pre-configured or network configured.

29. The device according to any one of claims 18 to 28, wherein The occurrence of carrier RLF in any carrier in the first carrier set is determined based on the value of the counter corresponding to the carrier reaching a first threshold; wherein, if PSFCH is not received on the carrier at the reception timing of PSFCH, the value of the counter corresponding to the carrier increases by 1.

30. The device according to claim 29, wherein: The device also includes: The second determining unit is configured to determine that a carrier RLF occurs in the carrier when the value of the counter corresponding to the carrier reaches the first threshold.

31. The device according to claim 29 or 30, wherein: The first threshold is pre-configured or network configured.

32. The device according to any one of claims 29 to 31, wherein: If the PSFCH is received on the carrier at the PSFCH reception timing, the value of the counter corresponding to the carrier is initialized to 0.

33. The device according to any one of claims 18 to 32, wherein: The first carrier set is pre-configured or network configured; or, The first carrier set is configured by the device or the second terminal; or, The first carrier set is a carrier set determined by the apparatus for data transmission; or, The first carrier set is a carrier set corresponding to the time-frequency resources used by the device to send data.

34. The device according to claim 33, wherein The device also includes: A fourth sending unit is used to send fourth indication information to the second terminal when the first carrier set is configured by the device, where the fourth indication information is used to indicate the first carrier set.

35. A terminal, comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 17.

36. A chip, comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 17.

37. A computer-readable storage medium for storing a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 17.

38. A computer program product comprising computer program instructions for causing a computer to execute the method as claimed in any one of claims 1 to 17.

39. A computer program, the computer program causing a computer to execute the method according to any one of claims 1 to 17.

Citation Information

Patent Citations

  • RLM and RLF procedures for NR v2x

    WO2020198586A1

  • Radio link failure trigger and recovery in case of sidelink carrier aggregation

    WO2023073210A1