Fault information transmission method, reception method, device, and system

By configuring multiple paths for a remote user device to transmit fault information via an alternate path upon failure, the solution addresses the issue of prolonged interruptions and delays in UE-to-network relay, enhancing user experience.

JP7800730B2Active Publication Date: 2026-01-161FINITY INC
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
JP2024561565
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2022-04-19
Publication Date
2026-01-16
Estimated Expiration
2042-04-19

AI Technical Summary

Technical Problem

The UE-to-network relay in Release 17 only supports a single path, leading to prolonged service interruption times and increased transmission delay due to RRC connection re-establishment when path failures occur, degrading user experience.

Method used

Configuring or activating two paths for a remote user device, allowing it to transmit fault information via the second path when a failure occurs on the first path, thereby reducing service interruption time.

Benefits of technology

Reduces service interruption time and guarantees service delay by enabling fault information transmission through an alternative path, improving user experience.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007800730000001
    Figure 0007800730000001
  • Figure 0007800730000002
    Figure 0007800730000002
  • Figure 0007800730000003
    Figure 0007800730000003
Patent Text Reader

Abstract

An embodiment of the present invention provides a method, an apparatus and a system for transmitting fault information, the method including: transmitting configuration information to a remote user device, the configuration information including information for adding and / or modifying and / or deleting a path, the path being a direct path and / or an indirect path between the remote user device and a network device.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

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

[0002] Release 17 considers sidelink relay (SL relay), which includes a UE-to-Network relay scenario. In this scenario, a remote user equipment (UE) communicates with a network device via a relay user equipment (relay UE). Here, the relay user equipment (UE) uses NR Uu on its Uu link, and NR sidelink on the PC5 interface between the remote user equipment (UE) and the relay user equipment (REE) uses NR sidelink. In the UE-to-Network Relay scenario, the relay UE is also referred to as a UE-to-Network relay UE.

[0003] The above description of the background art is merely for the purpose of explaining the configuration of the present invention more clearly and completely, and is provided for the understanding of those skilled in the art. These configurations described in the background art of the present invention should not be construed as being well known to those skilled in the art. Summary of the Invention [Problem to be solved by the invention]

[0004] According to the discovery of the present inventors, the UE-to-network relay in Release 17 only supports a single path, i.e., the remote UE communicates with the network device (e.g., gNB) via the relay UE. In the RRC_Connected state, the remote UE suspends Radio Link Monitoring (RLM) of the Uu interface.

[0005] The Relay UE monitors the radio link of its Uu interface. When a Uu RLF is detected, the Relay UE sends a message to the Remote UE to notify it that a Uu RLF has occurred in the Relay UE. This message triggers the Remote UE to perform an RRC connection re-establishment procedure.

[0006] In addition, the remote UE monitors the radio link quality of the PC5 interface, for example, based on the sidelink HARQ feedback of the PC5 interface to detect whether a PC5 RLF occurs. When the remote UE detects a PC5 RLF, the remote UE in the RRC_Connected state can also trigger an RRC connection re-establishment.

[0007] Because the remote UE in Release 17 does not support communication with the network using multiple routes, when the remote UE detects an RLF on the PC5 interface or receives a PC5-RRC message sent by the relay UE to notify the relay UE of a Uu RLF, an RRC connection re-establishment is triggered, or when the remote UE detects an RLF on the Uu interface, an RRC connection re-establishment is triggered, which prolongs the service interruption time of the remote UE, increases transmission delay, and degrades the user experience.

[0008] Release 18 considers a scheme to support multi-path (or multiple path). A multi-path scenario may be that a remote user equipment is connected to the same network device (e.g., gNB) using one direct path and one indirect path simultaneously. For example, a direct path may be that the remote user equipment is directly connected to the network device via a Uu interface, and an indirect path may be that the remote user equipment is connected to the network device via a Layer-2 (L2) UE-to-Network relay.

[0009] In a multi-path scheme, there is currently no solution as to how to reduce the service interruption time of a user device when a path failure occurs.

[0010] In view of at least one of the above problems, embodiments of the present invention provide a method, an apparatus and a system for transmitting and receiving fault information. [Means for solving the problem]

[0011] In one aspect of an embodiment of the present invention, there is provided a device for transmitting fault information of a remote user device, wherein the remote user device has a first path and a second path configured or activated, and includes a transmitter that transmits fault information to a network device via the second path when a fault occurs on the first path.

[0012] Another aspect of an embodiment of the present invention provides a method for transmitting fault information of a remote user device, the method including the step of transmitting fault information to a network device via the second path when a fault occurs in the first path, wherein the remote user device has a first path and a second path configured or activated.

[0013] Another aspect of the present invention provides a remote user device including a memory having a computer program stored therein and a processor, the processor configured to execute the computer program to realize the method for transmitting fault information described in another aspect of the present invention.

[0014] Another aspect of an embodiment of the present invention provides a fault information receiving device, the device including: a receiving unit that receives fault information transmitted by a remote user device via a second path when a fault occurs in a first path, the remote user device having the first path and the second path configured or activated.

[0015] Another aspect of an embodiment of the present invention provides a method for receiving fault information, the method including: receiving fault information transmitted by a remote user device via a second path when a fault occurs in a first path, the remote user device having the first path and the second path configured or activated.

[0016] Another aspect of the present invention provides a network device including a memory having a computer program stored therein, and a processor, the processor configured to execute the computer program to realize the method for receiving fault information described in another aspect of the present invention.

[0017] In another aspect of the present invention, there is provided a communication system including a network device and / or a remote user device according to the another aspect of the present invention.

[0018] One of the advantageous effects of the embodiment of the present invention is that when two or more paths (a first path and a second path) are configured or activated for a remote user device and a failure occurs on the first path, the remote user device sends failure information to a network device via the second path, thereby reducing the service interruption time of the user device, guaranteeing service delay, and improving user experience.

[0019] As shown in the following description and drawings, specific embodiments of the present invention are disclosed in detail to illustrate ways in which the principles of the present invention can be employed. However, the scope of the present invention is not limited to these embodiments. The present invention encompasses all modifications, alterations, and equivalents within the spirit and scope of the appended claims.

[0020] Features described and / or shown in one embodiment may be used in the same or similar manner in one or more other embodiments, may be combined with features in other embodiments, or may be substituted for features in other embodiments.

[0021] It should be noted that in this text, the term "comprise / have" means the presence of a feature, element, step or component, and does not exclude the presence or addition of one or more other features, elements, steps or components. [Brief explanation of the drawings]

[0022] Elements and features depicted in one drawing and one embodiment of an example of the invention may be combined with elements and features shown in one or more drawings or embodiments, and in the drawings, like reference numerals may indicate corresponding elements in multiple drawings and may indicate corresponding elements used in more than one embodiment. [Figure 1] FIG. 1 is a schematic diagram of an example of scenario 1 for relaying from a remote user device to a network. [Figure 2] FIG. 10 is a schematic diagram of an example of scenario 2 for relaying from a remote user device to a network. [Figure 3] FIG. 10 is a schematic diagram of an example of a remote user device to network relay scenario 3. [Figure 4] 1 is a schematic diagram of a communication system according to an embodiment of the present invention; [Figure 5] FIG. 2 is a schematic diagram of an example of a multi-path scenario according to an embodiment of the present invention; [Figure 6] FIG. 2 is a schematic diagram of an example of a multi-path protocol stack structure according to an embodiment of the present invention; [Figure 7] FIG. 2 is a schematic diagram illustrating an example of a method for transmitting fault information according to the first embodiment of the present invention. [Figure 8] FIG. 2 is a schematic diagram of an example of a scenario of a route failure according to the first embodiment of the present invention. [Figure 9] FIG. 10 is a schematic diagram of another example of a scenario of a path failure according to the first embodiment of the present invention. [Figure 10] FIG. 10 is a schematic diagram of another example of a scenario of a path failure according to the first embodiment of the present invention. [Figure 11] FIG. 10 is a schematic diagram of another example of a scenario of a path failure according to the first embodiment of the present invention. [Figure 12] FIG. 10 is a schematic diagram illustrating an example of a fault information transmitting device according to a second embodiment of the present invention. [Figure 13] FIG. 10 is a schematic diagram illustrating an example of a method for receiving fault information according to a third embodiment of the present invention. [Figure 14] FIG. 10 is a schematic diagram illustrating an example of a fault information receiving device according to a fourth embodiment of the present invention. [Figure 15] FIG. 10 is a schematic diagram illustrating the configuration of a terminal device according to a fifth embodiment of the present invention. [Figure 16] FIG. 10 is a schematic diagram illustrating the configuration of a network device according to a fifth embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

[0023] The above and other features of the present invention will become apparent from the following description. In the specification and drawings, specific embodiments of the present invention are disclosed in detail, and some of the embodiments in which the principles of the present invention can be adopted are shown. However, the present invention is not limited to the described embodiments. The present invention includes all modifications, variations, and equivalents within the scope of the appended claims. Below, 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.

[0024] In embodiments of the present invention, the terms "first," "second," etc. are used in titles to distinguish between different elements, but do not represent the spatial arrangement or temporal order of these elements, and these elements are not limited to these terms. The term "and / or" includes any and all combinations of one or more of the terms listed in the associated list. The terms "comprise," "include," "have," etc. refer to the presence of listed features, elements, elements, or components, but do not exclude the presence or addition of one or more other features, elements, elements, or components.

[0025] In the embodiments of the present invention, the singular forms "one," "the," etc., include the plural and should be understood broadly as "one kind" or "one class," and are not limited to "one." Furthermore, the term "said" should be understood to include both the singular and the plural, unless the context clearly indicates otherwise. Furthermore, the term "described in" should be understood to mean "described at least in part," and the term "based on" should be understood to mean "based at least in part," unless the context clearly indicates otherwise.

[0026] 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, for example, Long Term Evolution (LTE), Long Term Evolution Advanced (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0027] Additionally, communications between devices in a communications system may occur according to any stage of communications protocol, including, but not limited to, 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, and future 5G, New Radio (NR), etc., and / or other currently known or future developed communications protocols.

