Information sending methods and apparatuses, and related device

Abstract

The present application belongs to the technical field of communications. Disclosed are information sending methods and apparatuses, and a related device. A method in the embodiments of the present application comprises: a first relay terminal receiving target information sent by a remote terminal; and the first relay terminal sending the target information to a network-side device by means of a first parent node, the first parent node being a relay terminal in a relay link that is connected to the first relay terminal and located between the first relay terminal and the network-side device, wherein the first relay terminal is connected to the remote terminal, and the relay link is a relay link between the remote terminal and the network-side device.

Description

Information sending method, device and related equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese patent application No. 202311809542.9 filed in China on December 26, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to an information sending method, device and related equipment. Background Art

[0004] In related technologies, a remote terminal is connected to a network-side device through a relay terminal. The link quality of the relay terminal must meet a certain Reference Signal Received Power (RSRP) threshold requirement. The remote terminal may not be able to find a suitable relay terminal to connect to the network-side device, which will make it impossible for the remote terminal to communicate with the network-side device, resulting in poor communication performance between the remote terminal and the network-side device. Summary of the Invention

[0005] The embodiments of the present application provide an information sending method, apparatus, and related equipment, which can solve the problem of poor communication performance between a remote terminal and a network-side device.

[0006] In a first aspect, a method for sending information is provided, comprising:

[0007] The first relay terminal receives target information sent by the remote terminal;

[0008] The first relay terminal sends the target information to the network-side device through a first parent node, where the first parent node is a relay terminal connected to the first relay terminal in a relay link and located between the first relay terminal and the network-side device;

[0009] The first relay terminal is connected to the remote terminal, and the relay link is a relay link between the remote terminal and the network side device.

[0010] In a second aspect, a method for sending information is provided, comprising:

[0011] The second relay terminal receives target information sent by the remote terminal through a first sub-node, where the first sub-node is a relay terminal connected to the second relay terminal in a relay link and located between the second relay terminal and the remote terminal;

[0012] The second relay terminal sends the target information to the network side device;

[0013] The second relay terminal is connected to the network side device, and the relay link is a relay link between the remote terminal and the network side device.

[0014] In a third aspect, a method for sending information is provided, comprising:

[0015] The third relay terminal receives target information sent by the remote terminal through a second sub-node, where the second sub-node is a relay terminal connected to the third relay terminal in a relay link and located between the third relay terminal and the remote terminal;

[0016] The third relay terminal sends the target information to the network-side device through a second parent node, where the second parent node is a relay terminal connected to the third relay terminal in the relay link and located between the third relay terminal and the network-side device;

[0017] The relay link is a relay link between the remote terminal and the network side device.

[0018] In a fourth aspect, a method for sending information is provided, comprising:

[0019] The remote terminal sends target information to the network side device through at least two relay terminals;

[0020] The relay link between the remote terminal and the network side device includes the at least two relay terminals, and the at least two relay terminals include a first relay terminal connected to the remote terminal and a second relay terminal connected to the network side device.

[0021] In a fifth aspect, an information sending device is provided. The first relay terminal includes the information sending device, and the device includes:

[0022] A first receiving module, configured to receive target information sent by a remote terminal;

[0023] a sending module, configured to send the target information to the network-side device through a first parent node, where the first parent node is a relay terminal connected to the first relay terminal in a relay link and located between the first relay terminal and the network-side device;

[0024] The first relay terminal is connected to the remote terminal, and the relay link is a relay link between the remote terminal and the network side device.

[0025] In a sixth aspect, an information sending device is provided. The second relay terminal includes the information sending device, and the device includes:

[0026] a first receiving module, configured to receive target information sent by a remote terminal through a first sub-node, where the first sub-node is a relay terminal connected to the second relay terminal in a relay link and located between the second relay terminal and the remote terminal;

[0027] A first sending module, configured to send the target information to a network side device;

[0028] The second relay terminal is connected to the network side device, and the relay link is a relay link between the remote terminal and the network side device.

[0029] In a seventh aspect, an information sending device is provided. The third relay terminal includes the information sending device, and the device includes:

[0030] a first receiving module, configured to receive target information sent by a remote terminal through a second sub-node, where the second sub-node is a relay terminal connected to the third relay terminal in a relay link and located between the third relay terminal and the remote terminal;

[0031] a sending module, configured to send the target information to the network-side device through a second parent node, where the second parent node is a relay terminal connected to the third relay terminal in the relay link and located between the third relay terminal and the network-side device;

[0032] The relay link is a relay link between the remote terminal and the network side device.

[0033] In an eighth aspect, an information sending device is provided. The remote terminal includes the information sending device, and the device includes:

[0034] A sending module, configured to send target information to a network-side device via at least two relay terminals;

[0035] The relay link between the remote terminal and the network side device includes the at least two relay terminals, and the at least two relay terminals include a first relay terminal connected to the remote terminal and a second relay terminal connected to the network side device.

[0036] In the ninth aspect, a communication device is provided, which includes a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect, the second aspect, the third aspect, or the fourth aspect are implemented.

[0037] In a tenth aspect, a communication device is provided, wherein the communication device is a first relay terminal, including a processor and a communication interface, wherein the communication interface is configured to:

[0038] Receive target information sent by a remote terminal;

[0039] Sending the target information to the network-side device through a first parent node, where the first parent node is a relay terminal connected to the first relay terminal in a relay link and located between the first relay terminal and the network-side device;

[0040] The first relay terminal is connected to the remote terminal, and the relay link is a relay link between the remote terminal and the network side device.

[0041] In an eleventh aspect, a communication device is provided, wherein the communication device is a second relay terminal, including a processor and a communication interface, wherein the communication interface is configured to:

[0042] receiving target information sent by a remote terminal through a first child node, where the first child node is a relay terminal connected to the second relay terminal in a relay link and located between the second relay terminal and the remote terminal;

[0043] Sending the target information to the network side device;

[0044] The second relay terminal is connected to the network side device, and the relay link is a relay link between the remote terminal and the network side device.

[0045] According to a twelfth aspect, a communication device is provided. The communication device is a third relay terminal, including a processor and a communication interface, wherein the communication interface is configured to:

[0046] receiving target information sent by a remote terminal through a second child node, where the second child node is a relay terminal connected to the third relay terminal in a relay link and located between the third relay terminal and the remote terminal;

[0047] Sending the target information to the network-side device through a second parent node, where the second parent node is a relay terminal connected to the third relay terminal in the relay link and located between the third relay terminal and the network-side device;

[0048] The relay link is a relay link between the remote terminal and the network side device.

[0049] In a thirteenth aspect, a communication device is provided, wherein the communication device is a remote terminal, including a processor and a communication interface, wherein the communication interface is configured to:

[0050] Sending target information to a network-side device through at least two relay terminals;

[0051] The relay link between the remote terminal and the network side device includes the at least two relay terminals, and the at least two relay terminals include a first relay terminal connected to the remote terminal and a second relay terminal connected to the network side device.

[0052] In the fourteenth aspect, an information sending system is provided, comprising: a first relay terminal, a second relay terminal, a third relay terminal and a remote terminal, wherein the first relay terminal can be used to execute the steps of the method described in the first aspect, the second relay terminal can be used to execute the steps of the method described in the second aspect, the third relay terminal can be used to execute the steps of the method described in the third aspect, and the remote terminal can be used to execute the steps of the method described in the fourth aspect.

[0053] In the fifteenth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented, or the steps of the method described in the third aspect are implemented, or the steps of the method described in the fourth aspect are implemented.

[0054] In the sixteenth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method described in the first aspect, or the method described in the second aspect, or the method described in the third aspect, or the method described in the fourth aspect.

[0055] In the seventeenth aspect, a computer program / program product is provided, which is stored in a storage medium and executed by at least one processor to implement the steps of the method described in the first aspect, the second aspect, the third aspect, or the fourth aspect.

[0056] In an embodiment of the present application, a first relay terminal receives target information sent by a remote terminal; the first relay terminal sends the target information to a network-side device via a next-hop relay terminal; wherein the first relay terminal is connected to the remote terminal and is a relay terminal among at least two relay terminals included in a relay link between the remote terminal and the network-side device. In this way, the remote terminal can communicate with the network-side device via a relay link including at least two relay terminals, avoiding the possibility that the remote terminal may not find a suitable relay terminal to connect to the network-side device due to the remote terminal being able to connect to the network-side device via only one relay terminal, thereby improving the communication performance between the remote terminal and the network-side device. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] FIG1 is a block diagram of a wireless communication system to which embodiments of the present application may be applied;

[0058] Figure 2 is a diagram of a UE-to-Network relay scenario;

[0059] FIG3 is a flowchart of a method for sending information provided in an embodiment of the present application;

[0060] FIG4 is a second flowchart of an information sending method provided in an embodiment of the present application;

[0061] FIG5 is a third flowchart of an information sending method provided in an embodiment of the present application;

[0062] FIG6 is a fourth flowchart of an information sending method provided in an embodiment of the present application;

[0063] FIG7 is a schematic diagram of a multi-hop U2N link according to an embodiment of the present application;

[0064] FIG8 is a second schematic diagram of a multi-hop U2N link provided in an embodiment of the present application;

[0065] FIG9 is a schematic diagram of a structure of an information sending device according to an embodiment of the present application;

[0066] FIG10 is a second structural diagram of an information sending device provided in an embodiment of the present application;

[0067] FIG11 is a third structural diagram of an information sending device provided in an embodiment of the present application;

[0068] FIG12 is a fourth structural diagram of an information sending device provided in an embodiment of the present application;

[0069] FIG13 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0070] FIG14 is a schematic structural diagram of a terminal provided in an embodiment of the present application. DETAILED DESCRIPTION

[0071] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0072] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0073] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0074] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. thGeneration, 6G) communication system.

[0075] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AS) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, relay base station (RBS), serving base station (SBS), base transceiver station (BTS), radio base station, radio transceiver, basic service set (BSS), extended service set (ESS), home Node B (HNB), home evolved Node B (home evolved Node B), transmission reception point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example to introduce, and the specific type of the base station is not limited.

[0076] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (MME), access mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application service discovery function (EASDF), unified data management (UDM), unified data repository (UDR), home user server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BSF), application function ( Function, AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), Network Data Analytics Function (NWDAF), etc. It should be noted that in the embodiment of the present application, only the core network equipment in the NR system is taken as an example to introduce, and the specific type of the core network equipment is not limited.

[0077] For ease of understanding, some terms involved in the embodiments of this application are explained below:

[0078] 1. Sidelink relay mechanism

[0079] Relay technology in wireless communication systems adds one or more relay nodes between the base station and the terminal, which is responsible for forwarding the wireless signal once or multiple times. That is, the wireless signal has to go through multiple hops before reaching the terminal.

[0080] Wireless relay technology not only expands cell coverage and fills blind spots, but also increases cell capacity through spatial resource reuse. For indoor coverage, relay technology can also overcome penetration loss and improve indoor coverage quality.

[0081] Taking a simple two-hop relay as an example, wireless relay splits a base station-terminal link into two links: base station-relay station and relay station-terminal. This allows one poor-quality link to be replaced with two high-quality links, achieving higher link capacity and better coverage.

[0082] Currently, the relay supported in LTE is the UE-to-Network (U2N) relay, where one end of the relay is connected to the UE and the other end is connected to the network. The UE connected to the relay is called the remote UE. The remote UE can also be described as a remote terminal.

[0083] NR will also investigate how to support UE-to-network relay mechanisms. A typical scenario is shown in Figure 2. In this typical UE-to-network scenario, a remote UE needs to transmit data to the network. Due to poor coverage, a relay UE is used to relay data. The relay UE and the base station use the Uu interface, while the relay UE and remote UE use the sidelink (PC5) interface. Generally speaking, the relay UE is open and can serve any remote UE.

[0084] In related technologies, a remote terminal may not be able to find a suitable relay UE to connect to a network-side device, which may make it impossible for the remote terminal to communicate with the network-side device, resulting in poor communication performance between the remote terminal and the network-side device.

[0085] The information sending method, apparatus and related equipment provided in the embodiments of the present application are described in detail below with reference to some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0086] Referring to FIG3 , FIG3 is a flow chart of an information sending method provided in an embodiment of the present application. As shown in FIG3 , the information sending method includes the following steps:

[0087] Step 101: A first relay terminal receives target information sent by a remote terminal;

[0088] Step 102: The first relay terminal sends the target information to a network-side device through a first parent node, where the first parent node is a relay terminal connected to the first relay terminal in a relay link and located between the first relay terminal and the network-side device.

[0089] The first relay terminal is connected to the remote terminal, and the relay link is a relay link between the remote terminal and the network side device.

[0090] The relay link may include at least two relay terminals, and the relay link may also be described as a multi-hop U2N relay link. The first relay terminal being connected to the remote terminal may mean that the first relay terminal is directly connected to the remote terminal, that is, the first relay terminal is not connected to the remote terminal through other relay terminals.

[0091] The target information may be any information, and this embodiment does not limit the target information. For example, the target information may be user data.

[0092] The first parent node may be a second relay terminal or a third relay terminal. The second relay terminal is connected to a network-side device. It should be noted that the second relay terminal being connected to the network-side device may mean that the second relay terminal is directly connected to the network-side device, i.e., the second relay terminal is not connected to the network-side device through another relay terminal.

[0093] In one embodiment, taking the example of a relay link comprising two relay terminals, the relay link is composed of a first relay terminal and a second relay terminal, and the target information is transmitted in the following order: remote terminal > first relay terminal > second relay terminal > network-side device. In this case, the first parent node of the first relay terminal is the second relay terminal, and the child node of the second relay terminal is the first relay terminal.

[0094] In one embodiment, taking the relay link as an example, where the relay link includes three relay terminals, the relay link is composed of a first relay terminal, a third relay terminal, and a second relay terminal. The target information is transmitted in the following order: remote terminal > first relay terminal > third relay terminal > second relay terminal > network-side device. In this case, the first parent node is the third relay terminal.

