Wireless communication method, device, and storage medium

Abstract

Embodiments of the present application provide a wireless communication method, a device, and a storage medium. The method comprises: a first terminal device sends first information to a network device, wherein the first information is used for determining second information, the second information comprises first configuration information corresponding to each of one or more terminal devices on a multi-hop link, the one or more terminal devices comprise a remote device and / or one or more relay devices, and the second information is used by the relay device to determine a data routing manner.

Description

A wireless communication method and device, storage medium TECHNICAL FIELD

[0001] Embodiments of the present application relate to the field of mobile communication technology, and in particular to a wireless communication method and device, storage medium. BACKGROUND

[0002] Device to Device (D2D) communication is a kind of Sidelink (SL) transmission technology, which is different from the way of receiving or sending communication data through a base station in a cellular system, and D2D uses a terminal-to-terminal direct communication mode, thus having higher spectrum efficiency and lower transmission delay.

[0003] D2D supports a single-hop scenario, in which only data transmission between a Remote UE and a network needs to be considered. In related technologies, a multi-hop relay scenario is introduced, in which the Remote UE and the network include multiple relay devices.

[0004] SUMMARY

[0005] Embodiments of the present application provide a wireless communication method and device, storage medium.

[0006] The wireless communication method provided by the embodiments of the present application comprises:

[0007] The first terminal device sends first information to a network device;

[0008] The first information is used to determine second information, and the second information includes first configuration information corresponding to each of one or more terminal devices on a multi-hop link, the one or more terminal devices including a Remote UE and / or one or more relay devices, and the second information is used by the relay device to determine a routing mode of data.

[0009] The wireless communication method provided by the embodiments of the present application comprises:

[0010] The network device receives first information sent by a first terminal device;

[0011] The first information is used to determine second information, and the second information includes first configuration information corresponding to each of one or more terminal devices on a multi-hop link, the one or more terminal devices including a Remote UE and / or one or more relay devices, and the second information is used by the relay device to determine a routing mode of data.

[0012] The first terminal device provided by the embodiments of the present application comprises:

[0013] The first communication unit is configured to send first information to a network device;

[0014] The first information is used to determine second information, the second information including first configuration information corresponding to each of one or more terminal devices on a multi-hop link, the one or more terminal devices including a remote device and / or one or more relay devices, the second information being used by the relay device to determine a routing manner of data.

[0015] The network device provided by the embodiments of the present application includes:

[0016] The second communication unit is configured to receive first information sent by a first terminal device;

[0017] The first information is used to determine second information, the second information including first configuration information corresponding to each of one or more terminal devices on a multi-hop link, the one or more terminal devices including a remote device and / or one or more relay devices, the second information being used by the relay device to determine a routing manner of data.

[0018] The communication device provided by the embodiments of the present application can be the first terminal device in the above scheme or the network device in the above scheme, and the communication device includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the wireless communication method.

[0019] The chip provided by the embodiments of the present application is used to implement the wireless communication method.

[0020] Specifically, the chip includes a processor configured to call and run a computer program from a memory, so that a device installed with the chip executes the wireless communication method.

[0021] The computer readable storage medium provided by the embodiments of the present application is used to store a computer program, and the computer program causes a computer to execute the wireless communication method.

[0022] The computer program product provided by the embodiments of the present application includes computer program instructions, and the computer program instructions cause a computer to execute the wireless communication method.

[0023] The computer program provided by the embodiments of the present application, when running on a computer, causes the computer to execute the wireless communication method.

[0024] By the technical solution, the first terminal device reports the first information to the network device, so that the network device determines the first configuration information of each terminal device in the one or more terminal devices on the multi-hop link, thereby realizing the configuration information in the multi-hop link including multiple relay UEs, and realizing the multi-hop U2N relay. BRIEF DESCRIPTION OF DRAWINGS

[0025] The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and serve to explain the principles of the application, and do not limit the application. In the drawings:

[0026] FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present application;

[0027] FIG. 2 is a schematic diagram of an optional scenario of D2D communication of an embodiment of the present application;

[0028] FIG. 3 is a schematic diagram of an optional scenario of D2D communication of an embodiment of the present application;

[0029] FIG. 4 is a schematic diagram of a sidelink-based L2 relay UE user plane protocol stack of an embodiment of the present application;

[0030] FIG. 5 is a schematic diagram of a sidelink-based L2 relay UE control plane protocol stack of an embodiment of the present application;

[0031] FIG. 6A is a schematic diagram of an optional flow of a wireless communication method of an embodiment of the present application;

[0032] FIG. 6B is a schematic diagram of an optional flow of a wireless communication method of an embodiment of the present application;

[0033] FIG. 6C is a schematic diagram of an optional flow of a wireless communication method of an embodiment of the present application;

[0034] FIG. 7A is a schematic diagram of an optional flow of a wireless communication method of an embodiment of the present application;

[0035] FIG. 7B is a schematic diagram of an optional flow of a wireless communication method of an embodiment of the present application;

[0036] FIG. 8A is a schematic diagram of an optional flow of a wireless communication method of an embodiment of the present application;

[0037] FIG. 8B is a schematic diagram of an optional flow of a wireless communication method of an embodiment of the present application;

[0038] FIG. 8C is a schematic diagram of an optional flow of a wireless communication method of an embodiment of the present application;

[0039] FIG. 9 is a schematic diagram of an optional flow of a wireless communication method of an embodiment of the present application;

[0040] FIG. 10 is an optional flow chart of a wireless communication method according to an embodiment of the present application;

[0041] FIG. 11 is an optional flow chart of a multi-hop link according to an embodiment of the present application;

[0042] FIG. 12 is an optional flow chart of a multi-hop link according to an embodiment of the present application

[0043] FIG. 13A is an optional flow chart of a wireless communication method according to an embodiment of the present application;

[0044] FIG. 13B is an optional flow chart of a wireless communication method according to an embodiment of the present application;

[0045] FIG. 14A is an optional flow chart of a wireless communication method according to an embodiment of the present application;

[0046] FIG. 14B is an optional flow chart of a wireless communication method according to an embodiment of the present application;

[0047] FIG. 15A is an optional flow chart of a wireless communication method according to an embodiment of the present application;

[0048] FIG. 15B is an optional flow chart of a wireless communication method according to an embodiment of the present application;

[0049] FIG. 16 is an optional flow chart of a packet header conversion according to an embodiment of the present application;

[0050] FIG. 17 is an optional structure diagram of a first terminal device according to an embodiment of the present application;

[0051] FIG. 18 is an optional structure diagram of a network device according to an embodiment of the present application;

[0052] FIG. 19 is an optional structure diagram of a communication device according to an embodiment of the present application;

[0053] FIG. 20 is an optional structure diagram of a chip according to an embodiment of the present application;

[0054] FIG. 21 is an optional block diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION

[0055] The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all of the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of protection of the present application.

[0056] FIG. 1 is a schematic diagram of an application scenario according to an embodiment of the present application.

[0057] As shown in FIG. 1, the communication system 100 can include a terminal device 110 and a network device 120. The network device 120 can communicate with the terminal device 110 over an air interface. The terminal device 110 and the network device 120 support multi-service transmission.

[0058] It should be understood that the embodiments of the present application are only exemplarily described with the communication system 100, but the embodiments of the present application are not limited thereto. That is, the technical solutions of the embodiments of the present application can be applied to various communication systems, for example: a Long Term Evolution (LTE) system, an LTE Time Division Duplex (TDD), a Universal Mobile Telecommunication System (UMTS), an Internet of Things (IoT) system, a Narrow Band Internet of Things (NB-IoT) system, an enhanced Machine-Type Communications (eMTC) system, a 5th generation (5G) communication system (also referred to as a New Radio (NR) communication system), or a future communication system, etc.

[0059] In the communication system 100 shown in FIG. 1, the network device 120 can be an access network device that communicates with the terminal device 110. The access network device can provide communication coverage for a specific geographic area and can communicate with the terminal device 110 (for example, a UE) located in the coverage area.

[0060] The terminal device 110 can be any terminal device, including but not limited to a terminal device that uses a wired or wireless connection with the network device 120 or other terminal devices.

[0061] The terminal device 110 can be used for D2D communication. At this time, the terminal devices 110 can perform sidelink communication.

[0062] The wireless communication system 100 can further include a core network device 130 that communicates with the base station.

[0063] The various functional units in the communication system 100 can also communicate through a next generation (NG) interface to establish a connection and implement communication.

[0064] Fig. 1 exemplarily shows one base station, one core network device and two terminal devices. Optionally, the wireless communication system 100 can include multiple base stations and each base station can include other number of terminal devices within its coverage. The embodiments of the present application do not limit this.

[0065] It should be noted that Fig. 1 is only schematically shown as an example of the system to which the embodiments of the present application are applicable. Of course, the method shown in the embodiments of the present application can also be applicable to other systems. In addition, the terms "system" and "network" are often used interchangeably in the present application. The term "and / or" in the present application is only used to describe the associated relationship of the associated objects. It means that there can be three relationships, for example, A and / or B can represent the following three cases: A exists alone, A and B exist together, and B exists alone. In addition, the character " / " in the present application generally represents an "or" relationship between the associated objects. It should also be understood that the "indication" mentioned in the embodiments of the present application can be direct indication or indirect indication, or can represent an associated relationship. For example, A indicates B can mean that B can be obtained by A directly; or A indirectly indicates B, for example, A indicates C, and B can be obtained by C; or A and B have an associated relationship. It should also be understood that the "corresponding" mentioned in the embodiments of the present application can represent a direct corresponding or indirect corresponding relationship between the two, or can represent an associated relationship between the two, or can mean an indication and being indicated, a configuration and being configured, etc. It should also be understood that the "predefined" or "predefined rule" mentioned in the embodiments of the present application can be realized by pre-saving the corresponding code, table or other means that can be used to indicate the relevant information in the device (for example, including terminal device and network device). The specific implementation manner of the present application is not limited. For example, the predefined can mean the definition in the protocol. It should also be understood that the "protocol" in the embodiments of the present application can mean the standard protocol in the communication field, for example, it can include the LTE protocol, the NR protocol and the related protocol applied to the future communication system. The present application does not limit this.

[0066] In order to facilitate the understanding of the technical solutions of the embodiments of the present application, the related technologies of the embodiments of the present application are described as follows. The following related technologies can be combined with the technical solutions of the embodiments of the present application in any way, and all of them belong to the protection scope of the embodiments of the present application.

[0067] LTE D2D / vehicle to other device (Vehicle to Everything, V2X)

[0068] Device to device communication is a kind of SL transmission technology based on D2D, which is different from the way of receiving or sending communication data through the base station in the traditional cellular system. The vehicle networking system adopts the way of terminal to terminal direct communication, so it has higher spectrum efficiency and lower transmission delay. In 3GPP, two transmission modes are defined: mode A and mode B.

[0069] Mode A: the transmission resource of the terminal is allocated by the base station, and the terminal transmits data on the sidelink according to the resource allocated by the base station; the base station can allocate single transmission resource for the terminal, or semi-static transmission resource for the terminal. As shown in FIG. 2, the base station 210 allocates grant resource (Grant) for the terminal device 220 and the terminal device 230, and the terminal device 220 and the terminal device 230 transmit data based on the Grant allocated by the base station.

[0070] Mode B: the terminal selects a resource in the resource pool for data transmission. As shown in FIG. 3, the terminal device 220 and the terminal device 230 transmit data based on the resource obtained from the resource pool.

[0071] D2D is divided into the following different stages for research: proximity service (ProSe), VX2, further enhancement of terminal direct communication technology (FeD2D).

[0072] ProSe: for public safety type services.

[0073] In ProSe, by configuring the location of the resource pool in the time domain, for example, the resource pool is discontinuous in the time domain, the UE can discontinuously transmit / receive data on the sidelink, thereby achieving the effect of power saving.

[0074] V2X: researches the scenario of vehicle to vehicle communication, and faces the business of high-speed vehicle to vehicle and vehicle to person communication;

[0075] In V2X, since the vehicle system has continuous power supply, power efficiency is not the main problem, but the delay of data transmission is the main problem, so the terminal device is required to transmit and receive continuously in system design.

[0076] FeD2D: researches the scenario of wearable devices accessing the network through mobile phones, which mainly faces the scene of low mobile speed and low power access.

[0077] In FeD2D, 3GPP concluded that the base station can configure the DRX parameters of the remote terminal through a relay terminal in the pre-research stage, but since the issue has not further entered the standardization stage, the specific details of how to configure the DRX are not concluded.

[0078] NR V2X

[0079] NR V2X is based on LTE V2X, not limited to broadcast scenarios, but further expanded to unicast and groupcast scenarios, and the application of V2X in these scenarios is studied.

[0080] Similar to LTE V2X, NR V2X also defines two resource authorization modes, mode-1 / 2; that is, in mode-1, the base station allocates resources for terminal devices to use for data communication, and in mode-2, the terminal device selects resources from the resource pool. Further, users can be in a mixed mode, that is, they can use mode-1 to obtain resources and also use mode-2 to obtain resources. The resource acquisition is indicated by the way of sidelink authorization, that is, the sidelink authorization indicates the time-frequency location of the corresponding PSCCH and PSSCH resources.

[0081] Unlike LTE V2X, in addition to feedback-free, terminal-initiated HARQ retransmission, NR V2X introduces feedback-based HARQ retransmission, not limited to unicast communication, but also including groupcast communication.

[0082] UE-to-Network Relay (U2N)

[0083] The protocol stacks of the user plane and control plane of the Layer 2 (L2) U2N relay architecture are shown in FIG. 4 and FIG. 5. For L2 U2N relay, the sidelink relay adaptation protocol (SRAP) sublayer is on top of the radio link control (RLC) sublayer of the control plane and user plane at the PC5 interface and the Uu interface. The Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), and Radio Resource Control (RRC) sublayers of the Uu interface terminate between the remote UE of the U2N relay and the gNB, while the SRAP, Radio Link Control (RLC), Medium Access Control (MAC), and physical (PHY) sublayers terminate at each link, i.e., the link between the remote UE of the U2N relay and the U2N relay UE, and the link between the U2N relay UE and the gNB.

[0084] For L2 U2N relay, the SRAP sublayer on the PC5 interface is only used for bearer mapping. For Broadcast Control Channel (BCCH) and Paging Control Channel (PCCH) messages targeting the remote UE, the SRAP sublayer does not exist on the PC5 interface. For signalling radio bearer 0 (SRB0) messages targeting the remote UE, the SRAP sublayer also does not exist on the PC5 interface, but the SRAP sublayer exists on the uplink and downlink of the Uu interface.

[0085] For L2 U2N relay, for uplink:

[0086] The Uu interface SRAP sublayer of the relay UE supports the bearer mapping from the RLC channel on the PC5 interface to the RLC channel on the Uu interface by the relay UE. For uplink relay traffic, different end-to-end bearers (SRB or DRB) of the same remote UE and / or different remote UEs can be multiplexed on the same RLC channel of the Uu interface;

[0087] The Uu interface SRAP sublayer of the gNB supports the remote UE identity identification of the gNB for uplink data. The bearer information and UE identity information of the remote UE are contained in the SRAP header of the Uu interface, so that the gNB associates the received data packet to the specific PDCP entity of the correct remote UE;

[0088] The PC5 interface SRAP sublayer of the remote UE supports the mapping between the radio bearers of the remote UE and the RLC channels of the PC5 interface.

[0089] For L2 U2N relaying, for downlink:

[0090] The Uu interface SRAP sublayer of the gNB supports the downlink bearer mapping of the gNB to map the radio bearers (SRB and data radio bearers (DRB)) of the remote UE to the RLC channels of the Uu interface through the Uu interface of the relay UE. The SRAP sublayer of the Uu interface can be used to map and multiplex multiple radio bearers (SRB and DRB) of the remote UE and / or different remote UEs to one RLC channel on the Uu interface of the relay UE.

[0091] The Uu interface SRAP sublayer of the relay UE supports the remote UE identification of the downlink data. The gNB can put the index information of the remote UE radio bearer and the identity information of the remote UE into the SRAP header of the Uu interface, so that the relay UE can map the received data packet of the radio bearer facing a specific remote UE to the associated RLC channel of the PC5 interface.

[0092] The PC5 interface SRAP sublayer of the relay UE supports the mapping between the radio bearers of the remote UE and the RLC channels of the PC5 interface.

[0093] The remote UE identity information is configured by the gNB for the relay UE to fill in the SRAP header. And the gNB avoids the conflict in allocating the remote UE identity information, for example, the gNB can send the updated remote UE identity information to the relay UE through the RRC reconfiguration message. Further, the gNB can perform the remote UE identity information update independently of the layer 2 identity information update process on the PC5 unicast link.

[0094] Before the user plane data transmission, the remote UE needs to establish its own PDU session and radio bearer with the network.

[0095] The D2D supports a single-hop scenario, in which only the data transmission between the remote device (Remote UE) and the network needs to be considered. In the related art, a multi-hop relay scenario is introduced, in which the Remote UE and the network include multiple relay devices.

[0096] In order to facilitate the understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined with the technical solutions of the embodiments of the present application as optional solutions, which all belong to the protection scope of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0097] The embodiment of the present application provides a wireless communication method, as shown in FIG. 6A, which comprises the following steps:

[0098] S601, a first terminal device sends first information to a network device;

[0099] The first information is used for determining second information, and the second information comprises first configuration information corresponding to each terminal device in one or more terminal devices on a multi-hop link, the one or more terminal devices comprising a remote device and / or one or more relay devices, and the second information is used for the relay device to determine a routing mode of data.

[0100] The embodiment of the present application provides a wireless communication method, as shown in FIG. 6B, which comprises the following steps:

[0101] S610, a network device receives first information sent by a first terminal device;

[0102] The first information is used for determining second information, and the second information comprises first configuration information corresponding to each terminal device in one or more terminal devices on a multi-hop link, the one or more terminal devices comprising a remote device and / or one or more relay devices, and the second information is used for the relay device to determine a routing mode of data.

[0103] The wireless communication method described in FIG. 6A or FIG. 6B is described below.

[0104] In the embodiment of the present application, the first terminal device can be a remote UE or a relay UE. When the first terminal device is a relay UE, the first terminal device can be a last relay which can communicate with the network device through a Uu interface, or can be an intermediate relay which communicates with the network device through one or more relay UEs.

[0105] In the embodiment of the present application, the last relay can be considered as a relay device directly connected to the network device or a relay device with a logical position closest to the network device in the multi-hop link, and the last relay can directly receive a message sent by the network device or directly send a message to the network device.

[0106] In the embodiment of the present application, the multi-hop link between the remote UE and the network device can comprise a plurality of relay UEs.

[0107] In an example, as shown in FIG. 6C, the communication system includes: the UE 110-1, the UE 110-2, the UE 110-3 and the UE 110-4, wherein the UE 110-4 is a remote UE, the UE 110-1, the UE 110-2 and the UE 110-3 are relay UEs, and the UE 110-1 is a last relay, and the UE 110-2 and the UE 110-3 are intermediate relays.

[0108] In the embodiments of the present application, among the two terminal devices connected through the PC5 interface, the terminal device close to the network device is the parent node of the other terminal device, and the other terminal device is the child node of the terminal device close to the network device.

[0109] In an example, as shown in FIG. 6A, the UE 110-1 is the parent node of the UE 110-2, and the UE 110-2 is the child node of the UE 110-1; the UE 110-2 is the parent node of the UE 110-3, and the UE 110-3 is the child node of the UE 110-2; and the UE 110-3 is the parent node of the UE 110-4, and the UE 110-4 is the child node of the UE 110-3.

