WO2026031231A1 - Dispositifs et procédés de communication - Google Patents

Dispositifs et procédés de communication

Info

Publication number
WO2026031231A1
WO2026031231A1 PCT/CN2024/111275 CN2024111275W WO2026031231A1 WO 2026031231 A1 WO2026031231 A1 WO 2026031231A1 CN 2024111275 W CN2024111275 W CN 2024111275W WO 2026031231 A1 WO2026031231 A1 WO 2026031231A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
path
layer
relay
connection
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/111275
Other languages
English (en)
Inventor
You Li
Gang Wang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NEC Corp
Original Assignee
NEC Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by NEC Corp filed Critical NEC Corp
Priority to PCT/CN2024/111275 priority Critical patent/WO2026031231A1/fr
Publication of WO2026031231A1 publication Critical patent/WO2026031231A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22—Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/03—Reselecting a link using a direct mode connection
    • H04W36/033—Reselecting a link using a direct mode connection in pre-organised networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/19—Connection re-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/23—Manipulation of direct-mode connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user

Definitions

  • Example embodiments of the present disclosure generally relate to the field of communication techniques and in particular, to devices and methods for the connection management of multi-hop path.
  • a terminal device e.g., user equipment, UE
  • D2D sidelink communications
  • a terminal device may communicate with another terminal device via a direct link or an indirect link.
  • the terminal devices may communicate with each other via at least one further terminal device, which is called relay terminal device or relay terminal device.
  • embodiments of the present disclosure provide a solution of connection management of multi-hop path.
  • a first terminal device comprising: a processor configured to cause the first terminal device to: receive, from a first apparatus, an indication for multi-hop path switching; and switch from a first path to a second path based on the indication, both the first path and the second path starting from the first terminal device to a network device, the first path comprising one or more second terminal devices and a third terminal device connected to the network device, the second path excluding at least one of the one or more second terminal devices and/or the third terminal device.
  • a first apparatus comprising: a processor configured to cause the first apparatus to: transmit, to the first terminal device, an indication for multi-hop path switching, to cause the first terminal device to switch from a first path to a second path based on the indication, both the first path and the second path starting from the first terminal device to a network device, the first path comprising one or more second terminal devices and a third terminal device connected to the network device, the second path excluding at least one of the one or more second terminal devices or the third terminal device.
  • a third terminal device comprises: a processor configured to cause the third terminal device to: receive, from the one or more second terminal devices, a message comprising an indication for releasing a connection associated with the first terminal device and the third terminal device connected to a network device, wherein the first terminal device is to switch from a first path to a second path, both the first path and the second path starting from the first terminal device to the network device, the first path comprising one or more second terminal devices and the third terminal device connected to the network device, the second path excluding at least one of the one or more second terminal devices and/or the third terminal device.
  • a communication method performed by a first terminal device.
  • the method comprises: receiving, from a first apparatus, an indication for multi-hop path switching; and switching from a first path to a second path based on the indication, both the first path and the second path starting from the first terminal device to a network device, the first path comprising one or more second terminal devices and a third terminal device connected to the network device, the second path excluding at least one of the one or more second terminal devices and/or the third terminal device.
  • a communication method performed by a first apparatus.
  • the method comprises: transmitting, to the first terminal device, an indication for multi-hop path switching, to cause the first terminal device to switch from a first path to a second path based on the indication, both the first path and the second path starting from the first terminal device to a network device, the first path comprising one or more second terminal devices and a third terminal device connected to the network device, the second path excluding at least one of the one or more second terminal devices or the third terminal device.
  • a communication method performed by a third terminal device.
  • the method comprises: receiving, from the one or more second terminal devices, a message comprising an indication for releasing a connection associated with the first terminal device and the third terminal device connected to a network device, wherein the first terminal device is to switch from a first path to a second path, both the first path and the second path starting from the first terminal device to the network device, the first path comprising one or more second terminal devices and the third terminal device connected to the network device, the second path excluding at least one of the one or more second terminal devices and/or the third terminal device.
  • a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to carry out the method according to the fourth, fifth, or sixth aspect.
  • FIGS. 1A to 1C illustrate example communication environments in which example embodiments of the present disclosure can be implemented, respectively;
  • FIG. 2 illustrates a signaling flow of procedure of connection management of multi-hop path in accordance with some embodiments of the present disclosure
  • FIGS. 3A to 3D illustrate schematic diagrams of examples of paths of multi-hop path in accordance with some embodiments of the present disclosure, respectively;
  • FIGS. 4A and 4B illustrate example protocol stacks for sidelink communications, respectively
  • FIG. 5 illustrates schematic diagram of example of multi-hop path in accordance with some embodiments of the present disclosure
  • FIG. 6 illustrates a flowchart of a communication method implemented at a first terminal device according to some example embodiments of the present disclosure
  • FIG. 7 illustrates a flowchart of a communication method implemented at a first apparatus according to some example embodiments of the present disclosure
  • FIG. 8 illustrates a flowchart of a communication method implemented at a third terminal device according to some example embodiments of the present disclosure.
  • FIG. 9 illustrates a simplified block diagram of an apparatus that is suitable for implementing example embodiments of the present disclosure.
  • terminal device refers to any device having wireless or wired communication capabilities.
  • the terminal device include, but 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 communication (MTC) devices, devices on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure/network, devices for Integrated Access and Backhaul (IAB) , Space borne vehicles or Air borne vehicles in Non-terrestrial networks (NTN) including Satellites and High Altitude Platforms (HAPs) encompassing Unmanned Aircraft Systems (UAS) , eXtended Reality (XR) devices including different types of realities such as Augmented Reality (AR) , Mixed Reality (MR) and Virtual Reality (VR) , the unmanned aerial vehicle (UAV)
  • UE user equipment
  • the ‘terminal device’ can further has ‘multicast/broadcast’ feature, 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 multiple Subscriber Identity Module (SIM) as known as Multi-SIM.
  • SIM Subscriber Identity Module
  • the term “terminal device” can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal or a wireless device.
  • network device refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate.
  • a network device include, but not limited to, a Node B (Node or NB) , an evolved node (eNodeB or eNB) , a next generation node (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 intelligent surface (RIS) , and the like.
  • Node B Node B
  • eNodeB or eNB evolved node
  • gNB next generation node
  • TRP transmission reception point
  • RRU remote radio unit
  • RH radio head
  • RRH remote radio head
  • IAB node a low power node
  • RIS reconfigurable intelligent surface
  • the terminal device or the network device may have Artificial intelligence (AI) or Machine learning capability. It generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.
  • AI Artificial intelligence
  • Machine learning capability it generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.
  • the terminal or the network device may work on several frequency ranges, e.g., FR1 (e.g., 450 MHz to 6000 MHz) , FR2 (e.g., 24.25GHz to 52.6GHz) , frequency band larger than 100 GHz as well as Tera Hertz (THz) . It can further work on licensed/unlicensed/shared spectrum.
  • FR1 e.g., 450 MHz to 6000 MHz
  • FR2 e.g., 24.25GHz to 52.6GHz
  • THz Tera Hertz
  • the terminal device may have more than one connection with the network devices under Multi-Radio Dual Connectivity (MR-DC) application scenario.
  • MR-DC Multi-Radio Dual Connectivity
  • the terminal device or the network device can work on full duplex, flexible duplex and cross division duplex modes.
  • the embodiments of the present disclosure may be performed in test equipment, e.g., signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal device, test network device, channel emulator.
  • the terminal device may be connected with a first network device and a second network device.
  • One of the first network device and the second network device may be a master node and the other one may be a secondary node.
  • the first network device and the second network device may use different radio access technologies (RATs) .
  • the first network device may be a first RAT device and the second network device may be a second RAT device.
  • the first RAT device is eNB and the second RAT device is gNB.
  • Information related with different RATs may be transmitted to the terminal device from at least one of the first network device or the second network device.
  • first information may be transmitted to the terminal device from the first network device and second information may be transmitted to the terminal device from the second network device directly or via the first network device.
  • information related with configuration for the terminal device configured by the second network device may be transmitted from the second network device via the first network device.
  • Information related with reconfiguration for the terminal device configured by the second network device may be transmitted to the terminal device from the second network device directly or via the first network device.
  • the singular forms ‘a’ , ‘an’ and ‘the’ are intended to include the plural forms as well, unless the context clearly indicates otherwise.
  • the term ‘includes’ and its variants are to be read as open terms that mean ‘includes, but is not limited to. ’
  • the term ‘based on’ is to be read as ‘at least in part based on. ’
  • the term ‘one embodiment’ and ‘an embodiment’ are to be read as ‘at least one embodiment. ’
  • the term ‘another embodiment’ is to be read as ‘at least one other embodiment. ’
  • the terms ‘first, ’ ‘second, ’ and the like may refer to different or same objects. Other definitions, explicit and implicit, may be included below.
  • values, procedures, or apparatus are referred to as ‘best, ’ ‘lowest, ’ ‘highest, ’ ‘minimum, ’ ‘maximum, ’ or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.
  • the term “resource, ” “transmission resource, ” “uplink resource, ” or “downlink resource” may refer to any resource for performing a communication, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, or any other resource enabling a communication, and the like.
  • a resource in both frequency domain and time domain will be used as an example of a transmission resource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains.
  • a terminal device e.g., user equipment, UE
  • source (remote/end) terminal device As used herein, terms of “source (remote/end) terminal device” , “source (remote/end) UE” , “transmitting (TX) (remote/end) terminal device” , “transmitting (TX) (remote/end) UE” , “initiating (remote/end) terminal device” , “initiating (remote/end) UE” , “first (remote/end) terminal device” , “first (remote/end) UE” may be used interchangeably.
  • target (remote/end) terminal device As used herein, terms of “target (remote/end) terminal device” , “target (remote/end) UE” , “destination (remote/end) terminal device” , “destination (remote/end) UE” , “receiving (RX) (remote/end) terminal device” , “receiving (RX) (remote/end) UE” , “second (remote/end) terminal device” , “second (remote/end) UE” may be used interchangeably.
  • release As used herein, terms of “release” , “delete” , “clear” and “remove” may be used interchangeably.
  • RLC channel As used herein, terms of “RLC channel” , “RLC Relay channel” , “PC5 RLC Relay channel” , “RLC relay channel” and “PC5 RLC relay channel” may be used interchangeably.
  • wording of “apply a default/PC5 Relay RLC channel” refers to “apply RLC specified/default configuration of SL-RLCx” , “apply RLC default/specified configuration of (default/specified) PC5 Relay RLC channel” , “establish a Relay RLC channel/entity” , “apply a PC5 Relay RLC channel” , “apply the (default/specified) configuration of (default/specified) PC5 Relay RLC channel” and so on.
  • wording of “release a default/specified PC5 Relay RLC channel” refers to “release RLC specified/default configuration of PC5 Relay RLC channel” “release RLC specified/default configuration of SL-RLCx” , “release a Relay RLC channel/entity” and so on.
  • PC5 unicast link As used herein, terms of “PC5 unicast link” , “PC5 radio resource control (RRC) connection” , “PC5-RRC connection” , “PC5-Sconnection” , “PC5 connection” , “Layer-2 link” , and “Layer-2 unicast link” may be used interchangeably.
  • RRC radio resource control
  • lower layer of RRC layer
  • L2 sublayers such as MAC layer, RLC layer, or physical layer.
  • the term “Uu” is the air interface between the gNB and the UE.
  • the Uu interface is responsible for facilitating wireless communication by transmitting radio signals over the air.
  • the Uu interface connects the UE to the 5G RAN, which is managed by the gNB. It allows for the transmission of both user data (such as voice, video, and internet traffic) and control information (such as signaling messages) .
  • (intra-gNB) multi-hop indirect to direct path switching using the conventional framework need to be studied.
  • the mechanism for (intra-gNB) multi-hop indirect to single-hop indirect path switching using the conventional framework also needs to be developed.
  • there may be abnormal problems of intermediate relay UE occur during the switching.
  • the mechanism for (intra-gNB) direct to multi-hop indirect path switching and the mechanism for (intra-gNB) single-hop indirect to multi-hop indirect path switching are also to be developed.
  • an indication for multi-hop path switching is proposed.
  • the multi-hop path switching includes switching from a first path to a second path based on the indication, where both the first path and the second path start from the first terminal device to a network device.
  • the first path includes one or more second terminal devices and a third terminal device connected to the network device.
  • the second path excludes one of the one or more second terminal devices and/or the third terminal device.
  • FIGS. 1A to 1C illustrate example communication environments 100A to 100C in which example embodiments of the present disclosure can be implemented.
  • a terminal device also referred to as remote UE or multi-hop remote UE (denoted as UE1) communicates with a network device, e.g., a gNB via two terminal devices, namely, a U2U relay (denoted as UE2) and a U2N relay (denoted as UE3) .
  • the U2N relay may be a terminal device that is between another terminal device and the network device.
  • the communication between the UE1 and the UE2 is referred to as the 1 st hop
  • the communication between the UE2 and the UE3 is referred to as the 2 nd hop
  • the communication between the UE3 and the gNB is referred to as the 3 rd hop.
  • a sidelink is a communication mode that allows direct communications between two or more terminal devices without the communications going through network device.
  • SL communications may be carried out on a wireless interface, e.g., PC5 interface.
  • SL communications may be unicast, groupcast, or broadcast, and may be used for device-to-device (D2D) communications, vehicle-to-everything (V2X) communications, etc.
  • D2D device-to-device
  • V2X vehicle-to-everything
  • U2U relay communication may be useful in a variety of settings such as for communication in public safety networks, or in out-of-coverage or network overload scenarios.
  • the remote UE and the U2U relay may communicate with each other via sidelink (SL) connection (s) .
  • the remote UE may communicate with the gNB via the U2U relay and the U2N relay.
  • the U2U relay may be referred to as an intermedia relay UE, a U2U relay UE or the first relay UE.
  • the U2N relay operates as a relay for communications between the remote UE and the gNB.
  • the U2N relay is connected to the gNB.
  • the U2N relay may be referred to as a relay terminal device, a U2N relay UE or the last relay UE or a serving relay terminal device for the remote UE and the gNB.
  • the U2N relay may relay traffic from the remote UE to the gNB.
  • the remote UE is referred to as a source terminal device, or a transmitting (TX) terminal device
  • the gNB is referred to as a destination terminal device, a target terminal device, or a receiving (RX) terminal device.
  • the communications between any two of the remote UE, the U2U relay, the U2N relay, and the gNB may be bidirectional.
  • the 1st hop and the 2nd hop may be sidelink communications.
  • these hops may be implemented using the PC5 unicast link (also referred to as PC5-RRC connection) .
  • the PC5 unicast link may be per-hop link between the remote UE and the U2U relay.
  • the PC5 unicast link may be end-to-end link between the remote UE and the U2N relay.
  • the communication environment 100A may include any suitable number of devices configured to implementing example embodiments of the present disclosure.
  • the communication environment 100B comprises the remote UE (UE1) , U2U relays (UE2 and UE4) , the U2N relay (UE3) , and the gNB.
  • the hop between the UE1 and the UE2 is named the 1 st hop
  • the hop between the UE2 and the UE4 is named the 2 nd hop
  • the hop between the UE4 and the UE3 is named the 3 rd hop
  • the hop between the UE3 and the gNB is named the 4 th hop.
  • the remote UE and the U2U relays, and the U2N relay and the gNB may communicate with each other via SL connection (s) .
  • the remote UE may communicate with the gNB via the U2U relays (UE2 and UE4) and the U2N relay.
  • the U2U relays may be intermedia relay UEs.
  • the U2N relay operates as a relay for communications between the remote UE and the gNB.
  • the U2N relay is connected to the gNB.
  • the U2N relay may be referred to as a relay terminal device, or a serving relay terminal device for the remote UE and the gNB.
  • the U2N relay may relay traffic from the remote UE to the gNB.
  • the remote UE is referred to as a source terminal device, or a transmitting (TX) terminal device
  • the gNB is referred to as a destination terminal device, a target terminal device, or a receiving (RX) terminal device.
  • the communication between the remote UE, the U2U relay, the U2N relay, and the gNB may be bidirectional.
  • the 1 st hop, the 2 nd hop, and the 3 rd hop may be sidelink.
  • these hops may be implemented as PC5 unicast links (also referred to as PC5-RRC connections) .
  • the PC5 unicast link may be per-hop link between the remote UE and the U2U relay.
  • the PC5 unicast link may be per-hop link between the U2U relay (UE2) and another U2U relay (UE4) .
  • the PC5 unicast link may be end-to-end link between the remote UE and the U2N relay.
  • the communication environment 100B may include any suitable number of devices configured to implementing example embodiments of the present disclosure.
  • the communication environment 100C comprises the remote UE (UE1) , three U2U relays (UE2, UE4 and UE5) , the U2N relay (UE3) , and the gNB.
  • the hop between the UE1 and the UE2 is named the 1 st hop
  • the hop between the UE2 and the UE4 is named the 2 nd hop
  • the hop between the UE4 and the UE5 is named the 3 rd hop
  • the hop between the UE5 and the UE3 is named the 4 th hop
  • the hop between the UE3 and the gNB is named the 5 th hop.
  • the remote UE and the U2U relays, and the U2N relay and the gNB may communicate with each other via SL connection (s) . Further, the remote UE may communicate with the gNB via the U2U relays and the U2N relay.
  • the U2U relays may be intermedia relay UEs.
  • the U2N relay operates as a relay for communications between the remote UE and the gNB.
  • the U2N relay is connected to the gNB.
  • the U2N relay may be referred to as a relay terminal device, or a serving relay terminal device for the remote UE and the gNB.
  • the U2N relay may relay traffic from the remote UE to the gNB.
  • the remote UE is referred to as a source terminal device, or a transmitting (TX) terminal device
  • the gNB is referred to as a destination terminal device, a target terminal device, or a receiving (RX) terminal device.
  • the communication between the remote UE, the U2U relay, the U2N relay, and the gNB may be bidirectional.
  • the 1 st hop, the 2 nd hop, the 3 rd hop, and the 4 th hop may be sidelink.
  • these hops may be implemented as PC5 unicast links.
  • the PC5 unicast link may be per-hop link between the remote UE and the U2U relay.
  • the PC5 unicast link may be per-hop link between the U2U relay (e.g., UE2) and another U2U relay (e.g., UE4) .
  • the PC5 unicast link may be end-to-end link between the remote UE and the U2N relay.
  • the communication environment 100C may include any suitable number of devices configured to implementing example embodiments of the present disclosure.
  • the communications in the communication environments 100A to 100C may conform to any suitable standards including, but not limited to, Global System for Mobile Communications (GSM) , Long Term Evolution (LTE) , LTE-Evolution, LTE-Advanced (LTE-A) , New Radio (NR) , Wideband Code Division Multiple Access (WCDMA) , Code Division Multiple Access (CDMA) , GSM EDGE Radio Access Network (GERAN) , Machine Type Communication (MTC) and the like.
  • GSM Global System for Mobile Communications
  • LTE Long Term Evolution
  • LTE-Evolution LTE-Advanced
  • NR New Radio
  • WCDMA Wideband Code Division Multiple Access
  • CDMA Code Division Multiple Access
  • GERAN GSM EDGE Radio Access Network
  • MTC Machine Type Communication
  • Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or the sixth generation (6G) networks.
  • FIG. 2 illustrates a signaling flow 200 of a procedure of connection management of multi-hop path in accordance with some embodiments of the present disclosure.
  • the signaling flow 200 will be discussed with reference to FIGS. 1A to 1C.
  • the signaling flow 200 involves a first terminal device 210, a first apparatus 220, and a third terminal device 230.
  • the first terminal device 210 may be implemented as a remote terminal device or an end terminal device, including the remote UE (UE1) in FIGS 1A to 1C.
  • the first terminal device 210 may be a mobile phone, a tablets, laptop, an IoT device, or any other equipment that may access to network services.
  • the first apparatus 220 includes a device that may transmit an indication for multi-hop path switching to the first terminal device.
  • the first apparatus 220 may be implemented as the gNB and one of the U2U relays in FIGS. 1A to 1C.
  • the first apparatus 220 may be a core network device for example.
  • the third terminal device 230 may be implemented as a relay UE connected to the gNB or other network device including the U2N relay (UE3) in FIGS. 1A to 1C.
  • the first apparats 220 transmits (2010) , to the first terminal device 210, an indication for multi-hop path switching, such as multi-hop indirect to single-hop indirect path switching and multi-hop indirect to direct path switching .
  • the first terminal device 210 receives (2020) , from the first apparatus 220, the indication for multi-hop path switching.
  • the first terminal device 210 switch (2030) from a first path to a second path based on the indication. Additionally, both the first path and the second path start from the first terminal device 210 to a network device. Furthermore, the first path includes one or more second terminal devices and a third terminal device 230 connected to the network device. Moreover, the second path excludes one of the one or more second terminal devices and/or the third terminal device 230.
  • the first apparatus 220 transmits (2040) , to the third terminal device 230, a message including an indication for releasing a connection associated with the first terminal device 210 and the third terminal device 230 connected to a network device.
  • the third terminal device 230 receives (2050) , from the first apparatus 220, a message including an indication for releasing a connection associated with the first terminal device 210 and the third terminal device 230 connected to a network device.
  • the first terminal device 210 is to switch from a first path to a second path. Specifically, both the first path and the second path start from the first terminal device 210 to a network device.
  • the first path includes one or more second terminal devices and a third terminal device 230 connected to the network device.
  • the second path excludes, but not limited to, one of the one or more second terminal devices and/or the third terminal device 230.
  • the indication for multi-hop path switching may be received from the network device or one of the one or more second terminal devices.
  • the second path may exclude, but not limited to, the one or more second terminal devices.
  • the first terminal device 210 may cause a part of a first connection (also referred to as a PC5 unicast link or a PC5-RRC connection) associated with the first terminal device 210 and one of the one or more second terminal devices to be released.
  • the part of the first connection may include, but not limited to, a radio resource control (RRC) layer, a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a sidelink relay adaptation protocol (SRAP) layer, a radio link control (RLC) layer, a medium access control (MAC) layer, or a physical layer (PHY) .
  • RRC radio resource control
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • SRAP sidelink relay adaptation protocol
  • RLC radio link control
  • MAC medium access control
  • PHY physical layer
  • releasing RLC layer means releasing the PC5 Relay RLC channels.
  • releasing MAC layer means resetting the (sidelink specific) MAC.
  • releasing PDCP layer means releasing DRBs and/or SRBs.
  • releasing RRC layer means releasing SRBs.
  • releasing SDAP layer means releasing DRBs.
  • the first terminal device 210 may cause the first connection associated with the first terminal device 210 and one of the one or more second terminal devices to be released.
  • the first terminal device 210 may determine whether a maintaining indication is included in the indication or received from the first apparatus 220. Moreover, in response to determining the maintaining indication is not included in the indication or received from the first apparatus 220, the first terminal device 210 may cause a part of a second connection associated with the first terminal device 210 and the third terminal device 230 to be released.
  • the part of the second connection may include, but not limited to, a radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a sidelink relay adaptation protocol (SRAP) layer, a radio link control (RLC) layer, a medium access control (MAC) layer, or a physical layer (PHY) .
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • SRAP sidelink relay adaptation protocol
  • RLC radio link control
  • MAC medium access control
  • PHY physical layer
  • the first terminal device 210 may maintain a part of the second connection associated with the first terminal device 210 and the third terminal device 230, the part of the second connection including, but not limited to, a RRC layer or a PDCP layer.
  • the indication may include a target device identification (ID) .
  • ID a target device identification
  • the first terminal device 210 may determine whether the target device ID and a device ID of the third terminal device 230 is matched. Specifically, in response to determining the target device ID and the device ID is not matched, the first terminal device 210 may cause a part of a second connection associated with the first terminal device 210 and the third terminal device 230 to be released.
  • the part of the second connection may include, but not limited to, a radio resource control (RRC) layer, a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a sidelink relay adaptation protocol (SRAP) layer, a radio link control (RLC) layer, a medium access control (MAC) layer, or a physical layer (PHY) .
  • RRC radio resource control
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • SRAP sidelink relay adaptation protocol
  • RLC radio link control
  • MAC medium access control
  • PHY physical layer
  • the first terminal device 210 may maintain a part of the second connection associated with the first terminal device 210 and the third terminal device 230, the part of the second connection including, but not limited to, a RRC layer, a SDAP, a MAC or a PDCP layer.
  • the part of the second connection associated with the first terminal device 210 and the third terminal device 230 is to be maintained.
  • the first terminal device 210 may use the serving cell of the third terminal device 230 as a serving cell of the first terminal device 210.
  • the first terminal device 210 may apply a predetermined configuration of sidelink-radio link control (RLC) (such as SL-RLC1 and/or SL-RLC0) to a connection associated with the first terminal device 210 and/or the third terminal device 230.
  • RLC sidelink-radio link control
  • the first terminal device 210 may cause a configuration of a connection associated with one of the first terminal device 210, the first apparatus 220 and the third terminal device 230 to be released, the configuration including a configuration of a sidelink-user equipment to user equipment (U2U) RLC (such as SL-U2U-RLC) and/or a sidelink-intermediate-RLC.
  • U2U sidelink-user equipment to user equipment
  • RLC such as SL-U2U-RLC
  • the second path may exclude the one or more second terminal devices and the third terminal device 230 but may include a fourth terminal device connected to the network device.
  • the first terminal device 210 may cause a part of a second connection associated with the first terminal device 210 and the third terminal device 230 to be released.
  • the part of the second connection may include, but not limited to, a RRC layer, a PDCP layer, a SRAP layer, a RLC layer, a MAC layer, or a PHY.
  • the first terminal device 210 may cause a third connection associated with the first terminal device 210 and the forth terminal device to be established.
  • the third connection may include, but not limited to, a RRC layer, a PDCP layer, a SRAP layer, a RLC layer, a MAC layer, or a PHY.
  • the second path may exclude one of the one or more second terminal devices and the third terminal device.
  • the first terminal device 210 may cause a part of a second connection associated with the first terminal device 210 and the third terminal device 230 to be released.
  • the part of the second connection may include, but not limited to, a RRC layer, a PDCP layer, a SRAP layer, a RLC layer, a MAC layer, or a PHY.
  • the indication may be included in a message received from one of the one or more second terminal devices.
  • the message may further include, but not limited to, failure information indicating a failure in the first path or location information of the failure.
  • the failure information may indicate a radio link failure (RLF) occurs in the first path. Additionally, the location information may indicate a connection in which the RLF occurs or a terminal device for which the RLF occurs.
  • RLF radio link failure
  • the indication may include failure information indicating a failure in the first path or location information of the failure.
  • the first apparatus 220 may include, for example, the network device, or at least one of the one or more second terminal devices.
  • the first apparatus 220 may be a specific second terminal device of the one or more second terminal devices.
  • the second path to be switched to may start from the first terminal device 210 to the network device, excluding at least one of the one or more second terminal devices.
  • the specific second terminal device may cause a part of a first connection associated with the first terminal device 210 and the at least one of the one or more second terminal devices to be released.
  • the part of the first connection may include, but not limited to, a radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a sidelink relay adaptation protocol (SRAP) layer, a radio link control (RLC) layer, a medium access control (MAC) layer, or a physical layer (PHY) .
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • SRAP sidelink relay adaptation protocol
  • RLC radio link control
  • MAC medium access control
  • PHY physical layer
  • the specific second terminal device may transmit a message including the indication to the first terminal device 210 and/or the third terminal device 230 in a variety of cases.
  • cases include, but not limited to, determining one or more of the following occurs: a radio link failure (RLF) in a connection associated with the first terminal device, a radio resource control (RRC) connection release in a connection associated with the third terminal device, a RLF in a connection associated with the third terminal device, a RLF in an interface associated with the third terminal device and the network device in a connection associated with the third terminal device, a RLF or release in a connection associated with the further second terminal device, or a reconfiguration indication received from the network device.
  • RLF radio link failure
  • RRC radio resource control
  • the message may include, but not limited to, failure information indicating a failure in the first path and/or location information of the failure.
  • the failure information may indicate a radio link failure (RLF) occurs in the first path.
  • the location information may indicate a connection in which the RLF occurs or a terminal device for which the RLF occurs.
  • the first apparatus 220 may include a second terminal device of the one or more second terminal devices connected to the network device. Furthermore, the second terminal device, in response to determining a radio link failure (RLF) in the first path, may cause a radio resource control (RRC) connection to be re-established.
  • RLF radio link failure
  • RRC radio resource control
  • the location information may indicate that the RLF is in a connection associated with the second terminal device and the third terminal device 230.
  • the second terminal device may select a relay device for second terminal device. Additionally, the second terminal device may select a cell as a serving cell for second terminal device and may cause a radio resource control (RRC) connection to be re-established for second terminal device.
  • RRC radio resource control
  • the location information may indicate that the RLF is in a connection associated with the second terminal device and the first terminal device 210.
  • the second terminal device may cause a radio resource control (RRC) connection to be re-established.
  • RRC radio resource control
  • a connection associated with the first terminal device 210 and the third terminal device 230 may be an end-to-end connection. Furthermore, the second terminal device, in response to determining a connection failure occurs associated with the third terminal device 230, may transmit the message to the first terminal device 210. Alternatively, in response to determining a connection failure occurs associated with the first terminal device 210, the second terminal device may transmit the message to the third terminal device 230.
  • the location information may indicate that a radio link failure (RLF) occurs in a connection associated with the second terminal device and a further second terminal device.
  • RLF radio link failure
  • the further second terminal device may be associated with the third terminal device 230 and the second terminal device. In these cases, the second terminal device may transmit the message to, but not limited to, the first terminal device 210 and/or the further second terminal device.
  • the location information may indicate that a radio link failure (RLF) occurs in a connection associated with the second terminal device and a further second terminal device.
  • RLF radio link failure
  • the further second terminal device may be associated with the first terminal device 210 and the second terminal device. In these cases, the second terminal device may transmit the message to, but not limited to, the third terminal device 230 or the further second terminal device.
  • the third terminal device 230 may cause a part of a second connection associated with the first terminal device 210 and the third terminal device 230 to be released.
  • the part of the second connection may include, but not limited to, a radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a sidelink relay adaptation protocol (SRAP) layer, a radio link control (RLC) layer, a medium access control (MAC) layer, or a physical layer (PHY) .
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • SRAP sidelink relay adaptation protocol
  • RLC radio link control
  • MAC medium access control
  • PHY physical layer
  • the message may include failure information indicating a failure in the first path and/or location information of the failure.
  • the failure information may indicate a radio link failure (RLF) occurs in the first path.
  • the location information may indicate a connection in which the RLF occurs and/or a terminal device for which the RLF occurs.
  • the multi-hop path can be switched based on an indication transmitted from the first apparatus in a flexible and efficient way.
  • the flexibility and efficiency of connection management of multi-hop path is improved.
  • FIGS. 3A to 3D illustrate schematic diagrams of examples of path 300A to 300D of multi-hop path in accordance with some embodiments of the present disclosure.
  • the signaling flow 300A to 300D will be discussed with reference to FIGS. 1A to 1C, FIG. 2, and FIG 4A and 4B.
  • the path 300A involves a remote UE (denoted as UE1) 310, a U2U relay (denoted as UE2) 320, a U2N relay (denoted as UE3) 330, and a gNB.
  • the path 300A also involves the 1 st hop between the remote UE 310 and the U2U relay 320, a 2 nd hop between the U2U relay 320 and the U2N relay 330, and a 3 rd hop between the U2N relay 330 and the gNB.
  • the U2U relay (UE2) 320 may be implemented as one or more U2U relay UE connected together including the UE2, UE4 and UE5 in FIG. 1C.
  • the 1 st hop, and the 2 nd hop may be implemented as sidelink (SL) connections, specifically as PC5 unicast link.
  • the 3 rd hop may be implemented as Uu interface.
  • the protocol stacks for sidelink communications of the connection is illustrated in FIG. 4A.
  • the FIG. 4A involves the protocol stacks for connection between UE A and UE B including a (PC5) RRC layer, a (PC5) packet data convergence protocol (PDCP) layer, a (PC5) sidelink relay adaptation protocol (SRAP) layer, a (PC5) radio link control (RLC) layer, a (PC5) medium access control (MAC) layer, and a (PC5) physical layer (PHY) .
  • PC5 RRC layer a packet data convergence protocol (PDCP) layer
  • SRAP sidelink relay adaptation protocol
  • RLC radio link control
  • MAC medium access control
  • PHY physical layer
  • the remote UE 310 may be an implementation of the UE A in the FIG. 4A and the U2U relay 320 may be an implementation of the UE B in the FIG. 4A.
  • the connection of the 1st hop may include at least one of the RRC layer, the PDCP layer, the SRAP layer, the RLC layer, the MAC layer, or the PHY in the FIG. 4A.
  • the U2U relay 320 may include the SRAP layer, the RLC layer, the MAC layer, and the PHY.
  • the remote UE 310 may be an implementation of the first terminal device 210 in FIG. 2.
  • the U2N relay 330 may be an implementation of the third terminal device 230 in FIG. 2.
  • the U2U relay 320 may be an implementation of the first apparatus 220 in FIG. 2.
  • the gNB may be an implementation of the first apparatus 220 in FIG. 2.
  • the path 300A may be an implementation of the first path including one or more second terminal devices and a third terminal device 230 connected to the network device.
  • the remote UE 310 may be an implementation of the first terminal device 210 in FIG. 2
  • the U2N relay 330 may be an implementation of the first terminal device 210 according to some example embodiments of the present disclosure.
  • the remote UE 310 may be an implementation of the third terminal device 230 in FIG. 2.
  • the U2U relay 320 may be an implementation of the first apparatus 220 in FIG. 2.
  • the gNB may be an implementation of the first apparatus 220 in FIG. 2.
  • the present disclosure is not limited in this regard.
  • the remote UE 310 receives, from the gNB, an indication for (multi-hop) path switching.
  • the indication may be a RRC message such as the IE reconfigurationWithSync which may include sl-PathSwitchConfig or may not include sl-PathSwitchConfig.
  • the remote UE 310 may switch form the path 300A to 300B, 300C, or 300D.
  • the remote UE 310 may maintain the path 300A.
  • the remote UE 310 switch from the path 300A to 300C, for example, the connection between the remote UE 310 and the U2U relay 320 may be released.
  • the remote UE 310 removed the U2U relay 320 from the path. Furthermore, if the remote UE 310 switch from the path 300C to the path 300A, the remote UE 310 may cause the connection between the remote UE 310 and the U2U relay 320 to be established. In other word, for switching from the path 300C to the path 300A, the remote UE 310 may add the U2U relay 330 to the path.
  • the indication may be transmitted from the gNB via the connections of the 3 rd hop, the 2 nd hop, and the 1 st hop to the remote UE 310.
  • the remote UE 310 may trigger the PC5 unicast link between the remote UE 310 and the U2U relay 320 to be released via the upper layer including ProSe layer, V2X layer, PC5-Slayer, or NAS (Non-Access Stratum) layer.
  • the remote UE 310 may trigger the PC5 unicast link between the remote UE 310 and at least a part of the U2U relay UEs to be released.
  • the remote UE 310 may indicate to upper layer to trigger PC5 unicast link release with all the U2U relay UEs or at least a part of the U2U relay UEs.
  • the remote UE 310 may trigger the PC5 unicast link between the remote UE 310 and the nearest U2U relay UE (e.g., UE2 in FIG. 1B or FIG 1C) to be released. That is, the remote UE 310 may only be configured with the nearest U2U relay UE when there are more than one U2U relay UEs in the path.
  • the remote UE 310 may be indicated by a further indication including a list of identification (ID) of the U2U relay UEs associated with which the PC5 unicast link is to be released, for example, intermediateRelayUE-Identity (s) . That is, the remote UE 310 may indicate to upper layer to trigger PC5 unicast link release with at least a part of the U2U relay UEs indicated by the further indication. In these cases, the remote UE 310 may switch the multi-hop indirect path to a single hop indirect path by direct-to-indirect or indirect-to-indirect path switch procedure (i.e. sl-PathSwitchConfig) . Furthermore, the multi-hop U2N relay is configured in the source side. Specifically, as illustrated in FIGS. 3A to 3C, the multi-hop U2N relay may be implemented as the U2N relay 330 or the U2N relay 332.
  • ID identification
  • s intermediateRelayUE-Identity
  • the path of the path may include the remote UE 310 connected to the gNB through the U2N relay 330.
  • Table 1 shows an example for the acts performed by the remote UE 310 in different states (additions are underlined , and deleted parts are shown in strike-through, hereinafter the same) .
  • the multi-hop path can be switched to a single hop path in an efficient way.
  • the remote UE 310 may switch from the multi-hop indirect path to single hop indirect path by using reconfigurationWithSync including sl-PathSwitchConfig.
  • the remote UE 310 may use sl-PathSwitchConfig to switch from the multi-hop indirect path to single hop indirect path, in response to receiving reconfigurationWithSync including sl-PathSwitchConfig.
  • connection between the remote UE 310 and the U2N relay 330 may be maintained or re-established according to the indication.
  • the path 300B involves a remote UE (denoted as UE1) 310, a U2N relay (denoted as UE4) 332, and a gNB. Moreover, the path 300B also involves the 1 st hop between the remote UE 310 and the U2N relay 332 and a 2 nd hop between the U2N relay 332 and the gNB. Additionally, the path 300C involves a remote UE (denoted as UE1) 310, a U2N relay (denoted as UE3) 330, and a gNB. Moreover, the path 300C also involves the 1st hop between the remote UE 310 and the U2N relay 330 and a 2nd hop between the U2N relay 330 and the gNB.
  • the 1 st hop, and the 2 nd hop in the FIGS. 3B and 3C may be implemented as sidelink (SL) connections, specifically as PC5 unicast link.
  • SL sidelink
  • the remote UE 310 may be an implementation of the UE A in the FIG. 4A and the U2N relay 332 may be an implementation of the UE B in the FIG. 4A.
  • the connection of the 1st hop may include at least one of the RRC layer, the PDCP layer, the SRAP layer, the RLC layer, the MAC layer, or the PHY in the FIG. 4A.
  • the U2N relay 332 may include the SRAP layer, the RLC layer, the MAC layer, and the PHY.
  • the remote UE 310 may be an implementation of the UE A in the FIG. 4A and the U2N relay 330 may be an implementation of the UE B in the FIG. 4A.
  • the connection of the 1st hop may include at least one of the RRC layer, the PDCP layer, the SRAP layer, the RLC layer, the MAC layer, or the PHY in the FIG. 4A.
  • the U2N relay 330 may include the SRAP layer, the RLC layer, the MAC layer, and the PHY.
  • the remote UE 310 may be an implementation of the first terminal device 210 in FIG. 2.
  • the U2N relay 332 may be an implementation of the third terminal device 230 in FIG. 2.
  • the gNB may be an implementation of the first apparatus 220 in FIG. 2.
  • the path 300B may be an implementation of the second path.
  • the remote UE 310 may switch from the path 300A to the path 300B.
  • the remote UE 310 may be an implementation of the first terminal device 210 in FIG. 2.
  • the U2N relay 330 may be an implementation of the third terminal device 230 in FIG. 2.
  • the gNB may be an implementation of the first apparatus 220 in FIG. 2.
  • the path 300C may be a further implementation of the second path.
  • the remote UE 310 may switch from the path 300A to the path 300C.
  • a maintaining indication for example, sl-U2NRelayMaintain or sl-sourceU2NRelayMaintain, indicating the remote UE 310 whether to maintain the connection associated with the U2N relay 330 or establish a connection with a further U2N relay including the U2N relay 332 in FIG. 3B.
  • the remote UE 310 may determine whether a maintaining indication is included in the indication or received from the gNB.
  • the remote UE 310 may switch the path 300A to the path 300B.
  • the remote UE 310 may switch the path 300A to the path 300C.
  • the procedure of switching the path 300A to the path 300B or 300C is considered to be a multi-hop indirect to single-hop indirect path switching procedure.
  • the remote UE 310 may switch from the first path illustrated in FIG. 3A to a second path by causing the PC5 unicast link between the remote UE 310 and the U2U relay 320 in the FIG. 3A to be released. And the remote UE 310 may cause the PC5 unicast link between the remote UE 310 and the U2N relay 330 in FIG. 3A to be released. For example, the remote UE 310 may indicate to upper layer to trigger PC5 unicast link release with the U2N relay 330.
  • the remote UE 310 may consider the PC5-RRC connection is released for the U2N relay 330 and indicate the release of the PC5-RRC connection to the upper layers for the U2N relay 330 (i.e. PC5 is unavailable) . Furthermore, the remote UE 310 may cause the establishment of a PC5 unicast link with a further U2N device including the U2N relay (UE4) 332 in FIG. 3B via the upper layer.
  • a timer T420 may be started and a default configuration of SL-radio link control (RLC) , such as SL RLC1, may be applied to the remote UE 310.
  • RLC SL-radio link control
  • switching the path from the multi-hop indirect path to the single-hop indirect path is implemented by the implementations of direct-to-indirect and/or indirect-to-indirect path switching procedure (i.e., sl-PathSwitchConfig and sl-U2NRelayMaintain) .
  • the multi-hop U2N relay may be configured in the source side. Specifically, as illustrated in FIGS. 3A to 3C, the multi-hop U2N relay may be implemented as the U2N relay 330 or the U2N relay 332.
  • the U2N relay in the path can be changed in an efficient way.
  • the flexibility of the connection management of the multi-hop path is improved.
  • the remote UE 310 may switch from the first path illustrated in FIG. 3A to a second path by causing the PC5 unicast link between the remote UE 310 and the U2U relay 320 in the FIG. 3A to be released. And, the remote UE 310 may cause the (end-to-end) PC5 unicast link between the remote UE 310 and the U2N relay 330 in FIG. 3A to be released. For example, the remote UE 310 may indicate to upper layer to trigger PC5 unicast link release with the U2N relay 330.
  • the remote UE 310 may consider the PC5-RRC connection is released for the U2N relay 330 and indicate the release of the PC5-RRC connection to the upper layers for the U2N relay 330 (i.e. PC5 is unavailable) . Furthermore, the remote UE 310 may cause the (end-to-end) PC5 unicast link between the remote UE 310 and the U2N relay 330 in FIG. 3A to be established, for example, via the upper layer.
  • the remote UE 310 may cause the connection associated with the U2N relay 330 and the remote UE 310 to be released. Specifically, no matter whether the U2N relay 330 is maintained, the remote UE 310 may indicate to upper layer to trigger PC5 unicast link release with the U2N relay 330. For example, the remote UE 310 may indicate to upper layer to trigger PC5 unicast link release with the U2N relay 330. Then, the remote UE 310 may cause the connection between the remote UE 310 and a U2N relay (for example, the U2N relay 330, the U2N relay 332, or other U2N relay) to be established based on the indication.
  • a U2N relay for example, the U2N relay 330, the U2N relay 332, or other U2N relay
  • the remote UE 310 may switch from the first path illustrated in FIG. 3A to a second path by causing the PC5 unicast link between the remote UE 310 and the U2U relay 320 in the FIG. 3A to be released. Then, the remote UE 310 may cause the (end-to-end) PC5 unicast link between the remote UE 310 and the U2N relay 330 in FIG. 3A to be maintained via the upper layer. For example, the remote UE 310 may indicate to upper layer to trigger PC5 unicast link with the U2N relay 330.
  • the upper layer may cause the PC5 unicast link between the remote UE 310 and the U2N relay 330 to be maintained by the U2N relay 330, such as via an upper layer (e.g., PC5-singnaling layer ) message/signaling.
  • the PC5 unicast link between the remote UE 310 and the U2N relay 330 may include, but not limited to, the RRC layer, SDAP layer, and/or the PDCP layer.
  • the RLC layer or a part of the configuration of RLC layer may be released.
  • the PC5 Relay RLC channel for the PC5 unicast link or of U2U relay 320 may be released.
  • the SRAP layer or a part of the configuration of SRAP layer may be released.
  • the local ID of the U2N relay 330 and/or the mapping information associated with the U2N relay 330 may be released.
  • the process of causing the PC5 unicast link between the remote UE 310 and the U2N relay 330 to be released and the process of causing the PC5 unicast link between the remote UE 310 and the U2U relay 320 in the to be maintained are not limited to any particular order.
  • the U2N relay 330 may receive an indication for multi-hop path switching. Then, in response to receiving the indication, the U2N relay 330 may cause the PC5 unicast link between the remote UE 310 and the U2N relay 330 in the FIG. 3A to be released, such as via the upper layer or considering the PC5-RRC connection is released (locally) and indicating the release of PC5-RRC connection to the upper layer. Alternatively, or in addition, the U2N relay may cause the PC5 unicast link between the U2U relay 320 and the U2N relay 330 in the FIG.
  • the indication may be transmitted from the U2U relay 320 or the gNB to the U2N relay. Alternatively, or in addition, the indication may be transmitted from the remote UE 310 to the U2N relay.
  • the U2N relay may receive a maintaining indication included in the indication or transmitted from the gNB, the U2U relay 320, or the remote UE 310.
  • the U2N relay 330 may cause at least a part of the PC5 unicast link between the remote UE 310 and the U2N relay 330 to be maintained.
  • the at least a part of the PC5 unicast link between the remote UE 310 and the U2N relay 330 may include.
  • the PC5 unicast link between the remote UE 310 and the U2N relay 330 may include, but not limited to, the RRC layer, SDAP layer, and/or the PDCP layer.
  • the U2N relay 330 may include the SRAP layer, the RLC layer, the MAC layer, and the PHY.
  • FIG. 4B involves the protocol stacks for connection between UE A and UE B including at least one of a RRC layer, a packet data convergence protocol (PDCP) layer, a sidelink relay adaptation protocol (SRAP) layer, a radio link control (RLC) layer, a medium access control (MAC) layer, or a physical layer (PHY) .
  • a RRC layer a packet data convergence protocol (PDCP) layer
  • SRAP sidelink relay adaptation protocol
  • RLC radio link control
  • MAC medium access control
  • PHY physical layer
  • a timer T420 may not be started, a default configuration of SL-U2U-RLC or SL-intermediate-RLC may be released, and a default configuration of SL-radio link control (RLC) 1 may be applied to the remote UE 310.
  • RLC SL-radio link control
  • the maintaining indication may be included in a RRC message received from the gNB, for example, in information element (IE) reconfigurationWithSync or in IE sl-PathSwitchConfig contained in reconfigurationWithSync.
  • the maintaining indication may be included in other signaling or information element (IE) .
  • the maintaining indication may be included in the indication or received from the gNB no matter whether to maintain the connection. Furthermore, the maintaining indication may be set as 0 or false to indicate not to maintain the connection. Moreover, the maintaining indication may be set as 1 or true to indicate to maintain the connection. Table 2 shows an example for the acts performed by the remote UE 310 in different states.
  • MP multi-path
  • the MP direct path is caused to be released by a direct-to-indirect path switch procedure (i.e. sl-PathSwitchConfig, and sl-indirectPathMaintain included in RRCReconfiguration message and sl-U2NRelayMaintain included in RRCReconfiguration message) , where MP is configured in source side.
  • a direct-to-indirect path switch procedure i.e. sl-PathSwitchConfig, and sl-indirectPathMaintain included in RRCReconfiguration message and sl-U2NRelayMaintain included in RRCReconfiguration message
  • the indication may include a target device ID, for example, the targetRelayUE-Identity.
  • the remote UE 310 may determine whether the target device ID and a device ID of the U2N relay is matched. If the remote UE 310 determines that the target device ID and the device ID is not matched, the remote UE 310 may switch the path 300A to the path 300B. Alternatively, if the remote UE 310 determines that the target device ID and the device ID is matched, the remote UE 310 may switch the path 300A to the path 300C.
  • the remote UE 310 may use the serving cell of the U2N relay 330 as a serving cell of the remote UE 310. Moreover, the remote UE 310 may apply a predetermined configuration of SL-RLC1 to a connection associated with the remote UE 310 and/or the U2N relay 330. Additionally, the remote UE 310 may cause a configuration of a connection associated with the remote UE 310, the U2U relay 320 and the U2N relay 330 to be released.
  • the configuration may include a configuration of a sidelink-user equipment to user equipment (U2U) RLC and/or a sidelink-intermediate-RLC, wherein the sidelink-intermediate-RLC is a predefined PC5 relay RLC channel for (multi-hop) remote UE310's SL-SRB0/1/2/3 message transmission/reception with the U2N relay 330, via one or more U2U relays.
  • U2U user equipment
  • Table 3 and 4 shows an example for the acts performed by the remote UE 310 in different states.
  • the gNB indicate the remote UE 310 to switch the path to a second path including only the remote UE 310 and the gNB.
  • the path 300D involves a remote UE (denoted as UE1) 310, a gNB and a 1 st hop between them.
  • UE1 remote UE
  • gNB gNode B
  • the remote UE 310 is indicated by the gNB to switch the path 300A to the path 300D.
  • the remote UE 310 may cause the PC5 unicast link between the remote UE 310 and the U2U relay 320 in the FIG. 3A to be released and cause the PC5 unicast link between the remote UE 310 and the U2N relay 330 in the FIG. 3A to be released.
  • the U2U relay 320 may include the SRAP layer, the RLC layer, the MAC layer, and the PHY.
  • the remote UE 310 may be indicated by a further indication including a list of identification (ID) of the U2U relay UEs associated with which the PC5 unicast link is to be released, for example, intermediateRelayUE-Identity (s) .
  • ID identification
  • the remote UE 310 may trigger the PC5 unicast link between the remote UE 310 and the nearest U2U relay UE (e.g., UE2 in FIG. 1A) to be released.
  • the reconfigurationWithSync may not include sl-PathSwitchConfig.
  • the remote UE 310 may cause the PC5 unicast link between the remote UE 310 and the U2N relay 330 in FIG. 3A to be released.
  • the remote UE 310 may indicate to upper layer to trigger PC5 unicast link release with the U2N relay 330.
  • the remote UE 310 may consider the PC5-RRC connection is released for the U2N relay 330 and indicate the release of the PC5-RRC connection to the upper layers for the U2N relay 330 (i.e. PC5 is unavailable) .
  • the process of causing the PC5 unicast link between the remote UE 310 and the U2N relay 330 to be released and the process of causing the PC5 unicast link between the remote UE 310 and the U2U relay 320 in the to be released are not limited to any particular order.
  • the remote UE 310 may cause the establishment of connection between the remote UE 310 and the gNB in FIG. 3D.
  • the reconfigurationWithSync may be included in RRCReconfiguration message.
  • Table 5 shows an example for the acts performed by the remote UE 310 in different states.
  • reconfigurationWithSync may be used to realize switching from multi-hop indirect path to direct path.
  • the path switching is indicated by the reconfigurationWithSync which includes no sl-PathSwitchConfig.
  • switching the multi-hop indirect path to direct path is implemented by indirect-to-direct path switch procedure (i.e. ReconfigurationWithSync included in RRCReconfiguration message) .
  • the multi-hop U2N relay is configured in the source side. Specifically, as illustrated in FIGS. 3A to 3C, the multi-hop U2N relay may be implemented as the U2N relay 330 or the U2N relay 332.
  • connection between the remote UE 310 and the U2U relay and the U2N relay can be released.
  • the multi-hop indirect path can be switched to direct path.
  • the usability of the connection management of multi-hop is improved.
  • the U2U relay UE may inform the remote UE, the U2N relay UE and the gNB. Furthermore, the remote UE may be indicated to switch the path in response to be informed of connection failure.
  • FIG. 5 illustrates schematic diagram of example of multi-hop path 500 in accordance with some embodiments of the present disclosure.
  • the path 500 includes a remote UE (denoted as UE1) 510, a U2U relay (denoted as UE2) 522, a U2U relay (denoted as UE4) 520, a U2U relay (denoted as UE5) 524, a U2N relay (denoted as UE3) 530, and a gNB.
  • the path 500 also includes a 1 st hop between the remote UE 510 and the UE2 522, a 2 nd hop between the UE2 522 and the UE4 520, a 3 rd hop between the UE4 520 and the UE5 524, a 4 th hop between the UE5 524 and the UE3 530, and a 5 th hop between the UE3 530 and the gNB.
  • the protocol stacks for sidelink communications of the connection is illustrated in FIG. 4A.
  • the remote UE 510 may be an implementation of the UE A in the FIG. 4A and the UE2 522 may be an implementation of the UE B in the FIG. 4A.
  • the connection of the 1 st hop may include at least one of the RRC layer, the PDCP layer, the SRAP layer, the RLC layer, the MAC layer, or the PHY in the FIG. 4A.
  • the UE2 522 may include the SRAP layer, the RLC layer, the MAC layer and the PHY.
  • the UE4 520, UE5 524 and UE3 530 may include the SRAP layer, the RLC layer, the MAC layer and the PHY.
  • the remote UE 510 may be an implementation of the first terminal device 210 in FIG. 2.
  • the U2N relay 530 may be an implementation of the third terminal device 230 in FIG. 2.
  • the U2U relays 520, 522, and 524 may be an implementation of the first apparatus 220 in FIG. 2.
  • the U2U relay UE including one of the UE2 522, UE4 520, and UE5 524 transmits, to the remote UE 510, an indication for multi-hop path switching, to cause the remote UE 510 to switch from a first path to a second path based on the indication.
  • the indication may include a failure information indicates a radio link failure (RLF) occurs and/or a location information of the failure.
  • the indication may be included in a message including the failure information and/or the location information.
  • the U2U relay UE including one of the UE2 522, UE4 520, and UE5 524 may transmit the message including the indication to the remote UE 510 and the U2N relay 530, in response to determining an event occurs in the first path.
  • the event may include, but not limited to, a radio link failure (RLF) in a connection associated with the first terminal device, a radio resource control (RRC) connection release in a connection associated with the third terminal device, a RLF in a connection associated with the third terminal device, a RLF in an interface associated with the third terminal device and the network device in a connection associated with the third terminal device; a RLF or release in a connection associated with the further second terminal device, or a reconfiguration indication (for example, IE reconfigurationWithSync with or without sl-PathSwitchConfig) received from the network device.
  • RLF radio link failure
  • RRC radio resource control
  • the location information may indicate that the RLF is in a connection associated with the UE5 524 and the U2N relay 530.
  • the UE5 524 may select a relay device for the UE5 524.
  • the UE5 524 may select a cell as a serving cell for the UE5 524.
  • the UE5 524 may cause a RRC connection to be re-established for the UE5 524.
  • Table 6 shows an example for the acts performed by the U2U relay UE in different states.
  • the PC5 unicast link between the remote UE 510 and the U2N relay 530 may be an end-to-end connection.
  • the U2U relay UE including one of the UE2 522, UE4 520, and UE5 524 may, in response to determining a connection failure occurs associated with the U2N relay 530, transmit the message to the remote UE 510.
  • the U2U relay UE may, in response to determining a connection failure occurs associated with the remote UE 510, transmit the message to the U2N relay 530.
  • the message may include the indication to switch the multi-hop path.
  • the remote UE 510 may switch the path to release a part of the connection associated with the remote UE 510 and the U2N relay 530 for which the RLF occurs.
  • the U2N relay 530 may cause the PC5 unicast link between the remote UE 510 and the U2N relay 530 to be released.
  • Table 7 shows an example for the acts performed by the U2U relay UE in different states.
  • the intermediate Relay UE (noted as the UE2, UE4, and UE5 in FIG. 5) may be configured to perform the acts in Table 6 (i.e., U2N-like procedure) or the acts in Table 7 (i.e., U2N-like procedure) or both acts, when detects sidelink RLF.
  • Table 6 i.e., U2N-like procedure
  • Table 7 i.e., U2N-like procedure
  • the U2U relay UE may determine that the event mentioned above occurs and transmit the message (for example, NotificationMessageSidelink message ) to the remote UE 510.
  • the U2N relay 530 may be implemented as a L2 U2N relay UE. Specifically, the U2U relay UE may determine that PC5 RLF occurs in the connection associated with the U2N relay 530. Alternatively or in addition, the U2U relay UE may determine that PC5-RRC connection release occurs in the connection associated with the (per-hop) PC5 unicast link between the U2U relay UE and the U2N relay 530. Furthermore, the U2U relay UE may set the sl-IndicationType as relayUE-PC5-RLF.
  • the U2U relay UE may set sl-IndicationType as relay-PC5-release in response to the PC5-RRC connection release. Moreover, the U2U relay UE may set the sl-DestinationIdentityRemoteUE as the associated destination for/of the U2N relay 530.
  • the destination means, for example, a device for which the PC5 RLF or the PC5-RRC connection release occurs.
  • the U2U relay UE may submit the NotificationMessageSidelink message to lower layers for transmission (i.e., to the U2N remote UE510) .
  • the lower layers may include L2 sublayers, such as, PDCP layer, MAC layer, RLC layer, or physical layer.
  • the U2U relay UE may transmit the message to the U2N remote 510 via the lower layers. That is, the U2U relay UE may transmit the message to the U2N remote UE 510 via the PC5 unicast link between the U2U relay UE 530 and the U2N remote UE 510.
  • the U2U relay UE may transmit the NotificationMessageSidelink message in response to receiving a failure information of Uu RLF for the connection between the U2N relay 530 and the gNB. Furthermore, the U2U relay UE may set the sl-IndicationType as Uu-RLF. Additionally, the U2U relay UE may set the sl-DestinationIdentityRemoteUE as the associated destination for the U2N relay 530. The destination means, for example, a device for which the RLF or the Uu RLF occurs. Moreover, the U2U relay UE may submit the NotificationMessageSidelink message to lower layers for transmission (i.e., to the remote UE 510) . Additionally, the U2U relay UE may transmit the message to the remote UE 510 and/or another L2 intermediate relay UE via lower layers.
  • the U2U relay UE may transmit the NotificationMessageSidelink message in response to receiving a reconfiguration with sync (for example, including sl-PathSwitchConfig) from gNB.
  • the remote UE 510 may be implemented as a L2 U2N remote UE.
  • the U2U relay UE may set the sl-IndicationType as path switching (e.g., relayUE-PS) .
  • the U2U relay UE may set the sl-IndicationType as handover (e.g., relayUE-HO) .
  • U2U relay UE may set the sl-DestinationIdentityRemoteUE as the associated destination for the U2N relay 530.
  • the destination means for example, a device for which the reconfiguration with sync is received.
  • the U2U relay UE may submit the NotificationMessageSidelink message to lower layers for transmission (i.e., to the Remote UE 510) .
  • the U2U relay UE may transmit the message to the remote UE 510 and/or another L2 intermediate Relay UE via lower layers.
  • the U2U relay UE may transmit the NotificationMessageSidelink message in response to the PC5 RLF or the release of PC5 unicast link with a further U2U relay UE, for example, for the connection between the UE4 520 and the UE5 524, that is the 3 rd hop.
  • the PC5 RLF detection process is described by using the UE4 520 as an example of a device that detects the failure or the release.
  • the UE4 520 may further transmit the NotificationMessageSidelink message in response to receiving a failure information for the connection between a U2U relay UE and another U2U relay UE, such as, the UE5 524 and the UE2 522.
  • the UE4 520 may set the sl-IndicationType as relayUE-PC5-RLF. Moreover, the UE4 520 may set the sl-DestinationIdentityRemoteUE as the associated destination for/of another L2 intermediate relay or the further L2 intermediate relay UE. In addition, the UE4 520 may submit the NotificationMessageSidelink message to lower layers for transmission.
  • the UE4 520 may receive a message from the UE5 524 indicating a failure or release of the connection between the UE5 524 and the UE3 530. In these cases, the UE4 520 may transmit the message to the UE1 510. Alternatively, or in addition, the UE4 520 may transmit the message to the UE2 522.
  • the UE4 520 may transmit the message to the UE1 510. Alternatively, or in addition, the UE4 520 may transmit the message to the UE2 522.
  • the UE4 520 may receive a message from the UE2 522 indicating a failure or release of the connection between the UE2 522 and the UE1 510. In these cases, the UE4 520 may transmit the message to the UE3 530. Alternatively, or in addition, the UE4 520 may transmit the message to the UE5 524.
  • the UE4 520 may transmit the message to the UE3 530. Alternatively, or in addition, the UE4 520 may transmit the message to the UE5 524.
  • the remote UE 510 may switch the multi-hop path in response to the message .
  • the target path (noted as the second path shown in FIG. 3B ⁇ 3D)
  • the U2U relay of the target path the U2N relay of the target path
  • the gNB or a cell of the gNB may be preconfigured.
  • the remote UE 510 may cause to release the PC5 unicast link with the U2U relay UE, to release the PC5 unicast link with the U2N relay 530 and/or to maintain a part of the PC5 unicast link with U2N relay 530.
  • the U2U relay 520 may include the SRAP layer, the RLC layer, the MAC layer, and the PHY. Additionally, the remote UE 510 may be implemented as a L2 U2N multi-hop remote UE in RRC_IDLE or RRC_INACTIVE. In addition, the indicationType may be PC5_RLF and the remote UE 510 may be determined to cause the PC5 unicast link between the remote UE 510 and the U2U relay UE to be released.
  • the indicationType may be Uu_RLF and the remote UE 510 may be determined to cause the PC5 unicast link with the U2N relay 530 to be released.
  • the remote UE 510 may indicate to upper layer to trigger PC5 unicast link release with the U2N relay 530.
  • the remote UE 510 may consider the PC5-RRC connection is released for the U2N relay 530 and indicate the release of the PC5-RRC connection to the upper layers for the U2N relay 530 (i.e. PC5 is unavailable) .
  • the remote UE 510 may not switch the multi-hop path in response to the message. In these cases, the remote UE 510 may maintain the PC5 unicast link with the U2N relay 530 and/or the U2U relay UEs. Additionally, the remote UE 510 may be implemented as a L2 U2N multi-hop remote UE in RRC_IDLE or RRC_INACTIVE.
  • the remote UE 510 may be implemented as a L2 U2N remote UE and the indicationType is relayUE-PS, the remote UE 510 may re-select at least a part of cells being used for the remote UE 510 or the remote UE 510 may use the serving cell of U2U relay UE (s) as the serving cell or selected cell. That is, if indicationType is relayUE-PS, the remote UE 510 may consider cell re-selection occurs (for the remote UE 510) . Alternatively, the remote UE 510 may perform the RRC connection re-establishment. Additionally, if the remote UE 510 may be implemented as a L2 U2N multi-hop remote UE in RRC_CONNECTED. Furthermore, there is a T301 timer which is not running.
  • the U2U relay UE can inform the remote UE 510 for the failure for U2N relay 530, and inform the U2N relay 530 for the failure for the remote UE 510.
  • the remote UE 510 can switch the multi-hop path when the failure occurs.
  • the reliability and flexibility of the connection management of the multi-hop path is improved.
  • FIG. 6 illustrates a flowchart of a communication method 600 implemented at a first terminal device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 600 will be described from the perspective of the first terminal device 210 in FIG. 2.
  • the first terminal device 210 receives, from a first apparatus, an indication for multi-hop path switching.
  • the first terminal device 210 switches from a first path to a second path based on the indication, both the first path and the second path starting from the first terminal device to a network device, the first path comprising one or more second terminal devices and a third terminal device connected to the network device, the second path excluding at least one of the one or more second terminal devices and/or the third terminal device.
  • the indication for multi-hop path switching may be received from at least one of the network device or one of the one or more second terminal devices.
  • the second path excludes at least one of the one or more second terminal devices
  • the first terminal device 210 may cause at least a part of a first connection associated with the first terminal device 210 and the at least one of the one or more second terminal devices to be released, the at least part of the first connection comprising at least one of the following: a radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a sidelink relay adaptation protocol (SRAP) layer, a radio link control (RLC) layer, a medium access control (MAC) layer, or a physical layer (PHY) .
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • SRAP sidelink relay adaptation protocol
  • RLC radio link control
  • MAC medium access control
  • PHY physical layer
  • the first terminal device 210 may determine whether a maintaining indication is comprised in the indication or received from the first apparatus; and in response to determining the maintaining indication is not comprised in the indication or received from the first apparatus, cause at least a part of a second connection associated with the first terminal device 210 and the third terminal device to be released, the at least part of the second connection comprising at least one of the following: a radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a sidelink relay adaptation protocol (SRAP) layer, a radio link control (RLC) layer, a medium access control (MAC) layer, or a physical layer (PHY) ; or in response to determining the maintaining indication is comprised in the indication or received from the first apparatus, maintain at least a part of the second connection associated with the first terminal device 210 and the third terminal device, the at least part of the second connection comprising at least one of a RRC layer or a PDCP layer.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • the indication may comprise a target device identification (ID)
  • the first terminal device 210 may determine whether the target device ID and a device ID of the third terminal device is matched; and in response to determining the target device ID and the device ID is not matched, cause at least a part of a second connection associated with the first terminal device 210 and the third terminal device to be released, the at least part of the second connection comprising at least one of the following: a radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a sidelink relay adaptation protocol (SRAP) layer, a radio link control (RLC) layer, a medium access control (MAC) layer, or a physical layer (PHY) ; or in response to determining the target device ID and the device ID is matched, maintain at least a part of the second connection associated with the first terminal device 210 and the third terminal device, the at least part of the second connection comprising at least one of a RRC layer or a PDCP layer.
  • RRC radio resource control
  • PDCP
  • the first terminal device 210 may perform at least one of the following: using the serving cell of the third terminal device as a serving cell of the first terminal device; applying a predetermined configuration of . sidelink-radio link control (RLC) to a connection associated with at least one of the first terminal device 210 and the third terminal device; or causing a configuration of a connection associated with at least one of the first terminal device, the first apparatus and the third terminal device to be released, the configuration comprising a configuration of at least one of a sidelink-user equipment to user equipment (U2U) RLC or a sidelink-intermediate-RLC.
  • RLC sidelink-radio link control
  • the second path may exclude the one or more second terminal devices and the third terminal device but comprises a fourth terminal device connected to the network device
  • the first terminal device 210 may cause at least a part of a second connection associated with the first terminal device 210and the third terminal device to be released, the at least part of the second connection comprising at least one of the following: a RRC layer, a PDCP layer, a SRAP layer, a RLC layer, a MAC layer, or a PHY
  • a third connection associated with the first terminal device 210and the forth terminal device to be established, the third connection comprising at least one of the following: a RRC layer, a PDCP layer, a SRAP layer, a RLC layer, a MAC layer, or a PHY .
  • the second path may exclude at least one of the one or more second terminal devices and the third terminal device, and the first terminal device 210 may cause at least a part of a second connection associated with the first terminal device 210 and the third terminal device to be released, the at least part of the second connection comprising at least one of the following: a RRC layer, a PDCP layer, a SRAP layer, a RLC layer, a MAC layer, or a PHY.
  • the indication may be comprised in a message received from one of the one or more second terminal devices, and the message may further comprise at least one of failure information indicating a failure in the first path or location information of the failure.
  • the failure information may indicate a radio link failure (RLF) occurs in the first path, and/or the location information may indicate a connection in which the RLF occurs or a terminal device for which the RLF occurs.
  • RLF radio link failure
  • the indication may comprise at least one of failure information indicating a failure in the first path or location information of the failure.
  • FIG. 7 illustrates a flowchart of a communication method 700 implemented at a first apparatus in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 700 will be described from the perspective of the first apparatus 220 in FIG. 2.
  • the first apparatus 220 transmit, to the first terminal device, an indication for multi-hop path switching, to cause the first terminal device to switch from a first path to a second path based on the indication, both the first path and the second path starting from the first terminal device to a network device, the first path comprising one or more second terminal devices and a third terminal device connected to the network device, the second path excluding at least one of the one or more second terminal devices or the third terminal device.
  • the first apparatus 220 may comprise the network device or at least one of the one or more second terminal devices.
  • the first apparatus 220 may comprise a second terminal device of the one or more second terminal devices, the second path may exclude at least one of the one or more second terminal devices, and the second terminal device is caused to: cause at least a part of a first connection associated with the first terminal device and the at least one of the one or more second terminal devices to be released, the at least part of the first connection comprising at least one of the following: a radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a sidelink relay adaptation protocol (SRAP) layer, a radio link control (RLC) layer, a medium access control (MAC) layer, or a physical layer (PHY) .
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • SRAP sidelink relay adaptation protocol
  • RLC radio link control
  • MAC medium access control
  • PHY physical layer
  • the first apparatus 220 may comprise a second terminal device of the one or more second terminal devices, and the second terminal device is caused to: in response to determining at least one of the following events occurs: a radio link failure (RLF) in a connection associated with the first terminal device, a radio resource control (RRC) connection release in a connection associated with the third terminal device.
  • RLF radio link failure
  • RRC radio resource control
  • a RLF in a connection associated with the third terminal device a RLF in an interface associated with the third terminal device and the network device in a connection associated with the third terminal device; a RLF or release in a connection associated with the further second terminal device, or a reconfiguration indication received from the network device; and transmit a message comprising the indication to at least one of the first terminal device or the third terminal device.
  • the message may comprise at least one of failure information indicating a failure in the first path or location information of the failure.
  • the failure information may indicate a radio link failure (RLF) occurs in the first path
  • the location information may indicate a connection in which the RLF occurs or a terminal device for which the RLF occurs.
  • RLF radio link failure
  • the first apparatus may comprise a second terminal device of the one or more second terminal devices connected to the network device, and the second terminal device may, in response to determining a radio link failure (RLF) in the first path, cause a radio resource control (RRC) connection to be re-established.
  • RLF radio link failure
  • RRC radio resource control
  • the location information may indicates that the RLF is in a connection associated with the second terminal device and the third terminal device, and the second terminal device is further caused to perform at least one of the following: selecting a relay device for second terminal device; selecting a cell as a serving cell for second terminal device; or cause a radio resource control (RRC) connection to be re-established for second terminal device.
  • RRC radio resource control
  • the location information may indicate that the RLF is in a connection associated with the second terminal device and the first terminal device, and the second terminal device is further caused to: cause a radio resource control (RRC) connection to be re-established.
  • RRC radio resource control
  • a connection associated with the first terminal device and the third terminal device may be an end-to-end connection
  • the second terminal device may, in response to determining a connection failure occurs associated with the third terminal device, transmit the message to the first terminal device; or in response to determining a connection failure occurs associated with the first terminal device, transmit the message to the third terminal device.
  • the location information may indicate that a radio link failure (RLF) occurs in a connection associated with the second terminal device and a further second terminal device, the further second terminal device being associated with the third terminal device and the second terminal device, and the second terminal device may transmit the message to at least one of the first terminal device or the further second terminal device.
  • RLF radio link failure
  • the location information may indicate that a radio link failure (RLF) occurs in a connection associated with the second terminal device and a further second terminal device, the further second terminal device being associated with the first terminal device and the second terminal device, and the second terminal device may transmit the message to at least one of the third terminal device or the further second terminal device.
  • RLF radio link failure
  • FIG. 8 illustrates a flowchart of a communication method 800 implemented at a third terminal device in accordance with some embodiments of the present disclosure.
  • the method 800 will be described from the perspective of the third terminal device 230 in FIG. 2.
  • the third terminal device 230 from the one or more second terminal devices, a message comprising an indication for releasing a connection associated with the first terminal device and the third terminal device connected to a network device, wherein the first terminal device is to switch from a first path to a second path, both the first path and the second path starting from the first terminal device to the network device, the first path comprising one or more second terminal devices and the third terminal device connected to the network device, the second path excluding at least one of the one or more second terminal devices and/or the third terminal device.
  • the third terminal device 230 may cause at least a part of a second connection associated with the first terminal device and the third terminal device to be released, the at least part of the second connection comprising at least one of the following: a radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a sidelink relay adaptation protocol (SRAP) layer, a radio link control (RLC) layer, a medium access control (MAC) layer, or a physical layer (PHY) .
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • SRAP sidelink relay adaptation protocol
  • RLC radio link control
  • MAC medium access control
  • PHY physical layer
  • the message may comprise at least one of failure information indicating a failure in the first path or location information of the failure.
  • the failure information may indicate a radio link failure (RLF) occurs in the first path
  • the location information may indicate a connection in which the RLF occurs or a terminal device for which the RLF occurs.
  • RLF radio link failure
  • FIG. 9 is a simplified block diagram of a device 900 that is suitable for implementing embodiments of the present disclosure.
  • the device 900 can be considered as a further example implementation of any of the devices as shown in FIG. 1 A to 1C, 2, and 3A to 3D. Accordingly, the device 900 can be implemented at or as at least a part of the first terminal device 210, the first apparatus 220 and the third.
  • the device 900 includes a processor 910, a memory 920 coupled to the processor 910, a suitable transceiver 940 coupled to the processor 910, and a communication interface coupled to the transceiver 940.
  • the memory 920 stores at least a part of a program 930.
  • the transceiver 940 may be for bidirectional communications or a unidirectional communication based on requirements.
  • the transceiver 940 may include at least one of a transmitter 942 and a receiver 944.
  • the transmitter 942 and the receiver 944 may be functional modules or physical entities.
  • the transceiver 940 has at least one antenna to facilitate communication, though in practice an Access Node mentioned in this application may have several ones.
  • the communication interface may represent any interface that is necessary for communication with other network elements, such as X2/Xn interface for bidirectional communications between eNBs/gNBs, S1/NG interface for communication between a Mobility Management Entity (MME) /Access and Mobility Management Function (AMF) /SGW/UPF and the eNB/gNB, Un interface for communication between the eNB/gNB and a relay node (RN) , or Uu interface for communication between the eNB/gNB and a terminal device.
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • RN relay node
  • Uu interface for communication between the eNB/gNB and a terminal device.
  • the program 930 is assumed to include program instructions that, when executed by the associated processor 910, enable the device 900 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to FIGS. 1 to 8.
  • the embodiments herein may be implemented by computer software executable by the processor 910 of the device 900, or by hardware, or by a combination of software and hardware.
  • the processor 910 may be configured to implement various embodiments of the present disclosure.
  • a combination of the processor 910 and memory 920 may form processing means 950 adapted to implement various embodiments of the present disclosure.
  • the memory 920 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory 920 is shown in the device 900, there may be several physically distinct memory modules in the device 900.
  • the processor 910 may be of any type suitable to the local technical network, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • the device 900 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
  • a first terminal device comprising a circuitry.
  • the circuitry is configured to: receive, from a first apparatus, an indication for multi-hop path switching; and switch from a first path to a second path based on the indication, both the first path and the second path starting from the first terminal device to a network device, the first path comprising one or more second terminal devices and a third terminal device connected to the network device, the second path excluding at least one of the one or more second terminal devices and/or the third terminal device.
  • the circuitry may be configured to perform any method implemented by the first terminal device as discussed above.
  • a first apparatus comprising a circuitry.
  • the circuitry is configured to: transmit, to the first terminal device, an indication for multi-hop path switching, to cause the first terminal device to switch from a first path to a second path based on the indication, both the first path and the second path starting from the first terminal device to a network device, the first path comprising one or more second terminal devices and a third terminal device connected to the network device, the second path excluding at least one of the one or more second terminal devices or the third terminal device.
  • the circuitry may be configured to perform any method implemented by the first apparatus as discussed above.
  • a third terminal device comprising a circuitry.
  • the circuitry is configured to: receive, from the one or more second terminal devices, a message comprising an indication for releasing a connection associated with the first terminal device and the third terminal device connected to a network device, wherein the first terminal device is to switch from a first path to a second path, both the first path and the second path starting from the first terminal device to the network device, the first path comprising one or more second terminal devices and the third terminal device connected to the network device, the second path excluding at least one of the one or more second terminal devices and/or the third terminal device.
  • the circuitry may be configured to perform any method implemented by the third terminal device as discussed above.
  • circuitry used herein may refer to hardware circuits and/or combinations of hardware circuits and software.
  • the circuitry may be a combination of analog and/or digital hardware circuits with software/firmware.
  • the circuitry may be any portions of hardware processors with software including digital signal processor (s) , software, and memory (ies) that work together to cause an apparatus, such as a terminal device or a network device, to perform various functions.
  • the circuitry may be hardware circuits and or processors, such as a microprocessor or a portion of a microprocessor, that requires software/firmware for operation, but the software may not be present when it is not needed for operation.
  • the term circuitry also covers an implementation of merely a hardware circuit or processor (s) or a portion of a hardware circuit or processor (s) and its (or their) accompanying software and/or firmware.
  • a first terminal device comprises means for receiving, from a first apparatus, an indication for multi-hop path switching; and means for switching from a first path to a second path based on the indication, both the first path and the second path starting from the first terminal device to a network device, the first path comprising one or more second terminal devices and a third terminal device connected to the network device, the second path excluding at least one of the one or more second terminal devices and/or the third terminal device.
  • the first terminal device may comprise means for performing the respective operations of the method 600.
  • the first terminal device may further comprise means for performing other operations in some example embodiments of the method 600.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • a first apparatus comprises means for transmitting, to the first terminal device, an indication for multi-hop path switching, to cause the first terminal device to switch from a first path to a second path based on the indication, both the first path and the second path starting from the first terminal device to a network device, the first path comprising one or more second terminal devices and a third terminal device connected to the network device, the second path excluding at least one of the one or more second terminal devices or the third terminal device.
  • the first apparatus may comprise means for performing the respective operations of the method 700.
  • the first apparatus may further comprise means for performing other operations in some example embodiments of the method 700.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • a third terminal device comprises means for receiving, from the one or more second terminal devices, a message comprising an indication for releasing a connection associated with the first terminal device and the third terminal device connected to a network device, wherein the first terminal device is to switch from a first path to a second path, both the first path and the second path starting from the first terminal device to the network device, the first path comprising one or more second terminal devices and the third terminal device connected to the network device, the second path excluding at least one of the one or more second terminal devices and/or the third terminal device.
  • the third terminal deivce may comprise means for performing the respective operations of the method 800.
  • the third terminal deivce may further comprise means for performing other operations in some example embodiments of the method 800.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • embodiments of the present disclosure provide the following aspects.
  • a first terminal device comprising: a processor configured to cause the first terminal device to: receive, from a first apparatus, an indication for multi-hop path switching; and switch from a first path to a second path based on the indication, both the first path and the second path starting from the first terminal device to a network device, the first path comprising one or more second terminal devices and a third terminal device connected to the network device, the second path excluding at least one of the one or more second terminal devices and/or the third terminal device.
  • the indication for multi-hop path switching is received from at least one of the network device or one of the one or more second terminal devices.
  • the second path excludes at least one of the one or more second terminal devices
  • the first terminal device is caused to: cause at least a part of a first connection associated with the first terminal device and the at least one of the one or more second terminal devices to be released, the at least part of the first connection comprising at least one of the following: a radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a sidelink relay adaptation protocol (SRAP) layer, a radio link control (RLC) layer, a medium access control (MAC) layer, or a physical layer (PHY) .
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • SRAP sidelink relay adaptation protocol
  • RLC radio link control
  • MAC medium access control
  • PHY physical layer
  • the first terminal device is caused to: determine whether a maintaining indication is comprised in the indication or received from the first apparatus; and in response to determining the maintaining indication is not comprised in the indication or received from the first apparatus, cause at least a part of a second connection associated with the first terminal device and the third terminal device to be released, the at least part of the second connection comprising at least one of the following: a radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a sidelink relay adaptation protocol (SRAP) layer, a radio link control (RLC) layer, a medium access control (MAC) layer, or a physical layer (PHY) ; or in response to determining the maintaining indication is comprised in the indication or received from the first apparatus, maintain at least a part of the second connection associated with the first terminal device and the third terminal device, the at least part of the second connection comprising at least one of a RRC layer or a PDCP layer.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • SRAP side
  • the indication comprises a target device identification (ID)
  • the first terminal device is further caused to: determine whether the target device ID and a device ID of the third terminal device is matched; and in response to determining the target device ID and the device ID is not matched, cause at least a part of a second connection associated with the first terminal device and the third terminal device to be released, the at least part of the second connection comprising at least one of the following: a radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a sidelink relay adaptation protocol (SRAP) layer, a radio link control (RLC) layer, a medium access control (MAC) layer, or a physical layer (PHY) ; or in response to determining the target device ID and the device ID is matched, maintain at least a part of the second connection associated with the first terminal device and the third terminal device, the at least part of the second connection comprising at least one of a RRC layer or a PDCP layer.
  • RRC radio resource control
  • PDCP packet data convergence
  • the first terminal device 210 may perform at least one of the following: using the serving cell of the third terminal device as a serving cell of the first terminal device; applying a predetermined configuration of . sidelink-radio link control (RLC) to a connection associated with at least one of the first terminal device and the third terminal device; or causing a configuration of a connection associated with at least one of the first terminal device, the first apparatus and the third terminal device to be released, the configuration comprising a configuration of at least one of a sidelink-user equipment to user equipment (U2U) RLC or a sidelink-intermediate-RLC.
  • RLC sidelink-radio link control
  • the second path excludes the one or more second terminal devices and the third terminal device but comprises a fourth terminal device connected to the network device, and the first terminal device is caused to: cause at least a part of a second connection associated with the first terminal device and the third terminal device to be released, the at least part of the second connection comprising at least one of the following: a RRC layer, a PDCP layer, a SRAP layer, a RLC layer, a MAC layer, or a PHY; and cause a third connection associated with the first terminal device and the forth terminal device to be established, the third connection comprising at least one of the following: a RRC layer, a PDCP layer, a SRAP layer, a RLC layer, a MAC layer, or a PHY .
  • the second path excludes at least one of the one or more second terminal devices and the third terminal device, and the first terminal device is caused to: cause at least a part of a second connection associated with the first terminal device and the third terminal device to be released, the at least part of the second connection comprising at least one of the following: a RRC layer, a PDCP layer, a SRAP layer, a RLC layer, a MAC layer, or a PHY.
  • the indication is comprised in a message received from one of the one or more second terminal devices, and the message further comprises at least one of failure information indicating a failure in the first path or location information of the failure.
  • the failure information indicates a radio link failure (RLF) occurs in the first path, and/or wherein the location information indicates a connection in which the RLF occurs or a terminal device for which the RLF occurs.
  • RLF radio link failure
  • the indication comprises at least one of failure information indicating a failure in the first path or location information of the failure.
  • a first apparatus comprising: a processor configured to cause the first apparatus to: transmit, to the first terminal device, an indication for multi-hop path switching, to cause the first terminal device to switch from a first path to a second path based on the indication, both the first path and the second path starting from the first terminal device to a network device, the first path comprising one or more second terminal devices and a third terminal device connected to the network device, the second path excluding at least one of the one or more second terminal devices or the third terminal device.
  • the first apparatus comprises the network device or at least one of the one or more second terminal devices.
  • the first apparatus comprises a second terminal device of the one or more second terminal devices, the second path excludes at least one of the one or more second terminal devices, and the second terminal device is caused to: cause at least a part of a first connection associated with the first terminal device and the at least one of the one or more second terminal devices to be released, the at least part of the first connection comprising at least one of the following: a radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a sidelink relay adaptation protocol (SRAP) layer, a radio link control (RLC) layer, a medium access control (MAC) layer, or a physical layer (PHY) .
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • SRAP sidelink relay adaptation protocol
  • RLC radio link control
  • MAC medium access control
  • PHY physical layer
  • the first apparatus comprises a second terminal device of the one or more second terminal devices, and the second terminal device is caused to: in response to determining at least one of the following events occurs: a radio link failure (RLF) in a connection associated with the first terminal device, a radio resource control (RRC) connection release in a connection associated with the third terminal device.
  • RLF radio link failure
  • RRC radio resource control
  • the message comprises at least one of failure information indicating a failure in the first path or location information of the failure.
  • the failure information indicates a radio link failure (RLF) occurs in the first path
  • the location information indicates a connection in which the RLF occurs or a terminal device for which the RLF occurs.
  • RLF radio link failure
  • the first apparatus comprises a second terminal device of the one or more second terminal devices connected to the network device, and the second terminal device is further caused to: in response to determining a radio link failure (RLF) in the first path, cause a radio resource control (RRC) connection to be re-established.
  • RLF radio link failure
  • RRC radio resource control
  • the location information indicates that the RLF is in a connection associated with the second terminal device and the third terminal device, and the second terminal device is further caused to perform at least one of the following: selecting a relay device for second terminal device; selecting a cell as a serving cell for second terminal device; or cause a radio resource control (RRC) connection to be re-established for second terminal device.
  • RRC radio resource control
  • the location information indicates that the RLF is in a connection associated with the second terminal device and the first terminal device, and the second terminal device is further caused to: cause a radio resource control (RRC) connection to be re-established.
  • RRC radio resource control
  • a connection associated with the first terminal device and the third terminal device is an end-to-end connection
  • the second terminal device is caused to : in response to determining a connection failure occurs associated with the third terminal device, transmit the message to the first terminal device; or in response to determining a connection failure occurs associated with the first terminal device, transmit the message to the third terminal device.
  • the location information indicates that a radio link failure (RLF) occurs in a connection associated with the second terminal device and a further second terminal device, the further second terminal device being associated with the third terminal device and the second terminal device, and the second terminal device is caused to:transmit the message to at least one of the first terminal device or the further second terminal device.
  • RLF radio link failure
  • the location information indicates that a radio link failure (RLF) occurs in a connection associated with the second terminal device and a further second terminal device, the further second terminal device being associated with the first terminal device and the second terminal device, and the second terminal device is caused to transmit the message to at least one of the third terminal device or the further second terminal device.
  • RLF radio link failure
  • a third terminal device comprising: a processor configured to cause the third terminal device to: receive, from the one or more second terminal devices, a message comprising an indication for releasing a connection associated with the first terminal device and the third terminal device connected to a network device, wherein the first terminal device is to switch from a first path to a second path, both the first path and the second path starting from the first terminal device to the network device, the first path comprising one or more second terminal devices and the third terminal device connected to the network device, the second path excluding at least one of the one or more second terminal devices and/or the third terminal device.
  • the third terminal device is caused to: cause at least a part of a second connection associated with the first terminal device and the third terminal device to be released, the at least part of the second connection comprising at least one of the following: a radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a sidelink relay adaptation protocol (SRAP) layer, a radio link control (RLC) layer, a medium access control (MAC) layer, or a physical layer (PHY) .
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • SRAP sidelink relay adaptation protocol
  • RLC radio link control
  • MAC medium access control
  • PHY physical layer
  • the message comprises at least one of failure information indicating a failure in the first path or location information of the failure.
  • the failure information indicates a radio link failure (RLF) occurs in the first path
  • the location information indicates a connection in which the RLF occurs or a terminal device for which the RLF occurs.
  • RLF radio link failure
  • a first terminal device comprises: at least one processor; and at least one memory coupled to the at least one processor and storing instructions thereon, the instructions, when executed by the at least one processor, causing the device to perform the method implemented by the first terminal device discussed above.
  • a first apparatus comprises: at least one processor; and at least one memory coupled to the at least one processor and storing instructions thereon, the instructions, when executed by the at least one processor, causing the device to perform the method implemented by the first apparatus discussed above.
  • a third terminal device comprises: at least one processor; and at least one memory coupled to the at least one processor and storing instructions thereon, the instructions, when executed by the at least one processor, causing the device to perform the method implemented by the third terminal device discussed above.
  • a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the first terminal device discussed above.
  • a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the first apparatus discussed above.
  • a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the third terminal device discussed above.
  • a computer program comprising instructions, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the first terminal device discussed above.
  • a computer program comprising instructions, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the first apparatus discussed above.
  • a computer program comprising instructions, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the third terminal device discussed above.
  • various embodiments of the present disclosure may be implemented in hardware or special purpose 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 executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representation, it will be appreciated that the blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • 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, being executed in a device on a target real or virtual processor, to carry out the process or method as described above with reference to FIGS. 1 to 9.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or split between program modules as desired in various embodiments.
  • Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
  • Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented.
  • the program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
  • the above program code may be embodied on a machine readable medium, which may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • the machine readable medium may be a machine readable signal medium or a machine readable storage medium.
  • a machine readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
  • machine readable storage medium More specific examples of the machine readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, 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 disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • RAM random access memory
  • ROM read-only memory
  • EPROM or Flash memory erasable programmable read-only memory
  • CD-ROM portable compact disc read-only memory
  • magnetic storage device or any suitable combination of the foregoing.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation de la présente divulgation concernent une solution pour la gestion de connexion d'un trajet à sauts multiples. Dans une solution, un premier dispositif terminal reçoit une indication pour une commutation de trajet à sauts multiples à partir d'un premier appareil et commute d'un premier trajet à un second trajet sur la base de l'indication. À la fois le premier trajet et le second trajet sont du premier dispositif terminal vers un dispositif de réseau, le premier trajet comprend un ou plusieurs deuxièmes dispositifs terminaux et un troisième dispositif terminal connecté au dispositif de réseau, le deuxième trajet exclut au moins l'un parmi le ou les deuxièmes dispositifs terminaux et/ou le troisième dispositif terminal.
PCT/CN2024/111275 2024-08-09 2024-08-09 Dispositifs et procédés de communication Pending WO2026031231A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/111275 WO2026031231A1 (fr) 2024-08-09 2024-08-09 Dispositifs et procédés de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/111275 WO2026031231A1 (fr) 2024-08-09 2024-08-09 Dispositifs et procédés de communication

Publications (1)

Publication Number Publication Date
WO2026031231A1 true WO2026031231A1 (fr) 2026-02-12

Family

ID=98734601

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/111275 Pending WO2026031231A1 (fr) 2024-08-09 2024-08-09 Dispositifs et procédés de communication

Country Status (1)

Country Link
WO (1) WO2026031231A1 (fr)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101330308A (zh) * 2007-06-22 2008-12-24 中兴通讯股份有限公司 中继站快速切换方法、装置及无线通信网络
CN108337701A (zh) * 2017-01-19 2018-07-27 工业和信息化部电信研究院 一种传输路径切换方法
CN110636570A (zh) * 2018-06-25 2019-12-31 中兴通讯股份有限公司 Iab网络中iab节点信息的处理方法及装置
WO2020011907A1 (fr) * 2018-07-12 2020-01-16 Koninklijke Kpn N.V. Relais à sauts multiples dans un réseau de communication mobile
WO2020176537A1 (fr) * 2019-02-25 2020-09-03 Apple Inc. Retransmission de liaison montante (ul) et reprise après défaillance de la liaison radio (rlf) dans un réseau relais à plusieurs bonds
US20210160956A1 (en) * 2019-11-22 2021-05-27 Mediatek Singapore Pte. Ltd. Packet Routing for Layer-2-Based Sidelink Relay
US20210160957A1 (en) * 2019-11-22 2021-05-27 Mediatek Singapore Pte. Ltd. Adaptation Handling for Layer-2-Based Sidelink Relay

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101330308A (zh) * 2007-06-22 2008-12-24 中兴通讯股份有限公司 中继站快速切换方法、装置及无线通信网络
CN108337701A (zh) * 2017-01-19 2018-07-27 工业和信息化部电信研究院 一种传输路径切换方法
CN110636570A (zh) * 2018-06-25 2019-12-31 中兴通讯股份有限公司 Iab网络中iab节点信息的处理方法及装置
WO2020011907A1 (fr) * 2018-07-12 2020-01-16 Koninklijke Kpn N.V. Relais à sauts multiples dans un réseau de communication mobile
WO2020176537A1 (fr) * 2019-02-25 2020-09-03 Apple Inc. Retransmission de liaison montante (ul) et reprise après défaillance de la liaison radio (rlf) dans un réseau relais à plusieurs bonds
US20210160956A1 (en) * 2019-11-22 2021-05-27 Mediatek Singapore Pte. Ltd. Packet Routing for Layer-2-Based Sidelink Relay
US20210160957A1 (en) * 2019-11-22 2021-05-27 Mediatek Singapore Pte. Ltd. Adaptation Handling for Layer-2-Based Sidelink Relay

Similar Documents

Publication Publication Date Title
US20250142425A1 (en) Method, device and computer storage medium of communication
WO2023173283A1 (fr) Communication pour relais u2u
WO2023201490A1 (fr) Procédé, dispositif et support de stockage informatique destinés à la communication
WO2023077317A1 (fr) Procédé, dispositif et support de stockage informatique pour la communication
WO2026031231A1 (fr) Dispositifs et procédés de communication
WO2024168700A1 (fr) Dispositifs et procédés de communication
WO2024007176A1 (fr) Procédés, dispositifs et support de communication
WO2023230884A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2023178572A1 (fr) Procédés, dispositifs et support lisible par ordinateur de communication
WO2023050187A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2024229835A1 (fr) Dispositifs et procédés de communication
WO2024197677A1 (fr) Dispositifs, procédés et support pour communication
WO2024207238A1 (fr) Dispositifs et procédés de communication
WO2025091422A1 (fr) Dispositifs et procédés de communication
WO2026030893A1 (fr) Dispositifs et procédés d'approvisionnement de règles atsss
WO2025199769A1 (fr) Dispositifs et procédés de communication
WO2026091147A1 (fr) Dispositifs et procédés de communication
WO2024016364A1 (fr) Procédés, dispositifs et support de communication
WO2025147978A1 (fr) Dispositifs et procédés de communication
WO2025065406A1 (fr) Dispositifs et procédés de communication
WO2024229831A1 (fr) Dispositifs et procédés de communication
WO2024207377A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2025222516A1 (fr) Dispositifs et procédés de découverte de relais
WO2025025134A1 (fr) Dispositifs et procédés de communication
US20250330877A1 (en) Methods, devices, and medium for communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24950264

Country of ref document: EP

Kind code of ref document: A1