Information sending method and device and related equipment

Abstract

The invention discloses an information sending method and device and related equipment, and belongs to the technical field of communication, and the method comprises the steps that a first relay terminal receives target information sent by a remote terminal; the first relay terminal sends the target information to network side equipment through a first father node, wherein the first father node is a relay terminal which is connected with the first relay terminal in a relay link and is located between the first relay terminal and the network side equipment; wherein the first relay terminal is connected with the remote terminal, and the relay link is a relay link between the remote terminal and the network side equipment.

Description

Technical Field

[0001] This application belongs to the field of communication technologies, and particularly relates to a method and device for information transmission and related equipment. Background Art

[0002] In the related art, a remote terminal is connected to a network-side device through a relay terminal. The link quality of this relay terminal needs to meet certain requirements for the reference signal received power (RSRP) threshold. The remote terminal may not find a suitable relay terminal to connect to the network-side device, which will cause the remote terminal to be unable 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

[0003] Embodiments of this application provide a method and device for information transmission and related equipment, which can solve the problem of poor communication performance between a remote terminal and a network-side device.

[0004] In a first aspect, there is provided a method for information transmission, which is characterized by including:

[0005] A first relay terminal receives target information sent by a remote terminal;

[0006] 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;

[0007] Wherein, the first relay terminal is connected to the remote terminal, and the relay link is the relay link between the remote terminal and the network-side device.

[0008] In a second aspect, there is provided a method for information transmission, which is characterized by including:

[0009] 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 in a relay link that is connected to the second relay terminal and is located between the second relay terminal and the remote terminal;

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

[0011] 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.

[0012] In a third aspect, there is provided a method for information transmission, which is characterized by including:

[0013] The third relay terminal receives the target information sent by the remote terminal through the second sub-node, where the second sub-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;

[0014] 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;

[0015] Wherein, the relay link is the relay link between the remote terminal and the network-side device.

[0016] In a fourth aspect, an information sending method is provided, which is characterized by including:

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

[0018] 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.

[0019] In a fifth aspect, an information sending device is provided, which is characterized in that the first relay terminal includes the information sending device, and the device includes:

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

[0021] A sending module, configured to send the target information to the network-side device through the 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;

[0022] Wherein, the first relay terminal is connected to the remote terminal, and the relay link is the relay link between the remote terminal and the network-side device.

[0023] In a sixth aspect, an information sending device is provided, which is characterized in that the second relay terminal includes the information sending device, and the device includes:

[0024] A first receiving module, configured to receive the target information sent by the remote terminal through the first sub-node, where the first sub-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;

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

[0026] 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.

[0027] In a seventh aspect, an information sending device is provided, characterized in that a third relay terminal includes the information sending device, and the device includes:

[0028] 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 in the relay link that is connected to the third relay terminal and is located between the third relay terminal and the remote terminal;

[0029] A sending module, 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 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;

[0030] Wherein, the relay link is a relay link between the remote terminal and the network-side device.

[0031] In an eighth aspect, an information sending device is provided, characterized in that a remote terminal includes the information sending device, and the device includes:

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

[0033] 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.

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

[0035] In a tenth aspect, a communication device is provided. The communication device is a first relay terminal and includes a processor and a communication interface. Wherein, the communication interface is used for:

[0036] Receiving target information sent by a remote terminal;

[0037] 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;

[0038] 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.

[0039] In an eleventh aspect, a communication device is provided. The communication device is a second relay terminal and includes a processor and a communication interface. Wherein, the communication interface is used for:

[0040] Receive the target information sent by the 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;

[0041] Send the target information to the network-side device;

[0042] 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.

[0043] In a twelfth aspect, a communication device is provided. The communication device is a third relay terminal and includes a processor and a communication interface. Wherein, the communication interface is used for:

[0044] Receive the target information sent by the 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;

[0045] 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;

[0046] Wherein, the relay link is a relay link between the remote terminal and the network-side device.

[0047] In a thirteenth aspect, a communication device is provided. The communication device is a remote terminal and includes a processor and a communication interface. Wherein, the communication interface is used for:

[0048] Send the target information to the network-side device through at least two relay terminals;

[0049] 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.

[0050] In a fourteenth aspect, an information sending system is provided, including: a first relay terminal, a second relay terminal, a third relay terminal, and a remote terminal. 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.

[0051] In a fifteenth aspect, a readable storage medium is provided. A program or instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, it implements the steps of the method described in the first aspect, or implements the steps of the method described in the second aspect, or implements the steps of the method described in the third aspect, or implements the steps of the method described in the fourth aspect.

[0052] In a sixteenth aspect, a chip is provided. The chip includes a processor and a communication interface, and the communication interface is coupled to the processor. The processor is used to run a program or instruction to implement the method described in the first aspect, or implement the method described in the second aspect, or implement the method described in the third aspect, or implement the method described in the fourth aspect.

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

[0054] In the embodiments of the present application, the first relay terminal receives the target information sent by the remote terminal; the first relay terminal sends the target information to the network-side device through the next-hop relay terminal; among them, the first relay terminal is connected to the remote terminal, and the first relay terminal is a relay terminal among the at least two relay terminals included in the relay link between the remote terminal and the network-side device. In this way, it is possible to support the remote terminal to communicate with the network-side device through a relay link including at least two relay terminals, and avoid the situation that the remote terminal may not find a suitable relay terminal to connect to the network-side device because the remote terminal can only be connected to the network-side device through one relay terminal, thereby improving the communication performance between the remote terminal and the network-side device. Description of the Drawings

[0055] Figure 1It is a block diagram of a wireless communication system to which the embodiments of the present application can be applied;

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

[0057] Figure 3 It is one of the flowcharts of an information sending method provided by the embodiments of the present application;

[0058] Figure 4 It is the second flowchart of an information sending method provided by the embodiments of the present application;

[0059] Figure 5 It is the third flowchart of an information sending method provided by the embodiments of the present application;

[0060] Figure 6 It is the fourth flowchart of an information sending method provided by the embodiments of the present application;

[0061] Figure 7 It is one of the schematic diagrams of a multi-hop U2N link provided by the embodiments of the present application;

[0062] Figure 8 It is the second schematic diagram of a multi-hop U2N link provided by the embodiments of the present application;

[0063] Figure 9 It is one of the structural schematic diagrams of an information sending device provided by the embodiments of the present application;

[0064] Figure 10 It is the second structural schematic diagram of an information sending device provided by the embodiments of the present application;

[0065] Figure 11 It is the third structural schematic diagram of an information sending device provided by the embodiments of the present application;

[0066] Figure 12 It is the fourth structural schematic diagram of an information sending device provided by the embodiments of the present application;

[0067] Figure 13 It is the structural schematic diagram of a communication device provided by the embodiments of the present application;

[0068] Figure 14 It is the structural schematic diagram of a terminal provided by the embodiments of the present application. Detailed implementation manners

[0069] Next, the technical solutions in the embodiments of the present application will be clearly described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art belong to the scope of protection of the present application.

[0070] The terms "first", "second", etc. in the present application are used to distinguish similar objects, rather than to describe a specific order or sequence. It should be understood that such terms can be interchanged under appropriate circumstances 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 usually of the same type, and the number of objects is not limited. For example, the first object can be one or multiple. In addition, "or" in the present application means at least one of the connected objects. For example, "A or B" covers three scenarios, namely, Scenario 1: including A and not including B; Scenario 2: including B and not including A; Scenario 3: including both A and B. The character " / " generally indicates an "or" relationship between the associated objects before and after.

[0071] The term "indication" in the present application can be either a direct indication (or an explicit indication) or an indirect indication (or an implicit indication). Among them, a direct indication can be understood as that the sender clearly informs the receiver of specific information, operations to be performed, or request results, etc. in the sent indication; an indirect indication can be understood as that the receiver determines the corresponding information according to the indication sent by the sender, or makes a judgment and determines the operations to be performed or request results, etc. according to the judgment result.

[0072] It should be noted that the technology described in the embodiments of this application is not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, 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 this application are often used interchangeably, and the described technology can be used in the above-mentioned systems and radio technologies, as well as in other systems and radio technologies. The following description describes the New Radio (NR) system for example purposes, and the NR term is used in most of the following descriptions, but these technologies can also be applied to systems other than the NR system, such as the 6th Generation (6G) communication system. th Generation, 6G) communication system.

[0073] Figure 1Block diagram of a wireless communication system to which embodiments of the present application can be applied. The wireless communication system includes a terminal 11 and a network-side device 12. Among them, the terminal 11 can be a mobile phone, a tablet personal computer, a 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, a flight vehicle, a vehicle user equipment (VUE), a shipborne device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, TVs, washing machines or furniture, etc.), a game console, a personal computer (PC), a teller machine or a self-service machine, etc. Wearable devices include: smart watches, smart bracelets, smart earphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart ankle chains, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle user equipment can also be referred to as a vehicle terminal, a vehicle controller, a vehicle module, a vehicle component, a vehicle chip or a vehicle unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application. The network-side device 12 can include an access network device or a core network device. Among them, the access network device can also be referred to as a radio access network (RAN) device, a radio access network function or a radio access network unit. The access network device can include a base station, a wireless local area network (WLAN) access point (AP) 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, Transmission Reception Point (TRP), or some other suitable term in the art. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiments of this application, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.