[0110] It can be understood that, in FIG. 6C, the remote UE communicates with the network device through 3 hops, and in actual application, the number of hops through which the remote UE communicates with the network device can be any number greater than 1 other than 3.

[0111] The first information can be understood as information sent by the first terminal device to the network device for determining the second information. The second information can include first configuration information of one or more terminal devices in the multi-hop link, for the relay device to determine the routing mode of data.

[0112] In the embodiments of the present application, the first configuration information can be understood as configuration information allocated or configured by the network device for the terminal device.

[0113] In the embodiments of the present application, the configuration information used by the relay device to determine the routing mode of data can be understood as used by the SRAP entity to determine the routing path of the uplink data or downlink data based on the configuration information when the uplink data or downlink data is received. The routing path includes an egress link and / or an RLC channel.

[0114] In some embodiments, the configuration information of the terminal device comprises a local device identifier and / or bearer configuration. The local device identifier can be understood as a temporary device ID used to identify the terminal device in the multi-hop link, and used to identify the transmission end of data. The bearer configuration is used for bearer mapping. In the embodiments of the present application, the local device identifier can be described as a Local UE ID or UE ID. In some embodiments, the bearer configuration comprises a bearer ID and / or an RLC channel configuration associated with the bearer and / or a bearer transmission direction.

[0115] It can be understood that the UE ID is used by the SRAP to determine the link, and the bearer ID is used to determine the RLC channel in the associated link.

[0116] The method for wireless communication provided by the embodiments of the present application comprises: a first terminal device reporting first information to a network device, so that the network device determines first configuration information of each terminal device in one or more terminal devices on a multi-hop link, thereby realizing the configuration information in the multi-hop link comprising a plurality of relay UEs, and realizing multi-hop U2N relaying.

[0117] In some embodiments, the node for determining the second information can comprise the network device, and can also comprise the network device and the terminal device.

[0118] If the node for determining the second information is the network device, the network device determines the second information based on the first information, and sends the determined second information to one or more terminal devices corresponding to the second information.

[0119] If the node for determining the second information is the network device and the terminal device, the terminal device can first determine the second configuration information of all or part of the terminal devices, and send the determined second configuration information of part or all of the terminal devices and the first information to the network device, so that the network device determines the second information based on the received information.

[0120] In some embodiments, the network device can determine the first configuration information of one or more terminal devices included in the second information in steps, or can determine the second information at one time.

[0121] Next, scenario one in which the network device determines the first configuration information of one or more terminal devices included in the second information in steps, and scenario two in which the network device determines the second information at one time are described.

[0122] Scenario one

[0123] In some embodiments, the first information comprises third information corresponding to each terminal device in the one or more terminal devices,

[0124] The first terminal device sends the first information to the network device, comprising:

[0125] The first terminal device sends a first message to the network device, the first message comprising third information corresponding to the second terminal device, the third information being used by the network device to allocate first configuration information corresponding to the second terminal device to the second terminal device.

[0126] In some embodiments, the first information comprises third information corresponding to each of the one or more terminal devices, and the network device receives the first information sent by the first terminal device, comprising:

[0127] The network device receives the first message sent by the first terminal device, the first message comprising third information corresponding to the second terminal device, the third information being used by the network device to allocate first configuration information corresponding to the second terminal device to the second terminal device.

[0128] The first message can be understood as a report. The first terminal device sends the first message to the network device to send the third information of the second terminal device to the network device, and the network device determines the first configuration information corresponding to the second terminal device based on the received third information of the second terminal device.

[0129] In some embodiments, the first terminal device is a parent node of the second terminal device; and / or,

[0130] The first terminal device is a relay device directly connected to the network device.

[0131] In an example, for the multi-hop link shown in FIG. 6C, the first terminal device is UE110-1, and the second terminal device is UE110-2, at this time, the first terminal device is a parent node of the second terminal device, and the first terminal device is the relay device closest to the network device.

[0132] In an example, for the multi-hop link shown in FIG. 6C, the first terminal device is UE110-2, and the second terminal device is UE110-3, at this time, the first terminal device is a parent node of the second terminal device.

[0133] In an example, for the multi-hop link shown in FIG. 6C, the first terminal device is UE110-3, and the second terminal device is UE110-4, at this time, the first terminal device is a parent node of the second terminal device.

[0134] In an example, for the multi-hop link shown in FIG. 6C, the first terminal device is UE110-1, and the second terminal device is UE110-2, UE110-3, UE110-4.

[0135] It can be understood that the first terminal device is a parent node of the second terminal device, and different terminal devices in the multi-hop link can respectively send third information of the second terminal device to the network device as the first terminal device, so that the network device determines the first configuration information corresponding to different terminal devices based on the first message sent by different terminal devices.

[0136] It can be understood that the first terminal device is a last relay, and the terminal devices other than the last relay in the multi-hop link can respectively be the second terminal device, so that the third information of different terminal devices is sent to the network device through the last relay, so that the network device determines the first configuration information corresponding to different terminal devices based on the third information of different terminal devices.

[0137] In some embodiments, the first terminal device establishes an RRC connection with the network device.

[0138] Correspondingly, when the first terminal device establishes an RRC connection with the network device, the third information corresponding to the second terminal device is sent to the network device.

[0139] In some embodiments, the second terminal device is a remote device, and the first terminal device is a relay device directly connected to the network device.

[0140] Correspondingly, the last relay sends the third information of the remote UE to the network device, and the network device receives the third information of the remote UE sent by the last relay.

[0141] In some embodiments, the relay device between the second terminal device and the first terminal device does not have an RRC connection with the network device.

[0142] It can be understood that the intermediate relay does not have an RRC connection with the network device, at this time, the intermediate relay cannot send messages to the network device, and the network device cannot send messages to the terminal device, that is, the sending end and the destination of the message cannot be the intermediate relay and the network device.

[0143] At this time, the communication between the intermediate relay and the network device needs to pass through the forwarding of the nodes between the intermediate relay and the network device.

[0144] In an example, in the multi-hop link shown in FIG. 6C, there is no RRC connection between the UE 110-3, the UE 110-2 and the network device, but there is an RRC connection between the UE 110-1 and the network device, when the UE 110-3 sends a message to the network device, the message a needs to be sent to the UE 110-2, the UE 110-2 generates the message b after receiving the message a, and sends the message b to the UE 110-1, and the UE 110-1 sends the message b to the network device.

[0145] In some embodiments, the second terminal device is any terminal device in the multi-hop link, and the first terminal device is a parent node of the second terminal device.

[0146] Here, the second terminal device is any parent node in the multi-hop link, and there is an RRC connection between the second terminal device and the network device, when the intermediate relay enters the connected state, the third information of the child node is sent to the network device through the RRC connection between the intermediate relay and the network device.

[0147] It can be understood that the wireless communication method provided by the embodiments of the present application can be applied to the case where the intermediate relay enters the connected state or does not enter the connected state.

[0148] In some implementations, based on FIG. 6A, the method further includes:

[0149] The first terminal device receives a second message sent by the network device, and the second message contains the first configuration information corresponding to the second terminal device.

[0150] In some implementations, based on FIG. 6B, the method further includes:

[0151] The network device sends a second message to the first terminal device, and the second message contains the first configuration information corresponding to the second terminal device.

[0152] The second message is used to respond or feedback the first message. Wherein, the second message can be a report response.

[0153] The first message carries the third information of the second terminal device, and the second message responding to the first message carries the first configuration information of the second terminal device.

[0154] In some embodiments, the method further includes:

[0155] The first terminal device forwards the first configuration information corresponding to the second terminal device to the second terminal device.

[0156] Here, the first configuration information corresponding to the second terminal device is forwarded to the second terminal device by the first terminal device.

[0157] If the second terminal device is a child node of the first terminal device, the first terminal device sends the first configuration information of the second terminal device to the second terminal device through the PC5 interface.

[0158] If the second terminal device is a remote UE and the first terminal device is a last UE, the last UE forwards the configuration information of the remote UE to the remote UE through the forwarding of one or more intermediate relays between the remote UE and the last UE.

[0159] In some embodiments, the method further comprises:

[0160] The first terminal device receives a third message sent by the second terminal device, and the third message is used to request to establish an RRC connection of the second terminal device.

[0161] The first terminal device sends a fourth message to the network device, and the fourth message is determined based on the third message.

[0162] In some embodiments, the method further comprises:

[0163] The network device receives a fourth message sent by the first terminal device, and the fourth message is determined based on a third message, and the third message is used to request to establish an RRC connection of the second terminal device.

[0164] The third message is received by the first terminal device from the second terminal device.

[0165] The fourth message can be understood as a forwarded third message. The third message includes one of the following messages: RRC setup request (RRCSetupRequest), RRC resume request (RRCResumeRequest or RRCResumeRequest1), RRC reconfiguration completion message (RRCReconfigurationComplete), etc.

[0166] In the case where the first terminal device is a parent node of the second terminal device, the first terminal device receives a third message sent by a child node, and sends a forwarded third message to the network device, and the third message is used to request the child node to request to establish an RRC connection with the network device. Wherein, the third message can be triggered by the third message of the previous hop of the second terminal device requesting to establish an RRC connection. The first terminal device forwards a fourth message to the network device based on the received third message, to request to establish an RRC connection between the second terminal device and the network device. At this time, it can be considered that the third request of the child node of the second terminal device requesting to establish an RRC connection triggers the third message of the second terminal device, and it can be considered that the intermediate relay requests to enter a connected state.

[0167] In a case where the first terminal device is the last relay and the second terminal device is the remote UE, the remote sends a third message, and the third message passes through each intermediate relay in turn to the last relay. The third message is used to indicate that the remote UE requests to establish an RRC connection between the remote UE and the network device. Here, the intermediate relay including the child node of the first terminal device does not trigger a request to establish an RRC connection between the intermediate relay and the network device based on the third message of the remote, and it can be considered that the intermediate relay does not request to enter a connected state. The third message sent by the intermediate relay can be considered as a PC5 message, i.e., a first indication message, requesting to establish an RRC connection of the remote UE. It can be understood that the remote UE sends the third message to the parent node of the remote UE, and in a case where the parent node of the remote UE receives the third message, the parent node of the remote UE sends the first indication message to the next hop, so that the intermediate relay sends the first indication message to the next hop, until the last relay receives the first indication message sent by the child node of the last relay.

[0168] The third message can include third information of the second terminal device, so that the first terminal device receives the third information of the second terminal device.

[0169] In some embodiments, the method further includes:

[0170] The first terminal device establishes an RRC connection between the first terminal device and the network device in response to the third message.

[0171] The RRC connection establishment cause is determined based on the first terminal device, or based on the third message, or predefined.

[0172] In a case where the first terminal device does not establish an RRC connection with the network device, the first terminal device establishes an RRC connection with the network device in response to the received third message, and after establishing the RRC connection, sends a fourth message to the network device based on the established RRC connection.

[0173] In the embodiments of the present application, in a case where the first terminal device is an intermediate relay, after establishing an RRC connection with the network device in response to the received third message, the first terminal device sends a first message associated with the third message to the network device, wherein the third message for requesting to establish an RRC connection between the second terminal device and the network device includes third information of the second terminal device in the first message.

[0174] In some embodiments, the third message does not carry an SRAP packet header, and the fourth message carries an SRAP packet header.

[0175] In some embodiments, the SRAP header of the fourth message comprises one or more of the following:

[0176] a first local device identifier of the second terminal device, the first local device identifier being configured by the network device for the second terminal device;

[0177] a first bearer ID, the first bearer ID being default or predefined by the network device;

[0178] first indication information, the first indication information being used to indicate a transmission direction of the fourth message.

[0179] In some embodiments, the method further comprises:

[0180] receiving, by the first terminal device, a fifth message sent by the network device, the fifth message being used to indicate establishment of an RRC connection between the second terminal device and the network device;

[0181] sending, by the first terminal device, a sixth message to the second terminal device, the sixth message being determined based on the fifth message.

[0182] In some embodiments, the method further comprises:

[0183] sending, by the network device, a fifth message to the first terminal device, the fifth message being used to indicate establishment of an RRC connection between the second terminal device and the network device;

[0184] the fifth message being used to determine a sixth message, the sixth message being sent by the first terminal device.

[0185] In a case where the network device receives the fourth message, sending a fifth message to the first terminal device, the fifth message being used to indicate establishment of an RRC connection between the second terminal device and the network device.

[0186] In a case where the first terminal device is a parent node of the second terminal device, receiving, by the first terminal device, the fifth message, and sending, by the first terminal device, a sixth message to the second terminal device, the sixth message being used to indicate establishment of an RRC connection between a child node and the network device. The second terminal device enters a connected state.

[0187] In a case where the first terminal device is a last relay and the second terminal device is a remote UE, receiving, by the first terminal device, the fifth message, and sending, by the first terminal device, a sixth message to the second terminal device, the sixth message being used to indicate establishment of an RRC connection between the remote UE and the network device, the sixth message being forwarded by each intermediate relay in turn to reach the remote UE. Here, the intermediate relay does not enter a connected state.

[0188] In the embodiments of the present application, the sixth message can be understood as the forwarded fifth message. The fifth message can be an RRC connection establishment indication signaling in response to or feedback to the third message.

[0189] In some embodiments, the fifth message carries an SRAP header, and the sixth message does not carry an SRAP header.

[0190] In some embodiments, the fifth message includes the first configuration information corresponding to the second terminal device allocated by the network device.

[0191] At this time, the sixth message also includes the first configuration information corresponding to the second terminal device allocated by the network device, so that the second terminal device receives the first configuration information corresponding to the second terminal device determined by the network device based on the received sixth message.

[0192] In some embodiments, the SRAP header of the fifth message includes one or more of the following:

[0193] The first local device identifier of the second terminal device, which is configured by the network device for the second terminal device;

[0194] The first bearer ID, which is configured, default or predefined by the network device;

[0195] Second indication information, the second indication information is used to indicate the transmission direction of the fifth message.

[0196] In some embodiments, the first configuration information corresponding to the second terminal device is sent by the network device to all terminal devices except the second terminal device on the first link between the second terminal device and the network device.

[0197] For scenario one, the wireless communication method provided by the embodiments of the present application can be as shown in FIG. 7A or 7B, including:

[0198] S701, the second terminal device sends a third message to the first terminal device.

[0199] S702, the first terminal device sends a first message to the network device.

[0200] The first message carries the third information of the second terminal device.

[0201] Wherein, in the case that the first terminal device does not establish an RRC connection with the network device, after establishing an RRC connection with the network device, the first terminal device sends the first message to the network device.

[0202] S703, the network device sends a second message to the first terminal device.

[0203] The second message carries first configuration information of the second terminal device.

[0204] S704, the first terminal device sends a fourth message to the network device.

[0205] After the first terminal device receives the first configuration information of the second terminal device, the first terminal device can forward the third message of the second terminal device, that is, the first terminal device can send the fourth message.

[0206] S705, the network device sends a fifth message to the first terminal device.

[0207] S706, the first terminal device sends a sixth message to the second terminal device.

[0208] In FIG. 7A, the second terminal device is a child node of the first terminal device. The second terminal device establishes a process of RRC connection between the second terminal device and the network device from sending the third message to receiving the sixth message. The first terminal device is a relay node, and if the first terminal device needs to establish an RRC connection with the network device, the first terminal device can refer to the process shown in FIG. 7A to send a third message to a parent node of the first terminal device until receiving a sixth message sent by the parent node of the first terminal device.

[0209] The first terminal device is a last relay, and if the first terminal device needs to establish an RRC connection with the network device, the first terminal device sends a message for requesting an RRC connection to the network device, and completes the RRC connection establishment when receiving a message sent by the network device and indicating to establish the RRC connection.

[0210] The method shown in FIG. 7A above is a second information determination process in a case that an intermediate relay enters a connected state.

[0211] A second information determination process in a case that an intermediate relay does not enter a connected state can refer to a process shown in FIG. 7B.

[0212] S701, the remote terminal device sends a third message to the intermediate relay.

[0213] Here, the remote terminal device sends the third message to a parent node of the remote terminal device.

[0214] S701a, the intermediate relay sends a third message to the first terminal device, which can be understood as the third message forwarded by the intermediate relay.

[0215] In a case that the intermediate relay receives the third message, the intermediate relay sends a third message, and the third message is used to indicate that the remote terminal device requests to establish an RRC connection. The third message can carry third information of the remote terminal device.

[0216] S702, the first terminal device sends a first message to the network device.

[0217] The first terminal device sends the first message to the network device in the case of receiving the third message.

[0218] The first message carries the third information of the remote terminal device.

[0219] In the case that the first terminal device does not establish an RRC connection with the network device, the first terminal device sends the first message to the network device after establishing the RRC connection with the network device.

[0220] S703, the network device sends a second message to the first terminal device.

[0221] The second message carries the first configuration information of the remote terminal device.

[0222] S704, the first terminal device sends a fourth message to the network device.

[0223] After the first terminal device receives the first configuration information of the remote terminal device, the first terminal device can forward the third message of the remote terminal device, i.e., send the fourth message.

[0224] S705, the network device sends a fifth message to the first terminal device.

[0225] S706, the first terminal device sends a sixth message to the intermediate relay.

[0226] S706a, the intermediate relay sends the sixth message to the remote terminal device.

[0227] In FIG. 7B, an example of one intermediate relay is taken, and in actual application, multiple intermediate relays can be included between the first terminal device and the second terminal device. In S702a, the intermediate relay between the second terminal device and the first terminal device sends the third message to the next hop in the case of receiving the third message sent by the previous hop, until the first terminal device receives the third message; in S706a, the intermediate relay sends the sixth message to its child node in the case of receiving the sixth message, so that the second terminal device receives the sixth message.

[0228] Scenario two

[0229] In some embodiments, the first terminal device sends the first information to the network device, including:

[0230] The first terminal device sends a first message to the network device, the first message includes the first information, the first terminal device is a relay device directly connected to the network device, and the first information is used for the network device to allocate the second information.

[0231] In some embodiments, the network device receives first information sent by the first terminal device, including:

[0232] The network device receives a first message sent by the first terminal device, the first message including the first information, the first terminal device being a relay device directly connected to the network device, and the first information being used by the network device to allocate the second information.

[0233] Here, the first terminal device is a last relay, and the first message includes third information of all UEs, so that the network device can determine the configuration information, i.e., the second information, of all UEs.

[0234] For scenario two, the content included in the first message can include the following two cases:

[0235] Case one, the first message includes the first information;

[0236] Case two, the first message includes the first information and fourth information, wherein the fourth information includes configuration information configured by the fourth terminal device for all or part of one or more terminal devices.

[0237] Next, case one and case two are described respectively.

[0238] Case one

[0239] In some embodiments, the method further includes: the first terminal device receiving a second message sent by the network device, the second message including the second information.

[0240] In some embodiments, the method further includes:

[0241] The network device sends a second message to the first terminal device, the second message including the second information.

[0242] Here, the second message is used to respond or feedback the first message, and the second message can include the second information.

[0243] In some embodiments, based on FIG. 6A, the method further includes:

[0244] Before sending the first message, the first terminal device receives a third message sent by a second terminal device, the third message being used to request to establish an RRC connection between the second terminal device and the network device, or being used to indicate that a remote terminal device requests to establish an RRC connection with the network device, the second terminal device being one terminal device on the multi-hop link except the first terminal device.

