Method, apparatus, and system for handling sidelink wireless link failures

Abstract

Embodiments of the present invention provide a method, apparatus, and system for handling sidelink radio link failures. The method includes, when a sidelink radio link failure (SL RLF) with a second remote device is detected, or when a higher layer in the first remote device requests the release of the PC5 RRC connection between the first remote device and the second remote device, the first remote device releasing the PC5 RRC connection, PC5 unicast link, or PC5 RLC channel between the first remote device and the relay device; or maintaining the PC5 RRC connection, PC5 unicast link, or PC5 RLC channel between the first remote device and the relay device, and performing the above-described processing regarding the radio link failure.

Description

Technical Field

[0001] The present invention relates to the technical field of communications.

Background Art

[0002] In Release 18 (R18), UE-to-UE relay (U2U relay) is being considered. UE-to-UE relay can extend the coverage of sidelink transmission between two sidelink UEs and save power.

[0003] FIG. 1 is a diagram showing a scenario of UE-to-UE relay. As shown in FIG. 1, the scenario includes the following three cases, namely, All UEs (source UE, relay UE, and target UE (also referred to as destination UE / destination UE, etc.)) are located within the network coverage; All UEs (source UE, relay UE, and target UE) are located outside the network coverage; and Some UEs are covered, that is, at least one UE (source UE, relay UE, and target UE) is located within the network coverage, and at least one UE (including the source UE, relay UE, and target UE) is located outside the network coverage.

[0004] In the research on R18 Layer-2 UE-to-UE relay (L2 U2U relay), it has been agreed to use the user plane protocol stack shown in FIG. 2 and the control plane protocol stack shown in FIG. 3. Among them, an adaptation layer, for example, ADAPT shown in FIGS. 2 and 3, is introduced, which is also referred to as SRAP (Sidelink Relay Adaptation Protocol).

[0005] As shown in Figures 2 and 3, the PC5 interface links support the adaptive layer ADAPT. In Figure 2 (user-plane protocol stack diagram), the IP, SDAP, and PDCP layers are located above the ADAPT layer, and the RLC, MAC, and PHY layers are located below the ADAPT layer. In Figure 3 (control-plane protocol stack diagram), the RRC and PDCP layers are located above the ADAPT layer, and the RLC, MAC, and PHY layers are located below the ADAPT layer. In Figures 2 and 3, ADAPT may be replaced with SRAP. In Figure 2, the IP, SDAP, and PDCP layers are terminated between two remote UEs, and the RLC, MAC, and PHY layers are terminated on each PC5 link. In Figure 3, the RRC and PDCP layers are terminated between two remote UEs, and the RLC, MAC, and PHY layers are terminated on each PC5 link.

[0006] The above-mentioned introduction of background art is intended to clearly and completely explain the proposed technical aspects of the present invention and to facilitate understanding by those skilled in the art. These technical aspects, as described in the background art of the present invention, should not be construed as being well-known to those skilled in the art. [Overview of the Initiative] [Problems that the invention aims to solve]

[0007] The inventors have discovered the following: According to the conventional behavior of the UE regarding SL RLF (Sidelink Radio Link Failure), in a U2U relay scenario, for example, when the timer T400 for the other remote device (e.g., referred to as the second remote device) expires, or when the sidelink PDCP entity indicates a failure in the integrity check (inspection) for SL-SRB2 or SL-SRB3 for the other remote device (e.g., referred to as the second remote device), the first remote device can trigger relay reselection because it considers that a sidelink radio link failure (or SL RLF) or a PC5 interface radio link failure (PC5 RLF) has been detected between the destination address corresponding to the other remote device (or it can be said that an end-to-end sidelink radio link failure or PC5 radio link failure has been detected).

[0008] However, as shown in Figure 4, if the first remote device or first remote UE (e.g., the source UE in Figure 4) considers that an end-to-end PC5 RLF or SL RLF has been detected between it and the destination address corresponding to the second remote device or second remote UE (e.g., the target UE in Figure 4), it can release a PC5 connection to the destination address corresponding to the second remote device or second remote UE. However, there is no clear provision as to whether it should also release a per-hop PC5-RRC connection / PC5 unicast link to the destination address corresponding to the relay UE (e.g., the UE-to-UE relay in Figure 4). This can lead to service / traffic interruptions or waste resources or power consumption of the UE due to continued data transmission at lower layers. The same problem exists when the first remote device or first remote UE is the target UE (destination UE) and the second remote device or second remote UE is the source UE.

[0009] To solve at least one of the above-mentioned problems or other similar problems, embodiments of the present invention provide methods, apparatus and systems for handling side-link wireless link failures. [Means for solving the problem]

[0010] According to one aspect of an embodiment of the present invention, a side-link wireless link failure processing device is provided, which is located in a first remote device, and the device is The processing unit includes a processing unit that releases the PC5 RRC connection, PC5 unicast link, or PC5 RLC channel between the first remote device and the relay device when a sidelink radio link failure (SL RLF) is detected between the first remote device and the second remote device, or when the upper layer in the first remote device requests the release of the PC5 RRC connection between the first remote device and the second remote device.

[0011] According to another aspect of the embodiment of the present invention, a side-link radio link failure processing device is provided, which is located in a first remote device, and the device is The processing unit includes a processing unit that reserves a PC5 RRC connection, PC5 unicast link, or PC5 RLC channel between the first remote device and a relay device when a sidelink radio link failure (SL RLF) is detected between the first remote device and the second remote device, or when the upper layer in the first remote device requests the release of the PC5 RRC connection between the first remote device and the second remote device.

[0012] According to another aspect of the embodiment of the present invention, a sidelink radio link failure processing device is provided, which is arranged in a relay device, and the device includes a receiving unit and a processing unit. The receiving unit receives instruction information from the first remote device, and the instruction information indicates that an end-to-end sidelink wireless link failure has occurred. The processing unit performs at least one of the following operations based on the instruction information, namely, Stop sending data to the destination address corresponding to the second remote device; It is assumed that a sidelink wireless link failure has been detected for the destination address corresponding to the second remote device; Release the PC5 relay RLC channel, bearer, or entity between the destination address corresponding to the second remote device; The settings related to NR sidelink communication for the destination address corresponding to the second remote device are dropped (discarded); A dedicated MAC is reset to the associated sidelink of the destination address corresponding to the second remote device; The PC5-RRC connection between the second remote device and the destination address corresponding to the aforementioned second remote device is considered to have been released; The upper layer instructs the release of a PC5 unicast link to the destination address corresponding to the second remote device; and This instructs the upper layer to release a PC5-RRC connection to the destination address corresponding to the second remote device.

[0013] According to another aspect of the embodiment of the present invention, a side-link radio link failure processing device is provided, which is located in a first remote device, and the device includes a processing unit, The processing unit maintains the PC5 RRC connection or PC5 unicast link between the first remote device and the second remote device when a sidelink radio link failure (SL RLF) is detected between the first and second remote devices.

[0014] According to another aspect of the embodiments of the present invention, a setting device is provided, which is arranged in a network device, and the device includes a setting unit, The setting unit sets a third timer for the remote device, the value of which is greater than the value of timer T400, and the third timer is used by the remote device to perform RRC resetting related to the side link.

[0015] According to another aspect of the embodiment of the present invention, a setting device is provided which is placed in a remote device in an end-to-end relay (U2U relay), and the device is A setting unit that sets the value of the first timer T400 to a value obtained by adding or multiplying the value of the first timer T400 by the value of the second timer T400 set by the network device; and The system includes a processing unit that activates the first timer T400 when sending a sidelink RRC reset message.

[0016] According to another aspect of the embodiment of the present invention, a setting device is provided, which is placed in a network device, and the device is The setting unit includes a setting unit which sets a range of values ​​for timer T400, of which the second value within the range is set for the remote device in the end-to-end relay (U2U relay). [Effects of the Invention]

[0017] The advantageous effects of the embodiments of the present invention are at least as follows. According to the embodiments of the present invention, when an end-to-end sidelink radio link failure occurs in UE-to-UE relay, the lower layer can be prevented from continuously performing data transmission, so as to avoid waste of sidelink radio resources and reduce the processing complexity and power consumption of the UE.

[0018] Specific embodiments of the present invention are disclosed in detail by referring to the following description and drawings, showing aspects in which the principles of the present invention can be employed. It should be noted that the embodiments of the present invention are not limited in scope by these. Within the scope of the appended claims, the embodiments of the present invention may include various changes, modifications, and substitutions.

[0019] Also, the features described and / or shown in one embodiment can be used in one or more other embodiments in the same or similar manner, combined with the features in other embodiments, or replace the features in other embodiments.

[0020] Note that terms such as "comprising / including" when used in this specification refer to the presence of features, elements, steps, or assemblies, but also refer to the fact that they do not exclude the presence or addition of one or more other features, elements, steps, or assemblies.

Brief Description of the Drawings

[0021] Elements and features described in one drawing or one embodiment of the present invention can be combined with elements and features shown in one or more other drawings or embodiments. Also, in the drawings, similar reference numerals indicate corresponding parts in several drawings and are also used to indicate corresponding parts used in multiple embodiments.

[0022] The included drawings are used to provide a further understanding of embodiments of the present invention, and these drawings constitute part of this specification and are used to illustrate embodiments of the present invention and to explain the principles of the present invention together with the textual description. Also, as is obvious, the drawings described below are merely for illustrating some embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings without creative effort. [Figure 1] This diagram shows a scenario for a UE-to-UE relay. [Figure 2] This diagram shows the user-plane protocol stack for UE-to-UE relay. [Figure 3] This diagram shows the control plane protocol stack for UE-to-UE relay. [Figure 4] This diagram shows whether the connection between devices is released in the event of an end-to-end sidelink wireless link failure. [Figure 5] This figure shows a method for handling side-link wireless link failures in an embodiment of the present invention. [Figure 6] This is another figure illustrating a method for handling side-link wireless link failures in an embodiment of the present invention. [Figure 7] This is another figure illustrating a method for handling side-link wireless link failures in an embodiment of the present invention. [Figure 8] This diagram shows the operation of timer T400. [Figure 9] This diagram shows the operation of timer T400 in a UE-to-UE relay. [Figure 10] This figure shows the setting method in an embodiment of the present invention. [Figure 11] This is another figure illustrating the setting method in an embodiment of the present invention. [Figure 12] This is another figure illustrating the setting method in an embodiment of the present invention. [Figure 13] This figure shows a processing device for side-link wireless link failure in an embodiment of the present invention. [Figure 14]This is another figure showing a processing device for side-link wireless link failure in an embodiment of the present invention. [Figure 15] This is another figure showing a processing device for side-link wireless link failure in an embodiment of the present invention. [Figure 16] Another figure showing a processing device for side-link wireless link failure in an embodiment of the present invention. [Figure 17] This figure shows a setting device in an embodiment of the present invention. [Figure 18] This is another figure showing a setting device in an embodiment of the present invention. [Figure 19] This is another figure showing a setting device in an embodiment of the present invention. [Figure 20] This figure shows a communication system in an embodiment of the present invention. [Figure 21] This figure shows a terminal device in an embodiment of the present invention. [Figure 22] This figure shows a network device in an embodiment of the present invention. [Modes for carrying out the invention]