[0074] The core network device may include, but is not limited to, at least one of the following: core network node, core network function, Mobility Management Entity (MME), Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized network configuration (CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (L-NEF), Binding Support Function (BSF), Application Function (AF), Location Management Function (LMF), Gateway Mobile Location Centre (GMLC), Network Data Analytics Function (NWDAF), etc. It should be noted that in the embodiments of this application, only the core network devices in the NR system are taken as examples for introduction, and the specific types of core network devices are not limited.

[0075] For ease of understanding, some terms related to the embodiments of this application are explained below:

[0076] 1. Sidelink relay mechanism

[0077] In a wireless communication system, relay technology adds one or more relay nodes between the base station and the terminal, which are responsible for forwarding the wireless signal once or multiple times. That is, the wireless signal needs to go through multiple hops to reach the terminal.

[0078] Wireless relay technology can not only be used to expand cell coverage and make up for blind spots in cell coverage, but also improve cell capacity through spatial resource reuse. For indoor coverage, relay technology can also play a role in overcoming penetration loss and improving indoor coverage quality.

[0079] Taking a relatively simple two-hop relay as an example, wireless relay divides a base station-terminal link into two links: base station-relay station and relay station-terminal, thus having the opportunity to replace a link with poor quality with two links with better quality to obtain higher link capacity and better coverage.

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

[0081] NR will also study how to support the UE-to-Network relay mechanism, and typical scenarios are as Figure 2 shown. This is a typical UE-to-Network scenario. The remote UE needs to transmit data to the network side, but due to poor coverage, it finds a relay UE to forward for it. The interface between the relay UE and the base station is the Uu interface, and the interface between the relay UE and the remote UE is the sidelink (PC5) interface. Generally speaking, the relay UE is open and can serve any remote UE.

[0082] In related technologies, the remote terminal may not be able to find a suitable relay UE to connect to the network side device, which will cause the remote terminal to be unable to communicate with the network side device, resulting in poor communication performance between the remote terminal and the network side device.

[0083] Next, in conjunction with the accompanying drawings, the information sending method, device and related equipment provided by the embodiments of the present application will be described in detail through some embodiments and their application scenarios.

[0084] See Figure 3 , Figure 3 which is a flowchart of an information sending method provided by the embodiments of the present application. As Figure 3 shown, the information sending method includes the following steps:

[0085] Step 101: The first relay terminal receives the target information sent by the remote terminal;

[0086] Step 102: The first relay terminal sends the target information to the network-side device through the 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;

[0087] Among them, the first relay terminal is connected to the remote terminal, and the relay link is the relay link between the remote terminal and the network-side device.

[0088] Among them, 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 connection between the first relay terminal and 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.

[0089] Among them, 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.

[0090] Among them, the first parent node may be the second relay terminal or the third relay terminal. The second relay terminal is connected to the network-side device. It should be noted that the connection between the second relay terminal and the network-side device may mean that the second relay terminal is directly connected to the network-side device, that is, the second relay terminal is not connected to the network-side device through other relay terminals.

[0091] In an implementation manner, taking the relay link including two relay terminals as an example, the relay link is composed of the first relay terminal and the second relay terminal, and the transmission mode of the target information is: remote terminal > first relay terminal > second relay terminal > network-side device. At this time, the first parent node of the first relay terminal is the second relay terminal. The child node of the second relay terminal is the first relay terminal.

[0092] In an implementation manner, taking the relay link including three relay terminals as an example, the relay link is composed of the first relay terminal, the third relay terminal, and the second relay terminal, and the transmission mode of the target information is: remote terminal > first relay terminal > third relay terminal > second relay terminal > network-side device. At this time, the first parent node is the third relay terminal.

[0093] In one implementation, taking the example that the relay link includes N (N is an integer) third relay terminals, the relay link is composed of a first relay terminal, a plurality of third relay terminals, and a second relay terminal. The transmission method of the target information is: remote terminal > first relay terminal > first third relay terminal > second third relay terminal,..., (N-1)th third relay terminal > Nth third relay terminal > second relay terminal > network-side device. At this time, 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, and the child node of the Nth third relay terminal is the (N-1)th third relay terminal; the child node of the second relay terminal is the Nth third relay terminal.

[0094] In the related art, it only supports that a remote terminal (remote UE) is connected to the network through a relay terminal (relay UE), i.e., 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 needs to meet certain requirements of the RSRP high threshold or low threshold. Therefore, the effect of expanding the coverage is limited. It is possible that the remote UE cannot find an available relay UE around itself and thus cannot communicate with the network. The relay link in the embodiment of the present application is a multi-hop relay link, and the multi-hop relay link can better solve the coverage problem. The remote UE can establish a connection with the network through the relay transfer of multiple relay UEs.

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

[0096] 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:

[0097] 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 first discovery message after the addition;

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

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

[0100] Wherein, the first response message carries the routing information of the relay link.

[0101] Wherein, the first discovery message may carry the requirements of the remote terminal, for example, the desire to communicate with the network side through a multi-hop relay link for a certain type of service. The first relay terminal receives the first discovery message. Since the first relay terminal does not have the condition to directly communicate with the network side (such as a base station), but according to the capabilities of the first relay terminal, it can support multi-hop services. Therefore, 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.

[0102] 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 routing of the multi-hop U2N relay link, that is, which relay UEs the remote terminal (remote UE) accesses the network in sequence.

[0103] Taking the example that the relay link includes two relay terminals, 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, and the first response message carries the routing information of the relay link; the first relay terminal receives the first response message sent by the second relay terminal; the first relay terminal sends a first response message to the remote terminal. A hop-by-hop discovery process can be implemented.

[0104] In one implementation, the first relay terminal adds its device identifier to the routing information carried in the first discovery message and sends the first discovery message after the addition; the first parent node (i.e., the second relay terminal or the first third relay terminal) of the first 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 in the first discovery message, and sends the first discovery message after the addition; the 0-N third relay terminals sequentially receive the first discovery message and the routing table forwarded by the first relay terminal. Since they themselves do not have the condition to directly communicate with the network-side device (such as a base station), but can continue to support the forwarding of the multi-hop requirement according to their capabilities and service requirements (for example, some services have a delay requirement and cannot exceed 3 hops at most), they continue to help the remote terminal forward the first discovery message and sequentially add their own identifiers to the routing table. Finally, the second relay terminal receives the first discovery message. Since it has the condition to directly communicate with the network-side device, for example, the RSRP meets a certain threshold requirement, it can respond to the first discovery message, add its own identifier to the routing table, carry the routing information of the relay link (such as the complete routing table) in the first response message, and send the first response message to the previous-hop relay terminal in the reverse direction according to the node information recorded in the routing table in the first discovery message. Then each hop of the 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.

[0105] Further, since the first discovery message is sent in a broadcast manner, 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, meeting at least one of the conditions such as 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.

[0106] In addition, after the discovery process is completed, the remote terminal can also establish a PC5 link connection with the third relay terminal through a Direct Communication Request (DCR) process, and inform the third relay terminal of the routing information of the relay link. The third relay terminal then establishes a PC5 link connection with its next-hop, i.e., the parent node, through the DCR process and informs its parent node of the routing information of the relay link, and so on. Finally, the second relay terminal also establishes a PC5 connection with its child node through the DCR process and obtains the routing information of the relay link. Thus, the routing discovery and PC5 link establishment process between the remote terminal and the second relay terminal are completed.

[0107] 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 the discovery of the route and the pairwise progressive establishment of the PC5 link. Thus, the signaling delay can be saved.

[0108] 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 in 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 the 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.

[0109] 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:

[0110] 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;

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

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

[0113] Wherein, the second response message carries the routing information of the relay link.

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

[0115] Taking the example that the relay link includes two relay terminals, 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, sends a second response message to the first relay terminal, and 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; the second relay terminal receives the second response message sent by the first relay terminal. The hop-by-hop discovery process can be implemented.

[0116] In one implementation, the second relay terminal sends a second discovery message; 0 - N third relay terminals that receive the second discovery message can add their own identifiers to the routing table in sequence and forward the second discovery message; the first relay terminal can receive the second discovery message sent by the third relay terminal, add the device identifier of the first relay terminal to the routing information carried in the second discovery message, and send the added second discovery message; after receiving the second discovery message, the remote terminal has a matching U2N service to initiate, so it can respond to the second discovery message. Subsequently, it also sends second response messages step by step in the reverse direction of the routing table until the second relay terminal. Thus, the discovery process of a multi-hop U2N route is completed. In particular, when the remote terminal has multiple routes to choose from, it can also select the most suitable one as its final multi-hop relay route. For example, at least one of the conditions such as the minimum number of link hops, the shortest response delay, the best overall link quality, or the lightest overall link load is used as the final multi-hop relay route.

[0117] It should be noted that after the routing discovery is completed, the DCR process for each hop can be performed to establish the PC5 link connection between two ends. Since the remote terminal finally selects the route, generally, the remote terminal starts to initiate the DCR process to establish the PC5 link connection with the first relay terminal first, and then the first relay terminal establishes the PC5 link connection with the first third relay terminal, and so on, until the second relay terminal and the last third relay terminal complete the PC5 link establishment. Thus, the routing discovery and PC5 link establishment process between the remote terminal and the second relay terminal are completed.

[0118] In this embodiment, the first relay terminal receives a second discovery message sent by the next-hop 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; or, the first relay terminal receives a 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 a second discovery message initiated by other relay terminals, and realizes the establishment of a relay link including at least two relay terminals.

[0119] Optionally, the method further includes:

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

[0121] When the first relay terminal is in a non-connected state, the first relay terminal initiates to enter 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) procedure;