[0245] The third message includes one of the following messages: an RRC setup request (RRCSetupRequest), an RRC resume request (RRCResumeRequest or RRCResumeRequest1), an RRC reconfiguration complete message (RRCReconfigurationComplete), and the like. In a possible implementation, the first terminal device receives the third message sent by the second terminal device, which can be understood as that the first terminal device receives the third message sent by the second terminal device, where the third message is used to request to establish an RRC connection of the second terminal device, and the second terminal device is a child node of the first terminal device. The third message can be triggered by the third message for requesting to establish an RRC connection of the previous hop of the second terminal device. The first terminal device forwards a fourth message to the network device based on the received third message, to request to establish an RRC connection between the second terminal device and the network device. At this time, it can be considered that the third request for requesting to establish an RRC connection of the child node of the second terminal device triggers the third message of the second terminal device, and it can be considered that the intermediate relay enters a connected state.

[0246] In an example, the terminal devices on the multi-hop link include: UE1, UE2, UE3, and UE4, the UE4 is the first terminal device, the UE1 sends a third message for requesting to establish an RRC connection of the UE1 to the UE2, the UE2 sends a third message for requesting to establish an RRC connection of the UE2 to the UE3 in response to the received third message, and the UE3 sends a third request message for requesting to establish an RRC connection of the UE3 to the UE4 in response to the received third message. In a possible implementation, the first terminal device receives the third message sent by the second terminal device, which can be understood as that the first terminal device receives the fourth message sent by the child node, the second terminal device is not a child node of the first terminal device, and the fourth message is the third message determined and forwarded based on the third message sent by the second terminal device. The second terminal device sends the third message to its parent node, the parent node sends a third message indicating that the parent node requests to establish an RRC connection based on the received third message, and sends a fourth message, i.e., forwards the third message, after establishing an RRC connection with the network device, so that the first terminal device receives the fourth message sent by the child node.

[0247] In a possible implementation, the first terminal device receiving the third message sent by the second terminal device can be understood as that the first terminal device receives the first indication message sent by the child node, the second terminal device is a remote terminal device, and the first indication message is used to indicate that the remote terminal device requests to establish an RRC connection, that is, the first indication message is used to indicate that the remote terminal device requests to establish an RRC connection with the network device. Here, the intermediate relay including the child node of the first terminal device does not trigger a request to establish an RRC connection between the intermediate relay and the network device based on the third message of the remote, and it can be considered that the intermediate relay does not request to enter a connection state. The first indication message here can be considered as a PC5 message requesting to establish an RRC connection of the remote UE.

[0248] In some embodiments, in the case of requesting to establish an RRC connection between the second terminal device and the network device, the third message or the first indication message can carry the third information of the self and the third information carried by the third message received from the last hop, so that the first terminal device receives the third information of all terminal devices on the multi-hop link.

[0249] In the embodiments of the present application, the first message includes the first information, the second message includes the second information, the last relay receives the second information, receives the first configuration information of all terminal devices in the one or more terminal devices, and the first terminal device sends the second information to each terminal device on the multi-hop link, at this time, each terminal device can forward the third message received by the child node.

[0250] In some embodiments, the third message includes one or more of the following:

[0251] The device identifier of the second terminal device and / or first indication information, the first indication information being used to indicate the reason for establishing an RRC connection by the second terminal device;

[0252] Second indication information, the second indication information being used to indicate the RRC connection establishment indication of the child node of the second terminal device.

[0253] In some embodiments, the method further includes:

[0254] The first terminal device sends the second information to the other terminal devices in the multi-hop link except the first terminal device; or,

[0255] The first terminal device sends the second information to a third terminal device, so that the second information is sent to the child node by the parent node in the multi-hop link in turn, and the third terminal device is a child node of the first terminal device.

[0256] Here, the first terminal device sends the first information to all terminal devices on the multi-hop link. The first terminal device sends the first information in a direct sending mode or a non-direct sending mode.

[0257] In the direct sending mode, the first terminal device sends the second information to terminal devices other than the first terminal device on the multi-hop link.

[0258] In an example, the terminal devices on the multi-hop link include UE1, UE2, UE3, and UE4, UE4 is the first terminal device, UE4 sends messages to UE3, UE2, and UE1 respectively, and the second information is carried in the sent messages.

[0259] In the direct sending mode, an RRC connection is required between the first terminal device and other terminal devices. The UE ID used in the end-to-end RRC message between the two UEs in the direct sending mode is default, configured by the relay UE, or configured by the remote UE.

[0260] In the non-direct sending mode, the second information is transmitted in turn at each node of the multi-hop link.

[0261] In an example, the terminal devices on the multi-hop link include UE1, UE2, UE3, and UE4, UE4 is the first terminal device, UE4 sends the second information to UE3, UE3 receives the second information and sends the second information to UE2 based on a new message, and UE2 receives the second information and sends the second information to UE1 based on a new message.

[0262] In the non-direct sending mode, a terminal device receives an RRC message sent by a parent node, generates a new RRC message, and sends the new RRC message to a child node.

[0263] In some embodiments, the method further includes:

[0264] The first terminal device sends a fourth message to the network device, the fourth message indicating to establish an RRC connection between the second terminal device and the network device, and the fourth message is determined based on the third message.

[0265] In some embodiments, the method further includes:

[0266] The network device receives a fourth message sent by the first terminal device, the fourth message indicating to establish an RRC connection between the second terminal device and the network device, the second terminal device being a terminal device other than the first terminal device on the multi-hop link, and the fourth message being determined based on the third message sent by the second terminal device.

[0267] In the case that the intermediate relay enters the connected state, if the first terminal device is a parent node of the second terminal device, and the third message received by the first terminal device is sent by the second terminal device to the network device, the first terminal device receives the third message sent by the second terminal device, and after the first terminal device establishes the RRC connection with the network device, the first terminal device sends the forwarded third message, i.e., the fourth message, to the network device.

[0268] In the case that the intermediate relay enters the connected state, if the first terminal device is not a parent node of the second terminal device, i.e., the case that one or more relay devices are included between the first terminal device and the second terminal device, the second terminal device sends the third message to the parent node, and after the parent node of the second terminal device establishes the RRC connection with the network device, the parent node sends the forwarded third message, i.e., the fourth message, to the network device. At this time, the first terminal device transmits the fourth message sent by the parent node of the second terminal device.

[0269] In the embodiments of the present application, in the case that the intermediate relay enters the connected state, the parent node of the second terminal device establishes the RRC connection with the network device in response to the third message received from the second terminal device, so as to enter the connected state. After the RRC connection is established, the parent node sends the fourth message to the network device.

[0270] In the case that the intermediate relay does not enter the connected state, the intermediate relay triggers a first indication message indicating that the remote terminal device requests to establish the RRC connection based on the third message sent by the remote terminal device, and sends the triggered first indication message to the parent node, so that the next-hop transmits the first indication message until the first indication message is sent to the first terminal device. After receiving the first indication message, the first terminal device sends the forwarded first indication message, i.e., the fourth message, to the network device.

[0271] In the case that the intermediate relay does not enter the connected state, the first terminal device establishes the RRC connection with the network device in response to the first indication message sent by the child node.

[0272] In the embodiments of the present application, the third message carries the third information of the first terminal device and the third information carried in the third message received from the child node, so that the first terminal device can obtain the third information of all UEs on the multi-hop link.

[0273] In some embodiments, the method further includes:

[0274] The first terminal device receives the fifth message sent by the network device.

[0275] The first terminal device transparently transmits the fifth message, or sends a sixth message, the sixth message being determined based on the fifth message that the sixth message is sent by the network device to the second terminal device, and the fifth message being used to indicate establishment of an RRC connection between the second terminal device and the network device,

[0276] The fifth message contains first configuration information corresponding to the second terminal device.

[0277] In some embodiments, the method further comprises:

[0278] The network device sends a fifth message to the first terminal device;

[0279] The fifth message is transparently transmitted by the first terminal device, or a sixth message is sent by the first terminal device, the sixth message being determined based on the fifth message that the sixth message is sent by the network device to the second terminal device, and the fifth message being used to indicate establishment of an RRC connection between the second terminal device and the network device;

[0280] The fifth message contains first configuration information corresponding to the second terminal device.

[0281] The network device sends a fifth message to the first terminal device in response to the received fourth message.

[0282] The first terminal device transparently transmits the fifth message or sends a forwarded fifth message, i.e., a sixth message, upon receiving the fifth message.

[0283] It can be understood that, in the case that the parent node of the second terminal device is not the first terminal device, and the parent node of the second terminal device establishes an RRC connection with the network device, the first terminal device transparently transmits the fifth message to the child node, so that the fifth message is transparently transmitted to the parent node of the second terminal device, and the parent node of the second terminal device sends a sixth message to the second terminal device.

[0284] In the case that the intermediate relay enters a connected state, if the first terminal device is the parent node of the second terminal device, the first terminal device establishes an RRC connection with the network device upon receiving the fifth message, but the second terminal device does not establish an RRC connection with the network device, and the first terminal device sends a sixth message to the second terminal device.

[0285] In the case that the intermediate relay enters the connected state, if the first terminal device is not the parent node of the second terminal device, i.e., the first terminal device and the second terminal device include one or more relay devices therebetween, the first terminal device receives the fifth message, transmits the fifth message to the next node, and the first terminal device and the parent node of the second terminal device transmit the fifth message to the parent node of the second terminal device. In the case that the parent node of the second terminal device receives the fifth message, the parent node of the second terminal device sends the sixth message to the second terminal device.

[0286] In the case that the intermediate relay does not enter the connected state, the first terminal device receives the fifth message, forwards the sixth message to the next node, and the next node continues to forward the new sixth message until the parent node of the remote terminal device sends the sixth message to the remote terminal device.

[0287] In the embodiments of the present application, the first configuration information corresponding to the second terminal device included in the fifth message can be the same as or different from the first configuration information corresponding to the second terminal device in the second information.

[0288] For the case one in the scenario two, the wireless communication method provided by the embodiments of the present application can be as shown in FIG. 8A or 8B or 8C, including:

[0289] S801, the third terminal device sends a third message to the first terminal device.

[0290] The third message can be used to request to establish an RRC connection between the network device and the network device. The third message can be triggered based on the third message sent by the child node of the network device to the second terminal device to request to establish an RRC connection.

[0291] The third message can also be used to indicate the RRC connection between the remote device and the network device.

[0292] The third message sent by one terminal device includes the third information of the terminal device itself and the third information included in the received third message, so that the first terminal device receives the third information of all UEs on the multi-hop link in the sent third message.

[0293] S802, the first terminal device sends a first message to the network device.

[0294] The first message carries the third information of all terminal devices on the multi-hop link.

[0295] S803, the network device sends a second message to the first terminal device.

[0296] The second message carries the second information.

[0297] S804, the first terminal device sends the second information to the third terminal device.

[0298] S805, the first terminal device sends a fourth message to the network device.

[0299] After the first terminal device receives the first configuration information of the third terminal device, the third message of the third terminal device can be forwarded, that is, the fourth message can be sent.

[0300] S806, the network device sends a fifth message to the first terminal device.

[0301] S807, the first terminal device sends a sixth message to the third terminal device.

[0302] In FIG. 8A, the third terminal device is a child node of the first terminal device, and the third terminal device is the same terminal device as the second terminal device. From sending the third message to receiving the sixth message, the third terminal device establishes a one-time process of RRC connection between the third terminal device and the network device.

[0303] The first terminal device is a last relay, and if the first terminal device needs to establish an RRC connection with the network device, the first terminal device sends a message for requesting an RRC connection to the network device, and completes the RRC connection establishment when receiving a message sent by the network device and indicating to establish the RRC connection.

[0304] The method shown in FIG. 8A above is the RRC connection process of the child node of the first terminal device in the case that the intermediate relay enters the connected state.

[0305] It should be noted that the processes of different terminal devices establishing RRC connections with the network device are similar, but the sending of the first message, the second message and the second information is common. As shown in FIG. 8B, the second terminal device sends a third message to the third terminal device, and triggers the third terminal device to send the third message to establish the RRC connection process of the third terminal device. After the third terminal device establishes the RRC connection with the network device, the fourth message is forwarded to the network device, and the sixth message is sent to the second terminal device in the case of receiving the fifth message sent by the network device. Wherein, the first terminal device performs the transparent transmission of the fourth message and the transparent transmission of the fifth message.

[0306] The determination process of the second information in the case that the intermediate relay does not enter the connected state can refer to the process shown in FIG. 8C.

[0307] S801, the remote terminal device sends a third message to a parent node.

[0308] S801a, the first terminal device receives first information sent by other terminal devices.

[0309] The intermediate relay generates a new RRC message based on the received third information of the child node and its own third information and sends it to the parent node.

[0310] S802, the first terminal device sends a first message to the network device.

[0311] The first terminal device sends the first message to the network device upon receiving the first information. The first message carries the first information.

[0312] S903, the network device sends a second message to the first terminal device.

[0313] The second message carries second information.

[0314] S804, the first terminal device sends the second information to the terminal device on the multi-hop link.

[0315] S805, the first terminal device sends a fourth message to the network device.

[0316] After the first terminal device receives the first configuration information of the remote terminal device, it can forward the third message of the remote terminal device, i.e., send the fourth message.

[0317] S806, the network device sends a fifth message to the first terminal device.

[0318] S807, the sixth message is sent to the remote terminal device through the first terminal device and the intermediate relay in turn.

[0319] Case two

[0320] In some embodiments, the first message includes the first information and fourth information of one or more fourth terminal device configurations.

[0321] The fourth information includes second configuration information for part or all of the one or more terminal devices, and the fourth information is used by the relay device to determine the routing mode of data. The fourth terminal device is one of the terminal devices on the multi-hop link.

[0322] In case two, the fourth terminal device is a terminal device on the multi-hop link that can determine configuration information for terminal devices. The fourth terminal device can be a remote UE, an intermediate relay, or a last relay, i.e., the first terminal device.

[0323] In an example, the first terminal device allocates configuration information, i.e., second configuration information, to each of all terminal devices on the multi-hop link.

[0324] In an example, the intermediate relay determines the second configuration information of its child node and parent node.

[0325] In an example, two intermediate relays respectively determine the second configuration information of their own child node and parent node.

[0326] In the embodiments of the present application, the second configuration information determined by one or more fourth terminal devices can be referred to as fourth information.

[0327] In some embodiments, the first configuration information corresponding to the fifth terminal device includes the second configuration information or / and third configuration information, the third configuration information being configuration information reconfigured by the network device based on third information of the fifth terminal device in the first information, the fifth terminal device being one terminal device in the one or more terminal devices.

[0328] Here, for one terminal device, its first configuration information can only include third configuration information reconfigured by the network device based on third information of the terminal device, can also be second configuration information of the fifth terminal device determined by the fourth terminal device reused by the network device, and can further include third configuration information and second configuration information of the terminal device.

[0329] It can be understood that, in the embodiments of the present application, the fourth information can include second configuration information of all or part of terminal devices determined by the fourth terminal device.

[0330] In an example, the first terminal device determines second configuration information of all terminal devices, and the fourth information includes second configuration information of all terminal devices.

[0331] In an example, terminal devices on a multi-hop link include UE1, UE2, UE3 and UE4, UE4 is the first terminal device, UE2 determines second configuration information of UE1 and UE3, and the fourth information includes second configuration information of UE1 and UE3.

[0332] In an example, terminal devices on a multi-hop link include UE1, UE2, UE3 and UE4, UE4 is the first terminal device, UE2 determines second configuration information of UE1 and UE3, UE3 determines second configuration information of UE2 and UE4, and the fourth information includes second configuration information of UE1, UE2, UE3 and UE4.

[0333] In an example, terminal devices on a multi-hop link include UE1, UE2, UE3 and UE4, UE4 is the first terminal device, UE2 determines second configuration information of UE1 and UE3, UE3 determines second configuration information of UE2 and UE4, and the fourth information includes second configuration information of UE1 and UE3.

[0334] In some embodiments, the first configuration information includes the second configuration information and the third configuration information,

[0335] The Uu link performs data transmission based on the third configuration information, and the PC5 link performs data transmission based on the second configuration information; or

[0336] The multi-hop link performs data transmission based on the second configuration information.

[0337] The link between the network device and the terminal device performs data transmission based on the third configuration information, and the link between the two terminal devices performs data transmission based on the second configuration information.

[0338] If the Uu link performs data transmission based on the third configuration information, and the PC5 link performs data transmission based on the second configuration information, the second configuration information configured by the fourth terminal device is used on the PC5 link, that is, the network reconfiguration is only for transmission between the network, and the fourth terminal device uses different SRAP packet headers on the PC5 link and the Uu link. The fourth terminal device needs to maintain the mapping relationship of two sets of configurations and re-determine the SRAP packet header at the SRAP layer, so as to convert the SRAP packet header.

[0339] If the multi-hop link performs data transmission based on the second configuration information, it can be considered that if the network device reuses the second configuration information configured by the fourth terminal device, that is, the same configuration information, that is, the second configuration information, is used for each UE on the entire link, the information used by the fourth terminal device in the SRAP packet header is configured by the fourth terminal device.

[0340] If the link between the network device and the terminal device performs data transmission based on the third configuration information, and the link between the two terminal devices performs data transmission based on the second configuration information, the terminal device communicates with the network device, and the third configuration information reconfigured by the network device is used, and if the terminal device communicates with the terminal device, the second configuration information determined by the fourth terminal device is used. That is, the link / bearer with the PC5 node as the starting point and the terminal point uses the second configuration information configured by the fourth terminal device, and the configuration information used by the link / bearer with the network as the starting point or the terminal point is the third configuration information allocated by the network.

[0341] In some embodiments, the end-to-end communication between the terminal devices in the same terminal device group is based on the second configuration information determined by the corresponding fourth terminal device; or

[0342] The different fourth terminal devices allocate different second configuration information to the same terminal device, and the terminal device uses different second configuration information for data transmission on different PC5 links.

[0343] Among them, the fourth information of different terminal device groups is allocated based on different fourth terminal devices.

[0344] In the embodiments of the present application, one fourth terminal device determines the second configuration information of a plurality of terminal devices, and the terminal devices can be considered to belong to the same terminal device group. In the case that different fourth terminal devices determine the configuration information of the same terminal device, the terminal device has a plurality of second configuration information, and the plurality of second configuration information can be referred to as a configuration pair.

[0345] In the embodiments of the present application, for one configuration pair, the local device identifiers included can not coincide or the local device identifiers can coincide but the RLC channels need to be distinguished.

[0346] In some embodiments, the method further includes:

[0347] The first terminal device receives a second message sent by the network device, and the second message includes the second information.

[0348] In some embodiments, the method further includes: the network device sends a second message to the first terminal device, and the second message includes the second information.

[0349] The network device can determine the first configuration information of the terminal devices according to the third information included in the first information and the terminal devices corresponding to the second configuration information, and at this time, the second information includes the first configuration information of the terminal devices.

[0350] The network device sends the first information to the first terminal device, so that the first terminal device establishes the RRC connection between one or more terminal devices and the network device based on the obtained first configuration information.

[0351] In some embodiments, for the first terminal device, the method further includes:

[0352] The first terminal device receives a third message sent by a second terminal device before sending the first message, and the third message is used to request to establish the RRC connection between the third terminal device and the network device.

[0353] The third message is used to request to establish the RRC connection between the second terminal device and the network device.

[0354] The third message does not carry the SRAP packet header.

[0355] The second terminal device is any terminal device except the first terminal device in the multi-hop link. In some embodiments, the second terminal device has data that needs to be relayed, and sends the third message to the parent node, and the third message carries the data that needs to be relayed, at this time, the parent node of the second terminal device forwards the third message, that is, sends a fourth message, and the fourth message carries the SRAP packet header.