[0095] In one embodiment, taking the relay link including N (N is an integer) third relay terminals as an example, the relay link is composed of a first relay terminal, multiple third relay terminals, and a second relay terminal, and the target information is transmitted in the following order: remote terminal > first relay terminal > first third relay terminal > second third relay terminal, ..., N-1th third relay terminal > Nth third relay terminal > second relay terminal > network-side device. In this case, the first parent node of the first relay terminal is the first third relay terminal. The parent node of the first third relay terminal is the second third relay terminal; the child node of the first third relay terminal is the first third relay terminal; and so on, the parent node of the Nth third relay terminal is the second relay terminal, the child node of the Nth third relay terminal is the N-1th third relay terminal, and the child node of the second relay terminal is the Nth third relay terminal.

[0096] In the related art, only remote terminals (remote UE) are supported to connect to the network through a relay terminal (relay UE), that is, a one-hop relay link. The single-hop scenario is relatively simple, and the connection establishment process only involves the processing of one relay UE. However, the single-hop relay link requires that the relay UE must be a terminal within the network coverage, and the link quality of the relay UE must meet certain RSRP high thresholds or low thresholds, so the effect on coverage expansion is limited. The remote UE may not find an available relay UE around it and cannot communicate with the network. The relay link in the embodiment of the present application is a multi-hop relay link, which can better solve the coverage problem. The remote UE can establish a connection with the network through relaying of multiple relay UEs.

[0097] In an embodiment of the present application, a first relay terminal receives target information sent by a remote terminal; the first relay terminal sends the target information to a network-side device via a next-hop relay terminal; wherein the first relay terminal is connected to the remote terminal and is a relay terminal among at least two relay terminals included in a relay link between the remote terminal and the network-side device. In this way, the remote terminal can communicate with the network-side device via a relay link including at least two relay terminals, avoiding the possibility that the remote terminal may not find a suitable relay terminal to connect to the network-side device due to the remote terminal being able to connect to the network-side device via only one relay terminal, thereby improving the communication performance between the remote terminal and the network-side device.

[0098] Optionally, before the first relay terminal receives the target information sent by the remote terminal, the method further includes at least one of the following:

[0099] The first relay terminal receives the first discovery message sent by the remote terminal, adds the device identifier of the first relay terminal to the routing information carried in the first discovery message, and sends the added first discovery message;

[0100] The first relay terminal receives a first response message sent by the first parent node;

[0101] The first relay terminal sends a first response message to the remote terminal;

[0102] The first response message carries the routing information of the relay link.

[0103] The first discovery message may carry the needs of the remote terminal, such as the desire to communicate with the network side for a certain service type through a multi-hop relay link. The first relay terminal receives the first discovery message. Since the first relay terminal does not have the conditions to communicate directly with the network side (such as a base station), but can support multi-hop services based on the capabilities of the first relay terminal, the first relay terminal can help the remote UE forward the first discovery message and add the identifier of the first relay terminal to the routing table.

[0104] It should be noted that before establishing the relay link, a hop-by-hop discovery process can be implemented through the first discovery message or the first response message to determine the route of the multi-hop U2N relay link, that is, through which relay UEs the remote terminal (remote UE) accesses the network in sequence.

[0105] Taking the relay link as an example, in which two relay terminals are included, the first relay terminal receives the first discovery message sent by the remote terminal, adds the device identifier of the first relay terminal to the routing information carried in the first discovery message, and sends the first discovery message after the addition; the second relay terminal receives the first discovery message sent by the first relay terminal, adds the device identifier of the second relay terminal to the routing information carried in the first discovery message, and sends the first discovery message after the addition; the second relay terminal sends a first response message to the first relay terminal, the first response message carrying the routing information of the relay link; the first relay terminal receives the first response message sent by the second relay terminal; and the first relay terminal sends the first response message to the remote terminal. This can implement a hop-by-hop discovery process.

[0106] In one embodiment, the first relay terminal adds the device identifier of the first relay terminal to the routing information carried by the first discovery message, and sends the added first discovery message; the first parent node of the first relay terminal (i.e., the second relay terminal or the first third relay terminal) receives the first discovery message sent by the first relay terminal, adds the device identifier of the first parent node to the routing information carried by the first discovery message, and sends the added first discovery message; 0-N third relay terminals sequentially receive the first discovery message and routing table forwarded by the first relay terminal, and since they themselves do not have the conditions to communicate directly with the network side device (such as the base station), they can continue to communicate according to their capabilities and business requirements (for example, some businesses have time delay requirements, which cannot exceed 3 hops at most). Continue to support the forwarding of the multi-hop requirement, and therefore continue to help the remote terminal forward the first discovery message, and in turn add its own identifier to the routing table. Finally, the second relay terminal receives the first discovery message. Since it has the conditions to communicate directly with the network side device, such as RSRP meets certain threshold requirements, it can respond to the first discovery message and add its own identifier to the routing table. The first response message carries the routing information of the relay link (such as a complete routing table), and according to the node information recorded in the routing table in the first discovery message, the first response message is sent in reverse to the previous hop relay terminal. After that, each hop relay terminal sends the first response message step by step according to the routing table. Finally, the first relay terminal sends the first response message carrying the complete routing table to the remote terminal.

[0107] Furthermore, since the first discovery message is sent in broadcast mode, there may be more than one multi-hop relay link after a discovery process response. The remote terminal can select the most suitable one as its final multi-hop relay route, for example, the one that meets at least one of the following conditions: the minimum number of link hops, the shortest response delay, the best overall link quality, or the lightest overall link load, as the final multi-hop relay route.

[0108] In addition, after completing the discovery process, the remote terminal can also establish a PC5 link connection with the third relay terminal through the Direct Communication Request (DCR) process and inform the third relay terminal of the relay link routing information. The third relay terminal then establishes a PC5 link connection with its next hop, the parent node, through the DCR process and informs the parent node of the relay link routing information. This process is repeated in sequence, and finally the second relay terminal also establishes a PC5 connection with its child node through the DCR process and obtains the relay link routing information. This completes the route discovery and PC5 link establishment process between the remote terminal and the second relay terminal.

[0109] It should be noted that the above discovery process and DCR process can be combined, that is, the same set of signaling processes can complete both route discovery and the step-by-step establishment of PC5 links, thereby saving signaling delay.

[0110] In this embodiment, the first relay terminal receives the first discovery message sent by the remote terminal, adds the device identifier of the first relay terminal to the routing information carried by the first discovery message, and sends the added first discovery message; or, the first relay terminal receives the first response message sent by the first parent node; or, the first relay terminal sends a first response message to the remote terminal; in this way, the first relay terminal participates in the process of discovering or establishing a relay link through the first discovery message initiated by the remote terminal, and realizes the establishment of a relay link including at least two relay terminals.

[0111] Optionally, before the first relay terminal receives the target information sent by the remote terminal, the method further includes at least one of the following:

[0112] The first relay terminal receives the second discovery message sent by the first parent node, adds the device identifier of the first relay terminal to the routing information carried in the second discovery message, and sends the added second discovery message;

[0113] The first relay terminal receives a second response message sent by the remote terminal;

[0114] The first relay terminal sends a second response message to the first parent node;

[0115] The second response message carries the routing information of the relay link.

[0116] It should be noted that since the second relay terminal communicates directly with the gNB through the Uu interface, it can actively initiate a discovery process to the surrounding area, declare which multi-hop relay donor operations for specific services it can support, and add its own identifier to the routing table.

[0117] Taking the relay link as an example, in which two relay terminals are included, the second relay terminal sends a second discovery message; the first relay terminal receives the second discovery message sent by the second relay terminal, adds the device identifier of the first relay terminal to the routing information carried in the second discovery message, and sends the added second discovery message; the remote terminal receives the second discovery message sent by the first relay terminal and sends a second response message to the first relay terminal, where the second response message carries the routing information of the relay link; the first relay terminal receives the second response message sent by the remote terminal; the first relay terminal sends a second response message to the second relay terminal; and the second relay terminal receives the second response message sent by the first relay terminal. This can implement a hop-by-hop discovery process.

[0118] In one embodiment, a second relay terminal sends a second discovery message. The 0-N third relay terminals that receive the second discovery message may sequentially add their identifiers to the routing table and forward the second discovery message. The first relay terminal may receive the second discovery message sent by the third relay terminal, add the first relay terminal's device identifier to the routing information carried in the second discovery message, and then send the added second discovery message. After receiving the second discovery message, the remote terminal has a matching U2N service to initiate and may therefore respond to the second discovery message. Subsequently, the remote terminal also sends second response messages in the reverse direction of the routing table, step by step, until it reaches the second relay terminal. At this point, the discovery process for a multi-hop U2N route is complete. In particular, when the remote terminal has multiple routes to choose from, it may select the most suitable one as its final multi-hop relay route, for example, one that meets at least one of the following conditions: minimum link hops, shortest response delay, best overall link quality, or lightest overall link load.

[0119] It should be noted that after route discovery is complete, a DCR process can be performed on each hop to establish PC5 link connections between each hop. Since the remote terminal ultimately selects the route, the remote terminal generally initiates a DCR process with the first relay terminal to establish a PC5 link connection. This first relay terminal then establishes a PC5 link connection with the first third relay terminal, and so on, until a PC5 link is established between the second relay terminal and the last third relay terminal. This completes the route discovery and PC5 link establishment process between the remote terminal and the second relay terminal.

[0120] In this embodiment, the first relay terminal receives the second discovery message sent by the next-hop relay terminal, adds the device identifier of the first relay terminal to the routing information carried by the second discovery message, and sends the added second discovery message; or, the first relay terminal receives the second response message sent by the remote terminal; or, the first relay terminal sends a second response message to the next-hop relay terminal; in this way, the first relay terminal participates in the process of discovering or establishing a relay link through the second discovery message initiated by other relay terminals, thereby realizing the establishment of a relay link including at least two relay terminals.

[0121] Optionally, the method further includes:

[0122] The first relay terminal receives a first message sent by the remote terminal, where the first message is an end-to-end message between the remote terminal and the network-side device;

[0123] When the first relay terminal is in an unconnected state, the first relay terminal initiates entry into a connected state; or, when the first relay terminal is in a connected state, the first relay terminal sends a first relay request to the network side device through a radio resource control (RRC) process;

[0124] The first relay request includes at least one of the following:

[0125] Remote terminal identification;

[0126] Multi-hop relay link indication;

[0127] routing information of the relay link stored by the first relay terminal;

[0128] Indication information indicating the number of relay terminals included in the routing information of the relay link stored in the first relay terminal.

[0129] The first message can be used to establish a connection between a remote terminal and a network-side device. For example, the first message can be a connection establishment request carried by SRB0, a connection recovery request carried by SRB1, or a reestablishment request carried by SRB0. A multi-hop relay link indication can be used to indicate a desire to initiate a multi-hop relay link establishment. SRB refers to a signaling radio bearer.

[0130] In addition, the counterpart of the first message may be the network side device.

[0131] The remote terminal identifier may identify the identity of the remote terminal. The routing information of the relay link stored by the first relay terminal may include routing information between the remote terminal and the network-side device. The number of relay terminals included in the routing information of the relay link stored by the first relay terminal may include the number of relay terminals included in the routing information between the remote terminal and the network-side device.

[0132] It should be noted that the connection between the remote terminal and the network-side device may be established after the route discovery or PC5 link establishment process between the remote terminal and the second relay terminal is completed.

[0133] The embodiments of the present application provide a method for establishing a multi-hop U2N relay link, which enables a remote UE to perform an initial establishment process with the network side through a multi-hop relay connection (link) and supports relay UEs in different RRC states. This provides a feasible solution for establishing multi-hop links, ensuring the data transmission performance of the remote UE, reducing the processing complexity of the relay UE, and improving the overall network efficiency, capacity, and coverage.

[0134] In this embodiment, the first relay terminal receives a first message sent by the remote terminal, where the first message is an end-to-end message between the remote terminal and the network-side device; when the first relay terminal is in a non-connected state, the first relay terminal initiates entry into a connected state; or, when the first relay terminal is in a connected state, the first relay terminal sends a first relay request to the network-side device through an RRC process. In this way, the first message sent by the remote terminal triggers the first relay terminal to enter the connected state, or triggers the first relay terminal to send the first relay request, so that the remote terminal can enter the connected state by sending the first message to the first relay terminal with the network-side counterparty.

[0135] Optionally, the first relay terminal initiating entry into the connected state includes at least one of the following:

[0136] The first relay terminal sends a second message to the first parent node, where the second message is an end-to-end message between the first relay terminal and the network-side device;

[0137] The first relay terminal receives an RRC response message corresponding to the second message sent by the first parent node;

[0138] The method further comprises:

[0139] The first relay terminal sends a first relay request to the network side device through an RRC process.

[0140] The RRC response message corresponding to a message (such as the first message, the second message, or the third message, etc.) may be a response message of the network side device to the message. For example, the RRC response message may be RRC setup or RRC resume.

[0141] In addition, the counterpart of the second message may be the network-side device.

[0142] Taking the relay link including two relay terminals as an example, the first parent node is the second relay terminal, the first relay terminal sends a second message to the second relay terminal (in this case, the second message is equivalent to the third message); when the second relay terminal is in a non-connected state, the second relay terminal initiates entry into a connected state; or, when the second relay terminal is in a connected state, the second relay terminal sends a second relay request to the network side device through an RRC process (in this case, the second relay request is equivalent to the third relay request). The second relay terminal receives an RRC response message corresponding to the second message sent by the network side device; the second relay terminal sends an RRC response message corresponding to the second message to the first relay terminal; the first relay terminal receives an RRC response message corresponding to the second message sent by the second relay terminal; at this time, the first relay terminal enters a connected state, and the first relay terminal sends a first relay request to the network side device through an RRC process.

[0143] Taking the example that the relay link includes more than two relay terminals, that is, the relay link includes N (N is an integer) third relay terminals, the first parent node is a third relay terminal directly connected to the first relay terminal, and the first relay terminal sends a second message to the first parent node (in this case, the second message is equivalent to the fourth message); when the first parent node is in a non-connected state, the first parent node initiates entry into a connected state; or, when the first parent node is in a connected state, the first parent node sends a second relay request to the network side device through an RRC process (in this case, the second relay request is equivalent to the fourth relay request). When the first parent node is in a connected state and sends the second relay request, the first parent node receives an RRC response message corresponding to the second message sent by the network side device; the first parent node sends an RRC response message corresponding to the second message to the first relay terminal; the first relay terminal receives an RRC response message corresponding to the second message sent by the first parent node; at this time, the first relay terminal enters a connected state, and the first relay terminal sends a first relay request to the network side device through an RRC process.