[0028] In an embodiment of the present invention, the term "network device" refers to a device in a communication system that allows a terminal device to access the communication system and provides a service to the terminal device, and may include, but is not limited to, a base station (BS), an access point (AP), a transmission reception point (TRP), a broadcast transmitter, a mobility management entity (MME), a gateway, a server, a radio network controller (RNC), a base station controller (BSC), etc.

[0029] Here, the base station may include, but is not limited to, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), a 5G base station (gNB), etc., as well as a remote radio head (RRH), a remote radio unit (RRU), a relay, or a low-power node (e.g., femto, pico, etc.). Also, the term "base station" may include some or all of these functions, and each base station may provide communication coverage for a particular geographic area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0030] In the embodiments of the present invention, the term "User Equipment" (UE) or "Terminal Equipment" (TE) refers to a device that accesses a communication network and receives network services via, for example, a network device. The terminal device may be fixed or mobile, and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), a station, etc.

[0031] Here, the terminal device may include, but is not limited to, a cellular phone, a personal digital assistant (PDA), a wireless modulation / demodulation device, a wireless communication device, a handheld device, a machine-type communication device, a laptop computer, a cordless phone, a smartphone, a smart watch, a digital camera, etc.

[0032] Also, for example, in a scenario such as the Internet of Things (IoT), the user equipment may be a monitoring or measuring device or apparatus, and may include, but is not limited to, a Machine Type Communication (MTC) terminal, an in-vehicle communication terminal, a Device to Device (D2D) terminal, a Machine to Machine (M2M) terminal, etc.

[0033] Furthermore, the term "network side" or "network device side" refers to the network side, which may be a base station or may include one or more of the network devices described above. Furthermore, the term "user side" or "terminal side" or "terminal device side" refers to the user or terminal side, which may be a UE or may include one or more of the terminal devices described above. Unless otherwise specified in this specification, "device" may refer to either a network device or a terminal device.

[0034] The following describes a UE-to-Network Relay scenario as an example, but the present invention is not limited thereto.

[0035] FIG. 1 is a schematic diagram of an example of a scenario 1 for relaying from a remote user device to a network, FIG. 2 is a schematic diagram of an example of a scenario 2 for relaying from a remote user device to a network, and FIG. 3 is a schematic diagram of an example of a scenario 3 for relaying from a remote user device to a network.

[0036] As shown in FIG. 1, in scenario 1, a first terminal device 101 (remote user equipment, remote UE) is out of coverage (OOC) of a network device 103, and a second terminal device 102 (relay user equipment, relay UE) is in coverage (IC) of the network device 103.

[0037] As shown in Figure 2, in scenario 2, a first terminal device 101 (remote user device) is in coverage (IC) of a network device 103, and a second terminal device 102 (relay user device) is in coverage (IC) of the network device 103.

[0038] As shown in FIG. 3, in scenario 3, a first terminal device 101 (remote user device) is within the coverage range of a network device 103, and a second terminal device 102 (relay user device) is within the coverage range of another network device 103'.

[0039] 4 is a schematic diagram of a communication system according to an embodiment of the present invention, illustrating an example of a remote user device, a relay user device, and a network device. As shown in FIG. 4, the communication system 400 may include a remote user device 401, a relay user device 402, and a network device 403, and the remote user device 401 is connected to the network device 403 via a direct path and an indirect path. For convenience of explanation, FIG. 4 illustrates only two terminal devices (one remote user device and one relay user device) and one network device as an example, but the embodiment of the present invention is not limited thereto.

[0040] In an embodiment of the present invention, existing services or future services may be carried between the network device 403, the remote user device 401, and the relay user device 402. For example, these services may include, but are not limited to, enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable and low-latency communication (URLLC).

[0041] 5 is a schematic diagram of an example of a multi-path scenario according to an embodiment of the present invention. As shown in FIG. 5, in an embodiment of the present invention, a remote user device can simultaneously communicate with a network device via both a direct path and an indirect path. For example, a remote user device can communicate with a network device via a Uu interface (direct path) and with the same network device via a relay user device (indirect path).

[0042] 6 is a schematic diagram of an example of a multi-path protocol stack structure according to an embodiment of the present invention. As shown in FIG. 6, the direct path between the remote user equipment and the network device uses the protocol stack of the Uu interface, and the indirect path between the remote user equipment and the network device is transmitted via L2 UE-to-Network relay using the protocol stacks of the PC5 interface and the Uu interface.

[0043] In some embodiments, as shown in FIG. 6, the RRC layer, SDAP layer, and PDCP layer in the remote user equipment correspond to the RRC layer, SDAP layer, and PDCP layer in the network device, and PDCP layer data of the remote user equipment may be transmitted to the network device via an indirect route via a relay user equipment. For example, a PDCP PDU of the remote user equipment may be transmitted to the relay user equipment (UE) via PC5-SRAP, PC5-RLC, PC5-MAC, and PC5-PHY. The relay user equipment transmits data to the gNB via its Uu interface protocol stack (Uu-SRAP, Uu-RLC, Uu-MAC, and Uu-PHY), and the gNB receives the data from the Uu interface protocol stack corresponding to the relay user equipment and transmits it to the gNB's Uu-PDCP for processing. Alternatively, the PDCP layer data of the remote user equipment may be transmitted to the network device via a direct route. For example, a remote user equipment PDCP PDU may be sent to the gNB via Uu-RLC, Uu-MAC, and Uu-PHY, and the protocol stack of the Uu interface corresponding to the remote UE on the gNB side may receive the data and send it to the Uu-PDCP of the gNB for processing. Also, in the direct path and / or indirect path, one or more RLC entities (Uu-RLC entities or PC5-RLC entities) may be associated with one radio bearer PDCP entity.

[0044] In some embodiments, a single Uu-MAC entity may be used in the protocol stack on the gNB side to process data for remote user equipment and relay user equipment.

[0045] In some embodiments, a single MAC entity may be used in the remote user equipment to perform PC5-MAC and Uu-MAC operations.

[0046] Hereinafter, various aspects of the embodiments of the present invention will be described with reference to the drawings. These aspects are merely illustrative and do not limit the present invention.

[0047] Example 1 An embodiment of the present invention provides a method for transmitting fault information, and the method is applied to a remote user equipment, for example, the method is applied to the remote user equipment (remote UE) 401 in FIG.

[0048] 7 is a schematic diagram of an example of a fault information transmission method according to the first embodiment of the present invention. As shown in FIG. 7, the method includes the following steps:

[0049] Step 701: When a failure occurs on the first path, the remote user device sends failure information via the second path.

[0050] Although the above has outlined an embodiment of the present invention with reference to Figure 7, the present invention is not limited to this. For example, the execution order of each operation may be appropriately adjusted, some other operations may be added, or some of these operations may be deleted. Those skilled in the art will be able to make appropriate modifications to the above content without being limited to the description of Figure 7.

[0051] According to this embodiment, two or more paths (first path and second path) are configured or activated for a remote user device, and when a failure occurs on the first path, the remote user device sends failure information to the network device via the second path, thereby reducing the service interruption time of the user device, guaranteeing service delays, and improving user experience.

[0052] In some embodiments, a remote user device has at least two paths (a first path and a second path) configured or activated, the remote user device can communicate with a network device via at least one path, and if a first path of the at least two paths fails, the remote user device transmits failure information to the network device via an available second path of the at least two paths.

[0053] In some embodiments, the remote user equipment is configured with at least two paths (a first path and a second path). At least one of the at least two paths may be activated or used for a signaling radio bearer. For a data radio bearer, both of the at least two paths may be activated, one path may be activated and the other path may not be activated, or none of the at least two paths may be activated.

[0054] In some embodiments, the remote user equipment has at least two paths (a first path and a second path) activated, and for at least one data radio bearer, the remote user equipment may communicate with the network device via the at least two paths, e.g., via the first path and the second path.

[0055] In some embodiments, the first path may be a direct path or an indirect path, and the second path may be a direct path or an indirect path. For example, the first path is a direct path and the second path is an indirect path. As another example, the first path is an indirect path and the second path is a direct path.

[0056] In some embodiments, the path failure may include at least one of the following: The remote user equipment detects a radio link failure (RLF) on the PC5 interface of the remote user equipment; The remote user equipment receives a notification of a RLF on the Uu interface of the relay user equipment or a radio resource control (RRC) connection failure of the relay user equipment sent from the relay user equipment, or a handover of the relay user equipment, or a beam failure recovery (BFR) failure of the relay user equipment; The remote user equipment detects a beam failure on the PC5 interface or a failure to perform beam failure recovery (e.g., the remote user equipment detects a beam failure on the PC5 interface and then attempts beam failure recovery, but the recovery fails). A failure occurs in establishing a PC5 connection between the remote user equipment and the relay user equipment, for example, the remote user equipment does not discover, select, or reselect the relay user equipment, or does not receive a relay user equipment direct communication accept message, or receives a relay user equipment direct communication reject message, or is unable to follow the configuration after receiving a relay user equipment RRC reconfiguration sidelink, or receives a relay user equipment RRC reconfiguration sidelink failure message. The remote user equipment detects an RLF on the Uu interface of the remote user equipment, for example, the remote user equipment performs radio link monitoring (RLM) on the Uu interface and determines that an RLF has been detected when the T310 timer times out. The remote user equipment detects a beam failure or BFR failure on the Uu interface.A failure occurs in the synchronous reconfiguration of the PC5 interface and / or the Uu interface of the remote user equipment, for example, the remote user equipment receives an RRC reconfiguration message with a reconfiguration with sync IE sent by the network equipment and performs a path switch procedure on the PC5 interface and / or a random access procedure on the Uu interface, but the procedure is unsuccessful (for example, the path switch timer or the T304 timer times out). Alternatively, a failure occurs in the configuration of the PC5 interface and / or the Uu interface of the remote user equipment, for example, the remote user equipment cannot comply with the configuration of the PC5 interface and / or the Uu interface by the network equipment. That is, the path failure may include any of the above situations or any combination thereof.