[0023] The aforementioned and other features of the present invention will become clear by referring to the attached drawings and the following description. While the specification and drawings disclose specific embodiments of the present invention, these represent only a limited number of embodiments in which the principles of the present invention can be employed. It should be understood that the present invention is not limited to the described embodiments, and that it includes all modifications, variations, and substitutions of the claims.

[0024] In embodiments of the present invention, the terms "communication network" or "wireless communication network" may refer to a network conforming to any communication standard such as LTE (Long Term Evolution), LTE-A (LTE-Advanced), WCDMA (registered trademark) (Wideband Code Division Multiple Access), HSPA (High-Speed ​​Packet Access), etc.

[0025] Furthermore, communication between devices in a communication system may be carried out according to any stage of communication protocol, and may include, but is not limited to, the following communication protocols: namely, 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, 5G, New Radio (NR), and / or other conventional or future-developed communication protocols.

[0026] In embodiments of the present invention, the term "network device" refers, for example, to a device in a communication system that connects terminal devices to a communication network and provides services to said terminal devices. Network devices may include, but are not limited to, the following: base stations (BS), access points (AP), transmission and reception points (TRP), broadcast transmitters, mobile management entities (MME), network gateways, servers, radio network controllers (RNC), base station controllers (BSC), etc.

[0027] Base stations may include, but are not limited to, Node B (NodeB or NB), Evolutionary Node B (eNodeB or eNB), 5G base stations (gNB), and may also include RRH (Remote Radio Head), RRU (Remote Radio Unit), relay, or low-power nodes (e.g., femto, pico). The term “base station” may also include some or all of these functions, and each base station can provide communication coverage to a specific geographic area. The term “cell” may refer to a base station and / or the area it covers, depending on the context in which the term is used. Cells and base stations are interchangeable, as long as it does not cause confusion.

[0028] In embodiments of the present invention, the terms "User Equipment" (UE) or "Terminal Equipment" (TE) refer to devices that access a communication network via network equipment and receive services from the network. User equipment may be fixed or mobile, and may also be referred to as a mobile station (MS), terminal, subscriber station (SS), access terminal (AT), station, etc.

[0029] User devices may include, but are not limited to, the following: cellular phones, PDAs (Personal Digital Assistants), wireless modems, wireless communication devices, mobile devices, machine-type communication devices, laptop computers, cordless phones, smartphones, smartwatches, digital cameras, etc.

[0030] Furthermore, in scenarios such as IoT (Internet of Things), user devices may also be monitoring or measuring devices or equipment, and may include, but are not limited to, the following: machine-type communication (MTC) terminals, in-vehicle communication terminals, D2D (device-to-device) terminals, M2M (machine-to-machine) terminals, etc.

[0031] Currently, actions related to sidelink wireless link failures are defined in the standard as follows:

[0032] [Table 1] Furthermore, regarding L2 UE-to-UE relay, 3GPP (registered trademark) has the following agreements.

[0033] [Table 2] As can be seen, according to prior art, when a sidelink radio link failure (SL RLF) occurs, the UE's actions are directed at a "specific destination," and the conditions under which the UE determines whether an SL RLF has occurred are also directed at a "specific destination." In other words, according to the UE's actions regarding SL RLF in the conventional SL RLF scenario, for example, in a U2U relay scenario, when the T400 for the second remote device is disconnected, or when the sidelink PDCP entity indicates a failure of the integrity check for SL-SRB2 or SL-SRB3 for the second remote device, the first remote device considers that an SL RLF has been detected for the destination corresponding to the second remote device, and according to RAN2 agreements, a relay reselection can be triggered. However, the standard does not specify whether a per-hop PC5-RRC connection / PC5 unicast link to the destination corresponding to the relay UE is also released when an end-to-end PC5 RLF or SL RLF is detected between the first remote device and the destination corresponding to the second remote device.

[0034] The present invention has been made to solve at least one of the problems described above. Hereinafter, various embodiments of the present invention will be described with reference to the drawings. These embodiments are merely illustrative and do not limit the present invention.

[0035] <Example of the first side view> In embodiments of the present invention, a method for handling sidelink wireless link failures is provided, and the explanation will be given from the perspective of the first remote device. The first remote device may be the source UE in a UE-to-UE relay scenario, for example, source UE 11 in the scenario shown in Figure 1, or it may be the destination UE in a UE-to-UE relay scenario, for example, target UE 13 in the scenario shown in Figure 1. Accordingly, when the first remote device is the source UE in a UE-to-UE relay scenario, the second remote device is the target UE in a UE-to-UE relay scenario, and when the first remote device is the target UE in a UE-to-UE relay scenario, the second remote device is the source UE in a UE-to-UE relay scenario.

[0036] Figure 5 shows a method for handling side-link wireless link failures in an embodiment of the present invention. As shown in Figure 5, the method includes the following: 501: The first remote device releases the PC5 RRC connection, PC5 unicast link, or PC5 RLC channel between the first remote device and the relay device when a sidelink radio link failure (SL RLF) is detected between the first remote device and the second remote device, or when the upper layer in the first remote device requests the release of the PC5 RRC connection between the first remote device and the second remote device.

[0037] In the above embodiment, when an end-to-end SL RLF occurs in the UE-to-UE relay, or when the upper layer requests the release of the PC5 RRC connection with the other UE, the PC5 RRC connection, PC5 unicast link, or PC5 RLC channel between the first remote device and the relay device is released. This prevents the lower layer from continuing data transmission, thus avoiding the waste of sidelink radio resources and reducing the processing complexity and power consumption of the UE.

[0038] In the above embodiment, the release of the PC5 RRC connection, PC5 unicast link, or PC5 RLC channel between the first remote device and the relay device may be as follows: namely, the release of the PC5 RRC connection or PC5 unicast link for the destination address (destination or destination L2 ID) of the relay device, or the release of the PC5 RRC connection or PC5 unicast link for the pair of L2 IDs of the first remote device and the relay device, or the release of the PC5 RRC connection or PC5 unicast link corresponding to one PC5 unicast link between the first remote device and the relay device.

[0039] In some embodiments, the release of the PC5 RRC connection, PC5 unicast link, or PC5 RLC channel between the first remote device and the relay device may include at least one of the following (i.e., the act of release may include at least one of the following): For the destination address corresponding to the relay device, a sidelink wireless link failure is considered to have been detected; Release the PC5 relay RLC channel, bearer, or entity between the relay device and the corresponding destination address; Drop the NR sidelink communication settings related to the destination address corresponding to the relay device; Reset a dedicated MAC address to the sidelink for the destination address corresponding to the relay device; The PC5-RRC connection between the relay device and the corresponding destination address is considered released; The upper layer instructs the relay device to release the PC5 unicast link to the corresponding destination address; and This instructs the upper layer that a PC5-RRC connection has been released to the destination address corresponding to the relay device.

[0040] In the above-described embodiment, the upper layer refers to the non-access stratum (NAS) or the V2X (Vehicle-to-everything) layer.

[0041] According to the above-described embodiment, the relevant description in the protocol may be modified as follows.

[0042] [Table 3] In the above description, the relevant operations on the PC5 RLC channel and MAC of the detected SL RLF destination (which in this embodiment is the destination of the second remote device) have been removed compared to the description in the conventional standard (for example, releasing the PC5 RLC channel of the detected SL RLF destination and resetting the MAC dedicated to the sidelink of the detected SL RLF destination). Furthermore, according to embodiments of the present invention, the UE may perform at least one of the operations of the underlined characters described above.

[0043] Figure 6 is another diagram illustrating a method for handling side-link wireless link failures in an embodiment of the present invention. As shown in Figure 6, the method includes the following: 601: The first remote device maintains a PC5 RRC connection, PC5 unicast link, or PC5 RLC channel between the first remote device and the relay device when a sidelink radio link failure (SL RLF) is detected between the first remote device and the second remote device, or when the upper layer in the first remote device requests the release of the PC5 RRC connection between the first remote device and the second remote device.

[0044] In the above embodiment, if an end-to-end sidelink wireless link failure occurs in the UE-to-UE relay, or if the upper layer requests the release of the PC5 RRC connection with the other UE, the PC5 RRC connection, PC5 unicast link, or PC5 RLC channel between the first remote device and the relay device is maintained. This avoids the lower layer having to continue data transmission, thus avoiding the waste of sidelink wireless resources and reducing the processing complexity and power consumption of the UE.

[0045] In the embodiments described above, maintaining a PC5 RRC connection, PC5 unicast link, or PC5 RLC channel between the first remote device and the relay device may include, namely, maintaining a PC5 RRC connection or PC5 unicast link for the destination address (destination or destination L2 ID) of the relay device, or maintaining a PC5 RRC connection or PC5 unicast link for a pair of L2 IDs of the first remote device and the relay device, or maintaining a PC5 RRC connection or PC5 unicast link corresponding to one PC5 unicast link between the first remote device and the relay device.

[0046] In some embodiments, the first remote device considers the relay device to be the appropriate relay device. For example, the first remote device re-selects the current relay device again through relay re-selection.

[0047] In the above embodiment, the first remote device considers the relay device to be a suitable relay device, thereby enabling the first remote device to maintain a PC5 RRC connection, PC5 unicast link, or PC5 RLC channel with the relay device.

[0048] In several other embodiments, the first remote device transmits instruction information to the relay device indicating that an end-to-end sidelink radio link failure has occurred.

[0049] In the embodiment described above, the first remote device transmits a single instruction to the relay device, which is used to indicate that an end-to-end SL RLF has occurred. For example, the first remote device may transmit the instruction when an end-to-end sidelink radio link failure is detected, or when the upper layer requests the release of the PC5 RRC connection with the other UE, or after the PC5 RRC connection, PC5 unicast link, or PC5 RLC channel with the second remote device has been maintained.

[0050] In the embodiments described above, the instruction information may be transmitted by PC5 RRC messages, PC5-S signaling (V2X layer signaling), SL MAC CE, or sidelink control information (SCI), but the present invention is not limited to these.