[0144] The embodiments of the present application can solve the problem that in a multi-hop U2N relay link, the remote UE initiates a connection establishment process to the network side through the first relay terminal using the multi-hop relay link. When each relay node receives the end-to-end signaling trigger from the downstream remote UE or relay UE, if it is not in the RRC connected (CONNECTED) state, it first enters the connected state and reports the demand to the network, obtains the relay link configuration, and then forwards the end-to-end signaling.

[0145] In this embodiment, the first relay terminal sends a second message to the next-hop relay terminal, where the second message is an end-to-end message between the first relay terminal and the network-side device, so that the first relay terminal can transmit the second message whose opposite end is the network side through the next-hop relay terminal; the first relay terminal receives the RRC response message corresponding to the second message sent by the next-hop relay terminal, so that the network side can send the RRC response message whose opposite end is the first relay terminal to the first relay terminal through the next-hop relay terminal; the first relay terminal sends a first relay request to the network-side device through the RRC process, so that the first relay request can be transmitted after the first relay terminal enters the connected state.

[0146] Optionally, the second message is used to: when the first parent node is in a non-connected state, trigger the first parent node to initiate entry into a connected state; or, when the first parent node is in a connected state, trigger the first parent node to send a second relay request to the network side device through an RRC process.

[0147] The second relay request includes at least one of the following:

[0148] Remote terminal identification;

[0149] an identifier of the first relay terminal;

[0150] Multi-hop relay link indication;

[0151] Routing information of the relay link stored by the first parent node;

[0152] Indication information indicating the number of relay terminals included in the routing information of the relay link stored by the first parent node.

[0153] It should be noted that in a multi-hop U2N relay route, no matter how many relay nodes are involved, only the second relay terminal can directly communicate with the network-side device via the Uu interface. There is no direct Uu interface link between other relay terminals and the network-side device. However, since other relay terminals need to transfer data for remote UEs, these other relay terminals also need to be centrally controlled by the network-side device, obtain configuration or resources from the network side, and perform centralized bearer configuration and mapping management by the network-side device. Therefore, all relay terminals in the relay link must enter the connected state.

[0154] Optionally, after the first relay terminal sends the first relay request to the network side device through an RRC process, the method further includes at least one of the following:

[0155] The first relay terminal receives an RRC response message corresponding to the first message sent by the network side device;

[0156] The first relay terminal sends the RRC response message corresponding to the first message to the remote terminal through the PC5 radio link control RLC channel.

[0157] In this embodiment, the first relay terminal receives the RRC response message corresponding to the first message sent by the network side device, so that the network side can send the RRC response message with the remote terminal as the opposite end to the remote terminal through the first relay terminal; the first relay terminal sends the RRC response message corresponding to the first message to the remote terminal through the PC5 RLC channel, thereby realizing the transmission of the RRC response message with the remote terminal as the opposite end through the first relay terminal, thereby realizing the establishment of an RRC connection between the remote terminal and the network side device.

[0158] Optionally, before the first relay terminal receives the target information sent by the remote terminal, the method further includes:

[0159] The first relay terminal receives first configuration information sent by the network side device;

[0160] The first configuration information is used to configure at least one of the following:

[0161] The local identifier of the remote terminal; the first PC5 RLC channel; the mapping relationship between the E2E SRB0 or ​​E2ESRB1 of the remote terminal and the first PC5 RLC channel;

[0162] The local identifier of the remote terminal is used to identify data of the remote terminal in the first PC5 RLC channel;

[0163] The first PC5 RLC channel is a PC5 RLC channel between the first relay terminal and the first parent node.

[0164] In this embodiment, the first relay terminal receives the first configuration information sent by the network side device, so that the network side can configure the bearer and mapping relationship of the remote terminal for the first relay terminal, so that the first relay terminal can transmit the information transmitted between the terminal and the network side device according to the configuration of the network side.

[0165] It should be noted that the structure of a multi-hop relay link is relatively complex, and the establishment process of a one-hop relay link in the related technology cannot be directly reused. The embodiment of the present application redesigns the connection establishment process for a multi-hop relay link to avoid the remote terminal being unable to find a suitable relay terminal to connect to the network side device due to the remote terminal being able to connect to the network side device only through one relay terminal, thereby improving the communication performance between the remote terminal and the network side device.

[0166] Referring to FIG. 4 , FIG. 4 is a flow chart of an information sending method provided in an embodiment of the present application. As shown in FIG. 4 , the information sending method includes the following steps:

[0167] Step 201: A second relay terminal receives target information sent by a remote terminal through a first child node, where the first child node is a relay terminal connected to the second relay terminal in a relay link and located between the second relay terminal and the remote terminal.

[0168] Step 202: The second relay terminal sends the target information to the network side device;

[0169] The second relay terminal is connected to the network side device, and the relay link is a relay link between the remote terminal and the network side device.

[0170] Optionally, before the second relay terminal receives the target information sent by the remote terminal through the first subnode, the method further includes at least one of the following:

[0171] The second relay terminal receives a first discovery message sent by the first sub-node;

[0172] The second relay terminal sends a first response message to the first sub-node, where the first response message carries routing information of the relay link.

[0173] Optionally, before the second relay terminal receives the target information sent by the remote terminal through the first subnode, the method further includes at least one of the following:

[0174] The second relay terminal sends a second discovery message;

[0175] The second relay terminal receives a second response message sent by the first sub-node, where the second response message carries routing information of the relay link.

[0176] Optionally, the method further includes:

[0177] When the first sub-node is in a non-connected state, the second relay terminal receives a third message sent by the first sub-node, where the third message is an end-to-end message between the first sub-node and the network-side device.

[0178] The counterpart of the third message may be the network side device.

[0179] Optionally, after the second relay terminal receives the third message sent by the first subnode, the method further includes:

[0180] When the second relay terminal is in an unconnected state, the second relay terminal initiates entry into a connected state; or, when the second relay terminal is in a connected state, the second relay terminal sends a third relay request to the network side device through an RRC process;

[0181] The third relay request includes at least one of the following:

[0182] Remote terminal identification;

[0183] First child node identifier;

[0184] Multi-hop relay link indication;

[0185] routing information of the relay link stored by the second relay terminal;

[0186] Indication information indicating the number of relay terminals included in the routing information of the relay link stored by the second relay terminal.

[0187] The remote terminal identifier may identify the identity of the remote terminal. The routing information of the relay link stored by the second relay terminal may include routing information between the first child node and the network-side device. The number of relay terminals included in the routing information of the relay link stored by the first relay terminal may include the number of relay terminals included in the routing information between the first child node and the network-side device.

[0188] Optionally, after the second relay terminal initiates entering the connected state, the method further includes:

[0189] When the second relay terminal enters the connected state, the second relay terminal sends a third relay request to the network side device through the RRC process.

[0190] Optionally, after the second relay terminal sends a third relay request to the network-side device through an RRC process, the method further includes at least one of the following:

[0191] The second relay terminal receives an RRC response message corresponding to the third message sent by the network side device;

[0192] The second relay terminal sends an RRC response message corresponding to the third message to the first sub-node through the PC5 RLC channel.

[0193] Optionally, after the second relay terminal sends a third relay request to the network side device through an RRC process, the method further includes:

[0194] The second relay terminal receives second configuration information sent by the network side device;

[0195] The second configuration information is used to configure at least one of the following:

[0196] The local identifier of the first child node; Uu RLC channel; a mapping relationship between E2E SRB0 or ​​E2E SRB1 of the first child node and the Uu RLC channel;

[0197] The local identifier of the first sub-node is used to identify data of the first sub-node in the Uu RLC channel;

[0198] The Uu RLC channel is a Uu RLC channel between the second relay terminal and the network side device.

[0199] Optionally, before the second relay terminal receives the target information sent by the remote terminal through the first sub-node, the method further includes:

[0200] The second relay terminal receives third configuration information sent by the network side device;

[0201] The third configuration information is used to configure at least one of the following:

[0202] The local identifier of the remote terminal; the Uu RLC channel; the mapping relationship between the E2E SRB0 or ​​E2E SRB1 of the remote terminal and the Uu RLC channel;

[0203] The local identifier of the remote terminal is used to identify data of the remote terminal in the Uu RLC channel;

[0204] The Uu RLC channel is a Uu RLC channel between the second relay terminal and the network side device.

[0205] It should be noted that this embodiment is an implementation of the second relay terminal corresponding to the embodiment shown in Figure 3. Its same or corresponding implementation can refer to the relevant description of the embodiment shown in Figure 3. To avoid repetition, this embodiment will not be repeated.

[0206] 5 , which is a flow chart of a method for sending information provided by an embodiment of the present application. As shown in FIG5 , the method for sending information includes the following steps:

[0207] Step 301: A third relay terminal receives target information sent by a remote terminal through a second child node, where the second child node is a relay terminal connected to the third relay terminal in a relay link and located between the third relay terminal and the remote terminal.

[0208] Step 302: The third relay terminal sends the target information to the network-side device through a second parent node, where the second parent node is a relay terminal connected to the third relay terminal in the relay link and located between the third relay terminal and the network-side device.

[0209] The relay link is a relay link between the remote terminal and the network side device.

[0210] Optionally, before the third relay terminal receives the target information sent by the remote terminal through the second sub-node, the method further includes at least one of the following:

[0211] The third relay terminal receives the first discovery message sent by the second sub-node, adds the device identifier of the third relay terminal to the routing information carried in the first discovery message, and sends the first discovery message after the addition;

[0212] The third relay terminal receives a first response message sent by the second parent node;

[0213] The third relay terminal sends a first response message to the second sub-node;

[0214] The first response message carries the routing information of the relay link.

[0215] Optionally, before the third relay terminal receives the target information sent by the remote terminal through the second sub-node, the method further includes at least one of the following:

[0216] The third relay terminal receives the second discovery message sent by the second parent node, adds the device identifier of the third relay terminal to the routing information carried in the second discovery message, and sends the added second discovery message;

[0217] The third relay terminal receives a second response message sent by the second sub-node;

[0218] The third relay terminal sends a second response message to the second parent node;

[0219] The second response message carries the routing information of the relay link.

[0220] Optionally, the method further includes:

[0221] A PC5 link connection is established between the third relay terminal and the second parent node through a DCR process; or a PC5 link connection is established between the third relay terminal and the second child node through a DCR process.

[0222] Optionally, the method further includes:

[0223] When the second sub-node is in a non-connected state, the third relay terminal receives a fourth message sent by the second sub-node, where the fourth message is an end-to-end message between the second sub-node and the network-side device.

[0224] The counterpart of the fourth message may be the network side device.

[0225] Optionally, after the third relay terminal receives the fourth message sent by the second sub-node, the method further includes:

[0226] When the third relay terminal is in an unconnected state, the third relay terminal initiates entry into a connected state; or, when the third relay terminal is in a connected state, the third relay terminal sends a fourth relay request to the network side device through an RRC process;

[0227] The fourth relay request includes at least one of the following:

[0228] Remote terminal identification;

[0229] Second child node identifier;

[0230] Multi-hop relay link indication;

[0231] routing information of the relay link stored by the third relay terminal;

[0232] Indication information indicating the number of relay terminals included in the routing information of the relay link stored by the third relay terminal.

[0233] The remote terminal identifier may identify the identity of the remote terminal. The routing information of the relay link stored by the third relay terminal may include routing information between the second child node and the network-side device. The number of relay terminals included in the routing information of the relay link stored by the third relay terminal may include the number of relay terminals included in the routing information between the second child node and the network-side device.

[0234] Optionally, the third relay terminal initiates entering a connected state, including at least one of the following:

[0235] The third relay terminal sends a fifth message to the second parent node, where the fifth message is an end-to-end message between the third relay terminal and the network-side device;

[0236] The third relay terminal receives an RRC response message corresponding to the fifth message sent by the second parent node;

[0237] The method further comprises:

[0238] The third relay terminal sends a fourth relay request to the network side device through the RRC process.

[0239] Among them, the counterpart of the fifth message may be the network side device.

[0240] Optionally, the fifth message is used to: when the second parent node is in a non-connected state, trigger the second parent node to initiate entry into a connected state; or, when the second parent node is in a connected state, trigger the second parent node to send a fifth relay request to the network side device through the RRC process.

[0241] The fifth relay request includes at least one of the following:

[0242] Remote terminal identification;

[0243] an identifier of the third relay terminal;

[0244] Multi-hop relay link indication;

[0245] Routing information of the relay link stored by the second parent node;

[0246] Indication information indicating the number of relay terminals included in the routing information of the relay link stored by the second parent node.

[0247] Optionally, after the third relay terminal sends a fourth relay request to the network-side device through an RRC process, the method further includes at least one of the following:

[0248] The third relay terminal receives an RRC response message corresponding to the fourth message sent by the network side device;

[0249] The third relay terminal sends an RRC response message corresponding to the fourth message to the second sub-node through the PC5 RLC channel.

[0250] Optionally, after the third relay terminal sends a fourth relay request to the network side device through an RRC process, the method further includes:

[0251] The third relay terminal receives fourth configuration information sent by the network side device;

[0252] The fourth configuration information is used to configure at least one of the following:

[0253] The local identifier of the second child node; the second PC5 RLC channel; the mapping relationship between the E2E SRB0 or ​​E2E SRB1 of the second child node and the second PC5 RLC channel;

[0254] The local identifier of the second sub-node is used to identify the data of the remote terminal in the second PC5 RLC channel;

[0255] The second PC5 RLC channel is a PC5 RLC channel between the third relay terminal and the second parent node.

[0256] Optionally, before the third relay terminal sends the target information to the network-side device through the second parent node, the method further includes:

[0257] The third relay terminal receives fifth configuration information sent by the network side device;

[0258] The fifth configuration information is used to configure at least one of the following:

[0259] The local identifier of the remote terminal; the second PC5 RLC channel; the mapping relationship between the E2E SRB0 or ​​E2E SRB1 of the remote terminal and the second PC5 RLC channel;