[0122] Wherein, the first relay request includes at least one of the following:

[0123] Remote terminal identifier;

[0124] Multi-hop relay link indication;

[0125] Routing information of the relay link stored by the first relay terminal;

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

[0127] Wherein, the first message can be used to establish a connection between the remote terminal and the network-side device. Exemplarily, the first message can be a connection establishment request carried by SRB0, a connection recovery request carried by SRB1, or a reconstruction request carried by SRB0, etc. The multi-hop relay link indication can be used to indicate the desire to initiate the establishment of a multi-hop relay link. SRB refers to Signalling Radio Bearer.

[0128] In addition, the peer end of the first message can be the network-side device.

[0129] Among them, the remote terminal identifier can identify the identity of the remote terminal. The routing information of the relay link stored in the first relay terminal may include the 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 in 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.

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

[0131] The embodiment of the present application provides 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), supports relay UEs in different RRC states, and gives a feasible solution for the establishment of a multi-hop link, which not only ensures the data transmission performance of the remote UE, but also reduces the processing complexity of the relay UE, and improves the overall network efficiency, capacity and coverage.

[0132] In this embodiment, the first relay terminal receives a first message sent by the remote terminal, and 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 the connected state; or, when the first relay terminal is in the connected state, the first relay terminal sends a first relay request to the network-side device through the 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 a first relay request, so that the remote terminal can enter the connected state by sending the first message with the network side as the peer to the first relay terminal.

[0133] Optionally, the first relay terminal initiating to enter the connected state includes at least one of the following:

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

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

[0136] The method further includes:

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

[0138] Among them, the RRC response message corresponding to a certain message (such as the first message, the second message, the third message, etc.) can be the response message of the network-side device to this message. By way of example, this RRC response message can be RRC setup, or RRC resume, etc.

[0139] In addition, the peer of the second message can be the network-side device.

[0140] Taking the example that the relay link includes two relay terminals, the first parent node is the second relay terminal, and the first relay terminal sends the second message to the second relay terminal (at this time, the second message is equivalent to the third message); when the second relay terminal is in the non-connected state, the second relay terminal initiates to enter the connected state; or, when the second relay terminal is in the connected state, the second relay terminal sends a second relay request to the network-side device through the RRC procedure (at this time, the second relay request is equivalent to the third relay request). The second relay terminal receives the RRC response message corresponding to the second message sent by the network-side device; the second relay terminal sends the RRC response message corresponding to the second message to the first relay terminal; the first relay terminal receives the RRC response message corresponding to the second message sent by the second relay terminal; at this time, the first relay terminal enters the connected state, and the first relay terminal sends a first relay request to the network-side device through the RRC procedure.

[0141] 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 the third relay terminal directly connected to the first relay terminal, and the first relay terminal sends the second message to the first parent node (at this time, the second message is equivalent to the fourth message); when the first parent node is in the non-connected state, the first parent node initiates to enter the connected state; or, when the first parent node is in the connected state, the first parent node sends a second relay request to the network-side device through the RRC procedure (at this time, the second relay request is equivalent to the fourth relay request). After the first parent node is in the connected state and sends the second relay request, the first parent node receives the RRC response message corresponding to the second message sent by the network-side device; the first parent node sends the RRC response message corresponding to the second message to the first relay terminal; the first relay terminal receives the RRC response message corresponding to the second message sent by the first parent node; at this time, the first relay terminal enters the connected state, and the first relay terminal sends a first relay request to the network-side device through the RRC procedure.

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

[0143] In this embodiment, the first relay terminal sends a second message to the next-hop relay terminal. The second message is an end-to-end message between the first relay terminal and the network device, so that the first relay terminal can transmit the second message with the network side as the peer through the next-hop relay terminal; the first relay terminal receives an 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 with the first relay terminal as the peer to the first relay terminal through the next-hop relay terminal; the first relay terminal sends a first relay request to the network device through the RRC process, which can realize the transmission of the first relay request after the first relay terminal enters the connected state.

[0144] Optionally, 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 device through the RRC process when the first parent node is in the connected state.

[0145] Wherein, the second relay request includes at least one of the following:

[0146] Remote terminal identifier;

[0147] Identifier of the first relay terminal;

[0148] Multi-hop relay link indication;

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

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

[0151] It should be noted that in a routing of a multi-hop U2N relay, regardless of the number of relay nodes involved, only the second relay terminal can directly communicate with the network-side device through the Uu interface, and there is no direct Uu interface link between other relay terminals and the network-side device. However, since other relay terminals need to forward data for the remote UE, these other relay terminals also need to be centrally controlled by the network-side device, obtain configurations or resources from the network side, and have the network-side device perform centralized bearer configuration and mapping management. Therefore, all relay terminals in the relay link need to enter the connected state.

[0152] Optionally, after the first relay terminal sends a first relay request to the network-side device through the RRC procedure, the method further includes at least one of the following:

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

[0154] 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.

[0155] In this embodiment, the first relay terminal receives the RRC response message sent by the network-side device corresponding to the first message, so that the network side can send the RRC response message with the remote terminal as the peer 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, realizing the transmission of the RRC response message with the remote terminal as the peer through the first relay terminal, thereby realizing the establishment of the RRC connection between the remote terminal and the network-side device.

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

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

[0158] Wherein, the first configuration information is used to configure at least one of the following:

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

[0160] Wherein, the local identifier of the remote terminal is used to identify the data of the remote terminal in the first PC5 RLC channel;

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

[0162] 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, enabling the first relay terminal to transmit the information transmitted between the terminal and the network side device according to the configuration of the network side.

[0163] It should be noted that the multi-hop relay link has a complex structure, and the establishment process of the one-hop relay link in the related art cannot be directly reused. The embodiment of the present application redesigned the connection establishment process for the multi-hop relay link, avoiding the situation that the remote terminal may not find a suitable relay terminal to connect to the network side device because the remote terminal can only connect to the network side device through one relay terminal, and improving the communication performance between the remote terminal and the network side device.

[0164] See Figure 4 , Figure 4 is a flowchart of an information sending method provided by an embodiment of the present application. As Figure 4 shown, the information sending method includes the following steps:

[0165] Step 201: The second relay terminal receives the target information sent by the remote terminal through the first sub-node. The first sub-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;

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

[0167] 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.

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

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

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

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

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

[0173] The second relay terminal receives a second response message sent by the first child node, and the second response message carries routing information of the relay link.

[0174] Optionally, the method further includes:

[0175] When the first child node is in a 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.

[0176] Wherein, the peer end of the third message may be the network-side device.

[0177] Optionally, after the second relay terminal receives the third message sent by the first child node, the method further includes:

[0178] When the second relay terminal is in a non-connected state, the second relay terminal initiates to enter 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 an RRC procedure;

[0179] Wherein, the third relay request includes at least one of the following:

[0180] Remote terminal identifier;

[0181] First child node identifier;

[0182] Multi-hop relay link indication;

[0183] Routing information of the relay link stored by the second relay terminal;

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

[0185] Wherein, the remote terminal identifier can identify the identity of the remote terminal. The routing information of the relay link stored by the second relay terminal may include the 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.

[0186] Optionally, after the second relay terminal initiates to enter the connected state, the method further includes:

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

[0188] Optionally, after the second relay terminal sends a third relay request to the network device through the RRC procedure, the method further includes at least one of the following:

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

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

[0191] Optionally, after the second relay terminal sends a third relay request to the network device through the RRC procedure, the method further includes:

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

[0193] Wherein, the second configuration information is used to configure at least one of the following:

[0194] The local identifier of the first sub-node; the Uu RLC channel; the mapping relationship between the E2E SRB0 or E2E SRB1 of the first sub-node and the Uu RLC channel;

[0195] 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;

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

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

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

[0199] Wherein, the third configuration information is used to configure at least one of the following:

[0200] 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;

[0201] Wherein, the local identifier of the remote terminal is used to identify the data of the remote terminal in the Uu RLC channel;

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

[0203] It should be noted that, as the implementation manner of the second relay terminal corresponding to the embodiment shown in Figure 3 , the same or corresponding implementation manners can be referred to the relevant descriptions of the embodiment shown in Figure 3 . To avoid repeated description, the relevant descriptions of this embodiment will not be elaborated herein.

[0204] Refer to Figure 5 , Figure 5 is a flowchart of an information sending method provided by an embodiment of the present application. As shown in Figure 5 , the information sending method includes the following steps:

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

[0206] Step 302, 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 connected to the third relay terminal in the relay link and located between the third relay terminal and the network-side device;

[0207] Wherein, the relay link is the relay link between the remote terminal and the network-side device.

[0208] 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:

[0209] 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 added first discovery message;

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

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

[0212] Wherein, the first response message carries the routing information of the relay link.

[0213] 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:

[0214] 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;

[0215] The third relay terminal receives the second response message sent by the second child node;

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

[0217] Wherein, the second response message carries the routing information of the relay link.

[0218] Optionally, the method further includes:

[0219] The third relay terminal and the second parent node establish a PC5 link connection through a DCR process; or, the third relay terminal and the second child node establish a PC5 link connection through a DCR process.

[0220] Optionally, the method further includes:

[0221] In a case where 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.

[0222] Wherein, the peer end of the fourth message may be the network-side device.

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

[0224] In a case where the third relay terminal is in a non-connected state, the third relay terminal initiates to enter a connected state; or, in a case where 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;

[0225] Wherein, the fourth relay request includes at least one of the following:

[0226] Remote terminal identifier;

[0227] Second child node identifier;

[0228] Multi-hop relay link indication;

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

[0230] An indication message indicating the number of relay terminals included in the routing information of the relay link stored by the third relay terminal.

[0231] Wherein, the remote terminal identifier can identify the identity of the remote terminal. The routing information of the relay link stored by the third relay terminal may include the 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.

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

[0233] 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;

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

[0235] The method further includes:

[0236] The third relay terminal sends a fourth relay request to the network side device through an RRC procedure.

[0237] Wherein, the peer end of the fifth message can be the network side device.

[0238] Optionally, the fifth message is used to: trigger the second parent node to initiate entry into the connected state when the second parent node is in the non-connected state; or, trigger 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.

[0239] Wherein, the fifth relay request includes at least one of the following:

[0240] Remote terminal identifier;

[0241] Identifier of the third relay terminal;

[0242] Multi-hop relay link indication;

[0243] The routing information of the relay link stored by the second parent node;

[0244] An indication message indicating the number of relay terminals included in the routing information of the relay link stored by the second parent node.

[0245] Optionally, 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:

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

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

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

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

[0250] Wherein, the fourth configuration information is used to configure at least one of the following:

[0251] The local identifier of the second sub-node; the second PC5 RLC channel; the mapping relationship between the E2E SRB0 or E2E SRB1 of the second sub-node and the second PC5 RLC channel;

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

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

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

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

[0256] Wherein, the fifth configuration information is used to configure at least one of the following:

[0257] 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;

[0258] Wherein, the local identifier of the remote terminal is used to identify the data of the remote terminal in the second PC5 RLC channel;

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

[0260] It should be noted that this embodiment is used as Figure 3The implementation manner of the corresponding third relay terminal in the illustrated embodiment, for the same or corresponding implementation manners, reference may be made to Figure 3 the relevant description of the illustrated embodiment. To avoid repeated description, it will not be elaborated in this embodiment.

[0261] See Figure 6 , Figure 6 is a flowchart of an information sending method provided by an embodiment of the present application. As Figure 6 shown, the information sending method includes the following steps:

[0262] Step 401, the remote terminal sends target information to the network-side device through at least two relay terminals;

[0263] 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.

[0264] Optionally, 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:

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

[0266] 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, and the second response message carries the routing information of the relay link;

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

[0268] Optionally, the method further includes at least one of the following:

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

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

[0271] It should be noted that this embodiment, as the implementation manner of the corresponding remote terminal in the Figure 3 illustrated embodiment, for the same or corresponding implementation manners, reference may be made to Figure 3 the relevant description of the illustrated embodiment. To avoid repeated description, it will not be elaborated in this embodiment.

[0272] The information sending method provided by the embodiments of the present application will be described below through several specific embodiments:

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

[0274] The embodiments of the present application mainly solve the problem of establishing a multi-hop U2N relay link, and may include the following content:

[0275] Before the signaling process of establishing a multi-hop U2N link by the remote UE, the remote UE needs to first establish the overall multi-hop route through a hop-by-hop discovery process, or a hop-by-hop DCR (Direct Communication Request) process, or even an end-to-end DCR process, for example, determine the path of remote UE-relay UE1-relay UE2-gNB, providing a prerequisite for subsequent connection establishment;

[0276] The remote UE initiates an end-to-end signaling connection establishment request to the network side through the first relay UE (access relay UE), and 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;

[0277] 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 relay requirements to the network, such as the remote UE identifier (ID), and carries 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; or, if the UE is in the non-RRC CONNECTED state, it first performs an RRC connection state transition to its parent relay UE, also initiating an end-to-end establishment process with the network side, entering the connected state first, and then reporting relay requirements and the remote UE ID, and 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.

[0278] When the access relay UE is in the connected state, its parent relay UE should enter the connected state in advance. Equivalent to the request process for each downstream UE to enter the connected state, it first triggers its own parent node to enter the connected state, and 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.

[0279] Embodiment 1: discovery / DCR process

[0280] This embodiment realizes the establishment of a multi-hop U2N relay link. However, before the establishment, it is necessary to determine the route of the multi-hop U2N relay link through a hop-by-hop discovery process, and / or a Hop-by-hop DCR (Direct Communication Request) process, or even an End-to-end DCR process, that is, which relay UEs the remote UE accesses the network in sequence. In this embodiment, the discovery process and DCR process for the multi-hop link are briefly described first to ensure the smooth progress and connection of the subsequent processes.

[0281] Such as Figure 7For example, a typical multi-hop U2N link is shown. Here, the remote UE is the actual requester of the service, and the gNB is the network node with which the remote UE needs to establish a connection and communicate. All other relay UEs are relay nodes to assist in the communication between the remote UE and the gNB, and the number of these relay nodes is greater than or equal to 2, 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.

[0282] For ease of description, the relay directly connected to the remote UE is defined as the access relay UE, the relay directly connected to the gNB through the Uu interface is defined as the donor relay UE, and the one in between is the intermediate relay UE. In a multi-hop U2N link, the access relay UE and the donor relay UE must exist, and the number of intermediate relay UEs is 0 - N.

[0283] In addition, due to the particularity of the U2N link, the gNB is the global control node and has the control right of configuration and resources. Therefore, the direction towards the gNB is the upstream direction, and the direction away from the gNB is the downstream direction. Between two adjacent UE nodes, the one closer to the gNB is the parent node, and the one farther from the gNB is the child node.

[0284] Before a remote UE establishes a connection with the gNB through a multi-hop U2N relay link, it first needs to determine the route of the multi-hop U2N link, that is, the remote UE needs to find its own access relay UE, the optional 0 - N intermediate relay UEs, and the final donor relay UE, so that it can reach the gNB through the found path.

[0285] The two UEs interact with each other's requirements and capability information through the discovery and / or DCR process of the PC5 interface to establish a multi-hop route. A simple example is as follows:

[0286] Example 1: The remote UE sends out discovery messages to its surroundings, carrying its own requirements, such as the hope to communicate with the network through a multi-hop relay link for a certain type of service. The access relay UE receives this discovery message. Since it does not have the condition to directly communicate with the base station but can support this multi-hop service 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 sequentially receive the discovery message and the routing table forwarded by the access relay UE. Since they also do not have the condition to directly communicate with the base station but can continue to support the forwarding of this multi-hop requirement according to their capabilities and service requirements (for example, some services have latency requirements, with a maximum of no more than 3 hops), they continue to help the remote UE forward the discovery message and sequentially add their own identifiers to the routing table. Finally, the donor relay UE receives this discovery message. Since it has the condition to directly communicate with the base station, for example, the RSRP meets certain threshold requirements (such as high threshold and / or low threshold, etc.), it can respond to this discovery message, add its own identifier to the routing table, carry the complete routing table in the response message, and send the response message back to the previous-hop intermediate relay UE according to the node information recorded in the routing table of the discovery message. Then each hop of the intermediate relay UE sends this 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.

[0287] After receiving the response message, the remote UE can determine that this multi-hop relay link can be used for the data transmission it requests. Further, since the discovery message is sent in a broadcast manner, there may be more than one multi-hop relay link after a single discovery process response. The remote UE can select the most suitable one as its final multi-hop relay route among them, for example, meeting at least one of the conditions such as the minimum number of link hops, the shortest response latency, the best overall link quality, or the lightest overall link load.

[0288] 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 finally selected route. The access relay UE then establishes a PC5 link connection with its next hop, i.e., the parent node, through the DCR process, and informs the parent node of the final route information. This is executed sequentially. Eventually, the donor relay UE also establishes a PC5 connection with its child node through the DCR process and obtains the route information.

[0289] In another way, the above Discovery process and DCR process can be combined, that is, the same set of signaling processes can complete both the discovery of the route and the pairwise and step-by-step establishment of the PC5 link. The advantage of this is to save signaling latency, but the risk is that in the case of finding a multi-hop path, the establishment of non-final selected paths is a waste.

[0290] The above DCR process establishes a PC5 connection between two adjacent UEs. Further, if necessary, the remote UE can also establish an end-to-end PC5 connection with non-adjacent nodes, such as the donor relay UE and / or the intermediate relay UE, through the end-to-end DCR process. The transmission of the 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.

[0291] Example 2. Another process of discovery and route establishment can also be initiated by the donor relay UE. Due to the condition that the donor relay UE communicates directly with the gNB through the Uu interface, it can actively initiate the discovery process to the surrounding area, declare which specific services it can support for the donor operation of multi-hop relay, and add its own identifier to the routing table. Among the 0-N intermediate relay UEs that receive this discovery message, since they can act as relay nodes in the multi-hop relay link according to the service and capabilities, they add their own identifiers to the routing table in sequence and forward the discovery message. The access relay UE also forwards it similarly and adds its own identifier to the routing table in order. After receiving it, if the remote UE has a conforming U2N service to initiate, it can respond to this discovery message. Subsequently, it also responds step by step in the reverse direction of the routing table until the donor relay UE. Thus, the discovery process of a multi-hop U2N route is completed. 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, meeting at least one of the conditions such as the minimum number of link hops, the shortest response delay, the best overall link quality, or the lightest overall link load.