[0051] In the embodiments described above, the instruction information may include one bit or one field to indicate the cause of failure, and the cause of failure may be the detection of an SL RLF to the destination of the second remote device, or the detection of an end-to-end SL RLF, but the present invention is not limited to these.

[0052] In the above embodiment, upon receiving the above instruction information, the relay device may perform at least one of the following operations, namely, Stop sending data to the destination address corresponding to the second remote device; For the destination address corresponding to the second remote device, a sidelink wireless link failure is considered to have been detected; Release the PC5 relay RLC channel, bearer, or entity between the destination address corresponding to the second remote device; Drop the NR sidelink communication settings related to the destination address corresponding to the second remote device; Reset a dedicated MAC address to the associated sidelink for the destination address corresponding to the second remote device; The PC5-RRC connection between the second remote device and the corresponding destination address is considered to have been released; The upper layer instructs the second remote device to release a PC5 unicast link to the corresponding destination address; and This instructs the upper layer that a PC5-RRC connection to the destination address corresponding to the second remote device has been released, meaning that PC5 is unavailable.

[0053] That is, if a relay device receives instruction information from a first remote device and the instruction information indicates the occurrence of an end-to-end sidelink wireless link failure, the relay device may perform at least one of the above operations.

[0054] The above-described embodiment explains the actions of the first remote device.

[0055] In some embodiments, the first remote device is deemed to have detected an SL RLF between itself and the second remote device in the following cases, including, but not limited to, the following: Timer T400 for the destination address corresponding to the second remote device has expired; or The sidelink PDCP entity indicates a failure in the integrity check for SL-SRB2 or SL-SRB3 of the destination address corresponding to the second remote device.

[0056] In other words, the first remote device considers a sidelink radio link failure to have occurred with the second remote device when the timer T400 for the destination address corresponding to the second remote device expires, or when the sidelink PDCP entity indicates a failure in the integrity check for SL-SRB2 or SL-SRB3 for the destination address corresponding to the second remote device.

[0057] In several other embodiments, the first remote device considers a sidelink radio link failure with the second remote device to have been detected when it receives instruction information (referred to as the second instruction information) from the relay device indicating a sidelink radio link failure with the second remote device. That is, the relay device notifies the first remote device by the second instruction information that it has detected an SL RLF with the second remote device, and at this time, the first remote device also considers a sidelink radio link failure with the second remote device to have been detected.

[0058] In the above embodiment, the detection of an SL RLF with the second remote device may also be as follows: that is, that an SL RLF of the destination address (destination or destination L2 ID) corresponding to the second remote device is detected, or that an SL RLF of a pair of the L2 IDs of the first remote device and the L2 ID of the second remote device is detected, or that an RLF of a single PC5 unicast link with the second remote device is detected.

[0059] In the above embodiment, the release of the PC5 RRC connection with the second remote device may be as follows: that is, releasing the PC5 RRC connection for the destination address (destination or destination L2 ID) of the second remote device, releasing the PC5 RRC connection for the pair of the L2 IDs of the first remote device and the second remote device, or releasing the PC5 RRC connection corresponding to one PC5 unicast link with the second remote device.

[0060] The embodiments described above are illustrative examples illustrating embodiments of the present invention, but the present invention is not limited thereto, and appropriate modifications may be made based on the embodiments described above. For example, the trigger conditions in the embodiments described above may be used individually, or a combination of several of the trigger conditions in the embodiments described above may be used.

[0061] According to the method in the embodiment of the present invention, when an end-to-end SL RLF occurs in a UE-to-UE relay, or when a higher layer requests the release of the PC5 RRC connection with the other UE, the PC5 RRC connection, PC5 unicast link, or PC5 RLC channel between the first remote device and the relay device is maintained or released, thereby preventing the lower layer from continuing data transmission, thus avoiding the waste of sidelink radio resources and reducing the processing complexity and power consumption of the UE.

[0062] <Example of the second aspect> An embodiment of the present invention provides a method for handling side-link wireless link failures, which will be described from the perspective of the first remote device.

[0063] Figure 7 is another diagram illustrating a method for handling side-link wireless link failures in an embodiment of the present invention. As shown in Figure 7, the method includes the following: 701: The first remote device maintains the PC5 RRC connection or PC5 unicast link between the first remote device and the second remote device when a sidelink radio link failure (SL RLF) is detected between the first remote device and the second remote device.

[0064] In the SL RLF-related operations specified in the conventional standard, the UE can release the DRB and SRB for the corresponding destination address, release the PC5-RRC connection, and instruct the upper layer to release the PC5-RRC connection. In UE-to-UE relay, when the first remote device detects an SL RLF with the second remote device, following the operations specified in the conventional standard, it can release the DRB and SRB between the second remote device and the corresponding destination address, release the PC5-RRC connection to the corresponding destination address, and instruct the upper layer to release the PC5-RRC connection to the corresponding destination address. Therefore, business between the first and second remote devices may be interrupted, resulting in a failure to meet business QoS and a degraded user experience.

[0065] To solve the above-mentioned problems, according to an embodiment of the present invention, when an SL RLF is detected between the first remote device and the second remote device, the first remote device does not maintain or release the PC5 RRC connection or PC5 unicast link between the first and second remote devices. This is advantageous for faster recovery of business transmission with the second remote device, as it eliminates the need to establish the business on the PC5 interface, reduces the signaling overhead of setting up the RRC layer, and eliminates the need for the NAS layer to re-establish the PC5 unicast link.

[0066] In some embodiments, the first remote device further performs at least one of the following operations, namely: The DRB of the second remote device or relay device is suspended, for example, the DRB of the destination address corresponding to the second remote device or relay device; The SRB of the second remote device or relay device is suspended, for example, the SRB of the destination address corresponding to the second remote device or relay device is suspended; Reset a dedicated MAC to the sidelink of the second remote device or relay device, for example, reset a dedicated MAC to the sidelink of the destination address corresponding to the second remote device or relay device; Configure integrity protection and encryption for SRBs suspended by the PDCP layer, for example, configure integrity protection and encryption for SRBs with destination addresses corresponding to second remote devices or relay devices that are suspended by the PDCP layer; Start the first timer; Start the second timer; and The settings for the RRC layer and / or PDCP layer are saved, for example, the settings for the destination address corresponding to the second remote device or relay device.

[0067] In the above embodiment, the first timer is used for the first remote device to re-establish or restore the PC5 RRC connection with the second remote device. For example, the first timer is started when the PC5 RRC connection is re-established or restored, and stopped when the PC5 RRC connection re-establishment or restoration is completed.

[0068] In the above embodiment, the second timer is used for the first remote device to re-select the relay device. For example, the second timer is started when the relay device is re-selected, and stopped when the re-selection of the relay device is complete, or stopped when the appropriate relay device is re-selected.

[0069] Although the first and second timers have been described as illustrative examples above, the present invention is not limited to these, and in a specific implementation, these two timers may be used for other purposes and may be started or stopped at appropriate times as needed.

[0070] In some embodiments, the first remote device re-selects a relay device when an SL RLF is detected between it and the second remote device, and stops the second timer when it re-selects a relay device, for example, when it re-selects an appropriate relay device.

[0071] In the above embodiment, when the first remote device stops the second timer, it may also start the first timer in order to re-establish or recover the PC5 RRC connection.

[0072] In the above embodiment, the first remote device may re-select the previous relay device, or it may re-select a new relay device.

[0073] In some embodiments, when the first remote device re-establishes or restores the RC5 RRC connection with the second remote device, and the PC5 RRC connection between the first remote device and the second remote device is re-established or successfully restored, the first remote device may perform at least one of the following operations, namely: Stop the first timer; Re-establish the PDCP entities of the DRB and / or SRB of the second remote device or relay device, for example, re-establish the PDCP entities corresponding to the DRB and / or SRB of the destination address corresponding to the second remote device or relay device; Re-establish the RLC entities of the DRB and / or SRB of the second remote device or relay device, for example, re-establish the RLC entities corresponding to the DRB and / or SRB of the destination address corresponding to the second remote device or relay device; For the DRB and / or SRB of the second remote device or relay device, apply the settings prior to SL-RLF, or the default settings, or the predefined (i.e., specified) settings; Resume the DRB and / or SRB of the second remote device or relay device, for example, by resuming the DRB and / or SRB of the destination corresponding to the second remote device or relay device; Generate at least one new secret key, namely, a secret key for encryption of the sidelink SRB of the second remote device or relay device, a secret key for integrity protection of the sidelink SRB of the second remote device or relay device, a secret key for encryption of the sidelink DRB of the second remote device or relay device, and a secret key for integrity protection of the sidelink DRB of the second remote device or relay device; and Configure integrity protection and encryption for the SRB of a second remote device or relay device that is restarted by the PDCP layer.

[0074] In the above embodiment, the first remote device establishes a PC5-RRC connection with the re-selected relay device, and the second remote device also establishes a PC5-RRC connection with the re-selected relay device. After these two PC5-RRC connections are established, the first remote device can send a PC5-RRC message to the second remote device, such as an RRCReconfigurationSidelink message or an RRC re-establishment message on the sidelink. After receiving a response indicating success, such as an RRCReconfigurationCompleteSidelink message or an RRC re-establishment completion message on the sidelink, the PC5-RRC connection with the second remote device is deemed to have been successfully re-established or successfully restored.

[0075] In some embodiments, if the first timer expires, or the second timer expires, or the re-selected relay device becomes unsuitable, or if a higher layer of the first remote device (e.g., the V2X layer) instructs the release of the PC5 unicast link with the second remote device, the first remote device may further release the PC5 RRC connection with the second remote device.

[0076] In the above embodiment, the release of the PC5 RRC connection between the first remote device and the second remote device may include at least one of the following operations, namely, For the destination address corresponding to the relay device, a sidelink wireless link failure is considered to have been detected; Release the PC5 relay RLC channel, bearer, or entity between the relay device and the corresponding destination address; Drop the NR sidelink communication settings related to the destination address corresponding to the relay device; Reset a dedicated MAC address to the sidelink for the destination address corresponding to the relay device; The PC5-RRC connection between the relay device and the corresponding destination address is considered released; The upper layer instructs the relay device to release the PC5 unicast link to the corresponding destination address; and This instructs the upper layer that a PC5-RRC connection has been released to the destination address corresponding to the relay device.