[0356] In the embodiments of the present application, the intermediate relay can or can not enter the connected state. When the intermediate relay enters the connected state, the second terminal device sends a third message to the parent node, and the intermediate relay, in response to the third message, sends the third message to its parent node to establish an RRC connection between itself and the network device, thereby entering the connected state. In the case where the intermediate relay does not enter the connected state, the third message can be sent to the first terminal device through non-direct communication between the intermediate relay and the first terminal device, or the third message can be sent to the parent node, and the parent node is triggered to send a third message indicating that the remote terminal device requests to establish an RRC connection.

[0357] In the embodiments of the present application, the path for the remote device to send the third message and send the third message to the first terminal device is not limited.

[0358] If the intermediate relay enters the connected state and the second terminal device is a child node of the first terminal device, the first terminal device receiving the third message can be understood as that the first terminal device receives the third message sent by the child node, requesting the second terminal device to establish an RRC connection.

[0359] If the intermediate relay enters the connected state and the second terminal device is not a child node of the first terminal device, the first terminal device receiving the third message can be understood as that the first terminal device receives a fourth message sent by the child node, the fourth message being the forwarded third message, and the fourth message being used to indicate that the third terminal device requests to establish an RRC connection. Here, the second terminal device sends the third message to its parent node, and the parent node, upon receiving the third message, sends a fourth message to the next hop, thereby transmitting the fourth message on the PC5 link until the first terminal device receives the fourth message.

[0360] If the intermediate relay does not enter the connected state and the second terminal device is a remote terminal device, the first terminal device receiving the third message can be understood as that the first terminal device receives a first indication message sent by the child node, the first indication message being used to indicate that the remote terminal device requests to establish an RRC connection, wherein the first indication message is determined based on the third message sent by the remote terminal device. Here, the remote terminal device sends the third message to its parent node, and the parent node, upon receiving the third message, sends a first indication message to the next hop, thereby transmitting the first indication message on the PC5 link until the first terminal device receives the first indication message.

[0361] In some embodiments, a non-direct end-to-end connection is established between the first terminal device and the remote terminal device.

[0362] In the embodiments of the present application, when the first terminal device and the remote device are both allocated second configuration information, the first terminal device and the second terminal device establish a non-direct end-to-end connection based on the second configuration information of both.

[0363] In some embodiments, the remote terminal device sends a DCR message to the first terminal device, requesting to establish a non-direct end-to-end connection; the first terminal device responds to the DCA, indicating to accept the establishment of the non-direct end-to-end connection.

[0364] In the embodiments of the application, the DCR message can carry an SRAP packet header. The SRAP packet header includes:

[0365] a remote UE ID of the remote terminal device and / or a UE ID of the first terminal device;

[0366] a BEARER ID, which is default, protocol specified, or relay UE configured, or remote UE determined.

[0367] In the embodiments of the application, the DCA message can carry an SRAP packet header. The SRAP packet header includes:

[0368] a remote UE ID of the remote terminal device and / or a UE ID of the first terminal device;

[0369] a BEARER ID, which is default, protocol specified, or relay UE configured, or remote UE determined.

[0370] For DCR and DCA, the source and destination have changed.

[0371] In some embodiments, the first message includes fourth information of a plurality of fourth terminal devices,

[0372] The non-direct end-to-end communication is established between the child node of the fourth terminal device and the parent node of the fourth terminal device, wherein the second configuration information of the child node of the fourth terminal device and the second configuration information of the parent node of the fourth terminal device are allocated by the fourth terminal device.

[0373] In an example, the terminal devices on the multi-hop link include: UE1, UE2, UE3 and UE4, UE4 is the first terminal device, and after UE2 determines the second configuration information of UE1 and UE3, the non-direct end-to-end communication can be established between UE1 and UE3.

[0374] Here, the non-direct end-to-end communication between the child node of the fourth terminal device and the parent node of the fourth terminal device can be based on the interaction between the child node of the fourth terminal device and the parent node of the fourth terminal device about DCR and DCA, which will not be described here.

[0375] In some embodiments, the method further includes:

[0376] The first terminal device sends a fourth message to the network device, the fourth message being determined based on the third message. In some embodiments, the method further comprises:

[0377] The network device receives the fourth message sent by the first terminal device, the fourth message being determined based on the third message sent by the second terminal device, the third message being used to request to establish the RRC connection between the second terminal device and the network device.

[0378] The first terminal device receives the third message and the second information sent by the network device, and sends a fourth message, the fourth message being used to indicate that the second terminal device requests to establish the RRC connection.

[0379] If the intermediate relay enters the connected state, the second terminal device can be any terminal device on the multi-hop link except the first terminal device, and the first terminal device forwards the corresponding fourth message to the network device according to the order of the received third message or fourth message, so as to establish the RRC connection between each terminal device on the multi-hop link except the first terminal device and the network device.

[0380] Wherein, in the case that the intermediate relay enters the connected state and the second terminal device is a child node of the first terminal device, the first terminal device forwards the third message received from the child node to the network device as the fourth message. In the case that the intermediate relay enters the connected state and the second terminal device is not a child node of the first terminal device, the first terminal device forwards the fourth message received from the child node to the network device as the fourth message.

[0381] If the intermediate relay does not enter the connected state, the second terminal device is a remote terminal device, and the first terminal device forwards the corresponding fourth message to the network device according to the received first indication message indicating that the remote terminal device requests to establish the RRC connection, so as to establish the RRC connection between the remote terminal device and the network device. The first terminal device forwards the first indication message received from the child node to the network device as the fourth message.

[0382] In some embodiments, the method further comprises:

[0383] The first terminal device receives a fifth message sent by the network device, the fifth message being used to indicate to establish the RRC connection of the second terminal device, and the fifth message comprising the first configuration information corresponding to the second terminal device in the second information;

[0384] The first terminal device sends a sixth message to the second terminal device, the sixth message being determined based on the fifth message.

[0385] In some embodiments, the method further comprises:

[0386] The network device sends a fifth message to the first terminal device, the fifth message being used to instruct to establish an RRC connection of the second terminal device, and the fifth message comprising the first configuration information corresponding to the second terminal device in the second information;

[0387] The sixth message is sent by the first terminal device to the third terminal device, and the sixth message is determined based on the fifth message.

[0388] When the network device receives the fourth message sent by the first terminal device, the first terminal device responds to the fifth message, and the first terminal device sends the fifth message forwarded, i.e., the sixth message, to the second terminal device through an end-to-end link of a non-direct connection, or to a child node of the first terminal device, so as to send the sixth message to the second terminal device through the forwarding of each relay device.

[0389] For case 2, the bearer transmission on PC5 and the bearer transmission on Uu can be relatively independent. As shown in FIG. 9, the case 2 includes the following steps:

[0390] S901, the first terminal device receives a third message sent by the second terminal device.

[0391] Here, the first terminal device is a last relay, and the second terminal device can be a child node of the first terminal device or include one or more intermediate relays between the first terminal device.

[0392] S902, the first terminal device sends a first message to a network device.

[0393] S903, the network device sends a second message to the first terminal device.

[0394] S904, the first terminal device sends a fourth message to the network device.

[0395] S905, the network device sends a fifth message to the first terminal device.

[0396] S906, the first terminal device sends a sixth message to the second terminal device.

[0397] Here, the first terminal device directly sends the sixth message to the second terminal device, and the sixth message can also be sent through forwarding of an intermediate relay.

[0398] In the embodiments of the present application, if the first terminal device determines the second configuration information of each relay device on a multi-hop link, as shown in FIG. 10, the case includes the following steps:

[0399] S1001, the first terminal device sends fourth information to an intermediate relay and a remote terminal device.

[0400] Here, the fourth information includes second configuration information of the intermediate relay and the remote terminal device.

[0401] S1002, the remote terminal device sends a DCR message to the first terminal device.

[0402] S1003, the first terminal device sends a DCA message to the remote terminal device.

[0403] For the fourth message in scenario two, in some embodiments, the SRAP packet header of the fourth message includes one or more of the following:

[0404] The local device identifier of the remote device in the second information;

[0405] The local device identifier of the second terminal device in the second information;

[0406] The bearer ID in the second information;

[0407] First indication information, the first indication information is used to indicate the transmission direction of the fourth message.

[0408] For the fourth message in scenario one and scenario two, in some embodiments, the fourth message is transmitted on a first radio link control (RLC) channel, which is configured, default or predefined by the network device.

[0409] In some embodiments, the configuration of the first RLC channel is related to one or more of the following:

[0410] Local device identifier, link, remote terminal, bearer, transmission direction.

[0411] It can be understood that the configuration granularity of the first RLC channel is related to one or more of the following: local device identifier, link, remote terminal, bearer, transmission direction.

[0412] For the fifth message in scenario two, in some embodiments, the SRAP packet header of the fifth message includes one or more of the following:

[0413] The local device identifier of the remote device in the second information;

[0414] The local device identifier of the second terminal device in the second information;

[0415] The bearer ID in the second information;

[0416] Second indication information, the second indication information is used to indicate the transmission direction of the fifth message.

[0417] For the fifth message in scenario one and scenario two, in some embodiments, the fifth message is transmitted on a second RLC channel, which is configured, default or predefined by the network device.

[0418] In some embodiments, the configuration of the second RLC channel is related to one or more of the following:

[0419] Local device identity, link, remote terminal, bearer, transmission direction.

[0420] It can be understood that the configuration granularity of the second RLC channel is related to one or more of the following: local device identity, link, remote terminal, bearer, transmission direction.

[0421] In some embodiments, the first information includes one or more of the following:

[0422] Device identity information, the identity information is used to indicate the device identity of each terminal device in the one or more terminal devices;

[0423] First quality of service information.

[0424] In the embodiments of the application, the device identity can include one or more of the following: layer 2 identity, user information (User Info) and the like.

[0425] In the embodiments of the application, for the third information of the terminal device, the third information includes device identity and quality of service information. For different terminal devices, the quality of service information included in the third information of different terminal devices can be the same.

[0426] In some embodiments, the first quality of service information includes one or more of the following:

[0427] Quality of service information of the multi-hop link;

[0428] Quality of service information of the Uu segment in the multi-hop link, and / or quality of service information of one or more PC5 segments in the multi-hop link.

[0429] In some embodiments, the device identity information and the first quality of service information are transmitted in different first messages.

[0430] It can be understood that the terminal device can first send a first message carrying device identity information, and after receiving the local device identity sent by the network device, send a first message carrying the first quality of service information to the network device.

[0431] In some embodiments, the configuration information of the terminal device includes one or more of the following:

[0432] Local device identity;

[0433] bearer configuration.

[0434] In some embodiments, the bearer configuration comprises one or more of the following:

[0435] a bearer ID;

[0436] RLC channel configuration information;

[0437] a bearer transmission direction.

[0438] In some embodiments, the local device identifier and the bearer configuration are transmitted in different messages.

[0439] It should be noted that, in some embodiments, the terminal devices on the multi-hop link each report split quality of service (split-QoS) information on the hop associated with the UE after establishing an RRC connection with the network device.

[0440] Next, the wireless communication method provided by the embodiments of the present application is further described.

[0441] The wireless communication method provided by the embodiments of the present application is applied to a scenario including multiple relay UEs, i.e., multiple hops. In an example, as shown in FIG. 11, two relay UEs, relay UE1 and relay UE2, are included, where the link between relay UE1 and relay UE2 is a multi-hop relay link (MH relay link). As shown in FIG. 12, three relay UEs, relay UE1, relay UE2, and relay UE3, are included, where the link between relay UE1 and relay UE2 and the link between relay UE2 and relay UE3 are multi-hop relay links (MH relay links).

[0442] The wireless communication method provided by the embodiments of the present application can be applied to a multi-hop scenario including two, three, or more relay UEs.

[0443] The wireless communication method provided by the embodiments of the present application solves the SRAP configuration problem in multi-hop U2N relay technology, including the configuration of BEARER ID and UE ID. In multi-hop U2N relay, because there are multiple relays, i.e., multiple hops, who decides / allocates the UE ID and BEARER ID used in SRAP can have the following solutions: network configuration; configuration by the relay device closest to the network; configuration by the intermediate UE; configuration by the remote UE.

[0444] The wireless communication method provided by the embodiments of the present application includes but is not limited to the following embodiments one to four.

[0445] In an embodiment, the network allocates UE IDs and bearer configurations, and the allocation of each UE ID is performed in steps, and the data transmission and routing method are determined according to the corresponding UE ID allocated.

[0446] In an embodiment, the process shown in FIG. 13A or FIG. 13B can be included,

[0447] In an embodiment, the UE (at least the relay UE closest to the network, and / or including the UE on the entire link) can report the connection status of the child UE to the network after entering the connected state. After the network configures the UE ID and / or bearer ID of the child UE according to the connection status of the child UE, the UE can send / forward the corresponding bearer from the child UE, and fill the UE ID and BEARER ID of the child UE in the SRAP header to identify the source and destination of the data packet by the entity receiving the data packet. Each UE configures according to the UE ID and BEARER ID associated with the received bearer and its own UE ID configuration, and determines the egress link and egress RLC channel when receiving the data packet. Among them, the UE ID is used to determine the RLC link, and the bearer ID is used to determine the RLC channel.

[0448] In an embodiment, the message transmission between different devices can be as shown in FIG. 13A, including:

[0449] S1301, the remote UE sends message 1 to the relay UE1.

[0450] Among them, the IDLE / INACTIVE state remote UE sends message 1 to the network, and the message 1 is used to request to establish a connection.

[0451] The message 1 can be one or more of the following messages: RRC setup request (RRC setup REQ), RRC resume request (RRCResume REQ), RRC re-establishment request (Re-establish REQ), RRC reconfiguration complete message (Reconfiguration complete).

[0452] The message 1 can be a SRB1 message or a SRB0 message of the remote UE.

[0453] S1302, the relay UE1 sends message 2 to the relay UE2.

[0454] The message 2 can be a SRB1 message or a SRB0 message of the relay UE1.

[0455] S1303, the relay UE2 sends a message 3 to the relay UE3.

[0456] The message 3 can be an SRB1 message or an SRB0 message of the relay UE2.

[0457] S1304, the relay UE3 sends a message 4 to the base station.

[0458] The message 4 can be an SRB1 message or an SRB0 message of the relay UE4.

[0459] In S1302 to S1304, the non-connected state relay UE needs to establish its own RRC connection first to relay data for the remote UE, therefore, the relay UE of each hop first sends its own message to request to establish an RRC connection after receiving the message sent by the child node, wherein the relay UE1 first sends its own message 2 after receiving the message 1 sent by the remote UE, the relay UE2 first sends its own message 3 after receiving the message 2 sent by the relay UE1, and the relay UE3 first sends its own message 4 after receiving the message 3 sent by the relay UE2.

[0460] The connection establishment request message sent by the relay UE can be an RRC setup REQ / Resume REQ / Re-establish REQ.

[0461] In the embodiments of the present application, the message type of the message 2, the message 3 and the message 4 is the same as the message type of the message 1.

[0462] The sending of the messages in S1301 to S1304 does not need to add an SRAP packet header.

[0463] S1305, the base station sends a feedback message 4 to the relay UE3.

[0464] The feedback message 4 is a feedback message or a response of the message 4.

[0465] At this time, the RRC connection between the base station and the relay UE3 is established.

[0466] S1306, the relay UE3 sends a report 4 to the base station.

[0467] The report 4 includes the information of the relay UE2.

[0468] The relay UE 3 sends first reporting information to the network through reporting 4, and the first reporting information (through SidelinkUEInformation (SUI) information) carries:

[0469] ID information of the relay UE 2, end-to-end (E2E) QoS information, and split QoS information.

[0470] The ID of the relay UE 2 can be an L2 ID / User Info (Prose layer ID), and the purpose of the ID is to let the base station know that there is still a UE behind the relay UE 3 that needs to be configured with an ID, and to determine the configuration of the UE ID, that is, the RLC link ID.

[0471] The end-to-end (E2E) QoS information is the QoS information of the entire path from the remote to the base station. After the base station obtains the E2E QoS information, the base station can split and determine the QoS information of the Uu segment and / or the PC5 segment (all PC5 segments or only the PC5 segment associated with the relay UE 3).

[0472] The split QoS information includes the QoS information of the Uu segment and / or the PC5 segment (all PC5 segments or only the PC5 segment associated with the relay UE 3).

[0473] In another implementation, another implementation is that the QoS-related information and the UE ID-related information are reported through different messages respectively.

[0474] In S1306a, the base station sends reporting feedback 4 to the relay UE 3.

[0475] The reporting feedback 4 is a feedback or response of the reporting 4, and the reporting feedback 4 includes the configuration of the relay UE 2 allocated by the base station.

[0476] The base station sends the configuration information allocated by the base station according to the information of the relay UE 2 reported by the UE to the relay UE 3. The configuration information of the relay UE 2 includes: UE (local) ID and / or bearer configuration, wherein the bearer configuration includes: bearer ID and / or RLC channel configuration.

[0477] In S1306a, the UE ID and the bearer configuration are configured together or separately.

[0478] In S1303a, the relay UE 3 sends the forwarded message 3 to the base station.

[0479] After receiving the UE ID of relay UE2 configured by the base station, the relay UE3 forwards the message 3 of relay UE2, i.e., sends the forwarded message 3.

[0480] The forwarded message 3 carries an SRAP header, and the SRAP header can include the UE ID of relay UE2 configured by the base station.

[0481] The forwarded message 3 can be sent on the RLC channel configured by the base station, or by default, or specified by the protocol.

[0482] The bearer ID in the header of SRAP is configured by the base station for relay UE2, or by default, or specified by the protocol.

[0483] S1303b, the base station sends a feedback message 3 to relay UE2.

[0484] The feedback message 3 is the feedback message or response of message 3.

[0485] The base station sends a feedback message 3 to relay UE2 in response to the message 3 of relay UE2, and the message carries the UE(local)ID and / or bearer configuration of relay UE2 configured by the base station. The bearer configuration includes BEARER ID and / or RLC channel configuration.

[0486] In one possible way, the network configures relay UE3 (step 1306a), which is forwarded to relay UE2 by relay UE3.

[0487] It can be understood that the feedback message 3 can include the UE ID of relay UE2 and / or bearer configuration 1.

[0488] Here, the bearer configuration 1 and the bearer configuration 2 of relay UE2 can be the same or different.

[0489] S1303c, relay UE2 sends a report 3 to the base station.

[0490] The report 3 includes information of relay UE1.

[0491] S1303d, the base station sends a report feedback 3 to relay UE2.

[0492] The report feedback 3 is the feedback or response of the report 3, and the report feedback 3 includes the configuration of relay UE1 allocated by the base station.

[0493] The descriptions of S1303c and S1303d can refer to the descriptions of S1306 and S1306a, and the difference is that the information carried by the different messages of the sending end corresponds to different relay UEs.

[0494] S1302a, the relay UE2 forwards the message 2 to the base station.

[0495] S1302b, the base station sends the feedback message 2 to the relay UE1.

[0496] The feedback message 2 is the feedback message or response of the message 2.

[0497] It can be understood that the UE ID and / or bearer configuration of the relay UE1 can be included in the feedback message 2.

[0498] S1302c, the relay UE1 sends the report 2 to the base station.

[0499] The report 2 includes the information of the remote UE.

[0500] S1302d, the base station sends the report feedback 2 to the relay UE1.

[0501] The report feedback 2 is the feedback or response of the report 2, and the report feedback 2 includes the configuration of the relay UE1 allocated by the base station.

[0502] The descriptions of S1302a to S1302d can refer to the descriptions of S1303a to S1303d.

[0503] S1301a, the relay UE1 forwards the message 1 to the base station.