[0260] The local identifier of the remote terminal is used to identify data of the remote terminal in the second PC5 RLC channel;

[0261] The second PC5 RLC channel is a PC5 RLC channel between the third relay terminal and the second parent node.

[0262] It should be noted that this embodiment is an implementation of the third relay terminal corresponding to the embodiment shown in Figure 3. Its same or corresponding implementation can refer to the relevant description of the embodiment shown in Figure 3. To avoid repetition, this embodiment will not be repeated.

[0263] 6 , which is a flow chart of a method for sending information provided by an embodiment of the present application. As shown in FIG6 , the method for sending information includes the following steps:

[0264] Step 401: The remote terminal sends target information to the network side device through at least two relay terminals;

[0265] The relay link between the remote terminal and the network side device includes the at least two relay terminals, and the at least two relay terminals include a first relay terminal connected to the remote terminal and a second relay terminal connected to the network side device.

[0266] Optionally, before the remote terminal sends the target information to the network-side device through the at least two relay terminals, the method further includes at least one of the following:

[0267] The remote terminal sends a first discovery message, and receives a first response message sent by the first relay terminal, where the first response message carries routing information of the relay link;

[0268] The remote terminal receives the second discovery message sent by the first relay terminal, and sends a second response message to the first relay terminal, where the second response message carries the routing information of the relay link;

[0269] A PC5 link connection is established between the remote terminal and the first relay terminal through a DCR process.

[0270] Optionally, the method further comprises at least one of the following:

[0271] The remote terminal sends a first message to the first relay terminal, where the first message is an end-to-end message between the remote terminal and the network-side device;

[0272] The remote terminal receives an RRC response message corresponding to the first message sent by the first relay terminal through the PC5 RLC channel.

[0273] It should be noted that this embodiment is an implementation of the remote terminal corresponding to the embodiment shown in Figure 3. Its identical or corresponding implementation can refer to the relevant description of the embodiment shown in Figure 3. To avoid repetition, this embodiment will not be repeated.

[0274] The information sending method provided by the embodiment of the present application is described below through several specific embodiments:

[0275] In the following embodiments, the first relay terminal is an access relay UE, the third relay terminal is an intermediate relay UE, the second relay terminal is a donor relay UE, and the network-side device is a gNB.

[0276] The embodiments of this application mainly solve the problem of establishing a multi-hop U2N relay link, which may include the following contents:

[0277] Before the remote UE performs the signaling process for establishing a multi-hop U2N link, it must first establish the overall multi-hop routing through a hop-by-hop discovery process, a hop-by-hop Direct Communication Request (DCR) process, or even an end-to-end DCR process. For example, the path from remote UE to relay UE1 to relay UE2 to gNB is determined, providing the prerequisite for subsequent connection establishment.

[0278] The remote UE initiates end-to-end signaling of a connection establishment request to the network side through the first relay UE (access relay UE). This signaling is sent through the default PC5 Radio Link Control (RLC) channel between the remote UE and the access relay UE, such as SL RLC 0.

[0279] After the access relay UE receives the end-to-end connection establishment request message, if the UE is in the RRC CONNECTED state, it directly reports the relay requirement, such as the remote UE identifier (ID), and carries its own position in the relay link (e.g., the first hop) to the network. The network establishes or configures the mapping of the RLC channel for the SRB0 message of the remote UE to transmit the end-to-end connection establishment message of the remote UE; or, if the UE is in the non-RRC CONNECTED state, it first performs the RRC connection state transition to its parent relay UE, which also initiates the end-to-end establishment process with the network side, first enters the connected state, and then reports the relay requirement and the remote UE ID to the network, carrying its own position in the relay link (e.g., the first hop). The network establishes or configures the mapping of the RLC channel for the SRB0 message of the remote UE to transmit the end-to-end connection establishment message of the remote UE.

[0280] When the access relay UE is in the connected state, its parent relay UE should enter the connected state in advance. This is equivalent to the request process for each downstream UE to enter the connected state, which first triggers its own parent node to enter the connected state. Only then can it support the end-to-end establishment process between the child node and the network node, thereby allowing the child node to enter the connected state.

[0281] Example 1: Discovery / DCR process

[0282] This embodiment establishes a multi-hop U2N relay link. However, prior to this establishment, a hop-by-hop discovery process, a hop-by-hop Direct Communication Request (DCR) process, or even an end-to-end DCR process, is required to determine the routing of the multi-hop U2N relay link. Specifically, this process determines the sequence of relay UEs through which the remote UE accesses the network. This embodiment provides a brief description of the multi-hop link discovery and DCR processes to ensure smooth execution and integration of subsequent processes.

[0283] Figure 7 illustrates a typical multi-hop U2N link. The remote UE is the actual service demander, while the gNB is the network node with which the remote UE establishes a connection and communicates. Other relay UEs facilitate communication between the remote UE and the gNB. The number of these relay nodes is two or more, forming a multi-hop scenario. The interface between two adjacent UEs is the PC5 / SL interface, and the interface between the UE and the gNB is the Uu interface.

[0284] For ease of description, a relay directly connected to a remote UE is defined as an access relay UE, a relay directly connected to a gNB via the Uu interface is defined as a donor relay UE, and an intermediate relay UE is defined as a relay between the two. In a multi-hop U2N link, both access relay UEs and donor relay UEs are mandatory, and the number of intermediate relay UEs ranges from 0 to N.

[0285] In addition, due to the special characteristics of the U2N link, the gNB is the global control node and has control over configuration and resources. Therefore, the direction close to the gNB is the upstream direction, and the direction away from the gNB is the downstream direction. Between two adjacent UE nodes, the one close to the gNB is the parent node, and the one away from the gNB is the child node.

[0286] Before a remote UE establishes a connection with a gNB via a multi-hop U2N relay link, it must first determine the routing of the multi-hop U2N link. Specifically, the remote UE must locate its access relay UE, optional 0-N intermediate relay UEs, and the final donor relay UE, so that it can reach the gNB via the found path.

[0287] The two UEs exchange their needs and capabilities through the discovery and / or DCR process of the PC5 interface, thereby establishing a multi-hop route. A simple example is as follows:

[0288] Example 1: The remote UE sends a discovery message to the surrounding UE, carrying its own needs, such as the hope to communicate with the network for a certain type of business through a multi-hop relay link. The access relay UE receives the discovery message. Since it does not have the conditions to communicate directly with the base station, but can support the multi-hop business according to its capabilities, it helps the remote UE forward the discovery message and adds its own identifier to the routing table. 0-N intermediate relay UEs receive the discovery message and routing table forwarded by the access relay UE in turn. Since they do not have the conditions to communicate directly with the base station, but can continue to support the forwarding of the multi-hop requirements according to their capabilities and business requirements (for example, some businesses have time delay requirements, which cannot exceed 3 hops at most), they continue to help the remote UE forward the discovery message and add their own identifiers to the routing table in turn. Finally, the donor relay The UE receives the discovery message. Since it has the conditions to communicate directly with the base station, for example, RSRP meets certain threshold requirements (such as high threshold and / or low threshold, etc.), it can respond to the discovery message and add its own identifier to the routing table. The complete routing table is carried in the response message, and according to the node information recorded in the routing table in the discovery message, the response message is sent in the reverse direction to the intermediate relay UE of the previous hop. After that, each intermediate relay UE sends the response message step by step according to the routing table. Finally, the access relay UE sends the response message carrying the complete routing table to the remote UE.

[0289] After receiving the response message, the remote UE can determine that the multi-hop relay link can be used for the data transmission it requested. Furthermore, since the discover message is sent in broadcast mode, there may be more than one multi-hop relay link after a discovery process response. The remote UE can select the most suitable one as its final multi-hop relay route, for example, the one that meets at least one of the following conditions: the minimum number of link hops, the shortest response delay, the best overall link quality, or the lightest overall link load.

[0290] After the Discovery process, the remote UE can also establish a PC5 link connection with the access relay UE through the DCR process and inform the access relay UE of the final selected route. The access relay UE then establishes a PC5 link connection with its next hop, the parent node, through the DCR process and informs the parent node of the final routing information. This is performed in sequence. Finally, the donor relay UE also establishes a PC5 connection with its own child node through the DCR process and obtains the routing information.

[0291] Alternatively, the discovery and DCR processes can be combined. This means that the same signaling process completes both route discovery and the step-by-step establishment of PC5 links. This approach reduces signaling latency, but carries the risk that, if a multi-hop path is found, establishing paths other than the final selected path is wasteful.

[0292] The above DCR process establishes a PC5 connection between two adjacent UEs. Furthermore, if necessary, the remote UE can also establish an end-to-end PC5 connection with a non-adjacent node, such as a donor relay UE and / or an intermediate relay UE, through an end-to-end DCR process. The transmission of end-to-end PC5 signaling can reuse the U2U relay architecture and map the end-to-end DCR-related messages to the default RLC channel for relay transmission.

[0293] In Example 2, another discovery and route establishment process can also be initiated by the donor relay UE. Because the donor relay UE communicates directly with the gNB via the Uu interface, it can proactively initiate a discovery process with its surrounding nodes, announcing its ability to support specific services through multi-hop relay donor operations and adding its own identifier to the routing table. Upon receiving this discovery message, the 0-N intermediate relay UEs, each capable of serving as a relay node in a multi-hop relay link based on their services and capabilities, sequentially add their identifiers to the routing table and forward the discovery message. The access relay UE also forwards the message, adding its identifier to the routing table in sequence. Upon receiving the discovery message, the remote UE, having a matching U2N service to initiate, responds to the discovery message. Subsequent responses follow the reverse direction of the routing table, step by step, until the donor relay UE is reached. Thus, the discovery process for a multi-hop U2N route is complete. In particular, when the remote UE has multiple routes to choose from, it can also select the most suitable one as its final multi-hop relay route, for example, the one that meets at least one of the following conditions: minimum link hops, shortest response delay, best overall link quality, or lightest overall link load.

[0294] After route discovery is complete, a DCR process can be performed on each hop to establish a PC5 link connection between each hop. Since the remote UE ultimately selects the route, the remote UE generally initiates a DCR process with the access relay UE to establish a PC5 link connection, then the access relay UE and the first intermediate relay UE initiate a DCR process, and so on, until a PC5 link is established between the donor relay UE and the last intermediate relay UE.

[0295] Similar to Example 1, the discovery process and DCR process can be combined, that is, the same set of signaling processes can complete both route discovery and the step-by-step establishment of PC5 links. Furthermore, if necessary, the remote UE can also establish an end-to-end PC5 connection with non-adjacent nodes, such as donor relay UE and / or intermediate relay UE, through the end-to-end DCR process.

[0296] In particular, the above route discovery and establishment processes are all based on new establishment as an example. In practice, it is not ruled out that some relay UEs have already completed the discovery and establishment process due to the needs of other UEs. Then, when a new remote UE has a need, it can directly respond and complete the incremental establishment.

[0297] For example, if a remote UE 1 has discovered and established a multi-hop relay link, a multi-hop link between two relay nodes of the access relay UE and the donor relay UE, then if a new remote UE 2 has a multi-hop service requirement and conducts a discovery process around it, and the access relay UE and remote UE 2 meet the basic PC5 communication link threshold, the access relay UE can directly respond to remote UE 2 and carry the established routing table. In this way, remote UE 2 quickly completes route discovery and only needs to establish a PC5 link connection with the access relay UE to reuse the existing route and PC5 link to complete the entire discovery and establishment process, greatly shortening the latency. However, the disadvantage of this method is that one node responds on behalf of other nodes in the routing table, and there is a risk that other nodes may be overloaded and unable to support route reuse, resulting in establishment failure.

[0298] Example 2: Connected relay UE

[0299] In Example 1, the route discovery and PC5 link establishment process between the remote UE and the donor relay UE are completed, which are the basis for the remote UE to establish a connection with the base station. In this embodiment, how the remote UE and the base station establish a connection is further described.

[0300] First, in a multi-hop U2N relay route, regardless of the number of relay nodes involved, only the donor relay UE can directly communicate with the gNB via the Uu interface. Other intermediate relay UEs / access relay UEs do not have direct Uu interface links with the gNB. However, because intermediate relay UEs and access relay UEs need to relay data for remote UEs, they also require centralized control by the base station, obtaining configuration or resources from the base station, and centralized bearer configuration and mapping management. Therefore, intermediate relay UEs and access relay UEs also need to enter the connected state, accessing the gNB indirectly (for example, through a donor relay UE), and being controlled and receiving signaling from the gNB.

[0301] Generally speaking, for a child node on a multi-hop relay link to enter the RRC CONNECTED state, it needs to be relayed by its parent node. Therefore, the parent node must first enter the RRC CONNECTED state before it can help the child node enter the RRC CONNECTED state. Therefore, if a relay UE is in the RRC CONNECTED state, it means that its parent node and subsequent parent nodes must also be in the RRC CONNECTED state.

[0302] The simplest scenario is that the donor relay UE has entered the RRC CONNECTED state for other reasons, and the intermediate relay UE and access relay UE have also established indirect connections with the gNB through the donor relay UE due to their own or other remote UEs' needs, and have also entered the RRC CONNECTED state.

[0303] In this scenario, the remote UE sends an end-to-end RRC connection establishment request message to the access relay UE via the PC5 interface between them, with the destination being the gNB. This message is typically carried over the E2E SRB0, which has a default mapping on the PC5 interface. For example, it is mapped to SL RLC 0 (the configuration information of this PC5 RLC channel, including the Logical Channel Identification (LCID), is specified in the protocol). The access relay UE recognizes the data received from the default LCID as an E2E SRB0 message from the remote UE. Therefore, it reports the remote UE's relay request to the network through its own RRC process. Specifically, this message carries the remote UE identifier, indicating that it is a remote UE, and can further indicate that it is a multi-hop remote UE. It can even carry its own stored routing table for the remote UE.

[0304] After receiving the report from the access relay UE, the gNB can configure the bearer and mapping relationship related to the remote UE for the access relay UE based on this information, including at least one of the following:

[0305] (1) Assign a local identifier (i.e., the local identifier of the remote terminal) to the remote UE, the Local UE ID. This identifier is used to distinguish the remote UE's data in an RLC channel on the PC5 interface between the access relay UE and its parent node. The Local UE ID has a small size, for example, 8 bits, which is much smaller than the 24-bit overhead of the remote UE Layer 2 ID. Of course, if an additional short Local UE ID is not allocated, the existing remote UE Layer 2 ID (24 bits) can also be directly used to carry it in the data packet for differentiation;

[0306] (2) Establish a new PC5 RLC channel (i.e., the first PC5 RLC channel) between the access relay UE and its parent node to carry the E2E SRB0 message of the remote UE;

[0307] (3) Use the existing PC5 RLC channel between the access relay UE and its parent node or a newly created PC5 RLC channel to carry the remote UE's E2E SRB0 message and configure the mapping between the remote UE's E2E SRB0 and the PC5 RLC channel;

[0308] Furthermore, since the access relay UE's report can carry complete routing information, the base station can also learn the parent node of the access relay UE, such as the first intermediate relay UE or donor relay UE, and the identity of the relay UE node in the subsequent entire route. As analyzed above, if the access relay UE is in a connected state, then its parent node should also be in a connected state, and the relay UEs in the subsequent entire route are all in a connected state. Therefore, the base station can configure the bearer and mapping relationship of the remote UE for its parent node and each relay UE in the subsequent route. Similarly, the content configured for each subsequent relay node includes at least one of the following:

[0309] (1) Assign a local identifier (i.e., the local identifier of the remote terminal) to the remote UE, the Local UE ID, which is used to distinguish the remote UE's data in an RLC channel of the PC5 interface between the current relay UE and its parent node;

[0310] (2) Establish a new PC5 RLC channel (i.e., a second PC5 RLC channel) between the relay UE and its parent node to carry the E2E SRB0 message of the remote UE;

[0311] (3) Use the existing PC5 RLC channel between the relay UE and its parent node or a newly created PC5 RLC channel to carry the remote UE's E2E SRB0 message and configure the mapping between the remote UE's E2E SRB0 and the PC5 RLC channel.

[0312] In particular, for the donor relay UE, since the configuration it requires is the Uu interface configuration, the content obtained is slightly different from that of other relay UEs, including at least one of the following:

[0313] (1) Assign a local identifier, Local UE ID, to the remote UE. This identifier is used to distinguish the remote UE’s data in an RLC channel of the Uu interface between the current donor relay UE and the gNB.

[0314] (2) Establish a new Uu RLC channel between the donor relay UE and the gNB to carry the remote UE's E2E SRB0 message;

[0315] (3) Use the existing Uu RLC channel between the relay UE and the gNB or create a new Uu RLC channel to carry the remote UE's E2E SRBO message and configure the mapping between the remote UE's E2E SRBO and the Uu RLC channel;

[0316] Through the above process, the gNB configures the transmission channel (PC5 RLC channel and mapping) and identification method (e.g., local UE ID) for the remote UE's E2E SRB0 message on the PC5 interface between each relay UE and its parent node. The Uu RLC channel and local UE ID are also configured on the Uu interface between the donor relay UE and the gNB. Therefore, the remote UE's E2E SRB0 message can smoothly flow from the access relay UE -> intermediate relay UE -> donor relay UE -> gNB. After receiving the RRC Setup Request message, the gNB returns an RRC Setup message to the remote UE. The channel and mapping between the gNB and the access relay UE are the same as those for the uplink E2E SRB0 RRC Setup Request message. Upon reaching the access relay UE, it recognizes the message as an E2E SRB0 DL message for the remote UE and sends it to the remote UE via the default RLC channel between the access relay UE and the remote UE. At this point, the RRC connection establishment between the remote UE and the gNB is completed, and the remote UE enters the connected state. After that, other SRB1 / SRB2 / DRB channels can be established, so that the remote UE can communicate normally with the gNB.

[0317] At each relay UE level, the local UE ID and E2E RB ID are used to identify the remote UE's bearer, enabling multi-hop transmission. This allows for the aggregation of end-to-end bearers from multiple remote UEs into the same RLC channel, reducing relay UE processing complexity and channel overhead. As shown in Figure 8, a multi-hop relay path is established from remote UE1 to access relay UE 3, intermediate relay UE 4, donor relay UE 5, and gNB. A separate multi-hop relay path is established from remote UE2 to access relay UE 4, donor relay UE 5, and gNB. The mapping and identification of each remote UE's E2E RB in each hop's RLC channel are shown in Figure 8. This demonstrates that full channel aggregation significantly reduces the number of channels and processing complexity. Furthermore, the combination of the local ID and E2E RB ID effectively identifies the remote UE and bearer type to which the E2E bearer belongs.

[0318] Furthermore, on the PC5 interface between the remote UE and its access relay UE, only the initial E2E SRB0 and the E2E SRB1 used for recovery failures use the default RLC channel configurations: SL RLC 0 and SL RLC 1, respectively. Other SRBs and DRBs can also be configured and aggregated to specific RLC channels. Figure 8 does not show bearer aggregation between the remote and access nodes to emphasize subsequent routing.

[0319] As shown in Figure 8, when remote UE1 (i.e., remote terminal 1) has established a multi-hop connection, when remote UE2 (i.e., remote terminal 2) initiates it later, the access relay UE4 and donor relay UE5 it can find are in the RRC CONNECTED state, which is just right for executing the end-to-end establishment process in this example.

[0320] Example 3: Non-connected relay UE

[0321] On the basis of completing the route discovery and PC5 link establishment process between the remote UE and the donor relay UE, in this embodiment, another situation of establishing a connection between the remote UE and the base station is further introduced.

[0322] In Example 2, a relatively simple end-to-end connection establishment method is given. Each relay UE has entered the connected state in advance, so it is convenient to report and configure the remote UE's multi-hop request and bearer mapping. However, this scenario is not always met. A more general approach is to assume that the remote UE is the one that initiates the initial connection, such as remote UE 1 in Example 2. At this time, its access relay UE, intermediate relay UE, and donor relay UE are all in a non-connected state. Then how to trigger all relay UEs involved in the route to enter the connected state and configure each transmission path on the network side is a problem that needs to be solved. The process generally includes the following steps:

[0323] Step 0: Complete route discovery and PC5 link establishment between the remote UE and the donor relay UE;

[0324] Step 1: The remote UE sends an end-to-end RRC connection establishment request message with the gNB as the endpoint to the access relay UE via the PC5 interface between the remote UE and the access relay UE.

[0325] This message is typically carried over E2E SRB0. It has a default mapping on the PC5 interface, for example, to SL RLC 0. The access relay UE, upon receiving data from the default LCID, can identify it as an E2E SRB0 message from the remote UE. If the access relay UE is in the disconnected state, it must first enter the connected state.

[0326] Step 2: The access relay UE sends an end-to-end RRC connection establishment request message to its parent node through the PC5 interface with the gNB.

[0327] It should be noted that since route discovery and PC5 connection establishment have been completed in step 0, the access relay UE also knows the routing information between itself and the gNB. For example, it only needs to look up its next-hop parent node in the remote UE's routing table. Therefore, the parent node is already determined.

[0328] Similarly, this message is generally carried by E2E SRB0 and has a default mapping relationship on the PC5 interface. For example, it is mapped to SL RLC 0. When the next-hop parent node receives data from the default LCID, it can identify that this is the E2E SRB0 message of the access relay UE. If the parent node of the access relay UE is in the unconnected state at this time, it must also enter the connected state first.

[0329] Step 3: Each subsequent relay node repeats the process similar to steps 1 and 2, initiating its own transition to the connected state.

[0330] Step 4: When the donor relay UE receives the E2E RRC setup message from its child node, if the donor relay UE itself is not in the connected state, it directly establishes a connection to the gNB through the RACH process and RRC setup process of the Uu interface and enters the RRC connected state;

[0331] Step 5: After the donor relay UE enters the connected state, it can establish SRB1 and perform security activation according to the existing process. It then reports its own child node to the gNB. For example, an intermediate relay UE or access relay UE wants to initiate relay link establishment, so it reports the child node's relay requirements to the network through its own RRC process. Specifically, it carries the child node UE identity to indicate that this is a remote UE (in this case, the child node itself acts as a remote UE to open its own transmission channel).

[0332] Step 6: After receiving the report from the donor relay UE, the gNB can configure the bearer and mapping relationship of the child node for the donor relay UE based on this information, including at least one of the following:

[0333] (1) Assign a local identifier, Local UE ID, to the child node. This identifier is used to distinguish the child node's data in an RLC channel on the Uu interface between the donor relay UE and the gNB.

[0334] (2) Establish a new Uu RLC channel between the donor relay UE and the gNB to carry the E2E SRB0 message of the child node;

[0335] (3) Use the existing Uu RLC channel between the donor relay UE and the gNB or create a new Uu RLC channel to carry the E2E SRBO message of the child node and configure the mapping between the E2E SRBO of the child node and the Uu RLC channel;

[0336] Step 7: After obtaining the E2E SRB0 bearer configuration and local UE ID configuration of the child node, the donor relay UE can forward the E2E SRB0 message of the child node to the gNB through the configured Uu RLC channel.

[0337] Step 8: The gNB receives the E2E SRBO message from the child node and returns an E2E SRBO DL (RRC setup message) using the same Uu RLC channel.

[0338] Step 9: The donor relay UE sends the E2E SRBODL (RRC setup message) to the child node through the default RLC channel between the UE and the child node, such as SL RLC 0.

[0339] Step 10: The donor relay UE's child node receives the end-to-end RRC setup message, which means it enters the connected state and the signaling channel between it and the gNB is established.

[0340] Step 11: After the child node of the donor relay UE in the connected state enters the connected state, it can help its own child node enter the connected state in a similar process to steps 5 to 10;

[0341] By analogy, after entering the connected state, each parent node executes the process between steps 5 and 10 to help its child nodes enter the connected state;

[0342] Take the link from remote UE 1 to access relay UE 2 to intermediate relay UE 3 to donor relay UE 4 to gNB as an example:

[0343] (1) Remote UE 1->access relay UE 2 sends an E2E SRB 0 message, triggering access relay UE 2 to initiate and enter the connected state;

[0344] (2) Then, access relay UE2 sends its own E2E SRB 0 message to intermediate relay UE3, triggering intermediate relay UE3 to initiate entry into the connected state;

[0345] (3) Then, intermediate relay UE 3 sends its own E2E SRB 0 message to donor relay UE 4, triggering donor relay UE 4 to initiate entry into the connected state;

[0346] (4) Donor relay UE 4 has an available Uu interface, so it can enter the connected state using the usual UE method and obtain SRB1 configuration and security activation. Donor relay UE 4 also reports to the gNB that intermediate relay UE 3 wishes to establish a relay link through itself as a remote UE. In this case, it is a one-hop relay link, so it reports the intermediate relay UE 3 ID (Layer 2 ID) and the remote UE identity. After reporting, the donor relay UE can obtain the bearer configuration and mapping configuration, the intermediate relay UE 3 local UE ID from the gNB, and forward the first UL SRB0 RRC setup request message for the intermediate relay UE 3.

[0347] (5) The network sends an UL SRB0 RRC setup message to intermediate relay UE 3 via the same path as the UL SRB0 RRC setup request message sent by intermediate relay UE 3. Intermediate relay UE 3 enters the connected state and obtains SRB1 configuration and security activation. Intermediate relay UE 3 then reports to the gNB that access relay UE 2 wishes to establish a relay link with itself as the remote UE. This is a two-hop relay link. Therefore, in addition to reporting access relay UE 2 (Layer 2 ID) and the remote UE identity, it can also indicate that this is a multi-hop relay link request and carries the routing information between access relay UE 2 and the gNB. After reporting, intermediate relay UE 3 obtains the bearer configuration and mapping configuration, access relay UE 2 local UE ID, and can forward the first UL SRB0 RRC setup request message for access relay UE 2.