[0057] For example, if the first path is a direct path, the failure of the first path may include at least one of the following: the remote user equipment detects an RLF on the Uu interface; the remote user equipment detects a beam failure or a BFR on the Uu interface; a failure in synchronous reconfiguration of the Uu interface of the remote user equipment; or a failure in configuration of the Uu interface of the remote user equipment. That is, the path failure of the direct path may include any of the above situations or any combination of the above scenarios.

[0058] 8 is a schematic diagram of an example of a path failure scenario according to the first embodiment of the present invention, illustrating a direct path failure scenario. As shown in FIG. 8, the direct path failure may be a Uu interface failure between a remote user device and a network device. In this case, the remote user device may send failure information to the network device via an available indirect path.

[0059] Also, for example, if the first path is an indirect path, the failure of the first path may include at least one of the following: the remote user equipment detecting an RLF on the PC5 interface; the remote user equipment detecting a beam failure or BFR on the PC5 interface; the remote user equipment receiving a notification of an RLF on the Uu interface of the relay user equipment sent by the relay user equipment, or an RRC connection failure of the relay user equipment, or a handover of the relay user equipment, or a BFR failure of the relay user equipment; a failure in establishing a PC5 connection between the remote user equipment and the relay user equipment; a failure in synchronous reconfiguration of the PC5 interface of the remote user equipment; or a failure in configuration of the PC5 interface of the remote user equipment. That is, the path failure of the indirect path may include any of the above situations or any combination of these situations.

[0060] 9 is a schematic diagram of another example of a path failure scenario according to the first embodiment of the present invention, illustrating an indirect path failure scenario. As shown in FIG. 9, the indirect path failure may be a failure of a PC5 interface between a remote user device and a relay user device.

[0061] For example, if the remote user device detects an RLF on the PC5 interface, or detects a beam failure or a failure in the execution of BFR on the PC5 interface, or a failure occurs in establishing a PC5 connection between the remote user device and the relay user device, or a failure occurs in synchronous reconfiguration of the PC5 interface of the remote user device, or a failure occurs in the configuration of the PC5 interface of the remote user device, it determines that a failure has occurred in the PC5 interface between the remote user device and the relay user device.

[0062] 10 is a schematic diagram of another example of a path failure scenario according to the first embodiment of the present invention, illustrating an indirect path failure scenario. As shown in FIG. 10, the indirect path failure may be a failure of the Uu interface between the relay user equipment and the network equipment.

[0063] For example, the remote user equipment may determine a failure of the Uu interface between the relay user equipment and the network equipment based on the RLF of the Uu interface of the relay user equipment sent from the relay user equipment, or a failure of the RRC connection of the relay user equipment, or a handover of the relay user equipment, or a notification of a failure of the BFR of the relay user equipment.

[0064] In some embodiments, notification of the RLF of the Uu interface of the relay user equipment, or of the failure of the RRC connection of the relay user equipment, or of the handover of the relay user equipment, or of the failure of the BFR of the relay user equipment may be sent via a PC5-RRC message, although the present invention is not limited thereto and the above information may be sent in other manners.

[0065] Although Figures 9 and 10 respectively show a failure of the PC5 interface and a failure of the Uu interface in the indirect path, the present invention is not limited to this, and the failure of the indirect path may also be a failure occurring in both the PC5 interface and the Uu interface.

[0066] In some embodiments, in the event of a failure of an indirect path, the remote user device may send failure information to the network device via an available direct path.

[0067] In some embodiments, in the event of an indirect path failure, the remote user equipment may trigger a relay reselection procedure without waiting for configuration information from the network device. During this procedure, the remote user equipment may remain in the RRC_Connected state. The present invention is not limited thereto, and in the event of an indirect path failure, the remote user equipment may perform a relay reselection procedure after receiving configuration information sent from the network device. Alternatively, if an indirect path failure occurs and a direct path is available, the remote user equipment may not trigger a relay reselection procedure. For example, if there is no available path between the remote user equipment and the network device, e.g., if both the direct path and the indirect path fail, the remote user equipment triggers a relay reselection procedure.

[0068] In some embodiments, the second path for transmitting the fault information is an available path, such as: the channel quality of the available path is higher than a first threshold; the channel quality of the available paths satisfies the cell selection and / or cell reselection criteria; the channel quality of the available paths satisfies the relay selection and / or relay reselection criteria; The available path is an indirect path, and no radio link failure, beam failure, or beam failure recovery failure of the PC5 interface is detected on the indirect path; the available path is an indirect path, and no notification of an RLF of the Uu interface of the relay user equipment, or of a failure of the RRC connection of the relay user equipment, or of a handover of the relay user equipment, or of a failure of the BFR of the relay user equipment, has been received on the indirect path, transmitted by the relay user equipment; The available path is an indirect path, and no failure occurs in the synchronous reconfiguration of the PC5 interface of the remote user device on the indirect path; The available path is an indirect path, and there is no failure in the configuration of the PC5 interface of the remote user device on the indirect path; The available route is an indirect route, and there is no failure in establishing a PC5 connection with the relay user device on the indirect route; The available route is a direct route, and no RLF, beam obstruction, or BFR obstruction of the Uu interface is detected on the direct route; The available path is a direct path, and no failure occurs in the synchronous reconfiguration of the Uu interface of the remote user device on the direct path; The available route is a direct route, and the direct route does not have a configuration failure of the Uu interface of the remote user device; or At least one of the following conditions is met: the available route is not deactivated or deconfigured.

[0069] In other words, an available route may satisfy any of the above conditions, or any combination of the above conditions.

[0070] For example, if the available route is a direct route, the available route is the channel quality of the available path is higher than a first threshold; the channel quality of the available paths satisfies the cell selection and / or cell reselection criteria; The available route is a direct route, and no RLF, beam obstruction, or BFR obstruction at the Uu interface is detected on the direct route; The available path is a direct path, and no failure occurs in the synchronous reconfiguration of the Uu interface of the remote user device on the direct path; The available route is a direct route, and the direct route does not have a configuration failure of the Uu interface of the remote user device; or At least one of the following conditions is met: the available route is not inactive or de-configured.

[0071] Also, for example, if the available route is an indirect route, the available route is the channel quality of the available path is higher than a first threshold; the channel quality of the available paths satisfies the relay selection and / or relay reselection criteria; The available path is an indirect path, and no RLF, beam obstruction, or BFR obstruction at the PC5 interface is detected on the indirect path; the available path is an indirect path, and no notification of RLF or RRC connection failure of the relay user equipment on the Uu interface of the relay user equipment, or notification of handover of the relay user equipment or BFR failure of the relay user equipment has been received on the indirect path; The available route is an indirect route, and there is no failure in establishing a PC5 connection with the relay user device on the indirect route; The available path is an indirect path, and no failure occurs in the synchronous reconfiguration of the PC5 interface of the remote user device on the indirect path; The available path is an indirect path, and there is no failure in the configuration of the PC5 interface of the remote user device on the indirect path; or At least one of the following conditions is met: the available route is not deactivated or deconfigured.

[0072] In some embodiments, the channel quality of the path may be a measurement result of the path by a remote user equipment, for example, including Uu Reference Signal Receiving Power (Uu RSRP), Sidelink Reference Signal Receiving Power (SL-RSRP), or Sidelink Discovery Reference Signal Receiving Power (SD-RSRP). The present invention is not limited thereto, and the measurement result may include other information, or the channel quality of the path may be a measurement result for a path transmitted by a relay user equipment.

[0073] In some embodiments, the first threshold may be predefined or configurable.

[0074] In some embodiments, the fault information sent by the remote user equipment to the network equipment may include at least one of fault indication information, fault type information, serving cell measurement results, other cell and / or frequency measurement results, connected relay user equipment measurement results, or other relay user equipment measurement results, i.e., the fault information may include any one of the above information or any combination of the above information.

[0075] For example, if the first path where the failure occurred is a direct path, the failure information may include at least one of failure indication information, failure type information, measurement results of the serving cell, measurement results of other cells and / or frequencies, etc.

[0076] For example, if the first path where the failure occurred is an indirect path, the failure information may include at least one of failure indication information, failure type information, measurement results of connected relay user equipment, or measurement results of other relay user equipment, etc.

[0077] In some embodiments, the failure indication information may be used to notify the network device of the specific nature of the path failure, so that the network device can take appropriate action according to the specific nature, such as, for example, sending corresponding information to the remote user equipment and / or the relay user equipment.

[0078] The fault indication information includes Uu RLF (radio link failure at UU interface), Uu BF (beam failure at Uu interface), Uu BFR failure (beam failure recovery failure at UU interface), PC5 RLF (radio link failure at PC5 interface), PC5 BF (beam failure at PC5 interface), PC5 BFR failure (beam failure recovery failure at PC5 interface), Relay UE Uu RLF (radio link failure at UU interface of relay user equipment), Relay UE HO (handover of relay user equipment), Relay UE RRC failure (radio resource control connection failure of relay user equipment), Relay UE BFR failure (beam failure recovery of relay user equipment), PC5 connection failure (failure to establish PC5 connection), Uu reconfiguration with sync failure (failure to synchronously reconfigure UU interface), Uu configuration failure (failure to configure UU interface), PC5 reconfiguration with sync failure (failure to synchronously reconfigure PC5 interface), and PC5 configuration The failure may include at least one of the following: a failure in the configuration of a PC5 interface.

[0079] In some embodiments, the failure type information may be used to inform the network device of the specific cause of the path failure.

[0080] The failure type information may include at least one of a T310 timeout, a random access problem, an RLC reaching a maximum number of transmissions or retransmissions, a Hybrid Automatic Repeat Request (HARQ) feedback Discontinuous Transmission (DTX) reaching a maximum number of times, an integrity failure, a Listen Before Talk (LBT) failure, a beam failure recovery failure, a T312 timeout, a backhaul link RLF, or a relay user equipment transmission failure type.

