Communication method and device, and computer storage medium

Abstract

The embodiment of the invention relates to a communication method, equipment and a computer readable medium. In one aspect, a first terminal device receives, from a network device, a configuration for a direct path between the first terminal device and the network device and an indirect path between the first terminal device and the network device via a second terminal device. If the RLF is detected for one of the direct path and the indirect path, and the other of the direct path and the indirect path is available, the first terminal device transmits a first RRC message for RLF recovery to the network device via the other of the direct path and the indirect path. In this way, the network may appropriately process the RLF based on the indication of RLF recovery.

Description

Technical Field

[0001] Embodiments of the present disclosure relate generally to the field of telecommunications, and in particular to methods, devices, and computer storage media for communication with multiple paths having relays. Background Art

[0002] It has been proposed to support multi-path (MP) with relays, where a remote user equipment (UE) is connected to the network via a direct path and an indirect path. A direct path means that the remote UE is directly connected to the network. An indirect path means that the remote UE is connected to the network via a relay UE using a PC5 interface or a non-standardized UE-UE interconnect. Support of MP with relays has the potential to improve reliability or robustness as well as throughput. However, the scheme of MP with relays in the control plane is still imperfect and needs further development. Summary of the invention

[0003] Generally speaking, embodiments of the present disclosure provide communication methods, devices, and computer storage media for MPs with relays.

[0004] In a first aspect, a method of communication is provided. The method includes: receiving, at a first terminal device, configurations for a direct path between the first terminal device and the network device and an indirect path between the first terminal device and the network device via a second terminal device from a network device; and sending, based on determining that a radio link failure is detected for one of the direct path and the indirect path and that the other of the direct path and the indirect path is available, a first radio resource control message for recovery of the radio link failure to the network device via the other of the direct path and the indirect path, the first radio resource control message indicating at least one of the following: a type of the radio link failure; a measurement result associated with the first terminal device; or one of the direct path and the indirect path that has failed.

[0005] In a second aspect, a communication method is provided. The method includes: receiving, at a terminal device, an instruction for activating or deactivating at least one of a direct path between a first terminal device and a network device or an indirect path between the first terminal device and the network device via a second terminal device; performing an activation operation based on determining that the instruction is to activate one of the direct path and the indirect path; and performing a deactivation operation based on determining that the instruction is to deactivate one of the direct path and the indirect path.

[0006] In a third aspect, a communication method is provided. The method comprises: receiving, at a first terminal device, from a network device a configuration for a direct path between the first terminal device and the network device and an indirect path between the first terminal device and the network device via a second terminal device; and sending a request to the network device for releasing or deactivating the direct path or the indirect path.

[0007] In a fourth aspect, a communication device is provided, wherein the device includes a processor, and the processor is configured to enable the device to execute the method according to any one of the first to third aspects of the present disclosure.

[0008] In a fifth aspect, a computer readable medium having instructions stored thereon is provided. When the instructions are executed on at least one processor, the at least one processor executes the method according to any one of the first to third aspects of the present disclosure.

[0009] Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The above and other objects, features and advantageous effects of the present disclosure will become more apparent through a more detailed description of some embodiments of the present disclosure in the accompanying drawings, in which:

[0011] Figure 1 shows an example communication network in which some embodiments of the present disclosure may be implemented;

[0012] Figure 2 A diagram illustrating example bearer types for which some embodiments of the present disclosure may be implemented is shown;

[0013] Figure 3A shows an example protocol stack for an MP split data radio bearer (DRB) in which some embodiments of the present disclosure may be implemented;

[0014] Figure 3B shows an example protocol stack for an MP Split Signaling Radio Bearer (SRB) in which some embodiments of the present disclosure may be implemented;

[0015] Figure 3C Another example protocol stack for MP split DRBs is shown in which some embodiments of the present disclosure may be implemented;

[0016] Figure 3D Another example protocol stack for MP split SRB is shown in which some embodiments of the present disclosure may be implemented;

[0017] Figure 4A A schematic diagram illustrating a communication process according to an embodiment of the present disclosure is shown;

[0018] Figure 4B A schematic diagram illustrating another communication process according to an embodiment of the present disclosure is shown;

[0019] Figure 4C A schematic diagram illustrating yet another communication process according to an embodiment of the present disclosure is shown;

[0020] Figure 5 An example communication method implemented at a first terminal device according to some embodiments of the present disclosure is shown;

[0021] Figure 6 An example communication method implemented at a first terminal device or a second terminal device according to some embodiments of the present disclosure is shown;

[0022] Figure 7 An example communication method implemented at a first terminal device according to some embodiments of the present disclosure is shown; and

[0023] Figure 8 is a simplified block diagram of a device suitable for implementing embodiments of the present disclosure.

[0024] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0025] The principle of the present disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described only for illustrative purposes, and to help those skilled in the art understand and implement the present disclosure, without implying any limitation to the scope of the disclosure. The disclosure described herein can be implemented in various ways different from the modes described below.

[0026] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0027] As used herein, the term "terminal device" refers to any device with wireless or wired communication capabilities. Examples of terminal devices include, but are not limited to, user equipment (UE), personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs), portable computers, tablets, wearable devices, Internet of Things (IoT) devices, ultra-reliable and low latency communications (URLLC) devices, Internet of Everything (IoE) devices, machine type communications (MTC) devices, vehicle-mounted devices for V2X communications (where X represents pedestrians, vehicles, or infrastructure / network), devices for integrated access and backhaul (IAB), air transport vehicles or air vehicles in non-terrestrial networks (NTNs) including satellites and high altitude platforms (HAPs) including unmanned aircraft systems (UAS), extended reality (XR) devices including different types of reality such as augmented reality (AR), mixed reality (MR), and virtual reality (VR), unmanned aerial vehicles (UAVs) (commonly referred to as drones, which are aircraft without any human pilots), devices on high-speed trains (HSTs), or image capture devices such as digital cameras, sensors, gaming devices, music storage and playback devices, or Internet facilities enabling wireless or wired Internet access and browsing, etc. The "terminal device" may further have "multicast / broadcast" features to support public safety and mission-critical, V2X applications, transparent IPv4 / IPv6 multicast delivery, IPTV, Smart TV, radio services, software delivery over wireless, group communications, and IoT applications. It may also incorporate one or more subscriber identity modules (SIMs), as known as multi-SIM. The term "terminal device" may be used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal, or wireless device.

[0028] The term "network equipment" refers to equipment that is capable of providing or hosting a cell or coverage with which a terminal device can communicate. Examples of network equipment include, but are not limited to, a Node B (Node B or NB), an evolved Node B (eNodeB or eNB), a next generation Node B (gNB), a transmission reception point (TRP), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), an IAB node, a low power node such as a femto node, a pico node, a reconfigurable smart surface (RIS), etc.

[0029] Terminal devices or network devices can have artificial intelligence (AI) or machine learning capabilities. It usually includes models trained based on a large amount of data collected for specific functions and can be used to predict some information.

[0030] The terminal or network device can operate on several frequency ranges, such as FR1 (410MHz to 7125MHz), FR2 (24.25GHz to 71GHz), frequency bands greater than 100GHz, and terahertz (THz). It can also operate on licensed / unlicensed / shared spectrum. In the multi-radio dual connection (MR-DC) application scenario, the terminal device can have more than one connection with the network device. The terminal device or network device can operate in full-duplex, flexible duplex, and cross-division duplex modes.

[0031] The embodiments of the present disclosure may be executed in a test device, such as a signal generator, a signal analyzer, a spectrum analyzer, a network analyzer, a test terminal device, a test network device, and a channel emulator.