[0077] In the above embodiment, the first remote device may further perform at least one of the following operations, namely, Release the DRB for the destination address corresponding to the second remote device; Release the SRB for the destination address corresponding to the second remote device; Drop the NR sidelink communication settings related to the destination address corresponding to the second remote device; The PC5-RRC connection between the second remote device and the corresponding destination address is considered to have been released; The upper layer instructs the second remote device to release a PC5 unicast link to the corresponding destination address; and This instructs the upper layer that a PC5-RRC connection to the destination address corresponding to the second remote device has been released, meaning that PC5 is unavailable.

[0078] The embodiments described above are illustrative examples illustrating embodiments of the present invention, but the present invention is not limited thereto, and appropriate modifications may be made based on the embodiments described above. For example, the embodiments described above may be used individually, or a combination of several of the embodiments described above may be used.

[0079] According to the method in the embodiment of the present invention, when an SL RLF is detected between the first remote device and the second remote device, the first remote device maintains the PC5-RRC connection and the PC5 unicast link with the second remote device, thereby omitting the business establishment procedure for the PC5 interface. This is advantageous for faster recovery of business transmission between the first remote device and the second remote device, reduces the signaling overhead of setting up the RRC layer, and eliminates the need for the NAS layer to re-establish the PC5 unicast link.

[0080] <Example of the third side> The current 3GPP (registered trademark) standard specifies the operation of the timer T400 as follows:

[0081] [Table 4] Figure 8 shows the operation of timer T400.

[0082] As shown in Figure 8, when the UE sends an RRCReconfigurationSidelink message, it starts timer T400 for the associated destination address. When it receives an RRCReconfigurationFailureSidelink or RRCReconfigurationCompleteSidelink message, it stops timer T400 for the associated destination address.

[0083] Furthermore, under the current standard, for UEs in the RRC_Idle / Inactive state, the T400 value set in SIB12 may be used; for UEs in the RRC_Connected state, the T400 value set in the RRC reconfiguration message may be used; or for UEs out of network coverage, the T400 value set in pre-configuration may be used. In all of these cases, the range of the T400 value is 100 milliseconds, 200 milliseconds, 300 milliseconds, 400 milliseconds, 600 milliseconds, 1000 milliseconds, 1500 milliseconds, and 2000 milliseconds.

[0084] The following describes the range of values ​​for T400 in the current standard.

[0085] [Table 5] In other words, the network device sets one of the values ​​within the range mentioned above as the T400 value.

[0086] Figure 9 shows the operation of timer T400 in a UE-to-UE relay. As shown in Figure 9, for the first remote UE (source remote UE or target remote UE), the RRCReconfigurationSidelink message, RRCReconfigurationCompleteSidelink message, or RRCReconfigurationFailureSidelink message is transmitted via two hops, namely, from the first remote UE (e.g., the source remote UE in Figure 9) to the relay UE (first hop) and from the relay UE to the second remote UE (e.g., the target remote UE in Figure 9) (second hop). As a result, the first remote UE may need more time after sending the RRCReconfigurationSidelink message to receive the RRCReconfigurationCompleteSidelink message or RRCReconfigurationFailureSidelink message transmitted by the second remote UE.

[0087] Therefore, when the T400 value is set to a relatively small value, when T400 is lost, the first remote UE that sends RRCReconfigurationSidelink may not yet have received the RRCReconfigurationCompleteSidelink message or RRCReconfigurationFailureSidelink message sent by the second remote UE. In this case, according to prior art, the first remote UE that sends RRCReconfigurationSidelink may consider that an SL RLF has been detected, and may release the PC5-RRC connection, causing a business interruption.

[0088] To solve the above-mentioned problems, a setting method is provided in the embodiments of the present invention.

[0089] Figure 10 shows a configuration method in an embodiment of the present invention. The explanation will be given from the network equipment side. As shown in Figure 10, the method includes the following, namely, 1001: The network device sets a third timer for the remote device, the value of which is greater than the value of timer T400, and the third timer is used by the remote device to perform RRC reconfiguration related to the sidelink.

[0090] In the above embodiment, the range of values ​​for the third timer is different from the range of values ​​for timer T400. For example, the range of values ​​for the third timer is within the range of values ​​for timer T400, and the range of values ​​for the third timer is the largest N values ​​within the range of values ​​for timer T400, where N is a positive integer.

[0091] Still using the aforementioned range of values ​​for T400 as an example, the range of values ​​for the third timer in the embodiment of the present invention may be {ms600, ms1000, ms1500, ms2000} within the above-mentioned range {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000}, i.e., N=4.

[0092] In the above-described embodiment, the method for setting the third timer is not limited, nor is the name of the third timer limited.

[0093] In some embodiments, for remote devices in an RRC idle or inactive state (RRC_Idle / Inactive UE), the value of the third timer may be set in SIB12; for remote devices in an RRC connected state (RRC_Connected UE), the value of the third timer may be set in an RRC reconfiguration message; and for remote devices out of network coverage, the value of the third timer may be set in pre-configuration. However, the present invention is not limited to these, and other configuration methods may exist.

[0094] In some embodiments, the value of the third timer is set for the identifier (ID) of the source remote UE among the remote devices, or for the identifier of the destination remote UE among the remote devices, or for a pair of the source remote UE identifier and destination remote UE identifier.

[0095] In the embodiments described above, the label may be, for example, an L2 ID (layer 2 label) or a local ID (local label), but the present invention is not limited to these.

[0096] In some embodiments, the third timer and T400 are configured, and the remote device determines whether to activate the third timer or timer T400 when sending the RRCReconfigurationSidelink message, based on whether it communicates with the other remote device via a relay device. For example, if the remote device communicates with the other remote device via a relay device, the remote device activates the third timer, and if the remote device communicates directly with the other remote device (without going through a relay device), it activates timer T400.

[0097] In some embodiments, the third timer is set, T400 is not set, and the third timer is activated when the remote device sends the RRCReconfigurationSidelink message, either when communicating with the other remote device via a relay device or when communicating directly with the other remote device (without going through a relay device).

[0098] According to the embodiment described above, the network device sets a new timer (for example, referred to as the third timer) for the remote UE. The value of the third timer is greater than the value of T400, and the range of the value of the third timer may differ from the range of the value of T400. This is advantageous in meeting the business quality requirements of sidelink communication, as it avoids sidelink wireless link failures caused by the set T400 value being inappropriate for the UE-to-UE relay scenario, and can also reduce business interruptions and improve the user experience.

[0099] Figure 11 is another diagram illustrating a configuration method in an embodiment of the present invention. The explanation is given from the side of the remote device in the end-to-end relay. As shown in Figure 11, the method includes, namely, 1101: In an end-to-end relay (U2U relay), the remote device sets the value of the first timer T400 to a value obtained by adding or multiplying the value of the first timer T400 by the value of the second timer T400 set by the network device; and 1102: When the remote device sends a sidelink RRC reset message, the first timer T400 is activated.

[0100] In the above-described embodiment, unlike the embodiment in Figure 10, the remote UE in the U2U relay sets the value of the first timer T400 to a value obtained by adding or multiplying the value of the first timer T400 by the value of the second timer T400 set by the network. This avoids sidelink wireless link failures due to the set T400 value being inappropriate for the UE-to-UE relay scenario, which is advantageous in meeting the business quality requirements for sidelink communication, and can also reduce business interruptions and improve the user experience.

[0101] In the embodiments described above, the first value is used to extend the value of the first timer T400 used by the remote UE in the U2U relay. In some embodiments, the first value is a positive integer, but the present invention does not limit its specific value, and the first value may be the same or different when "adding the first value" and when "multiplying the first value".

[0102] In some embodiments, the first value is predefined, for example, its value is 1000ms (when "adding the first value") or 2 (when "multiplying the first value").

[0103] In some embodiments, the first value is set by a network device.

[0104] For example, for remote devices in an RRC idle or inactive state (RRC_Idle / Inactive UE), the first value is set in SIB12; for remote devices in an RRC connected state (RRC_Connected UE), the first value is set in the RRC reconfiguration message; and for remote devices out of network coverage, the first value is set in pre-configuration.

[0105] Furthermore, for example, the first value may be set for the indicator of a source remote UE among the remote devices, or for the indicator of a destination remote UE among the remote devices, or for a pair of source remote UE and destination remote UE indicators.

[0106] The above-mentioned identifiers may be, for example, L2 IDs, local IDs, etc.

[0107] In some embodiments, when a remote device sends an RRCReconfigurationSidelink message, it determines whether to activate the first timer T400 or the second timer T400 based on whether it communicates with the other remote device via a relay device. For example, if the remote device communicates with the other remote device via a relay device, it activates the first timer T400, and if the remote device communicates directly with the other remote device (without going through a relay device), it activates the second timer T400.

[0108] In the above embodiment, the remote UE in the U2U relay sets the value of the first timer T400 as the value obtained by adding or multiplying the first value by the value of the second timer T400 set by the network. This is advantageous in satisfying the business quality requirements of sidelink communication, as it avoids sidelink wireless link failures caused by the set T400 value being inappropriate for the UE-to-UE relay scenario, and can also reduce business interruptions and improve the user experience.

[0109] Figure 12 is another diagram illustrating a configuration method in an embodiment of the present invention. The explanation will be given from the network equipment side. As shown in Figure 12, the method includes, namely, 1201: The network device sets a range of values ​​for timer T400, and the second value within that range is set for the remote device in the end-to-end relay (U2U relay).

[0110] In the above-described embodiment, the second value is, for example, 1000 milliseconds, 1500 milliseconds, or 2000 milliseconds.

[0111] As described above, a specific value within the range of Timer T400 values ​​is set for the remote UE. This is advantageous in meeting the operational quality requirements for sidelink communication, as it avoids sidelink wireless link failures due to the set T400 value being inappropriate for the UE-to-UE relay scenario, and can also reduce business interruptions and improve the user experience.

[0112] The embodiments described above are illustrative examples illustrating embodiments of the present invention, but the present invention is not limited thereto, and appropriate modifications may be made based on the embodiments described above. For example, the embodiments described above may be used individually, or a combination of several of the embodiments described above may be used.

[0113] According to the method in the embodiment of the present invention, sidelink wireless link failures due to the setting of T400 being inappropriate for the UE-to-UE relay scenario can be avoided, which is advantageous in satisfying the business quality requirements of sidelink communication, and can also reduce business interruptions and improve the user experience.

[0114] <Example of the fourth side> An embodiment of the present invention provides a processing device for side-link wireless link failure. The device may be, for example, a terminal device, or one or more components or assemblies installed on a terminal device. The principle by which the device solves the problem is the same as the method in the embodiment of the first aspect, so for its specific implementation, refer to the implementation of the method in the embodiment of the first aspect, and redundant explanations will be omitted here.