[0348] (6) The network sends an UL SRB0 RRC setup message to access relay UE 2 through the same path as the UL SRB0 RRC setup request of access relay UE 2. Access relay UE 2 enters the connected state and obtains SRB1 configuration and security activation. Access relay UE 2 also reports to the gNB that remote UE 1 wishes to establish a relay link as a remote UE. This is a three-hop relay link. Therefore, in addition to reporting the remote UE 1 ID (Layer 2 In addition to the local UE ID and remote UE identity, the access relay UE 2 may also indicate that this is a multi-hop relay link request and carry routing information between remote UE 1 and the gNB. After reporting, access relay UE 2 obtains the bearer configuration and mapping configuration, as well as remote UE 1's local UE ID, and can forward the first UL SRB0 RRC setup request message to remote UE 1.

[0349] (7) The network sends a UL SRB0 RRC setup message to remote UE 1 through the same path as the UL SRB0 RRC setup request of remote UE 1. Remote UE 1 enters the connected state and obtains SRB1 configuration and security activation. Subsequently, the remote UE can directly communicate with the gNB to obtain subsequent DRB configuration and data transmission.

[0350] In the above process, it is assumed that each relay node needs to be triggered to enter the connected state. If a relay UE at a certain level is already in the connected state, the step of entering the connected state can be omitted and the needs of the child node can be directly reported to help the child node enter the connected state.

[0351] The embodiments of the present application are not limited to NR Uu and sidelink (SL), and can be extended to other different versions.

[0352] The embodiment of the present application provides a method for establishing a multi-hop U2N relay link, which enables a remote UE to establish a connection with the network through a multi-hop relay path, ensuring the feasibility and efficiency of transmission, expanding coverage, and reducing UE complexity and improving system efficiency while ensuring transmission effect.

[0353] The information sending method provided in the embodiment of the present application can be executed by an information sending device. In the embodiment of the present application, the information sending device provided in the embodiment of the present application is described by taking the information sending method executed by the information sending device as an example.

[0354] Please refer to FIG. 9 , which is a structural diagram of an information sending device provided in an embodiment of the present application. The first relay terminal includes the information sending device. As shown in FIG. 9 , the information sending device 500 includes:

[0355] The first receiving module 501 is configured to receive target information sent by a remote terminal;

[0356] a sending module 502 configured to send the target information to a network-side device through a first parent node, where the first parent node is a relay terminal connected to the first relay terminal in a relay link and located between the first relay terminal and the network-side device;

[0357] The first relay terminal is connected to the remote terminal, and the relay link is a relay link between the remote terminal and the network side device.

[0358] Optionally, the device further includes a first transceiver module, configured to:

[0359] receiving a first discovery message sent by the remote terminal, adding the device identifier of the first relay terminal to the routing information carried in the first discovery message, and sending the first discovery message after the addition;

[0360] receiving a first response message sent by the first parent node;

[0361] Sending a first response message to the remote terminal;

[0362] The first response message carries the routing information of the relay link.

[0363] Optionally, the device further includes a second transceiver module, configured to:

[0364] receiving a second discovery message sent by the first parent node, adding the device identifier of the first relay terminal to the routing information carried in the second discovery message, and sending the added second discovery message;

[0365] receiving a second response message sent by the remote terminal;

[0366] Sending a second response message to the first parent node;

[0367] The second response message carries the routing information of the relay link.

[0368] Optionally, the device further comprises:

[0369] A second receiving module is configured to receive a first message sent by the remote terminal, where the first message is an end-to-end message between the remote terminal and the network-side device;

[0370] a processing module, configured to, when the first relay terminal is in a non-connected state, initiate entry into a connected state; or, when the first relay terminal is in a connected state, send a first relay request to the network side device through an RRC process;

[0371] The first relay request includes at least one of the following:

[0372] Remote terminal identification;

[0373] Multi-hop relay link indication;

[0374] routing information of the relay link stored by the first relay terminal;

[0375] Indication information indicating the number of relay terminals included in the routing information of the relay link stored in the first relay terminal.

[0376] Optionally, the initiating entry into the connected state includes at least one of the following:

[0377] Sending a second message to the first parent node, where the second message is an end-to-end message between the first relay terminal and the network-side device;

[0378] receiving an RRC response message corresponding to the second message sent by the first parent node;

[0379] The device further comprises:

[0380] A sending module is used to send a first relay request to the network side device through an RRC process.

[0381] Optionally, the second message is used to: when the first parent node is in a non-connected state, trigger the first parent node to initiate entry into a connected state; or, when the first parent node is in a connected state, trigger the first parent node to send a second relay request to the network side device through the RRC process.

[0382] Optionally, the apparatus further includes a third transceiver module, configured to perform at least one of the following:

[0383] Receiving an RRC response message corresponding to the first message sent by the network side device;

[0384] The RRC response message corresponding to the first message is sent to the remote terminal through the PC5 radio link control RLC channel.

[0385] Optionally, the device further comprises:

[0386] A third receiving module is used to receive the first configuration information sent by the network side device;

[0387] The first configuration information is used to configure at least one of the following:

[0388] The local identifier of the remote terminal; the first PC5 RLC channel; the mapping relationship between the E2E SRB0 or ​​E2ESRB1 of the remote terminal and the first PC5 RLC channel;

[0389] The local identifier of the remote terminal is used to identify data of the remote terminal in the first PC5 RLC channel;

[0390] The first PC5 RLC channel is a PC5 RLC channel between the first relay terminal and the first parent node.

[0391] The information sending device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal, or it can be other devices other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0392] The information sending device provided in the embodiment of the present application can implement the various processes implemented in the method embodiment of Figure 3 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0393] Please refer to FIG. 10 , which is a structural diagram of an information sending device provided in an embodiment of the present application. The second relay terminal includes the information sending device. As shown in FIG. 10 , the information sending device 600 includes:

[0394] A first receiving module 601 is configured to receive target information sent by a remote terminal through a first sub-node, where the first sub-node is a relay terminal connected to the second relay terminal in a relay link and located between the second relay terminal and the remote terminal;

[0395] A first sending module 602 is configured to send the target information to a network-side device;

[0396] The second relay terminal is connected to the network side device, and the relay link is a relay link between the remote terminal and the network side device.

[0397] Optionally, the device further includes a first transceiver module, configured to:

[0398] receiving a first discovery message sent by the first subnode;

[0399] A first response message is sent to the first sub-node, where the first response message carries routing information of the relay link.

[0400] Optionally, the device further includes a second transceiver module, configured to:

[0401] Sending a second discovery message;

[0402] A second response message sent by the first sub-node is received, where the second response message carries routing information of the relay link.

[0403] Optionally, the device further comprises:

[0404] The second receiving module is configured to receive a third message sent by the first sub-node when the first sub-node is in a non-connected state, where the third message is an end-to-end message between the first sub-node and the network-side device.

[0405] Optionally, the device further comprises:

[0406] a processing module, configured to initiate entry into a connected state when the second relay terminal is in an unconnected state; or, when the second relay terminal is in a connected state, send a third relay request to the network side device through an RRC process;

[0407] The third relay request includes at least one of the following:

[0408] Remote terminal identification;

[0409] First child node identifier;

[0410] Multi-hop relay link indication;

[0411] routing information of the relay link stored by the second relay terminal;

[0412] Indication information indicating the number of relay terminals included in the routing information of the relay link stored by the second relay terminal.

[0413] Optionally, the device further comprises:

[0414] The second sending module is used to send a third relay request to the network side device through the RRC process when the second relay terminal enters the connected state.

[0415] Optionally, the apparatus further includes a third transceiver module, configured to perform at least one of the following:

[0416] Receiving an RRC response message corresponding to the third message sent by the network side device;

[0417] Send an RRC response message corresponding to the third message to the first subnode through the PC5 RLC channel.

[0418] Optionally, the device further comprises:

[0419] A third receiving module is used to receive the second configuration information sent by the network side device;

[0420] The second configuration information is used to configure at least one of the following:

[0421] The local identifier of the first child node; Uu RLC channel; the mapping relationship between E2E SRB0 or ​​E2ESRB1 of the first child node and the Uu RLC channel;

[0422] The local identifier of the first sub-node is used to identify data of the first sub-node in the Uu RLC channel;

[0423] The Uu RLC channel is a Uu RLC channel between the second relay terminal and the network side device.

[0424] Optionally, the device further comprises:

[0425] a fourth receiving module, configured to receive third configuration information sent by the network side device;

[0426] The third configuration information is used to configure at least one of the following:

[0427] The local identifier of the remote terminal; the Uu RLC channel; the mapping relationship between the E2E SRB0 or ​​E2E SRB1 of the remote terminal and the Uu RLC channel;

[0428] The local identifier of the remote terminal is used to identify data of the remote terminal in the Uu RLC channel;

[0429] The Uu RLC channel is a Uu RLC channel between the second relay terminal and the network side device.

[0430] The information sending device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal, or it can be other devices other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0431] The information sending device provided in the embodiment of the present application can implement the various processes implemented in the method embodiment of Figure 4 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0432] Please refer to FIG. 11 , which is a structural diagram of an information sending device provided in an embodiment of the present application. The third relay terminal includes the information sending device. As shown in FIG. 11 , the information sending device 500 includes:

[0433] A first receiving module 701 is configured to receive target information sent by a remote terminal through a second child node, where the second child node is a relay terminal connected to the third relay terminal in a relay link and located between the third relay terminal and the remote terminal;

[0434] a sending module 702, configured to send the target information to a network-side device through a second parent node, where the second parent node is a relay terminal connected to the third relay terminal in the relay link and located between the third relay terminal and the network-side device;

[0435] The relay link is a relay link between the remote terminal and the network side device.

[0436] Optionally, the device further includes a first transceiver module, configured to:

[0437] receiving a first discovery message sent by the second sub-node, adding the device identifier of the third relay terminal to the routing information carried in the first discovery message, and sending the first discovery message after the addition;

[0438] receiving a first response message sent by the second parent node;

[0439] Sending a first response message to the second sub-node;

[0440] The first response message carries the routing information of the relay link.

[0441] Optionally, the device further includes a second transceiver module, configured to:

[0442] receiving a second discovery message sent by the second parent node, adding the device identifier of the third relay terminal to the routing information carried in the second discovery message, and sending the second discovery message after the addition;

[0443] receiving a second response message sent by the second sub-node;

[0444] Sending a second response message to the second parent node;

[0445] The second response message carries the routing information of the relay link.

[0446] Optionally, the device further comprises:

[0447] An establishing module is used to establish a PC5 link connection between the third relay terminal and the second parent node through a DCR process; or to establish a PC5 link connection between the third relay terminal and the second child node through a DCR process.

[0448] Optionally, the device further comprises:

[0449] The second receiving module is configured to receive a fourth message sent by the second sub-node when the second sub-node is in a non-connected state, where the fourth message is an end-to-end message between the second sub-node and the network-side device.

[0450] Optionally, the device further comprises:

[0451] a processing module, configured to, when the third relay terminal is in an unconnected state, initiate entry into a connected state; or, when the third relay terminal is in a connected state, send a fourth relay request to the network side device through an RRC process;

[0452] The fourth relay request includes at least one of the following:

[0453] Remote terminal identification;

[0454] Second child node identifier;

[0455] Multi-hop relay link indication;

[0456] routing information of the relay link stored by the third relay terminal;

[0457] Indication information indicating the number of relay terminals included in the routing information of the relay link stored by the third relay terminal.

[0458] Optionally, the third relay terminal initiates entering a connected state, including at least one of the following:

[0459] The third relay terminal sends a fifth message to the second parent node, where the fifth message is an end-to-end message between the third relay terminal and the network-side device;

[0460] The third relay terminal receives an RRC response message corresponding to the fifth message sent by the second parent node;

[0461] The method further comprises:

[0462] The third relay terminal sends a fourth relay request to the network side device through the RRC process.

[0463] Optionally, the fifth message is used to: when the second parent node is in a non-connected state, trigger the second parent node to initiate entry into a connected state; or, when the second parent node is in a connected state, trigger the second parent node to send a fifth relay request to the network side device through the RRC process.

[0464] Optionally, the apparatus further includes a third transceiver module, configured to perform at least one of the following:

[0465] Receiving an RRC response message corresponding to the fourth message sent by the network side device;

[0466] Send an RRC response message corresponding to the fourth message to the second sub-node through the PC5 RLC channel.

[0467] Optionally, after the third relay terminal sends a fourth relay request to the network side device through an RRC process, the apparatus further includes:

[0468] A third receiving module, configured to receive fourth configuration information sent by the network side device;

[0469] The fourth configuration information is used to configure at least one of the following:

[0470] The local identifier of the second child node; the second PC5 RLC channel; the mapping relationship between the E2E SRB0 or ​​E2E SRB1 of the second child node and the second PC5 RLC channel;

[0471] The local identifier of the second sub-node is used to identify the data of the remote terminal in the second PC5 RLC channel;

[0472] The second PC5 RLC channel is a PC5 RLC channel between the third relay terminal and the second parent node.

[0473] Optionally, the device further comprises:

[0474] a fourth receiving module, configured to receive fifth configuration information sent by the network side device;

[0475] The fifth configuration information is used to configure at least one of the following:

[0476] The local identifier of the remote terminal; the second PC5 RLC channel; the mapping relationship between the E2E SRB0 or ​​E2ESRB1 of the remote terminal and the second PC5 RLC channel;

[0477] The local identifier of the remote terminal is used to identify data of the remote terminal in the second PC5 RLC channel;

[0478] The second PC5 RLC channel is a PC5 RLC channel between the third relay terminal and the second parent node.

[0479] The information sending device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal, or it can be other devices other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0480] The information sending device provided in the embodiment of the present application can implement the various processes implemented in the method embodiment of Figure 5 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0481] Please refer to FIG. 12 , which is a structural diagram of an information sending device provided in an embodiment of the present application. The remote terminal includes the information sending device. As shown in FIG. 12 , the information sending device 800 includes:

[0482] A sending module 801 is configured to send target information to a network-side device via at least two relay terminals;

[0483] The relay link between the remote terminal and the network side device includes the at least two relay terminals, and the at least two relay terminals include a first relay terminal connected to the remote terminal and a second relay terminal connected to the network side device.

[0484] Optionally, the device further comprises a processing module, configured to perform at least one of the following:

[0485] Sending a first discovery message, and receiving a first response message sent by the first relay terminal, where the first response message carries routing information of the relay link;

[0486] receiving a second discovery message sent by the first relay terminal, and sending a second response message to the first relay terminal, where the second response message carries routing information of the relay link;

[0487] A PC5 link connection is established with the first relay terminal through a DCR process.

[0488] Optionally, the device further includes a transceiver module, configured to:

[0489] Sending a first message to the first relay terminal, where the first message is an end-to-end message between the remote terminal and the network-side device;

[0490] An RRC response message corresponding to the first message sent by the first relay terminal is received through the PC5 RLC channel.

[0491] The information sending device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal, or it can be other devices other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0492] The information sending device provided in the embodiment of the present application can implement the various processes implemented in the method embodiment of Figure 6 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0493] As shown in Figure 13, an embodiment of the present application also provides a communication device 900, including a processor 901 and a memory 902, and the memory 902 stores a program or instruction that can be run on the processor 901. When the program or instruction is executed by the processor 901, the various steps of the above-mentioned information sending method embodiment are implemented and the same technical effect can be achieved.

[0494] The present application also provides a terminal including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiments shown in Figures 3, 4, 5, or 6. This terminal embodiment corresponds to the aforementioned terminal-side method embodiment, and each implementation process and implementation method of the aforementioned method embodiment can be applied to this terminal embodiment and achieve the same technical effects. Specifically, Figure 14 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0495] The terminal 1000 includes but is not limited to: a radio frequency unit 1001, a network module 1002, an audio output unit 1003, an input unit 1004, a sensor 1005, a display unit 1006, a user input unit 1007, an interface unit 1008, a memory 1009 and at least some of the components of the processor 1010.

[0496] Those skilled in the art will appreciate that the terminal 1000 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 1010 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG14 does not limit the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be described in detail here.

[0497] It should be understood that in an embodiment of the present application, the input unit 1004 may include a graphics processing unit (GPU) 10041 and a microphone 10042, and the graphics processor 10041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1006 may include a display panel 10061, and the display panel 10061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1007 includes a touch panel 10071 and at least one of other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 may include two parts: a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and an operating stick, which will not be repeated here.