[0081] In some embodiments, the failure type transmitted by the relay user equipment may be transmitted via a PC5-RRC message, although the present invention is not limited thereto and the relay user equipment may transmit the failure type in other manners.

[0082] In some embodiments, if there is no available second path, for example if both the first and second paths fail, the remote user equipment may trigger an RRC connection re-establishment procedure.

[0083] 11 is a schematic diagram of another example of a path failure scenario according to the first embodiment of the present invention, illustrating a scenario in which failures occur in both the direct path and the indirect path. In this case, the remote user equipment triggers an RRC connection re-establishment procedure. In other words, if both the direct path and the indirect path between the remote user equipment and the network equipment fail, the remote user equipment may trigger an RRC connection re-establishment procedure.

[0084] In some embodiments, the direct path and the indirect path may employ split transmission and duplication transmission. When split transmission is employed, the direct path and the indirect path may transmit different data, e.g., different PDCP PDUs, thereby improving throughput. When duplication transmission is employed, the direct path and the indirect path may transmit the same data, e.g., the same PDCP PDU, thereby ensuring the reliability of data transmission by the remote user equipment.

[0085] In some embodiments, when multiple routes exist between a remote user device and a network device, the multiple routes may be configured as a primary route and a secondary route, for example, one route may be selected as a primary route and another route may be selected as a secondary route.

[0086] In some embodiments, the primary path may be a main path responsible for split transmission. For example, the primary path may be a path used by PDCP control PDU transmissions associated with one radio bearer when PDCP duplication is activated, or a path used for PDCP PDU transmissions when the amount of PDCP data and / or RLC data waiting for initial transmission is less than a threshold when PDCP duplication is deactivated. Here, the RLC entity corresponding to the primary path may be referred to as a primary RLC entity. The secondary path may be a path other than the primary path responsible for split transmission or repeated transmission. For example, when a remote user equipment uses two paths, the path other than the primary path is the secondary path.

[0087] In some embodiments, if a failure occurs on the first path and the first path is the primary path, the remote user equipment may trigger an RRC connection re-establishment procedure.

[0088] In some embodiments, if a failure occurs on a first path, the first path is a secondary path, a second path is available, and the second path is a primary path, failure information is sent to a network device via the second path.

[0089] Therefore, when a failure occurs on the secondary path and the primary path is available, the remote user equipment transmits failure information to the network device and does not trigger the RRC connection re-establishment procedure, whereas when a failure occurs on the primary path, the remote user equipment triggers the RRC connection re-establishment procedure, thereby reducing the service interruption time for the user equipment.

[0090] In some embodiments, the primary and / or secondary paths may be configured or predefined by the network device, although the invention is not limited in this respect and the primary and / or secondary paths may be selected by the remote user device.

[0091] In some embodiments, the primary path and the secondary path may be selected or configured according to various rules. For example, a direct path may be the primary path, and an indirect path may be the secondary path. For example, a path with good channel quality may be the primary path, and a path with poor channel quality may be the secondary path. Furthermore, a path including a primary RLC entity (or a primary RLC channel or a primary logical channel, etc.) may be the primary path, and / or a path including a secondary RLC entity (or a secondary RLC channel or a secondary logical channel, etc.) or a path not including a primary RLC entity (or a primary RLC channel or a primary logical channel, etc.) may be the secondary path. Here, the primary RLC entity (or a primary RLC channel or a primary logical channel, etc.) may be configured by a network device.

[0092] In some embodiments, the remote user equipment may transmit the failure information via an RRC message, but the present invention is not limited thereto and may transmit the failure information in other manners.

[0093] Although the above embodiments are merely illustrative of the present invention, the present invention is not limited thereto and may be appropriately modified based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be used in combination.

[0094] Although only steps related to the present invention have been described above, the present invention is not limited thereto. The fault information transmission method may include other steps, and for details of these steps, reference may be made to related art.

[0095] According to this embodiment, two or more paths (first path and second path) are configured or activated for a remote user device, and when a failure occurs on the first path, the remote user device sends failure information to the network device via the second path, thereby reducing the service interruption time of the user device, guaranteeing service delays, and improving user experience.

[0096] <Example 2> An embodiment of the present invention provides a fault information transmission device. The device may be, for example, a remote user device (e.g., the above-mentioned remote user device 401), or may be a component or element configured in the remote user device. Descriptions of the same content as in the first embodiment will be omitted.

[0097] 12 is a schematic diagram of an example of a fault information transmitting device according to Example 2 of the present invention. As shown in FIG. 12, a fault information transmitting device 1200 includes the following units.

[0098] When a failure occurs on the first route, the transmitting unit 1201 transmits failure information to the network device via the second route.

[0099] In some embodiments, a remote user device has at least two paths (a first path and a second path) configured or activated, the remote user device can communicate with a network device via at least one path, and if a first path of the at least two paths fails, the remote user device transmits failure information to the network device via an available second path of the at least two paths.

[0100] In some embodiments, the first path may be a direct path or an indirect path, and the second path may be a direct path or an indirect path. For example, the first path is a direct path and the second path is an indirect path. As another example, the first path is an indirect path and the second path is a direct path.

[0101] In some embodiments, a path failure may include: A Radio Link Failure (RLF) or Beam failure of the PC5 interface of the remote user equipment, or a failure to perform Beam failure recovery has been detected; a notification of a relay user equipment RLF on the Uu interface of the relay user equipment, or a failure of the relay user equipment Radio Resource Control (RRC) connection, or a handover of the relay user equipment, or a failure of the relay user equipment Beam failure recovery (BFR) has been received, the notification being sent by the relay user equipment; a failure to establish a PC5 connection with the relay user equipment; that a failure to perform RLF or beam failure or BFR on the Uu interface of the Remote User Equipment has been detected; A failure in the synchronous reconfiguration of the PC5 interface and / or Uu interface of the remote user equipment has occurred; or The method includes at least one of: a failure in the configuration of the PC5 interface and / or the Uu interface of the remote user device.

[0102] In some embodiments, notification of an RLF on the Uu interface of a relay user equipment, or a failure of an RRC connection of a relay user equipment, or a handover of a relay user equipment is sent via a PC5-RRC message.

[0103] In some embodiments, the failure of the indirect path may be: a radio link failure, or beam failure, or failure to perform beam failure recovery of the PC5 interface of the remote user device has been detected; a notification of an RLF on the Uu interface of the relay user equipment, or a failure of the RRC connection of the relay user equipment, or a handover of the relay user equipment, or a beam failure recovery failure of the relay user equipment, transmitted by the relay user equipment, has been received; that a failure has occurred in the synchronous reconfiguration of the Uu interface of the remote user equipment; A failure in the configuration of the Uu interface of the remote user device; or a failure to establish a PC5 connection with the relay user equipment occurs.

[0104] In some embodiments, the failure of the direct path is that a radio link failure or beam failure or failure to perform beam failure recovery of the Uu interface of the remote user equipment has been detected; A failure in the synchronous reconfiguration of the Uu interface of the remote user equipment has occurred, or The method includes at least one of: a failure in the configuration of the Uu interface of the remote user device.

[0105] In some embodiments, the second route is an available route, and the available route is: the channel quality of the available path is higher than a first threshold; the channel quality of the available paths satisfies the cell selection and / or cell reselection criteria; the channel quality of the available paths satisfies the relay selection and / or relay reselection criteria; The available path is an indirect path, and no RLF, beam obstruction, or BFR obstruction of the PC5 interface is detected on the indirect path; the available path is an indirect path, and no notification of an RLF on the Uu interface of the relay user equipment, or of a failure of the RRC connection of the relay user equipment, or of a handover of the relay user equipment, or of a failure of the BFR of the relay user equipment, has been received from the relay user equipment on the indirect path; The available path is an indirect path, and no failure occurs in the synchronous reconfiguration of the PC5 interface of the remote user device on the indirect path; The available path is an indirect path, and there is no failure in the configuration of the PC5 interface of the remote user device on the indirect path; The available route is an indirect route, and there is no failure in establishing a PC5 connection with the relay user device on the indirect route; The available route is a direct route, and no RLF, beam obstruction, or BFR obstruction of the Uu interface is detected on the direct route; The available path is a direct path, and no failure occurs in the synchronous reconfiguration of the Uu interface of the remote user device on the direct path; The available route is a direct route, and the direct route does not have a configuration failure of the Uu interface of the remote user device; or At least one of the following conditions is met: the available route is not deactivated or deconfigured.

[0106] In some embodiments, the channel quality of the path is a measurement of the path by a remote user equipment, the measurement being Uu RSRP, or SL-RSRP, or SD-RSRP.

[0107] In some embodiments, the first threshold is predefined or configurable.

[0108] In some embodiments, the failure information includes at least one of failure indication information, failure type information, measurement results of the serving cell, measurement results of other cells and / or frequencies, measurement results of connected relay user equipment, or measurement results of other relay user equipment.

[0109] In some embodiments, the failure indication information may be Uu RLF (radio link failure at Uu interface), Uu BF (beam failure at Uu interface), Uu BFR (beam failure recovery at Uu interface) failure, PC5 RLF (radio link failure at PC5 interface), PC5 BF (beam failure at PC5 interface), PC5 BFR (beam failure recovery at PC5 interface) failure, Relay UE Uu RLF (radio link failure at Uu interface of relay user equipment), Relay UE HO (handover of relay user equipment), Relay UE RRC failure (radio resource control connection failure of relay user equipment), Relay UE BFR failure (beam failure recovery failure of relay user equipment), PC5 connection failure (failure to establish PC5 connection), Uu reconfiguration with sync failure (failure to establish PC5 connection), Uu configuration failure (failure to configure Uu interface), PC5 reconfiguration with sync failure (failure to reconfigure synchronously at PC5 interface), or PC5 configuration failure (failure to configure PC5 interface).

[0110] In some embodiments, the failure type information includes at least one of a T310 timeout, a random access problem, a RLF reaching a maximum number of transmissions or retransmissions, a HARQ feedback DTX reaching a maximum number of times, a consistency failure, an LBT failure, a beam failure recovery failure, a T312 timeout, a backhaul link RLF, or a relay user equipment transmission failure type.

