Communication method, apparatus and system

Abstract

This application provides a communication method, apparatus, and system for avoiding false triggering of RLF (Ranged Link Failure) or reducing the probability of false triggering of RLF. The method includes: a first user equipment (User Equipment) sending first data to a second user equipment (User Equipment) via a sidelink (SL); if the first user equipment does not receive first feedback information, the first user equipment initializes a first counter, or the count value of the first counter remains unchanged; wherein the first feedback information indicates whether the second user equipment successfully received the first data; the first counter is used for RLF detection.

Description

Technical Field

[0001] This application relates to the field of sidelink (SL) communication technology, and in particular to SL communication methods, apparatus and systems. Background Technology

[0002] Vehicle-to-everything (V2X) is a key technology for intelligent transportation systems and is considered one of the most promising areas in the Internet of Things (IoT) ecosystem, with the clearest market demand. V2X generally refers to a communication network that uses sensors and onboard terminals to provide vehicle information, enabling communication between vehicles (V2V), vehicles (V2I), vehicles (V2N), and vehicles (V2P).

[0003] V2X has the characteristics of wide application scope, great industrial potential and strong social benefits. It is of great significance for promoting the innovative development of the automotive and information and communication industries, building new models and new business forms of automotive and transportation services, promoting the innovation and application of technologies such as unmanned driving, assisted driving, intelligent driving, connected driving, intelligent connected driving, autonomous driving, and car sharing, as well as improving traffic efficiency and safety.

[0004] In general, in V2X scenarios, the communication link that enables direct communication between terminals can be called a sidelink (SL) or a side link.

[0005] Currently, in new radio (NR) V2X, hybrid automatic repeat request (HARQ) feedback is supported on the SL (Short Link Line) for both unicast and multicast. The HARQ feedback is transmitted on the physical side link feedback channel (PSFCH). Furthermore, for unicast, radio link failure (RLF) can be detected based on HARQ, specifically by triggering an SL RLF when the number of consecutive PFSCH failures reaches a certain threshold. However, in existing technologies, this may lead to the transmitter falsely triggering RLF. Summary of the Invention

[0006] This application provides a communication method, apparatus, and system for avoiding false triggering of RLF or reducing the probability of false triggering of RLF.

[0007] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0008] Firstly, a communication method is provided. The communication device executing this method can be a first user equipment or a module applied in the first user equipment, such as a chip or chip system. The following description uses the first user equipment as the executing entity. The first user equipment sends first data to a second user equipment via a sidelink (SL). If the first user equipment does not receive first feedback information, it initializes a first counter, or the count value of the first counter remains unchanged. The first feedback information indicates whether the second user equipment successfully received the first data. The first counter is used for radio link failure (RLF) detection. In the communication method provided in this application embodiment, the first user equipment fails to receive the first feedback information because it does not receive it, rather than because of a problem with the radio link. The first counter used for RLF detection does not count cases where the first user equipment fails to receive the first feedback information, thus preventing the count value of the first counter from reaching the RLF trigger value incorrectly / prematurely / too quickly, thereby avoiding false RLF triggering and reducing communication latency, improving / guaranteeing communication quality or reliability.

[0009] In conjunction with the first aspect described above, in one possible implementation, if the first user equipment receives the first feedback information, and if the first user equipment does not receive the first feedback information, the first user equipment increments the count value of the first counter by 1. In this method, the first user equipment receiving but not receiving the first feedback information may be due to a problem with the wireless link. The first counter records the cases where the first user equipment receives but does not receive the first feedback information. Compared to existing technologies, this method adds a conditional constraint on the increment of the first counter's count value. Therefore, it can prevent the first counter's count value from reaching the trigger value for RLF incorrectly / prematurely / too quickly, thereby avoiding false triggering of RLF, and further reducing communication latency and improving / guaranteeing communication quality or reliability.

[0010] In conjunction with the first aspect described above, in one possible implementation, the first user equipment not receiving the first feedback information includes: the reception of the first feedback information conflicted with the first transmission, and the first user equipment did not receive the first feedback information. In this method, the first counter used for RLF detection does not count resource conflicts, allowing the first counter to exclude more other possible reasons why the first user equipment might not receive the first feedback information. It can more specifically count the number of times the first user equipment failed to receive the first feedback information due to problems with the wireless link, thereby further preventing the first counter's count value from reaching the RLF trigger value incorrectly / prematurely / too quickly, thus avoiding false RLF triggering. This can also reduce communication latency and improve / guarantee communication quality or reliability.

[0011] In conjunction with the first aspect described above, in one possible implementation, the first user equipment fails to receive the first feedback information due to a conflict between the reception of the first feedback information and the first transmission. This includes situations where the reception of the first feedback information conflicts with the first transmission, and the priority of receiving the first feedback information is lower than or equal to the priority of the first transmission. In this method, a resource conflict occurs, and the priority of receiving the first feedback information is lower. The first user equipment executes the higher-priority first transmission instead of receiving the first feedback information, resulting in the failure to receive the first feedback information. This is not due to a problem with the wireless link. The first counter used for RLF detection does not count cases where the first user equipment fails to receive the first feedback information, thus preventing the count value of the first counter from reaching the RLF trigger value incorrectly / prematurely / too quickly, thereby avoiding false triggering of RLF and reducing communication latency, improving / guaranteeing communication quality or reliability.

[0012] In conjunction with the first aspect above, in one possible implementation, the initialization of the first counter by the first user equipment includes: the first user equipment initializing the count value of the first counter to 0.

[0013] In conjunction with the first aspect above, in one possible implementation, the signal quality between the first user equipment and the second user equipment is greater than or equal to a first threshold. When the signal quality is good, it indicates that the wireless link is normal. The first counter used for RLF detection does not count cases where the first user equipment does not receive the first feedback information, thus avoiding false triggering of RLF. This can also reduce communication latency and improve / guarantee communication quality or reliability.

[0014] In conjunction with the first aspect described above, in one possible implementation, if the signal quality between the first user equipment and the second user equipment is less than or equal to a second threshold, and the first user equipment does not receive the first feedback information, the first user equipment increments the count value of the first counter by 1. Poor signal quality indicates a possible anomaly in the wireless link. In this case, the first counter used for RLF detection counts instances where the first user equipment fails to receive the first feedback information, thus triggering RLF more quickly.

[0015] In conjunction with the first aspect above, in one possible implementation, the first feedback information is transmitted on the physical side line feedback channel (PSFCH).

[0016] In conjunction with the first aspect described above, in one possible implementation, the count value of the first counter is greater than or equal to a third threshold. The first user equipment sends first indication information to the network device, which indicates that the first user equipment has detected an RLF. The first user equipment triggers the RLF and reports it to the network device to indicate that there is an anomaly in the wireless link.

[0017] Secondly, a communication device is provided for implementing the above-described method. This communication device includes modules, units, or means corresponding to the implementation of the above-described method. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above-described functions.

[0018] In conjunction with the second aspect above, in one possible implementation, the communication device includes: a transceiver module and a processing module; the transceiver module is used to send first data to a second user equipment via a sidelink (SL); the processing module is used to initialize a first counter if no first feedback information is received, or to keep the count value of the first counter unchanged; wherein the first feedback information indicates whether the second user equipment has successfully received the first data; the first counter is used for radio link failure (RLF) detection.

[0019] In conjunction with the second aspect above, in one possible implementation, the transceiver module is further configured to receive the first feedback information; the processing module is further configured to increment the count value of the first counter by 1 if the first feedback information is not received.

[0020] In conjunction with the second aspect above, in one possible implementation, not receiving the first feedback information includes: the reception of the first feedback information conflicts with the first transmission, and the first feedback information is not received.

[0021] In conjunction with the second aspect above, in one possible implementation, not receiving the first feedback information includes: the reception of the first feedback information conflicts with the first transmission, and the priority of receiving the first feedback information is lower than or equal to the priority of the first transmission.

[0022] In conjunction with the second aspect above, in one possible implementation, the processing module initializes the first counter by: initializing the count value of the first counter to 0.

[0023] In conjunction with the second aspect above, in one possible implementation, the signal quality between the first user equipment and the second user equipment is greater than or equal to a first threshold.

[0024] In conjunction with the second aspect above, in one possible implementation, the processing module is further configured to increment the count value of the first counter by 1 if the signal quality between the first user equipment and the second user equipment is less than or equal to the second threshold and the first feedback information is not received.

[0025] In conjunction with the second aspect above, in one possible implementation, the first feedback information is transmitted on the physical side line feedback channel (PSFCH).

[0026] In conjunction with the second aspect above, in one possible implementation, the transceiver module is further configured to send first indication information to the network device when the count value of the first counter is greater than or equal to a third threshold. The first indication information is used to indicate that the first user equipment has detected an RLF.

[0027] The technical effects of the second aspect and any possible implementation thereof can be found in the first aspect and the technical effects of different implementations thereof, and will not be repeated here.

[0028] Thirdly, a communication method is provided. The communication device executing this method can be a first user equipment or a module applied in the first user equipment, such as a chip or chip system. The following description uses the first user equipment as the executing entity. The first user equipment sends first data to a second user equipment via a side link SL; if the first user equipment does not receive first feedback information, it increments the count value of a second counter by 1; wherein the first feedback information indicates whether the second user equipment successfully received the first data; the second counter is used to count the number of consecutive times the first user equipment fails to receive feedback information.

[0029] In conjunction with the third aspect above, in one possible implementation, the first user equipment receives the first feedback information and initializes the second counter.

[0030] In conjunction with the third aspect above, in one possible implementation, the first user equipment initializes the second counter by setting the second counter to 0.

[0031] In conjunction with the third aspect described above, in one possible implementation, the count value of the second counter is greater than or equal to a fourth threshold, and the first user equipment sends a second indication message and / or a third indication message to the network device, or the first user equipment triggers resource reselection. The second indication message is used to indicate that the first user equipment detected an RLF, or to indicate that an RLF occurred, or to indicate that the reason for the SL failure was an RLF. The third indication message is used to indicate that the count value of the second counter reaches (or is greater than or equal to) the fourth threshold, or that the count value of the second counter reaches (or is less than or equal to) 0 or a second value, or to indicate that the number of consecutive times the first user equipment has not received feedback information has reached a preset threshold (e.g., the fourth threshold), or to indicate that the number of consecutive conflicts between the reception of feedback information and other transmissions has reached a preset threshold (e.g., the fourth threshold).

[0032] In conjunction with the third aspect described above, in one possible implementation, the second indication information is further used to indicate the cause of the RLF (Resource Conflict of Interest), including the first user equipment failing to receive feedback information for a certain number of consecutive times reaching the fourth threshold. In this scheme, the first user equipment can report the second indication information (e.g., the cause of triggering / detecting the RLF) and / or the third indication information to the network device, indicating that the probability of a resource conflict is currently high. This allows the network device to adjust certain parameters accordingly to reduce the probability of resource conflicts, thereby improving communication quality, reducing communication latency, and ensuring communication reliability.