[0115] Figure 13 shows a side-link wireless link failure processing device in an embodiment of the present invention. For example, the device is the first remote device deployed in a U2U relay scenario. As shown in Figure 13, the side-link wireless link failure processing device 1300 in an embodiment of the present invention includes the following: Processing unit 1301: When a sidelink radio link failure (SL RLF) is detected between the first remote device and the second remote device, or when the upper layer of the first remote device requests the release of the PC5 RRC connection between the first remote device and the second remote device, it releases the PC5 RRC connection, PC5 unicast link, or PC5 RLC channel between the first remote device and the relay device.

[0116] In some embodiments, the release of the PC5 RRC connection, PC5 unicast link, or PC5 RLC channel between the first remote device and the relay device by the processing unit 1301 includes at least one of the following: Release the PC5 RRC connection or PC5 unicast link to the destination address of the relay device; Release the PC5 RRC connection or PC5 unicast link of the pair of L2 IDs of the first remote device and the relay device; and Release a PC5 RRC connection or PC5 unicast link corresponding to one PC5 unicast link between the first remote device and the relay device.

[0117] In some embodiments, the release of the PC5 RRC connection, PC5 unicast link, or PC5 RLC channel between the first remote device and the relay device by the processing unit 1301 includes the processing unit 1301 performing at least one of the following operations: For the destination address corresponding to the relay device, a sidelink wireless link failure is considered to have been detected; Release the PC5 relay RLC channel, bearer, or entity between the relay device and the corresponding destination address; Drop the NR sidelink communication settings related to the destination address corresponding to the relay device; Reset a dedicated MAC address to the sidelink for the destination address corresponding to the relay device; The PC5-RRC connection between the relay device and the corresponding destination address is considered released; The upper layer instructs the relay device to release the PC5 unicast link to the corresponding destination address; and This instructs the upper layer that a PC5-RRC connection has been released to the destination address corresponding to the relay device.

[0118] In the above embodiment, the upper layer includes a non-contact layer or a V2X (Vehicle-to-everything) layer.

[0119] Figure 14 is another diagram showing a side-link wireless link failure processing device in an embodiment of the present invention. For example, the device is the first remote device deployed in a U2U relay scenario. As shown in Figure 14, the relay selection or reselection device 1400 in an embodiment of the present invention includes, namely, Processing unit 1401: When a sidelink radio link failure (SL RLF) is detected between the first remote device and the second remote device, or when the upper layer of the first remote device requests the release of the PC5 RRC connection between the first remote device and the second remote device, the unit maintains the PC5 RRC connection, PC5 unicast link, or PC5 RLC channel between the first remote device and the relay device.

[0120] In some embodiments, the maintenance of a PC5 RRC connection, PC5 unicast link, or PC5 RLC channel between the first remote device and the relay device includes at least one of the following: Maintain a PC5 RRC connection or PC5 unicast link for the destination address of the relay device; Maintain a PC5 RRC connection or PC5 unicast link between the L2 ID pair of the first remote device and the L2 ID of the relay device; and Maintain a PC5 RRC connection or PC5 unicast link corresponding to one PC5 unicast link between the first remote device and the relay device.

[0121] In some embodiments, the processing unit 1401 considers the relay device to be a suitable relay device.

[0122] In some embodiments, the processing unit 1401 transmits instruction information to a relay device indicating that an end-to-end sidelink wireless link failure has occurred.

[0123] In the embodiments described above, the first remote device may transmit the above-described instruction information when an end-to-end side-link wireless link failure is detected, or when the upper layer requests the release of the PC5 RRC connection with the second remote device, or after the PC5 RRC connection, PC5 unicast link, or PC5 RLC channel with the second remote device has been maintained.

[0124] In the above embodiment, the above instruction information may include bits or fields for indicating the cause of instruction failure, and the cause of failure may include the detection of an SL RLF for the destination address of the second remote device, or the detection of an end-to-end SL RLF.

[0125] In the above embodiment, the instruction information is used for the relay device to perform at least one of the following operations, namely, Stop sending data to the destination address corresponding to the second remote device; A sidelink wireless link failure is considered to have been detected for the destination address corresponding to the second remote device; Release the PC5 relay RLC channel, bearer, or entity between the destination address corresponding to the second remote device; Discard the associated settings for NR sidelink communication regarding the destination address corresponding to the second remote device; Reset a dedicated MAC address to the associated side link of the destination address corresponding to the second remote device; The PC5-RRC connection between the destination address corresponding to the second remote device is considered to have been released; The upper layer instructs the second remote device to release a PC5 unicast link to the corresponding destination address; and This instructs the upper layer that a PC5-RRC connection has been released between the second remote device and the corresponding destination address.

[0126] In the above-described embodiment, instruction information may be transmitted via PC5-RRC messages, PC5-S signaling, SL MAC CE, or sidelink control information (SCI).

[0127] In some embodiments, the processing unit 1401 determines that a sidelink radio link failure between the first remote device and the second remote device has been detected when the timer T400 for the destination address corresponding to the second remote device expires, or when the sidelink PDCP entity indicates a failure in the integrity check for SL-SRB2 or SL-SRB3 of the destination address corresponding to the second remote device.

[0128] In some embodiments, the processing unit 1401 determines that a sidelink wireless link failure has been detected between the first remote device and the second remote device when it receives a second instruction information from the relay device to indicate a sidelink wireless link failure between the relay device and the second remote device.

[0129] Figure 15 is another diagram showing a side-link wireless link failure processing device in an embodiment of the present invention. The device is, for example, a relay device deployed in a U2U relay scenario. As shown in Figure 15, the device includes, namely, Receiving unit 1501: receives instruction information from the first remote device, the instruction information indicates that an end-to-end sidelink radio link failure has occurred; and Processing unit 1502: Based on the instruction information, it performs at least one of the following operations, namely, Stop sending data to the destination address corresponding to the second remote device; It is assumed that a sidelink wireless link failure has been detected for the destination address corresponding to the second remote device; Release the PC5 relay RLC channel, bearer, or entity between the destination address corresponding to the second remote device; The relevant settings for NR sidelink communication regarding the destination address corresponding to the second remote device are dropped; A dedicated MAC is reset to the associated sidelink of the destination address corresponding to the second remote device; The PC5-RRC connection between the second remote device and the destination address corresponding to the aforementioned second remote device is considered to have been released; The upper layer instructs the release of a PC5 unicast link to the destination address corresponding to the second remote device; and This instructs the upper layer that a PC5-RRC connection has been released to the destination address corresponding to the second remote device.

[0130] Although only the components or modules of the present invention have been described above, the present invention is not limited to these. The side-link wireless link failure processing devices 1300-1500 in the embodiments of the present invention may further include other components or modules, and the specific details of these components or modules can be found in the relevant technologies.

[0131] Furthermore, for convenience, Figures 13-15 only show the connection relationships or signal directions between each component or module; however, as those skilled in the art will understand, various related technologies such as bus connections may be employed. The above-mentioned components or modules may be realized by hardware such as processors, memory devices, transmitters, and receivers, but the implementation of the present invention is not limited thereto.

[0132] The apparatus according to the embodiment of the present invention avoids continuous data transmission by the lower layer, thereby avoiding the waste of sidelink wireless resources and reducing the processing complexity and power consumption of the UE.

[0133] <Example of the fifth side> An embodiment of the present invention provides a processing device for side-link wireless link failure. The device may be, for example, a terminal device, or one or more components or assemblies installed on a terminal device. Since the principle by which the device solves the problem is the same as the method in the embodiment of the second aspect, its specific implementation can be found by referring to the implementation of the method in the embodiment of the second aspect, and redundant explanations will be omitted here.

[0134] Figure 16 is another diagram showing a side-link wireless link failure processing device in an embodiment of the present invention. For example, the device is the first remote device deployed in a U2U relay scenario. As shown in Figure 16, the side-link wireless link failure processing device 1600 in an embodiment of the present invention includes, namely, Processing unit 1601: If a sidelink radio link failure (SL RLF) is detected between the first remote device and the second remote device, maintain the PC5 RRC connection or PC5 unicast link between the first remote device and the second remote device.

[0135] In some embodiments, the processing unit 1601 further performs at least one of the following operations, namely: Suspend the DRB of the second remote device or relay device; Suspend the SRB of the second remote device or relay device; Reset a dedicated MAC to the sidelink of the second remote device or relay device; Configure integrity protection and encryption for SRBs suspended by the PDCP layer; Start the first timer; Start the second timer; and Save the settings for the RRC layer and / or PDCP layer.

[0136] In some embodiments, the first timer is used for the first remote device to re-establish or restore the PC5 RRC connection with the second remote device, and the second timer is used for the first remote device to re-select the relay device.

[0137] In the above embodiment, the processing unit 1601 may further re-select the relay equipment, and when the relay equipment is re-selected, it may also stop the second timer.

[0138] In the above embodiment, when the processing unit 1601 stops the second timer, it may also start the first timer.

[0139] In some embodiments, the processing unit 1601 further re-establishes or restores the RC5 RRC connection with the second remote device, and when the PC5 RRC connection with the second remote device is re-established or successfully restored, it performs at least one of the following operations, namely, Stop the first timer; Re-establish the PDCP entities of the DRB and / or SRB of the second remote device or relay device; Re-establish the RLC entities of the DRB and / or SRB of the second remote device or relay device; For the DRB and / or SRB of the second remote device or relay device, apply the settings prior to SL-RLF, or apply the default settings, or apply the predefined settings; Restart the DRB and / or SRB of the second remote device or relay device; Generate at least one new secret key, namely, a secret key for encryption of the sidelink SRB of the second remote device or relay device, a secret key for integrity protection of the sidelink SRB of the second remote device or relay device, a secret key for encryption of the sidelink DRB of the second remote device or relay device, and a secret key for integrity protection of the sidelink DRB of the second remote device or relay device; and The PDCP layer enables integrity protection and encryption of the SRB of the second remote device or relay device, which is restarted by the PDCP layer.

[0140] In some embodiments, the processing unit 1601 releases the PC5 RRC connection with the second remote device when the first timer expires, or when the second timer expires, or when the re-selected relay device becomes inappropriate, or when the upper layer of the first remote device instructs the release of the PC5 unicast link with the second remote device.

[0141] In the above embodiment, the release of the PC5 RRC connection between the processing unit 1601 and the second remote device includes at least one of the following: It is assumed that a sidelink wireless link failure has been detected for the destination address corresponding to the relay device; Release the PC5 relay RLC channel, bearer, or entity between the relay device and the destination address corresponding to the relay device; Discard the associated settings for NR sidelink communication related to the destination address corresponding to the aforementioned relay device; A dedicated MAC is reset to the sidelink for the destination address corresponding to the relay device; The PC5-RRC connection between the relay device and the corresponding destination address is considered to have been released; The upper layer instructs the relay device to release the PC5 unicast link to the corresponding destination address; and This instructs the upper layer that a PC5-RRC connection has been released between the relay device and the corresponding destination address.