[0111] In some embodiments, the failure type information is communicated to the remote user equipment by a relay user equipment.

[0112] In some embodiments, the fault information transmitting device 1200 further includes the following units:

[0113] The processing unit 1202 triggers an RRC connection re-establishment procedure when a failure occurs on both the first path and the second path.

[0114] In some embodiments, the processing unit 1202 triggers an RRC connection re-establishment procedure when a failure occurs on the first path and the first path is a primary path.

[0115] In some embodiments, when a failure occurs in the first route, the first route is a secondary route, the second route is available, and the second route is a primary route, the transmitter 1201 transmits failure information to the network device via the second route.

[0116] In some embodiments, the primary and / or secondary paths are configured or predefined by the network devices.

[0117] In some embodiments, the failure information is transmitted via a Radio Resource Control (RRC) message.

[0118] The above-mentioned embodiments are merely illustrative of the embodiments of the present invention, but the present invention is not limited thereto and may be appropriately modified based on the above-mentioned embodiments. For example, the above-mentioned embodiments may be used alone or in combination with one or more of them.

[0119] Although the above describes only the components or modules related to the present invention, the present invention is not limited to these. The fault information transmission device 1200 may include other components or modules, and the specific contents of these components or modules may be found in related art.

[0120] 12 only exemplifies the connections or signal flows between the components or modules, but those skilled in the art may employ various related technologies such as bus connections. The various components or modules described above may be implemented by hardware devices such as a processor, memory, transmitter, and receiver, but the present invention is not limited to such implementations.

[0121] According to this embodiment, two or more paths (first path and second path) are configured or activated for a remote user device, and when a failure occurs on the first path, the remote user device sends failure information to the network device via the second path, thereby reducing the service interruption time of the user device, guaranteeing service delays, and improving user experience.

[0122] Example 3 The embodiment of the present invention provides a method for receiving fault information, which may be executed in a network device (for example, the above network device 403), and the description of the same content as in the first embodiment will be omitted.

[0123] 13 is a schematic diagram of an example of a method for receiving fault information according to Example 3 of the present invention. As shown in FIG. 13, the method includes the following steps:

[0124] Step 1301: When a failure occurs in a first path, receive failure information sent by a remote user device via a second path, where the remote user device has the first path and the second path configured or activated.

[0125] In some embodiments, the method further comprises the following steps:

[0126] Step 1302: Based on the failure information, send first configuration information for configuring a first route to a remote user device or a relay user device.

[0127] In some embodiments, the first configuration information may include, for example, information for triggering the remote user equipment to perform relay selection or relay reselection, or information for triggering the remote user equipment to perform an RRC reestablishment procedure, etc. For details of the first configuration information, please refer to the related art.

[0128] In some embodiments, the method further comprises the following steps:

[0129] Step 1303: Send second configuration information for configuring the primary path and / or the secondary path to the remote user device.

[0130] In some embodiments, the second configuration information may include, for example, a path identifier or index, an indication of a primary path and / or a secondary path, etc. For details of the second configuration information, reference may be made to the related art.

[0131] In some embodiments, the first path may be a direct path and the second path may be an indirect path, or the first path may be an indirect path and the second path may be a direct path.

[0132] In some embodiments, the failure information includes at least one of failure indication information, failure type information, measurement results of the serving cell, measurement results of other cells and / or frequencies, measurement results of connected relay user equipment, or measurement results of other relay user equipment.

[0133] In some embodiments, the failure indication information may be Uu RLF (radio link failure at Uu interface), Uu BF (beam failure at Uu interface), Uu BFR (beam failure recovery at Uu interface) failure, PC5 RLF (radio link failure at PC5 interface), PC5 BF (beam failure at PC5 interface), PC5 BFR (beam failure recovery at PC5 interface) failure, Relay UE Uu RLF (radio link failure at Uu interface of relay user equipment), Relay UE HO (handover of relay user equipment), Relay UE RRC failure (radio resource control connection failure of relay user equipment), Relay UE BFR failure (beam failure recovery failure of relay user equipment), PC5 connection failure (failure to establish PC5 connection), Uu reconfiguration with sync failure (failure to establish PC5 connection), Uu configuration failure (failure to configure Uu interface), PC5 reconfiguration with sync failure (failure to reconfigure synchronously at PC5 interface), or PC5 configuration failure (failure to configure PC5 interface).

[0134] In some embodiments, the failure type information includes at least one of a T310 timeout, a random access problem, a RLF reaching a maximum number of transmissions or retransmissions, a HARQ feedback DTX reaching a maximum number of times, a consistency failure, an LBT failure, a beam failure recovery failure, a T312 timeout, a backhaul link RLF, or a relay user equipment transmission failure type.

[0135] In some embodiments, the failure information is received via a Radio Resource Control (RRC) message.

[0136] Although the above embodiments are merely illustrative of the present invention, the present invention is not limited thereto and may be appropriately modified based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be used in combination.

[0137] Although only steps related to the present invention have been described above, the present invention is not limited thereto. The fault information transmission method may include other steps, and for details of these steps, reference may be made to related art.

[0138] According to this embodiment, two or more paths (first path and second path) are configured or activated for a remote user device, and when a failure occurs on the first path, the remote user device sends failure information to the network device via the second path, thereby reducing the service interruption time of the user device, guaranteeing service delays, and improving user experience.

[0139] Example 4 An embodiment of the present invention provides a fault information receiving device. The device may be, for example, a network device (e.g., the above-mentioned network device 403), or may be a constituent element or component configured in the network device. Descriptions of the same content as in the second embodiment will be omitted.

[0140] 14 is a schematic diagram of an example of a fault information receiving device according to Example 4 of the present invention. As shown in FIG. 14, a fault information receiving device 1400 includes the following units.

[0141] When a failure occurs in the first path, the receiver 1401 receives failure information transmitted by a remote user device via the second path, the remote user device having the first path and the second path configured or activated.

[0142] In some embodiments, the fault information receiving device 1400 further includes the following units:

[0143] The transmitter 1402 transmits first configuration information for configuring a first route to a remote user equipment or a relay user equipment based on the failure information.

[0144] In some embodiments, the transmitter 1402 transmits second configuration information for configuring the primary path and / or the secondary path to the remote user device.

[0145] In some embodiments, the first path is a direct path and the second path is an indirect path, or the first path is an indirect path and the second path is a direct path.

[0146] In some embodiments, the failure information includes at least one of failure indication information, failure type information, measurement results of the serving cell, measurement results of other cells and / or frequencies, measurement results of connected relay user equipment, or measurement results of other relay user equipment.

[0147] In some embodiments, the failure indication information may be Uu RLF (radio link failure at Uu interface), Uu BF (beam failure at Uu interface), Uu BFR (beam failure recovery at Uu interface) failure, PC5 RLF (radio link failure at PC5 interface), PC5 BF (beam failure at PC5 interface), PC5 BFR (beam failure recovery at PC5 interface) failure, Relay UE Uu RLF (radio link failure at Uu interface of relay user equipment), Relay UE HO (handover of relay user equipment), Relay UE RRC failure (radio resource control connection failure of relay user equipment), Relay UE BFR failure (beam failure recovery failure of relay user equipment), PC5 connection failure (failure to establish PC5 connection), Uu reconfiguration with sync failure (failure to establish PC5 connection), Uu configuration failure (failure to configure Uu interface), PC5 reconfiguration with sync failure (failure to reconfigure synchronously at PC5 interface), or PC5 configuration failure (failure to configure PC5 interface).

[0148] In some embodiments, the failure type information includes at least one of a T310 timeout, a random access problem, a RLF reaching a maximum number of transmissions or retransmissions, a HARQ feedback DTX reaching a maximum number of times, a consistency failure, an LBT failure, a beam failure recovery failure, a T312 timeout, a backhaul link RLF, or a relay user equipment transmission failure type.

[0149] In some embodiments, the failure information is received via an RRC message.

[0150] The above-mentioned embodiments are merely illustrative of the embodiments of the present invention, but the present invention is not limited thereto and may be appropriately modified based on the above-mentioned embodiments. For example, the above-mentioned embodiments may be used alone or in combination with one or more of them.

[0151] Although the above describes only the components or modules related to the present invention, the present invention is not limited to these. The fault information receiving device 1400 may include other components or modules, and the specific contents of these components or modules may be found in related art.

[0152] 14 only exemplifies the connections or signal flows between the components or modules, but those skilled in the art may employ various related technologies such as bus connections. The various components or modules described above may be implemented by hardware devices such as a processor, memory, transmitter, and receiver, but the present invention is not limited to such implementations.

[0153] According to this embodiment, two or more paths (first path and second path) are configured or activated for a remote user device, and when a failure occurs on the first path, the remote user device sends failure information to the network device via the second path, thereby reducing the service interruption time of the user device, guaranteeing service delays, and improving user experience.

[0154] <Example 5> An embodiment of the present invention provides a communication system, and reference may be made to Fig. 4, and the same content as in the first to fourth embodiments will not be described.

[0155] In some embodiments, the communication system 400 may include at least a remote user device 401 and / or a network device 403 and / or a relay user device 402 .

[0156] In this embodiment of the present invention, the remote user device 401 is configured to execute the fault information transmission method described in the first embodiment, the contents of which are incorporated herein by reference and the description thereof is omitted.

[0157] In this embodiment of the present invention, the network device 403 is configured to execute the method for receiving fault information described in the third embodiment, the contents of which are incorporated herein by reference and the description thereof is omitted.

[0158] An embodiment of the present invention provides a terminal device.

[0159] 15 is a schematic diagram of a terminal device according to a fifth embodiment of the present invention. The terminal device may be a remote user device. As shown in FIG. 15, the terminal device 1500 may include a processor 1510 and a memory 1520. The memory 1520 stores data and programs and is connected to the processor 1510. Note that this diagram is merely exemplary, and other types of structures may be used to supplement or replace the structure to realize communication functions or other functions.