[0033] In conjunction with the third aspect mentioned above, in one possible implementation, when the first user equipment triggers / detects an RLF, it can take corresponding strategies, such as restoring or rebuilding the unicast connection, which is beneficial for improving communication quality, reducing communication latency, and ensuring communication reliability.

[0034] In conjunction with the third aspect mentioned above, in one possible implementation, the first user equipment triggers resource reselection, which allows the first user equipment to reselect resources. This helps reduce the probability of resource conflicts / transmission conflicts, improves communication quality, reduces communication latency, and ensures communication reliability.

[0035] Fourthly, a communication device is provided for implementing the above-described method. This communication device includes modules, units, or means corresponding to the implementation of the above-described method. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above-described functions.

[0036] In conjunction with the fourth aspect above, in one possible implementation, the communication device includes: a transceiver module and a processing module; the transceiver module is used to send first data to a second user equipment via a side link SL; the processing module is used to increment the count value of a second counter by 1 if the first feedback information is not received; wherein the first feedback information indicates whether the second user equipment has successfully received the first data; the second counter is used to count the number of times the first user equipment has consecutively failed to receive feedback information.

[0037] In conjunction with the fourth aspect above, in one possible implementation, the transceiver module is further configured to receive the first feedback information, and the processing module is further configured to initialize the second counter.

[0038] In conjunction with the fourth aspect above, in one possible implementation, the processing module is further configured to initialize the second counter by: initializing the second counter to 0.

[0039] In conjunction with the fourth aspect above, in one possible implementation, the transceiver module is further configured to: send second indication information and / or third indication information to the network device when the count value of the second counter is greater than or equal to the fourth threshold; or, the processing module is configured to trigger resource reselection. The second indication information is used to indicate that the first user equipment has detected an RLF, or to indicate that an RLF has occurred, or to indicate that the reason for the SL failure is an RLF. The third indication information is used to indicate that the count value of the second counter reaches (or is greater than or equal to) the fourth threshold, or that the count value of the second counter reaches (or is less than or equal to) 0 or a second value, or to indicate that the number of times the first user equipment has continuously failed to receive feedback information has reached a preset threshold (e.g., the fourth threshold), or to indicate that the number of times the reception of feedback information and other transmissions have continuously conflicted has reached a preset threshold (e.g., the fourth threshold).

[0040] In conjunction with the fourth aspect above, in one possible implementation, the second indication information is also used to indicate the reason for the RLF, which includes the number of times the first user equipment has not received feedback information for a continuous period of time reaching the fourth threshold.

[0041] The technical effects of the fourth aspect and any possible implementation of the fourth aspect can be found in the third aspect and the technical effects of different implementations of the third aspect, which will not be repeated here.

[0042] Fifthly, a communication device is provided, comprising: a processor; the processor being configured to be coupled to a memory, and after reading computer instructions stored in the memory, to execute the method as described in any of the preceding aspects according to the instructions.

[0043] In conjunction with the fifth aspect above, in one possible implementation, the communication device further includes a memory for storing computer instructions.

[0044] In conjunction with the fifth aspect above, in one possible implementation, the communication device further includes a communication interface; this communication interface is used for the communication device to communicate with other devices. For example, the communication interface may be a transceiver, an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or related circuitry, etc.

[0045] In conjunction with the fifth aspect above, in one possible implementation, the communication device can be a chip or a chip system. When the communication device is a chip system, it can be composed of chips or may include chips and other discrete components.

[0046] In conjunction with the fifth aspect above, in one possible implementation, when the communication device is a chip or chip system, the aforementioned communication interface can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system. The aforementioned processor can also be embodied as a processing circuit or logic circuit.

[0047] In a sixth aspect, a computer-readable storage medium is provided that stores instructions which, when executed on a computer, cause the computer to perform the methods described in any of the preceding aspects.

[0048] In a seventh aspect, a computer program product containing instructions is provided, which, when run on a computer, enables the computer to perform the methods described in any of the preceding aspects.

[0049] The technical effects of any possible implementation of aspects five to six can be found in the technical effects of different implementations of aspects one and three above, and will not be repeated here. Attached Figure Description

[0050] Figure 1 A schematic diagram illustrating how the sending end uses parallel HARQ processes to send data in existing technologies;

[0051] Figure 2 This is a schematic diagram of the existing HARQ-based SL RLF detection process;

[0052] Figure 3 This application provides a schematic diagram of the architecture of a communication system.

[0053] Figure 4 This is a schematic diagram of the structure of a communication device provided in this embodiment;

[0054] Figure 5This is a schematic diagram of the structure of a mobile terminal provided in an embodiment of this application;

[0055] Figure 6a A communication method provided in an embodiment of this application;

[0056] Figure 6b Another communication method provided in the embodiments of this application;

[0057] Figure 7 This is a schematic diagram illustrating the existing HARQ-based SL RLF detection process and the communication method provided in the embodiments of this application for the RLF detection process;

[0058] Figure 8 This application provides yet another communication method.

[0059] Figure 9 This is a schematic diagram of another communication device provided in this embodiment. Detailed Implementation

[0060] To facilitate understanding of the technical solutions of the embodiments of this application, a brief introduction to the relevant technologies or terms of this application is given below.

[0061] First, vehicle-to-everything (V2X)

[0062] In V2X communication, the communication link for direct communication between terminal devices can be called a sidelink (SL). The wireless communication link from the terminal device to the network device can be called an uplink (UL); the wireless communication link from the network device to the terminal device can be called a downlink (DL). Since the UL or DL ​​interface can also be called a Uu interface, UL or DL ​​can be referred to as a Uu interface link.

[0063] NR V2X supports unicast, multicast and broadcast services.

[0064] It should be noted that the terminal, terminal equipment, user equipment, and UE in this application can be interchanged.

[0065] Second, Hybrid Automatic Repeat Request (HARQ).

[0066] 1) HARQ Feedback:

[0067] One possible HARQ feedback mechanism is as follows: if the receiver successfully receives data, it sends an acknowledgment (ACK) to the sender; if the receiver fails to receive data, it sends a negative acknowledgment (NACK) to the sender.

[0068] In NR V2X, SL HARQ feedback is supported for both unicast and multicast.

[0069] 2) HARQ process:

[0070] HARQ uses a stop-and-wait protocol to control data transmission. Specifically, after sending a transport block (TB), the sender pauses and waits until it receives feedback information for that TB before sending the next TB. This process of the sender stopping to wait for feedback information leads to a decrease in throughput.

[0071] To improve throughput, the sender can use multiple parallel HARQ processes. That is, while the sender is waiting for feedback from one HARQ process, another HARQ process can continue sending data. For example, as... Figure 1 As shown, the sender uses the first HARQ process to send TB1, and the transmission of TB1 is completed at time T1. The sender waits for feedback from TB1 until time T2, when it receives the feedback. During the waiting period from T1 to T2, the sender can use the second HARQ process to send TB2. Similarly, after the sender completes the transmission of TB2 at time T2, it waits for feedback from TB2 until time T3, when it receives the feedback. During the waiting period from T2 to T3, the sender can use the third HARQ process to send TB3.

[0072] It should be noted that a HARQ process on the Uu port can be referred to as a HARQ process. On the UU port, a HARQ process can be identified by a HARQ process identity (process ID), or in other words, a HARQ process can be associated with a HARQ process ID.

[0073] It should be noted that in NR V2X, the HARQ process on the SL can be called the SL process.

[0074] Third, SL process

[0075] On the SL, the transmitting user equipment (UE) can send sidelink control information (SCI) and SL data to one or more receiving UEs. The SCI is used to schedule the SL data.

[0076] In NR V2X, SCI can include Level 1 SCI and Level 2 SCI.

[0077] Since SL data is transmitted through the physical sidelink shared channel (PSSCH), SL data can also be referred to as PSSCH. This will be used consistently here and will not be repeated below. The first-level SCI and the second-level SCI will be described separately below.

[0078] The Level 1 SCI can be used to schedule Level 2 SCI and SL data / PSSCH. The Level 1 SCI can be transmitted via the physical sidelink control channel (PSCCH).

[0079] The second-level SCI can be used to decode SL data / PSSCH.

[0080] An SCI or a second-level SCI may include an SL process ID, a first destination ID, a first source ID, and a cast type.

[0081] In NR V2X, a set of IDs can identify a SL process, or a SL process can be associated with a set of IDs.

[0082] The ID set may include an SL process ID, a first destination ID, a first source ID, and a communication type; or, the ID set may include an SL process ID, a first destination ID, and a first source ID; or, the ID set may include an SL process ID, a second destination ID, a second source ID, and a communication type; or, the ID set may include an SL process ID, a second destination ID, and a second source ID.

[0083] The following sections will explain the SL process ID, first destination ID, second destination ID, first source ID, second source ID, and communication type.

[0084] 1)SL process ID

[0085] The SL process ID can be used to identify an SL process.

[0086] 2) First destination ID and second destination ID

[0087] The first destination ID can be used to identify the target of SL data scheduled by SCI. Optionally, the first destination ID can be used by the physical layer of the receiving UE to filter data packets. For example, the first destination ID can be a destination layer-1 ID. For instance, layer 1 can represent the first layer in the Open Systems Interconnection Reference Model (OSI model)—the physical layer.

[0088] For example, the first destination ID can be a subset of the bits of the second destination ID. For instance, if the second destination ID is 24 bits, then the first destination ID can be the lower 16 bits of the second destination ID.

[0089] The second destination ID can be used to identify the destination (e.g., target) / receiving end / receiving terminal of data. For example, the second destination ID can be used to identify a multicast or broadcast service. For example, the second destination ID can be an identifier for the destination / receiving end / receiving terminal. For example, the second destination ID can be a Destination Layer-2 ID. Optionally, the second destination ID can be used for packet filtering at the media access control (MAC) layer of the receiving terminal. For example, Layer 2 represents the second layer in the OSI model—the data link layer, which includes the MAC layer.

[0090] 3) First source ID and second source ID

[0091] The first source ID can be used to identify the source of SL data scheduled by SCI. Optionally, the first source ID can be used by the PHY layer of the receiving terminal for packet filtering. For example, the first source ID can be a source layer-1 ID.

[0092] For example, the first source ID can be a subset of the bits of the second source ID. For instance, if the second source ID is 24 bits, then the first source ID can be the lower 8 bits of the second source ID. The second source ID can be used to identify the source or sender of the data. For example, the second source ID can be a source layer-2 ID.

[0093] 4) Communication type