[0292] After the route discovery is completed, the DCR process for each hop can be carried out to establish the PC5 link connection between two parties. Since the remote UE finally selects the route, generally, the remote UE starts to initiate the DCR process to establish the PC5 link connection with the access relay UE first, and then between the access relay UE and the first intermediate relay UE, and so on, until the PC5 link is established between the donor relay UE and the last intermediate relay UE.

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

[0294] Specifically, the above routing discovery and establishment processes are exemplified by new establishments. In practice, it is not excluded that the discovery and establishment processes have been completed among some relay UEs due to the requirements of other UEs. Then, when a new remote UE has a requirement, it can directly respond and complete the incremental establishment.

[0295] For example, if a remote UE 1 has already discovered and established a multi-hop relay link, the multi-hop link between the two relay nodes of the access relay UE - donor relay UE, then if a new remote UE 2 later has a multi-hop service requirement and conducts a discovery process around, and the basic PC5 communication link threshold is met between the access relay UE and remote UE 2, the access relay UE can directly respond to remote UE 2 and carry the already established routing table. In this way, remote UE 2 quickly completes the routing discovery, and after only establishing a PC5 link connection with the access relay UE, it can reuse the existing routing and PC5 link to complete the overall discovery and establishment process, greatly shortening the latency. However, the disadvantage of this method is that one node represents other nodes in the routing table to respond, and there may be a risk that other nodes cannot support routing reuse due to overloading, resulting in the failure of establishment.

[0296] Embodiment 2: Connected state relay UE

[0297] In Embodiment 1, the routing discovery and PC5 link establishment processes 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, it is further introduced how the remote UE and the base station establish a connection.

[0298] First, in a routing of a multi-hop U2N relay, regardless of the number of relay nodes involved, only the donor relay UE can directly communicate with the gNB through the Uu interface. There is no direct Uu interface link between other intermediate relay UEs / access relay UEs and the gNB. However, since the intermediate relay UEs and access relay UEs need to forward data for remote UEs, they also need to be centrally controlled by the base station, obtain configurations or resources from the base station, and have the base station perform centralized bearer configuration and mapping management. Therefore, the intermediate relay UEs and access relay UEs also need to enter the connected state and access the gNB indirectly (e.g., through the donor relay UE for transit), being controlled by the gNB and transceiver signaling.

[0299] 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 needs to enter the RRC CONNECTED state first to help the child node enter. Thus, if a relay UE is in the RRC CONNECTED state, it means that its parent node and subsequent parent nodes must also already be in the RRC CONNECTED state.

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

[0301] In this scenario, the remote UE sends an end-to-end RRC connection establishment request message with the destination of gNB to the access relay UE through the PC5 interface between the remote UE and the access relay UE. 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 (the configuration information of this PC5 RLC channel, including the logical channel identification (LCID), is specified in the protocol). The access relay UE can identify that this is the E2E SRB0 message of the remote UE from the data received on the default LCID. Therefore, it reports the relay requirement of the remote UE to the network through its own RRC process, specifically including carrying the remote UE identifier to indicate that this is a remote UE, and further indicating that this is a multi-hop remote UE, and even carrying the routing table of the remote UE stored by itself.

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

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