[0032] In some embodiments, the terminal device may be connected to a first network device and a second network device. One of the first network device and the second network device may be a primary node, and the other may be a secondary node. The first network device and the second network device may use different radio access technologies (RATs). In some embodiments, the first network device may be a first RAT device, and the second network device may be a second RAT device. In some embodiments, the first RAT device is an eNB and the second RAT device is a gNB. Information related to different RATs may be sent to the terminal device from at least one of the first network device or the second network device. In some embodiments, the first information may be sent from the first network device to the terminal device, and the second information may be sent directly or via the first network device from the second network device to the terminal device. In some embodiments, information related to the configuration of the terminal device configured by the second network device may be sent from the second network device via the first network device. Information related to the reconfiguration of the terminal device configured by the second network device may be sent directly or via the first network device from the second network device to the terminal device.

[0033] As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term "including" and its variations are to be interpreted as open-ended terms, which mean "including but not limited to". The term "based on" is to be interpreted as "based at least in part on". The terms "one embodiment" and "embodiment" are to be interpreted as "at least one embodiment". The term "another embodiment" is to be interpreted as "at least one other embodiment". The terms "first", "second", etc. may refer to different or identical objects. Other explicit and implicit definitions may be included below.

[0034] In some examples, values, processes, or devices are referred to as "best," "lowest," "highest," "minimum," "maximum," etc. It should be understood that such descriptions are intended to indicate that a selection may be made among a number of functional alternatives used, and that such a selection is not necessarily better, lesser, higher, or more preferred than other selections.

[0035] In the context of the present disclosure, the term "direct path" may be used interchangeably with "Master Cell Group (MCG)" or "direct transmission" or "direct path transmission", "MCG transmission" or "Uu path". The term "indirect path" may be used interchangeably with "indirect transmission", "indirect path transmission", "PC5 path", "sidelink path" or "relay path". The term "packet replication" may be used interchangeably with "Packet Data Convergence Protocol (PDCP) replication".

[0036] In the context of the present disclosure, the term “first terminal device” may refer to a terminal device serving as a remote UE, and the term “second terminal device” may refer to a terminal device serving as a relay UE.

[0037] Supporting multipath with relays, where remote UEs are connected to the network via both direct and indirect paths, has the potential to improve reliability / robustness as well as throughput, and therefore needs to be considered as an enhancement area. The MP relay scheme can also be used for UE aggregation, where a UE is connected to the network via a direct path and via another UE using a non-standardized UE-UE interconnect. UE aggregation is intended to provide applications that require high uplink (UL) bit rates on 5G terminals, for situations where normal UEs are too limited by UL UE transmission power to achieve the required bit rate, especially at the cell edge. In addition, UE aggregation can improve reliability and stability, and also reduce latency of services. That is, if the channel conditions of a terminal are deteriorating, another terminal can be used to compensate for the instability in service performance caused by changes in channel conditions.

[0038] However, the solution of MP with relay in the control plane is still imperfect. For example, when a radio link failure (RLF) occurs at one of the direct path and the indirect path, if the other of the direct path and the indirect path is still available, it is unclear how to recover the RLF via the other path. In addition, it is unclear how to enable activation or deactivation of the direct or indirect path. In addition, when a terminal device is configured with an MP with relay, the terminal device may be low on power or may not have much data to send. Maintaining the MP costs the terminal device additional power.

[0039] In view of this, an embodiment of the present disclosure provides a solution for an MP with relay to solve the above or other potential problems. In one aspect, a first terminal device (e.g., a remote UE) receives a configuration for a direct path between the first terminal device and the network device and an indirect path between the first terminal device and the network device via a second terminal device (e.g., a relay UE) from a network device. If an RLF is detected for one of the direct path and the indirect path and the other of the direct path and the indirect path is available, the first terminal device sends a radio resource control (RRC) message for RLF recovery to the network device via the other of the direct path and the indirect path. The RRC message indicates at least one of the following: the type of RLF; a measurement result associated with the first terminal device; or one of the direct path and the indirect path that has failed. In this way, the network can appropriately handle the RLF based on the indication of RLF recovery.

[0040] On the other hand, a terminal device (e.g., a remote UE or a relay UE) receives an instruction for activating or deactivating at least one of a direct path between a first terminal device (e.g., a remote UE) and a network device or an indirect path between the first terminal device and the network device via a second terminal device (e.g., a relay UE). If the instruction is to activate one of the direct path and the indirect path, the first terminal device performs an activation operation. If the instruction is to deactivate one of the direct path and the indirect path, the first terminal device performs a deactivation operation. In this way, activation or deactivation of the direct path or the indirect path can be enabled.

[0041] In another aspect, the first terminal device (e.g., a remote UE) receives configurations for a direct path between the first terminal device and the network device and an indirect path between the first terminal device and the network device via a second terminal device from a network device, and sends a request to the network device for releasing or deactivating the direct path or the indirect path. In this way, when the terminal device does not need the MP due to lack of power or data, the terminal device can request the network to release or deactivate the MP.

[0042] The principles and implementations of the present disclosure will be described in detail below with reference to the accompanying drawings.

[0043] Example of a communication network

[0044] Figure 1 1 shows a schematic diagram of an example communication network 100 in which some embodiments of the present disclosure may be implemented. Figure 1As shown, the communication network 100 may include a terminal device 110, a terminal device 120 and a network device 130. The network device 130 may provide one or more cells (not shown) to serve one or more terminal devices. In this example, the terminal devices 110 and 120 are served by the network device 130.

[0045] In some embodiments, terminal device 110 and terminal device 120 may be served by the same cell of network device 130. In some embodiments, terminal device 110 and terminal device 120 may be served by different intra-frequency cells of network device 130. In some embodiments, terminal device 110 and terminal device 120 may be served by different inter-frequency cells of network device 130.

[0046] In some embodiments, terminal device 110 may communicate directly with network device 130 (i.e., via a direct path). Terminal device 110 may also communicate with network device 130 via terminal device 120 (i.e., via an indirect path). In this case, terminal device 110 acts as a remote UE, while terminal device 120 acts as a relay UE.

[0047] In some embodiments, terminal device 120 may communicate directly with network device 130 (i.e., via a direct path). Terminal device 120 may also communicate with network device 130 via terminal device 110 (i.e., via an indirect path). In this case, terminal device 120 acts as a remote UE, while terminal device 110 acts as a relay UE.

[0048] For convenience, the following description is given by taking the terminal device 110 as an example of a remote UE and the terminal device 120 as an example of a relay UE.

[0049] In some embodiments, the network device 130 and any one of the terminal devices 110 and 120 can communicate with each other via an air interface (e.g., a Uu interface), for example, via a wireless communication channel. The wireless communication channel may include a physical uplink control channel (PUCCH), a physical uplink shared channel (PUSCH), a physical random access channel (PRACH), a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), and a physical broadcast channel (PBCH). Of course, any other suitable channel is also feasible.

[0050] In some embodiments, the terminal device 110 may be connected to the terminal device 120 via a sidelink (SL) interface (e.g., a PC5 interface, etc.). In this case, the terminal device 120 acts as a Layer 2 (L2) UE-to-Network (U2N) relay. In some embodiments, the terminal device 110 and the terminal device 120 may communicate with each other via SL channels such as a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), a physical sidelink feedback channel (PSFCH), a physical sidelink broadcast channel (PSBCH), etc. For example, a PC5 connection may be established between the terminal device 110 and the second device 120.

[0051] In some embodiments, the terminal device 110 may be connected to the terminal device 120 via an ideal UE-UE interconnection or a backhaul connection.

[0052] It should be understood that Figure 1 The number of devices in FIG. 1 is given for illustrative purposes and does not imply any limitation to the present disclosure. The communication network 100 may include any suitable number of network devices and / or terminal devices suitable for implementing the embodiments of the present disclosure.