[0094] Communication types can include one or more of unicast, multicast, and broadcast. The communication type in an SCI indicates whether the current communication is unicast, multicast, or broadcast; or, the communication type in an SCI indicates whether the SL data scheduled by the SCI is unicast data, multicast data, or broadcast data.

[0095] For example, a second source ID and a second destination ID pair can identify a unicast.

[0096] For example, when the MAC layer of the receiving UE filters data packets for unicast, it can use a second destination ID and a second source ID.

[0097] For example, when the physical layer of the receiving UE filters data packets for unicast, it can use the first destination ID and the first source ID.

[0098] Fourth, the reception of the physical side link feedback channel (PSFCH) may conflict with other transmissions / receptions.

[0099] For example, the following describes three scenarios where PSFCH reception conflicts with other transmissions / receptions.

[0100] For example, a conflict can be either a conflict in the time domain or a conflict within a time slot.

[0101] For example, conflict can be understood / replaced as overlap or overlap.

[0102] The reception of PSFCH is associated with SCI 1 and / or SL data 1. It is understood that after the sending UE sends SCI 1 and / or SL data 1 to the receiving UE, the sending UE may receive the receiving UE's SL HARQ feedback on PSFCH resource 1 (which can be understood as the reception of PSFCH).

[0103] 1) Conflict between PSFCH reception and PSFCH transmission.

[0104] The reception of PSFCH (for the transmission of SL data 1) conflicts with the transmission of PSFCH (associated with other data transmissions). If the priority of receiving PSFCH is lower than or equal to the priority of transmitting PSFCH (or in other words, receiving PSFCH is not given priority), then the UE that sends SL data 1 will perform the transmission of PSFCH instead of the reception of PSFCH, and thus the UE that sends SL data 1 will not receive PSFCH.

[0105] It should be noted that the UE that sends SL data 1 can also act as the UE that receives SL data 2, thereby sending PSFCH to the UE that sends SL data 2.

[0106] It should be noted that the priority of receiving or transmitting PSFCH is determined by the priority of the SL data associated with PSFCH. Specifically, the priority field in the SCI or the first-level SCI corresponding to the SL data carries the priority information of the SL data; the smaller the value of the priority field, the higher the priority of the SL data.

[0107] 2) Conflict between PSFCH reception and UL transmission

[0108] The reception of PSFCH (for the transmission of SL data 1) conflicts with UL transmission. If the priority of PSFCH reception is lower than or equal to the priority of UL transmission (or in other words, PSFCH reception is not prioritized), then the sending UE performs UL transmission instead of PSFCH reception, and thus the sending UE does not receive PSFCH. Here, "transmission" can be understood as "sending and / or receiving".

[0109] For example, a conflict between PSFCH reception (for the transmission of SL data 1) and UL transmission could include: the PSFCH reception (for the transmission of SL data 1) and UL transmission conflicting within the same time slot. It should be noted that, in one possible implementation, the priority of PSFCH reception within a time slot can be the highest priority among the priorities of the SL data corresponding to multiple PSFCHs within that time slot.

[0110] 3) NR SL PSFCH reception conflicts with Long Term Evolution (LTE) SL transmission.

[0111] In NR SL transmission, at the sending UE, the reception of PSFCH conflicts with the LTE SL transmission in terms of time. If the priority of PSFCH reception is lower than or equal to the priority of LTE SL transmission (or in other words, PSFCH reception is not given priority), then the sending UE performs LTE SL transmission instead of PSFCH reception, and thus the sending UE does not receive PSFCH.

[0112] It should be noted that the priority of receiving or transmitting PSFCH is determined by the priority of the SL data associated with PSFCH. Specifically, the priority field in the SCI or the first-level SCI corresponding to the SL data carries the priority information of the SL data; the smaller the value of the priority field, the higher the priority of the SL data.

[0113] It should be noted that different priority levels are defined in the NR and LTE systems. For a comparison of transmission priorities between the two systems, please refer to existing technologies; further details will not be elaborated here.

[0114] It should be noted that the above conflict can be understood as a conflict within a single UE (sending UE).

[0115] It should be noted that the sending end can be understood as the end that sends the data.

[0116] It should be noted that the above-mentioned conflict situations and their priority comparisons are existing technologies and will not be elaborated here. For details, please refer to the descriptions in 3GPP TS 38.213: "NR; Physical Layer Procedures for control" and 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification".

[0117] Fifth, HARQ-based radio link failure (RLF) detection in SL (Single Link Flow).

[0118] In NR V2X, HARQ-based SL RLF detection is introduced for unicast connections. The transmitting UE uses a counter to count the number of consecutive PFSCH failures. Specifically, if the transmitting UE does not receive the PFSCH, it increments the counter by 1; if the transmitting UE receives the PFSCH, it initializes / sets the counter to 0. If the counter reaches a threshold, the transmitting UE triggers RLF. For details, refer to section 5.22.1.3.3 of 3GPP TS 38.321: "NR; Medium Access Control (MAC) protocol specification".

[0119] When a unicast connection is established, or when a threshold is configured or reconfigured, the sending UE initializes / sets the counter value to 0.

[0120] The counter can be numConsecutiveDTX, and the threshold can be sl-maxNumConsecutiveDTX. The value of the threshold is configured by the network device, or the value of the threshold is pre-configured.

[0121] For example, Figure 2The HARQ-based SL RLF detection process is illustrated. The initial value of the counter is 0, and the threshold for triggering RLF is 3. For example, the PSFCH listening timing can be understood as the PSFCH itself, its location, its time-domain location, or the timing of PSFCH reception. It should be noted that... Figure 2 The diagram only schematically illustrates 11 PSFCH listening opportunities. In reality, the PSFCH listening opportunities may be continuous or discontinuous in the time domain, and different PSFCH listening opportunities may also overlap in the time domain. This application does not impose any limitations on this.

[0122] In this context, "receive" PSFCH by the sending UE indicates that the sending UE has performed the action of "receiving" PSFCH. The result of the sending UE "receiving" PSFCH may be that the sending UE "received" PSFCH, or it may be that the sending UE "did not receive" PSFCH.

[0123] A "not received" PSFCH message from the sending UE indicates that the sending UE did not perform the "receive" action. When the sending UE's "receive" of PSFCH conflicts with other transmissions / receptions by the sending UE, because the priority of "receive" PSFCH is lower than the priority of other transmissions / receptions (or in other words, "receive" PSFCH was not given priority), the sending UE performs other transmissions / receptions instead of performing the "receive" PSFCH action. Therefore, the result of the sending UE "not receiving" PSFCH is simply that the sending UE "did not receive" PSFCH.

[0124] During the first PSFCH listening opportunity, the sending UE did not receive the PSFCH because the reception of the PSFCH conflicted with other transmissions and was not prioritized. Therefore, the sending UE did not receive the PSFCH. In the existing protocol, the counter value is incremented by 1, changing from an initial value of 0 to 1.

[0125] During the second PSFCH listening opportunity, the sending UE attempts to receive the PSFCH, but fails to actually receive it. The counter value in the existing protocol is incremented by 1, becoming 2.

[0126] During the third PSFCH listening opportunity, the sending UE receives the PSFCH. The counter value in the existing protocol is initialized / set to 0.

[0127] During the fourth PSFCH listening opportunity, the sending UE attempts to receive the PSFCH, but fails to actually receive it. The counter value in the existing protocol is incremented by 1, becoming 1.

[0128] During the 5th PSFCH listening time, the sending UE attempts to receive the PSFCH, but fails to actually receive it. The counter value in the existing protocol is incremented by 1, becoming 2.

[0129] During the 6th PSFCH listening opportunity, due to a conflict between PSFCH reception and other transmissions, and because PSFCH reception was not prioritized, the sending UE did not receive the PSFCH. Therefore, the sending UE did not receive the PSFCH. The counter value in the existing protocol increments by 1, becoming 3. Since the counter value in the existing protocol has reached the threshold, the sending UE triggers an RLF (Restricted Read Response).

[0130] At the 7th PSFCH listening time, the sending UE receives the PSFCH. The counter value in the existing protocol is initialized / set to 0.

[0131] During the 8th PSFCH listening opportunity, the sending UE did not receive the PSFCH because the reception of the PSFCH conflicted with other transmissions and was not prioritized. Therefore, the sending UE did not receive the PSFCH. In the existing protocol, the counter value is incremented by 1, changing from an initial value of 0 to 1.

[0132] During the 9th PSFCH listening opportunity, the sending UE did not receive the PSFCH because its reception conflicted with other transmissions and was not prioritized. Therefore, the sending UE did not receive the PSFCH. The counter value in the existing protocol is incremented by 1, becoming 2.

[0133] At the 10th PSFCH listening time, the sending UE receives the PSFCH. The counter value in the existing protocol is initialized / set to 0.

[0134] At the 11th PSFCH listening time, the sending UE receives the PSFCH. In the existing protocol, the counter value is initialized / set to 0, or in other words, the first counter value remains unchanged at 0.

[0135] It is necessary to understand that Figure 2 The 7th PSFCH listening opportunity and subsequent PSFCH listening opportunities may be the PSFCH corresponding to the SL transmission after the unicast connection is restored. It is understandable that if an RLF is triggered, in order to restore the unicast connection, Figure 2 The 7th PSFCH listening opportunity and subsequent PSFCH listening opportunities may not exist.

[0136] Based on the above analysis, the counter value is 2 during the 5th PSFCH listening time. During the 6th PSFCH listening time, the sending UE did not receive the PSFCH because it did not, not because of a problem with the radio link. In existing HARQ-based SL RLF detection, the counter value increases by 1 during the 6th PSFCH listening time, causing the counter value to reach the threshold of 3. This leads to the sending UE falsely triggering an RLF, increasing communication latency and reducing communication quality or reliability. Especially when the threshold is 1, the sending UE is more likely to falsely trigger an RLF using existing HARQ-based SL RLF detection.

[0137] It should be noted that currently in NR V2X, HARQ-based SL RLF detection is performed on a unicast connection basis, and the counter is maintained separately for each unicast connection. Here, the number of consecutive PSFCH failures can be understood as: the number of consecutive PSFCH failures for a single unicast connection (e.g., one unicast connection), or the number of consecutive PSFCH failures for all sidelink processes of a single unicast connection (e.g., one unicast connection).

[0138] A unicast connection can also be referred to as a radio resource control (RRC) connection in SL, or a PC5-RRC connection. A unicast connection can be a logical connection between a pair of second source IDs and second destination IDs; alternatively, a unicast connection can be a logical connection between a pair of second source IDs and second destination IDs at the access stratum (AS) layer. A unicast connection can include / replace / correspond to any one or more of the following: unicast, unicast connection, destination address, and a pair of second source IDs and second destination IDs. The destination address can be understood as the corresponding pair of second source IDs and second destination IDs.