[0498] In the embodiment of the present application, after receiving downlink data from a network-side device, the RF unit 1001 may transmit the data to the processor 1010 for processing. Furthermore, the RF unit 1001 may send uplink data to the network-side device. Typically, the RF unit 1001 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0499] The memory 1009 can be used to store software programs or instructions and various data. The memory 1009 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 1009 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM), and a direct memory bus random access memory (DRRAM). The memory 1009 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0500] Processor 1010 may include one or more processing units. Optionally, processor 1010 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 1010.

[0501] When the terminal is a first relay terminal:

[0502] The radio frequency unit 1001 is used for:

[0503] Receive target information sent by a remote terminal;

[0504] Sending the target information to the network-side device through a first parent node, where the first parent node is a relay terminal connected to the first relay terminal in a relay link and located between the first relay terminal and the network-side device;

[0505] The first relay terminal is connected to the remote terminal, and the relay link is a relay link between the remote terminal and the network side device.

[0506] Optionally, the radio frequency unit 1001 is further configured to perform at least one of the following:

[0507] receiving a first discovery message sent by the remote terminal, adding the device identifier of the first relay terminal to the routing information carried in the first discovery message, and sending the first discovery message after the addition;

[0508] receiving a first response message sent by the first parent node;

[0509] Sending a first response message to the remote terminal;

[0510] The first response message carries the routing information of the relay link.

[0511] Optionally, the radio frequency unit 1001 is further configured to perform at least one of the following:

[0512] receiving a second discovery message sent by the first parent node, adding the device identifier of the first relay terminal to the routing information carried in the second discovery message, and sending the added second discovery message;

[0513] receiving a second response message sent by the remote terminal;

[0514] Sending a second response message to the first parent node;

[0515] The second response message carries the routing information of the relay link.

[0516] Optionally, the radio frequency unit 1001 is further configured to: receive a first message sent by the remote terminal, where the first message is an end-to-end message between the remote terminal and the network-side device;

[0517] The processor 1010 is configured to: when the first relay terminal is in an unconnected state, initiate entry into a connected state; or, when the first relay terminal is in a connected state, send a first relay request to the network side device through an RRC process;

[0518] The first relay request includes at least one of the following:

[0519] Remote terminal identification;

[0520] Multi-hop relay link indication;

[0521] routing information of the relay link stored by the first relay terminal;

[0522] Indication information indicating the number of relay terminals included in the routing information of the relay link stored in the first relay terminal.

[0523] Optionally, the initiating entry into the connected state includes at least one of the following:

[0524] Sending a second message to the first parent node, where the second message is an end-to-end message between the first relay terminal and the network-side device;

[0525] receiving an RRC response message corresponding to the second message sent by the first parent node;

[0526] The device further comprises:

[0527] A sending module is used to send a first relay request to the network side device through an RRC process.

[0528] Optionally, the second message is used to: when the first parent node is in a non-connected state, trigger the first parent node to initiate entry into a connected state; or, when the first parent node is in a connected state, trigger the first parent node to send a second relay request to the network side device through an RRC process.

[0529] Optionally, the radio frequency unit 1001 is further configured to perform at least one of the following:

[0530] Receiving an RRC response message corresponding to the first message sent by the network side device;

[0531] The RRC response message corresponding to the first message is sent to the remote terminal through the PC5 radio link control RLC channel.

[0532] Optionally, the radio frequency unit 1001 is further configured to: receive first configuration information sent by the network side device;

[0533] The first configuration information is used to configure at least one of the following:

[0534] The local identifier of the remote terminal; the first PC5 RLC channel; the mapping relationship between the E2E SRB0 or ​​E2ESRB1 of the remote terminal and the first PC5 RLC channel;

[0535] The local identifier of the remote terminal is used to identify data of the remote terminal in the first PC5 RLC channel;

[0536] The first PC5 RLC channel is a PC5 RLC channel between the first relay terminal and the first parent node.

[0537] In the case where the terminal is a second relay terminal:

[0538] The radio frequency unit 1001 is used for:

[0539] receiving target information sent by a remote terminal through a first child node, where the first child node is a relay terminal connected to the second relay terminal in a relay link and located between the second relay terminal and the remote terminal;

[0540] Sending the target information to the network side device;

[0541] The second relay terminal is connected to the network side device, and the relay link is a relay link between the remote terminal and the network side device.

[0542] Optionally, the radio frequency unit 1001 is further configured to perform at least one of the following:

[0543] receiving a first discovery message sent by the first subnode;

[0544] A first response message is sent to the first sub-node, where the first response message carries routing information of the relay link.

[0545] Optionally, the radio frequency unit 1001 is further configured to perform at least one of the following:

[0546] Sending a second discovery message;

[0547] A second response message sent by the first sub-node is received, where the second response message carries routing information of the relay link.

[0548] Optionally, the radio frequency unit 1001 is further used to: when the first sub-node is in a non-connected state, receive a third message sent by the first sub-node, where the third message is an end-to-end message between the first sub-node and the network side device.

[0549] Optionally, the processor 1010 is configured to: when the second relay terminal is in an unconnected state, initiate entry into a connected state; or, when the second relay terminal is in a connected state, send a third relay request to the network side device through an RRC process;

[0550] The third relay request includes at least one of the following:

[0551] Remote terminal identification;

[0552] First child node identifier;

[0553] Multi-hop relay link indication;

[0554] routing information of the relay link stored by the second relay terminal;

[0555] Indication information indicating the number of relay terminals included in the routing information of the relay link stored by the second relay terminal.

[0556] Optionally, the radio frequency unit 1001 is further configured to: when the second relay terminal enters a connected state, send a third relay request to the network side device through an RRC process.

[0557] Optionally, the radio frequency unit 1001 is further configured to perform at least one of the following:

[0558] Receiving an RRC response message corresponding to the third message sent by the network side device;

[0559] Send an RRC response message corresponding to the third message to the first subnode through the PC5 RLC channel.

[0560] Optionally, the device further comprises:

[0561] The radio frequency unit 1001 is further configured to: receive second configuration information sent by the network side device;

[0562] The second configuration information is used to configure at least one of the following:

[0563] The local identifier of the first child node; Uu RLC channel; the mapping relationship between E2E SRB0 or ​​E2ESRB1 of the first child node and the Uu RLC channel;

[0564] The local identifier of the first sub-node is used to identify data of the first sub-node in the Uu RLC channel;

[0565] The Uu RLC channel is a Uu RLC channel between the second relay terminal and the network side device.

[0566] Optionally, the radio frequency unit 1001 is further configured to: receive third configuration information sent by the network side device;

[0567] The third configuration information is used to configure at least one of the following:

[0568] The local identifier of the remote terminal; the Uu RLC channel; the mapping relationship between the E2E SRB0 or ​​E2E SRB1 of the remote terminal and the Uu RLC channel;

[0569] The local identifier of the remote terminal is used to identify data of the remote terminal in the Uu RLC channel;

[0570] The Uu RLC channel is a Uu RLC channel between the second relay terminal and the network side device.

[0571] In the case where the terminal is a third relay terminal:

[0572] The radio frequency unit 1001 is used for:

[0573] receiving target information sent by a remote terminal through a second child node, where the second child node is a relay terminal connected to the third relay terminal in a relay link and located between the second relay terminal and the remote terminal;

[0574] Sending the target information to the network-side device through a second parent node, where the second parent node is a relay terminal connected to the third relay terminal in the relay link and located between the third relay terminal and the network-side device;

[0575] The relay link is a relay link between the remote terminal and the network side device.

[0576] Optionally, the radio frequency unit 1001 is further configured to perform at least one of the following:

[0577] receiving a first discovery message sent by the second sub-node, adding the device identifier of the third relay terminal to the routing information carried in the first discovery message, and sending the first discovery message after the addition;

[0578] receiving a first response message sent by the second parent node;

[0579] Sending a first response message to the second sub-node;

[0580] The first response message carries the routing information of the relay link.

[0581] Optionally, the radio frequency unit 1001 is further configured to perform at least one of the following:

[0582] receiving a second discovery message sent by the second parent node, adding the device identifier of the third relay terminal to the routing information carried in the second discovery message, and sending the second discovery message after the addition;

[0583] receiving a second response message sent by the second sub-node;

[0584] Sending a second response message to the second parent node;

[0585] The second response message carries the routing information of the relay link.

[0586] Optionally, the processor 1010 is configured to establish a PC5 link connection between the third relay terminal and the second parent node through a DCR process; or to establish a PC5 link connection between the third relay terminal and the second child node through a DCR process.

[0587] Optionally, the radio frequency unit 1001 is further used to: when the second sub-node is in a non-connected state, receive a fourth message sent by the second sub-node, where the fourth message is an end-to-end message between the second sub-node and the network side device.

[0588] Optionally, the processor 1010 is configured to: when the third relay terminal is in an unconnected state, initiate entry into a connected state; or, when the third relay terminal is in a connected state, send a fourth relay request to the network side device through an RRC process;

[0589] The fourth relay request includes at least one of the following:

[0590] Remote terminal identification;

[0591] Second child node identifier;

[0592] Multi-hop relay link indication;

[0593] routing information of the relay link stored by the third relay terminal;

[0594] Indication information indicating the number of relay terminals included in the routing information of the relay link stored by the third relay terminal.

[0595] Optionally, the third relay terminal initiates entering a connected state, including at least one of the following:

[0596] The third relay terminal sends a fifth message to the second parent node, where the fifth message is an end-to-end message between the third relay terminal and the network-side device;

[0597] The third relay terminal receives an RRC response message corresponding to the fifth message sent by the second parent node;

[0598] The method further comprises:

[0599] The third relay terminal sends a fourth relay request to the network side device through the RRC process.

[0600] Optionally, the fifth message is used to: when the second parent node is in a non-connected state, trigger the second parent node to initiate entry into a connected state; or, when the second parent node is in a connected state, trigger the second parent node to send a fifth relay request to the network side device through the RRC process.

[0601] Optionally, the radio frequency unit 1001 is further configured to perform at least one of the following:

[0602] Receiving an RRC response message corresponding to the fourth message sent by the network side device;

[0603] Send an RRC response message corresponding to the fourth message to the second sub-node through the PC5 RLC channel.

[0604] Optionally, the radio frequency unit 1001 is further configured to: receive fourth configuration information sent by the network side device;

[0605] The fourth configuration information is used to configure at least one of the following:

[0606] The local identifier of the second child node; the second PC5 RLC channel; the mapping relationship between the E2E SRB0 or ​​E2E SRB1 of the second child node and the second PC5 RLC channel;

[0607] The local identifier of the second sub-node is used to identify the data of the remote terminal in the second PC5 RLC channel;

[0608] The second PC5 RLC channel is a PC5 RLC channel between the third relay terminal and the second parent node.

[0609] Optionally, the radio frequency unit 1001 is further configured to: receive fifth configuration information sent by the network side device;

[0610] The fifth configuration information is used to configure at least one of the following:

[0611] The local identifier of the remote terminal; the second PC5 RLC channel; the mapping relationship between the E2E SRB0 or ​​E2ESRB1 of the remote terminal and the second PC5 RLC channel;

[0612] The local identifier of the remote terminal is used to identify data of the remote terminal in the second PC5 RLC channel;

[0613] The second PC5 RLC channel is a PC5 RLC channel between the third relay terminal and the second parent node.

[0614] In the case where the terminal is a remote terminal:

[0615] The radio frequency unit 1001 is used for:

[0616] Sending target information to a network-side device through at least two relay terminals;

[0617] The relay link between the remote terminal and the network side device includes the at least two relay terminals, and the at least two relay terminals include a first relay terminal connected to the remote terminal and a second relay terminal connected to the network side device.

[0618] Optionally, the radio frequency unit 1001 is further configured to: send a first discovery message, and receive a first response message sent by the first relay terminal, where the first response message carries routing information of the relay link;

[0619] receiving a second discovery message sent by the first relay terminal, and sending a second response message to the first relay terminal, where the second response message carries routing information of the relay link;

[0620] or

[0621] The processor 1010 is configured to establish a PC5 link connection with the first relay terminal through a DCR process.

[0622] Optionally, the radio frequency unit 1001 is further configured to perform at least one of the following:

[0623] Sending a first message to the first relay terminal, where the first message is an end-to-end message between the remote terminal and the network-side device;

[0624] An RRC response message corresponding to the first message sent by the first relay terminal is received through the PC5 RLC channel.

[0625] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment Figure 3, Figure 4, Figure 5 or Figure 6, and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0626] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned information sending method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0627] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0628] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned information sending method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0629] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0630] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned information sending method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0631] An embodiment of the present application also provides an information sending system, including: a first relay terminal, a second relay terminal, a third relay terminal and a remote terminal, wherein the first relay terminal can be used to execute the steps of the information sending method applied to the first relay terminal as described above, the second relay terminal can be used to execute the steps of the information sending method applied to the second relay terminal as described above, the third relay terminal can be used to execute the steps of the information sending method applied to the third relay terminal as described above, and the remote terminal can be used to execute the steps of the information sending method applied to the remote terminal as described above.

[0632] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0633] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0634] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. An information sending method, comprising: The first relay terminal receives target information sent by a remote terminal; The first relay terminal sends the target information to a network-side device through a first parent node, where the first parent node is a relay terminal in a relay link that is connected to the first relay terminal and is located between the first relay terminal and the network-side device; Wherein, the first relay terminal is connected to the remote terminal, and the relay link is a relay link between the remote terminal and the network-side device.

2. The method according to claim 1, wherein, Before the first relay terminal receives the target information sent by the remote terminal, the method further comprises at least one of the following: The first relay terminal receives a first discovery message sent by the remote terminal, adds the device identifier of the first relay terminal to the routing information carried in the first discovery message, and sends the added first discovery message; The first relay terminal receives a first response message sent by the first parent node; The first relay terminal sends a first response message to the remote terminal; Wherein, the first response message carries the routing information of the relay link.

3. The method according to claim 1, wherein, Before the first relay terminal receives the target information sent by the remote terminal, the method further comprises at least one of the following: The first relay terminal receives a second discovery message sent by the first parent node, adds the device identifier of the first relay terminal to the routing information carried in the second discovery message, and sends the added second discovery message; The first relay terminal receives a second response message sent by the remote terminal; The first relay terminal sends a second response message to the first parent node; Wherein, the second response message carries the routing information of the relay link.