[0053] The communications in the communication network 100 may conform to any suitable standard, including but not limited to Global System for Mobile Communications (GSM), Long Term Evolution (LTE), LTE Evolution, Advanced LTE (LTE-A), New Radio (NR), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), GSM EDGE Radio Access Network (GERAN), Machine Type Communications (MTC), etc. The embodiments of the present disclosure may be performed according to any generation of communication protocols currently known or developed in the future. Examples of communication protocols include but are not limited to first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) communication protocols, 5.5G, 5G advanced networks, or sixth generation (6G) networks.

[0054] In some embodiments, direct bearers, indirect bearers, and MP split bearers may be supported. A direct bearer may refer to a radio bearer mapped to a direct path on an air interface (e.g., a Uu interface). An indirect bearer may refer to a radio bearer mapped to an indirect path via a relay UE. An MP split bearer may refer to a radio bearer mapped to a direct path and an indirect path based on a split bearer framework. This will be described below in conjunction with Figure 2 Describe in detail.

[0055] Figure 2 A diagram 200 is shown illustrating example bearer types for which some embodiments of the present disclosure may be implemented. Figure 2As shown in 210 in FIG. 1 , the Uu PDCP entity may communicate with the Uu radio link control (RLC) entity via a direct bearer, and thus a direct bearer may be formed. Figure 2 As shown in 220 in FIG. 1 , the Uu PDCP entity may communicate with the Sidelink Relay Adaptation Protocol (SRAP) entity and the SL RLC entity, and thus may form an indirect bearer. Figure 2 As shown in 230, the Uu PDCP entity can communicate with the Uu RLC entity via the MP split bearer, and also communicate with the SRAP entity and the SL RLC entity, thereby forming an MP split bearer.

[0056] Figure 3A An example protocol stack 300A for MP-split DRBs in which some embodiments of the present disclosure may be implemented is shown. In this example, a remote UE and a relay UE communicate with each other via an SL interface. For MP-split DRBs, a PDCP entity where the remote UE is located is configured with a direct Uu RLC channel and an indirect PC5 RLC channel. For uplink, the PDCP entity at the remote UE side delivers to the Uu RLC entity and the PC5 RLC entity using the SRAP entity. For downlink, the PDCP entity at the remote UE side receives from the Uu RLC entity and the PC5 RLC entity using the SRAP entity.

[0057] Figure 3B An example protocol stack 300B for MP-split SRB in which some embodiments of the present disclosure may be implemented is shown. In this example, the remote UE and the relay UE communicate with each other via the SL interface. For MP-split SRB, a PDCP entity at the remote UE is configured with a direct Uu RLC channel and an indirect PC5 RLC channel. For uplink, the SRAP entity utilized by the PDCP entity at the remote UE side delivers to the Uu RLC entity and the PC5 RLC entity. For downlink, the PDCP entity at the remote UE side receives from the Uu RLC entity and the PC5 RLC entity using the SRAP entity.

[0058] Figure 3CAnother example protocol stack 300C for MP-split DRBs is shown in which some embodiments of the present disclosure may be implemented. In this example, the remote UE and the relay UE communicate with each other via an ideal UE-UE interconnect. For MP-split DRBs, a PDCP entity at the remote UE is configured with a direct Uu RLC channel and an indirect non-standard connection associated with the relay UE. For uplink, the PDCP entity at the remote UE side delivers to the Uu RLC entity and the non-standard connection with the relay UE using the SRAP entity. For downlink, the PDCP entity at the remote UE side receives from the Uu RLC entity and the non-standard connection associated with the relay UE using the SRAP entity.

[0059] Figure 3D Another example protocol stack 300D for MP-split SRB is shown in which some embodiments of the present disclosure may be implemented. In this example, the remote UE and the relay UE communicate with each other via an ideal UE-UE interconnect. For MP-split SRB, a PDCP entity at the remote UE is configured with a direct Uu RLC channel and an indirect non-standard connection associated with the relay UE. For the uplink, the PDCP entity at the remote UE side delivers to the Uu RLC entity and the non-standard connection associated with the relay UE using the SRAP entity. For the downlink, the PDCP entity at the remote UE side receives from the Uu RLC entity and the non-standard connection associated with the relay UE using the SRAP entity.

[0060] Embodiments of the present disclosure provide a communication scheme for an MP with a relay. Figures 4A to 4C Describe the details of the program.

[0061] Example implementation of RLF processing

[0062] Figure 4A A schematic diagram illustrating a communication process 400A according to an embodiment of the present disclosure is shown. For the purpose of discussion, reference will be made to Figure 1 Process 400A is described. Process 400A may include the following: Figure 1 The terminal device 110, the terminal device 120 and the network device 130 are shown. It is assumed that the terminal device 110 is used as a remote UE and the terminal device 120 is used as a relay UE.

[0063] like Figure 4A As shown, the network device 130 may send 410 to the terminal device 110 the configuration of the direct path between the terminal device 110 and the network device 130 and the indirect path between the terminal device 110 and the network device 130 via the terminal device 120. That is, the terminal device 110 is configured with the MP.

[0064] Based on the configuration, the terminal device 110 may perform 411 radio link monitoring at both the air interface (e.g., Uu interface) and the sidelink interface (e.g., PC5 interface). If RLF is detected for one of the direct path and the indirect path, and the other of the direct path and the indirect path is available, the terminal device 110 may send 412 an RRC message for RLF recovery (also referred to herein as a first RRC message for convenience) to the network device 130 via the other of the direct path and the indirect path. In some embodiments, the RRC message may be a UE Assistance Information message or any other suitable message.

[0065] Based on the indication of RLF recovery, the network can correctly handle the RLF. Some exemplary embodiments will be described below in conjunction with Embodiments 1 and 2.

[0066] Example 1

[0067] In this embodiment, the one of the direct path and the indirect path where the failure occurs is the direct path.

[0068] In some embodiments, if RLF is detected for the direct path and the indirect path is available (i.e., the indirect transmission is not suspended or deactivated), the terminal device 110 may suspend the direct path. For example, the terminal device 110 may suspend direct transmission for all SRBs and DRBs. In some embodiments, the terminal device 110 may reset the media access control (MAC) entity (i.e., Uu MAC) for the direct path.

[0069] In some embodiments, the terminal device 110 may send a first RRC message for direct path failure recovery or report the RLF of the direct path to the network device 130 by using an indirect path / branch of an indirect SRB or an MP split SRB (eg, MP split SRB1).

[0070] In some embodiments, the first RRC message may indicate the type of RLF / failure. In some embodiments, the type of RLF / failure may include at least one of: T310 expiration, random access problem, RLC maximum number of retransmissions reached, T312 expiration, listen before talk (LBT) failure, or beam failure recovery failure. It should be understood that any other suitable type of RLF is also feasible.

[0071] In some embodiments, the first RRC message may indicate measurement results associated with the terminal device 110. In some embodiments, these measurement results may include at least one of the following: a measurement result of a serving cell, a measurement result of a neighboring cell, and a measurement result of a candidate L2 U2N relay UE. It should be understood that any other suitable measurement results are also feasible.

[0072] In some embodiments, the first RRC message may indicate that one of the direct path and the indirect path has failed. In this embodiment, the first RRC message may indicate the direct path.

[0073] It should be noted that the first RRC message may indicate any combination of the above information and any other suitable information.

[0074] In some embodiments, if packet replication is not configured for an MP split SRB (eg, MP split SRB1) for direct and indirect paths, and the primary path of the MP split SRB is the direct path, the terminal device 110 may set the primary path to the indirect path.

[0075] In some embodiments, if the timer (for convenience, also referred to herein as the first timer) is not running, the first RRC message may be sent. In some embodiments, when sending the first RRC message, the terminal device 110 may start or restart the first timer.