[0139] For example, the RLF in this application may include / be understood as SL RLF.

[0140] For example, initialization in this application may include / be replaced by: reinitialization.

[0141] For example, the first user equipment in this application may include / be replaced by: the HARQ entity of the first user equipment, or the SL HARQ entity of the first user equipment, or the MAC entity of the first user equipment.

[0142] For example, "for a unicast connection" in this application may include / be replaced with: "for a single unicast connection", or "for a first unicast connection".

[0143] For example, the SL process associated with a unicast connection in this application may include / be replaced by any one or more of the following: an SL process associated with a destination address, an SL process associated with a second source ID and a second destination ID pair, and an SL process associated with a first source ID and a first destination ID pair.

[0144] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0145] It should be noted that, in this application, the terms "exemplary" or "for example" are used to indicate that something is being described as an example, illustration, or illustration. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0146] The methods provided in this application are applicable to, but not limited to, the following fields: device-to-device (D2D), V2X, unmanned driving, automated driving (ADS), driver assistance (ADAS), intelligent driving, connected driving, intelligent network driving, carsharing, etc.

[0147] The communication systems in this application include, but are not limited to, long-term evolution (LTE) systems, 5th-generation (5G) systems, new radio (NR) systems, wireless local area networks (WLAN) systems, and future evolution systems, or a combination of multiple communication systems. The 5G system can be a non-standalone (NSA) 5G system or a standalone (SA) 5G system.

[0148] The network device in this application embodiment is an entity on the network side used to transmit signals, or receive signals, or both transmit and receive signals. The network device can be a device deployed in a radio access network (RAN) to provide wireless communication functions for terminals, such as a transmission reception point (TRP), a base station, or various forms of control nodes (e.g., network controllers, radio controllers (e.g., radio controllers in cloud radio access network (CRAN) scenarios)). Specifically, the network device can be various forms of macro base stations, micro base stations (also called small stations), relay stations, access points (APs), etc., or it can be the antenna panel of a base station. The control node can connect to multiple base stations and configure resources for multiple terminals covered by the multiple base stations. In systems employing different radio access technologies, the name of the device with base station functions may differ. For example, in an LTE system, it may be called an evolved NodeB (eNB or eNodeB), and in a 5G or NR system, it may be called a next-generation node base station (gNB). This application does not limit the specific name of the base station. Network equipment can also be network equipment in future evolved public land mobile networks (PLMNs), etc.

[0149] The terminal in this application embodiment is a user-side entity used to receive signals, or transmit signals, or both. The terminal is used to provide users with one or more of voice services and data connectivity services. The terminal can also be referred to as user equipment (UE), terminal equipment, access terminal, user unit, user station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication equipment, user agent, or user device. The terminal can be a V2X device, such as a smart car, digital car, unmanned car, driverless car, pilotless car, or automobile, self-driving car, or autonomous car, pure electric vehicle (EV), hybrid electric vehicle (HEV), range-extended electric vehicle (REEV), plug-in hybrid electric vehicle (PHEV), new energy vehicle, or roadside unit (RSU). The terminal can also be a D2D device, such as an electricity meter or water meter. Terminals can also be mobile stations (MS), subscriber units, drones, Internet of Things (IoT) devices, stations (ST) in WLANs, cellular phones, smartphones, cordless phones, wireless data cards, tablets, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistant (PDA) devices, laptop computers, machine type communication (MTC) terminals, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, and wearable devices (also known as wearable smart devices). Terminals can also be terminals in next-generation communication systems, such as terminals in 5G systems, terminals in future PLMNs, and terminals in NR systems.

[0150] The embodiments of this application are applicable to NR systems, but can also be applied to other systems, such as other future-oriented new systems, etc., and the embodiments of this application do not specifically limit them. In addition, the term "system" can be used interchangeably with "network".

[0151] like Figure 3 The diagram illustrates a communication system 30 provided in an embodiment of this application. The communication system 30 includes one or more user equipments 301. Different user equipments 301 can communicate with each other via SL.

[0152] For example, the first user equipment in this application embodiment can be one of any two user equipment 301 that communicate with each other, and the other can be the second user equipment in this application embodiment.

[0153] Optionally, the communication system also includes a network device 302. This network device 302 can communicate with the user equipment 301 via UL or DL. For example, in a broadcast scenario, a user equipment 301 can send relevant request information to the network device 302 to ensure that other terminal devices requiring discontinuous reception (DRX) can receive the broadcast signal. This embodiment does not specifically limit this aspect.

[0154] It should be noted that, Figure 3 This is merely a schematic diagram. Although not shown, the communication system 30 may also include other network devices, such as one or more of a core network device, a wireless relay device, and a wireless backhaul device. No specific limitations are made here. The network devices can connect to the core network device wirelessly or via a wired connection. The core network device and the network device 302 can be independent physical devices, or the functions of the core network device and the logical functions of the network device 302 can be integrated on the same physical device. Alternatively, a single physical device can integrate some of the functions of the core network device and some of the functions of the network device 302. This embodiment does not specifically limit these possibilities.

[0155] Optionally, the network device 302 in this embodiment is a device that connects the user equipment 301 to a wireless network. It can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a 5G mobile communication system, a base station in a future mobile communication system, or an access node in a wireless-fidelity (Wi-Fi) system; it can also be a module or unit that performs some of the functions of a base station, for example, a central unit (CU) or a distributed unit (DU). The embodiments of this application do not limit the specific technology or device form used in the network device. In this application, unless otherwise specified, network device refers to wireless access network device.

[0156] Optionally, the user equipment 301 in this embodiment can be a vehicle, an in-vehicle terminal installed on the vehicle to assist in vehicle operation, or a chip within the in-vehicle terminal. Alternatively, the user equipment 301 in this embodiment can be a device for implementing wireless communication functions, such as a terminal or a chip that can be used in a terminal. The aforementioned in-vehicle terminal or terminal can be a UE, access terminal, terminal unit, terminal station, mobile station, mobile station, remote station, remote terminal, mobile device, wireless communication device, terminal agent, or UE in a 5G network or a future evolved public land mobile network (PLMN). The access terminal can be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device or wearable device, virtual reality (VR) UE, augmented reality (AR) UE, wireless terminal in industrial control or self-driving, wireless terminal in remote medical care, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc. User equipment 301 can be fixed in location or mobile; this application embodiment does not specifically limit this.

[0157] Optionally, in this embodiment, the user equipment 301 includes a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, such as Linux, Unix, Android, iOS, or Windows. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. Furthermore, this embodiment does not specifically limit the specific structure of the execution entity of the method provided in this embodiment, as long as it can communicate according to the method provided in this embodiment by running a program that records the code of the method provided in this embodiment. For example, the execution entity of the method provided in this embodiment can be the user equipment 301, or a functional module in the user equipment 301 that can call and execute a program.

[0158] In other words, the relevant functions of the user equipment 301 in this application embodiment can be implemented by one device, multiple devices working together, or one or more functional modules within a single device. This application embodiment does not specifically limit this. It is understood that the above functions can be network elements in hardware devices, software functions running on dedicated hardware, a combination of hardware and software, or virtualization functions instantiated on a platform (e.g., a cloud platform).

[0159] For example, the relevant functions of the user equipment 301 in this embodiment of the application can be achieved through... Figure 4 The communication device 40 in the middle is used to achieve this. Figure 4 The diagram shown is a structural schematic of a communication device 40 provided in an embodiment of this application. The communication device 40 includes one or more processors 401, a communication line 402, and at least one communication interface. Figure 4 (This is merely an example illustration, using a communication interface 404 and a processor 401 as examples. Optionally, a memory 403 may also be included.)

[0160] Processor 401 may be a CPU, a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of programs according to the present application.

[0161] Communication line 402 may include a path for connecting different components.

[0162] The communication interface 404 can be a transceiver module used to communicate with other devices or communication networks, such as Ethernet, RAN, and wireless local area networks (WLAN). For example, the transceiver module can be a transceiver or similar device. Optionally, the communication interface 404 can also be a transceiver circuit located within the processor 401, used to implement the processor's signal input and signal output.

[0163] Memory 403 can be a device with storage function. For example, it can be read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions; random access memory (RAM) or other types of dynamic storage devices capable of storing information and instructions; electrically erasable programmable read-only memory (EEPROM); compact disc read-only memory (CD-ROM) or other optical disc storage; optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.); magnetic disk storage media or other magnetic storage devices; or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited to these. Memory can exist independently and be connected to the processor via communication line 402. Memory can also be integrated with the processor.

[0164] The memory 403 stores computer execution instructions for implementing the scheme of this application, and the processor 401 controls the execution. The processor 401 executes the computer execution instructions stored in the memory 403, thereby implementing the communication method provided in the embodiments of this application.

[0165] Alternatively, in this embodiment, the processor 401 may execute the processing-related functions in the communication method provided in the following embodiments of this application, and the communication interface 404 may be responsible for communicating with other devices or communication networks. This embodiment does not specifically limit this.

[0166] The computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.

[0167] In a specific implementation, as one example, processor 401 may include one or more CPUs, for example... Figure 4 CPU0 and CPU1 in the CPU.

[0168] In a specific implementation, as one example, the communication device 40 may include multiple processors, such as... Figure 4 Processors 401 and 407 are described herein. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor here may refer to one or more devices, circuits, and / or processing cores used to process data (e.g., computer program instructions).

[0169] In a specific implementation, as one embodiment, the communication device 40 may further include an output device 405 and an input device 406. The output device 405 communicates with the processor 401 and can display information in various ways.

[0170] The aforementioned communication device 40 can be a general-purpose device or a special-purpose device. For example, the communication device 40 can be a desktop computer, a portable computer, a network server, a handheld digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, a vehicle-mounted terminal device, an embedded device, or a device with... Figure 4 Devices with similar structures. This application does not limit the type of communication device 40 to any particular embodiment.

[0171] by Figure 3 Taking user equipment 301 as an example, which is a mobile terminal, Figure 5 A schematic diagram of the structure of the mobile terminal 50 is shown.

[0172] like Figure 5 As shown, the mobile terminal 50 may include a processor 510, an external memory interface 520, an internal memory 521, a USB interface 530, a mobile communication module 540, a wireless communication module 550, an audio module 560, a sensor module 570, a camera 580, and a display screen 581, etc.

[0173] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the mobile terminal 50. In other embodiments of this application, the mobile terminal 50 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0174] In this embodiment, the processor 510 may include one or more processing units, such as an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU). These different processing units may be independent devices or integrated into one or more processors.