[0504] S1301b, the base station sends the feedback message 1 to the remote UE.

[0505] The descriptions of S1301a to S1301d can refer to the descriptions of S1303a to S1303b.

[0506] In some embodiments, the relay UE (relay UE1 and relay UE2) can serve the remote UE without entering the connected state.

[0507] For the relay UE that does not enter the connected state, the message 2 and the message 3 can be PC5 messages indicating that the remote UE is to perform RRC connection establishment and is not used for its own RRC connection, but these PC5 messages carry the L2 ID of the remote UE. At this time, it can be considered to allocate a UE ID for the relay UE1 or the relay UE2.

[0508] If message 2, 3 is not used to request to establish RRC connection, it is not needed to wait for relay UE1, relay UE2 to establish RRC connection with the base station.

[0509] At this time, FIG. 13A can be adjusted to FIG. 13B, including:

[0510] S1301, the remote UE sends message 1 to the relay UE1.

[0511] S1302, the relay UE1 sends message 2 to the relay UE2.

[0512] Message 2 is a PC5 message carrying the information of the remote UE, used to indicate that the remote UE wants to perform RRC connection establishment.

[0513] S1303, the relay UE2 sends message 3 to the relay UE3.

[0514] Message 3 is a PC5 message carrying the information of the remote UE, used to indicate that the remote UE wants to perform RRC connection establishment.

[0515] S1304, the relay UE3 sends message 4 to the base station.

[0516] Message 4 is a message carrying the information of the remote UE, used to indicate that the remote UE wants to perform RRC connection establishment.

[0517] S1305, the base station sends feedback message 4 to the relay UE3.

[0518] Wherein, the feedback message 4 is the feedback message or response of the message 4.

[0519] S1306, the relay UE3 sends report 1 to the base station.

[0520] The report 1 includes the information of the remote UE.

[0521] S1306a, the base station sends report feedback 1 to the relay UE3.

[0522] Wherein, the report feedback 1 is the feedback or response of the report 1, and the report feedback 1 includes the configuration of the remote UE allocated by the base station.

[0523] S1307, the relay UE3 sends feedback message 3 to the relay UE2.

[0524] The feedback message 3 is used to respond to the message 3, carrying the configuration of the remote UE.

[0525] S1308, the relay UE2 sends a feedback message 2 to the relay UE1.

[0526] The feedback message 2 is used to respond to the message 2, carrying the configuration of the remote UE.

[0527] S1309, the relay UE1 sends a feedback message 1 to the remote UE.

[0528] In FIG. 13B, in this way, the message 2 and the message 3 help the remote UE forward the RRC connection establishment request message from the remote UE and / or the indication indicating that the remote UE requests the connection establishment, for the relay UE1 and the relay UE2, and the indication includes:

[0529] - the connection establishment cause value.

[0530] The feedback message 1 is used to respond to the message 1, and carries the configuration of the remote UE in the feedback message 1, for the instruction of establishing the RRC connection.

[0531] Embodiment two, the network allocates the UE ID and the bearer configuration, and each UE knows the UE ID of the remote UE and / or the UE ID of the relay UE, and determines the data transmission and the routing manner according to the UE ID.

[0532] In the embodiment two, the flow shown in FIG. 14A or FIG. 14B can be included,

[0533] In FIG. 14, the UE (at least the relay UE closest to the network, and / or including the UE on the whole link) can report the connection status of the UE on the link to the network after entering the connected state, and the network configures the UE ID and / or the bearer ID after the UE can send / forward the corresponding bearer from the corresponding UE, and fills the UE ID and the BEARER ID in the SRAP header for the entity receiving the data packet to identify the source and the destination of the data packet. And each UE needs to know the ID of the remote UE, and optionally knows the ID of the other relay UE (if needed) and the BEARER ID configuration, when receiving the data packet, the UE ID in the received data packet is the ID of the remote UE, and the uplink Egress link and the Egress RLC channel are determined according to the UE ID and the BEARER ID, and the SRAP header of the sending does not need to be changed.

[0534] As shown in FIG. 14A, it includes:

[0535] S1401, the remote UE sends a message 1 to the relay UE1.

[0536] The remote UE in the IDLE / INACTIVE state sends a message 1 to the network, and the message 1 is used to request to establish a connection.

[0537] The message 1 can be one or more of the following messages: RRC setup REQ, RRCResume REQ, RRC Re-establish REQ, RRC Reconfiguration complete message.

[0538] The message 1 can be an SRB1 message or an SRB0 message of the remote UE.

[0539] S1402, the relay UE1 sends a message 2 to the relay UE2.

[0540] S1403, the relay UE2 sends a message 3 to the relay UE3.

[0541] S1404, the relay UE3 sends a message 4 to the base station.

[0542] In S1402 to S1404, the non-connected state relay UE needs to establish its own RRC connection first to relay data for the remote UE, so each hop of the relay UE first sends its own message to request to establish an RRC connection after receiving the message sent by the child node. Among them, the relay UE1 first sends its own message 2 after receiving the message 1 sent by the remote UE, the relay UE2 first sends its own message 3 after receiving the message 2 sent by the relay UE1, and the relay UE3 first sends its own message 4 after receiving the message 3 sent by the relay UE2.

[0543] The connection establishment request message sent by the relay UE can be RRC setup REQ / Resume REQ / Re-establish REQ.

[0544] In the embodiments of the application, the message types of the message 2, the message 3 and the message 4 are the same as the message type of the message 1.

[0545] The sending of the messages in S1401 to S1404 does not need to add an SRAP header.

[0546] S1405, the base station sends a feedback message 4 to the relay UE3.

[0547] The feedback message 4 is a feedback message or response of the message 4.

[0548] S1406, the relay UE 3 sends the report 4 to the base station.

[0549] The report 4 includes information of all UEs.

[0550] The relay UE 3 sends the first report information to the network through the report 4, and the first report information (through SUI information) carries:

[0551] ID information of all UEs of the entire link, E2E QoS information, end-to-end (E2E) QoS information, and split QoS information.

[0552] The ID of the UE can be an L2 ID / User Info (Prose layer ID), and the purpose of the ID is to let the base station know that the UE needs to be configured with an ID, and to determine the configuration of the UE ID, i.e., the RLC link ID.

[0553] The end-to-end (E2E) QoS information is the QoS information of the entire path from the remote to the base station. After obtaining the E2E QoS information, the base station can split and determine the QoS information of the Uu segment and / or the PC5 segment (all PC5 segments or only the PC5 segment associated with the relay UE 3).

[0554] The split QoS information includes the QoS information of the Uu segment and / or the PC5 segment (all PC5 segments or only the PC5 segment associated with the relay UE 3).

[0555] For the QoS-related information and the UE ID-related information reported in S1406, in another implementation manner, they can be reported through different information respectively.

[0556] S1406a, the base station sends a report feedback 4 to the relay UE 3.

[0557] The report feedback 4 is a feedback or response of the report 4, and the report feedback 4 includes configuration information of all UEs allocated by the base station.

[0558] The base station sends the configuration information allocated to all UEs according to the information reported by the UEs to the relay UE 3. The configuration information of the UE includes: UE (local) ID and / or bearer configuration, and the bearer configuration includes: bearer ID and / or RLC channel configuration.

[0559] S1407. The relay UE 3 sends the UE IDs of all UEs to each of all UEs.

[0560] The manner of sending the configuration of all UEs to each of all UEs includes:

[0561] The manner of sending directly, i.e. direct RRC information message, which requires RRC connection between two UEs. The UE IDs used in the end-to-end RRC message between the two UEs of direct sending are default, relay UE configured, and remote UE configured.

[0562] The manner of sending indirectly, i.e. the relay UE 2 receives the RRC message of the relay UE 3, generates a new RRC message and sends it to the relay UE 1, and the relay UE 1 also sends to the remote UE in this manner.

[0563] S1403a. The relay UE 3 sends the forwarded message 3 to the base station.

[0564] The relay UE 3 receives the UE ID of the relay UE 2 configured by the base station, and forwards the message 3 and / or other data information of the relay UE 2 for the relay UE 2. The SRAP header is carried in the forwarded message 3, which can include: the UE ID of the remote UE, and / or the UE ID of the relay UE, and / or the BEARER ID information.

[0565] S1303b. The base station sends the feedback message 3 to the relay UE 2.

[0566] The feedback message 3 is the feedback message or response of the message 3. The configuration of the relay UE 1 allocated by the base station is carried in the feedback message 3.

[0567] The feedback message 3 sent by the base station to the relay UE 3 carries the SRAP header, and the relay UE 3 sends the forwarded feedback message 3 to the relay UE 2, which does not carry the SRAP header.

[0568] S1402a. The relay UE 2 forwards the message 2 to the base station.

[0569] The relay UE 2 receives the UE ID of the relay UE 1 configured by the base station, and forwards the message 2 and / or other data information of the relay UE 1 for the relay UE 1. The SRAP header is carried in the forwarded message 2, which can include: the UE ID of the remote UE, and / or the UE ID of the relay UE, and / or the BEARER ID information.

[0570] S1402b, the base station sends a feedback message 2 to the relay UE1.

[0571] The feedback message 2 is a feedback message or response of the message 2. The feedback message 2 carries the configuration of the Remote UE assigned by the base station.

[0572] The feedback message 2 between the base station and the relay UE2 carries an SRAP header. The SRAP header can include: the UE ID of the Remote UE, and / or the UE ID of the Relay UE, and / or the BEARER ID information.

[0573] The feedback message 2 sent by the relay UE2 to the relay UE1 does not carry the SRAP header.

[0574] S1401a, the relay UE1 forwards the message 1 to the base station.

[0575] After receiving the UE ID of the Remote UE configured by the base station, the relay UE1 forwards the message 1 and / or other data information of the Remote UE. The SRAP header is carried in the forwarded message 1. The SRAP header can include: the UE ID of the Remote UE, and / or the UE ID of the Relay UE, and / or the BEARER ID information.

[0576] S1401b, the base station sends a feedback message 1 to the remote UE. The feedback message 1 carries the configuration of the remote UE assigned by the base station.

[0577] The feedback message 1 between the base station and the relay UE1 carries an SRAP header. The SRAP header can include: the UE ID of the Remote UE, and / or the UE ID of the Relay UE, and / or the BEARER ID information.

[0578] The feedback message 1 sent by the relay UE1 to the Remote UE does not carry the SRAP header.

[0579] For FIG. 14A, each UE can also report the split-QoS information on the hop associated with the UE after entering the connected state.

[0580] In FIG. 14B, the relay UE other than the relay UE closest to the network can serve the remote UE without entering the connected state.

[0581] As shown in FIG. 14B, it includes:

[0582] S1401, the remote UE sends message 1 to the relay UE1.

[0583] S1408, the UE sends message 5 to the parent node, so that message 5 reaches the base station from the remote UE.

[0584] Message 5 can be a connection establishment indication.

[0585] Message 5 includes: a connection establishment indication sent by the node (including UE information and / or a connection establishment cause value); own UE information and / or a connection establishment cause value.

[0586] S1403, the relay UE2 sends message 3 to the relay UE3.

[0587] S1404, the relay UE3 sends message 4 to the base station.

[0588] Message 4 carries the information of all UEs.

[0589] The connection establishment cause value carried by message 4 is set by the relay UE3 implementation, or set according to MSG3 from the relay UE2 (such as emergency service), or set according to the connection establishment cause value from the remote UE.

[0590] S1405, the base station sends feedback message 4 to the relay UE3.

[0591] Wherein, the feedback message 4 is a feedback message or response of message 4, used to indicate the establishment of the RRC connection of the relay UE3.

[0592] S1406, the relay UE3 sends report 4 to the base station.

[0593] Report 4 includes: information of all UEs, or information of UEs that need to establish RRC connection, UE information can be L2ID / User Info(Prose layer ID) / 5G-S-TMSI / I-RNTI;

[0594] E2E QoS information, or split QoS information, including Uu segment and / or PC5 segment (all PC5 segments or only the QoS information of the PC5 segment between the relay UE2 and the relay UE3 associated with the relay UE3).

[0595] S1406a, the base station sends report feedback 4 to the relay UE3.

[0596] The report feedback 4 is a feedback or response of the report 4, and the report feedback 4 includes the configurations of all UEs allocated by the base station.

[0597] In some embodiments, the bearer ID and the UE (local) ID configuration can be configured together or separately.

[0598] S1407, the relay UE 3 sends the UE IDs of all UEs configured by the network to all UEs on the link.

[0599] Here, the sending mode of the UE ID includes the following two modes:

[0600] Mode 1, a direct sending mode, i.e., direct RRC information, which requires RRC connection between two UEs. The UE IDs used in the end-to-end RRC messages between the two UEs are default, relay UE configured, and remote UE configured. For example, the relay UE 3 sends the feedback message 5 to the relay UE 2, the relay UE 3 sends the feedback message 5 to the relay UE 1, and the relay UE 3 sends the feedback message 5 to the remote UE.

[0601] Mode 2, a non-direct sending mode, i.e., the relay UE 2 receives the RRC message of the relay UE 3, generates a new RRC message, and sends it to the relay UE 1, and the relay UE 1 also sends it to the remote UE in this way.

[0602] S1401a, the relay UE 1 forwards the message 1 to the base station.

[0603] After receiving the UE ID of the remote UE configured by the base station, the relay UE 1 forwards the message 1 and / or other data information of the remote UE for the remote UE. The SRAP header is carried in the forwarded message 1, and the SRAP header can include the UE ID of the remote UE, the UE ID of the relay UE, and / or the BEARER ID information.

[0604] S1401b, the base station sends the feedback message 1 to the remote UE. The feedback message 1 carries the configuration of the remote UE allocated by the base station.

[0605] The feedback message 1 between the base station and the relay UE 1 carries the SRAP header, and the SRAP header can include the UE ID of the remote UE, the UE ID of the relay UE, and / or the BEARER ID information.

[0606] The feedback message 1 sent by the relay UE1 to the remote UE does not carry the SRAP header.

[0607] In the third embodiment, the relay UE closest to the network is allocated (or this method can also be extended to other relay and / or remote UE configurations, the steps are similar, and the focus is on centralized configuration by one node), and each UE knows the UE ID and / or relay UE ID of the remote UE, and determines the data transmission and routing method according to the UE ID.

[0608] Compared with the network allocation in the first and second embodiments, in the third embodiment, the bearer transmission on PC5 and the bearer transmission on Uu can be relatively independent. That is, the bearer transmission on PC5 can start after the relay UE allocates the UE ID and BEARER ID after the PC5 link (multi-hop) is established, and does not need to be established by the Uu RRC connection. The bearer forwarding on Uu needs to be reported to the network by the UE (at least the relay UE closest to the network) after entering the connected state, and / or the UE ID and bearer ID configured by the relay UE (another implementation is that the network reconfigures the UE ID and / or bearer ID according to the connection condition) after the UE can transmit / forward the corresponding bearer from the corresponding UE on the Uu, and fill the UE ID and BEARER ID in the SRAP header to identify the data packet source and destination of the entity receiving the data packet.

[0609] The non-direct data and signaling transmission on the PC5 link needs to be completed after the UE ID configuration of the relay UE3 and the indication to other UEs, such as the unicast DCR message in step 2. When transmitting non-direct messages, the SRAP header containing the UE ID configured by the relay UE3 needs to be carried.

[0610] The SRAP header used between the network and the relay UE3 when the relay UE3 forwards data and signaling for other UEs is:

[0611] If the network reuses the UE ID / BEARER ID configured by the relay UE3, that is, the same UE ID / BEARER ID is used for each UE on the entire link, the ID used in the SRAP header by the relay UE3 is the UE ID / BEARER ID configured by the relay UE3.

[0612] If the network reconfigures the UE ID / Bearer ID, but the UE ID / Bearer ID configured by the relay UE3 can still be used on the PC5 link, i.e. the reconfiguration of the network only applies to the transmission between the network, then the relay UE3 uses different SRAP packet headers on the PC5 link and the Uu link. The relay UE3 needs to maintain the mapping relationship of two sets of configurations, and set the UE ID / Bearer ID again at the SRAP layer;

[0613] If the network reconfigures the UE ID / Bearer ID, and the reconfiguration applies to the PC5 and Uu link, i.e. the same UE ID / Bearer ID is used for each UE on the entire link, then the ID used by the relay UE3 in the SRAP packet header is the network configuration;

[0614] Another way is that the link / bearer with both the starting point and the ending point being PC5 nodes uses the UE ID configured by the relay 3, and the link / bearer with the starting point or the ending point being the network uses the UE ID allocated by the network (refer to embodiment one / two). The UE ID may or may not coincide, but the RLC channel needs to be distinguished.

[0615] As shown in FIG. 15A, it includes:

[0616] S1501, the relay UE3 sends UE configuration to all UEs on the multi-hop link.

[0617] Among them, the relay UE3 allocates UE ID for the Remote UE and / or Relay UE on the link and / or configures bearer ID for the bearer on the link.

[0618] The UE ID can be allocated by L2 ID / User Info, such as: taking the high several bits or low several bits of L2 ID / User Info. Among them, the allocation of UE ID can be realized based on the relay UE. The allocation of UE ID can be realized based on the network device, such as: the network configures a part of UE ID space.

[0619] The configuration of bearer ID can be based on the SLRB-PC5-ConfigIndex indicated by the Remote UE, or the default bearer ID (such as SRB) or the protocol stipulation.

[0620] The configured UE ID and / or bearer ID (DRB and or SRB) are sent to all UEs on the link. Among them, it is sent in an indirect manner, that is, relay UE3 sends to relay UE2, relay UE2 sends to relay UE1, and so on.

[0621] Among them, the PC5 link between each two UEs on PC5 has been established.

[0622] S1502, the Remote UE sends a direct communication request DCR message to the relay UE3.

[0623] The DCR message is used to request to establish an end-to-end connection between the Remote UE and the relay UE3, and the DCR message needs to carry an SRAP packet header, which includes: the remote UE ID allocated by the relay UE3 and / or the UE ID of the relay UE3; the BEARER ID, which is default, protocol specified, or determined by the remote UE.

[0624] S1502a, the relay UE3 sends a direct communication acceptance DCA message to the Remote UE.

[0625] The relay UE feeds back the DCA message, which needs to carry an SRAP packet header, which includes:

[0626] The remote UE ID allocated by the relay UE3 and / or the UE ID of the relay UE3;

[0627] The BEARER ID, which is default, protocol specified, or determined by the remote UE.

[0628] S1503, the Remote UE sends a message 1 to the base station.

[0629] The IDLE / INACTIVE Remote UE sends a message 1 to the network device, and the message 1 is used to request to establish a connection, which can be an RRC setup REQ / Resume REQ / Re-establish REQ / Reconfiguration complete message.

[0630] S1504, the relay UE1 sends a message 2 to the relay UE2.

[0631] S1505, the relay UE2 sends a message 3 to the relay UE3.

[0632] S1506, the relay UE3 sends message 4 to the base station.

[0633] The non-connected state relay UE needs to establish its own RRC connection first to relay data for the remote UE, so each hop relay first sends its own connection establishment request message after receiving the connection establishment request message sent by the child node, wherein the connection establishment request message can be RRC setup REQ / Resume REQ / Re-establish REQ.

[0634] Another implementation is that the intermediate relay (relay UE1 / 2) can not enter the connected state to serve the remote terminal. At this time, the description of relay UE1 and relay UE2 in the non-connected state in embodiment 1 and embodiment 2 can be referred to.

[0635] S1503a, the relay UE1 forwards message 1 to the relay UE3.

[0636] S1504a, the relay UE2 forwards message 2 to the relay UE3.