[0076] In some embodiments, another RRC message (also referred to herein as a second RRC message for convenience) may be received. In some embodiments, the second RRC message may be used to release the direct path. For example, the second RRC message may be an RRC reconfiguration (RRCReconfiguration) message that releases the direct path. In some embodiments, the second RRC message may be used to reconfigure the direct path. For example, the second RRC message may be an RRC reconfiguration message with synchronous reconfiguration (reconfigurationWithSync). In some embodiments, the second RRC message may be used to release the connection between the terminal device 110 and the network device 130. For example, the second RRC message may be an RRC release (RRCRelease) message. Of course, any other suitable message is also feasible. In these embodiments where the second RRC message is received, the terminal device 110 may stop the first timer.

[0077] In some embodiments, if the first timer expires, the terminal device 110 may initiate an RRC reestablishment process. In some embodiments, if the first timer expires, the terminal device 110 may release the direct path. It should be understood that the terminal device 110 may perform any combination of the above operations and any other suitable operations when the first timer expires.

[0078] In some embodiments, if RLF is detected for the direct path, and the indirect path is not available, for example if the indirect path is suspended or deactivated, the terminal device 110 may initiate an RRC re-establishment procedure.

[0079] In this way, the RLF in the direct path can be recovered via the indirect path.

[0080] Example 2

[0081] In this embodiment, the one of the direct path and the indirect path where the failure occurs is the indirect path.

[0082] In some embodiments, if RLF is detected for the indirect path and the direct path is available (i.e., direct transmission is not suspended or deactivated), the terminal device 110 may suspend the indirect path. For example, the terminal device 110 may suspend indirect transmission for all SRBs and DRBs. In some embodiments, the terminal device 110 may reset the media access control (MAC) entity (i.e., PC5 MAC) for the indirect path.

[0083] In some embodiments, the terminal device 110 may send a first RRC message for indirect path failure recovery or report the RLF of the indirect path to the network device 130 by using a direct path / branch of a direct SRB or an MP split SRB (eg, MP split SRB1).

[0084] In some embodiments, the first RRC message may indicate the type of RLF / failure. In some embodiments, the type of RLF / failure may include at least one of the following: T310 expiration, random access problem, RLC maximum retransmission number reached, T312 expiration, listen before talk (LBT) failure, beam failure recovery failure, or information about a failure in the link between the network device 130 and the terminal device 120. It should be understood that any other suitable type of RLF is also feasible.

[0085] In some embodiments, the first RRC message may indicate measurement results associated with the terminal device 110. In some embodiments, these measurement results may include at least one of the following: a measurement result of a serving cell, a measurement result of a neighboring cell, and a measurement result of a candidate L2 U2N relay UE. It should be understood that any other suitable measurement results are also feasible.

[0086] In some embodiments, the first RRC message may indicate that one of the direct path and the indirect path has failed. In this embodiment, the first RRC message may indicate the indirect path.

[0087] It should be noted that the first RRC message may indicate any combination of the above information and any other suitable information.

[0088] In some embodiments, if packet replication is not configured for an MP split SRB (eg, MP split SRB1) for direct and indirect paths, and the primary path of the MP split SRB is an indirect path, the terminal device 110 may set the primary path to the direct path.

[0089] In some embodiments, if the timer (also referred to herein as the second timer for convenience) is not running, the first RRC message may be sent. In some embodiments, when sending the RRC message, the terminal device 110 may start or restart the second timer. In some embodiments, the second timer may be the same timer as the first timer.

[0090] In some embodiments, another RRC message (also referred to herein as a second RRC message for convenience) may be received. In some embodiments, the second RRC message may be used to release the indirect path. For example, the second RRC message may be an RRC reconfiguration message that releases the indirect path. In some embodiments, the second RRC message may be used to reconfigure the indirect path. In some embodiments, the second RRC message may be used to release the connection between the terminal device 110 and the network device 130. For example, the second RRC message may be an RRC release message. Of course, any other suitable message is also feasible. In these embodiments where the second RRC message is received, the terminal device 110 may stop the second timer.

[0091] In some embodiments, if the second timer expires, the terminal device 110 may initiate an RRC reestablishment process. In some embodiments, if the second timer expires, the terminal device 110 may release the indirect path. It should be understood that the terminal device 110 may perform any combination of the above operations and any other suitable operations when the second timer expires.

[0092] In some embodiments, if RLF is detected for the indirect path, and the direct path is not available, for example if the direct path is suspended or deactivated, the terminal device 110 may initiate an RRC re-establishment procedure.

[0093] In this way, the RLF in the indirect path can be recovered via the direct path.

[0094] Example implementation of indirect or direct path activation or deactivation

[0095] Figure 4B A schematic diagram illustrating another communication process 400B according to an embodiment of the present disclosure is shown. For the purpose of discussion, reference will be made to Figure 1 Process 400B is described. Process 400B may include the following: Figure 1The terminal device 110, the terminal device 120 and the network device 130 are shown. It is assumed that the terminal device 110 is used as a remote UE and the terminal device 120 is used as a relay UE.

[0096] like Figure 4B As shown, the network device 130 may send 420 to the terminal device 110 an instruction for activating or deactivating at least one of a direct path between the terminal device 110 and the network device 130 or an indirect path between the terminal device 110 and the network device 130 via the terminal device 120. If the instruction is to activate one of the direct path and the indirect path, the terminal device 110 may perform 430 an activation operation. If the instruction is to deactivate one of the direct path and the indirect path, the terminal device 110 may perform 440 a deactivation operation. Some exemplary embodiments will be described below in conjunction with Embodiments 3 and 4.

[0097] Example 3

[0098] Continue to refer Figure 4B In this embodiment, the network device 130 may directly send 421 the indication to the terminal device 110 .

[0099] In some embodiments, the indication may be sent in an RRC message via SRB1. In some embodiments, the indication may be sent in a MAC control element (CE). In some embodiments, the indication may indicate that one of the direct path and the indirect path is activated, while the other of the direct path and the indirect path is deactivated. In some embodiments, the indication may indicate that both the direct path and the indirect path are activated.

[0100] In some embodiments, if the indication is to activate one of the direct path and the indirect path, the terminal device 110 may resume the corresponding path for the set of radio bearers configured for the terminal device 110. For example, the terminal device 110 may resume transmission of the corresponding path for all SRBs and DRBs.

[0101] In some embodiments where the indication is to activate the direct path, if the time alignment timer is not running or the count value for the beam failure indication is equal to or higher than a threshold, the terminal device 110 may initiate a random access procedure to a specific cell (SPCell) or a primary cell (PCell) of the network device 130. In some embodiments where the indication is to activate the direct path, the terminal device 110 may resume RLF monitoring for the direct path. In some embodiments where the indication is to activate the direct path, the terminal device 110 may activate the SPCell and the secondary cell set (SCell) for the direct path. It should be understood that when the indication is to activate the direct path, the above operations may be performed individually or in any suitable combination.

[0102] In some embodiments where the indication is activation of an indirect path, the terminal device 110 may consider the service cell associated with the terminal device 120 to be activated. In other words, the terminal device 110 may consider the service cell for the indirect path to be activated. In some embodiments where the indication is activation of an indirect path, the terminal device 110 may resume RLF monitoring for the indirect path. In some embodiments where the indication is activation of an indirect path, the terminal device 110 may perform transmissions on the indirect path for the terminal device 110. For example, the terminal device 110 may perform transmissions on a PC5 connection or an ideal connection, for example, performing transmissions of a sidelink shared channel (SL-SCH) or a PSCCH or a PSSCH. It should be understood that when the indication is activation of an indirect path, the above operations may be performed individually or in any suitable combination.

[0103] In some embodiments, if the indication is to deactivate one of the direct path and the indirect path, the terminal device 110 may suspend the corresponding path for the set of radio bearers configured for the terminal device 110. For example, the terminal device 110 may suspend transmission of the corresponding path for all SRBs and DRBs.

[0104] In some embodiments, if the indication is to deactivate one of the direct path and the indirect path, the terminal device 110 may reset the MAC entity corresponding to the deactivated one of the direct path and the indirect path.