[0175] In addition, the processor 510 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 510 is a cache memory. This memory can store instructions or data that the processor 510 has just used or that are used repeatedly. If the processor 510 needs to use the instruction or data again, it can directly retrieve it from the memory. This avoids repeated accesses, reduces the waiting time of the processor 510, and thus improves the efficiency of the system.

[0176] In this embodiment, the wireless communication function of the mobile terminal 50 can be implemented through antenna 1, antenna 2, mobile communication module 540, wireless communication module 550, modem processor, and baseband processor.

[0177] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals.

[0178] The mobile communication module 540 can provide solutions for wireless communication, including second-generation (2G), third-generation (3G), fourth-generation (4G), and fifth-generation (5G), applied to the mobile terminal 50. In some embodiments, at least some functional modules of the mobile communication module 540 can be housed in the processor 510. In some embodiments, at least some functional modules of the mobile communication module 540 and at least some modules of the processor 510 can be housed in the same device.

[0179] The wireless communication module 550 can provide wireless communication solutions for mobile terminal 50, including WLAN (such as Bluetooth, WiFi), global navigation satellite system (GNSS), near field communication (NFC), infrared (IR) technology, or frequency modulation (FM).

[0180] In some embodiments, the antenna 1 of the mobile terminal 50 is coupled to the mobile communication module 540, and the antenna 2 is coupled to the wireless communication module 550, so that the mobile terminal 50 can communicate with the network and other devices through wireless communication technology.

[0181] In this embodiment, the mobile terminal 50 implements display functions through a GPU, a display screen 581, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 581 and the application processor. The GPU performs mathematical and geometric calculations and is used for graphics rendering. The processor 510 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0182] The display screen 581 is used to display images or videos, etc. The display screen 581 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a minimized LED, a microLED, a micro-LED, or a quantum dot light-emitting diode (QLED), etc. In some embodiments, the mobile terminal 50 may include one or N displays 581, where N is a positive integer greater than 1.

[0183] In this embodiment, the mobile terminal 50 can implement the shooting function through an ISP, a camera 580, a video codec, a GPU, a display screen 581, and an application processor.

[0184] Camera 580 is used to capture still images or videos. An object is projected onto a photosensitive element by generating an optical image through the lens. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then passed to an ISP for conversion into a digital image signal. The ISP outputs the digital image signal to a DSP for processing. The DSP converts the digital image signal into image signals in standard RGB, YUV, or other formats. In some embodiments, the mobile terminal 50 may include one or N cameras 580, where N is a positive integer greater than 1.

[0185] In this embodiment, the external memory interface 520 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the mobile terminal 50. The external memory card communicates with the processor 510 through the external memory interface 520 to perform data storage functions. For example, music, video, and other files can be stored on the external memory card.

[0186] In this embodiment, the internal memory 521 can be used to store computer executable program code, which includes instructions. The internal memory 521 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.). The data storage area may store data created during the use of the mobile terminal 50 (such as audio data, phonebook, etc.). Furthermore, the internal memory 521 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. The processor 510 executes various functional applications and data processing of the mobile terminal 50 by running instructions stored in the internal memory 521 and / or instructions stored in memory located in the processor.

[0187] In this embodiment, the sensor module 570 may include an accelerometer, a gyroscope, a GPS sensor, and a touch sensor, etc.

[0188] Of course, the mobile terminal 50 may also include a charging management module, a power management module, a battery, buttons, indicators, and one or more subscriber identity module (SIM) card interfaces, etc., and this application embodiment does not impose any restrictions on this.

[0189] In existing technologies, when the time for the transmitter to receive the PSFCH conflicts with the time for the transmitter to send or receive other information, if the priority of sending or receiving other information is higher than the priority of receiving the PSFCH, the transmitter will execute the sending or receiving of other information, thus failing to receive the PSFCH. Clearly, this is not due to a problem with the wireless link causing the transmitter to fail to receive the PSFCH. However, since the transmitter also fails to receive the PSFCH in this situation, it will still increment the counter value by 1, which may cause the counter value to reach a preset threshold. This could lead to the transmitter falsely triggering RLF, affecting communication quality and causing communication delays.

[0190] Understandably, according to the existing protocol, if an RLF is accidentally triggered, the sender and receiver may need some time to restore / rebuild the connection (e.g., unicast connection) before they can continue to communicate normally. It is understandable that accidentally triggering an RLF will cause some communication delay and affect the quality of communication.

[0191] The following example uses any two user devices 301 communicating with each other as the first user device. Figures 1 to 5 The communication method provided in the embodiments of this application will be described in detail.

[0192] It should be understood that the method embodiments described below only use the first user equipment and the second user equipment as examples of the executing entities, but are not limited to the first user equipment and the second user equipment. The first user equipment and the second user equipment can be replaced by any device that can implement the method in this application. For example, the first user equipment can also be replaced by a chip or a first device configured in the first user equipment, and the second user equipment can also be replaced by a chip or a second device configured in the second user equipment.

[0193] like Figure 6a The image shows a communication method provided in an embodiment of this application. The communication method includes the following steps:

[0194] S601, The first user equipment sends the first data to the second user equipment via SL.

[0195] Optionally, step S601 may include / be replaced by: for a unicast connection, the first user equipment sends first data to the second user equipment via SL.

[0196] For example, the first data can be SL data.

[0197] Optionally, step S601 can be replaced by: the first user equipment sending first control information to the second user equipment via SL, or the first user equipment sending first control information and first data to the second user equipment via SL.

[0198] The first control information is used to schedule the first data.

[0199] For example, the first control information can be SCI, or Level 1 SCI.

[0200] It is understandable that the first user equipment may send only the first control information to the second user equipment via SL, or it may send both the first control information and the first data to the second user equipment. For example, the first user equipment may send the first control information to the second user equipment via SL, but may fail to send the first data for some reason (e.g., due to a conflict between the transmission of the first data and other transmissions).

[0201] It should be noted that the solution in this application can also be applied to other scenarios / systems besides SL. The phrase "via SL" in step S601 can be deleted (i.e., the link for sending the first data and / or the first control information is not limited), and the first user equipment and the second user equipment can be replaced with the first device and the second device.

[0202] After step S601, the first user equipment may perform any one or more of the following steps S602, S603, and S604.

[0203] S602. If the first user equipment does not receive the first feedback information, the first user equipment initializes the first counter, or the count value of the first counter remains unchanged.

[0204] Optionally, step S602 may include / be replaced by: for a unicast connection, if the first user equipment does not receive the first feedback information, the first user equipment initializes the first counter, or the count value of the first counter remains unchanged.

[0205] The first feedback information can indicate whether the second user equipment has successfully received the first data.

[0206] The first counter can be used for RLF detection.

[0207] It should be noted that the first counter can be the same as or different from the counter used for RLF detection in existing protocols (e.g., numConsecutiveDTX). For example, the first counter is numConsecutiveDTX.

[0208] Optionally, one or more of the first data, first control information, first feedback information, first feedback resource, first counter, first indication information, PSFCH listening timing, and RLF are associated with a unicast connection (e.g., a unicast connection, or the first unicast connection) and / or the RRC connection of the SL (e.g., an RRC connection of the SL, or the RRC connection of the first SL).

[0209] Optionally, it is understood that the communication method provided in the embodiments of this application may be executed for a unicast connection (e.g., a unicast connection), or the communication method provided in the embodiments of this application may be executed for SL processes associated with a unicast connection (e.g., all SL processes).

[0210] In the embodiments of this application, "receive" and "received" have different meanings. Specifically, "receive" refers to performing the action of receiving, and the result of "receiving" may be "received" or "not received"; "not received" refers to not performing the action of receiving, and the result of "not received" is "not received". That is to say, "not received" includes two situations: one is that the action of receiving was performed but no data was received, and the other is that the action of receiving was not performed. This is explained uniformly here and will not be repeated below.

[0211] Optionally, the first feedback information is transmitted on a first feedback resource. For example, the first feedback resource can be a PSFCH resource.

[0212] For example, the first feedback information in the embodiments of this application can be ACK / NACK information.

[0213] For example, the first feedback message is ACK, indicating that the second user equipment has successfully received the first data.

[0214] For example, the first feedback message is NACK, indicating that the second user equipment has not successfully received the first data.

[0215] Optionally, the first feedback information can also be replaced with PSFCH in its wording.

[0216] In one possible implementation, initializing the first counter by the first user equipment includes: initializing the count value of the first counter to 0 or a first value. In this implementation, the initial value of the first counter is 0 or the first value, and the count value that triggers the RLF is a preset threshold (e.g., a third threshold). It is understood that the RLF will be triggered when the count value of the first counter reaches (or is greater than or equal to) the preset threshold (e.g., the third threshold).

[0217] For example, the first value can be an integer. For instance, the first value can be 1, etc., and this application is not limited to this.

[0218] It should be noted that the third threshold can be the same as or different from the threshold used for RLF detection in existing protocols (e.g., sl-maxNumConsecutiveDTX). For example, the third threshold can be sl-maxNumConsecutiveDTX.

[0219] In another possible implementation, the first user equipment may also initialize the count value of the first counter to a preset threshold (e.g., a third threshold). In this implementation, the initial value of the first counter is the preset threshold (e.g., the third threshold), and the count value that triggers the RLF is 0 or a first value. It is understood that the count value of the first counter reaching (or being less than or equal to) 0 or the first value will / will trigger the RLF.

[0220] Optionally, keeping the count value of the first counter unchanged may include / be replaced by: the first user equipment determining that the count value of the first counter remains unchanged, or the count value of the first counter remains unchanged.

[0221] In the communication method provided in this application embodiment, if the first user equipment does not receive the first feedback information, the first user equipment initializes the first counter, or the count value of the first counter remains unchanged. The first user equipment fails to receive the first feedback information because it does not receive it, and not because of a problem with the wireless link (e.g., SL). The first counter does not count cases where the first user equipment fails to receive the first feedback information, thus preventing the count value of the first counter from reaching the trigger value for RLF incorrectly / prematurely / too quickly, thereby reducing the probability of erroneous RLF triggering, and further reducing communication latency and improving / guaranteeing communication quality or reliability.

[0222] S603, if the first user equipment receives first feedback information, or if the first user equipment does not receive first feedback information, the first user equipment increments or decrements the count value of the first counter by 1. In this method, the first user equipment receiving but not receiving the first feedback information may be due to a problem with the wireless link (e.g., SL). The first counter records the cases where the first user equipment receives but does not receive the first feedback information.

[0223] Optionally, step S603 may include / be replaced by: for a unicast connection, if the first user equipment receives first feedback information and the first user equipment does not receive the first feedback information, the first user equipment increments or decrements the count value of the first counter by 1.

[0224] It should be noted that when the initial value of the first counter is 0 or the first value, and the count value that triggers the RLF is a preset threshold (e.g., the third threshold), the first user equipment receives the first feedback information. If the first user equipment does not receive the first feedback information, the first user equipment increments the count value of the first counter by 1.