[0304] (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;

[0305] (3) Use the existing PC5 RLC channel between the access relay UE and its parent node or the newly established PC5 RLC channel to carry the E2E SRB0 message of the remote UE, and configure the mapping between the E2E SRB0 of the remote UE and this PC5 RLC channel;

[0306] Furthermore, since the complete routing information can be carried in the report of the access relay UE, the base station can also learn the parent node of the access relay UE, such as the first intermediate relay UE or the donor relay UE, and the identities of the relay UE nodes in the subsequent entire routing. As analyzed before, the access relay UE is in the connected state, so its parent node should also be in the connected state, and the relay UEs in the subsequent entire routing are all in the connected state. Therefore, the base station can configure the bearer and mapping relationships of the remote UE for its parent node and each relay UE in the subsequent routing. Similarly, the content configured for each subsequent relay node includes at least one of the following:

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

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

[0309] (3) Use the existing PC5 RLC channel between this relay UE and its parent node or the newly established PC5 RLC channel to carry the E2E SRB0 message of the remote UE, and configure the mapping between the E2E SRB0 of the remote UE and this PC5 RLC channel.

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

[0311] (1) Allocate a local identifier, Local UE ID, for the remote UE, which is used to distinguish the data of the remote UE in an RLC channel of the Uu interface between the current donor relay UE and the gNB;

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

[0313] (3) Use the existing Uu RLC channel or the newly established Uu RLC channel between the relay UE and the gNB to carry the E2E SRB0 message of the remote UE, and configure the mapping between the E2E SRB0 of the remote UE and this Uu RLC channel;

[0314] Through the above process, the gNB configures the transmission pipeline (PC5 RLC channel and mapping) and the identification method (such as local UE ID) on the PC5 interface between each relay UE and its parent node for the E2E SRB0 message of the remote UE, and also configures the Uu RLC channel and local UE ID on the Uu interface between the donor relay UE and the gNB. Therefore, the E2E SRB0 message of the remote UE can smoothly go from the access relay UE -> intermediate relay UE -> donor relay -> gNB. After the gNB receives the RRC setup request message, it returns an RRC setup message to the remote UE. The pipeline and mapping relationship of this message from the gNB to the access relay UE are the same as those of the uplink E2E SRB0 RRC setup request message. After reaching the access relay UE, it can identify that it is the E2E SRB0 DL message of the remote UE, so it is sent to the remote UE through the default RLC channel between the access relay UE and the remote UE. Thus, 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 with the gNB normally.

[0315] In each level of relay UE, the bearers of remote UEs are identified using the local UE ID and the E2E RB ID to complete multi-hop transmission. Moreover, it can support the aggregation of end-to-end bearers of multiple remote UEs for common transmission in the same RLC channel, reducing the processing complexity and channel overhead of the relay UE. As Figure 8 shown in the example, a multi-hop relay path of remote UE1 -> access relay UE 3 -> intermediate relay UE 4 -> donor relay UE 5 -> gNB is established, and another multi-hop relay path of remote UE2 -> access relay UE 4 -> donor relay UE 5 -> gNB is established. The mapping relationship and identification of the E2E RB of each remote UE in the RLC channel of each hop are as Figure 8 shown in the pipeline. Therefore, it can be seen that the sufficient aggregation of the pipeline can greatly reduce the number of pipelines and the processing complexity, and the combination of the local ID + E2E RB ID can well identify the identity and bearer type of the remote UE to which the E2E bearer belongs.

[0316] Furthermore, on the PC5 interface between the remote UE and its access relay UE node, only the initial E2E SRB0 and the E2E SRB1 used for recovery of failures adopt the default RLC channel configuration, which are SLRLC 0 and SL RLC 1 respectively. Other SRBs and DRBs can also be configured to be aggregated into a certain RLC channel respectively. In Figure 8 order to highlight the subsequent routing key points, the bearer aggregation between the remote and the access is not given.

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

[0318] Embodiment 3: Disconnected state relay UE

[0319] Based on the completion of the routing discovery and PC5 link establishment process between the remote UE and the donor relay UE, in this embodiment, another scenario of establishing a connection between the remote UE and the base station is further introduced.

[0320] In the second embodiment, a relatively simple end-to-end connection establishment method is given. Each relay UE has already entered the connected state in advance, so it is more convenient to report and configure the multi-hop requests and bearer mappings of the remote UE. However, this scenario is not always satisfied. A more general way is to assume that the remote UE is the one that initiates initially, such as the remote UE 1 in Embodiment 2. At this time, its access relay UE, intermediate relay UE, and donor relay UE are all in the non-connected state. Then, how to trigger all relay UEs involved in the routing to enter the connected state and have each transmission path configured by the network side is a problem that needs to be solved. This process generally includes the following steps:

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

[0322] Step 1: The remote UE sends an end-to-end RRC connection establishment request message with the destination of gNB to the access relay UE through the PC5 interface between the remote UE and the access relay UE;

[0323] This message is generally carried by E2E SRB0. This message has a default mapping relationship on the PC5 interface. For example, it is mapped to SL RLC 0. The access relay UE can recognize that this is the E2E SRB0 message of the remote UE from the data received on the default LCID. If the access relay UE is in the non-connected state at this time, then it needs to enter the connected state by itself first;

[0324] Step 2: The access relay UE sends an end-to-end RRC connection establishment request message with the destination of gNB to its parent node through the PC5 interface between itself and its parent node;

[0325] It should be noted that since the routing discovery and the establishment of each PC5 connection have been completed in Step 0, the access relay UE is also clear about the routing information between itself and the gNB. For example, it can find its next-hop parent node in the routing table of the remote UE. Therefore, the parent node is already determined;

[0326] 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 recognize that this is the E2E SRB0 message of the accessrelay UE. If the parent node of the access relay UE is in the disconnected state at this time, then it also needs to enter the connected state by itself;

[0327] Step 3: Each subsequent relay node repeats the process similar to Step 1 and Step 2 to initiate its own transition to the connected state;

[0328] 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, the donor relay UE directly establishes a connection to the gNB through the RACH procedure and the RRCsetup procedure on the Uu interface and enters the RRC connected state;

[0329] Step 5: After the donor relay UE enters the connected state, it can establish SRB1 and perform security activation and other operations according to the existing process. Then it reports its child node to the gNB. For example, a certain intermediate relay UE or access relay UE hopes to initiate the establishment of a relay link. Therefore, it reports the relay requirements of the child node to the network through its own RRC process, specifically including carrying the child node UE identifier to indicate that this is a remote UE (at this time, the child node itself acts as a remote UE to establish its own transmission channel).

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

[0331] (1) Allocate a local identifier, Local UE ID, for the child node, which is used to distinguish the data of the child node in an RLC channel on the Uu interface between the donor relay UE and the gNB;

[0332] (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;

[0333] (3) Use the existing Uu RLC channel between the donor relay UE and the gNB or the newly established Uu RLC channel to carry the E2E SRB0 message of the child node, and configure the mapping between the E2E SRB0 of the child node and this Uu RLC channel;

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

[0335] Step 8: The gNB receives the E2E SRB0 message of the child node and returns the E2E SRB0 DL (RRC setup message) through the same Uu RLC channel;

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

[0337] Step 10: When the receiving end of the child node of the donor relay UE receives the end-to-end RRC setup message, it means entering the connected state, and the signaling channel between it and the gNB is established.

[0338] 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 process similar to that between Step 5 and Step 10;

[0339] And so on. After each parent node enters the connected state, it executes the process between Step 5 and Step 10 to help its own child node enter the connected state;

[0340] Taking the link of remote UE 1 -> access relay UE 2 -> intermediate relay UE 3 -> donor relay UE 4 -> gNB as an example:

[0341] (1) The remote UE 1 -> access relay UE 2 sends the E2E SRB 0 message, triggering the access relay UE2 to initiate entering the connected state;

[0342] (2) Then, the access relay UE2 sends its E2E SRB 0 message to the intermediate relay UE 3, triggering the intermediate relay UE 3 to initiate entering the connected state;

[0343] (3) Next, the intermediate relay UE 3 sends its E2E SRB 0 message to the donor relay UE 4, triggering the donor relay UE 4 to initiate entering the connected state;

[0344] (4) The donor relay UE 4 has an available Uu interface, so it can enter the connected state in the same way as a normal UE and obtain the SRB1 configuration and security activation, etc.; and the donor relay UE4 reports to the gNB that the intermediate relay UE3 hopes to establish a relay link through itself as a remote UE. At this time, it is a one-hop relay link, so the intermediate relay UE 3 ID (Layer 2 ID) and the remote UE identity are reported. After reporting, the donor relay UE can obtain the bearer configuration and mapping configuration, and the intermediate relay UE 3 local UE ID from the gNB, and can forward the first UL SRB0 RRC setup request message for the intermediate relay UE 3;

[0345] (5) The network sends a UL SRB0 RRC setup message to the intermediate relay UE 3 through the same path as the UL SRB0 RRC setup request of the intermediate relay UE 3. The intermediate relay UE 3 enters the connected state and obtains the SRB1 configuration, security activation, etc. The intermediate relay UE 3 reports to the gNB that the access relay UE 2 hopes to establish a relay link as a remote UE through itself. At this time, it is a two-hop relay link. Therefore, in addition to reporting the 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 carry the routing information between the access relay UE 2 and the gNB. After reporting, the intermediate relay UE 3 obtains the bearer configuration, mapping configuration, and the access relay UE 2 local UE ID, and can forward the first UL SRB0 RRC setup request message for the access relay UE 2;

[0346] (6) The network sends a UL SRB0 RRC setup message to the access relay UE 2 through the same path as the UL SRB0 RRC setup request of the access relay UE 2. The access relay UE 2 enters the connected state and obtains the SRB1 configuration, security activation, etc. The access relay UE 2 reports to the gNB that the remote UE 1 hopes to establish a relay link as a remote UE through itself. At this time, it is a three-hop relay link. Therefore, in addition to reporting the remote UE 1 ID (Layer 2 ID) and the remote UE identity, it can also indicate that this is a multi-hop relay link request and carry the routing information between the remote UE 1 and the gNB. After reporting, the access relay UE 2 obtains the bearer configuration, mapping configuration, and the remote UE 1 local UE ID, and can forward the first UL SRB0 RRC setup request message for the remote UE 1;

[0347] (7) The network sends the 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 the SRB1 configuration and security activation, etc. Subsequently, the remote UE can directly communicate with the gNB to obtain subsequent DRB configurations and data transmissions;

[0348] In the above process, it is assumed that each hop relay node needs to trigger the entry into the connected state. If a certain level of relay UE in the middle is already in the connected state, the steps of entering the connected state can be omitted, and the requirements of its child nodes can be directly reported to help the child nodes enter the connected state.

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

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

[0351] For the information sending method provided by the embodiments of the present application, the execution subject can be an information sending device. In the embodiments of the present application, taking the information sending device as an example to execute the information sending method, the information sending device provided by the embodiments of the present application is described.

[0352] Please refer to Figure 9 , Figure 9 which is a structural diagram of an information sending device provided by the embodiments of the present application. The first relay terminal includes the information sending device. As Figure 9 shown, the information sending device 500 includes:

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

[0354] 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 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;

[0355] 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.

[0356] Optionally, the device further includes a first transceiver module for at least one of the following:

[0357] Receive a first discovery message sent by the remote terminal, add the device identifier of the first relay terminal to the routing information carried in the first discovery message, and send the added first discovery message;

[0358] Receive a first response message sent by the first parent node;

[0359] Send a first response message to the remote terminal;

[0360] Wherein, the first response message carries the routing information of the relay link.

[0361] Optionally, the device further includes a second transceiver module for at least one of the following:

[0362] Receive a second discovery message sent by the first parent node, add the device identifier of the first relay terminal to the routing information carried in the second discovery message, and send the added second discovery message;

[0363] Receive a second response message sent by the remote terminal;

[0364] Send a second response message to the first parent node;

[0365] Wherein, the second response message carries the routing information of the relay link.

[0366] Optionally, the device further includes:

[0367] A second receiving module, 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;

[0368] A processing module, configured to initiate entering a connected state when the first relay terminal is in a non-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 procedure;

[0369] Wherein, the first relay request includes at least one of the following:

[0370] Remote terminal identifier;

[0371] Multi-hop relay link indication;

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

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

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

[0375] 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;

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

[0377] The apparatus further includes:

[0378] A sending module, configured to send a first relay request to the network-side device through an RRC procedure.

[0379] Optionally, the second message is used for: triggering the first parent node to initiate entry into 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.

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

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

[0382] Sending the RRC response message corresponding to the first message to the remote terminal through a PC5 radio link control (RLC) channel.

[0383] Optionally, the apparatus further includes:

[0384] A third receiving module, configured to receive first configuration information sent by the network-side device;

[0385] Wherein, the first configuration information is used to configure at least one of the following:

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

[0387] Wherein, the local identifier of the remote terminal is used to identify the data of the remote terminal in the first PC5 RLC channel;

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

[0389] The information sending device in the embodiments of the present application may 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 a chip. The electronic device may be a terminal or other devices other than terminals. Exemplarily, the terminal may include, but is not limited to, the types of the terminal 11 listed above, and other devices may be a server, a Network Attached Storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0390] The information sending device provided in the embodiments of the present application can implement Figure 3 each process implemented by the method embodiments and achieve the same technical effects. To avoid repetition, details are not described herein again.

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

[0392] A first receiving module 601, 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;

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

[0394] 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.

[0395] Optionally, the device further includes a first transceiver module, configured to perform at least one of the following:

[0396] Receive a first discovery message sent by the first sub-node;

[0397] Send a first response message to the first sub-node, where the first response message carries routing information of the relay link.

[0398] Optionally, the device further includes a second transceiver module, configured to perform at least one of the following:

[0399] Send a second discovery message;

[0400] Receive a second response message sent by the first sub-node, where the second response message carries routing information of the relay link.

[0401] Optionally, the device further includes:

[0402] A second receiving module, 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.

[0403] Optionally, the apparatus further includes:

[0404] A processing module, configured to initiate entering a connected state when the second relay terminal is in a non-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 procedure;

[0405] Wherein, the third relay request includes at least one of the following:

[0406] Remote terminal identifier;

[0407] First sub-node identifier;

[0408] Multi-hop relay link indication;

[0409] Routing information of the relay link stored by the second relay terminal;

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

[0411] Optionally, the apparatus further includes:

[0412] A second sending module, configured to send a third relay request to the network-side device through an RRC procedure when the second relay terminal enters a connected state.

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

[0414] Receive an RRC response message corresponding to the third message sent by the network-side device;

[0415] Send an RRC response message corresponding to the third message to the first sub-node through a PC5 RLC channel.

[0416] Optionally, the apparatus further includes:

[0417] A third receiving module, configured to receive second configuration information sent by the network-side device;

[0418] Wherein, the second configuration information is used to configure at least one of the following:

[0419] The local identifier of the first sub-node; the Uu RLC channel; the mapping relationship between the E2E SRB0 or E2E SRB1 of the first sub-node and the Uu RLC channel;

[0420] 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;

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

[0422] Optionally, the device further includes:

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

[0424] Wherein, the third configuration information is used to configure at least one of the following:

[0425] 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;

[0426] Wherein, the local identifier of the remote terminal is used to identify the data of the remote terminal in the Uu RLC channel;

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

[0428] The information sending device in the embodiments of the present application may 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 a chip. The electronic device may be a terminal or other devices other than the terminal. Exemplarily, the terminal may include, but is not limited to, the types of the above-mentioned terminal 11, and other devices may be a server, a Network Attached Storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0429] The information sending device provided by the embodiments of the present application can implement Figure 4 each process implemented by the method embodiments and achieve the same technical effects. To avoid repetition, details are not described here again.