[0105] In some embodiments, if the indication is to deactivate one of the direct path and the indirect path, the terminal device 110 may reestablish the RLC entity of the radio bearer. In some embodiments, the radio bearer may include at least an SRB. In some embodiments where the path to be deactivated is an indirect path, the terminal device 110 may reestablish the RLC entity of the indirect bearer. In some embodiments where the path to be deactivated is a direct path, the terminal device 110 may reestablish the RLC entity of the direct bearer.

[0106] In some embodiments, if the indication is to deactivate one of a direct path and an indirect path, the terminal device 110 may trigger the discarding of a PDCP service data unit (SDU) for the radio bearer. In some embodiments, the radio bearer may include at least an SRB. In some embodiments where the path to be deactivated is an indirect path, the terminal device 110 may trigger the PDCP entity of the indirect bearer to perform PDCP SDU discarding. In some embodiments where the path to be deactivated is a direct path, the terminal device 110 may trigger the PDCP entity of the direct bearer to perform PDCP SDU discarding. In the context of the present disclosure, PDCP SDU discarding refers to the PDCP entity of the terminal device 110 discarding all stored PDCP SDUs and PDCP protocol data units (PDUs).

[0107] In some embodiments where the indication is to deactivate the direct path, the terminal device 110 may start a time alignment timer (TAT). In some embodiments where the indication is to deactivate the direct path, the terminal device 110 may stop RLF monitoring for the direct path. In some embodiments where the indication is to deactivate the direct path, the terminal device 110 may continue beam failure monitoring for the direct path. In some embodiments where the indication is to deactivate the direct path, the terminal device 110 may consider the SPCell and SCell sets for the direct path to be deactivated. It should be understood that when the indication is to deactivate the direct path, the above operations may be performed individually or in any suitable combination.

[0108] In some embodiments where the indication is to deactivate an indirect path, the terminal device 110 may de-enable the indirect path. That is, there is no transmission on the indirect path, for example, no transmission of SL-SCH or PSCCH or PSSCH. In some embodiments where the indication is to deactivate an indirect path, the terminal device 110 may consider that the serving cell for the indirect path is deactivated. In some embodiments where the indication is to deactivate an indirect path, the terminal device 110 may suspend RLF monitoring for the indirect path. It should be understood that when the indication is to deactivate an indirect path, the above operations may be performed individually or in any suitable combination.

[0109] In this way, the network can send indications to the remote UE to control the activation or deactivation status of the direct or indirect path.

[0110] Example 4

[0111] Still reference Figure 4B In this embodiment, the network device 130 may send 422 an indication for activating or deactivating at least one of the direct path or the indirect path to the terminal device 120. In some embodiments, the indication may include an identification of the terminal device 110.

[0112] In some embodiments, the indication may be sent in an RRC message via SRB1. In some embodiments, the indication may be sent in a MAC CE. In some embodiments, the indication may indicate that one of the direct path and the indirect path is activated, while the other of the direct path and the indirect path is deactivated. In some embodiments, the indication may indicate that both the direct path and the indirect path are activated.

[0113] In some embodiments, if the indication is to activate an indirect path, the terminal device 120 may consider the serving cell associated with the terminal device 110 to be activated. In other words, the terminal device 120 may consider the serving cell for the sidelink path associated with the terminal device 110 to be activated. In some embodiments, if the indication is to activate an indirect path, the terminal device 120 may perform a transmission on the indirect path for the terminal device 110. For example, the terminal device 120 may perform a transmission over a PC5 or an ideal connection for the terminal device 110, such as performing a transmission over a SL-SCH or a PSCCH or a PSSCH. It should be understood that when the indication is to activate an indirect path, the above operations may be performed individually or in any suitable combination.

[0114] In some embodiments, if the indication is to deactivate the indirect path, the terminal device 120 may suspend transmission on the indirect path for the set of radio bearers configured for the terminal device 110. For example, the terminal device 120 may suspend transmission for all SRBs and DRBs associated with the terminal device 110.

[0115] In some embodiments, if the indication is to deactivate the indirect path, the terminal device 120 may reset the MAC entity for the sidelink interface (PC5 MAC). In some embodiments, the terminal device 120 may also reset the MAC entity for the air interface associated with the terminal device 110 (Uu MAC).

[0116] In some embodiments, if the indication is to deactivate the indirect path, the terminal device 120 may reestablish the RLC entity of the radio bearer (e.g., the indirect bearer) associated with the indirect path. In some embodiments, the indirect bearer may include at least an SRB. In some embodiments, the terminal device 120 may reestablish the PC5 RLC entity and the Uu RLC entity of the indirect bearer associated with the terminal device 110.

[0117] In some embodiments, if the indication is to deactivate the indirect path, the terminal device 120 may consider the serving cell associated with the terminal device 110 to be deactivated. In other words, the terminal device 120 may consider the serving cell for the sidelink path associated with the terminal device 110 to be deactivated.

[0118] In some embodiments, if the indication is to deactivate the indirect path, the terminal device 120 may deactivate the indirect path. For example, the terminal device 120 may not perform transmissions on PC5 or the ideal connection for the terminal device 110, for example, no transmissions on the SL-SCH or PSCCH or PSSCH for the terminal device 110.

[0119] It should be understood that when the instruction is to deactivate the indirect path, the above operations may be performed individually or in any suitable combination.

[0120] Continue to refer Figure 4B Upon receiving the indication, the terminal device 120 may send 423 another indication for activating or deactivating at least one of the direct path or the indirect path to the terminal device 110. In some embodiments, the another indication may be sent via SL-SRB3 in a PC5RRC message. In some embodiments, the another indication may be sent in a MAC CE.

[0121] In some embodiments, if the further indication is to activate one of the direct path and the indirect path, the terminal device 110 may resume the corresponding path for the set of radio bearers configured for the terminal device 110. For example, the terminal device 110 may resume transmission of the corresponding path for all SRBs and DRBs.

[0122] In some embodiments where the other indication is activation of the direct path, if the time alignment timer is not running or the count value for the beam failure indication is equal to or higher than the threshold, the terminal device 110 may initiate a random access procedure to the SPCell or PCell of the network device 130. In some embodiments where the other indication is activation of the direct path, the terminal device 110 may resume RLF monitoring for the direct path. In some embodiments where the indication is activation of the direct path, the terminal device 110 may activate the SPCell and SCell set for the direct path. It should be understood that when the other indication is activation of the direct path, the above operations may be performed individually or in any suitable combination.

[0123] In some embodiments where the other indication is activation of an indirect path, the terminal device 110 may consider the service cell associated with the terminal device 120 to be activated. In other words, the terminal device 110 may consider the service cell for the indirect path to be activated. In some embodiments where the other indication is activation of an indirect path, the terminal device 110 may resume RLF monitoring for the indirect path. In some embodiments where the other indication is activation of an indirect path, the terminal device 110 may perform transmissions on the indirect path for the terminal device 110. For example, the terminal device 110 may perform transmissions on a PC5 connection or an ideal connection, for example, performing transmissions of a sidelink shared channel (SL-SCH) or a PSCCH or a PSSCH. It should be understood that when the other indication is activation of an indirect path, the above operations may be performed individually or in any suitable combination.

[0124] In some embodiments, if the further indication is to deactivate one of the direct path and the indirect path, the terminal device 110 may suspend the corresponding path for the set of radio bearers configured for the terminal device 110. For example, the terminal device 110 may suspend transmission of the corresponding path for all SRBs and DRBs.

[0125] In some embodiments, if the other indication is to deactivate one of the direct path and the indirect path, the terminal device 110 may reset the MAC entity corresponding to the deactivated one of the direct path and the indirect path.

[0126] In some embodiments, if the other indication is to deactivate one of the direct path and the indirect path, the terminal device 110 may reestablish the RLC entity of the radio bearer. In some embodiments, the radio bearer may include at least an SRB. In some embodiments where the path to be deactivated is an indirect path, the terminal device 110 may reestablish the RLC entity of the indirect bearer. In some embodiments where the path to be deactivated is a direct path, the terminal device 110 may reestablish the RLC entity of the direct bearer.