[0142] In some embodiments, the processing unit 1601 further includes at least one of the following operations, namely: Release the DRB for the destination address corresponding to the second remote device; Release the SRB for the destination address corresponding to the second remote device; Drop the NR sidelink communication settings related to the destination address corresponding to the second remote device; The PC5-RRC connection between the destination address corresponding to the second remote device is considered to have been released; The upper layer instructs the release of a PC5 unicast link between the destination address corresponding to the second remote device; and This instructs the upper layer that a PC5-RRC connection has been released between the second remote device and the corresponding destination address.

[0143] Although only the components or modules according to the present invention have been described above, the present invention is not limited to these. The side-link wireless link failure processing device 1600 in the embodiment of the present invention may further include other components or modules, and the specific details of these components or modules can be found in the relevant technologies.

[0144] Furthermore, for convenience, Figure 16 only shows the connection relationships or signal directions between each component or module; however, as those skilled in the art will understand, various related technologies such as bus connections may be employed. The above-mentioned components or modules may be realized by hardware such as processors, memory devices, transmitters, and receivers, but the implementation of the present invention is not limited thereto.

[0145] The apparatus in the embodiment of the present invention is advantageous for faster recovery of business transmission between the second remote device, reduces the signaling overhead of setting up the RRC layer, and eliminates the need to re-establish the PC5 unicast link by the NAS layer.

[0146] <Example of the sixth side view> An embodiment of the present invention provides a setting device. This device may be, for example, a network device, or one or more components or assemblies installed on a network device, or it may be a terminal device, or one or more components or assemblies installed on a terminal device. The principle by which this device solves the problem is the same as the method in the embodiment of the third aspect, so for its specific implementation, refer to the implementation of the method in the embodiment of the third aspect, and redundant explanations will be omitted here.

[0147] Figure 17 shows a setting device in an embodiment of the present invention. The device is shown as being installed in a network device. As shown in Figure 17, the setting device 1700 in the embodiment of the present invention includes the following: Setting unit 1701: Sets a third timer for the remote device, the value of which the third timer is greater than the value of timer T400, and the third timer is used for the remote device to perform RRC resetting related to the side link.

[0148] In some embodiments, the range of values ​​for the third timer is different from the range of values ​​for timer T400.

[0149] In some embodiments, the range of the third timer's value is within the range of the timer T400's value, and the range of the third timer's value is the maximum N values ​​within the range of the timer T400's value.

[0150] In some embodiments, for remote devices in an RRC idle or inactive state, the value of the third timer is set by SIB12, and / or for remote devices in an RRC connected state, the value of the third timer is set by an RRC reset message, and / or for remote devices outside network coverage, the value of the third timer is set by a pre-configuration.

[0151] In some embodiments, the value of the third timer is set for the indicator of the source remote device among the remote devices, or for the indicator of the destination remote device among the remote devices, or for a pair of source remote device indicators and destination remote device indicators.

[0152] In the above-described embodiment, the label is either an L2 ID or a local ID.

[0153] Figure 18 is another diagram showing a setting device in an embodiment of the present invention. For example, the device is a remote device located on an end-to-end relay (U2U relay). As shown in Figure 18, the setting device 1800 in an embodiment of the present invention includes the following: Setting unit 1801: Sets the value of the first timer T400 to a value obtained by adding or multiplying the value of the first timer T400 by the value of the second timer T400 set by the network device; and Processing unit 1802: When sending a side link RRC reset message, activates the first timer T400.

[0154] In some embodiments, the first value is a positive integer.

[0155] In some embodiments, the first value is either predefined or set by network equipment.

[0156] For example, for remote devices in an RRC idle or inactive state, the first value is set by SIB12, and / or for remote devices in an RRC connected state, the first value is set by an RRC reconfiguration message, and / or for remote devices outside network coverage, the first value is set by a pre-configuration.

[0157] In some embodiments, the first value is set for the label of the source remote device among the remote devices, or for the label of the destination remote device among the remote devices, or for a pair of source remote device labels and destination remote device labels.

[0158] In the above-described embodiment, the label is either an L2 ID or a local ID.

[0159] Figure 19 is another diagram showing a setting device in an embodiment of the present invention, taking the example of the device being installed on network equipment. As shown in Figure 19, the setting device 1900 in an embodiment of the present invention includes the following, namely, Setting unit 1901: Sets the range of values ​​for timer T400, and the second value within that range is set for the remote device in the end-to-end relay (U2U relay).

[0160] In the above-described embodiment, the second value is 1000 milliseconds, 1500 milliseconds, or 2000 milliseconds.

[0161] Although only the components or modules of the present invention have been described above, the present invention is not limited to these. The setting devices 1700-1900 in the embodiments of the present invention may further include other components or modules, and the specific details of these components or modules can be found in the relevant technologies.

[0162] Furthermore, for convenience, Figures 17-19 only show the connection relationships or signal directions between each component or module; however, as those skilled in the art will understand, various related technologies such as bus connections may be employed. The above-mentioned components or modules may be realized by hardware such as processors, memory devices, transmitters, and receivers, but the implementation of the present invention is not limited thereto.

[0163] The apparatus in the embodiment of the present invention can avoid sidelink wireless link failures caused by the set T400 value being inappropriate for the UE-to-UE relay scenario, thus benefiting from satisfying the business quality requirements of sidelink communication, reducing business interruptions, and improving the user experience.

[0164] <Example of the seventh side view> An embodiment of the present invention provides a communication system. Figure 20 shows a communication system in an embodiment of the present invention. As shown in Figure 20, the communication system 2000 includes a first remote device 2001, a second remote device 2002, and a relay device 2003. For convenience, Figure 20 uses one first remote device, one second remote device, and one relay device as examples, but embodiments of the present invention are not limited thereto.

[0165] In the embodiment of the present invention, the first remote device 2001, the second remote device 2002, and the relay device 2003 are in a UE-to-UE relay scenario.

[0166] In some embodiments, the first remote device 2001 and the second remote device 2002 are configured to perform the methods performed by the first and second remote devices in the embodiments of the first to third aspects, and the relay device 1003 is configured to perform the method performed by the relay device in the embodiment of the first aspect. Since each method is described in detail in the embodiments of the first to third aspects, that content is combined here and a detailed explanation is omitted here.

[0167] In some embodiments, the communication system 200 may further include network equipment (not shown) configured to perform the methods performed by the network equipment in the embodiments of the third aspect. Since the methods performed by the network equipment are described in detail in the embodiments of the third aspect, that content is combined here and described in detail here.

[0168] In embodiments of the present invention, terminal equipment is further provided, which may be, for example, a source UE (first remote device) in a UE-to-UE relay scenario, a target UE (second remote device) in a UE-to-UE relay scenario, or a relay UE (relay device) in a UE-to-UE relay scenario. However, the present invention is not limited to these, and other devices may also be provided.

[0169] Figure 21 shows a terminal device in an embodiment of the present invention. As shown in Figure 21, the terminal device 2100 may include a processor 2101 and a memory unit 2102, the memory unit 2102 storing data and programs and connected to the processor 2101. Note that this figure is merely illustrative, and telecommunications functions or other functions may be realized by supplementing or substituting other types of structures with this structure.

[0170] For example, the processor 2101 is configured to execute a program and perform the method performed by the remote device or relay device in the embodiment of the first, second, or third aspect.

[0171] As shown in Figure 21, the terminal device 2100 may further include a communication module 2103, an input unit 2104, a display unit 2105, a power supply 2106, and the like. Since the functions of these components are similar to those in the prior art, a detailed explanation is omitted here. Note that the terminal device 2100 does not need to include all the components shown in Figure 21. Furthermore, the terminal device 2100 may also include components not shown in Figure 21, for which prior art can be referenced.

[0172] In embodiments of the present invention, network equipment is further provided.

[0173] Figure 22 shows a network device in an embodiment of the present invention. As shown in Figure 22, the network device 2200 may include a processor (e.g., a central processor CPU) 2201 and a memory unit 2202, the memory unit 2202 being connected to the processor 2201. The memory unit 2202 can store various data, as well as information processing programs, and can execute these programs under the control of the central processor 2201.

[0174] For example, the processor 2201 is configured to execute a program and perform the method performed by the network device in the third embodiment.

[0175] Furthermore, as shown in Figure 22, the network device 2200 may also include a transceiver 2203, an antenna 2204, etc., and since the functions of the above-mentioned components are similar to those of the prior art, a detailed explanation is omitted here. Note that the network device 2200 does not need to include all the components shown in Figure 22. Also, the network device 1600 may include components not shown in Figure 22, for which prior art can be referenced.

[0176] In embodiments of the present invention, a computer-readable program is further provided, wherein when the program is executed on a terminal device, the program causes the computer to execute the method performed by the remote device or relay device in the embodiments of the first to third aspects on the terminal device.

[0177] In embodiments of the present invention, a storage medium storing a computer-readable program is further provided, wherein the computer-readable program causes a computer to execute the method performed by a remote device or relay device in the embodiments of the first to third aspects on a terminal device.

[0178] In embodiments of the present invention, a computer-readable program is further provided, wherein when the program is executed on a network device, the program causes the computer to execute the method performed by the network device in the embodiment of the third aspect.

[0179] In embodiments of the present invention, a storage medium storing a computer-readable program is further provided, wherein the computer-readable program causes a computer to execute the method performed by the network device in the embodiment of the third aspect on the network device.

[0180] Furthermore, the above-described apparatus and method may be implemented by software or hardware, or by a combination of hardware and software. The present invention further relates to a computer-readable program as described below, that is, the program, when executed by a logic component, causes the logic component to implement the above-described apparatus or component, or to the logic component to implement each of the above-described methods or steps. The logic component may be, for example, an FPGA (Field Programmable Gate Array), a microprocessor, or a processor used in a computer. The present invention further relates to a storage medium storing the above-described program, for example, a hard disk, a magnetic disk, an optical hard disk, a DVD, a flash memory, etc.

[0181] Furthermore, one or more combinations of the functional blocks shown in the drawings and / or one or more combinations of functional blocks may be implemented as a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic component, discrete gate or transistor logic component, discrete hardware assembly or any other suitable combination for performing the functions described herein. Also, one or more combinations of the functional blocks shown in the drawings and / or one or more combinations of functional blocks may further be configured as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors connected to a DSP by communication or any other combination of any other configuration.