[0225] It should be noted that when the initial value of the first counter is a preset threshold (e.g., a third threshold), and the count value of the trigger RLF is 0 or a first value, the first user equipment receives the first feedback information. If the first user equipment does not receive the first feedback information, the first user equipment decrements the count value of the first counter by 1.

[0226] Compared to existing technologies, this method adds conditional restrictions on the increase or decrease of the count value of the first counter. Therefore, it can avoid the count value of the first counter from reaching the count value that triggers the RLF incorrectly / prematurely / too quickly, thereby avoiding false triggering of the RLF. This can also reduce communication latency and improve / guarantee the quality or reliability of communication.

[0227] It should be noted that the count value of the first counter can increase or decrease by 1, that is, the granularity / step size of the change in the count value of the first counter can be 1. Alternatively, the count value of the first counter can also increase or decrease by a, where a is a positive integer, that is, the granularity / step size of the change in the count value of the first counter can also be a, and this application does not impose any limitation on this. It is understood that the first user equipment increasing or decreasing the count value of the first counter by 1 can be replaced by: the first user equipment increasing or decreasing the count value of the first counter by a.

[0228] S604. The first user equipment receives the first feedback information and initializes the first counter.

[0229] Optionally, step S604 may include / be replaced by: for a unicast connection, the first user equipment receives first feedback information and initializes the first user equipment's first counter.

[0230] Optionally, this application further includes: when the count value of the first counter reaches (or is greater than or equal to) a third threshold, or when the count value of the first counter reaches (or is less than or equal to) 0 or a first value, the first user equipment performs any one or more of the following: the first user equipment triggers / detects an RLF, the MAC layer (or MAC entity, or HARQ entity, or SL HARQ entity) of the first user equipment indicates to the upper layer (e.g., RRC layer) of the first user equipment that an RLF has been detected, and the first user equipment sends a first indication message to the network device.

[0231] Optionally, the first user equipment triggering / detecting an RLF may include / be replaced with: the first user equipment determining that an RLF has been triggered / detected.

[0232] The first indication information is used to indicate that the first user equipment has detected an RLF, or to indicate that an RLF has occurred, or to indicate that the reason for the SL failure is an RLF.

[0233] For example, the first indication information is used to indicate that: for the first unicast connection or the first SL's RRC connection, the first user equipment detected an RLF, or, an RLF occurred, or, the reason for the SL failure was an RLF.

[0234] For example, the first indication information may be included in the sidelink UE information (SUI), and this application does not limit it in any way.

[0235] Understandably, the first user equipment triggers an RLF and reports it to the network device to indicate that there is an anomaly or failure of the radio link (e.g., SL).

[0236] Optionally, this application may also include: unicast connection establishment, or, the third threshold / first value being configured or reconfigured, the first user equipment initializing the first counter.

[0237] Optionally, the first user equipment not receiving the first feedback information includes: the reception of the first feedback information conflicted with the first transmission, and the first user equipment did not receive the first feedback information.

[0238] In this method, the first counter used for RLF detection does not count resource conflicts / transmission conflicts. This allows the first counter to exclude other possible reasons why the first user equipment may not receive the first feedback information. It focuses on counting the number of times the first user equipment has not received the first feedback information due to problems with the wireless link (e.g., SL). This further avoids the count value of the first counter from reaching the count value that triggers RLF incorrectly / prematurely / too quickly, thereby avoiding false triggering of RLF. This can also reduce communication latency and improve / guarantee the quality or reliability of communication.

[0239] In this embodiment of the application, the first transmission is a different transmission from the reception of the first feedback information.

[0240] The first transmission may include a first sending and / or a first receiving.

[0241] For example, the first transmission can be a PSFCH transmission, a UL transmission, or an LTE SL transmission.

[0242] Optionally, if the reception of the first feedback information conflicts with the first transmission, and the first user equipment does not receive the first feedback information, the following are possible scenarios: the reception of the first feedback information conflicts with the first transmission, and the priority of receiving the first feedback information is lower than or equal to the priority of the first transmission, and the first user equipment does not receive the first feedback information; or, the reception of the first feedback information conflicts with the first transmission, and the priority of receiving the first feedback information is lower than or equal to the priority of the first transmission.

[0243] Optionally, the fact that the priority of receiving the first feedback information is lower than or equal to the priority of the first transmission can be understood / replaced as: the reception of the first feedback information is not given priority.

[0244] Optionally, the priority of receiving the first feedback information being lower than or equal to the priority of the first transmission may include: the first user equipment determining that the priority of receiving the first feedback information is lower than or equal to the priority of the first transmission.

[0245] Optionally, the fact that the reception of the first feedback information was not prioritized may include: the first user equipment determining that the reception of the first feedback information was not prioritized.

[0246] In this method, if a resource conflict / transmission conflict occurs, and the reception of the first feedback information has a low priority, the first user equipment executes the higher-priority first transmission instead of receiving the first feedback information, resulting in the first feedback information not being received. This is not due to a problem with the wireless link. The first counter does not count cases where the first feedback information is not received due to the first user equipment not receiving it, thus preventing the first counter's count value from reaching the trigger value for RLF incorrectly / prematurely / too quickly, thereby avoiding false triggering of RLF. This can also reduce communication latency and improve / guarantee communication quality or reliability.

[0247] In the embodiments of this application, the definition of the priority of receiving or transmitting, and the comparison of priorities, are detailed in the preamble of the specification regarding conflicts between PSFCH reception and other transmissions / receivers, and will not be repeated here.

[0248] For example, combined Figure 2 , Figure 7 The existing protocol and the communication method provided in the embodiments of this application are illustrated for the RLF detection process. In both the first counter and the counter in the existing protocol, the initial value is 0, and the count value for triggering the RLF is 3. For details of the existing protocol for RLF detection, please refer to [link to documentation]. Figure 2 The content described above will not be repeated here. The following will describe the process of using the communication method provided in the embodiments of this application for RLF detection.

[0249] During the first PSFCH listening opportunity, the sending UE did not receive the PSFCH because the reception of the PSFCH conflicted with other transmissions and was not given priority. The count value of the first counter remained unchanged, still at the initial value of 0.

[0250] During the second PSFCH listening opportunity, the sending UE attempts to receive the PSFCH, but fails to actually receive it. The first counter increments by 1, becoming 1.

[0251] During the third PSFCH listening session, the sending UE receives the PSFCH. The first counter is initialized to 0.

[0252] During the fourth PSFCH listening opportunity, the sending UE attempts to receive the PSFCH, but fails to actually receive it. The first counter increments by 1, becoming 1.

[0253] During the 5th PSFCH listening time, the sending UE attempts to receive the PSFCH, but fails to actually receive it. The first counter increments by 1, becoming 2.

[0254] During the sixth PSFCH listening opportunity, the sending UE did not receive the PSFCH because the reception of the PSFCH conflicted with other transmissions and was not given priority. The count value of the first counter remained unchanged at 2.

[0255] At the 7th PSFCH listening time, the sending UE receives the PSFCH. The first counter is initialized to 0.

[0256] During the 8th PSFCH listening opportunity, the sending UE did not receive the PSFCH because the reception of the PSFCH conflicted with other transmissions and was not given priority. The count value of the first counter remained unchanged at 0.

[0257] During the 9th PSFCH listening opportunity, the sending UE did not receive the PSFCH because the reception of the PSFCH conflicted with other transmissions and was not given priority. The count value of the first counter remained unchanged at 0.

[0258] At the 10th PSFCH listening time, the transmitting UE receives the PSFCH. The first counter is initialized to 0.

[0259] At the 11th PSFCH listening time, the transmitting UE receives the PSFCH. The count value of the first counter remains unchanged at 0, or in other words, the first counter is initialized to 0.

[0260] Understandable Figure 7The diagram only shows the PSFCH listening timing associated with the first unicast connection or the RRC connection of the first SL. PSFCH reception associated with other unicast connections or multicast communications is not relevant to this scheme and is not shown in the diagram.

[0261] It should be noted that, Figure 7 The diagram only schematically illustrates 11 PSFCH listening opportunities. In reality, the PSFCH listening opportunities may be continuous or discontinuous in the time domain, and different PSFCH listening opportunities may also overlap in the time domain. This application does not impose any limitations on this.

[0262] Based on the above analysis, compared with the prior art, the first user equipment in the communication method provided in this application embodiment will not erroneously trigger RLF during the sixth PSFCH listening time, thereby reducing communication latency and improving / guaranteeing communication quality or reliability.

[0263] In one possible implementation (implementation 1), this application further includes: the signal quality between the first user equipment and the second user equipment is greater than or equal to a first threshold, and after executing step S601, the first user equipment executes any one or more of steps S602, S603, and S604.

[0264] Optionally, the signal quality between the first user equipment and the second user equipment being greater than or equal to the first threshold may include: the first user equipment determining / judging that the signal quality between the first user equipment and the second user equipment is greater than or equal to the first threshold.

[0265] It should be noted that the order of "the first user equipment determines / judges that the signal quality between the first user equipment and the second user equipment is greater than or equal to the first threshold" and step S601 is not limited in this application.

[0266] For example, a signal quality between the first user equipment and the second user equipment that is greater than or equal to a first threshold can be understood as a signal quality between the first user equipment and the second user equipment being relatively good.

[0267] It is understandable that when the signal quality is good, it indicates that the wireless link is normal. The first counter used for RLF detection does not count the cases where the first user equipment does not receive the first feedback information, thus avoiding false triggering of RLF. This can also reduce communication latency and improve / guarantee the quality or reliability of communication.

[0268] In the embodiments of this application, the determination of the signal quality between the first user equipment and the second user equipment can be based on reference signal received power (RSRP), reference signal received quality (RSRQ), channel state information (CSI), SL-CSI, or sounding reference signal (SRS), etc., and this application does not impose any limitations on this. In another possible implementation (implementation 2), this application further includes: the signal quality between the first user equipment and the second user equipment is less than or equal to a second threshold, such as... Figure 6b As shown, after executing step S601, the first user equipment executes steps S605 and / or S606.

[0269] Optionally, the signal quality between the first user equipment and the second user equipment being less than or equal to the second threshold may include: the first user equipment determining / judging that the signal quality between the first user equipment and the second user equipment is less than or equal to the second threshold.

[0270] It should be noted that the order of "the first user equipment determines / judges that the signal quality between the first user equipment and the second user equipment is less than or equal to the second threshold" and step S601 is not limited in this application.

[0271] For example, if the signal quality between the first user equipment and the second user equipment is less than or equal to the second threshold, it can be understood as the signal quality between the first user equipment and the second user equipment being poor.