[0430] Please refer to Figure 11 , Figure 11 is a structural diagram of an information sending device provided by the embodiments of the present application. The third relay terminal includes the information sending device. As Figure 11 shown, the information sending device 500 includes:

[0431] The first receiving module 701 is configured to receive the target information sent by the remote terminal through the 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;

[0432] The sending module 702 is configured to send 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;

[0433] Wherein, the relay link is a relay link between the remote terminal and the network-side device.

[0434] Optionally, the device further includes a first transceiver module, configured to perform at least one of the following:

[0435] Receive a first discovery message sent by the second child node, add the device identifier of the third relay terminal to the routing information carried in the first discovery message, and send the added first discovery message;

[0436] Receive a first response message sent by the second parent node;

[0437] Send a first response message to the second child node;

[0438] Wherein, the first response message carries the routing information of the relay link.

[0439] Optionally, the device further includes a second transceiver module, configured to perform at least one of the following:

[0440] Receive a second discovery message sent by the second parent node, add the device identifier of the third relay terminal to the routing information carried in the second discovery message, and send the added second discovery message;

[0441] Receive a second response message sent by the second child node;

[0442] Send a second response message to the second parent node;

[0443] Wherein, the second response message carries the routing information of the relay link.

[0444] Optionally, the device further includes:

[0445] A establishing module, configured to establish a PC5 link connection between the third relay terminal and the second parent node through a DCR process; or, establish a PC5 link connection between the third relay terminal and the second child node through a DCR process.

[0446] Optionally, the apparatus further comprises:

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

[0448] Optionally, the apparatus further comprises:

[0449] A processing module, configured to initiate entering a connected state when the third relay terminal is in a non-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 procedure;

[0450] Wherein, the fourth relay request includes at least one of the following:

[0451] Remote terminal identifier;

[0452] Second child node identifier;

[0453] Multi-hop relay link indication;

[0454] Routing information of the relay link stored by the third relay terminal;

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

[0456] Optionally, the third relay terminal initiating entering a connected state includes at least one of the following:

[0457] 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;

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

[0459] The method further comprises:

[0460] The third relay terminal sends a fourth relay request to the network-side device through an RRC procedure.

[0461] Optionally, the fifth message is used for: triggering the second parent node to initiate entering a connected state when the second parent node is in a 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 a connected state.

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

[0463] Receive an RRC response message corresponding to the fourth message sent by the network-side device;

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

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

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

[0467] Wherein, the fourth configuration information is used to configure at least one of the following:

[0468] The local identifier of the second sub-node; the second PC5 RLC channel; the mapping relationship between the E2E SRB0 or E2E SRB1 of the second sub-node and the second PC5 RLC channel;

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

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

[0471] Optionally, the apparatus further includes:

[0472] A fourth receiving module, configured to receive fifth configuration information sent by the network-side device;

[0473] Wherein, the fifth configuration information is used to configure at least one of the following:

[0474] 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;

[0475] Wherein, the local identifier of the remote terminal is used to identify the data of the remote terminal in the second PC5 RLC channel;

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

[0477] The information sending device in the embodiments of the present application may 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 a chip. The electronic device may be a terminal or other devices other than the terminal. Exemplarily, the terminal may include, but is not limited to, the types of the terminal 11 listed above, and other devices may be a server, a Network Attached Storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0478] The information sending device provided in the embodiments of the present application can implement Figure 5 each process implemented by the method embodiments and achieve the same technical effects. To avoid repetition, details are not described herein again.

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

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

[0481] 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.

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

[0483] 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;

[0484] Receive a second discovery message sent by the first relay terminal, and send a second response message to the first relay terminal, where the second response message carries routing information of the relay link;

[0485] Establish a PC5 link connection with the first relay terminal through a DCR process.

[0486] Optionally, the device further includes a transceiver module, configured to perform at least one of the following:

[0487] Send 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;

[0488] Receive, through the PC5 RLC channel, the RRC response message corresponding to the first message sent by the first relay terminal.

[0489] The information sending device in the embodiments of the present application may 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 a chip. The electronic device may be a terminal or other devices other than terminals. Exemplarily, the terminal may include, but is not limited to, the types of the above-listed terminal 11, and other devices may be a server, a Network Attached Storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0490] The information sending device provided in the embodiments of the present application can implement Figure 6 each process implemented by the method embodiments and achieve the same technical effects. To avoid repetition, details are not described herein again.

[0491] As Figure 13 shown, the embodiments of the present application further provide a communication device 900, including a processor 901 and a memory 902. A program or instruction that can run on the processor 901 is stored on the memory 902. When the program or instruction is executed by the processor 901, each step of the above information sending method embodiment is implemented, and the same technical effects can be achieved.

[0492] The embodiments of the present application further provide a terminal, including a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run a program or instruction to implement the steps in the method embodiments as Figure 3 , Figure 4 , Figure 5 or Figure 6 shown. This terminal embodiment corresponds to the above terminal-side method embodiments. Each implementation process and implementation manner of the above method embodiments can be applied to this terminal embodiment, and the same technical effects can be achieved. Specifically, Figure 14 is a schematic diagram of the hardware structure of a terminal for implementing the embodiments of the present application.

[0493] The terminal 1000 includes, but is not limited to, at least some components such as 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 a processor 1010.

[0494] Those skilled in the art can understand that the terminal 1000 may further include a power source (such as a battery) for supplying power to each component. The power source can be logically connected to the processor 1010 through a power management system, so as to implement functions such as management of charging, discharging, and power consumption management through the power management system. Figure 14 The terminal structure shown in Figure 14 does not limit the terminal. The terminal may include more or fewer components than shown in the figure, or combine some components, or have different component arrangements, which will not be elaborated here.

[0495] It should be understood that in the embodiments of the present application, the input unit 1004 may include a Graphics Processing Unit (GPU) 10041 and a microphone 10042. The GPU 10041 processes the image data of still pictures or videos 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 at least one of a touch panel 10071 and 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. The 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 a joystick, which will not be elaborated here.

[0496] In the embodiments of the present application, after the radio frequency unit 1001 receives downlink data from a network-side device, it can be transmitted to the processor 1010 for processing; in addition, the radio frequency unit 1001 can send uplink data to the network-side device. Generally, the radio frequency unit 1001 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0497] 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. Among them, the first storage area may store an operating system, application programs 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 (DDR SDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM), and a direct rambus random access memory (DRRAM). The memory 1009 in the embodiments of the present application includes but is not limited to these and any other suitable types of memories.

[0498] The processor 1010 may include one or more processing units; optionally, the processor 1010 integrates an application processor and a modem processor. Among them, the application processor mainly processes operations related to the operating system, user interface, and application programs, etc., and the modem processor mainly processes wireless communication signals, such as a baseband processor. It can be understood that the above modem processor may not be integrated into the processor 1010 either.

[0499] In the case where the terminal is a first relay terminal:

[0500] Among them, the radio frequency unit 1001 is used for:

[0501] Receiving target information sent by a remote terminal;

[0502] Send the target information to the network-side device through the 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;

[0503] 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.

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

[0505] Receive a first discovery message sent by the remote terminal, add the device identifier of the first relay terminal to the routing information carried in the first discovery message, and send the added first discovery message;

[0506] Receive a first response message sent by the first parent node;

[0507] Send a first response message to the remote terminal;

[0508] Wherein, the first response message carries the routing information of the relay link.

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

[0510] Receive a second discovery message sent by the first parent node, add the device identifier of the first relay terminal to the routing information carried in the second discovery message, and send the added second discovery message;

[0511] Receive a second response message sent by the remote terminal;

[0512] Send a second response message to the first parent node;

[0513] Wherein, the second response message carries the routing information of the relay link.

[0514] 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;

[0515] The processor 1010 is configured to: initiate entering the connected state when the first relay terminal is in the non-connected state; or, send a first relay request to the network-side device through the RRC procedure when the first relay terminal is in the connected state;

[0516] Wherein, the first relay request includes at least one of the following:

[0517] Remote terminal identifier;

[0518] Multi-hop relay link indication;

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

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

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

[0522] 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;

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

[0524] The apparatus further includes:

[0525] A sending module, configured to send a first relay request to the network-side device through an RRC procedure.

[0526] Optionally, the second message is used for: triggering the first parent node to initiate entry into 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.

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

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

[0529] Sending the RRC response message corresponding to the first message to the remote terminal through a PC5 radio link control (RLC) channel.

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

[0531] Wherein, the first configuration information is used to configure at least one of the following:

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