[0182] Although preferred embodiments of the present invention have been described above, the present invention is not limited to such embodiments, and any modifications to the present invention that do not deviate from the spirit of the invention fall within the technical scope of the present invention.

[0183] Furthermore, the following additional information is disclosed regarding the above-mentioned embodiments.

[0184] (Note 1) A method for handling sidelink wireless link failures, which is applied to a first remote device, wherein the method is: The first remote device includes releasing a PC5 RRC connection, PC5 unicast link, or PC5 RLC channel between the first remote device and a relay device when a sidelink radio link failure (SL RLF) is detected between the first remote device and the second remote device, or when a higher layer in the first remote device requests the release of the PC5 RRC connection between the first remote device and the second remote device.

[0185] (Note 1a) The method described in Appendix 1, The release of the PC5 RRC connection, PC5 unicast link, or PC5 RLC channel between the first remote device and the relay device includes at least one of the following: Release the PC5 RRC connection or PC5 unicast link to the destination address of the relay device; Release the PC5 RRC connection or PC5 unicast link between the L2 ID of the first remote device and the L2 ID of the relay device; A device that releases a PC5 RRC connection or PC5 unicast link corresponding to one PC5 unicast link between the first remote device and the relay device.

[0186] (Note 2) The method described in Appendix 1, The release of the PC5 RRC connection, PC5 unicast link, or PC5 RLC channel between the first remote device and the relay device includes at least one of the following: It is assumed that a sidelink wireless link failure has been detected for the destination address corresponding to the relay device; Release the PC5 relay RLC channel, bearer, or entity between the relay device and the destination address corresponding to the relay device; Discard the associated settings for NR sidelink communication related to the destination address corresponding to the aforementioned relay device; A dedicated MAC is reset to the sidelink for the destination address corresponding to the relay device; The PC5-RRC connection between the relay device and the corresponding destination address is considered to have been released; The upper layer instructs the relay device to release the PC5 unicast link to the corresponding destination address; and This instructs the upper layer that a PC5-RRC connection for the destination address corresponding to the relay device has been released.

[0187] (Note 3) The method described in Appendix 2, The aforementioned upper layer includes a non-contact layer or a V2X (Vehicle-to-everything) layer.

[0188] (Note 4) A method for handling sidelink wireless link failures, which is applied to a first remote device, wherein the method is: The first remote device includes maintaining a PC5 RRC connection, PC5 unicast link, or PC5 RLC channel between the first remote device and a relay device when a sidelink radio link failure (SL RLF) is detected between the first remote device and the second remote device, or when a higher layer in the first remote device requests the release of the PC5 RRC connection between the first remote device and the second remote device.

[0189] (Note 4a) The method described in Appendix 4, The first remote device maintaining a PC5 RRC connection, PC5 unicast link, or PC5 RLC channel between the first remote device and the relay device includes at least one of the following: Maintain the PC5 RRC connection or PC5 unicast link for the destination address of the relay device; Maintain a PC5 RRC connection or PC5 unicast link between the L2 ID of the first remote device and the L2 ID of the relay device; and A device that maintains a PC5 RRC connection or PC5 unicast link corresponding to one PC5 unicast link between the first remote device and the relay device.

[0190] (Note 5) The method described in Appendix 4, wherein the method further includes: The first remote device includes determining that the relay device is a suitable relay device.

[0191] (Note 6) The method described in Appendix 4, wherein the method further includes: The first remote device transmits instruction information to the relay device, The aforementioned instruction information indicates that an end-to-end sidelink radio link failure has occurred.

[0192] (Note 6a) The method described in Appendix 6, The first remote device transmits the instruction information when an end-to-end sidelink wireless link failure is detected, or when the upper layer requests the release of the PC5 RRC connection with the second remote device, or after maintaining the PC5 RRC connection, PC5 unicast link, or PC5 RLC channel with the second remote device.

[0193] (Note 6b) The method described in Appendix 6, The instruction information includes bits or areas for indicating the cause of the failure, The cause of the failure includes the detection of an SL RLF for the destination address of the second remote device, or the detection of an end-to-end SL RLF.

[0194] (Note 7) The method described in Appendix 6, The instruction information is used by the relay device to perform at least one of the following operations, namely, The transmission of data to the destination address corresponding to the second remote device is stopped; It is assumed that a sidelink wireless link failure has been detected for the destination address corresponding to the second remote device; Release the PC5 relay RLC channel, bearer, or entity between the destination address corresponding to the second remote device; The relevant settings for NR sidelink communication regarding the destination address corresponding to the second remote device are dropped; A dedicated MAC is reset to the associated sidelink of the destination address corresponding to the second remote device; The PC5-RRC connection between the second remote device and the destination address corresponding to the aforementioned second remote device is considered to have been released; The upper layer instructs the release of a PC5 unicast link to the destination address corresponding to the second remote device; and This instructs the upper layer that a PC5-RRC connection has been released to the destination address corresponding to the second remote device.

[0195] (Note 8) The method described in Appendix 6, The aforementioned instruction information is transmitted via PC5-RRC messages, PC5-S signaling, SL MAC CE, or Sidelink Control Information (SCI).

[0196] (Note 9) A method described in any one of the appendices 1-8, The first remote device deems a sidelink radio link failure to have occurred with the second remote device when the timer T400 for the destination address corresponding to the second remote device expires, or when the sidelink PDCP entity indicates a failure in the integrity check for SL-SRB2 or SL-SRB3 for the destination address corresponding to the second remote device.

[0197] (Note 10) A method described in any one of the appendices 1-8, The first remote device, upon receiving a second instruction from the relay device indicating that a sidelink wireless link failure has been detected between it and the second remote device, deems that a sidelink wireless link failure has been detected between it and the second remote device.

[0198] (Note 11) A method for handling side link wireless link failures, applicable to relay equipment, wherein the method is: This includes the relay device receiving instruction information from the first remote device, The aforementioned instruction information indicates that an end-to-end sidelink radio link failure has occurred. The relay device performs at least one of the following operations based on the instruction information, namely, Stop sending data to the destination address corresponding to the second remote device; It is assumed that a sidelink wireless link failure has been detected for the destination address corresponding to the second remote device; Release the PC5 relay RLC channel, bearer, or entity between the destination address corresponding to the second remote device; The relevant settings for NR sidelink communication regarding the destination address corresponding to the second remote device are dropped; A dedicated MAC is reset to the associated sidelink of the destination address corresponding to the second remote device; The PC5-RRC connection between the second remote device and the destination address corresponding to the aforementioned second remote device is considered to have been released; The upper layer instructs the release of a PC5 unicast link to the destination address corresponding to the second remote device; and This instructs the upper layer to release a PC5-RRC connection to the destination address corresponding to the second remote device.

[0199] (Note 12) A method for handling sidelink wireless link failures, which is applied to a first remote device, wherein the method is: The first remote device includes maintaining a PC5 RRC connection or PC5 unicast link between the first remote device and the second remote device when a sidelink radio link failure (SL RLF) is detected between the first remote device and the second remote device.

[0200] (Note 13) The method described in Appendix 12, wherein the method further includes: The first remote device performs at least one of the following operations, that is, suspends the DRB of the second remote device or relay device; suspends the SRB of the second remote device or relay device; resets the MAC dedicated to the sidelink of the second remote device or relay device; configures integrity protection and encryption of the SRB suspended by the PDCP layer; starts a first timer; starts a second timer; and saves the settings of the RRC layer and / or PDCP layer.

[0201] (Appendix 14) The method according to Appendix 13, wherein the first timer is used for the first remote device to re-establish or resume the PC5 RRC connection with the second remote device, and the second timer is used for the first remote device to perform reselection of the relay device.

[0202] (Appendix 15) The method according to Appendix 13, wherein the method further comprises the first remote device performs reselection of the relay device; and when the first remote device reselects the relay device, it includes stopping the second timer.

[0203] (Appendix 16) The method according to Appendix 15, wherein the method further comprises when the first remote device stops the second timer and starts the first timer.

[0204] (Appendix 17) The method according to Appendix 13, wherein the method further comprises the first remote device re-establishes or resumes the RC5 RRC connection with the second remote device, When the PC5 RRC connection between the first remote device and the second remote device is re-established or successfully restored, the first remote device shall perform at least one of the following operations, namely: Stop the first timer; Re-establish the PDCP entities of the DRB and / or SRB of the second remote device or relay device; Re-establish the RLC entities of the DRB and / or SRB of the second remote device or relay device; For the DRB and / or SRB of the second remote device or relay device, apply the settings prior to SL-RLF, or apply the default settings, or apply the predefined settings; Restart the DRB and / or SRB of the second remote device or relay device; Generate at least one new secret key, namely, a secret key for encryption of the sidelink SRB of the second remote device or relay device, a secret key for integrity protection of the sidelink SRB of the second remote device or relay device, a secret key for encryption of the sidelink DRB of the second remote device or relay device, and a secret key for integrity protection of the sidelink DRB of the second remote device or relay device; and This configuration sets up integrity protection and encryption for the SRB of the second remote device or relay device, which is restarted by the PDCP layer.

[0205] (Note 18) A method according to any one of the appendices 13-17, wherein the method further includes: The first remote device includes releasing the PC5 RRC connection with the second remote device when the first timer expires, or when the second timer expires, or when the re-selected relay device becomes inappropriate, or when the higher layer of the first remote device instructs the release of the PC5 unicast link with the second remote device.

[0206] (Note 19) The method described in Appendix 18, The release of the PC5 RRC connection between the first remote device and the second remote device includes at least one of the following: It is assumed that a sidelink wireless link failure has been detected for the destination address corresponding to the aforementioned relay device; Release the PC5 relay RLC channel, bearer, or entity between the relay device and the destination address corresponding to the relay device; Discard the associated settings for NR sidelink communication related to the destination address corresponding to the aforementioned relay device; A dedicated MAC is reset to the sidelink for the destination address corresponding to the relay device; The PC5-RRC connection between the relay device and the corresponding destination address is considered to have been released; The upper layer instructs the relay device to release the PC5 unicast link to the destination address corresponding to the relay device; and This instructs the upper layer that a PC5-RRC connection for the destination address corresponding to the relay device has been released.

[0207] (Note 20) The method described in Appendix 18, wherein the method further includes: The first remote device performs at least one of the following operations, namely, Release the DRB for the destination address corresponding to the second remote device; Release the SRB for the destination address corresponding to the second remote device; The relevant settings for NR sidelink communication regarding the destination address corresponding to the second remote device are dropped; The PC5-RRC connection between the second remote device and the destination address corresponding to the aforementioned second remote device is considered to have been released; The upper layer instructs the release of a PC5 unicast link to the destination address corresponding to the second remote device; and An apparatus for instructing to release a PC5-RRC connection with a destination address corresponding to the second remote device to an upper layer.