[0272] S605. If the first user equipment does not receive the first feedback information, the first user equipment increments the count value of the first counter by 1.

[0273] Optionally, step S605 may include / be replaced by: for a unicast connection, if the first user equipment does not receive the first feedback information, the first user equipment increments the count value of the first counter by 1.

[0274] The first user equipment not receiving the first feedback information includes: the first user equipment not receiving the first feedback information, and / or, the first user equipment receiving the first feedback information, and the first user equipment not receiving the first feedback information.

[0275] S606. The first user equipment receives the first feedback information and initializes the first counter, or the count value of the first counter remains unchanged.

[0276] Optionally, step S606 may include / be replaced by: for a unicast connection, the first user equipment receives the first feedback information, the first user equipment initializes the first counter, or the count value of the first counter remains unchanged.

[0277] Understandably, poor signal quality indicates a potential anomaly in the wireless link. In this situation, the first counter used for RLF detection counts cases where the first user equipment fails to receive the first feedback information, thus triggering the RLF more quickly. Furthermore, this allows for the rapid restoration / reconstruction of the unicast connection, reducing communication latency.

[0278] It should be noted that the first threshold and the second threshold can be the same or different, and this application does not limit this.

[0279] It should be noted that implementation method 1 and implementation method 2 can be used as separate embodiments (or implementation method 2 can be independent of implementation method 1, or implementation method 2 can be independent of steps S602, S603, and S604), or implementation method 1 and implementation method 2 can be combined with each other (or any one or more of steps S602, S603, and S604 can be combined with steps S605 and / or S606), and the present invention does not limit this.

[0280] like Figure 8 As shown, another communication method provided in this application embodiment includes the following steps:

[0281] S801, The first user equipment sends the first data to the second user equipment via SL.

[0282] The description of step S801 can be found in the relevant description of step S601, and will not be repeated here.

[0283] After step S801, the first user equipment may execute steps S802 and / or S803.

[0284] S802, if the first user equipment does not receive the first feedback information, the first user equipment will increment or decrement the count value of the second counter by 1.

[0285] The first feedback information indicates whether the second user equipment has successfully received the first data.

[0286] For details regarding the first feedback information, please refer to the relevant description in the embodiment shown in Figure 6, which will not be repeated here.

[0287] The second counter is used to count the number of times the first user equipment has not received feedback information consecutively.

[0288] Optionally, step 801 may include / be replaced by: for a unicast connection, if the first user equipment does not receive the first feedback information, the first user equipment increments or decrements the count value of the second counter by 1.

[0289] Optionally, one or more of the first data, first control information, first feedback information, first feedback resource, feedback information, second counter, second indication information, third indication information, and PSFCH listening timing are associated with a unicast connection (e.g., a unicast connection, or the first unicast connection) and / or the RRC connection of the SL (e.g., an RRC connection of the SL, or the RRC connection of the first SL).

[0290] Optionally, it is understood that the communication method provided in the embodiments of this application may be executed for a unicast connection (e.g., a unicast connection), or the communication method provided in the embodiments of this application may be executed for SL processes associated with a unicast connection (e.g., all SL processes).

[0291] It should be noted that the count value of the second counter can increase or decrease by 1, that is, the granularity / step size of the change in the count value of the second counter can be 1. Alternatively, the count value of the second counter can also increase or decrease by b, where b is a positive integer, that is, the granularity / step size of the change in the count value of the second counter can also be b, and this application does not impose any limitation on this. It is understood that the first user equipment increasing or decreasing the count value of the second counter by 1 can be replaced by: the first user equipment increasing or decreasing the count value of the second counter by b.

[0292] It should be noted that the second counter can be used alone, or the second counter can be used simultaneously with the first counter provided in the embodiments of this application, or the second counter can be used in conjunction with... Figure 2 The counters shown in the existing protocols are used simultaneously, and this application does not impose any limitations on them.

[0293] S803, the first user equipment receives the first feedback information and initializes the second counter.

[0294] Optionally, step 802 may include / be replaced by: for a unicast connection, the first user equipment receives first feedback information and initializes the second counter.

[0295] In one possible implementation, initializing the second counter by the first user equipment includes: initializing the count value of the second counter to 0 or a second value. In this implementation, the initial value of the second counter is 0 or the second value, and the count value for triggering RLF, triggering the transmission of second and / or third indication information, or triggering resource reselection is a preset threshold (e.g., a fourth threshold). It is understood that the count value of the second counter reaching (or being greater than or equal to) the preset threshold (e.g., the fourth threshold) will / will trigger RLF, trigger the transmission of second and / or third indication information, or trigger resource reselection.

[0296] For example, the second value can be an integer. For instance, the second value can be 1, etc., and this application is not limited to this.

[0297] For example, resource reselection may include SL resource reselection.

[0298] In another possible implementation, the first user equipment may also initialize the count value of the second counter to a preset threshold (e.g., a fourth threshold). In this implementation, the initial value of the second counter is the preset threshold (e.g., the fourth threshold), and the count value is 0 or a second value when any one or more of the following are triggered: RLF, transmission of the second indication information and / or the third indication information, or resource reselection. It is understood that the count value of the second counter reaching (or being less than or equal to) 0 or the second value will / will trigger RLF, transmission of the second indication information and / or the third indication information, or resource reselection.

[0299] It should be noted that when the initial value of the second counter is 0 or the second value, and the count value of any one or more of the triggering RLF, triggering the sending of the second indication information and / or the third indication information, or triggering resource reselection is a preset threshold (e.g., the fourth threshold), the first user equipment receives the first feedback information, and if the first user equipment does not receive the first feedback information, the first user equipment increments the count value of the second counter by 1.

[0300] It should be noted that when the initial value of the second counter is a preset threshold (e.g., the fourth threshold), and the count value of any one or more of triggering RLF, triggering the sending of the second indication information and / or the third indication information, or triggering resource reselection is 0 or the second value, the first user equipment receives the first feedback information, and if the first user equipment does not receive the first feedback information, the first user equipment decrements the count value of the second counter by 1.

[0301] Optionally, this application also includes: unicast connection establishment, or, the fourth threshold / second value being configured or reconfigured, the first user equipment initializing the second counter.

[0302] Optionally, this application further includes: when the count value of the second counter reaches (or is greater than or equal to) a fourth threshold, or when the count value of the second counter reaches (or is less than or equal to) 0 or a second value, the first user equipment performs any one or more of the following: the first user equipment triggers / detects an RLF, the MAC layer (or MAC entity, or HARQ entity, or SL HARQ entity) of the first user equipment indicates to the upper layer (e.g., RRC layer) of the first user equipment that an RLF has been detected, the first user equipment sends a second indication information and / or a third indication information to the network device, or the first user equipment triggers resource reselection.

[0303] Optionally, the first user equipment triggering / detecting an RLF may include / be replaced with: the first user equipment determining that an RLF has been triggered / detected.

[0304] The second indication information is used to indicate that the first user equipment has detected an RLF, or to indicate that an RLF has occurred, or to indicate that the reason for the SL failure is an RLF.

[0305] The third indication information is used to indicate that the count value of the second counter reaches (or is greater than or equal to) the fourth threshold or the count value of the second counter reaches (or is less than or equal to) 0 or the second value, or to indicate that the number of times the first user equipment has not received feedback information for a consecutive period of time has reached a preset threshold (e.g., the fourth threshold), or to indicate that the number of times the reception of feedback information and other transmissions have continuously conflicted has reached a preset threshold (e.g., the fourth threshold).

[0306] For example, the second indication information is used to indicate that: for the first unicast connection or the RRC connection of the first SL, the first user equipment detected an RLF, or, an RLF occurred, or, the reason for the SL failure was an RLF.

[0307] For example, the third indication information is used to indicate that: for the first unicast connection or the RRC connection of the first SL, the count value of the second counter reaches (or is greater than or equal to) the fourth threshold or the count value of the second counter reaches (or is less than or equal to) 0 or the second value, or the number of times the first user equipment has not received feedback information for a consecutive period reaches a preset threshold (e.g., the fourth threshold), or the number of times the reception of feedback information and other transmissions have consecutive conflicts reaches a preset threshold (e.g., the fourth threshold).

[0308] It should be noted that the second instruction information may be the same as or different from the first instruction information; this application does not limit this.

[0309] Optionally, the second indication information can also be used to indicate the reason for triggering / detecting an RLF. For example, the reason may include the number of times the first user equipment has not received feedback information consecutively reaching a preset threshold (e.g., a fourth threshold), or the number of times the reception of feedback information and other transmissions have continuously conflicted reaching a preset threshold (e.g., a fourth threshold), or the count value of the second counter reaching (or being greater than or equal to) the fourth threshold or the count value of the second counter reaching (or being less than or equal to) 0 or a second value.

[0310] For example, the second indication information and / or the third indication information may be included in the sidelink UE information (SUI), and this application does not limit this in any way.

[0311] In another communication method provided in the embodiments of this application, the first user equipment can report second indication information (e.g., the reason for triggering / detecting RLF) and / or third indication information to the network device, indicating to the network that the probability of resource conflict / transmission conflict is currently high (or, indicating to the network that the number of resource conflict / transmission conflict has reached a certain threshold). Thus, the network device can adjust certain parameters accordingly to reduce the probability of resource conflict / transmission conflict, which is beneficial to improving communication quality, reducing communication latency, and ensuring communication reliability.

[0312] In another communication method provided in the embodiments of this application, when the first user equipment triggers / detects an RLF, it can take corresponding strategies, such as restoring or rebuilding the unicast connection, which is beneficial to improving communication quality, reducing communication latency, and ensuring communication reliability.

[0313] In another communication method provided in the embodiments of this application, the first user equipment triggers resource reselection, which allows the first user equipment to reselect resources, thereby reducing the probability of resource conflicts / transmission conflicts, improving communication quality, reducing communication latency, and ensuring communication reliability.

[0314] It should be noted that in this application, different embodiments can be combined with each other, and there can be a combination of some contents / steps in different embodiments or a combination of all contents in different embodiments.

[0315] It should be noted that, in this application, for the sake of simplicity, the same terms / content are not explained repeatedly in different embodiments. Unless otherwise specified, they are generally applicable in different embodiments.

[0316] Wherein, since the first user equipment in the above embodiments can adopt such Figure 4 The architecture of the communication device 40 shown indicates that the operation of the first user equipment in the above embodiment can be achieved by... Figure 4 The processor 401 in the communication device 40 shown calls the application code stored in the memory 403 to instruct the first user equipment to execute it; this embodiment does not impose any limitations on this.

[0317] Alternatively, the actions of the first user equipment in steps S601-S602 and S801-S802 can be performed by... Figure 5 The processor 510 in the mobile terminal 50 shown calls application code stored in memory (including internal memory 521 or external memory connected to external memory interface 520) to instruct the mobile terminal to execute. This embodiment does not impose any limitations on this.