[0160] For example, the processor 1510 may be configured to execute a program to realize the fault information transmission method described in Example 1. For example, the processor 1510 may be configured to transmit fault information to a network device via a second path when a fault occurs on a first path.

[0161] As shown in Fig. 15, the terminal device 1500 may further include a communication module 1530, an input unit 1540, a display 1550, and a power supply 1560. Here, the functions of the above components are similar to those of the prior art, and therefore description thereof will be omitted here. Note that the terminal device 1500 does not need to include all of the units shown in Fig. 15, and the above components are not essential. Furthermore, the terminal device 1500 may further include units not shown in Fig. 15, and prior art may be referenced.

[0162] An embodiment of the present invention further provides a network device, which may be a base station, but the present invention is not limited thereto and may be other networks.

[0163] Fig. 16 is a schematic diagram of a network device according to an embodiment of the present invention. As shown in Fig. 16, the network device 1600 may include a processor 1610 (e.g., a central processing unit (CPU)) and a memory 1620, which is connected to the processor 1610. The memory 1620 stores data and programs. The memory 1620 also stores a program 1630 for information processing, and executes the program 1630 under the control of the processor 1610.

[0164] For example, the processor 1610 may be configured to execute a program to implement the method for receiving fault information described in Example 3. For example, the processor 1610 may be configured to receive fault information sent by a remote user device via a second path when a fault occurs in the first path, where the remote user device has the first path and the second path configured or activated.

[0165] As shown in Fig. 16, the network device 1600 may further include a transceiver 1640 and an antenna 1650. The functions of the above components are similar to those of the prior art, and their description will be omitted here. Note that the network device 1600 does not need to include all the units shown in Fig. 16. Furthermore, the network device 1600 may further include units not shown in Fig. 16, and prior art may be referred to.

[0166] According to this embodiment, two or more paths (first path and second path) are configured or activated for a remote user device, and when a failure occurs on the first path, the remote user device sends failure information to the network device via the second path, thereby reducing the service interruption time of the user device, guaranteeing service delays, and improving user experience.

[0167] In an embodiment of the present invention, there is further provided a computer-readable program that, when executed on a remote user device, causes a computer to execute the fault information transmission method described in the above embodiment 1 on the remote user device.

[0168] An embodiment of the present invention further provides a storage medium having a computer-readable program stored therein, the program, when executed, causing a computer to execute the fault information transmission method described in the above embodiment 1 in a remote user device.

[0169] In an embodiment of the present invention, there is further provided a computer-readable program that, when executed in a network device, causes a computer to execute the fault information receiving method described in the above-mentioned embodiment 3 in the network device.

[0170] An embodiment of the present invention further provides a storage medium having a computer-readable program stored therein, the program, when executed, causing a computer to execute the method for receiving fault information described in the above-mentioned embodiment 3 in a network device.

[0171] The above-described apparatus and methods of the present invention may be realized by hardware or a combination of hardware and software. The present invention relates to a computer-readable program that, when executed by a logic unit, causes the logic unit to implement the above-described apparatus or components, or to implement the above-described various methods or steps. The logic unit may be, for example, a field programmable logic unit, a microprocessor, or a processor used in a computer. The present invention also relates to a storage medium for storing the above-described program, for example, a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0172] Each processing method in each device described with reference to the embodiments of the present invention may be implemented by hardware, a software module executed by a processor, or a combination of both. For example, one or more of the functional block diagrams shown in the drawings, or one or more combinations of the functional block diagrams, may correspond to each software module in a computer program flow or each hardware module. These software modules may correspond to each step shown in the drawings. These hardware modules may be implemented by implementing these software modules in hardware, for example, using a field programmable gate array (FPGA).

[0173] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, mobile hard disk, CD-ROM, or any other form of storage medium known to those skilled in the art. The storage medium may be connected to the processor so that the processor reads information from or writes information to the storage medium, or the storage medium may be a component of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal or in a memory card inserted into the mobile terminal. For example, if a device (e.g., a mobile terminal) uses a relatively large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0174] One or more functional blocks and / or one or more combinations of functional blocks in the functional block diagrams set forth in the figures may be implemented with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any suitable combination thereof to perform the functions described herein. One or more functional blocks and / or one or more combinations of functional blocks in the functional block diagrams set forth in the figures may be implemented with, for example, a combination of computing devices, such as a combination of a DSP and a microprocessor, a combination of multiple microprocessors, one or more microprocessors in combination with a DSP communication, or any other configuration.

[0175] Although the present invention has been described above with reference to specific embodiments, the above description is merely illustrative and does not limit the scope of protection of the present invention. Various modifications and changes may be made to the present invention without departing from the spirit and principles of the present invention, and these modifications and changes are also within the scope of the present invention.