[0637] For S1503a and S1504a, the relay UE1 / 2 can forward the data for the remote UE / relay UE1 after receiving the UE ID configuration and / or BEARER ID configuration and the data to be transmitted from the child node, and the SRAP header on the PC5 link needs to include: the UE ID of the remote UE, and / or the UE ID of the relay UE, and / or the BEARER ID.

[0638] S1506a, the base station sends feedback message 4 to the relay UE3.

[0639] The feedback message 4 is a connection establishment instruction in response to the message 4.

[0640] S1507, the relay UE3 sends report 1 to the base station.

[0641] The report 1 includes first report information, and the first report (through SUI information) information includes:

[0642] ID information of all UEs in the entire link, which can be L2 ID / User Info (Prose layer ID); and / or UE ID information that has been allocated

[0643] E2E QoS information;

[0644] - split QoS information after segmentation, including Uu segment and / or PC5 segment (all or only associated with relay UE3);

[0645] BEARER ID information that has been configured.

[0646] In addition, each UE reports the split-QoS information associated with the hop after entering the connected state.

[0647] Another implementation is that QoS-related information / BEARER information and UE ID-related information are reported through different information respectively.

[0648] S1507a, the base station sends a feedback report to the relay UE3.

[0649] The feedback report includes the configuration of all UEs configured by the base station.

[0650] Among them, the base station can configure the entire path according to the path information reported by the UE: UE (local) ID and / or bearer configuration, bearer configuration includes BEARER ID and / or RLC channel configuration. Among them, the bearer ID and the UE (local) ID configuration are configured together or separately.

[0651] In another implementation, the base station directly uses the reported UE ID and BEARER ID, and further configures the RLC channel.

[0652] S1505a, the relay UE3 sends the forwarded message 3 to the base station.

[0653] S1505b, the base station sends a feedback message 3 to the relay UE2.

[0654] S1504b, the relay UE3 sends the forwarded message 2 to the base station.

[0655] S1504c, the base station sends a feedback message 2 to the relay UE1.

[0656] S1503b, the relay UE3 sends the forwarded message 1 to the base station.

[0657] S1503c, the base station sends a feedback message 1 to the remote UE.

[0658] In the embodiment of the application, the relay UE3 forwards the information from the remote UE and / or other relays on this link, and the SRAP header on the Uu link needs to include:

[0659] Remote UE’s UE ID; and / or

[0660] Relay UE’s UE ID; and / or

[0661] BEARER ID information.

[0662] In embodiment four, the intermediate relay UE allocates, and each UE knows the Remote UE’s UE ID and / or Relay UE ID, and decides the data transmission and routing manner according to the UE ID.

[0663] Here, compared with embodiment three, after the PC5 link (multi-hop) is established, the relay UE allocates the UE ID and BEARER ID and then starts to send the bearer on PC5, without the need of Uu RRC connection establishment completion.

[0664] Here, the main difference from embodiment three is that the UE ID configuration on the PC5 link is not completed by the relay UE3, but by two intermediate relays, each of which completes a part. Non-direct data on the PC5 link needs to be performed after the UE ID is allocated to both non-direct UEs.

[0665] In embodiment four, the bearer transmission between the network, such as the relay UE3 forwarding data and signaling for other UEs, uses a packet header similar to embodiment three. In particular, in addition to the difference between Uu and PC5, on the PC5 link, since there are also different UE ID allocation entities, when different entities allocate different UE IDs for the same UE,

[0666] - Different UE pairs (allocated by different UEs ID / BEARER ID) use different UE ID / BEARER ID when sending end-to-end messages;

[0667] If there are different entities allocating different UE IDs for the same UE, the UE facing two entities needs to do UE ID / BEARER ID conversion to ensure that the data can be correctly identified by each entity.

[0668] As shown in FIG. 15B, it includes:

[0669] S1601-S1601A, the relay 1 configures the UE configuration for the Remote UE and / or the Relay UE2.

[0670] The UE configuration includes the UE ID and bearer configuration.

[0671] ​The UE ID can be allocated based on the L2 ID / User Info, such as taking the high or low several bits of the L2 ID / User Info. The allocation of the UE ID can be implemented based on the relay UE. The allocation of the UE ID can be implemented based on the network device, such as the network configuring a part of the UE ID space.

[0672] The configuration of the bearer ID can be based on the SLRB-PC5-ConfigIndex indicated by the Remote UE, or a default bearer ID (such as an SRB) or a protocol specification. The Remote UE sends a direct communication request (DCR) message to the relay UE 3.

[0673] The relay 1 sends the configured UE configuration to the Remote UE and / or the Relay UE 2.

[0674] The Remote UE sends a DCR message to the relay UE 2.

[0675] The DCR message is used to request the establishment of an end-to-end connection between the Remote UE and the relay UE 2, and the DCR message needs to carry an SRAP packet header, which includes: the remote UE ID allocated by the relay UE 1 and / or the UE ID of the relay UE 2; the BEARER ID, which is a default, protocol specified, relay UE configured, or remote UE determined.

[0676] The relay UE 2 sends a DCA message to the Remote UE.

[0677] The relay UE 2 feeds back the DCA message, which needs to carry an SRAP packet header, which includes:

[0678] The remote UE ID allocated by the relay UE 1 and / or the UE ID of the relay UE 2;

[0679] The BEARER ID, which is a default, protocol specified, relay UE configured, or remote UE determined.

[0680] The relay UE 2 configures the UE configuration for the Remote UE and / or the Relay UE 3.

[0681] The UE configuration includes the UE ID and the bearer configuration.

[0682] The UE ID can be reassigned or reused by the relay UE2 based on the L2 ID / User Info, such as taking the high or low bits of the L2 ID / User Info. The allocation of the UE ID can be based on the relay UE implementation. The allocation of the UE ID can be based on the network device implementation, such as the network configuring a part of the UE ID space.

[0683] The configuration of the bearer ID can be based on the SLRB-PC5-ConfigIndex indicated by the Remote UE, or a default bearer ID (such as an SRB) or a protocol specification. The Remote UE sends a direct communication request (DCR) message to the relay UE3.

[0684] The relay UE2 sends the configured UE configuration to the Remote UE and / or the relay UE3.

[0685] The relay UE2 can also allocate ID information for the relay UE1 (the allocation method is the same as that of the relay UE3).

[0686] Optionally, the relay UE2 sends the ID information of the relay UE1 and itself to the remote UE and the relay UE3.

[0687] If the UE ID of the remote UE is reassigned, the remote UE uses different UE IDs when communicating with the relay UE2 (using the ID allocated by the relay UE1) and the relay UE3 (using the ID allocated by the relay UE2).

[0688] S1604, the Remote UE sends a DCR message to the relay UE3.

[0689] The DCR message is used to request the establishment of an end-to-end connection between the Remote UE and the relay UE3, and the DCR message needs to carry an SRAP packet header, which includes the remote UE ID allocated by the relay UE2 or the relay UE1 and / or the UE ID of the relay UE3.

[0690] BEARER ID, wherein the BEARER ID is a default, protocol-specified, or relay UE-configured, or remote UE-determined.

[0691] S1604a, the relay UE3 sends a DCA message to the Remote UE.

[0692] The relay UE3 feeds back a DCA message, which needs to carry an SRAP header, and the SRAP header includes:

[0693] The remote UE ID allocated by the relay UE1 or the relay UE2 and / or the UE ID of the relay UE3;

[0694] BEARER ID, default, protocol specified, or relay UE configured, or remote UE determined

[0695] S1605, the remote UE sends a message 1 to the base station.

[0696] The IDLE / INACTIVE remote UE sends a message 1 to the network device, and the message 1 is used to request to establish a connection, which can be an RRC setup REQ / Resume REQ / Re-establish REQ / Reconfiguration complete message.

[0697] S1606, the relay UE1 sends a message 2 to the relay UE2.

[0698] S1607, the relay UE2 sends a message 3 to the relay UE3.

[0699] S1608, the relay UE3 sends a message 4 to the base station.

[0700] The non-connected state relay UE needs to establish its own RRC connection first to relay data for the remote UE, so each hop relay first sends its own connection establishment request message after receiving the connection establishment request message sent by the child node, wherein the connection establishment request message can be an RRC setup REQ / Resume REQ / Re-establish REQ.

[0701] Another implementation is that the intermediate relay (relay UE1 / 2) can not enter the connected state to serve the remote terminal. At this time, the description of the relay UE1 and the relay UE2 in the connected state in the embodiment 1 and the embodiment 2 can be referred to.

[0702] S1605a, the relay UE1 forwards the message 1 to the relay UE3.

[0703] S1606a, the relay UE2 forwards the message 2 to the relay UE3.

[0704] For S1605a and S1606a, after receiving the UE ID configuration and / or BEARER ID configuration and the data to be transmitted from the child node, the Relay UE1 / 2 can forward the data for the remote UE / relay UE1, and the SRAP header on the PC5 link needs to include: the UE ID of the remote UE, and / or the UE ID of the relay UE, and / or the BEARER ID.

[0705] S1608a, the base station sends a feedback message 4 to the relay UE3.

[0706] The feedback message 4 is a connection establishment instruction in response to the message 4.

[0707] S1609, the relay UE3 sends a report 1 to the base station.

[0708] The report 1 includes first report information, and the first report (through SUI information) information includes:

[0709] ID information of all UEs of the entire link or information of the relay UE3 and the remote UE, or information of the relay UE3, the relay UE2 and the remote UE, the ID can be L2 ID / User Info (Prose layer ID); and / or UE ID information that has been allocated

[0710] E2E QoS information;

[0711] Split QoS information, including Uu segment and / or PC5 segment (all or only associated with the relay UE3);

[0712] BEARER ID information that has been configured.

[0713] In addition, each UE reports the split-QoS information and / or related UE ID information on the hop associated with the UE after entering the connected state. For example, the relay UE3 only reports the remote UE information and the relay UE3 information, and the relay UE1 reports the relay UE1 information, the remote UE information and the relay UE2 information.

[0714] Another implementation is that the QoS related information / BEARER information and the UE ID related information are reported through different information respectively.

[0715] S1609a, the base station sends a feedback report to the relay UE3.

[0716] The feedback report includes the UE configuration configured by the base station. The base station configures the UE configuration for the reported link according to the information reported by the UE.

[0717] The base station configures the UE(local)ID and / or bearer configuration for the reported link according to the information reported by the UE, wherein the bearer configuration includes BEARER ID and / or RLC channel configuration. The bearer ID and UE(local)ID configuration are configured together or separately.

[0718] In another implementation, the base station directly uses the reported UE ID and BEARER ID, and further configures the RLC channel.

[0719] S1607a, the relay UE3 sends the forwarded message 3 to the base station.

[0720] S1607b, the base station sends the feedback message 3 to the relay UE2.

[0721] S1606b, the relay UE3 sends the forwarded message 2 to the base station.

[0722] S1606c, the base station sends the feedback message 2 to the relay UE1.

[0723] S1605b, the relay UE3 sends the forwarded message 1 to the base station.

[0724] S1605c, the base station sends the feedback message 1 to the remote UE.

[0725] In the embodiments of the present application, the relay UE3 forwards the information from the remote UE and / or other relays on the link, and the SRAP header on the Uu link needs to include:

[0726] The UE ID of the remote UE; and / or

[0727] The UE ID of the relay UE; and / or

[0728] The BEARER ID information.

[0729] In the embodiments of the present application, the SRAP header conversion can be as shown in FIG. 16. When the message passes through the relay device 2, the UE ID1 and bearerID1 of the SRAP header are modified to UE ID2 and bearer ID2 respectively.

[0730] The preferred embodiments of the present application are described in detail above with reference to the drawings, but the present application is not limited to the specific details of the above-described embodiments. Within the technical concept of the present application, various simple modifications can be made to the technical solutions of the present application, and these simple modifications all belong to the protection scope of the present application. For example, in the above-described specific embodiments, various specific technical features described in the embodiments can be combined in any appropriate manner without contradiction. In order to avoid unnecessary repetition, various possible combinations are not described again in the present application. For another example, various different embodiments of the present application can also be combined in any manner, as long as it does not deviate from the idea of the present application, and it should also be considered as disclosed in the present application. For another example, under the premise of no conflict, each embodiment described in the present application and / or technical features in each embodiment can be combined with any prior art, and the technical solutions obtained after combination should also fall within the protection scope of the present application.

[0731] It should also be understood that, in various method embodiments of the present application, the size of the sequence number of the above-described processes does not mean the order of execution, and the execution order of the processes should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. In addition, in the embodiments of the present application, the terms "downlink", "uplink" and "sidelink" are used to represent the transmission direction of signals or data, wherein "downlink" is used to represent the transmission direction of signals or data as the first direction from the station to the user equipment of the cell, "uplink" is used to represent the transmission direction of signals or data as the second direction from the user equipment of the cell to the station, and "sidelink" is used to represent the transmission direction of signals or data as the third direction from the user equipment 1 to the user equipment 2. For example, "downlink signal" represents that the transmission direction of the signal is the first direction. In addition, in the embodiments of the present application, the term "and / or" is only used to describe the association relationship of the associated objects, which means that there can be three relationships. Specifically, A and / or B can represent three cases of A alone, A and B together, and B alone. In addition, the character " / " in this paper generally represents that the front and rear associated objects are in an "or" relationship.

[0732] FIG. 17 is a structural composition schematic diagram of a first terminal device provided by an embodiment of the present application, as shown in FIG. 17, the first terminal device 1700 includes:

[0733] The first communication unit 1701 is configured to send first information to a network device;

[0734] The first information is used to determine second information, the second information includes first configuration information corresponding to each of one or more terminal devices on a multi-hop link, the one or more terminal devices include a remote device and / or one or more relay devices, and the second information is used by the relay device to determine a routing mode of data.

[0735] In some embodiments, the first communication unit 1701 is further configured to send, to the network device, a first message including third information corresponding to the second terminal device, the third information being used by the network device to allocate first configuration information corresponding to the second terminal device to the second terminal device.

[0736] The first information includes third information corresponding to each of the one or more terminal devices.

[0737] In some embodiments,

[0738] The first terminal device is a parent node of the second terminal device; and / or,

[0739] The first terminal device is a relay device directly connected to the network device.

[0740] In some embodiments, the first terminal device establishes an RRC connection with the network device.

[0741] In some embodiments, the second terminal device is a remote terminal device, and the first terminal device is a relay device directly connected to the network device.

[0742] In some embodiments, the relay device between the second terminal device and the first terminal device does not establish an RRC connection with the network device.

[0743] In some embodiments, the second terminal device is any terminal device in the multi-hop link, and the first terminal device is a parent node of the second terminal device.

[0744] In some embodiments, the first communication unit 1701 is further configured to receive a second message sent by the network device, the second message including first configuration information corresponding to the second terminal device.

[0745] In some embodiments, the first communication unit 1701 is further configured to forward the first configuration information corresponding to the second terminal device to the second terminal device.

[0746] In some embodiments, the first communication unit 1701 is further configured to receive a third message sent by the second terminal device, the third message being used to request establishment of an RRC connection of the second terminal device;

[0747] The first terminal device sends a fourth message to the network device, the fourth message being determined based on the third message.

[0748] In some embodiments, the first communication unit 1701 is further configured to, in response to the third message, establish an RRC connection between the first terminal device and the network device.

[0749] The RRC connection establishment cause is determined based on the first terminal device, based on the third message, or predefined.

[0750] In some embodiments, the SRAP packet header of the fourth message comprises one or more of the following:

[0751] A first local device identifier of the second terminal device, which is configured by the network device for the second terminal device;

[0752] A first bearer ID, which is configured by the network device, default, or predefined;

[0753] First indication information, which is used to indicate the transmission direction of the fourth message.

[0754] In some embodiments, the first communication unit 1701 is further configured to receive a fifth message sent by the network device, the fifth message being used to indicate the establishment of an RRC connection between the second terminal device and the network device;

[0755] The first terminal device sends a sixth message, which is determined based on the fifth message.

[0756] In some embodiments, the fifth message contains first configuration information of the second terminal device allocated by the network device.

[0757] In some embodiments, the SRAP packet header of the fifth message comprises one or more of the following:

[0758] A first local device identifier of the second terminal device, which is configured by the network device for the second terminal device;

[0759] A first bearer ID, which is configured by the network device, default, or predefined;

[0760] Second indication information, which is used to indicate the transmission direction of the fifth message.

[0761] In some embodiments, the first configuration information of the second terminal device is sent by the network device to all terminal devices except the second terminal device on a first link between the second terminal device and the network device.

[0762] In some embodiments, the first communication unit 1701 is further configured to send, to the network device, a first message including the first information, the first terminal device being a relay device directly connected to the network device, the first information being used by the network device to allocate the second information.

[0763] In some embodiments, the first communication unit 1701 is further configured to receive a second message sent by the network device, the second message including the second information.

[0764] In some embodiments, the first communication unit 1701 is further configured to, before sending the first message, receive a third message sent by a second terminal device, the third message being used to request to establish an RRC connection between the second terminal device and the network device or being used to indicate that a remote terminal device requests to establish an RRC connection with the network device, the second terminal device being one terminal device on the multi-hop link except the first terminal device.

[0765] In some embodiments, the third message includes one or more of the following:

[0766] device identifier of the second terminal device and / or first indication information, the first indication information being used to indicate a reason for the second terminal device to establish an RRC connection;

[0767] second indication information, the second indication information being used to indicate an RRC connection establishment indication of a child node of the second terminal device.

[0768] In some embodiments, the first communication unit 1701 is further configured to send the second information to other terminal devices on the multi-hop link except the first terminal device; or,

[0769] send the second information to a third terminal device, so that the second information is sent by parent nodes to child nodes on the multi-hop link in turn, the third terminal device being a child node of the first terminal device.

[0770] In some embodiments, the first communication unit 1701 is further configured to send a fourth message to the network device, the fourth message indicating to establish an RRC connection between the second terminal device and the network device, the fourth message being determined based on the third message.

[0771] In some embodiments, the first communication unit 1701 is further configured to:

[0772] receive a fifth message sent by the network device;

[0773] transmit a sixth message, the sixth message being determined based on the fifth message that the sixth message is for the network device to send to the second terminal device, the fifth message being used to indicate to establish the RRC connection between the second terminal device and the network device;

[0774] The fifth message contains first configuration information corresponding to the second terminal device.

[0775] In some embodiments, the first message includes the first information and fourth information of one or more fourth terminal device configurations;

[0776] The fourth information includes second configuration information for part or all of the one or more terminal devices, and the fourth information is used by the relay device to determine the routing manner of data, and the fourth terminal device is one terminal device on the multi-hop link.

[0777] In some embodiments, the first configuration information corresponding to the fifth terminal device includes the second configuration information and / or third information, and the third information is configuration information reconfigured by the network device based on the third information of the fifth terminal device in the first information, and the fifth terminal device is one terminal device in the one or more terminal devices.

[0778] In some embodiments, the first configuration information includes the second configuration information and the third configuration information,

[0779] The Uu link performs data transmission based on the third configuration information, and the PC5 link performs data transmission based on the second configuration information; or,

[0780] The multi-hop link performs data transmission based on the second configuration information;

[0781] The link between the network device and the terminal device performs data transmission based on the third configuration information, and the link between the two terminal devices performs data transmission based on the second configuration information.

[0782] In some embodiments, the end-to-end communication between terminal devices in the same terminal device group is based on the second configuration information allocated by the corresponding fourth terminal device; or,

[0783] Different fourth terminal devices allocate different second configuration information to the same terminal device, and the terminal device uses different second configuration information for data transmission in different PC5 links;