[0318] It is understood that the methods and / or steps implemented by the first user equipment in the above embodiments can also be implemented by components (e.g., chips or circuits) that can be used in the first user equipment.

[0319] The above description primarily focuses on the solutions provided by the embodiments of this application from the perspective of a first user equipment. Correspondingly, the embodiments of this application also provide a communication device for implementing the various methods described above. This communication device can be the first user equipment in the above method embodiments, or a device containing the first user equipment, or a component usable by the first user equipment. It is understood that, in order to achieve the above functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0320] This application embodiment can divide the communication device into functional modules according to the above method embodiment. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0321] Figure 9A schematic diagram of a communication device 90 is shown. The communication device 90 includes a transceiver module 901 and a processing module 902. The transceiver module 901, also known as a transceiver unit, is used to implement transceiver functions, and may be, for example, a transceiver circuit, a transceiver, a transceiver device, or a communication interface.

[0322] Taking the communication device 90 as an example of the first user equipment in the above method embodiment, the transceiver module 901 is used to send first data to the second user equipment through the side link SL. The processing module 902 is used to initialize the first counter if the first feedback information is not received, or to leave the count value of the first counter unchanged. The first feedback information indicates whether the second user equipment has successfully received the first data; the first counter is used for RLF detection.

[0323] In one possible implementation, the transceiver module 901 is further configured to receive first feedback information. The processing module 902 is further configured to increment the count value of the first counter by 1 if the first feedback information is not received.

[0324] In one possible implementation, not receiving the first feedback information includes: if the reception of the first feedback information conflicts with the first transmission, the first feedback information is not received.

[0325] In one possible implementation, not receiving the first feedback information includes: if the reception of the first feedback information conflicts with the first transmission, and the priority of receiving the first feedback information is lower than or equal to the priority of the first transmission, then the first feedback information is not received.

[0326] In one possible implementation, the processing module 902 is used to initialize the first counter by: initializing the count value of the first counter to 0.

[0327] In one possible implementation, the processing module 902 is further configured to increment the count value of the first counter by 1 if the signal quality between the first user equipment and the second user equipment is less than or equal to a second threshold and no first feedback information is received.

[0328] In one possible implementation, the transceiver module 901 is further configured to send first indication information to the network device when the count value of the first counter is greater than or equal to a third threshold. The first indication information is used to indicate that the first user equipment has detected an RLF.

[0329] All relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0330] In this embodiment, the communication device 90 is presented in an integrated manner, divided into various functional modules. Here, "module" can refer to a specific ASIC, circuit, processor and memory executing one or more software or firmware programs, integrated logic circuits, and / or other devices that can provide the above-mentioned functions.

[0331] When the communication device 90 is the first user equipment in the above method embodiments, in a simple embodiment, those skilled in the art will realize that the communication device 90 can adopt... Figure 4 As shown in the figure.

[0332] for example, Figure 4 The processor 401 or 407 in the first user equipment shown can execute the communication method in the above method embodiment by calling computer execution instructions stored in memory 403. Specifically, Figure 9 The functions / implementation process of the transceiver module 901 and the processing module 902 can be obtained through... Figure 4 The processor 401 or 407 in the first user equipment shown calls computer execution instructions stored in memory to implement this. Alternatively, Figure 9 The function / implementation process of the processing module 902 can be achieved through... Figure 4 The processor 401 or 407 in the first user equipment shown implements this by calling computer execution instructions stored in memory. Figure 9 The function / implementation process of the transceiver module 901 can be obtained through Figure 4 The communication interface 404 shown is used to implement this.

[0333] Alternatively, when the communication device 90 is the first user equipment in the above method embodiments, and the first user equipment is a mobile terminal, in a simple embodiment, those skilled in the art will realize that the communication device 90 can adopt... Figure 5 The mobile terminal 50 shown is in the form of [example device].

[0334] for example, Figure 5 The processor 510 in the mobile terminal 50 shown can execute the communication method in the above-described method embodiment by calling computer execution instructions stored in the memory (including internal memory 521 or external memory connected to external memory interface 520). Specifically, Figure 9 The functions / implementation process of the transceiver module 901 and the processing module 902 can be obtained through... Figure 5 The processor 510 in the mobile terminal 50 shown calls computer execution instructions stored in memory to implement this. Alternatively, Figure 9 The function / implementation process of the processing module 902 can be achieved through... Figure 5The processor 510 in the mobile terminal 50 shown calls computer execution instructions stored in the memory to implement this. Figure 9 The function / implementation process of the transceiver module 901 can be obtained through Figure 5 This is achieved using the wireless communication module 550 shown.

[0335] Since the communication device 90 provided in this embodiment can execute the above-described communication method, the technical effects it can achieve can be referred to the above-described method embodiments, and will not be repeated here.

[0336] It should be noted that one or more of the above modules or units can be implemented by software, hardware, or a combination of both. When any of the above modules or units are implemented by software, the software exists as computer program instructions and is stored in memory. The processor can be used to execute the program instructions and implement the above method flow. The processor can be built into a SoC (System-on-a-Chip) or ASIC, or it can be a separate semiconductor chip. In addition to the core that executes software instructions for computation or processing, the processor may further include necessary hardware accelerators, such as field-programmable gate arrays (FPGAs), PLDs (Programmable Logic Devices), or logic circuits that implement dedicated logic operations.

[0337] When the above modules or units are implemented in hardware, the hardware can be any one or any combination of a CPU, microprocessor, digital signal processing (DSP) chip, microcontroller unit (MCU), artificial intelligence processor, ASIC, SoC, FPGA, PLD, application-specific digital circuit, hardware accelerator, or non-integrated discrete device, which can run the necessary software or perform the above method flow independently of software.

[0338] Optionally, embodiments of this application also provide a chip system, including: at least one processor and an interface, wherein the at least one processor is coupled to a memory via the interface, and when the at least one processor executes a computer program or instructions in the memory, the method in any of the above method embodiments is executed. In one possible implementation, the communication device further includes a memory. Optionally, the chip system may be composed of chips, or may include chips and other discrete devices; embodiments of this application do not specifically limit this.

[0339] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0340] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, disclosure, and appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0341] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of this application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from the spirit and scope of this application. Thus, if such modifications and modifications of this application fall within the scope of the claims of this application and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A communication method, characterized in that, include: The first user equipment sends the first data to the second user equipment via the side link SL; If the first user equipment does not receive the first feedback information, the first user equipment initializes the first counter, or the count value of the first counter remains unchanged; and If the first user equipment receives the first feedback information, and if the first user equipment does not receive the first feedback information, the first user equipment increments the count value of the first counter by 1. The first feedback information indicates whether the second user equipment has successfully received the first data; the first counter is used for radio link failure (RLF) detection. The first user equipment did not receive the first feedback information, including: The reception of the first feedback information conflicted with the first transmission, and the first user equipment did not perform the action of receiving the first feedback information; The first user equipment receives first feedback information, including: The first user equipment performs the action of receiving the first feedback information.

2. The method according to claim 1, characterized in that, The reception of the first feedback information conflicts with the first transmission, and the first user equipment does not perform the action of receiving the first feedback information, including: The reception of the first feedback information conflicts with the first transmission, and the priority of receiving the first feedback information is lower than or equal to the priority of the first transmission.

3. The method according to any one of claims 1-2, characterized in that, The initialization of the first counter by the first user equipment includes: the first user equipment initializing the count value of the first counter to 0.

4. The method according to any one of claims 1-2, characterized in that, The signal quality between the first user equipment and the second user equipment is greater than or equal to a first threshold.

5. The method according to any one of claims 1-2, characterized in that, The method further includes: when the signal quality between the first user equipment and the second user equipment is less than or equal to a second threshold, and the first user equipment does not receive the first feedback information, the first user equipment increments the count value of the first counter by 1.

6. The method according to any one of claims 1-2, characterized in that, The first feedback information is transmitted on the physical side line feedback channel PSFCH.

7. The method according to any one of claims 1-2, characterized in that, The method further includes: the count value of the first counter is greater than or equal to a third threshold, and the first user equipment sends first indication information to the network device, the first indication information being used to indicate that the first user equipment has detected an RLF.

8. A communication device, characterized in that, The communication device includes: a transceiver module and a processing module; The transceiver module is used to send first data to the second user equipment via the side link SL; The processing module is configured to initialize the first counter if it does not receive the first feedback information, or to keep the count value of the first counter unchanged. The transceiver module is further configured to receive the first feedback information, and the processing module is further configured to increment the count value of the first counter by 1 if the first feedback information is not received. The first feedback information indicates whether the second user equipment has successfully received the first data; the first counter is used for radio link failure (RLF) detection. The failure to receive the first feedback information includes: The reception of the first feedback information conflicts with the first transmission, and the communication device does not perform the action of receiving the first feedback information; The receipt of the first feedback information includes: The communication device performs the action of receiving the first feedback information.

9. The communication device according to claim 8, characterized in that, The reception of the first feedback information conflicts with the first transmission, and the communication device does not perform the action of receiving the first feedback information, including: The reception of the first feedback information conflicts with the first transmission, and the priority of receiving the first feedback information is lower than or equal to the priority of the first transmission.

10. The communication device according to any one of claims 8-9, characterized in that, The processing module is used to initialize the first counter, including: initializing the count value of the first counter to 0.

11. The communication device according to any one of claims 8-9, characterized in that, The signal quality between the communication device and the second user equipment is greater than or equal to a first threshold.

12. The communication device according to any one of claims 8-9, characterized in that, The processing module is further configured to increment the count value of the first counter by 1 if the signal quality between the communication device and the second user equipment is less than or equal to a second threshold and the first feedback information is not received.

13. The communication device according to any one of claims 8-9, characterized in that, The first feedback information is transmitted on the physical side line feedback channel PSFCH.

14. The communication device according to any one of claims 8-9, characterized in that, The transceiver module is further configured to send a first indication message to the network device when the count value of the first counter is greater than or equal to a third threshold. The first indication message is used to indicate that the communication device has detected an RLF.

15. A communication device, characterized in that, include: A memory and a processor coupled to the memory, the memory being used to store a program, and the processor being used to execute the program stored in the memory; when the communication device is in operation, the processor runs the program, causing the communication device to perform the method of any one of claims 1-7.

16. The apparatus according to claim 15, characterized in that, The device is a chip or chip system.

17. A computer-readable storage medium, characterized in that, It stores a computer program that, when executed by a computer, causes the computer to perform the method of any one of claims 1-7.

18. A computer program product containing instructions, characterized in that, When the instructions are executed on a computer, the computer performs the method of any one of claims 1-7.

Images