[0127] In some embodiments, if the other indication is to deactivate one of the direct path and the indirect path, the terminal device 110 may trigger the discarding of the PDCP SDU for the radio bearer. In some embodiments, the radio bearer may include at least an SRB. In some embodiments where the path to be deactivated is an indirect path, the terminal device 110 may trigger the PDCP entity of the indirect bearer to perform PDCP SDU discarding. In some embodiments where the path to be deactivated is a direct path, the terminal device 110 may trigger the PDCP entity of the direct bearer to perform PDCP SDU discarding.

[0128] In some embodiments where the other indication is to deactivate the direct path, the terminal device 110 may start TAT. In some embodiments where the other indication is to deactivate the direct path, the terminal device 110 may stop RLF monitoring for the direct path. In some embodiments where the other indication is to deactivate the direct path, the terminal device 110 may continue beam failure monitoring for the direct path. In some embodiments where the other indication is to deactivate the direct path, the terminal device 110 may consider the SPCell and SCell sets for the direct path to be deactivated. It should be understood that when the other indication is to deactivate the direct path, the above operations may be performed individually or in any suitable combination.

[0129] In some embodiments where the other indication is to deactivate an indirect path, the terminal device 110 may de-enable the indirect path. That is, there is no transmission on the indirect path, for example, no transmission of SL-SCH or PSCCH or PSSCH. In some embodiments where the other indication is to deactivate an indirect path, the terminal device 110 may consider that the serving cell for the indirect path is deactivated. In some embodiments where the other indication is to deactivate an indirect path, the terminal device 110 may suspend RLF monitoring for the indirect path. It should be understood that when the other indication is to deactivate an indirect path, the above operations may be performed individually or in any suitable combination.

[0130] In this way, the network can send an indication to the relay UE to control the activation or deactivation status of the direct or indirect path.

[0131] Example implementation of release or deactivation of MP

[0132] Figure 4C A schematic diagram illustrating yet another communication process 400C according to an embodiment of the present disclosure is shown. For the purpose of discussion, reference will be made to Figure 1 The process 400C may include: Figure 1 The terminal device 110, the terminal device 120 and the network device 130 are shown. It is assumed that the terminal device 110 is used as a remote UE and the terminal device 120 is used as a relay UE.

[0133] like Figure 4C As shown, the network device 130 may send 450 to the terminal device 110 the configuration of the direct path between the terminal device 110 and the network device 130 and the indirect path between the terminal device 110 and the network device 130 via the terminal device 120. That is, the terminal device 110 is configured with the MP.

[0134] The terminal device 110 may send 451 a request to release or deactivate a direct path or an indirect path to the network device 130. In some embodiments, the terminal device 110 may send the request if the terminal device 110 is low on power. In some embodiments, the terminal device 110 may send the request if the terminal device 110 does not have enough data to send. It should be understood that the terminal device 110 may send the request under any suitable conditions, and the present disclosure is not limited in this regard. That is, after the terminal device 110 is configured with an MP, the terminal device 110 may indicate to the network device 130 the release or deactivation of the MP.

[0135] In some embodiments, the request may include an indication of a path to be released or deactivated. That is, the terminal device 110 may indicate a path, such as a direct path or an indirect path, that the terminal device 110 wants or prefers to release or deactivate.

[0136] In some embodiments, the request may include an indication of a path to be maintained. That is, the terminal device 110 may indicate a path that the terminal device 110 wants or prefers to maintain, such as a direct path or an indirect path.

[0137] In some embodiments, the terminal device 110 may send the request via an RRC message. For example, the RRC message may be a UE assistance information message or any other suitable message.

[0138] In some embodiments, if the timer (also referred to herein as the third timer for convenience) is not running, the request may be sent. In some embodiments, when sending the request, the terminal device 110 may start or restart the third timer.

[0139] With process 400C, when the remote UE does not need the MP due to lack of power or data, the remote UE may indicate to the network to release or deactivate the MP.

[0140] It should be understood that the approaches described in processes 400A, 400B, and 400C may be used alone or in any suitable combination.

[0141] Example implementation of method

[0142] Accordingly, the embodiments of the present disclosure provide a communication method implemented at a terminal device and a network device. Figures 5 to 7 Describe these methods.

[0143] Figure 5 An example communication method 500 implemented at a first terminal device according to some embodiments of the present disclosure is shown. For example, the method 500 may be implemented in a Figure 1 For the purpose of discussion, reference will be made to Figure 1 Method 500 is described. It should be understood that method 500 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard.

[0144] In block 510 , a first terminal device (eg, terminal device 110 ) receives configurations for a direct path between terminal device 110 and network device 130 and an indirect path between terminal device 110 and network device 130 via a second terminal device (eg, terminal device 120 ) from network device 130 .

[0145] At block 520 , the terminal device 110 determines whether RLF is detected for one of the direct path and the indirect path and the other of the direct path and the indirect path is available. If RLF is detected for one of the direct path and the indirect path and the other of the direct path and the indirect path is available, the method 500 proceeds to block 530 .

[0146] At block 530, the terminal device 110 sends a first RRC message for RLF recovery to the network device 130 via the other of the direct path and the indirect path. The first radio resource control message indicates at least one of: the type of RLF; a measurement result associated with the terminal device 110; or a failure of the direct path and the indirect path.

[0147] In some embodiments where one of the direct path and the indirect path where the failure occurs is the indirect path, the type of radio link failure may include information of the failure in the link between the network device 130 and the terminal device 120 .

[0148] In some embodiments, the terminal device 110 may suspend the one of the direct path and the indirect path that fails. In some embodiments, the terminal device 110 may reset the MAC entity for the one of the direct path and the indirect path that fails. In some embodiments, if packet replication is not configured for a split SRB for a direct path and an indirect path, and the primary path of the split SRB is the one of the direct path and the indirect path that fails, the terminal device 110 may set the primary path to the other of the direct path and the indirect path.

[0149] In some embodiments, if the first RRC message is sent, the terminal device 110 may start or restart the timer.

[0150] In some embodiments, if the second RRC message is received, the terminal device 110 may stop the timer. The second RRC message may be used for at least one of: releasing the direct path and the indirect path that have failed; reconfiguring the direct path and the indirect path that have failed; or releasing the connection between the terminal device 110 and the network device 130.

[0151] In some embodiments, if the timer expires, the terminal device 110 may perform at least one of the following: initiate an RRC reestablishment procedure; or release the failed one of the direct path and the indirect path.

[0152] In some embodiments, if the timer is not running, the terminal device 110 may send a first RRC message for recovery of the RLF.

[0153] Utilizing method 500, the network may appropriately handle RLF based on the indication of RLF recovery.

[0154] Figure 6 An example communication method 600 implemented at a first terminal device or a second terminal device according to some embodiments of the present disclosure is shown. For example, the method 600 may be implemented at a first terminal device or a second terminal device according to some embodiments of the present disclosure. Figure 1 For the purpose of discussion, reference will be made to Figure 1 Method 600 is described. It should be understood that method 600 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard.

[0155] In box 610, a terminal device (e.g., terminal device 110 or 120) receives an indication for activating or deactivating at least one of a direct path between a first terminal device (e.g., terminal device 110) and a network device 130 or an indirect path between terminal device 110 and network device 130 via a second terminal device (e.g., terminal device 120).

[0156] At block 620, the terminal device determines whether the indication is to activate or deactivate one of the direct path and the indirect path. If the indication is to activate one of the direct path and the indirect path, the method 600 proceeds to block 630. At block 630, the terminal device performs an activation operation.

[0157] If the indication is to deactivate one of the direct path and the indirect path, the method 600 proceeds to block 640. At block 640, the terminal device performs a deactivation operation.