[0176] Furthermore, the following supplementary notes are disclosed regarding the embodiments including the above examples. (Appendix 1) A device for transmitting fault information of a remote user device, wherein the remote user device has a first path and a second path configured or activated; a transmitter that transmits failure information to a network device via the second path when a failure occurs on the first path. (Appendix 2) The route obstruction is A radio link failure (RLF) or beam failure or failure to perform beam failure recovery of the PC5 interface of the remote user device is detected; a notification of a relay user equipment RLF on the Uu interface of the relay user equipment, or a failure of the relay user equipment Radio Resource Control (RRC) connection, or a handover of the relay user equipment, or a failure of the relay user equipment Beam failure recovery (BFR) has been received, the notification being sent by the relay user equipment; a failure to establish a PC5 connection with the relay user equipment; a failure of RLF, beam failure, or BFR implementation of the Uu interface of the remote user equipment has been detected; a failure in the synchronous reconfiguration of the PC5 interface and / or Uu interface of the remote user device; or 2. The apparatus of claim 1, wherein the remote user device is configured to receive a signal from a PC5 interface and / or a Uu interface. (Appendix 3) 3. The apparatus of claim 2, wherein notification of an RLF of the Uu interface of the relay user equipment, or a failure of the RRC connection of the relay user equipment, or a handover of the relay user equipment is sent via a PC5-RRC message. (Appendix 4) the first path is a direct path and the second path is an indirect path; or 2. The apparatus of claim 1, wherein the first path is an indirect path and the second path is a direct path. (Appendix 5) Indirect pathway failures include: a radio link failure, or beam failure, or failure to perform beam failure recovery of the PC5 interface of the remote user device is detected; a notification of an RLF on the Uu interface of the relay user equipment, or a failure of the RRC connection of the relay user equipment, or a handover of the relay user equipment, or a beam failure recovery failure of the relay user equipment, transmitted by the relay user equipment, has been received; a failure in synchronous reconfiguration of the Uu interface of the remote user device; a failure in the configuration of the Uu interface of the remote user device; or 5. The apparatus of claim 4, wherein the failure includes at least one of: a failure to establish a PC5 connection with the relay user equipment. (Appendix 6) The direct path failure is a radio link failure, or beam failure, or failure to perform beam failure recovery of the Uu interface of the remote user equipment is detected; a failure in the synchronous reconfiguration of the Uu interface of the remote user equipment; or The apparatus of claim 4, further comprising at least one of: a failure in the configuration of the Uu interface of the remote user device. (Appendix 7) The second route is an available route, and the available route is the channel quality of the available path is higher than a first threshold; the channel quality of the available paths satisfies cell selection and / or cell reselection criteria; the channel quality of the available paths satisfies a relay selection and / or relay reselection criterion; The available path is an indirect path, and no RLF, beam obstruction, or BFR obstruction of the PC5 interface is detected on the indirect path; the available path is an indirect path, and no notification of an RLF of the Uu interface of the relay user equipment, or of a failure of the RRC connection of the relay user equipment, or of a handover of the relay user equipment, or of a failure of the BFR of the relay user equipment, has been received on the indirect path, transmitted by the relay user equipment; The available path is an indirect path, and no failure occurs in synchronous reconfiguration of the PC5 interface of the remote user device on the indirect path; The available path is an indirect path, and no failure occurs in the configuration of the PC5 interface of the remote user device on the indirect path; The available path is an indirect path, and there is no failure in establishing a PC5 connection with a relay user device on the indirect path; The available path is a direct path, and no RLF, beam obstruction, or BFR obstruction of the Uu interface is detected on the direct path; the available path is a direct path, and no failure occurs in synchronous reconfiguration of the Uu interface of the remote user device on the direct path; The available path is a direct path, and no failure occurs in the configuration of the Uu interface of the remote user device on the direct path; or 7. The apparatus of claim 1, wherein the available path satisfies at least one of the following conditions: the path is not deactivated or deconfigured. (Appendix 8) the channel quality of the path is a measurement of the path by the remote user equipment; 8. The apparatus of claim 7, wherein the measurement result is Uu RSRP, or SL-RSRP, or SD-RSRP. (Appendix 9) 9. The apparatus of claim 7 or 8, wherein the first threshold is predefined or configurable. (Appendix 10) 10. The apparatus of claim 1, wherein the fault information includes at least one of fault indication information, fault type information, measurement results of a serving cell, measurement results of other cells and / or frequencies, measurement results of connected relay user equipment, or measurement results of other relay user equipment. (Appendix 11) The fault indication information includes Uu RLF (radio link failure of Uu interface), Uu BF (beam failure of Uu interface), Uu BFR (beam failure recovery of Uu interface) failure, PC5 RLF (radio link failure of PC5 interface), PC5 BF (beam failure of PC5 interface), PC5 BFR (beam failure recovery of PC5 interface) failure, Relay UE Uu RLF (radio link failure of Uu interface of relay user equipment), Relay UE HO (handover of relay user equipment), Relay UE RRC failure (radio resource control connection failure of relay user equipment), Relay UE BFR failure (beam failure recovery failure of relay user equipment), PC5 connection failure (failure to establish PC5 connection), Uu reconfiguration with sync failure (failure to synchronize reconfiguration of Uu interface), Uu configuration failure (failure to configure Uu interface), PC5 reconfiguration with sync failure (failure to synchronize reconfiguration of PC5 interface), and PC5 configuration 11. The apparatus of claim 10, further comprising at least one of: a failure in configuring a PC5 interface; (Appendix 12) 11. The apparatus of claim 10, wherein the failure type information includes at least one of a T310 timeout, a random access problem, a RLF reaching a maximum number of transmissions or retransmissions, a HARQ feedback DTX reaching a maximum number of times, a consistency failure, an LBT failure, a beam failure recovery failure, a T312 timeout, a backhaul link RLF, or a relay user equipment transmission failure type. (Appendix 13) 13. The apparatus of claim 12, wherein the failure type information is notified to the remote user equipment by the relay user equipment. (Appendix 14) 14. The apparatus of any one of Supplementary Notes 1 to 13, further comprising: a processing unit that triggers an RRC connection re-establishment procedure when failures occur on both the first path and the second path. (Appendix 15) 15. The apparatus of any one of Supplementary Notes 1 to 14, further comprising: a processing unit that triggers an RRC connection re-establishment procedure when a failure occurs in the first path and the first path is a primary path. (Appendix 16) 16. The device described in any of Supplementary Notes 1 to 15, wherein when a failure occurs in the first route, the first route is a secondary route, the second route is available, and the second route is a primary route, the transmitter transmits failure information to a network device via the second route. (Appendix 17) 17. The apparatus of claim 15 or 16, wherein the primary path and / or the secondary path are configured or predefined by a network device. (Appendix 18) 2. The apparatus of claim 1, wherein the failure information is transmitted via a Radio Resource Control (RRC) message. (Appendix 19) 1. A method for transmitting fault information of a remote user device, the remote user device having a first path and a second path configured or activated; If a failure occurs on the first route, transmitting failure information to a network device via the second route. (Appendix 20) The route obstruction is A radio link failure (RLF) or beam failure or failure to perform beam failure recovery of the PC5 interface of the remote user device is detected; a notification of a relay user equipment RLF on the Uu interface of the relay user equipment, or a failure of the relay user equipment Radio Resource Control (RRC) connection, or a handover of the relay user equipment, or a failure of the relay user equipment Beam failure recovery (BFR) has been received, the notification being sent by the relay user equipment; a failure to establish a PC5 connection with the relay user equipment; a failure of RLF, beam failure, or BFR implementation of the Uu interface of the remote user equipment has been detected; a failure in the synchronous reconfiguration of the PC5 interface and / or Uu interface of the remote user device; or 20. The method of claim 19, including at least one of: a failure in the configuration of the PC5 interface and / or Uu interface of the remote user device. (Appendix 21) 21. The method of claim 20, wherein notification of an RLF of the Uu interface of the relay user equipment, or a failure of the RRC connection of the relay user equipment, or a handover of the relay user equipment is sent via a PC5-RRC message. (Appendix 22) the first path is a direct path and the second path is an indirect path; or 20. The method of claim 19, wherein the first path is an indirect path and the second path is a direct path. (Appendix 23) Indirect pathway failures include: a radio link failure, or beam failure, or failure to perform beam failure recovery of the PC5 interface of the remote user device is detected; a notification of an RLF on the Uu interface of the relay user equipment, or a failure of the RRC connection of the relay user equipment, or a handover of the relay user equipment, or a beam failure recovery failure of the relay user equipment, transmitted by the relay user equipment, has been received; a failure in synchronous reconfiguration of the Uu interface of the remote user device; a failure in the configuration of the Uu interface of the remote user device; or 23. The method of claim 22, comprising at least one of: a failure to establish a PC5 connection with the relay user equipment. (Appendix 24) The direct path failure is a radio link failure, or beam failure, or failure to perform beam failure recovery of the Uu interface of the remote user equipment is detected; a failure in the synchronous reconfiguration of the Uu interface of the remote user equipment; or 23. The method of claim 22, including at least one of: a failure in the configuration of the Uu interface of the remote user device. (Appendix 25) The second route is an available route, and the available route is the channel quality of the available path is higher than a first threshold; the channel quality of the available paths satisfies cell selection and / or cell reselection criteria; the channel quality of the available paths satisfies a relay selection and / or relay reselection criterion; The available path is an indirect path, and no RLF, beam obstruction, or BFR obstruction of the PC5 interface is detected on the indirect path; the available path is an indirect path, and no notification of an RLF of the Uu interface of the relay user equipment, or of a failure of the RRC connection of the relay user equipment, or of a handover of the relay user equipment, or of a failure of the BFR of the relay user equipment, has been received on the indirect path, transmitted by the relay user equipment; The available path is an indirect path, and no failure occurs in synchronous reconfiguration of the PC5 interface of the remote user device on the indirect path; The available path is an indirect path, and no failure occurs in the configuration of the PC5 interface of the remote user device on the indirect path; The available path is an indirect path, and there is no failure in establishing a PC5 connection with a relay user device on the indirect path; The available path is a direct path, and no RLF, beam obstruction, or BFR obstruction of the Uu interface is detected on the direct path; the available path is a direct path, and no failure occurs in synchronous reconfiguration of the Uu interface of the remote user device on the direct path; The available path is a direct path, and no failure occurs in the configuration of the Uu interface of the remote user device on the direct path; or 25. The method of any of claims 19 to 24, wherein the available path satisfies at least one of the following conditions: the path is not deactivated or deconfigured. (Appendix 26) the channel quality of the path is a measurement of the path by the remote user equipment; 26. The method of claim 25, wherein the measurement result is Uu RSRP, or SL-RSRP, or SD-RSRP. (Appendix 27) 27. The method of claim 25 or 26, wherein the first threshold is predefined or configurable. (Appendix 28) 28. The method of any of Supplementary Notes 19 to 27, wherein the failure information includes at least one of failure indication information, failure type information, measurement results of a serving cell, measurement results of other cells and / or frequencies, measurement results of connected relay user equipments, or measurement results of other relay user equipments. (Appendix 29) The fault indication information includes Uu RLF (radio link failure of Uu interface), Uu BF (beam failure of Uu interface), Uu BFR (beam failure recovery of Uu interface) failure, PC5 RLF (radio link failure of PC5 interface), PC5 BF (beam failure of PC5 interface), PC5 BFR (beam failure recovery of PC5 interface) failure, Relay UE Uu RLF (radio link failure of Uu interface of relay user equipment), Relay UE HO (handover of relay user equipment), Relay UE RRC failure (radio resource control connection failure of relay user equipment), Relay UE BFR failure (beam failure recovery failure of relay user equipment), PC5 connection failure (failure to establish PC5 connection), Uu reconfiguration with sync failure (failure to synchronize reconfiguration of Uu interface), Uu configuration failure (failure to configure Uu interface), PC5 reconfiguration with sync failure (failure to synchronize reconfiguration of PC5 interface), and PC5 configuration 29. The method of claim 28, including at least one of: a failure of configuration of a PC5 interface. (Appendix 30) 29. The method of claim 28, wherein the failure type information comprises at least one of a T310 timeout, a random access problem, a RLF reaching a maximum number of transmissions or retransmissions, a HARQ feedback DTX reaching a maximum number of times, a consistency failure, an LBT failure, a beam failure recovery failure, a T312 timeout, a backhaul link RLF, or a relay user equipment transmission failure type. (Appendix 31) 31. The method of claim 30, wherein the failure type information is notified to the remote user equipment by the relay user equipment. (Appendix 32) 32. The method of any of Supplementary Notes 19 to 31, further comprising the step of triggering an RRC connection re-establishment procedure if failures occur on both the first path and the second path. (Appendix 33) 33. The method of any of Supplementary Notes 19 to 32, further comprising: triggering an RRC connection re-establishment procedure when a failure occurs on the first path and the first path is a primary path. (Appendix 34) 34. The method of any one of appendixes 19 to 33, further comprising the step of: if a failure occurs in the first route, the first route is a secondary route, the second route is available, and the second route is a primary route, transmitting failure information to a network device via the second route. (Appendix 35) 35. The method of claim 33 or 34, wherein the primary route and / or the secondary route are configured or predefined by a network device. (Appendix 36) 20. The method of claim 19, wherein the failure information is transmitted via an RRC message. (Appendix 37) A remote user device comprising: a memory having a computer program stored therein; and a processor, the processor configured to execute the computer program to realize a method for transmitting fault information according to any one of appendices 19 to 36. (Appendix 38) A fault information receiving device, An apparatus including: a receiver that receives failure information transmitted by a remote user device via a second path when a failure occurs in a first path, the remote user device having the first path and the second path configured or activated. (Appendix 39) 39. The apparatus of claim 38, further comprising: a transmitter that transmits, based on failure information, first configuration information for configuring the first route to the remote user device or relay user device. (Appendix 40) 39. The apparatus of claim 38, further comprising: a transmitter that transmits second configuration information for configuring a primary path and / or a secondary path to the remote user device. (Appendix 41) the first path is a direct path and the second path is an indirect path; or 39. The apparatus of claim 38, wherein the first path is an indirect path and the second path is a direct path. (Appendix 42) 42. The apparatus of any of Supplementary Notes 38 to 41, wherein the failure information includes at least one of failure indication information, failure type information, measurement results of a serving cell, measurement results of other cells and / or frequencies, measurement results of connected relay user equipments, or measurement results of other relay user equipments. (Appendix 43) The fault indication information includes Uu RLF (radio link failure of Uu interface), Uu BF (beam failure of Uu interface), Uu BFR (beam failure recovery of Uu interface) failure, PC5 RLF (radio link failure of PC5 interface), PC5 BF (beam failure of PC5 interface), PC5 BFR (beam failure recovery of PC5 interface) failure, Relay UE Uu RLF (radio link failure of Uu interface of relay user equipment), Relay UE HO (handover of relay user equipment), Relay UE RRC failure (radio resource control connection failure of relay user equipment), Relay UE BFR failure (beam failure recovery failure of relay user equipment), PC5 connection failure (failure to establish PC5 connection), Uu reconfiguration with sync failure (failure to synchronize reconfiguration of Uu interface), Uu configuration failure (failure to configure Uu interface), PC5 reconfiguration with sync failure (failure to synchronize reconfiguration of PC5 interface), and PC5 configuration 43. The apparatus of claim 42, further comprising at least one of: a failure in configuring a PC5 interface; (Appendix 44) 43. The apparatus of claim 42, wherein the failure type information comprises at least one of a T310 timeout, a random access problem, a RLF reaching a maximum number of transmissions or retransmissions, a HARQ feedback DTX reaching a maximum number of times, a consistency failure, an LBT failure, a beam failure recovery failure, a T312 timeout, a backhaul link RLF, or a relay user equipment transmission failure type. (Appendix 45) 39. The apparatus of claim 38, wherein the failure information is received via an RRC message. (Appendix 46) A method for receiving fault information, comprising: A method comprising: if a failure occurs in a first path, receiving failure information transmitted by a remote user device via a second path, the remote user device having the first path and the second path configured or activated. (Appendix 47) 47. The method of claim 46, further comprising the step of sending first configuration information to the remote user device or relay user device for configuring the first route based on failure information. (Appendix 48) 47. The method of claim 46, further comprising sending second configuration information to the remote user device for configuring a primary path and / or a secondary path. (Appendix 49) the first path is a direct path and the second path is an indirect path; or 47. The method of claim 46, wherein the first path is an indirect path and the second path is a direct path. (Appendix 50) 50. The method of any of claims 46 to 49, wherein the failure information includes at least one of failure indication information, failure type information, measurement results of a serving cell, measurement results of other cells and / or frequencies, measurement results of connected relay user equipments, or measurement results of other relay user equipments. (Appendix 51) The fault indication information includes Uu RLF (radio link failure of Uu interface), Uu BF (beam failure of Uu interface), Uu BFR (beam failure recovery of Uu interface) failure, PC5 RLF (radio link failure of PC5 interface), PC5 BF (beam failure of PC5 interface), PC5 BFR (beam failure recovery of PC5 interface) failure, Relay UE Uu RLF (radio link failure of Uu interface of relay user equipment), Relay UE HO (handover of relay user equipment), Relay UE RRC failure (radio resource control connection failure of relay user equipment), Relay UE BFR failure (beam failure recovery failure of relay user equipment), PC5 connection failure (failure to establish PC5 connection), Uu reconfiguration with sync failure (failure to synchronize reconfiguration of Uu interface), Uu configuration failure (failure to configure Uu interface), PC5 reconfiguration with sync failure (failure to synchronize reconfiguration of PC5 interface), and PC5 configuration 51. The method of claim 50, including at least one of: a failure of configuration of a PC5 interface. (Appendix 52) 51. The method of claim 50, wherein the failure type information includes at least one of a T310 timeout, a random access problem, a RLF reaching a maximum number of transmissions or retransmissions, a HARQ feedback DTX reaching a maximum number of times, a consistency failure, an LBT failure, a beam failure recovery failure, a T312 timeout, a backhaul link RLF, or a relay user equipment transmission failure type. (Appendix 53) 47. The method of claim 46, wherein the failure information is received via a Radio Resource Control (RRC) message. (Appendix 54) A network device comprising: a memory having a computer program stored therein; and a processor, wherein the processor is configured to execute the computer program to realize a method for receiving fault information according to any one of appendices 46 to 53. (Appendix 55) 54. A communications system comprising a network device according to claim 54 and / or a remote user device according to claim 37.