4. The method according to any one of claims 1-3, the method further comprises: The first relay terminal receives a first message sent by the remote terminal, where the first message is an end-to-end message between the remote terminal and the network-side device; When the first relay terminal is in a non-connected state, the first relay terminal initiates entering a connected state; Or, when the first relay terminal is in a connected state, the first relay terminal sends a first relay request to the network-side device through an RRC procedure; Wherein, the first relay request comprises at least one of the following: Remote terminal identifier; Multi-hop relay link indication; The routing information of the relay link stored by the first relay terminal; Indication information indicating the number of relay terminals included in the routing information of the relay link stored by the first relay terminal.

5. The method according to claim 4, wherein The first relay terminal initiates entering a connected state, including at least one of the following: The first relay terminal sends a second message to the first parent node, where the second message is an end-to-end message between the first relay terminal and the network-side device; The first relay terminal receives an RRC response message corresponding to the second message sent by the first parent node; The method further comprises: The first relay terminal sends a first relay request to the network-side device through an RRC procedure.

6. The method according to claim 5, wherein The second message is used for: triggering the first parent node to initiate entering the connected state when the first parent node is in the non-connected state; or, triggering the first parent node to send a second relay request to the network-side device through an RRC procedure when the first parent node is in the connected state.

7. The method according to any one of claims 4-6, wherein, After the first relay terminal sends a first relay request to the network-side device through an RRC procedure, the method further includes at least one of the following: The first relay terminal receives an RRC response message corresponding to the first message sent by the network-side device; The first relay terminal sends the RRC response message corresponding to the first message to the remote terminal through a PC5 radio link control (RLC) channel.

8. The method according to any one of claims 1-7, wherein, Before the first relay terminal receives target information sent by the remote terminal, the method further includes: The first relay terminal receives first configuration information sent by the network-side device; Wherein, the first configuration information is used to configure at least one of the following: The local identifier of the remote terminal; the first PC5 RLC channel; the mapping relationship between the end-to-end signaling radio bearer 0 (E2E SRB0) or end-to-end signaling radio bearer 1 (E2E SRB1) of the remote terminal and the first PC5 RLC channel; Wherein, the local identifier of the remote terminal is used to identify the data of the remote terminal in the first PC5 RLC channel; The first PC5 RLC channel is the PC5 RLC channel between the first relay terminal and the first parent node.

9. An information sending method, including: A second relay terminal receives target information sent by a remote terminal through a first child node, where the first child node is a relay terminal connected to the second relay terminal in a relay link and located between the second relay terminal and the remote terminal; The second relay terminal sends the target information to the network-side device; Wherein, the second relay terminal is connected to the network-side device, and the relay link is the relay link between the remote terminal and the network-side device.

10. The method according to claim 9, wherein, Before the second relay terminal receives target information sent by the remote terminal through the first child node, the method further includes at least one of the following: The second relay terminal receives a first discovery message sent by the first child node; The second relay terminal sends a first response message to the first child node, and the first response message carries the routing information of the relay link.

11. The method according to claim 9, wherein Before the second relay terminal receives target information sent by the remote terminal through the first child node, the method further includes at least one of the following: The second relay terminal sends a second discovery message; The second relay terminal receives a second response message sent by the first child node, and the second response message carries the routing information of the relay link.

12. According to the method according to any one of claims 9-11, the method further includes: When the first child node is in the non-connected state, the second relay terminal receives a third message sent by the first child node, and the third message is an end-to-end message between the first child node and the network-side device.

13. The method according to claim 12, wherein, After the second relay terminal receives the third message sent by the first sub-node, the method further includes: When the second relay terminal is in a non-connected state, the second relay terminal initiates entering the connected state; or, when the second relay terminal is in the connected state, the second relay terminal sends a third relay request to the network-side device through the RRC procedure; Wherein, the third relay request includes at least one of the following: Remote terminal identifier; First sub-node identifier; Multi-hop relay link indication; Routing information of the relay link stored by the second relay terminal; Indication information indicating the number of relay terminals included in the routing information of the relay link stored by the second relay terminal.

14. The method according to claim 13, wherein, After the second relay terminal initiates entering the connected state, the method further includes: When the second relay terminal enters the connected state, the second relay terminal sends a third relay request to the network-side device through the RRC procedure.

15. The method according to claim 13 or 14, wherein, After the second relay terminal sends the third relay request to the network-side device through the RRC procedure, the method further includes at least one of the following: The second relay terminal receives an RRC response message corresponding to the third message sent by the network-side device; The second relay terminal sends an RRC response message corresponding to the third message to the first sub-node through the PC5 RLC channel.

16. The method according to any one of claims 13-15, wherein, After the second relay terminal sends the third relay request to the network-side device through the RRC procedure, the method further includes: The second relay terminal receives second configuration information sent by the network-side device; Wherein, the second configuration information is used to configure at least one of the following: The local identifier of the first sub-node; Uu RLC channel; the mapping relationship between the E2E SRB0 or E2E SRB1 of the first sub-node and the Uu RLC channel; Wherein, the local identifier of the first sub-node is used to identify the data of the first sub-node in the Uu RLC channel; The Uu RLC channel is the Uu RLC channel between the second relay terminal and the network-side device.

17. The method according to any one of claims 9-16, wherein, Before the second relay terminal receives target information sent by a remote terminal through a first sub-node, the method further includes: The second relay terminal receives third configuration information sent by the network-side device; Wherein, the third configuration information is used to configure at least one of the following: The local identifier of the remote terminal; Uu RLC channel; the mapping relationship between the E2E SRB0 or E2E SRB1 of the remote terminal and the Uu RLC channel; Wherein, the local identifier of the remote terminal is used to identify the data of the remote terminal in the Uu RLC channel; The Uu RLC channel is the Uu RLC channel between the second relay terminal and the network-side device.

18. An information sending method, including: A third relay terminal receives target information sent by a remote terminal through a second sub-node, where the second sub-node is a relay terminal connected to the third relay terminal in a relay link and located between the third relay terminal and the remote terminal; The third relay terminal sends the target information to the network-side device through the second parent node, where the second parent node is a relay terminal in the relay link that is connected to the third relay terminal and is located between the third relay terminal and the network-side device; Wherein, the relay link is a relay link between the remote terminal and the network-side device.

19. The method according to claim 18, wherein Before the third relay terminal receives the target information sent by the remote terminal through the second child node, the method further includes at least one of the following: The third relay terminal receives a first discovery message sent by the second child node, adds the device identifier of the third relay terminal to the routing information carried in the first discovery message, and sends the added first discovery message; The third relay terminal receives a first response message sent by the second parent node; The third relay terminal sends a first response message to the second child node; Wherein, the first response message carries the routing information of the relay link.

20. The method according to claim 18, wherein, Before the third relay terminal receives the target information sent by the remote terminal through the second child node, the method further includes at least one of the following: The third relay terminal receives a second discovery message sent by the second parent node, adds the device identifier of the third relay terminal to the routing information carried in the second discovery message, and sends the added second discovery message; The third relay terminal receives a second response message sent by the second child node; The third relay terminal sends a second response message to the second parent node; Wherein, the second response message carries the routing information of the relay link.

21. The method according to claim 18, the method further includes: The third relay terminal and the second parent node establish a PC5 link connection through a direct communication request (DCR) process; Or, the third relay terminal and the second child node establish a PC5 link connection through a DCR process.

22. The method according to any one of claims 18-21, wherein, The method further includes: When the second child node is in a non-connected state, the third relay terminal receives a fourth message sent by the second child node, and the fourth message is an end-to-end message between the second child node and the network-side device.

23. The method according to claim 22, wherein, After the third relay terminal receives the fourth message sent by the second child node, the method further includes: When the third relay terminal is in a non-connected state, the third relay terminal initiates entering a connected state; or, when the third relay terminal is in a connected state, the third relay terminal sends a fourth relay request to the network-side device through an RRC process; Wherein, the fourth relay request includes at least one of the following: Remote terminal identifier; Second child node identifier; Multi-hop relay link indication; The routing information of the relay link stored by the third relay terminal; Indication information indicating the number of relay terminals included in the routing information of the relay link stored by the third relay terminal.

24. The method according to claim 23, wherein The third relay terminal initiates entering a connected state, including at least one of the following: The third relay terminal sends a fifth message to the second parent node, and the fifth message is an end-to-end message between the third relay terminal and the network-side device; The third relay terminal receives an RRC response message corresponding to the fifth message sent by the second parent node; The method further includes: The third relay terminal sends a fourth relay request to the network-side device through an RRC procedure.

25. The method according to claim 24, wherein, The fifth message is used for: triggering the second parent node to initiate entering the connected state when the second parent node is in the non-connected state; or, triggering the second parent node to send a fifth relay request to the network-side device through an RRC procedure when the second parent node is in the connected state.

26. The method according to any one of claims 23-25, wherein, After the third relay terminal sends a fourth relay request to the network-side device through an RRC procedure, the method further includes at least one of the following: The third relay terminal receives an RRC response message corresponding to the fourth message sent by the network-side device; The third relay terminal sends an RRC response message corresponding to the fourth message to the second child node through a PC5 RLC channel.

27. The method according to any one of claims 23-26, wherein, After the third relay terminal sends a fourth relay request to the network-side device through an RRC procedure, the method further includes: The third relay terminal receives fourth configuration information sent by the network-side device; Wherein, the fourth configuration information is used to configure at least one of the following: The local identifier of the second child node; the second PC5 RLC channel; the mapping relationship between the E2E SRB0 or E2E SRB1 of the second child node and the second PC5 RLC channel; Wherein, the local identifier of the second child node is used to identify the data of the remote terminal in the second PC5 RLC channel; The second PC5 RLC channel is the PC5 RLC channel between the third relay terminal and the second parent node.

28. The method according to any one of claims 18-27, wherein Before the third relay terminal sends the target information to the network-side device through the second parent node, the method further includes: The third relay terminal receives fifth configuration information sent by the network-side device; Wherein, the fifth configuration information is used to configure at least one of the following: The local identifier of the remote terminal; the second PC5 RLC channel; the mapping relationship between the E2E SRB0 or E2E SRB1 of the remote terminal and the second PC5 RLC channel; Wherein, the local identifier of the remote terminal is used to identify the data of the remote terminal in the second PC5 RLC channel; The second PC5 RLC channel is the PC5 RLC channel between the third relay terminal and the second parent node.

29. An information sending method, including: A remote terminal sends target information to a network-side device through at least two relay terminals; Wherein, the relay link between the remote terminal and the network-side device includes the at least two relay terminals, and the at least two relay terminals include a first relay terminal connected to the remote terminal and a second relay terminal connected to the network-side device.

30. The method according to claim 29, wherein, Before the remote terminal sends target information to the network-side device through at least two relay terminals, the method further includes at least one of the following: The remote terminal sends a first discovery message and receives a first response message sent by the first relay terminal, where the first response message carries routing information of the relay link; The remote terminal receives a second discovery message sent by the first relay terminal and sends a second response message to the first relay terminal, where the second response message carries routing information of the relay link; A PC5 link connection is established between the remote terminal and the first relay terminal through a DCR process.

31. The method according to claim 29 or 30, wherein, The method further includes at least one of the following: The remote terminal sends a first message to the first relay terminal, where the first message is an end-to-end message between the remote terminal and the network-side device; The remote terminal receives an RRC response message corresponding to the first message sent by the first relay terminal through a PC5 RLC channel.

32. An information sending device, where the first relay terminal includes the information sending device, and the device includes: A first receiving module, configured to receive target information sent by a remote terminal; A sending module, configured to send the target information to the network-side device through a first parent node, where the first parent node is a relay terminal in the relay link that is connected to the first relay terminal and is located between the first relay terminal and the network-side device; Wherein, the first relay terminal is connected to the remote terminal, and the relay link is a relay link between the remote terminal and the network-side device.

33. An information sending device, where the second relay terminal includes the information sending device, and the device includes: A first receiving module, configured to receive target information sent by a remote terminal through a first child node, where the first child node is a relay terminal in the relay link that is connected to the second relay terminal and is located between the second relay terminal and the remote terminal; A first sending module, configured to send the target information to the network-side device; Wherein, the second relay terminal is connected to the network-side device, and the relay link is a relay link between the remote terminal and the network-side device.

34. An information sending device, where the third relay terminal includes the information sending device, and the device includes: A first receiving module, configured to receive target information sent by a remote terminal through a second child node, where the second child node is a relay terminal in the relay link that is connected to the third relay terminal and is located between the third relay terminal and the remote terminal; A sending module, configured to send the target information to the network-side device through a second parent node, where the second parent node is a relay terminal in the relay link that is connected to the third relay terminal and is located between the third relay terminal and the network-side device; Wherein, the relay link is a relay link between the remote terminal and the network-side device.

35. An information sending device, where the remote terminal includes the information sending device, and the device includes: A sending module, configured to send target information to the network-side device through at least two relay terminals; Among them, the relay link between the remote terminal and the network-side device includes the at least two relay terminals, and the at least two relay terminals include a first relay terminal connected to the remote terminal and a second relay terminal connected to the network-side device.

36. A communication device, comprising a processor and a memory, where the memory stores programs or instructions that can run on the processor, and when the programs or instructions are executed by the processor, the steps of the information sending method according to any one of claims 1-8 are implemented, or the steps of the information sending method according to any one of claims 9-17 are implemented, or the steps of the information sending method according to any one of claims 18-28 are implemented, or the steps of the information sending method according to any one of claims 29-31 are implemented.

37. A chip, the chip comprising a processor and a communication interface, the communication interface being coupled to the processor, and the processor being configured to run programs or instructions to implement the steps of the information sending method according to any one of claims 1-8, or to implement the steps of the information sending method according to any one of claims 9-17, or to implement the steps of the information sending method according to any one of claims 18-28, or to implement the steps of the information sending method according to any one of claims 29-31.

38. A readable storage medium, having programs or instructions stored thereon, and when the programs or instructions are executed by a processor, the steps of the information sending method according to any one of claims 1-8 are implemented, or the steps of the information sending method according to any one of claims 9-17 are implemented, or the steps of the information sending method according to any one of claims 18-28 are implemented, or the steps of the information sending method according to any one of claims 29-31 are implemented.

Images