[0533] Wherein, the local identifier of the remote terminal is used to identify the data of the remote terminal in the first PC5 RLC channel;

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

[0535] When the terminal is the second relay terminal:

[0536] Among them, the radio frequency unit 1001 is used to:

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

[0538] Send the target information to the network-side device;

[0539] Among them, 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.

[0540] Optionally, the radio frequency unit 1001 is further used for at least one of the following:

[0541] Receive the first discovery message sent by the first child node;

[0542] Send a first response message to the first child node, where the first response message carries the routing information of the relay link.

[0543] Optionally, the radio frequency unit 1001 is further used for at least one of the following:

[0544] Send a second discovery message;

[0545] Receive the second response message sent by the first child node, where the second response message carries the routing information of the relay link.

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

[0547] Optionally, the processor 1010 is used to: when the second relay terminal is in a non-connected state, initiate entering the connected state; or, when the second relay terminal is in the connected state, send a third relay request to the network-side device through the RRC process;

[0548] Among them, the third relay request includes at least one of the following:

[0549] Remote terminal identifier;

[0550] First child node identifier;

[0551] Multi-hop relay link indication;

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

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

[0554] Optionally, the radio frequency unit 1001 is further configured to: in the case where the second relay terminal enters the connected state, send a third relay request to the network-side device through the RRC procedure.

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

[0556] Receive an RRC response message corresponding to the third message sent by the network-side device;

[0557] Send an RRC response message corresponding to the third message to the first sub-node through the PC5 RLC channel.

[0558] Optionally, the apparatus further includes:

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

[0560] Wherein, the second configuration information is used to configure at least one of the following:

[0561] The local identifier of the first sub-node; the Uu RLC channel; the mapping relationship between the E2E SRB0 or E2E SRB1 of the first sub-node and the Uu RLC channel;

[0562] 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;

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

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

[0565] Wherein, the third configuration information is used to configure at least one of the following:

[0566] 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;

[0567] Among them, the local identifier of the remote terminal is used to identify the data of the remote terminal in the Uu RLC channel;

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

[0569] When the terminal is the third relay terminal:

[0570] Among them, the radio frequency unit 1001 is used for:

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

[0572] Sending 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;

[0573] Among them, the relay link is the relay link between the remote terminal and the network-side device.

[0574] Optionally, the radio frequency unit 1001 is further used for at least one of the following:

[0575] Receiving the 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 added first discovery message;

[0576] Receiving the first response message sent by the second parent node;

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

[0578] Among them, the first response message carries the routing information of the relay link.

[0579] Optionally, the radio frequency unit 1001 is further used for at least one of the following:

[0580] Receiving the 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 added second discovery message;

[0581] Receiving the second response message sent by the second sub-node;

[0582] Sending the second response message to the second parent node;

[0583] Wherein, the second response message carries the routing information of the relay link.

[0584] 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, establish a PC5 link connection between the third relay terminal and the second child node through a DCR process.

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

[0586] Optionally, the processor 1010 is configured to: initiate entering a connected state when the third relay terminal is in a non-connected state; or, send a fourth relay request to the network-side device through an RRC process when the third relay terminal is in a connected state.

[0587] Wherein, the fourth relay request includes at least one of the following:

[0588] Remote terminal identifier;

[0589] Second child node identifier;

[0590] Multi-hop relay link indication;

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

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

[0593] Optionally, the third relay terminal initiating entering a connected state includes at least one of the following:

[0594] 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;

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

[0596] The method further includes:

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

[0598] Optionally, the fifth message is used to: trigger the second parent node to initiate entering the connected state when the second parent node is in the disconnected state; or, trigger the second parent node to send a fifth relay request to the network-side device through the RRC procedure when the second parent node is in the connected state.

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

[0600] Receive an RRC response message corresponding to the fourth message sent by the network-side device;

[0601] Send an RRC response message corresponding to the fourth message to the second child node through the PC5 RLC channel.

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

[0603] Wherein, the fourth configuration information is used to configure at least one of the following:

[0604] 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;

[0605] 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;

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

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

[0608] Wherein, the fifth configuration information is used to configure at least one of the following:

[0609] 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;

[0610] Wherein, the local identifier of the remote terminal is used to identify the data of the remote terminal in the second PC5 RLC channel;

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

[0612] When the terminal is a remote terminal:

[0613] Among them, the radio frequency unit 1001 is used for:

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

[0615] 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.

[0616] Optionally, the radio frequency unit 1001 is further used for: sending a first discovery message, receiving a first response message sent by the first relay terminal, where the first response message carries routing information of the relay link;

[0617] 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;

[0618] Or

[0619] The processor 1010 is used for: establishing a PC5 link connection with the first relay terminal through the DCR process.

[0620] Optionally, the radio frequency unit 1001 is further used for at least one of the following:

[0621] 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;

[0622] Receiving an RRC response message corresponding to the first message sent by the first relay terminal through the PC5 RLC channel.

[0623] It can be understood that the implementation processes of the implementation manners mentioned in this embodiment can refer to the relevant descriptions of the method embodiments Figure 3 、 Figure 4 、 Figure 5 Or Figure 6 and achieve the same or corresponding technical effects. To avoid repetition, they will not be elaborated here.

[0624] The embodiment of the present application further provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, it implements each process of the above information sending method embodiment and can achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0625] Among them, the processor is the processor in the terminal described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory ROM, random access memory RAM, magnetic disks, or optical discs, etc. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0626] Another embodiment of the present application provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement each process of the above information sending method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0627] It should be understood that the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, system chip, chip system, or system-on-chip, etc.

[0628] Another embodiment of the present application provides a computer program / program product. The computer program / program product is stored in a storage medium. The computer program / program product is executed by at least one processor to implement each process of the above information sending method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0629] The embodiment of the present application further provides an information sending system, including: a first relay terminal, a second relay terminal, a third relay terminal, and a remote terminal. 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. The remote terminal can be used to execute the steps of the information sending method applied to the remote terminal as described above.

[0630] It should be noted that in this text, the terms "include", "comprise" 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 not only includes those elements, but also includes other elements not explicitly listed, or elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "comprising one..." does not exclude the existence of additional identical elements in the process, method, article or device comprising such 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 reverse order according to the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted or combined. Additionally, features described with reference to certain examples may be combined in other examples.

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

[0632] The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not restrictive. Under the inspiration of the present application, those of ordinary skill in the art can also make many forms of embodiments without departing from the purpose of the present application and the scope protected by the claims. These embodiments are all within the protection scope of the present application.

Claims

1. An information sending method, characterized in that, Including: 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, characterized in that, Before the first relay terminal receives the target information sent by the remote terminal, the method further includes 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 includes 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 to 3, characterized in that, The method further includes: The first relay terminal receives a first message sent by the remote terminal, and 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 includes 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 initiating entering a connected state includes at least one of the following: The first relay terminal sends a second message to the first parent node, and 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 includes: 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, characterized in that, 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 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 to 6, characterized in that, After the first relay terminal sends a first relay request to the network 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 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, characterized in that, 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 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. A method for sending information, characterized in that, Including: The second relay terminal receives target information sent by the remote terminal through the first child node, where the first child node is a relay terminal connected to the second relay terminal in the relay link and located between the second relay terminal and the remote terminal; The second relay terminal sends the target information to the network device; Wherein, the second relay terminal is connected to the network device, and the relay link is the relay link between the remote terminal and the network 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. The method according to any one of claims 9-11, characterized in that, 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 device.

13. The method according to claim 12, characterized in that, After the second relay terminal receives the third message sent by the first child 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 an 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, characterized in that, 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 an RRC procedure.

15. The method according to claim 13 or 14, characterized in that, After the second relay terminal sends a third relay request to the network-side device through an 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 a PC5 RLC channel.

16. The method according to any one of claims 13 - 15, characterized in that, After the second relay terminal sends a third relay request to the network-side device through an 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, characterized in that, 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. A method for sending information, characterized in that, 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 the 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, characterized in that, 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, characterized in that, 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, characterized in that, 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 initiating entering a connected state includes 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 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 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, characterized in that, After the third relay terminal sends a fourth relay request to the network 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 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, characterized in that, After the third relay terminal sends a fourth relay request to the network device through an RRC procedure, the method further includes: The third relay terminal receives fourth configuration information sent by the network 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, characterized in that, Before the third relay terminal sends the target information to the network device through the second parent node, the method further includes: The third relay terminal receives fifth configuration information sent by the network 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, characterized in that, Including: The remote terminal sends target information to the network device through at least two relay terminals; Wherein, the relay link between the remote terminal and the network 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 device.

30. The method according to claim 29, wherein Before the remote terminal sends target information to the network 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, characterized in that, 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, characterized in that, 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, characterized in that, 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, characterized in that, 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, characterized in that, 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; 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.

36. A communication device, characterized in that, It includes a processor and a memory, and the memory stores programs or instructions that can run on the processor. 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, characterized in that, The chip includes a processor and a communication interface, and the communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the steps of the information sending method according to any one of claims 1-8, or the steps of the information sending method according to any one of claims 9-17, or the steps of the information sending method according to any one of claims 18-28, or the steps of the information sending method according to any one of claims 29-31.

38. A readable storage medium, characterized in that, Programs or instructions are stored on the readable storage medium. 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