[0158] In some embodiments, the terminal device may be a first terminal device (e.g., a remote UE). In some embodiments, the activation operation may include restoring one of a direct path and an indirect path that is activated for a set of radio bearers configured for the first terminal device. In some embodiments, if the indication is to activate a direct path, the activation operation may include at least one of the following: initiating a random access process to a specific cell of a network device based on determining that a time alignment timer is not running or a count value for a beam failure indication is equal to or higher than a threshold; restoring radio link failure monitoring for a direct path; or activating a specific cell and a set of secondary cells for the direct path. In some embodiments, if the indication is to activate an indirect path, the activation operation may include at least one of the following: considering that a serving cell associated with the second terminal device is activated; restoring radio link failure monitoring for the indirect path; or performing an indirect path for the first terminal device. It should be understood that any combination of the above operations is also feasible.

[0159] In some embodiments where the terminal device is a first terminal device (e.g., a remote UE), the deactivation operation may include at least one of the following: suspending the deactivated one of the direct path and the indirect path for a set of radio bearers configured for the first terminal device; resetting the medium access control entity corresponding to the deactivated one of the direct path and the indirect path; reestablishing the radio link control entity of the radio bearer associated with the deactivated one of the direct path and the indirect path; triggering the discarding of the PDCP SDU for the radio bearer associated with the deactivated one of the direct path and the indirect path. In some embodiments where the indication is to deactivate the direct path, the deactivation operation may include: performing at least one of the following: starting a time alignment timer; stopping radio link failure monitoring for the direct path; continuing beam failure monitoring for the direct path; or considering a specific cell and a set of secondary cells for the direct path to be deactivated. In some embodiments where the indication is to deactivate the indirect path, the deactivation operation may include at least one of the following: disabling the indirect path; considering the serving cell for the indirect path to be deactivated; or suspending radio link failure monitoring for the indirect path.

[0160] In some embodiments, the terminal device may be a second terminal device (e.g., a relay UE). In some embodiments in which one of the direct path and the indirect path that is activated is the indirect path, the activation operation may include at least one of the following: considering that the service cell associated with the second terminal device is activated; or executing the indirect path for the first terminal device. In some embodiments in which one of the direct path and the indirect path that is deactivated is the indirect path, the deactivation operation may include at least one of the following: suspending the indirect path for a set of radio bearers configured for the first terminal device; resetting at least one of the medium access control entities for the air interface and the sidelink interface associated with the first terminal device; reestablishing the radio link control entity of the radio bearer associated with the indirect path; considering that the service cell associated with the second terminal device is deactivated; or disabling the indirect path.

[0161] In some embodiments where the terminal device is a second terminal device (e.g., a relay UE), the indication may include an identification of the first terminal device. In some embodiments where the terminal device is a second terminal device (e.g., a relay UE), the second terminal device may send another indication to the first terminal device for activating or deactivating at least one of the direct path or the indirect path.

[0162] Using the method 600, activation or deactivation of a direct or indirect path may be enabled.

[0163] Figure 7An example communication method 700 implemented at a first terminal device according to some embodiments of the present disclosure is shown. For example, the method 700 may be implemented in a Figure 1 For the purpose of discussion, reference will be made to Figure 1 Method 700 is described. It should be understood that method 700 may include additional blocks not shown and / or may omit some of the blocks shown, and the scope of the present disclosure is not limited in this regard.

[0164] In block 710 , a first terminal device (eg, terminal device 110 ) receives from network device 130 configurations for a direct path between terminal device 110 and network device 130 and an indirect path between terminal device 110 and network device 130 via a second terminal device (eg, terminal device 120 ).

[0165] At block 720 , the terminal device 110 sends a request to the network device 130 to release or deactivate the direct path or the indirect path.

[0166] In some embodiments, the request may include: an indication of a path to be released or deactivated; or an indication of a path to be maintained. In some embodiments, the terminal device 110 may send the request via an RRC message.

[0167] In some embodiments, if the timer is not running, the terminal device 110 may send the request. In some embodiments, if the request is sent, the terminal device 110 may start or restart the timer.

[0168] Using method 700, when the terminal device does not need the MP due to lack of power or data, the terminal device can request the network to release or deactivate the MP.

[0169] It should be understood that the operations of methods 500 to 700 are combined with Figures 4A to 4C The operations described are similar, so for the sake of brevity, further details are not repeated here.

[0170] Example implementations of devices and apparatus

[0171] Figure 8 is a simplified block diagram of a device 800 suitable for implementing an embodiment of the present disclosure. The device 800 can be considered as Figure 1 Another example implementation of the terminal device 110 or the terminal device 120 or the network device 130 is shown. Therefore, the device 800 can be implemented at the terminal device 110 or the terminal device 120 or the network device 130 or as at least a part of the terminal device 110 or the terminal device 120 or the network device 130.

[0172] As shown, the device 800 includes a processor 810, a memory 820 coupled to the processor 810, a suitable transmitter (TX) and receiver (RX) 840 coupled to the processor 810, and a communication interface coupled to the TX / RX 840. The memory 810 stores at least a portion of the program 830. The TX / RX 840 is used for bidirectional communication. The TX / RX 840 has at least one antenna to facilitate communication, but in fact the access node mentioned in this application may have several antennas. The communication interface may represent any interface required for communication with other network elements, such as an X2 / Xn interface for bidirectional communication between eNB / gNB, an S1 / NG interface for communication between a mobility management entity (MME) / access and mobility management function (AMF) / SGW / UPF and an eNB / gNB, a Un interface for communication between an eNB / gNB and a relay node (RN), or a Uu interface for communication between an eNB / gNB and a terminal device.

[0173] Assume that program 830 includes program instructions that, when executed by associated processor 810, enable device 800 to operate in accordance with embodiments of the present disclosure, as referred to herein. Figures 1 to 7 As discussed above. The embodiments herein may be implemented by computer software executable by a processor 810 of the device 800, or by hardware, or by a combination of software and hardware. The processor 810 may be configured to implement various embodiments of the present disclosure. In addition, the combination of the processor 810 and the memory 820 may form a processing component 850 suitable for implementing various embodiments of the present disclosure.

[0174] The memory 820 may be of any type suitable for the local technology network and may be implemented using any suitable data storage technology, such as, as non-limiting examples, non-transitory computer-readable storage media, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and removable memory. Although only one memory 820 is shown in the device 800, there may be several physically separate memory modules in the device 800. As non-limiting examples, the processor 810 may be of any type suitable for the local technology network and may include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. The device 800 may have multiple processors, such as a dedicated integrated circuit chip that is time-slave to a clock that synchronizes a main processor.

[0175] In some embodiments, a first terminal device includes a circuit device configured to: receive, from a network device, a configuration for a direct path between the first terminal device and the network device and an indirect path between the first terminal device and the network device via a second terminal device; and based on determining that a radio link failure is detected for one of the direct path and the indirect path and the other of the direct path and the indirect path is available, send a first radio resource control message for recovery of the radio link failure to the network device via the other of the direct path and the indirect path, the first radio resource control message indicating at least one of: the type of the radio link failure; a measurement result associated with the first terminal device; or one of the direct path and the indirect path where a failure occurs.

[0176] In some embodiments, the first terminal device or the second terminal device includes a circuit device configured to: receive an indication for activating or deactivating at least one of a direct path between the first terminal device and a network device or an indirect path between the first terminal device and the network device via a second terminal device; perform an activation operation based on determining that the indication is to activate one of the direct path and the indirect path; and perform a deactivation operation based on determining that the indication is to deactivate one of the direct path and the indirect path.

[0177] In some embodiments, the first terminal device includes a circuit device configured to: receive, from a network device, a configuration for a direct path between the first terminal device and the network device and an indirect path between the first terminal device and the network device via a second terminal device; and send a request to the network device to release or deactivate the direct path or the indirect path.