[0784] Wherein, the fourth information of different terminal device groups is allocated based on different fourth terminal devices.

[0785] In some embodiments, the first communication unit 1701 is further configured to receive a second message sent by the network device, the second message comprising the second information.

[0786] In some embodiments, the first communication unit 1701 is further configured to receive, before sending the first message, a third message sent by a second terminal device, the third message being used to request to establish an RRC connection between the second terminal device and the network device.

[0787] In some embodiments, the first terminal device and the remote terminal device have a non-direct end-to-end connection established therebetween.

[0788] In some embodiments, the first message comprises fourth information of a plurality of fourth terminal devices,

[0789] A non-direct end-to-end communication is established between a child node of the fourth terminal device and a parent node of the fourth terminal device, wherein the second configuration information of the child node of the fourth terminal device and the second configuration information of the parent node of the fourth terminal device are allocated by the fourth terminal device.

[0790] In some embodiments, the first communication unit 1701 is further configured to send a fourth message to the network device, the fourth message being determined based on the third message.

[0791] In some embodiments, the first communication unit 1701 is further configured to receive a fifth message sent by the network device, the fifth message being used to instruct to establish the RRC connection of the second terminal device, the fifth message comprising the first configuration information corresponding to the second terminal device in the second information;

[0792] The first terminal device sends a sixth message to the second terminal device, the sixth message being determined based on the fifth message.

[0793] In some embodiments, the SRAP header of the fourth message comprises one or more of the following:

[0794] A local device identifier of the remote device in the second information;

[0795] A local device identifier of the second terminal device in the second information;

[0796] A bearer ID in the second information;

[0797] First indication information, the first indication information being used to indicate a transmission direction of the fourth message.

[0798] In some embodiments, the fourth message is transmitted on a first radio link control (RLC) channel, which is configured, default, or predefined for the network device.

[0799] In some embodiments, the configuration of the first RLC channel is related to one or more of: local device identity, link, remote terminal, bearer, transmission direction.

[0800] In some embodiments, the SRAP header of the fifth message includes one or more of:

[0801] the local device identity of the remote device in the second information; the local device identity of the second terminal device in the second information; the bearer ID in the second information;

[0802] second indication information, which is used to indicate the transmission direction of the fifth message.

[0803] In some embodiments, the fifth message is transmitted on a second RLC channel, which is configured, default, or predefined for the network device.

[0804] In some embodiments, the configuration of the second RLC channel is related to one or more of: local device identity, link, remote terminal, bearer, transmission direction.

[0805] In some embodiments, the first information includes one or more of:

[0806] device identity information, which is used to indicate the device identity of each terminal device in the one or more terminal devices;

[0807] first quality of service information.

[0808] In some embodiments, the first quality of service information includes one or more of: quality of service information of the multi-hop link; quality of service information of a Uu segment in the multi-hop link, and / or quality of service information of one or more PC5 segments in the multi-hop link.

[0809] In some embodiments, the device identity information and the first quality of service information are transmitted in different messages.

[0810] In some embodiments, the configuration information of the terminal device includes one or more of: local device identity; bearer configuration.

[0811] In some embodiments, the bearer configuration includes one or more of: bearer ID; RLC channel configuration information; bearer transmission direction.

[0812] In some embodiments, the local device identity and the bearer configuration are transmitted in different messages.

[0813] FIG. 18 is a schematic diagram of a structure of a network device according to an embodiment of the present application. As shown in FIG. 18, the network device 1800 includes:

[0814] a second communication unit 1801, configured to receive first information sent by a first terminal device;

[0815] The first information is used to determine second information, and the second information includes first configuration information corresponding to each of one or more terminal devices on a multi-hop link, the one or more terminal devices including a remote device and / or one or more relay devices, and the second information is used by the relay device to determine a routing manner of data.

[0816] In some embodiments, the second communication unit 1801 is further configured to receive a first message sent by the first terminal device, the first message including third information corresponding to a second terminal device, the third information being used by the network device to allocate the first configuration information corresponding to the second terminal device to the second terminal device, and the first information including the third information corresponding to each of the one or more terminal devices.

[0817] In some embodiments, the first terminal device is a parent node of the second terminal device; and / or,

[0818] The first terminal device is a relay device directly connected to the network device.

[0819] In some embodiments, the first terminal device establishes an RRC connection with the network device.

[0820] In some embodiments, the second terminal device is a remote device, and the first terminal device is a relay device directly connected to the network device.

[0821] In some embodiments, the relay device between the second terminal device and the first terminal device does not have an RRC connection with the network device.

[0822] In some embodiments, the second terminal device is any terminal device on the multi-hop link, and the first terminal device is a parent node of the second terminal device.

[0823] In some embodiments, the second communication unit 1801 is further configured to send a second message to the first terminal device, the second message including the first configuration information corresponding to the second terminal device.

[0824] In some embodiments, the first configuration information corresponding to the second terminal device is forwarded by the first terminal device to the second terminal device.

[0825] In some embodiments, the second communication unit 1801 is further configured to receive a fourth message sent by the first terminal device, the fourth message being determined based on the third message, the third message being used to request to establish an RRC connection of the second terminal device.

[0826] The third message is received by the first terminal device from the second terminal device.

[0827] In some embodiments, the RRC connection establishment reason is determined based on the first terminal device, or based on the third message, or predefined.

[0828] In some embodiments, the SRAP packet header of the fourth message comprises one or more of the following:

[0829] The first local device identifier of the second terminal device, the first local device identifier being configured by the network device for the second terminal device;

[0830] The first bearer ID; the first bearer ID being configured by the network device, default or predefined;

[0831] The first indication information, the first indication information being used to indicate the transmission direction of the fourth message.

[0832] In some embodiments, the second communication unit 1801 is further configured to send a fifth message to the first terminal device, the fifth message being used to indicate to establish an RRC connection between the second terminal device and the network device.

[0833] The fifth message is used to determine a sixth message, the sixth message being sent by the first terminal device.

[0834] In some embodiments, the fifth message contains the first configuration information corresponding to the second terminal device allocated by the network device.

[0835] In some embodiments, the SRAP packet header of the fifth message comprises one or more of the following:

[0836] The first local device identifier of the second terminal device, the first local device identifier being configured by the network device for the second terminal device;

[0837] The first bearer ID; the first bearer ID being configured by the network device, default or predefined;

[0838] The second indication information is used for indicating a transmission direction of the fifth message.

[0839] In some embodiments, the first configuration information corresponding to the second terminal device is transmitted by the network device to all terminal devices except the second terminal device on the first link, the first link being a link between the second terminal device and the network device.

[0840] In some embodiments, the second communication unit 1801 is further configured to receive a first message transmitted by a first terminal device, the first message comprising the first information, the first terminal device being a relay device directly connected to the network device, and the first information being used for the network device to allocate the second information.

[0841] In some embodiments, the second communication unit 1801 is further configured to transmit a second message to the first terminal device, the second message comprising the second information.

[0842] In some embodiments, the second communication unit 1801 is further configured to receive a fourth message transmitted by the first terminal device, the fourth message indicating to establish an RRC connection between a second terminal device and the network device, the second terminal device being one terminal device on the multi-hop link except the first terminal device, and the fourth message being determined based on a third message transmitted by the second terminal device.

[0843] In some embodiments, the second communication unit 1801 is further configured to transmit a fifth message to the first terminal device;

[0844] The fifth message is transparently transmitted by the first terminal device, or a sixth message is transmitted by the first terminal device, the sixth message being determined based on the fifth message, the sixth message being transmitted by the network device to the second terminal device, and the fifth message being used for indicating to establish an RRC connection between the second terminal device and the network device.

[0845] The fifth message comprises first configuration information corresponding to the second terminal device.

[0846] In some embodiments, the first message comprises the first information and fourth information configured for one or more fourth terminal devices.

[0847] The fourth information comprises second configuration information for part or all of the one or more terminal devices, and the fourth information is used for the relay device to determine a routing manner of data, the fourth terminal device being one terminal device on the multi-hop link.

[0848] In some embodiments, the first configuration information corresponding to the fifth terminal device includes the second configuration information and / or third information, the third configuration information being reconfigured by the network device based on the third information of the fifth terminal device in the first information, and the fifth terminal device being one of the one or more terminal devices.

[0849] In some embodiments, the first configuration information includes the second configuration information and the third configuration information,

[0850] The Uu link performs data transmission based on the third configuration information, and the PC5 link performs data transmission based on the second configuration information; or,

[0851] The multi-hop link performs data transmission based on the second configuration information.

[0852] The link between the network device and the terminal device performs data transmission based on the third configuration information, and the link between the two terminal devices performs data transmission based on the second configuration information.

[0853] In some embodiments, the end-to-end communication between terminal devices in the same terminal device group is based on the second configuration information allocated by the corresponding fourth terminal device; or,

[0854] The different fourth terminal devices allocate different second configuration information to the same terminal device, and the terminal device uses different second configuration information for data transmission in different PC5 links.

[0855] Wherein, the fourth information of different terminal device groups is allocated based on different fourth terminal devices.

[0856] In some embodiments, the second communication unit 1801 is further configured to send a second message to the first terminal device, the second message including the second information.

[0857] In some embodiments, the first terminal device and the remote terminal device have established a non-direct end-to-end connection.

[0858] In some embodiments, the first message includes fourth information of a plurality of fourth terminal devices,

[0859] The fourth terminal device and the parent node of the fourth terminal device have established non-direct end-to-end communication, wherein the second configuration information of the child node of the fourth terminal device and the second configuration information of the parent node of the fourth terminal device are allocated by the fourth terminal device.

[0860] In some embodiments, the second communication unit 1801 is further configured to receive a fourth message sent by the first terminal device, the fourth message being determined based on a third message sent by the second terminal device, the third message being used to request to establish the RRC connection of the second terminal device.

[0861] In some embodiments, the second communication unit 1801 is further configured to send a fifth message to the first terminal device, the fifth message being used to indicate to establish the RRC connection of the second terminal device, the fifth message comprising the first configuration information corresponding to the second terminal device in the second information;

[0862] A sixth message is sent by the first terminal device to the second terminal device, the sixth message being determined based on the fifth message.

[0863] In some embodiments, the SRAP packet header of the fourth message comprises one or more of the following:

[0864] The local device identifier of the remote device in the second information; the local device identifier of the second terminal device in the second information; the bearer ID in the second information; first indication information, the first indication information being used to indicate the transmission direction of the fourth message.

[0865] In some embodiments, the fourth message is transmitted on a first radio link control (RLC) channel, the first RLC channel being configured, default or predefined by the network device.

[0866] In some embodiments, the configuration of the first RLC channel is related to one or more of the following: local device identifier, link, remote terminal, bearer, transmission direction.

[0867] In some embodiments, the SRAP packet header of the fifth message comprises one or more of the following: the local device identifier of the remote device in the second information; the local device identifier of the second terminal device in the second information; the bearer ID in the second information;

[0868] Second indication information, the second indication information being used to indicate the transmission direction of the fifth message.

[0869] In some embodiments, the fifth message is transmitted on a second RLC channel, the second RLC channel being configured, default or predefined by the network device.

[0870] In some embodiments, the configuration of the second RLC channel is related to one or more of the following: local device identifier, link, remote terminal, bearer, transmission direction.

[0871] In some embodiments, the first information comprises one or more of the following:

[0872] device identification information, the identification information being used to indicate a device identification of each terminal device in the one or more terminal devices;

[0873] first quality of service information.

[0874] In some embodiments, the first quality of service information comprises one or more of the following: quality of service information of the multi-hop link; quality of service information of a Uu segment in the multi-hop link, and / or quality of service information of one or more PC5 segments in the multi-hop link.

[0875] In some embodiments, the device identification information and the first quality of service information are transmitted in different messages.

[0876] In some embodiments, the configuration information of the terminal device comprises one or more of the following: a local device identification; a bearer configuration.

[0877] In some embodiments, the bearer configuration comprises one or more of the following: a bearer ID; RLC channel configuration information; a bearer transmission direction.

[0878] In some embodiments, the local device identification and the bearer configuration are transmitted in different messages.

[0879] Those skilled in the art should understand that the above description of the device of the embodiments of the present application can be understood with reference to the description of the wireless communication method of the embodiments of the present application.

[0880] FIG. 19 is a schematic structural diagram of a communication device 1900 provided by an embodiment of the present application. The communication device can be a first terminal device or a network device. The communication device 1900 shown in FIG. 19 comprises a processor 1910, which can call and run a computer program from a memory to implement the method in the embodiments of the present application.

[0881] Optionally, as shown in FIG. 19, the communication device 1900 can further comprise a memory 1920. The processor 1910 can call and run a computer program from the memory 1920 to implement the method in the embodiments of the present application.

[0882] The memory 1920 can be a separate device independent of the processor 1910, or can be integrated in the processor 1910.

[0883] Optionally, as shown in FIG. 19, the communication device 1900 can further include a transceiver 1930, which can be controlled by the processor 1910 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

[0884] The transceiver 1930 can include a transmitter and a receiver. The transceiver 1930 can further include an antenna, and the number of antennas can be one or more.

[0885] Optionally, the communication device 1900 can be specifically a first terminal device of the embodiments of the present application, and the communication device 1900 can implement the corresponding procedures in the various methods of the embodiments of the present application that are implemented by the first terminal device. For the sake of brevity, details are not described herein.

[0886] Optionally, the communication device 1900 can be specifically a network device of the embodiments of the present application, and the communication device 1900 can implement the corresponding procedures in the various methods of the embodiments of the present application that are implemented by the network device. For the sake of brevity, details are not described herein.

[0887] FIG. 20 is a schematic structural diagram of a chip according to the embodiments of the present application. The chip 2000 shown in FIG. 20 includes a processor 2010, which can call and run a computer program from a memory to implement the methods in the embodiments of the present application.

[0888] Optionally, as shown in FIG. 20, the chip 2000 can further include a memory 2020. The processor 2010 can call and run a computer program from the memory 2020 to implement the methods in the embodiments of the present application.

[0889] The memory 2020 can be a separate device independent of the processor 2010, or can be integrated in the processor 2010.

[0890] Optionally, the chip 2000 can further include an input interface 2030. The processor 2010 can control the input interface 2030 to communicate with other devices or chips, specifically, to obtain information or data sent by other devices or chips.

[0891] Optionally, the chip 2000 can further include an output interface 2040. The processor 2010 can control the output interface 2040 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.

[0892] Optionally, the chip can be applied to a first terminal device in the embodiments of the present application, and the chip can implement the corresponding procedures in the various methods of the embodiments of the present application that are implemented by the first terminal device. For the sake of brevity, details are not described herein.

[0893] Optionally, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding procedures implemented by the network device in the various methods of the embodiments of the present application. For brevity, details are not repeated here.

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

[0895] FIG. 21 is a schematic block diagram of a communication system 2100 provided by the embodiments of the present application. As shown in FIG. 21, the communication system 2100 includes a first terminal device 2110 and a network device 2120.

[0896] The first terminal device 2110 can be used to implement the corresponding functions implemented by the first terminal device in the above methods, and the network device 2120 can be used to implement the corresponding functions implemented by the network device in the above methods. For brevity, details are not repeated here.

[0897] It should be understood that the processor of the embodiments of the present application can be an integrated circuit chip having a processing capability of a signal. In the implementation process, each step of the above method embodiments can be completed by integrated logic circuits or instructions in the form of software in the processor. The processor mentioned above can be a general processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a ready programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component. The disclosed methods, steps and logic block diagrams in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can be any conventional processor. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as a hardware coding processor for execution, or a combination of hardware and software modules in the coding processor for execution. The software module can be located in a random access memory, a flash memory, a read only memory, a programmable read only memory or an electrically erasable programmable memory, a register, etc. The storage medium in the art. The storage medium is located in the memory, and the processor reads the information in the memory, and combines the hardware to complete the steps of the above method.

[0898] It is to be understood that the memory in the embodiments of the present application can be a volatile memory or a nonvolatile memory, or can include both volatile and nonvolatile memory. Among them, the nonvolatile memory can be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or a flash memory. The volatile memory can be a random access memory (Random Access Memory, RAM) used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synchlink DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM). It should be noted that the memory of the system and method described herein is intended to include, but not limited to, these and any other suitable types of memory.

[0899] It should be understood that the above-mentioned memory is exemplary but not limiting, for example, the memory in the embodiments of the present application can also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and the like. That is, the memory in the embodiments of the present application is intended to include, but not limited to, these and any other suitable types of memory.

[0900] The embodiment of the present application further provides a computer readable storage medium for storing the computer program.

[0901] Optionally, the computer readable storage medium can be applied to the first terminal device in the embodiment of the present application, and the computer program makes the computer execute the corresponding process realized by the first terminal device in the various methods of the embodiment of the present application. For the sake of brevity, details are not described herein.

[0902] Optionally, the computer readable storage medium can be applied to the network device in the embodiment of the present application, and the computer program makes the computer execute the corresponding process realized by the network device in the various methods of the embodiment of the present application. For the sake of brevity, details are not described herein.

[0903] The embodiment of the present application further provides a computer program product comprising computer program instructions.

[0904] Optionally, the computer program product can be applied to the first terminal device in the embodiment of the present application, and the computer program instructions make the computer execute the corresponding process realized by the first terminal device in the various methods of the embodiment of the present application. For the sake of brevity, details are not described herein.

[0905] Optionally, the computer program product can be applied to the network device in the embodiment of the present application, and the computer program instructions make the computer execute the corresponding process realized by the network device in the various methods of the embodiment of the present application. For the sake of brevity, details are not described herein.

[0906] The embodiment of the present application further provides a computer program.

[0907] Optionally, the computer program can be applied to the first terminal device in the embodiment of the present application, and when the computer program runs on the computer, makes the computer execute the corresponding process realized by the first terminal device in the various methods of the embodiment of the present application. For the sake of brevity, details are not described herein.

[0908] Optionally, the computer program can be applied to the network device in the embodiment of the present application, and when the computer program runs on the computer, makes the computer execute the corresponding process realized by the network device in the various methods of the embodiment of the present application. For the sake of brevity, details are not described herein.

[0909] Those skilled in the art can realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be realized in electronic hardware or in combination of computer software and electronic hardware. Whether the functions are realized in hardware or software mode depends on the specific application and design constraints of the technical solutions. The skilled person can use different methods to realize the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0910] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the system, device and unit described above can refer to the corresponding processes in the foregoing method embodiments, which will not be repeated here.

[0911] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, device or unit, and can be electrical, mechanical or other forms.

[0912] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the embodiment scheme.

[0913] In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit.

[0914] If the functions are realized in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application or the part of the present application that essentially contributes to the prior art or the part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium, and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various program code storage media.

[0915] The above merely provides the specific implementation of the present application, but the protection scope of the present application is not limited to this. Any person skilled in the art can easily think of the changes or replacements within the technical range disclosed by the present application, which should be covered in the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method of wireless communication, the method comprising: a first terminal device sending first information to a network device; the first information being used to determine second information, the second information comprising first configuration information corresponding to each of one or more terminal devices on a multi-hop link, the one or more terminal devices comprising a remote device and / or one or more relay devices, the second information being used by a relay device to determine a routing manner of data.

2. The method of claim 1, wherein, the first information comprising third information corresponding to each of the one or more terminal devices, the first terminal device sending first information to a network device, comprising: the first terminal device sending a first message to the network device, the first message comprising third information corresponding to a second terminal device, the third information being used by the network device to allocate first configuration information corresponding to the second terminal device to the second terminal device.

3. The method of claim 2, wherein, the first terminal device is a parent node of the second terminal device; and / or, the first terminal device is a relay device directly connected to the network device.