[0208] (Appendix 21) A setting method applicable to a network device, wherein the method includes: The network device sets a third timer for a remote device, where the value of the third timer is greater than the value of timer T400, and the third timer is used for the remote device to perform an RRC reconfiguration related to sidelink.

[0209] (Appendix 22) The method according to Appendix 21, wherein the range of the value of the third timer is different from the range of the value of timer T400.

[0210] (Appendix 23) The method according to Appendix 21, wherein the range of the value of the third timer is within the range of the value of timer T400, and the range of the value of the third timer is the largest N values within the range of the value of timer T400.

[0211] (Appendix 24) The method according to any one of Appendices 21 to 23, wherein for the remote device in the RRC idle state or non-active state, the value of the third timer is set in SIB12; and / or for the remote device in the RRC connected state, the value of the third timer is set in an RRC reconfiguration message; and / or for the remote device outside the network coverage, the value of the third timer is set by pre-configuration.

[0212] (Appendix 25) The method according to any one of Appendices 21 to 24, wherein The value of the third timer is set for the indicator of the source remote device among the remote devices, or for the indicator of the destination remote device among the remote devices, or for a pair of indicators of the source remote device and the destination remote device.

[0213] (Note 26) The method described in Appendix 25, The aforementioned identifier is either an L2 ID or a local ID.

[0214] (Note 27) A configuration method applicable to remote devices in an end-to-end relay (U2U relay), wherein the method is: In an end-to-end relay (U2U relay), the remote device sets the value of the first timer T400 to a value obtained by adding or multiplying the value of the first timer T400 by the value of the second timer T400 set by the network device; and This includes activating the first timer T400 when the remote device sends a sidelink RRC reset message.

[0215] (Note 28) The method described in Appendix 27, The first value mentioned above is a positive integer.

[0216] (Note 29) The method described in Appendix 27, The aforementioned first value is one that is predefined or set by network equipment.

[0217] (Note 30) The method described in Appendix 29, For the remote device in an RRC idle or inactive state, the first value is set in SIB12; and / or For the remote device in an RRC connection state, the first value is set by the RRC reset message; and / or For the remote device located outside the network coverage, the first value is set in advance.

[0218] (Note 31) A method according to any one of the items in Appendix 27-30, The first value is set for the label of the source remote device among the remote devices, or for the label of the destination remote device among the remote devices, or for a pair of source remote device labels and destination remote device labels.

[0219] (Note 32) The method described in Appendix 31, The aforementioned identifier is either an L2 ID or a local ID.

[0220] (Note 33) A configuration method applicable to network equipment, wherein the method is The network device includes setting a range of values ​​for timer T400, Of these, the second value within the aforementioned range is set for the remote device in the end-to-end relay (U2U relay).

[0221] (Note 34) The method described in Appendix 33, The second value is 1000 milliseconds, 1500 milliseconds, or 2000 milliseconds.

[0222] (Note 35) Terminal device, A device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program and perform the method described in any one of the appendices 1-20 and 27-32.

[0223] (Note 36) Network equipment, A device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program and perform the method described in any one of the appendices 21-26 and 33-34.

[0224] (Note 37) It is a communication system, Including the first remote device, the second remote device, and relay devices, The first remote device is configured to perform the method described in any one of the appendices 1-10, 12-20, and 27-32, The relay device is configured to perform the method described in Appendix 11, The second remote device is configured to perform end-to-end communication with the first remote device via the relay device.

[0225] (Note 38) The system described in Appendix 37, The present invention further includes network equipment, wherein the network equipment is configured to perform the method described in any one of the appendices 21-26 and 33-34.

Claims

1. A side link wireless link failure processing device, which is located in a first remote device, and of which the device is A device comprising a processing unit which releases the PC5 RRC connection, PC5 unicast link, or PC5 RLC channel between the first remote device and a relay device when a sidelink radio link failure (SL RLF) is detected between the first remote device and the second remote device, or when the upper layer in the first remote device requests the release of the PC5 RRC connection between the first remote device and the second remote device.

2. The apparatus according to claim 1, The processing unit releasing the PC5 RRC connection, PC5 unicast link, or PC5 RLC channel between the first remote device and the relay device includes at least one of the following: It is assumed that a sidelink wireless link failure has been detected for the destination address corresponding to the relay device; Release the PC5 relay RLC channel, bearer, or entity between the destination addresses corresponding to the relay equipment; Discard the associated settings for NR sidelink communication related to the destination address corresponding to the relay device; Reset a dedicated MAC to the side link for the destination address corresponding to the relay device; The PC5-RRC connection between the relay device and the corresponding destination address is considered to be released; The upper layer is instructed to release the PC5 unicast link to the destination address corresponding to the relay device; A device that instructs the upper layer that a PC5-RRC connection to the destination address corresponding to the relay device has been released.

3. The apparatus according to claim 2, The apparatus wherein the upper layer includes a non-contact layer or a V2X (Vehicle-to-everything) layer.

4. The apparatus according to claim 1, The processing unit is a device that determines that a sidelink wireless link failure has been detected with the second remote device when the timer T400 for the destination address corresponding to the second remote device expires, or when the sidelink PDCP entity indicates a failure in the integrity check for SL-SRB2 or SL-SRB3 of the destination address corresponding to the second remote device.

5. The apparatus according to claim 1, The processing unit is a device that, when it receives second instruction information from the relay device indicating that a sidelink wireless link failure has been detected between it and the second remote device, determines that a sidelink wireless link failure has been detected between it and the second remote device.

6. A side link wireless link failure processing device, which is located in a first remote device, and of which the device is A device including a processing unit which maintains a PC5 RRC connection or PC5 unicast link between the first remote device and the second remote device when a sidelink radio link failure (SL RLF) is detected between the first and second remote devices.

7. The apparatus according to claim 6, The processing unit performs at least one of the following operations, namely, The DRB of the second remote device or relay device is suspended; The SRB of the second remote device or relay device is suspended; A dedicated MAC is reset to the side link of the second remote device or relay device; The PDCP layer provides integrity protection and encryption for the suspended SRB; Start the first timer; The second timer is activated; and A device for saving the settings of the RRC layer and / or PDCP layer.

8. The apparatus according to claim 7, The first timer is used by the first remote device to re-establish or restore the PC5 RRC connection with the second remote device, and the second timer is used by the first remote device to re-select the relay device.

9. The apparatus according to claim 7, The processing unit further performs a re-selection of the relay equipment, The processing unit is a device that stops the second timer when the relay equipment is re-selected.

10. The apparatus according to claim 9, The processing unit is a device that starts the first timer when it stops the second timer.

11. The apparatus according to claim 7, The processing unit further re-establishes or restores the RC5 RRC connection with the second remote device. When the PC5 RRC connection with the second remote device is re-established or successfully restored, the processing unit performs at least one of the following operations, namely: Stop the first timer; Re-establish the PDCP entities of the DRB and / or SRB of the second remote device or relay device; Re-establish the RLC entities of the DRB and / or SRB of the second remote device or relay device; Apply the settings prior to SL-RLF, the default settings, or the predefined settings to the DRB and / or SRB of the second remote device or relay device; Restart the DRB and / or SRB of the second remote device or relay device; Generate at least one new secret key, namely, a secret key for encryption of the sidelink SRB of the second remote device or relay device, a secret key for integrity protection of the sidelink SRB of the second remote device or relay device, a secret key for encryption of the sidelink DRB of the second remote device or relay device, and a secret key for integrity protection of the sidelink DRB of the second remote device or relay device; and A device for configuring integrity protection and encryption for the SRB of the second remote device or relay device, which is restarted by the PDCP layer.

12. The apparatus according to claim 7, The processing unit is a device that releases the PC5 RRC connection between the second remote device and the first remote device when the first timer expires, or when the second timer expires, or when the re-selected relay device becomes inappropriate, or when the upper layer of the first remote device instructs the release of the PC5 unicast link between it and the second remote device.

13. The apparatus according to claim 12, The processing unit releasing the PC5 RRC connection with the second remote device includes at least one of the following: It is assumed that a sidelink radio link failure has been detected for the destination address corresponding to the aforementioned relay device; Release the PC5 relay RLC channel, bearer, or entity between the relay device and the destination address corresponding to the relay device; The relevant settings for NR sidelink communication regarding the destination address corresponding to the relay device are dropped; Reset a dedicated MAC to the side link for the destination address corresponding to the relay device; The PC5-RRC connection between the relay device and the corresponding destination address is considered to be released; The upper layer instructs the relay device to release the PC5 unicast link to the destination address corresponding to the relay device; and A device that instructs the upper layer that a PC5-RRC connection for the destination address corresponding to the relay device has been released.

14. The apparatus according to claim 12, The processing unit further performs at least one of the following operations, namely, Release the DRB for the destination address corresponding to the second remote device; Release the SRB for the destination address corresponding to the second remote device; The relevant settings for NR sidelink communication regarding the destination address corresponding to the second remote device are dropped; It is assumed that the PC5-RRC connection between the second remote device and the destination address corresponding to the second remote device has been released; The upper layer instructs the PC5 unicast link to be released between the destination address corresponding to the second remote device; and A device that instructs the upper layer that it has released a PC5-RRC connection to the destination address corresponding to the second remote device.

15. A setting device, which is placed on network equipment, and of which the device is A device including a setting unit which sets a third timer for a remote device, the value of which the third timer is greater than the value of timer T400, and the third timer is used by the remote device to perform RRC resetting with respect to the side link.

16. The apparatus according to claim 15, The range of values ​​for the third timer is different from the range of values ​​for the timer T400 in the device.

17. The apparatus according to claim 15, The range of values ​​for the third timer is within the range of values ​​for the timer T400, and the range of values ​​for the third timer is the maximum N values ​​within the range of values ​​for the timer T400, in this apparatus.

18. The apparatus according to claim 15, For the remote device in an RRC idle or inactive state, the value of the third timer is set by SIB12; and / or For the remote device in the RRC connection state, the value of the third timer is set by the RRC reset message; and / or For the remote device located outside network coverage, the value of the third timer is set in advance.

19. The apparatus according to claim 15, A device in which the value of the third timer is set for the indicator of the source remote device among the remote devices, or for the indicator of the destination remote device among the remote devices, or for a pair of indicators of a source remote device and a destination remote device.

20. The apparatus according to claim 19, The aforementioned identifier is an L2 ID or local ID in the device.

Images