[0178] The term "circuitry" as used herein may refer to a combination of hardware circuits and / or hardware circuits and software. For example, a circuit arrangement may be a combination of analog and / or digital hardware circuits and software / firmware. As another example, a circuit arrangement may be any part of a hardware processor with software, including a digital signal processor, software, and memory that work together to enable devices such as terminal equipment or network equipment to perform various functions. In yet another example, a circuit arrangement may be a hardware circuit and / or processor, such as a microprocessor or a part of a microprocessor, which requires software / firmware to operate, but when software is not required to operate, the software may not exist. As used herein, the term circuit arrangement also encompasses the implementation of only a hardware circuit or processor or a part of a hardware circuit or processor and its (or their) accompanying software and / or firmware.

[0179] In general, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be run by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are shown and described as block diagrams, flow charts, or using some other graphical representations, it will be understood that the boxes, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof, as non-limiting examples.

[0180] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer executable instructions such as those included in program modules that are executed in a device on a target real or virtual processor to implement the above referenced Figures 1 to 7 The process or method described. In general, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The functions of program modules can be combined or separated between program modules as needed in various embodiments. Machine executable instructions for program modules can be run in local or distributed devices. In distributed devices, program modules can be located in both local storage media and remote storage media.

[0181] The program code for implementing the disclosed method can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that the program code is implemented when the processor or controller is run. The program code can be run completely on the machine, partially on the machine, as an independent software package, partially on the machine and partially on a remote machine, or completely on a remote machine or server.

[0182] The above program code can be implemented on a machine-readable medium, which can be any tangible medium that can contain or store a program used by an instruction execution system, device or equipment or used in conjunction with an instruction execution system, device or equipment. The machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium can include, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared or semiconductor system, device or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium will include an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0183] In addition, although operations are described in a particular order, this should not be understood as requiring the specific order shown or to perform these operations in order, or to perform all the operations shown, to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these details should not be interpreted as limitations on the scope of the present disclosure, but should be interpreted as descriptions of features peculiar to a particular embodiment. Certain features described in the context of separate embodiments may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.

[0184] Although the present disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or actions described above. Instead, the specific features and actions described above are disclosed as example forms of implementing the claims.

Claims

1. A method of communication, comprising: At a first terminal device, receiving, from a network device, configuration for a direct path between the first terminal device and the network device and an indirect path between the first terminal device and the network device via a second terminal device; as well as Based on determining that a radio link failure is detected for one of the direct path and the indirect path and the other of the direct path and the indirect path is available, sending a first radio resource control message for recovery of the radio link failure to the network device via the other of the direct path and the indirect path, the first radio resource control message indicating at least one of the following: type of the radio link failure; a measurement result associated with the first terminal device; or One of the direct path and the indirect path fails.

2. The method according to claim 1, wherein the one of the direct path and the indirect path in which the failure occurs is the indirect path, and the type of the radio link failure includes information of the failure in the link between the network device and the second terminal device.

3. The method according to claim 1, further comprising at least one of the following: suspending the one of the direct path and the indirect path where the failure occurs; resetting a media access control entity for a failed one of the direct path and the indirect path; or The primary path is set to the other of the direct path and the indirect path based on determining that packet duplication is not configured for separate signaling radio bearers for the direct path and the indirect path and a primary path of the separate signaling radio bearer is the one of the direct path and the indirect path that fails.

4. The method according to claim 1, further comprising at least one of the following: Starting or restarting a timer according to determining that the first radio resource control message is sent; According to determining that a second radio resource control message is received, stopping the timer, the second radio resource control message being used for one of the following: releasing the one of the direct path and the indirect path where the fault occurs; reconfiguring the failed one of the direct path and the indirect path; or releasing the connection between the first terminal device and the network device; or performing at least one of the following according to determining that the timer expires: Initiate a radio resource control re-establishment procedure; or The failed one of the direct path and the indirect path is released.

5. The method of claim 4, wherein sending the first radio resource control message comprises: Based on determining that the timer is not running, sending the first radio resource control message for recovery of the radio link failure.

6. A method of communication, comprising: At a terminal device, receiving an indication for activating or deactivating at least one of a direct path between a first terminal device and a network device or an indirect path between the first terminal device and the network device via a second terminal device; performing an activation operation according to determining that the indication is to activate one of the direct path and the indirect path; as well as Based on determining that the indication is to deactivate one of the direct path and the indirect path, a deactivation operation is performed. The method according to claim 6 , wherein the terminal device is the first terminal device.

8. The method according to claim 7, wherein the activation operation comprises at least one of the following: for a set of radio bearers configured for the first terminal device, resuming the activated one of the direct path and the indirect path; According to determining that the instruction is to activate the direct path, performing at least one of the following: initiating a random access procedure to a special cell of the network device based on determining that a time alignment timer is not running or a count value for a beam failure indication is equal to or greater than a threshold; resuming radio link failure monitoring for the direct path; or activating a special cell and a set of secondary cells for the direct path; or performing at least one of the following according to determining that the indication is to activate the indirect path: Considering that the serving cell associated with the second terminal device is activated; resuming radio link failure monitoring for the indirect path; or Transmission on the indirect path is performed for the first terminal device.

9. The method according to claim 7, wherein the deactivation operation comprises at least one of the following: suspending, for a set of radio bearers configured for the first terminal device, the deactivated one of the direct path and the indirect path; resetting a medium access control entity corresponding to the deactivated one of the direct path and the indirect path; a radio link control entity reestablishing a radio bearer associated with the deactivated one of the direct path and the indirect path; triggering discarding of a Packet Data Convergence Protocol (PDCP) Service Data Unit (SDU) for a radio bearer associated with the deactivated one of the direct path and the indirect path; According to determining that the instruction is to deactivate the direct path, performing at least one of the following: Start the time alignment timer; stopping radio link failure monitoring for the direct path; continuing beam failure monitoring for the direct path; or The special cell and the set of secondary cells used for the direct path are considered to be deactivated; or In response to determining that the instruction is to deactivate the indirect path, performing at least one of the following: disabling the indirect path; the serving cell for the indirect path is considered to be deactivated; or Radio link failure monitoring for the indirect path is suspended.

10. The method according to claim 6, wherein the terminal device is the second terminal device.

11. The method of claim 10, wherein the one of the direct path and the indirect path that is activated is the indirect path, and wherein performing the activation operation comprises at least one of: The serving cell associated with the first terminal device is considered to be activated; or Transmission on the indirect path is performed for the first terminal device.

12. The method of claim 10, wherein the one of the direct path and the indirect path that is deactivated is the indirect path, and wherein performing the deactivation operation comprises at least one of: suspending the indirect path for a set of radio bearers configured for the first terminal device configuration; resetting at least one of the medium access control entities for a sidelink interface and an air interface associated with the first terminal device; reestablishing a radio link control entity of a radio bearer associated with the indirect path; The serving cell associated with the first terminal device is considered to be deactivated; or Disenable the indirect path. The method according to claim 10 , wherein the indication comprises an identification of the first terminal device.

14. The method according to claim 10, further comprising: Another indication is sent to the first terminal device, where the other indication is used to activate or deactivate at least one of the direct path or the indirect path.

15. A method of communication, comprising: At a first terminal device, receiving, from a network device, configuration for a direct path between the first terminal device and the network device and an indirect path between the first terminal device and the network device via a second terminal device; as well as A request for releasing or deactivating the direct path or the indirect path is sent to the network device.

16. The method of claim 15, wherein the request comprises: an indication of a path to be released or deactivated; or An indication of the path to be maintained.

17. The method of claim 15, wherein sending the request comprises: Based on determining that the timer is not running, sending the request, and The method further includes: starting or restarting the timer according to determining that the request is sent.

18. The method of claim 15, wherein sending the request comprises: The request is sent via a radio resource control message.

Images