Claims

1. A device for transmitting fault information of a remote user device, wherein the remote user device has a first path and a second path configured or activated; a transmitter that transmits failure information to a network device via the second path when a failure occurs on the first path; The device, wherein the fault information includes at least one of measurement results of the connected relay user equipment or measurement results of other relay user equipment.

2. The failure of the first path is a radio link failure, or beam failure, or failure to perform beam failure recovery of the PC5 interface of the remote user device is detected; a notification of a radio link failure of the Uu interface of the relay user equipment, or a radio resource control connection failure of the relay user equipment, or a handover of the relay user equipment, or a beam failure recovery failure of the relay user equipment, transmitted by the relay user equipment, is received; a failure to establish a PC5 connection with the relay user equipment; a radio link failure, or beam failure, or failure to perform beam failure recovery of the Uu interface of the remote user equipment is detected; a failure in the synchronous reconfiguration of the PC5 interface and / or Uu interface of the remote user device; or The device of claim 1 , including at least one of: a failure in the configuration of a PC5 interface and / or a Uu interface of the remote user device.

3. The apparatus according to claim 2, wherein notification of a radio link failure of the Uu interface of the relay user equipment, or a radio resource control connection failure of the relay user equipment, or a handover of the relay user equipment is sent via a PC5-RRC message.

4. the first path is a direct path and the second path is an indirect path; or The apparatus of claim 1 , wherein the first path is an indirect path and the second path is a direct path.

5. The second route is an available route, and the available route is the channel quality of the available path is higher than a first threshold; the channel quality of the available paths satisfies a cell selection and / or cell reselection criterion; the channel quality of the available paths satisfies a relay selection and / or relay reselection criterion; The available path is an indirect path, and no radio link failure, beam failure, or beam failure recovery failure of the PC5 interface has been detected on the indirect path; the available path is an indirect path, and no notification of a radio link failure of a Uu interface of a relay user equipment, or a radio resource control connection failure of a relay user equipment, or a handover of a relay user equipment, or a beam failure recovery failure of a relay user equipment, transmitted by a relay user equipment on the indirect path, has been received; The available path is an indirect path, and no failure occurs in synchronous reconfiguration of the PC5 interface of the remote user device on the indirect path; The available path is an indirect path, and no failure occurs in the configuration of the PC5 interface of the remote user device on the indirect path; The available path is an indirect path, and no failure occurs in establishing a PC5 connection with a relay user device on the indirect path; The available path is a direct path, and no radio link failure, beam failure, or beam failure recovery failure of the Uu interface has been detected on the direct path; the available path is a direct path, and no failure occurs in synchronous reconfiguration of the Uu interface of the remote user equipment on the direct path; The available path is a direct path, and no failure occurs in the configuration of the Uu interface of the remote user equipment on the direct path; or The apparatus of claim 1 , wherein the available paths satisfy at least one of the following conditions: not being deactivated or not being deconfigured.

6. The apparatus of claim 1 , wherein the failure information further comprises at least one of failure indication information, failure type information, serving cell measurement results, or other cell and / or frequency measurement results.

7. 7. The device of claim 6, wherein the fault indication information includes at least one of a radio link failure of a Uu interface, a beam failure of a Uu interface, a beam failure recovery failure of a Uu interface, a radio link failure of a PC5 interface, a beam failure of a PC5 interface, a beam failure recovery failure of a PC5 interface, a radio link failure of a Uu interface of a relay user equipment, a handover of a relay user equipment, a radio resource control connection failure of a relay user equipment, a beam failure recovery failure of a relay user equipment, a failure to establish a PC5 connection, a synchronous reconfiguration failure of a Uu interface, a configuration failure of a Uu interface, a synchronous reconfiguration failure of a PC5 interface, and a configuration failure of a PC5 interface.

8. 2. The apparatus of claim 1, further comprising: a processing unit that triggers a radio resource control connection re-establishment procedure when failures occur on both the first path and the second path; and / or triggers a radio resource control connection re-establishment procedure when a failure occurs on the first path and the first path is a primary path.

9. 2. The device according to claim 1, wherein when a failure occurs in the first route, the first route is a secondary route, the second route is available, and the second route is a primary route, the transmitter transmits failure information to a network device via the second route.

10. The device of claim 9 , wherein the primary path and / or the secondary path are configured or predefined by a network device.

11. The apparatus of claim 1 , wherein the failure information is transmitted via a radio resource control message.

12. A fault information receiving device, a receiver configured to receive failure information transmitted by a remote user device via a second path when a failure occurs in a first path, the remote user device having the first path and the second path configured or activated; The device, wherein the fault information includes at least one of measurement results of the connected relay user equipment or measurement results of other relay user equipment.

13. The device described in Claim 12, further comprising a transmitting unit that transmits first configuration information for configuring the first route to the remote user device or relay user device based on the failure information.

14. The device of claim 12 , further comprising: a transmitter configured to transmit second configuration information for configuring a primary path and / or a secondary path to the remote user device.

15. the first path is a direct path and the second path is an indirect path; or The apparatus of claim 12 , wherein the first path is an indirect path and the second path is a direct path.

16. The apparatus of claim 12 , wherein the failure information further comprises at least one of failure indication information, failure type information, serving cell measurements, or other cell and / or frequency measurements.

17. 17. The device of claim 16, wherein the failure indication information includes at least one of a radio link failure of a Uu interface, a beam failure of a Uu interface, a beam failure recovery failure of a Uu interface, a radio link failure of a PC5 interface, a beam failure of a PC5 interface, a beam failure recovery failure of a PC5 interface, a radio link failure of a Uu interface of a relay user equipment, a handover of a relay user equipment, a radio resource control connection failure of a relay user equipment, a beam failure recovery failure of a relay user equipment, a failure to establish a PC5 connection, a synchronous reconfiguration failure of a Uu interface, a configuration failure of a Uu interface, a synchronous reconfiguration failure of a PC5 interface, and a configuration failure of a PC5 interface.

18. The apparatus of claim 12 , wherein the failure information is received via a radio resource control message.

19. 1. A communication system including: a remote user device; and a network device, wherein the remote user device has a first path and a second path configured or activated; When a failure occurs on the first path, the remote user device transmits failure information to the network device via the second path; the fault information includes at least one of a measurement result of the connected relay user equipment or a measurement result of another relay user equipment; The network device receives the failure information transmitted by the remote user device via the second path.

Citation Information

Patent Citations

  • Terminal and communication nodes

    WO2021009883A1

  • Methods, infrastructure equipment and wireless communications networks

    WO2021197807A1

  • Methods and apparatus for link management and recovery for sidelink relays

    WO2022032034A1