4. The method of claim 3, wherein, the first terminal device has an RRC connection with the network device.

5. The method of claim 3 or 4, wherein, the second terminal device is a remote device, and the first terminal device is a relay device directly connected to the network device.

6. The method of claim 5, wherein, a relay device between the second terminal device and the first terminal device does not have an RRC connection with the network device.

7. The method of claim 3 or 4, wherein, the second terminal device is any terminal device in the multi-hop link, and the first terminal device is a parent node of the second terminal device.

8. The method according to any one of claims 2 to 7, wherein, the method further comprising: the first terminal device receiving a second message sent by the network device, the second message containing first configuration information corresponding to the second terminal device.

9. The method of claim 8, wherein, the method further comprising: the first terminal device forwarding the first configuration information corresponding to the second terminal device to the second terminal device.

10. The method of any one of claims 8-9, wherein, the method further comprising: the first terminal device receiving a third message sent by the second terminal device, the third message being used to request establishment of an RRC connection of the second terminal device; the first terminal device sending a fourth message to the network device, the fourth message being determined based on the third message.

11. The method of claim 10, wherein, the method further comprising: the first terminal device establishing an RRC connection between the first terminal device and the network device in response to the third message; wherein an RRC connection establishment cause is determined based on the first terminal device, or based on the third message, or predefined.

12. The method of claim 11, wherein, the SRAP packet header of the fourth message comprising one or more of: a first local device identifier of the second terminal device, the first local device identifier being configured by the network device for the second terminal device; a first bearer ID, the first bearer ID being configured by the network device, default, or predefined; first indication information, the first indication information being used to indicate a transmission direction of the fourth message.

13. The method according to any one of claims 10 to 12, wherein, the method further comprising: The first terminal device receives a fifth message sent by the network device, and the fifth message is used to instruct to establish an RRC connection between the second terminal device and the network device. The first terminal device sends a sixth message, and the sixth message is determined based on the fifth message.

14. The method of claim 13, wherein, The fifth message contains first configuration information corresponding to the second terminal device allocated by the network device.

15. The method of claim 13 or 14, wherein, The SRAP packet header of the fifth message includes one or more of the following: A first local device identifier of the second terminal device, which is configured by the network device for the second terminal device; A first bearer ID, which is a default or predefined bearer ID configured by the network device; Second indication information, which is used to indicate the transmission direction of the fifth message.

16. The method of claim 9 or 14, wherein, The first configuration information corresponding to the second terminal device is sent by the network device to all terminal devices on a first link except the second terminal device, and the first link is a link between the second terminal device and the network device.

17. The method of claim 1, wherein, The first terminal device sends first information to the network device, including: The first terminal device sends a first message to the network device, and the first message includes the first information, the first terminal device is a relay device directly connected to the network device, and the first information is used by the network device to allocate the second information.

18. The method of claim 17, wherein, The method further includes: The first terminal device receives a second message sent by the network device, and the second message includes the second information.

19. The method of claim 18, wherein, The method further includes: Before sending the first message, the first terminal device receives a third message sent by the second terminal device, and the third message is used to request to establish an RRC connection between the second terminal device and the network device or to indicate that a remote terminal device requests to establish an RRC connection with the network device, and the second terminal device is one terminal device on the multi-hop link except the first terminal device.

20. The method of claim 19, wherein, The third message includes one or more of the following: A device identifier of the second terminal device and / or first indication information, the first indication information being used to indicate the reason for establishing an RRC connection by the second terminal device; Second indication information, which is used to indicate the RRC connection establishment indication of a child node of the second terminal device.

21. The method of any one of claims 18 to 20, wherein, The method further includes: The first terminal device sends the second information to other terminal devices on the multi-hop link except the first terminal device; or, The first terminal device sends the second information to a third terminal device, so that the second information is sent by parent nodes to child nodes in the multi-hop link in turn, and the third terminal device is a child node of the first terminal device.

22. The method of any one of claims 19 to 21, wherein, The method further includes: The first terminal device sends a fourth message to the network device, and the fourth message instructs to establish an RRC connection between the second terminal device and the network device, and the fourth message is determined based on the third message.

23. The method of claim 21 or 22, wherein, The method further includes: The first terminal device receives a fifth message sent by the network device; The first terminal device transmits the fifth message or sends a sixth message, the sixth message is determined based on the fifth message that the sixth message is sent by the network device to the second terminal device, and the fifth message is used to indicate establishment of the RRC connection between the second terminal device and the network device. The fifth message contains first configuration information corresponding to the second terminal device.

24. The method of claim 17, wherein, The first message includes the first information and fourth information configured for one or more fourth terminal devices; The fourth information includes second configuration information for part or all of the one or more terminal devices, and the fourth information is used by the relay device to determine the routing mode of data, and the fourth terminal device is one terminal device on the multi-hop link.

25. The method of claim 24, wherein, The first configuration information corresponding to the fifth terminal device includes the second configuration information and / or third information, and the third information is configuration information reconfigured by the network device based on the third information of the second terminal device in the first information, and the fifth terminal device is one terminal device in the one or more terminal devices.

26. The method of claim 25, wherein, The first configuration information includes the second configuration information and the third configuration information, The Uu link performs data transmission based on the third configuration information, and the PC5 link performs data transmission based on the second configuration information; or The multi-hop link performs data transmission based on the second configuration information. The link between the network device and the terminal device performs data transmission based on the third configuration information, and the link between the two terminal devices performs data transmission based on the second configuration information.

27. The method of any one of claims 24 to 26, wherein, The end-to-end communication between terminal devices in the same terminal device group is based on the second configuration information allocated by the corresponding fourth terminal device; or Different fourth terminal devices allocate different second configuration information to the same terminal device, and the terminal device uses different second configuration information for data transmission in different PC5 links; Wherein, the fourth information of different terminal device groups is allocated based on different fourth terminal devices.

28. The method of any one of claims 24 to 27, wherein, The method further comprises: The first terminal device receives a second message sent by the network device, and the second message includes the second information.

29. The method of any one of claims 24 to 27, wherein, The method further comprises: Before sending the first message, the first terminal device receives a third message sent by the second terminal device, and the third message is used to request establishment of the RRC connection between the second terminal device and the network device.

30. The method of claim 29, wherein, The first terminal device and the remote terminal device have a non-direct end-to-end connection established therebetween.

31. The method of claim 30, wherein, The first message includes fourth information of a plurality of fourth terminal devices, The fourth terminal device has a non-direct end-to-end communication established between the child node of the fourth terminal device and the parent node of the fourth terminal device, wherein the second configuration information of the child node of the fourth terminal device and the second configuration information of the parent node of the fourth terminal device are allocated by the fourth terminal device.

32. The method of any one of claims 29 to 31, wherein, The method further comprises: The first terminal device sends a fourth message to the network device, and the fourth message is determined based on the third message.

33. The method of any one of claims 29 to 32, wherein, The method further comprises: The first terminal device receives a fifth message sent by the network device, the fifth message being used to instruct to establish an RRC connection of the second terminal device, and the fifth message comprising first configuration information corresponding to the second terminal device in the second information; The first terminal device sends a sixth message to the second terminal device, the sixth message being determined based on the fifth message.

34. The method of claim 22 or 32, wherein, The SRAP packet header of the fourth message comprises one or more of the following: The local device identifier of the remote device in the second information; The local device identifier of the second terminal device in the second information; The bearer ID in the second information; First indication information, the first indication information being used to indicate the transmission direction of the fourth message.

35. The method of claim 13 or 34, wherein, The fourth message is transmitted on a first radio link control (RLC) channel, the first RLC channel being configured, default or predefined by the network device.

36. The method of claim 35, wherein, The configuration of the first RLC channel is related to one or more of the following: Local device identifier, link, remote terminal, bearer, transmission direction.

37. The method of claim 23 or 33, wherein, The SRAP packet header of the fifth message comprises one or more of the following: The local device identifier of the remote device in the second information; The local device identifier of the second terminal device in the second information; The bearer ID in the second information; Second indication information, the second indication information being used to indicate the transmission direction of the fifth message.

38. The method of claim 15 or 37, wherein, The fifth message is transmitted on a second RLC channel, the second RLC channel being configured, default or predefined by the network device.

39. The method of claim 38, wherein, The configuration of the second RLC channel is related to one or more of the following: Local device identifier, link, remote terminal, bearer, transmission direction.

40. The method of any one of claims 1 to 39, wherein, The first information comprises one or more of the following: Device identifier information, the identifier information being used to indicate the device identifier of each terminal device in the one or more terminal devices; First quality of service (QoS) information.

41. The method of claim 40, wherein, The first QoS information comprises one or more of the following: The QoS information of the multi-hop link; The QoS information of the Uu segment in the multi-hop link, and / or the QoS information of one or more PC5 segments in the multi-hop link.

42. The method of claim 40 or 41, wherein, The device identifier information and the first QoS information are transmitted in different messages.

43. The method of claims 1-42, wherein, The configuration information of the terminal device comprises one or more of the following: Local device identifier; Bearer configuration.

44. The method of claim 43, wherein, The bearer configuration comprises one or more of the following: Bearer ID; RLC channel configuration information; Bearer transmission direction.

45. The method of claim 43 or 44, wherein, The local device identifier and the bearer configuration are transmitted in different messages.

46. A wireless communication method, comprising: A network device receives first information sent by a first terminal device; The first information is used to determine second information, the second information comprising first configuration information corresponding to each terminal device in one or more terminal devices on a multi-hop link, the one or more terminal devices comprising a remote device and / or one or more relay devices, and the second information being used by a relay device to determine the routing manner of data.

47. The method of claim 46, wherein, The first information comprises third information corresponding to each terminal device in the one or more terminal devices, The network device receives first information sent by a first terminal device, including: The network device receives a first message sent by a first terminal device, and the first message includes third information corresponding to a second terminal device, and the third information is used for the network device to allocate first configuration information corresponding to the second terminal device to the second terminal device.

48. The method of claim 47, wherein, The first terminal device is a parent node of the second terminal device; and / or, The first terminal device is a relay device directly connected to the network device.

49. The method of claim 48, wherein, The first terminal device establishes an RRC connection with the network device.

50. The method of claim 48 or 49, wherein, The second terminal device is a remote terminal device, and the first terminal device is a relay device directly connected to the network device.

51. The method of claim 50, wherein, The relay device between the second terminal device and the first terminal device does not have an RRC connection with the network device.

52. The method of claim 48 or 49, wherein, The second terminal device is any terminal device in the multi-hop link, and the first terminal device is a parent node of the second terminal device.

53. The method of any one of claims 47 to 52, wherein, The method further includes: The network device sends a second message to the first terminal device, and the second message includes first configuration information corresponding to the second terminal device.

54. The method of claim 53, wherein, The first configuration information corresponding to the second terminal device is forwarded to the second terminal device by the first terminal device.

55. The method of any one of claims 53-54, wherein, The method further includes: The network device receives a fourth message sent by the first terminal device, and the fourth message is determined based on a third message, and the third message is used to request to establish an RRC connection of the second terminal device; The third message is received by the first terminal device and sent by the second terminal device.

56. The method of claim 55, wherein, The RRC connection establishment reason is based on the first terminal device, or is determined based on the third message, or is predefined.

57. The method of claim 56, wherein, The SRAP packet header of the fourth message includes one or more of the following: A first local device identifier of the second terminal device, which is configured by the network device for the second terminal device; A first bearer ID; the first bearer ID is configured by the network device, is default, or is predefined; First indication information, which is used to indicate the transmission direction of the fourth message.

58. The method of any one of claims 55 to 57, wherein, The method further includes: The network device sends a fifth message to the first terminal device, and the fifth message is used to indicate to establish an RRC connection between the second terminal device and the network device; The fifth message is used to determine a sixth message, and the sixth message is sent by the first terminal device.

59. The method of claim 58, wherein, The fifth message includes first configuration information corresponding to the second terminal device allocated by the network device.

60. The method of claim 58 or 59, wherein, The SRAP packet header of the fifth message includes one or more of the following: A first local device identifier of the second terminal device, which is configured by the network device for the second terminal device; A first bearer ID; the first bearer ID is configured by the network device, is default, or is predefined; Second indication information, which is used to indicate the transmission direction of the fifth message.

61. The method of claim 54 or 59, wherein, The first configuration information corresponding to the second terminal device is sent by the network device to all terminal devices on the first link except the second terminal device, and the first link is a link between the second terminal device and the network device.

62. The method of claim 46, wherein, The network device receives first information sent by a first terminal device, including: The network device receives a first message sent by a first terminal device, and the first message includes the first information, the first terminal device is a relay device directly connected to the network device, and the first information is used for the network device to allocate the second information.

63. The method of claim 61, wherein, The method further includes: The network device sends a second message to the first terminal device, and the second message includes the second information.

64. The method of claim 63, wherein, The method further includes: The network device receives a fourth message sent by the first terminal device, and the fourth message indicates to establish an RRC connection between a second terminal device and the network device, the second terminal device is one terminal device on the multi-hop link except the first terminal device, and the fourth message is determined based on a third message sent by the second terminal device.

65. The method of claim 63, wherein, The method further includes: The network device sends a fifth message to the first terminal device; The fifth message is transparently transmitted by the first terminal device, or a sixth message is sent by the first terminal device, the sixth message is determined based on the fifth message, the sixth message is sent by the network device to the second terminal device, and the fifth message is used to indicate to establish an RRC connection between the second terminal device and the network device; The fifth message includes first configuration information corresponding to the second terminal device.

66. The method of claim 62, wherein, The first message includes the first information and fourth information configured for one or more fourth terminal devices; The fourth information includes second configuration information for part or all of the one or more terminal devices, and the fourth information is used for a relay device to determine a routing manner of data, and the fourth terminal device is one terminal device on the multi-hop link.

67. The method of claim 66, wherein, The first configuration information corresponding to the fifth terminal device includes the second configuration information and / or third information, and the third configuration information is reconfigured by the network device based on third information of the second terminal device in the first information, and the fifth terminal device is one terminal device in the one or more terminal devices.

68. The method of claim 67, wherein, The first configuration information includes the second configuration information and the third configuration information, The Uu link performs data transmission based on the third configuration information, and the PC5 link performs data transmission based on the second configuration information; or The multi-hop link performs data transmission based on the second configuration information; The link between the network device and the terminal device performs data transmission based on the third configuration information, and the link between the two terminal devices performs data transmission based on the second configuration information.

69. The method of any one of claims 66 to 68, wherein, End-to-end communication between terminal devices in the same terminal device group is based on second configuration information allocated by corresponding fourth terminal devices; or Different fourth terminal devices assign different second configuration information to the same terminal device, and the terminal device uses different second configuration information for data transmission on different PC5 links. The fourth information of different terminal device groups is assigned based on different fourth terminal devices.

70. The method of any one of claims 66 to 69, wherein, The method further includes: The network device sends a second message to the first terminal device, and the second message includes the second information.

71. The method of claim 66, wherein, The first terminal device and the remote terminal device have a non-direct end-to-end connection established therebetween.

72. The method of claim 71, wherein, The first message includes fourth information of a plurality of fourth terminal devices, The fourth terminal device has a non-direct end-to-end communication established between a child node of the fourth terminal device and a parent node of the fourth terminal device, wherein the second configuration information of the child node of the fourth terminal device and the second configuration information of the parent node of the fourth terminal device are assigned by the fourth terminal device.

73. The method of any one of claims 66 to 72, wherein, The method further includes: The network device receives a fourth message sent by the first terminal device, and the fourth message is determined based on a third message sent by a second terminal device, wherein the third message is used to request to establish an RRC connection of the second terminal device.

74. The method of any one of claims 66 to 73, wherein, The method further includes: The network device sends a fifth message to the first terminal device, and the fifth message is used to instruct to establish an RRC connection of a second terminal device, and the fifth message includes first configuration information corresponding to the second terminal device in the second information; A sixth message is sent by the first terminal device to the second terminal device, and the sixth message is determined based on the fifth message.

75. The method of claim 64 or 73, wherein, The SRAP packet header of the fourth message includes one or more of the following: A local device identifier of the remote device in the second information; A local device identifier of the second terminal device in the second information; A bearer ID in the second information; First indication information, the first indication information is used to indicate the transmission direction of the fourth message.

76. The method of claim 58 or 75, wherein, The fourth message is transmitted on a first radio link control (RLC) channel, and the first RLC channel is configured, default, or predefined by the network device.

77. The method of claim 76, wherein, The configuration of the first RLC channel is related to one or more of the following: Local device identifier, link, remote terminal, bearer, transmission direction.

78. The method of claim 65 or 74, wherein, The SRAP packet header of the fifth message includes one or more of the following: A local device identifier of the remote device in the second information; A local device identifier of the second terminal device in the second information; A bearer ID in the second information; Second indication information, the second indication information is used to indicate the transmission direction of the fifth message.

79. The method of claim 60 or 78, wherein, The fifth message is transmitted on a second RLC channel, and the second RLC channel is configured, default, or predefined by the network device.

80. The method of claim 79, wherein, The configuration of the second RLC channel is related to one or more of the following: Local device identifier, link, remote terminal, bearer, transmission direction.

81. The method of any one of claims 46 to 80, wherein, The first information includes one or more of the following: Device identifier information, the identifier information is used to indicate the device identifier of each terminal device in the one or more terminal devices; First quality of service information.

82. The method of claim 81, wherein, The first service quality information comprises one or more of the following: The service quality information of the multi-hop link; The service quality information of a Uu segment in the multi-hop link, and / or the service quality information of one or more PC5 segments in the multi-hop link.

83. The method of claim 81 or 82, wherein, The device identity information and the first service quality information are transmitted in different messages.

84. The method of claims 46-83, wherein, The configuration information of the terminal device comprises one or more of the following: A local device identity; A bearer configuration.

85. The method of claim 84, wherein, The bearer configuration comprises one or more of the following: A bearer ID; RLC channel configuration information; A bearer transmission direction.

86. The method of claim 84 or 85, wherein, The local device identity and the bearer configuration are transmitted in different messages.

87. A first terminal device, comprising: A first communication unit configured to send first information to a network device; The first information is used to determine second information, the second information comprising first configuration information corresponding to each of one or more terminal devices on a multi-hop link, the one or more terminal devices comprising a remote device and / or one or more relay devices, the second information being used by a relay device to determine a routing manner of data.

88. A network device, comprising: A second communication unit configured to receive first information sent by a first terminal device; The first information is used to determine second information, the second information comprising first configuration information corresponding to each of one or more terminal devices on a multi-hop link, the one or more terminal devices comprising a remote device and / or one or more relay devices, the second information being used by a relay device to determine a routing manner of data.

89. A communication device, comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to invoke and run the computer program stored in the memory to execute the method of any one of claims 1 to 45, or execute the method of any one of 46 to 86.

90. A communication device, comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to invoke and run the computer program stored in the memory to execute the method of any one of claims 1 to 45, or execute the method of any one of 46 to 86.

91. A chip comprising: A processor, used to invoke and run a computer program from a memory, so that a device installed with the chip executes the method of any one of claims 1 to 45, or executes the method of any one of 46 to 86.

92. A computer readable storage medium, used to store a computer program, the computer program causing a computer to execute the method of any one of claims 1 to 45, or execute the method of any one of 46 to 86.

93. A computer program product, comprising computer program instructions, the computer program instructions causing a computer to execute the method of any one of claims 1 to 45, or execute the method of any one of 46 to 86.

94. A computer program, the computer program causing a computer to execute the method of any one of claims 1 to 45, or execute the method of any one of 46 to 86.

Images