Data transmission and reception method, apparatus, and communication system

Abstract

The present invention provides a data transmission and reception method, apparatus, and communication system. The data transmission and reception method includes a relay terminal device receiving a first data packet transmitted by a source terminal device to a destination terminal device, the first data packet containing data transmitted by the source terminal device to the destination terminal device; determining a first exit RLC channel corresponding to the destination terminal device, with different first exit RLC channels corresponding to different destination terminals; and transmitting a second data packet to the destination terminal device via the determined first exit RLC channel, the second data packet containing the data.

Description

Technical Field

[0001] The present invention relates to the technical field of wireless communication.

Background Art

[0002] In the standardization process of 3GPP (registered trademark) (3rd Generation Partnership Project)'s 5G mobile communication technology (5th Generation Mobile Communication Technology), new technologies have been introduced, which permit user equipment (UE) to directly discover and / or communicate with each other using sidelink (SL) communication technology, where the sidelink interface is also called the PC5 interface. For example, V2X (vehicle-to-everything) communication, PS (public safety) communication, direct file transmission between user equipment, etc. may depend on communication over the sidelink interface.

[0003] Release 18 explores UE-to-UE relay (U2U relay), specifically the communication between a "Source UE" and a "Destination UE" (which may also be called a "Source remote UE" and a "Destination remote UE," or collectively referred to as a "remote UE") via a "Relay UE." Sidelink communication is used between the Source UE and the Relay UE, and between the Relay UE and the Destination UE. This effectively expands the coverage of sidelink transmission between the Source UE and the Destination UE, while also effectively saving the transmission power of the remote UE.

[0004] The above-mentioned introduction of background art is intended to clearly and completely explain the proposed technical aspects of the present invention and to facilitate understanding by those skilled in the art. These technical aspects, as described in the background art of the present invention, should not be construed as being well-known to those skilled in the art. [Overview of the Initiative] [Problems that the invention aims to solve]

[0005] Release 18 agrees on the use of user-plane protocol stacks and control-plane protocol stacks that incorporate an adaptive layer in research on U2U relay, and this adaptive layer may also be called the SRAP (Sidelink Relay Adaptation Protocol) layer.

[0006] The inventor discovered the following: In the case of a U2U relay, the problems that need to be solved are whether to support multiplexing data from different destination UEs onto the same RLC channel, and how to perform the data transmission.

[0007] To solve at least one of the above-mentioned problems or other similar problems, embodiments of the present invention provide a data transmission and reception method and apparatus and a communication system. [Means for solving the problem]

[0008] According to one aspect of an embodiment of the present invention, a data transmission and reception device is provided, which is placed in a relay terminal device, and the device is A receiving unit for receiving a first data packet transmitted by a source terminal device to a destination terminal device, wherein the first data packet includes data transmitted by the source terminal device to the destination terminal device; A first determination unit for determining a first exit RLC channel corresponding to the destination terminal equipment, wherein the first exit RLC channels corresponding to different destination terminals are different; and A transmitting unit for transmitting a second data packet to the destination terminal device via the confirmed first exit RLC channel, wherein the second data packet includes the data.

[0009] According to another aspect of the embodiments of the present invention, a data transmission and reception method is provided, which is applied to relay terminal equipment, and the method is The source terminal device receives a first data packet that the destination terminal device transmits, and the first data packet includes data that the source terminal device transmits to the destination terminal device. Determine the first exit RLC channel corresponding to the destination terminal device, and determine the first exit RLC channel corresponding to a different destination terminal; and The process includes transmitting a second data packet to the destination terminal device via the confirmed first exit RLC channel, wherein the second data packet contains the data.

[0010] According to another aspect of the embodiment of the present invention, a terminal device is provided which includes a memory and a processor, wherein the memory stores a computer program and the processor is configured to execute the computer program to realize the above-described data transmission and reception method on the relay terminal device side.

[0011] According to another aspect of the embodiment of the present invention, a data transmission device is provided, which is located in a source terminal device, and the device is A determination unit for determining a second exit RLC channel corresponding to a destination terminal device, wherein different destination terminal devices correspond to the same second exit RLC channel; and A transmitting unit for transmitting data packets to a relay terminal device via the confirmed second exit RLC channel, wherein the source terminal device transmits the data packets to a different destination terminal device, the data packets include data transmitted by the source terminal device to the destination terminal device.

[0012] According to another aspect of the embodiment of the present invention, a data transmission method is provided which is applied to a source terminal device, and it is Determine the second exit RLC channel corresponding to the destination terminal device, and different destination terminal devices correspond to the same second exit RLC channel; and The confirmed second exit RLC channel transmits a data packet to the relay terminal device that the source terminal device will transmit to a different destination terminal device, and the data packet includes data that the source terminal device will transmit to the destination terminal device.

[0013] According to another aspect of the embodiment of the present invention, a data transmission device is provided, which is located in a source terminal device, and the device is A determination unit for determining a third exit RLC channel corresponding to a destination terminal device, wherein different destination terminal devices correspond to different third exit RLC channels; and Includes a transmission unit for transmitting data packets that the source terminal device transmits to the destination terminal device via the confirmed third exit RLC channel to the relay terminal device, The data packet includes data transmitted by the source terminal device to the destination terminal device, and a wireless bearer label, but does not include a label that can be mapped to the destination terminal device.

[0014] According to another aspect of the embodiment of the present invention, a data transmission method is provided which is applied to a source terminal device, and it is Determine the third exit RLC channel corresponding to the destination terminal device, and different destination terminal devices will correspond to different third exit RLC channels; and This includes transmitting data packets that the source terminal device intends to send to the destination terminal device to the relay terminal device via the confirmed third exit RLC channel, The data packet includes data transmitted by the source terminal device to the destination terminal device, and a wireless bearer label, but does not include a label that can be mapped to the destination terminal device.

[0015] According to another aspect of the embodiment of the present invention, a terminal device is provided which includes a memory and a processor, wherein the memory stores a computer program and the processor executes the computer program to realize the above-described data transmission method on the source terminal device side.

[0016] According to another aspect of the embodiment of the present invention, a communication system is provided, which is, A source terminal device configured to perform the data transmission method on the source terminal device side described above; A relay terminal device configured to perform the above-described data transmission and reception method on the relay terminal device side; and A destination terminal device configured to receive data packets transmitted by the relay terminal device, and includes the same.

Advantages of the Invention

[0017] The advantageous effects in the embodiments of the present invention are at least as follows: that is, different destination terminals correspond to different egress RLC channels, the relay device determines the egress RLC channel corresponding to the destination terminal device, and based on the determined egress RLC channel, the received data can be transmitted to the corresponding destination terminal device. Thereby, whether or not multiplexing the data of different destination terminal devices onto the same RLC channel is supported, the received data can be transmitted to the corresponding destination terminal device, so that the above problems existing in the prior art can be solved.

[0018] Specific embodiments of the present invention are disclosed in detail by referring to the following description and drawings, showing aspects in which the principles of the present invention can be employed. It should be noted that the embodiments of the present invention are not limited in scope by these. Within the scope of the appended claims, the embodiments of the present invention may include various changes, modifications, and substitutions.

[0019] Also, the features described and / or shown for one embodiment can be used in one or more other embodiments in the same or similar manner, combined with the features in other embodiments, or replace the features in other embodiments.

[0020] It should be noted that terms such as "comprising / including" when used in this specification refer to the presence of features, elements, steps, or assemblies, but also refer to not excluding the presence or addition of one or more other features, elements, steps, or assemblies.

Brief Description of the Drawings

[0021] Elements and features described in one drawing or one embodiment of the present invention can be combined with elements and features shown in one or more other drawings or embodiments. Furthermore, in the drawings, the same reference numerals are used to indicate corresponding parts in several drawings and to indicate corresponding parts used in multiple embodiments.

[0022] Furthermore, the included drawings are used to provide a further understanding of embodiments of the present invention, and they constitute part of the specification, illustrating embodiments of the present invention and, together with the textual description, are used to explain the principles of the present invention. As is clear, the following drawings are only a few embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings without any creative effort. [Figure 1] This figure shows the system protocol stack architecture in an embodiment of the present invention. [Figure 2] This figure shows a scenario according to an embodiment of the present invention. [Figure 3] This figure shows a data transmission and reception method in an embodiment of the present invention. [Figure 4] This figure shows a data transmission and reception method in an embodiment of the present invention. [Figure 5] This figure shows a data transmission method in an embodiment of the present invention. [Figure 6] This figure shows a data transmission method in an embodiment of the present invention. [Figure 7] This figure shows a data reception method in an embodiment of the present invention. [Figure 8] This figure shows an example of data transmission and reception in an embodiment of the present invention. [Figure 9] This figure shows the system protocol stack architecture in an embodiment of the present invention. [Figure 10] This figure shows another example of data transmission and reception in an embodiment of the present invention. [Figure 11] This figure shows the system protocol stack architecture in an embodiment of the present invention. [Figure 12]This figure shows a data transmission and reception device according to an embodiment of the present invention. [Figure 13] This figure shows another data transmission and reception device in an embodiment of the present invention. [Figure 14] This figure shows a data transmission device according to an embodiment of the present invention. [Figure 15] This figure shows a data transmission device according to an embodiment of the present invention. [Figure 16] This figure shows a data receiving device according to an embodiment of the present invention. [Figure 17] This is a configuration diagram of a terminal device in an embodiment of the present invention. [Modes for carrying out the invention]

[0023] The aforementioned and other features of the present invention will become clear by referring to the attached drawings and the following description. While the specification and drawings disclose specific embodiments of the present invention, these represent only a limited number of embodiments in which the principles of the present invention can be employed. It should be understood that the present invention is not limited to the described embodiments, but rather includes all modifications, variations, and substitutions within the scope of the attached claims.

[0024] In this embodiment of the present invention, the terms "communication network" or "wireless communication network" may refer to a network conforming to any communication standard such as LTE (Long Term Evolution), LTE-A (LTE-Advanced), WCDMA (registered trademark) (Wideband Code Division Multiple Access), HSPA (High-Speed ​​Packet Access), etc.

[0025] Furthermore, communication between devices in a communication system may be carried out according to any stage of communication protocol, and may include, but is not limited to, the following communication protocols: namely, 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, 5G, New Radio (NR), and / or other conventional or future-developed communication protocols.

[0026] In this embodiment of the present invention, the term "network device" refers, for example, to a device in a communication system that connects terminal devices to a communication network and provides services to said terminal devices. Network devices may include, but are not limited to, the following: "nodes" and / or "donors" under the IAB architecture, base stations (BS), access points (AP), transmission and reception points (TRP), broadcast transmitters, mobile management entities (MME), network gateways, servers, radio network controllers (RNC), base station controllers (BSC), etc.

[0027] Among these, base stations may include, but are not limited to, Node B (NodeB or NB), Evolutionary Node B (eNodeB or eNB), 5G base stations (gNB), and may also include RRH (Remote Radio Head), RRU (Remote Radio Unit), relay, or low-power nodes (e.g., femto, pico). Furthermore, the term "base station" may include some or all of these functions, and each base station can provide communication coverage to a specific geographic area. For example, a 5G base station gNB may include one gNB CU and one or more gNB DUs, where the CU / DU is a logical node of the gNB having some of the functions of the gNB. The term "cell" may refer to a base station and / or the area it covers, and this depends on the context in which the term is used.

[0028] In this embodiment of the present invention, the terms "User Equipment" (UE) or "Terminal Equipment" (TE) refer to devices that access a communication network via network equipment and receive services from the network. User equipment may be fixed or mobile, and may also be referred to as a mobile station (MS), terminal, subscriber station (SS), access terminal (AT), or station. For example, it may be terminal equipment served by an IAB node or IAB donor under an IAB architecture.

[0029] User devices may include, but are not limited to, the following: cellular phones, PDAs (Personal Digital Assistants), wireless modems, wireless communication devices, mobile devices, machine-type communication devices, laptop computers, cordless phones, smartphones, smartwatches, digital cameras, etc.

[0030] Furthermore, in scenarios such as IoT (Internet of Things), user devices may also be monitoring or measuring devices or equipment, and may include, but are not limited to, the following: machine-type communication (MTC) terminals, in-vehicle communication terminals, D2D (device-to-device) terminals, M2M (machine-to-machine) terminals, etc.

[0031] Furthermore, the terms “network side” or “network equipment side” refer to the network side, or may be a base station, and may include one or more network devices as described above. The terms “user side” or “terminal side” or “terminal equipment side” refer to the user or terminal side, or may be a UE, and may include one or more terminal devices as described above. Unless otherwise specified, “equipment” here may refer to network equipment or terminal equipment.

[0032] Figure 1 shows a system protocol stack architecture in an embodiment of the present invention, and includes a user plane protocol stack diagram (left side of Figure 1) and a control plane protocol stack diagram (right side of Figure 1). As shown in Figure 1, the ADAPT layer is supported in the PC5 interface link. In the user plane protocol stack diagram, the IP layer, SDAP (Service Data Adaptation Protocol) layer, and PDCP (Packet Data Convergence Protocol) layer are located above the ADAPT layer, while the RLC (Radio Link Control) layer, MAC (Media Access Control) layer, and PHY (Physical) layer are located below the ADAPT layer. In the control plane protocol stack diagram, the RRC (Radio Resource Control) layer and PDCP layer are located above the ADAPT layer, while the RLC layer, MAC layer, and PHY layer are located below the ADAPT layer. Optionally, ADAPT in Figure 1 may be replaced with SRAP, but the present invention is not limited thereto. In the user plane protocol stack diagram, the IP layer, SDAP layer, and PDCP layer are terminated between two remote UEs, and the RLC layer, MAC layer, and PHY layer are terminated on each PC5 link. In the control plane protocol stack diagram, the RRC layer and PDCP layer are terminated between two remote UEs, and the RLC layer, MAC layer, and PHY layer are terminated on each PC5 link.

[0033] The following examples illustrate scenarios relating to embodiments of the present invention, but the present invention is not limited thereto.

[0034] Figure 2 shows a scenario of an embodiment of the present invention. For convenience, Figure 2 only describes the signaling interaction and data transmission method between the UE-to-UE relay UE / U2U relay UE, i.e., the relay UE 203, and the source UE 201 and destination UE 202. The source UE may also be referred to as the transmission UE, and the destination UE may also be referred to as the receiving UE or target UE. As shown in Figure 2, a PC5 interface is used between the source UE 201 and the relay UE 203, and between the destination UE 202 and the relay UE 203, and the first hop (1) is used from the source UE 201 to the relay UE. st (hop) and the distance from the relay UE to the destination UE is the second hop (2 nd hop). Among these, Release 18 explores UE-to-UE relays, which can extend the coverage of sidelink transmissions between two remote UEs and save power. The scenarios of the present invention include at least one of the following scenarios, namely, All UEs (Source UE, Relay UE, Destination UE) are within network coverage; All UEs (Source UE, Relay UE, Destination UE) are outside network coverage; or, This is partial coverage, where at least one UE (Source UE, Relay UE, Destination UE) is within network coverage, and at least one UE (Source UE, Relay UE, Destination UE) is outside network coverage.

[0035] Of these, the protocol stack structure of the relay UE 203, source UE 201, and destination UE 202 in Figure 2 can be found in the protocol stack in Figure 1, and a detailed explanation is omitted here.

[0036] The inventors have discovered the following: In the case of Layer 2 (L2) U2U relay, the problem to be solved is whether it is possible to support multiplexing data from different destination UEs onto the same RLC channel. Furthermore, when the source UE supports multiplexing data from different destination UEs onto the same RLC channel, it is currently unclear how the source UE multiplexes and transmits data from different destination UEs onto the same RLC channel. In addition, in the case of a relay UE, since the MAC layer sends data to only one destination L2 ID at a time, it is also unclear how the MAC layer of the relay UE distinguishes between data from different destination UEs and selects the destination UE for data transmission.

[0037] Therefore, whether to support multiplexing data from different destination UEs onto the same RLC channel, and how the UEs perform data transmission, are all issues that need to be resolved.

[0038] In view of at least one of the above-mentioned problems, embodiments of the present invention provide a data transmission and reception method and apparatus and a communication system.

[0039] <Example of the first side view> Figure 3 shows a data transmission and reception method in an embodiment of the present invention. As shown in Figure 3, the method is applied to a relay terminal device, and the method includes the following, namely, 301: The source terminal device receives a first data packet that the destination terminal device transmits, and the first data packet contains data that the source terminal device transmits to the destination terminal device; 302: Determine the first egress RLC channel corresponding to the destination terminal device, and among them, the first egress RLC channels corresponding to different destination terminals will be different; and 303: A second data packet is transmitted to the destination terminal device via the confirmed first exit RLC channel, and the second data packet contains the data.

[0040] According to the above embodiment, different destination terminals correspond to different exit RLC channels, the relay device determines the exit RLC channel corresponding to the destination terminal device, and based on the determined exit RLC channel, can transmit the received data to the corresponding destination terminal device. This solves the problems of the prior art, as it supports and does not support multiplexing data from different destination terminal devices onto the same RLC channel, and can transmit the received data to the corresponding destination terminal device.

[0041] Figure 3 above is provided to illustrate an embodiment of the present invention, but the present invention is not limited thereto. For example, the execution order between each operation can be appropriately adjusted, or some operations can be appropriately increased or decreased. Those skilled in the art can make appropriate modifications based on the above description, not limited to the description in Figure 3.

[0042] In some embodiments, the first data packet that the source terminal device transmits to the destination terminal device, received at 301, may also be transmitted by the source terminal device over the same second exit RLC channel. This allows the source terminal device to multiplex and transmit data over the same exit RLC channel when transmitting data for at least two different destination terminal devices, and the relay terminal device can receive data for at least two different destination terminal devices transmitted over the exit RLC channel. This solves the data transmission and reception problems when supporting data multiplexing.

[0043] In some embodiments, the first data packet received at 301, which the source terminal device transmits to the destination terminal device, may be transmitted by the source terminal device via a different second exit RLC channel. This allows the source terminal device to transmit data for at least two different destination terminal devices via different exit RLC channels, rather than multiplexing and transmitting the data on the same exit RLC channel. This solves the data transmission and reception problems that do not support data multiplexing.

[0044] In some embodiments, determining the first exit RLC channel corresponding to the destination terminal device in 302 includes determining the first exit RLC channel associated with the destination terminal device's radio bearer (RB), where different destination terminal devices' RBs are associated with different first exit RLC channels. For example, determining the first exit RLC channel associated with the destination terminal device's radio bearer (RB) allows 303 to transmit a second data packet over the first exit RLC channel. The relay terminal device can determine the first exit RLC channel associated with the destination terminal device's radio bearer (RB) based on a mapping relationship between the destination terminal device's RB and the exit RLC channel (e.g., obtained by first configuration information or determined by the relay device itself). This allows the received data to be transmitted to the corresponding destination terminal device, whether or not it supports multiplexing data from different destination terminal devices onto the same RLC channel.

[0045] In some embodiments, the first data packet received at 301 may further include a DST ID that can be mapped to a destination terminal device, and a Radio Bearer ID (RB ID). Thus, determining the first exit RLC channel associated with the RB of the destination terminal device at 302 includes determining the first exit RLC channel associated with the RB of the destination terminal device based on the DST ID that can be mapped to the destination terminal device, the Radio Bearer ID, and the first configuration information. For example, a receiving entity of a relay device (e.g., an SRAP receiving entity) receives the first data packet, and by analyzing the data packet, it can obtain the DST ID and RB ID in the header of the first data packet, and the receiving entity forwards the DST ID, RB ID and the data in the first data packet to a transmitting entity (e.g., an SRAP transmitting entity), and the transmitting entity determines the first exit RLC channel based on the obtained DST ID and RB ID and the first configuration information; or, a receiving entity of a relay device (e.g., an SRAP receiving entity) receives the first data packet, forwards it to a transmitting entity (e.g., an SRAP transmitting entity), and the transmitting entity analyzes the data packet to obtain the DST ID and RB ID in the header of the first data packet, and then determines the first exit RLC channel based on the obtained DST ID and RB ID and the first configuration information.

[0046] In some embodiments, the first configuration information includes, but is not limited to, an exit RLC channel associated with the RB of a destination terminal device, or an RB of a destination terminal device associated with an exit RLC channel. For example, the first configuration information includes an exit RLC channel associated with the RB of a destination terminal device, for example, an exit RLC channel identifier (RLC channel ID) associated with one RB ID, of which one RB of a destination terminal device is associated with one exit RLC channel; or the first configuration information includes an RB of a destination terminal device associated with an exit RLC channel, for example, an RB ID associated with one exit RLC channel ID, of which one exit RLC channel is associated with one RB of a destination terminal device. The radio bearer identifier (RB ID) in embodiments of the present invention may be, for example, a Signaling Radio Bearer Identifier (SRB ID) and / or a Data Radio Bearer Identifier (DRB ID). In this way, whether or not it supports multiplexing data from different destination terminal devices onto the same RLC channel, the received data from different destination terminal devices can be transmitted to the corresponding destination terminal devices via different exit RLC channels.

[0047] In some embodiments, 302 determines the first exit RLC channel associated with the RB of the destination terminal device based on a label that can be mapped to the destination terminal device and a radio bearer label. For example, the relay terminal device determines the first exit RLC channel associated with the RB of the destination terminal device based on a label that can be mapped to the destination terminal device, a radio bearer label, and information implemented or stored by the relay device. Implemented refers to the method by which the relay terminal determines the channel itself, and stored information refers to information stored in the relay terminal, such as information stored based on previous configuration information or information stored at the time of shipment of the relay terminal device.

[0048] In some embodiments, different RBs of a pair of source terminal devices and destination terminal devices have different RB IDs, i.e., the source terminal device's label, the destination terminal device's label, and the RB ID can label one RB; or, in a source terminal device, different RBs of the same or different destination terminal devices have different RB IDs, i.e., the source terminal device's label and the RB ID can label one RB; or, in a destination terminal device, different RBs of the same or different source terminal devices have different RB IDs, i.e., the destination terminal device's label and the RB ID can label one RB, or the RB ID can label one RB.

[0049] The relationship between the “source terminal device identifier” in this embodiment and the “indicator that can be mapped to a source terminal device” in the aforementioned other embodiments is as follows: the “indicator that can be mapped to a source terminal device” includes the “source terminal device identifier,” and the source terminal device identifier may be, for example, the L2 identifier of the source terminal device or the local identifier of the source terminal device. Similarly, the relationship between the “destination terminal device identifier” in this embodiment and the “indicator that can be mapped to a destination terminal device” in the aforementioned other embodiments is as follows: the “indicator that can be mapped to a destination terminal device” includes the “destination terminal device identifier,” and the destination terminal device identifier may be, for example, the L2 identifier of the destination terminal device or the local identifier of the destination terminal device.

[0050] In some embodiments, the first configuration information may come from a network device and / or a source terminal device and / or from the pre-configuration of a relay terminal device, but the present invention is not limited thereto. For example, the first configuration information may be transmitted to a relay terminal device by a network device, for example, by the network device via system information or a dedicated RRC message; and / or, the first configuration information may be transmitted to a relay terminal device by a source terminal device, for example, by the source terminal device via a PC5-RRC message or PC5-S signaling; and / or, the first configuration information may be included in the pre-configuration information of the relay terminal device, for example, in the pre-configuration of the relay terminal device. In such cases, the method further includes (not shown) acquiring the first configuration information. The first configuration information may be acquired in the following manner, namely, the relay terminal device receives the first configuration information transmitted by the network device and / or the source terminal device; and / or acquires the first configuration information from the pre-configuration information of the relay terminal device.

[0051] In some embodiments, the identifiers that can be mapped to the destination terminal device include, namely, the Layer-2 (L2) identifier (L2 ID) of the source terminal device; or the L2 identifier of the destination terminal device; or a pair of L2 identifiers of the source terminal device and the L2 identifier of the destination terminal device. For example, the L2 identifier of the source terminal device and / or the L2 identifier of the destination terminal device can be determined by the V2X layer of the source terminal device according to a conventional method, and the length of the L2 identifier is 24 bits.

[0052] In some embodiments, the identifier (DST ID) that can be mapped to the destination terminal device may further be: a local identifier (local ID) of the source terminal device; or a local identifier of the destination terminal device; or a pair of local identifiers of the source terminal device and the destination terminal device; or a pair of local identifiers of the source terminal device and the destination terminal device. For example, the length of the local identifier of the source terminal device and the local identifier of the destination terminal device may be less than 24 bits, and the pair of local identifiers of the source terminal device and the destination terminal device may be a pair of local identifiers of the source terminal device and the destination terminal device, for example, local ID of the source terminal device + local ID of the destination terminal device, for example, if the length of the local ID of the source terminal device and the local ID of the destination terminal device are both 8 bits, then the length of the local identifier pair is 16 bits; and the pair of local identifiers of the source terminal device and the destination terminal device may be a single local ID set or used by a pair of source terminal devices and destination terminal devices, the local ID identifies this pair of source terminal devices and destination terminal devices. The length of the local ID mentioned above may be, for example, 4 bits, 8 bits, or 12 bits. Therefore, overhead can be saved when the local identifier is used as an identifier that can be mapped to a destination terminal device. The specific content and method of determining the local ID can be found in the prior art, and the present invention is not limited thereto.

[0053] In some embodiments, 303 transmits a second data packet to the destination terminal device using a first exit RLC channel corresponding to the destination terminal device determined by 302, the second data packet containing data transmitted by the source terminal device to the destination terminal device, and may further include an identifier (SRC ID) that can be mapped to the source terminal device.

[0054] In some embodiments, the identifiers that can be mapped to the source terminal device are the Layer 2 (L2) identifier (L2 ID) of the source terminal device; or the L2 identifier of the destination terminal device; or a pair of L2 identifiers of the source terminal device and the destination terminal device. For example, the L2 identifier of the source terminal device and / or the L2 identifier of the destination terminal device can be determined by the V2X layer of the terminal device according to a conventional method, and the length of the L2 identifier is 24 bits.

[0055] In some embodiments, the identifier that can be mapped to the source terminal device may further be a local identifier (local ID) of the source terminal device; a local identifier of the destination terminal device; a pair of local identifiers of the source terminal device and the destination terminal device; or a pair of local identifiers of the source terminal device and the destination terminal device. For example, the length of the local identifier of the source terminal device and the local identifier of the destination terminal device may be less than 24 bits, as in the embodiments described above, and a detailed explanation is omitted here. Therefore, overhead can be saved when a local identifier is used as an identifier that can be mapped to the destination terminal device. Note that the specific content and method of determining the local ID can be found in the prior art, and the present invention is not limited thereto.

[0056] In the embodiment described above, the RLC channel may also be referred to as an RLC bearer or an RLC entity.

[0057] As can be seen from the above embodiment, if a Layer 2 (L2) U2U relay supports multiplexing data from different destination terminal devices (UEs) onto the same RLC channel, and does not support multiplexing data from different destination UEs onto the same RLC channel, the relay UE can determine the corresponding exit RLC channel based on the exit RLC channel associated with the destination UE's radio bearer (RB), thereby transmitting the data transmission that the source UE sends to the destination UE to the corresponding destination UE via the determined exit RLC channel; and if a Layer 2 (L2) U2U relay supports multiplexing data from different destination UEs onto the same RLC channel, the MAC layer of the relay UE can distinguish between data from different destination UEs (multiplexed data), and therefore can select and transmit the data from the corresponding destination UE.

[0058] Figure 4 shows a data transmission and reception method in an embodiment of the present invention. As shown in Figure 4, the method is applied to a relay terminal device and includes steps 400, 401, 402 and 403, of which steps 401 to 403 are the same as those in steps 301 to 303 of Figure 3, and the explanation of the same content will be omitted here, with only the differences being described in detail. As shown in Figure 4, the method includes the following, namely, 400: Determine the ingress RLC channel that receives the first data packet that the source terminal device transmits to the destination terminal device, and the first data packet contains the data that the source terminal device transmits to the destination terminal device.

[0059] In some embodiments, 401 can receive the first data packet that the source terminal device transmits to the destination terminal device using the ingress RLC channel determined by 400.

[0060] In some embodiments, determining the ingress RLC channel to receive the first data packet at 400 includes determining the ingress RLC channel associated with the logical channel of the destination terminal device. For example, the ingress RLC channel associated with the logical channel of the destination terminal device can be determined, and in this way, the ingress RLC channel associated with the logical channel of the destination terminal device can be the ingress RLC channel to receive the first data packet. At 401, the first data packet is received by the determined ingress RLC channel. The relay terminal device can determine the ingress RLC channel associated with the logical channel of the destination terminal device based on association information (mapping relationship, for example, second configuration information) between the logical channel of the destination terminal device and the ingress RLC channel. For example, a relay terminal device determines the associated ingress RLC channel based on the logical channel of the destination terminal device. If one logical channel of a destination terminal device is associated with one ingress RLC channel and does not support multiplexing data from different destination terminal devices onto the same RLC channel, then one ingress RLC channel may be associated with one logical channel of a destination terminal device, and if it supports multiplexing data from different destination terminal devices onto the same RLC channel, then one ingress RLC channel may be associated with one or more logical channels of destination terminal devices.

[0061] In some embodiments, determining the ingress RLC channel associated with the logical channel of the destination terminal device involves determining the ingress RLC channel that receives the first data packet based on an identifier that can be mapped to the destination terminal device, a logical channel identifier, and second configuration information. For example, the identifier that can be mapped to the destination terminal device is the L2 identifier of the source terminal device and / or the L2 identifier of the destination terminal device, where the upper 16 bits of the L2 identifier of the source terminal device and the upper 8 bits of the L2 identifier of the destination terminal device are included in the header of the MAC PDU received by the relay terminal device. The lower 8 bits of the L2 identifier of the source terminal device and the lower 16 bits of the L2 identifier of the destination terminal device are included in the Sidelink Control Information (SCI) transmitted by the source terminal device. When the first data packet reaches the relay UE, the relay UE's PC5-PHY can determine a portion of the L2 indicators that can be mapped to the destination terminal device, for example, the lower 8 bits of the source terminal device's L2 indicator and the lower 16 bits of the destination terminal device's L2 indicator. The relay UE's PC5-MAC entity can then analyze the first data packet to obtain another portion of the indicators included in the data header of the first data packet that can be mapped to the destination terminal device, for example, the upper 16 bits of the source terminal device's L2 indicator and the upper 8 bits of the destination terminal device's L2 indicator, and then obtain the logical channel indicator.

[0062] The second configuration information includes, but is not limited to, the following: an inlet RLC channel associated with the logical channels of a source terminal device and / or destination terminal device, where one logical channel of a source terminal device and / or destination terminal device is associated with one inlet RLC channel, for example, the second configuration information includes an RLC channel identifier (RLC channel ID) associated with one logical channel identifier; or a logical channel of a source terminal device and / or destination terminal device associated with an inlet RLC channel, where one inlet RLC channel is associated with one or more logical channels of a source terminal device and / or destination terminal device, for example, the second configuration information includes one or more logical channel identifiers associated with one RLC channel ID.

[0063] In some embodiments, different logical channels of a pair of source terminal devices and destination terminal devices have different logical channel indicators, i.e., the indicator of the source terminal device, the indicator of the destination terminal device, and the logical channel indicator can each indicate one logical channel; or, in the source terminal device, different logical channels of the same or different destination terminal devices have different logical channel indicators, i.e., the indicator of the source terminal device and the logical channel indicator can each indicate one logical channel; or, in the destination terminal device, different logical channels of the same or different source terminal devices have different logical channel indicators, i.e., the indicator of the destination terminal device and the logical channel indicator can each indicate one logical channel, or the logical channel indicator can each indicate one logical channel.

[0064] For the distinction between a source terminal device identifier and an identifier that can be mapped to a source terminal device, and for the distinction between a destination terminal device identifier and an identifier that can be mapped to a destination terminal device, please refer to the previously described embodiment, and a detailed explanation will be omitted here.

[0065] The following explains, using an example, how to determine the entry RLC channel that receives the first data packet at 400.

[0066] For example, when the second configuration information includes an ingress RLC channel associated with the logical channel of the source terminal device, and the identifier that can be mapped to the destination terminal device is the L2 identifier of the source terminal device, the 400 determines the ingress RLC channel based on the L2 identifier of the source terminal device, the logical channel identifier, and the second configuration information. Specifically, the MAC entity of the relay terminal device determines the logical channel of the source terminal device based on the L2 identifier and the logical channel identifier of the source terminal device; and then, based on the logical channel of the source terminal device and the association information between the logical channel of the source terminal device and the ingress RLC channel in the second configuration information, it obtains the ingress RLC channel that receives the first data packet.

[0067] For example, when the second configuration information includes an ingress RLC channel associated with the logical channel of the source terminal device, and the identifier that can be mapped to the destination terminal device is the L2 identifier of the destination terminal device, 400 determines the ingress RLC channel based on the L2 identifier of the destination terminal device, the logical channel identifier, and the second configuration information. Specifically, the MAC entity of the relay terminal device determines the logical channel of the source terminal device based on the L2 identifier and the logical channel identifier of the destination terminal device; and then determines the ingress RLC channel that receives the first data packet based on the logical channel of the source terminal device and the association information between the logical channel of the source terminal device and the ingress RLC channel in the second configuration information.

[0068] For example, when the second configuration information includes an ingress RLC channel associated with the logical channel of the destination terminal device, and the identifier that can be mapped to the destination terminal device is the L2 identifier of the source terminal device, the 400 determines the ingress RLC channel based on the L2 identifier of the source terminal device, the logical channel identifier, and the second configuration information. Specifically, the MAC entity of the relay terminal device determines the logical channel of the destination terminal device based on the L2 identifier and the logical channel identifier of the source terminal device; and then, based on the logical channel of the destination terminal device and the association information between the logical channel of the destination terminal device and the ingress RLC channel in the second configuration information, it obtains the ingress RLC channel that receives the first data packet.

[0069] For example, when the second configuration information includes an ingress RLC channel associated with the logical channel of the destination terminal device, and the identifier that can be mapped to the destination terminal device is the L2 identifier of the destination terminal device, 400 determines the ingress RLC channel based on the L2 identifier of the destination terminal device, the logical channel identifier, and the second configuration information. Specifically, the MAC entity of the relay terminal device determines the logical channel of the destination terminal device based on the L2 identifier and the logical channel identifier of the destination terminal device; and then determines the ingress RLC channel that receives the first data packet based on the logical channel of the destination terminal device and the association information between the logical channel of the destination terminal device and the ingress RLC channel in the second configuration information.

[0070] The above lists methods for determining the inlet RLC channel when the second configuration information includes an inlet RLC channel associated with a logical channel of the source terminal device or the destination terminal device, and the identifier that can be mapped to the destination terminal device is the L2 identifier of the source terminal device or the L2 identifier of the destination terminal device. When the second configuration information includes an inlet RLC channel associated with logical channels of the source terminal device and the destination terminal device, and the identifier (DST ID) that can be mapped to the destination terminal device is a pair of L2 identifiers of the source terminal device and the L2 identifier of the destination terminal device, the 400 determines the inlet RLC channel based on the pair of L2 identifiers of the source terminal device and the L2 identifier of the destination terminal device, the logical channel identifier, and the second configuration information. Specifically, the MAC entity of the relay terminal device determines the logical channels of the source terminal device and the destination terminal device based on the L2 indicator of the source terminal device and the L2 indicator and logical channel indicator of the destination terminal device; and thereafter, it acquires the ingress RLC channel that receives the first data packet based on the logical channels of the source terminal device and the destination terminal device, and the association information between the logical channels of the source terminal device and the destination terminal device in the second configuration information and the ingress RLC channel.

[0071] The second configuration information may come from network equipment and / or source terminal equipment and / or from the pre-configuration of relay terminal equipment, and the present invention is not limited thereto. For example, the second configuration information may be transmitted to the relay terminal equipment by network equipment; and / or transmitted to the relay terminal equipment by source terminal equipment; and / or included in the pre-configuration information of the relay terminal equipment. In such cases, the method further includes (not shown) the acquisition of the second configuration information. The second configuration information may be obtained in the following manner, i.e., the relay terminal equipment receives the second configuration information transmitted by network equipment and / or source terminal equipment; and / or acquires the second configuration information from the pre-configuration information of the relay terminal equipment.

[0072] In this embodiment, the labels that can be mapped to the destination terminal device are as described above, and a detailed explanation of them is omitted here.

[0073] In this embodiment, determining the ingress RLC channel that receives the first data packet at 400 can be achieved by the MAC layer of the relay UE. For example, when the first data packet reaches the relay UE, the relay UE's PC5-PHY can determine a portion of the identifier that can be mapped to the destination terminal device, for example, the lower 8 bits of the source terminal device's L2 ID and the lower 16 bits of the destination terminal device. The relay UE's PC5-MAC entity analyzes the first data packet to obtain another portion of the identifier that can be mapped to the destination terminal device, contained in the data header of the first data packet, for example, the upper 16 bits of the source terminal device's L2 ID and the upper 8 bits of the destination terminal device. It also obtains the logical channel identifier. Since the second configuration information contains the ingress RLC channel associated with the logical channel of the destination terminal device, the relay UE's PC5-MAC entity can determine the ingress RLC channel that receives the first data packet based on the identifier that can be mapped to the destination terminal device, the logical channel identifier, and the second configuration information.

[0074] In some embodiments, determining the ingress RLC channel associated with the logical channel of the destination terminal device includes determining the ingress RLC channel that receives the first data packet based on an indicator that can be mapped to the destination terminal device and a logical channel indicator.

[0075] Eventually, the relay UE itself determines the ingress RLC channel associated with the logical channel of the destination terminal device. For example, when the first data packet of a logical channel from one source terminal device to one destination terminal device reaches the PC5-MAC entity of the relay terminal device, the PC5-MAC entity can determine that one ingress RLC channel is associated with the logical channel of the source terminal device and / or the destination terminal device. The relay UE can then receive the data that the source terminal device transmits to the destination terminal device via the determined ingress RLC channel associated with the logical channel of the source terminal device and / or the destination terminal device.

[0076] In this embodiment, the labels that can be mapped to the destination terminal device are as described above, and a detailed explanation of them is omitted here.

[0077] In this embodiment, determining the ingress RLC channel that receives the first data packet at 400 can be achieved by the MAC layer of the relay UE. For example, when the first data packet reaches the relay UE, the relay UE's PC5-PHY can determine a portion of the identifier that can be mapped to the destination terminal device, for example, the lower 8 bits of the source terminal device's L2 ID and the lower 16 bits of the destination terminal device. The relay UE's PC5-MAC entity analyzes the first data packet to obtain another portion of the identifier that can be mapped to the destination terminal device, included in the data header of the first data packet, for example, the upper 16 bits of the source terminal device's L2 ID and the upper 8 bits of the destination terminal device. It also obtains the logical channel identifier. The relay UE's PC5-MAC entity then determines that one ingress RLC channel is associated with the logical channel of the destination terminal device, and can receive the first data packet through the determined ingress RLC channel. The ingress RLC channel determined by the relay UE's PC5-MAC entity is, for example, an idle ingress RLC channel.

[0078] In some embodiments, the RLC channel may be referred to as an RLC bearer or an RLC entity. In the scenario shown in Figure 2, the RLC channel may be a PC5-RLC channel, or it may be a PC5-RLC bearer or a PC5-RLC entity.

[0079] In some embodiments, the exit RLC channel may be referred to as an exit RLC bearer or an exit RLC entity. In the scenario shown in Figure 2, the exit RLC channel may be an exit PC5-RLC channel, or it may be an exit PC5-RLC bearer or an exit PC5-RLC entity.

[0080] In some embodiments, the inlet RLC channel may be described as an inlet RLC bearer or an inlet RLC entity. In the scenario shown in Figure 2, the inlet RLC channel may be an inlet PC5-RLC channel, or it may be an inlet PC5-RLC bearer or an outlet PC5-RLC entity.

[0081] As can be seen from the above embodiments, in the embodiments of the present invention, the relay terminal equipment (relay UE) determines the exit RLC channel corresponding to the destination UE based on the exit RLC channel associated with the destination UE's radio bearer (RB), and transmits the data that the source UE sends to the destination UE to the corresponding destination UE via the determined exit RLC channel. Whether or not the Layer 2 (L2) U2U relay supports multiplexing data from different destination terminal equipment (UEs) onto the same RLC channel, the MAC layer of the relay UE can distinguish between data from different destination UEs (multiplexed data), and thus can select and transmit the data from the corresponding destination UE. Furthermore, when supporting multiplexing data from different destination terminal equipment (UEs) onto the same RLC channel, it is possible to save the number of RLC channels, reduce the demands on the terminal equipment's capabilities, and decrease the complexity of processing on the terminal equipment.

[0082] <Example of the second aspect> An embodiment of the present invention provides a data transmission method.

[0083] Figure 5 shows a data transmission method in an embodiment of the present invention. This method is applied to source terminal equipment and corresponds to cases where data multiplexing is supported. As shown in Figure 5, the method includes the following, namely, 501: Determine the second exit RLC channel corresponding to the destination terminal device, among which different destination terminal devices correspond to the same second exit RLC channel; and 502: A data packet is transmitted to a relay terminal device via a confirmed second exit RLC channel by a source terminal device, and the data packet contains data that the source terminal device transmits to the destination terminal device.

[0084] According to the above embodiment, when supporting the multiplexing of data from different destination terminal devices onto the same RLC channel, the source terminal device can conserve the number of RLC channels, reduce the demands on the UE's capabilities, and decrease the complexity of the UE's processing by sending data packets to different destination terminal devices, for example, at least two destination terminal devices, via the same exit RLC channel.

[0085] Figure 5 above is provided to illustrate an embodiment of the present invention, but the present invention is not limited thereto. For example, the execution order between each operation can be appropriately adjusted, or some operations can be appropriately increased or decreased. Those skilled in the art can make appropriate modifications based on the above description, not limited to the description in Figure 5.

[0086] In some embodiments, determining a second exit RLC channel corresponding to a destination terminal device in 501 includes determining a second exit RLC channel associated with the RB of the destination terminal device, such that the RBs of different destination terminal devices (e.g., at least two destination terminal devices) are associated with the same second exit RLC channel. This allows a source terminal device to determine a second exit RLC channel based on the second exit RLC channel associated with the RB of a destination terminal device when transmitting data to different destination terminal devices (at least two destination terminal devices) via the same exit RLC channel.

[0087] In some embodiments, different RBs of a pair of source terminal devices and destination terminal devices have different RB IDs, i.e., the source terminal device's label, the destination terminal device's label, and the RB ID can label one RB; or, in a source terminal device, different RBs of the same or different destination terminal devices have different RB IDs, i.e., the source terminal device's label and the RB ID can label one RB; or, in a destination terminal device, different RBs of the same or different source terminal devices have different RB IDs, i.e., the destination terminal device's label and the RB ID can label one RB, or the RB ID can label one RB.

[0088] In some embodiments, the second exit RLC channel can be determined based on the mapping relationship between the destination terminal device's RB and the exit RLC channel (e.g., second configuration information). For example, the second exit RLC channel associated with the destination terminal device's RB can be determined based on a mappable marker, a radio bearer marker, and third configuration information, the third configuration information may include the second exit RLC channel associated with the destination terminal device's RB, or the destination terminal's RB associated with the second exit RLC channel.

[0089] In some embodiments, the third configuration information may be obtained from a network device and / or from a relay terminal device and / or from the preconfiguration of the source terminal device. For example, the third configuration information is transmitted to the source terminal device by a network device; and / or transmitted to the source terminal device by a relay terminal device; and / or included in the preconfiguration of the source terminal device. In such cases, the method may further include (not shown) obtaining the third configuration information. The third configuration information can be obtained in the following manner: the source terminal device receives the third configuration information transmitted by the network device and / or the relay terminal device; and / or obtains the third configuration information from the preconfiguration information of the source terminal device.

[0090] In some embodiments, after the source terminal device has determined the identifiers and radio bearer identifiers that can be mapped to the destination terminal device, the method further includes including the identifiers and radio bearer identifiers that can be mapped to the destination terminal device in the header of a data packet to be transmitted to the destination terminal device, for example, an SRAP PDU, so that the data packet transmitted by the source terminal device to the terminal device in step 502 may further include the identifiers and radio bearer identifiers that can be mapped to the destination terminal device. This allows the relay terminal device to determine the first exit RLC channel associated with the RB of the destination terminal device based on the identifiers and radio bearer identifiers that can be mapped to the destination terminal device and the acquired first configuration information when it receives a data packet containing the identifiers and radio bearer identifiers that can be mapped to the destination terminal device.

[0091] In some embodiments, the labels that can be mapped to the destination terminal device are the same as in the embodiments described above, and this information is combined here, so a detailed explanation is omitted.

[0092] In this embodiment, the RLC channel may be described as an RLC bearer or an RLC entity. In the scenario shown in Figure 2, the RLC channel may be a PC5-RLC channel, or it may be a PC5-RLC bearer or a PC5-RLC entity.

[0093] In this embodiment, the exit RLC channel may also be referred to as an exit RLC bearer or an exit RLC entity. In the scenario shown in Figure 2, the exit RLC channel may be an exit PC5-RLC channel, or it may be an exit PC5-RLC bearer or an exit PC5-RLC entity.

[0094] In this embodiment, the inlet RLC channel may also be described as an inlet RLC bearer or an inlet RLC entity. In the scenario shown in Figure 2, the inlet RLC channel may be an inlet PC5-RLC channel, or it may be an inlet PC5-RLC bearer or an inlet PC5-RLC entity.

[0095] The embodiments described above are for illustrative purposes to illustrate embodiments of the present invention, but the present invention is not limited thereto, and appropriate modifications can be made based on the embodiments described above. For example, the embodiments described above may be used individually, or a combination of several of the embodiments described above may be used.

[0096] Although only the steps of the present invention have been described above, the present invention is not limited thereto. The data transmission method according to the present invention may further include other steps, and the specific details of these steps can be found in related technologies.

[0097] <Example of the third side> An embodiment of the present invention provides a data transmission method.

[0098] Figure 6 shows a data transmission method in an embodiment of the present invention. This method is applied to source terminal equipment and corresponds to cases where data multiplexing is not supported. As shown in Figure 6, the method includes the following, namely: 601: Determine the third exit RLC channel corresponding to the destination terminal device, of which different destination terminal devices correspond to different third exit RLC channels; and 602: The data packet that the source terminal device transmits to the destination terminal device is transmitted to the relay terminal device via the confirmed third exit RLC channel. Of these, the data packet includes data transmitted by the source terminal device to the destination terminal device and a radio bearer identifier, but does not include an identifier that can be mapped to the destination terminal device.

[0099] According to the above embodiment, each source terminal device transmits data packets to different destination terminal devices via different exit RLC channels and does not support multiplexing data from different destination terminal devices onto the same RLC channel. At the first hop, overhead can be saved because the data packets transmitted by the source terminal device to the destination terminal device do not need to have any indicators that can be mapped to the destination terminal device, or do not need to be reflected.

[0100] In other words, the data packet may include data transmitted by the source terminal device to the destination terminal device, a label that can be mapped to the destination terminal device, and a wireless bearer label, but the label that can be mapped to the destination terminal device may be omitted or not reflected.

[0101] Figure 6 above is provided to illustrate an embodiment of the present invention, but the present invention is not limited thereto. For example, the execution order between each operation can be appropriately adjusted, or some operations can be appropriately increased or decreased. Those skilled in the art can make appropriate modifications based on the above description, not limited to the description in Figure 6.

[0102] In this way, when omitting the identifier that can be mapped to the destination terminal device, the method may further include, namely, including the radio bearer identifier (without the identifier mapped to the destination terminal device) in the data header of the data packet to be sent to the destination terminal device, so that in step 602, the data packet sent by the source terminal device to the terminal device includes the radio bearer identifier but does not include the identifier mapped to the destination terminal device. This saves overhead when omitting the identifier mapped to the destination terminal device.

[0103] In some embodiments, determining a third exit RLC channel corresponding to a destination terminal device in 601 includes determining a third exit RLC channel associated with the RB of the destination terminal device, where different destination terminal devices' RBs are associated with different third exit RLC channels. This allows a source terminal device to determine a third exit RLC channel based on the third exit RLC channel associated with the RB of a destination terminal device when transmitting data to a different destination terminal device via a different exit RLC channel.

[0104] In one embodiment, the third exit RLC channel can be determined based on the mapping relationship between the destination terminal device's RB and the exit RLC channel (e.g., second configuration information). For example, the third exit RLC channel associated with the destination terminal device's RB can be determined based on a mappable marker, a radio bearer marker, and fourth configuration information, the fourth configuration information may include the third exit RLC channel associated with the destination terminal device's RB, or the destination terminal's RB associated with the third exit RLC channel.

[0105] In some embodiments, the fourth configuration information may be obtained from a network device and / or from a relay terminal device and / or from the preconfiguration of the source terminal device. For example, the fourth configuration information may be transmitted to the source terminal device by a network device; and / or transmitted to the source terminal device by a relay terminal device; and / or included in the preconfiguration of the source terminal device. In such cases, the method may further include (not shown) the acquisition of the fourth configuration information. The fourth configuration information may be acquired in the following manner: the source terminal device receives the fourth configuration information transmitted by the network device and / or the relay terminal device; and / or acquires the fourth configuration information from the preconfiguration of the source terminal device.

[0106] As a result, when a relay terminal device receives a data packet containing a marker, a radio bearer marker, and a logical channel marker mapped to a destination terminal device, it can determine the inlet RLC channel associated with the logical channel of the destination terminal device based on the marker, the logical channel marker mapped to the destination terminal device and the acquired second configuration information, and also determine the first outlet RLC channel associated with the RB of the destination terminal device based on the marker, the radio bearer marker mapped to the destination terminal device and the acquired first configuration information.

[0107] In some embodiments, the labels that can be mapped to the destination terminal device are the same as those in the embodiments described above, and their contents are combined here, so a detailed explanation is omitted here.

[0108] In this embodiment, the RLC channel may be described as an RLC bearer or an RLC entity. In the scenario shown in Figure 2, the RLC channel may be a PC5-RLC channel, or it may be a PC5-RLC bearer or a PC5-RLC entity.

[0109] In this embodiment, the exit RLC channel may also be referred to as an exit RLC bearer or an exit RLC entity. In the scenario shown in Figure 2, the exit RLC channel may be an exit PC5-RLC channel, or it may be an exit PC5-RLC bearer or an exit PC5-RLC entity.

[0110] The embodiments described above are for illustrative purposes to illustrate embodiments of the present invention, but the present invention is not limited thereto, and appropriate modifications can be made based on the embodiments described above. For example, the embodiments described above may be used individually, or a combination of several of the embodiments described above may be used.

[0111] Although only the steps of the present invention have been described above, the present invention is not limited thereto. The data transmission method according to the present invention may further include other steps, and the specific details of these steps can be found in related technologies.

[0112] <An example of the fourth side view.

[0113] An embodiment of the present invention provides a data reception method.

[0114] Figure 7 shows a data reception method in an embodiment of the present invention. The method is applied to a destination terminal device, and as shown in Figure 7, the method includes the following: 701: Determine the second entry RLC channel that receives the second data packet, the second data packet containing data that the source terminal device transmits to the destination terminal device; and 702: The second data packet is received via the confirmed second entry RLC channel.

[0115] According to the embodiment described above, the destination terminal device can receive data packets transmitted by the source terminal device based on a determined ingress RLC channel, and this applies both to devices that support and do not support multiplexing data from different destination terminal devices onto the same RLC channel.

[0116] In some embodiments, determining the ingress RLC channel that receives the second data packet at 701 includes determining the ingress RLC channel associated with the RB of the source terminal device. For example, the ingress RLC channel associated with the RB of the source terminal device may be determined.

[0117] In some embodiments, the inlet RLC channel associated with the RB of the source terminal device can be determined based on a marker that can be mapped to the source terminal device, a wireless bearer marker, and fifth configuration information.

[0118] In some embodiments, the second data packet may further include an identifier that can be mapped to a source terminal device and a radio bearer identifier. For example, the destination UE's PC5-PHY can determine a portion of the identifier that can be mapped to a source terminal device by Sidelink control information (SCI), such as the lower 8 bits of the source terminal device's L2 ID and the lower 16 bits of the destination terminal device's L2 ID. The destination UE's PC5-MAC entity can then analyze the second data packet to obtain another portion of the identifier that can be mapped to a source terminal device, such as the upper 16 bits of the source terminal device's L2 ID and the upper 8 bits of the destination terminal device's L2 ID, and also obtain a radio bearer identifier. Based on the identifier that can be mapped to a source terminal device, the radio bearer identifier, and the fifth configuration information, the destination UE's PC5-MAC entity can determine the inlet RLC channel associated with the source terminal device's RB.

[0119] In some embodiments, the fifth configuration information includes an inlet RLC channel associated with the RB of a source terminal device, or an inlet RLC channel associated with the RB of a source terminal device.

[0120] In some embodiments, the fifth configuration information may come from network equipment and / or relay terminal equipment and / or from the pre-configuration of the intermediate destination terminal equipment. For example, the fifth configuration information may be transmitted to the destination terminal equipment by network equipment; and / or transmitted to the destination terminal equipment by relay terminal equipment; and / or included in the pre-configuration of the destination terminal equipment. In such cases, the method may further include (not shown) the acquisition of the fifth configuration information. The fifth configuration information can be acquired in the following manner: the destination terminal equipment receives the fifth configuration information transmitted by network equipment and / or relay terminal equipment; and / or acquires the fifth configuration information from the pre-configuration information of the destination terminal equipment.

[0121] In some embodiments, the method for determining the markers and wireless bearer markers that can be mapped to the source terminal equipment, as well as the markers that can be mapped to the source terminal equipment, are the same as in the embodiments described above, and their contents are combined here, so a detailed explanation is omitted here.

[0122] In this embodiment, the inlet RLC channel may also be described as an inlet RLC bearer or an inlet RLC entity. In the scenario shown in Figure 2, the inlet RLC channel may be an inlet PC5-RLC channel, or it may be an inlet PC5-RLC bearer or an inlet PC5-RLC entity.

[0123] The embodiments described above are for illustrative purposes to illustrate embodiments of the present invention, but the present invention is not limited thereto, and appropriate modifications can be made based on the embodiments described above. For example, the embodiments described above may be used individually, or a combination of several of the embodiments described above may be used.

[0124] Although only the steps of the present invention have been described above, the present invention is not limited thereto. The data receiving method of the present invention may further include other steps, and the specific details of these steps can be found in related technologies.

[0125] <Example of the fifth side> This embodiment provides a data transmission and reception method. The explanation will be given using the scenario shown in Figure 2, along with an example of supporting data multiplexing. While this embodiment uses the example of multiplexing data from two different destination terminal devices, it is not limited to this. Similar methods can be used for transmitting and receiving data from three or more destination terminal devices, and a detailed explanation of this is omitted here.

[0126] Figure 8 shows a method for receiving and transmitting data in an embodiment of the present invention. Figure 9 shows a system protocol stack architecture in an embodiment of the present invention. As shown in Figures 8 and 9, the method includes the following, namely, 800: Determine the markers that the source UE can map to the destination UE, and the radio bearer markers.

[0127] 801: The source UE determines the corresponding exit RLC channel for the destination UE, and among these, different destination terminal devices correspond to the same exit RLC channel.

[0128] In this embodiment, when the source UE transmits data to at least two destination UEs, it determines the corresponding exit RLC channel for each destination UE. In this embodiment, the exit RLC channel may be an exit PC5-RLC channel, and the source UE transmits data for two or more destination UEs through a single exit PC5-RLC channel.

[0129] For example, a source UE can determine the exit RLC channel (e.g., egress PC5-RLC channel) corresponding to a destination UE based on a marker that can be mapped to the destination UE, a radio bearer marker, and third-party configuration information. For example, using destination UE1 and destination UE2 as examples, as shown in Figure 9, the source UE determines that the exit RLC channel is PC5-RLC based on a marker (DST1) and a radio bearer marker (RB1) that can be mapped to destination UE1, and the source UE determines that the exit RLC channel is PC5-RLC based on a marker (DST2) and a radio bearer marker (RB2) that can be mapped to destination UE2. In other words, destination UE1 and destination UE2 are mapped to the same exit RLC channel (e.g., PC5-RLC).

[0130] Of these, the identifiers and wireless bearer identifiers that can be mapped to the destination terminal device can be generated by 800, and the acquisition of the third configuration information is the same as in the embodiment described above, and its contents are combined here, so a detailed explanation is omitted here.

[0131] As shown in Figure 9, the source UE transmits data to destination UE1 and destination UE2. Of these, RB1 of destination UE1 corresponds to the source UE's PC5-PDCP entity PC5-PDCP1, and RB2 of destination UE2 corresponds to the source UE's PC5-PDCP entity PC5-PDCP2. The source UE's SRAP layer determines that PC5-PDCP1 and PC5-PDCP2 correspond to the same exit RLC channel. As a result, the data packet of RB1 of destination UE1 and the data packet of RB2 of destination UE2 are transmitted to the same exit RLC channel.

[0132] 802: Source UE transmits a first data packet to a relay terminal device via its determined exit RLC channel, the first data packet containing data that the source terminal device transmits to the destination terminal device.

[0133] The first data packet may include data transmitted by the source terminal device to the destination terminal device, an identifier that can be mapped to the destination terminal device, and a wireless bearer identifier. For example, let us explain using destination UE1 and destination UE2 as examples. As shown in Figure 9, corresponding to destination UE1, the first data packet includes data1 and may further include DST1 and RB1, and corresponding to destination UE2, the first data packet includes data2 and may further include DST2 and RB2.

[0134] 803: The relay UE receives the first data packet that the source terminal device transmits to the destination terminal device.

[0135] The relay UE's PC5-PHY receives Sidelink control information (SCI) transmitted by the source UE, and the relay UE's PC5-MAC layer receives the MAC PDU transmitted by the source UE and then analyzes the MAC PDU to obtain an identifier and logical channel identifier that can be mapped to the destination terminal device corresponding to the first data packet.

[0136] The PC5-MAC layer of the relay terminal device determines the ingress RLC channel associated with the logical channel of the destination terminal device based on the indicators and logical channel indicators included in the MAC PDU that can be mapped to the destination terminal device, as well as the second configuration information.

[0137] The RLC channel at the relay device's entry point transmits the first data packet from the destination terminal device to the SRAP receiving entity.

[0138] 804: The relay UE determines the exit RLC channel corresponding to the destination terminal device, and among them, the exit RLC channels corresponding to different destination terminals are different.

[0139] The relay terminal equipment then determines the exit RLC channel associated with the RB of the destination terminal equipment based on a marker that can be mapped to the destination terminal equipment, a radio bearer marker, and first configuration information.

[0140] For example, as shown in Figure 9, the SRAP transmission entity of the relay UE determines the exit RLC channel (PC5-RLC1) associated with the RB of destination UE1 based on a marker (DST1) that can be mapped to destination UE1, a radio bearer marker (RB1), and first configuration information, and the SRAP transmission entity of the relay UE determines the exit RLC channel (PC5-RLC2) associated with the RB of destination UE2 based on a marker (DST2) that can be mapped to destination UE2, a radio bearer marker (RB2), and first configuration information.

[0141] 805: The relay UE transmits a second data packet to the destination terminal device via the confirmed exit RLC channel, and the second data packet contains data that the source terminal device transmits to the destination terminal device.

[0142] In this embodiment, prior to 805, the method may further include the following (not shown): generating a second data packet to be transmitted to a different destination terminal device.

[0143] For example, as shown in Figure 9, the relay terminal device receives a first data packet from the source terminal device that the source terminal device transmits to destination UE1, and the data header of the first data packet includes a label (DST1) that can be mapped to destination terminal device 1. The relay terminal device changes the label (DST1) that can be mapped to destination terminal device 1 in the data header of the first data packet to a label (SRC1) that can be mapped to the source terminal device, and the relay terminal device receives a first data packet from the source terminal device that the source terminal device transmits to destination UE2, and the data header of the first data packet includes a label (DST2) that can be mapped to destination UE2. The relay terminal device changes the label (DST2) that can be mapped to destination UE2 in the data header of the first data packet to a label (SRC2) that can be mapped to the source terminal device. This generates the second data packet, and the second data packet may include data that the source terminal device transmits to the destination terminal device, as well as a label that can be mapped to the source terminal device and a wireless bearer label.

[0144] When the source terminal device that transmits the first data packet to destination terminal device 1 and destination terminal device 2 is the same, the identifier that can be mapped to the source terminal device (SRC1) and the identifier that can be mapped to the source terminal device (SRC2) are the same. When the source terminal devices that transmit the first data packet to destination terminal device 1 and destination terminal device 2 are different, the identifier that can be mapped to the source terminal device (SRC1) and the identifier that can be mapped to the source terminal device (SRC2) are different.

[0145] 806: The destination UE determines the entry RLC channel corresponding to the destination terminal device.

[0146] The destination UE then determines the exit RLC channel associated with the RB of the destination terminal device based on the marker, radio bearer marker, and fifth configuration information that can be mapped to the source terminal device.

[0147] For example, as shown in Figure 9, the operation of the MAC layers of destination UE1 and destination UE2 to receive data is the same as the operation of the MAC layer of the relay UE to receive data.

[0148] 807: The destination UE receives the second data packet via the confirmed entry RLC channel.

[0149] As can be seen from the embodiments described above, relaying from one UE to another can support multiplexing data from different destination terminal devices onto the same RLC channel. When multiplexing is supported, the source UE can transmit data to at least two different destination UEs via the same exit RLC channel, and the relay UE can receive data that the source UE is sending to different destination UEs via the same ingress channel, and transmit data that the source UE is sending to different destination UEs via different exit RLC channels. When multiplexing is supported, the present invention can conserve the number of RLC channels, reduce the demands on the capabilities of terminal devices, and decrease the complexity of processing for terminal devices, and the relay terminal device can distinguish between data that the source UE is sending to different destination UEs and transmit it via different exit RLC channels.

[0150] In this embodiment, the implementation of steps 800 to 802 and the interpretation of nouns are the same as those described in the embodiments of the second aspect of the present invention, and the relevant contents described above are combined here, and a detailed explanation is omitted.

[0151] The implementation of steps 803 to 805 and the interpretation of nouns are the same as those described in the embodiments of the first aspect of the present invention, and the relevant contents described above are hereby combined and their detailed explanation is omitted here.

[0152] The implementation of steps 806 to 807 and the interpretation of nouns are the same as those described in the embodiments of the fourth aspect of the present invention, and the relevant contents described above are combined here, and a detailed explanation is omitted here.

[0153] <Example of the sixth side view> This embodiment provides a data transmission and reception method. The explanation will be given using the scenario shown in Figure 2, along with an example where data multiplexing is not supported. While this embodiment explains the case where data from two different destination terminal devices is not multiplexed, this embodiment is not limited to this. A similar method can be used for transmitting and receiving data from three or more destination terminal devices, and a detailed explanation of this is omitted here.

[0154] Figure 10 shows a data reception and transmission method in an embodiment of the present invention. Figure 11 shows a system protocol stack architecture in an embodiment of the present invention. As shown in Figures 10 and 11, the method includes the following:

[0155] 1000: Determine the signs and radio bearer signs that the source UE can map to the destination UE.

[0156] 1001: The source UE determines the exit RLC channel corresponding to the destination terminal device, and different destination terminal devices correspond to different exit RLC channels.

[0157] When the source UE transmits data to at least two destination UEs, the exit RLC channel corresponding to the destination UE is determined. In this embodiment, the exit RLC channel may be an exit PC5-RLC channel, and the source UE transmits data to one destination UE via one exit PC5-RLC channel.

[0158] For example, a source UE can determine the exit RLC channel (e.g., egress PC5-RLC channel) corresponding to a destination UE based on a marker that can be mapped to the destination UE, a radio bearer marker, and fourth configuration information. For example, let's explain using destination UE1 and destination UE2 as examples. As shown in Figure 11, the source UE determines that the exit RLC channel is PC5-RLC1 based on a marker that can be mapped to destination UE1 (DST1) and a radio bearer marker (RB1), and the source UE determines that the exit RLC channel is PC5-RLC2 based on a marker that can be mapped to destination UE2 (DST2) and a radio bearer marker (RB2). In other words, destination UE1 and destination UE2 are mapped to different exit RLC channels.

[0159] Of these, the identifiers and wireless bearer identifiers that can be mapped to the destination terminal device can be generated by 800, and the acquisition of the third configuration information is the same as in the embodiment described above, and its contents are combined here, so a detailed explanation is omitted here.

[0160] As shown in Figure 11, the source UE transmits data to destination UE1 and destination UE2. Of these, RB1 of destination UE1 corresponds to the source UE's PC5-PDCP entity PC5-PDCP1, and RB2 of destination UE2 corresponds to the source UE's PC5-PDCP entity PC5-PDCP2. The source UE's SRAP layer determines that PC5-PDCP1 and PC5-PDCP2 correspond to different exit RLC channels. As a result, the data packet of RB1 of destination UE1 and the data packet of RB2 of destination UE2 are transmitted to different exit RLC channels.

[0161] 1002: Source UE transmits a first data packet to the relay terminal device via the confirmed exit RLC channel, and the first data packet includes data to be transmitted by the source terminal device to the destination terminal device.

[0162] The first data packet may include data transmitted by the source terminal device to the destination terminal device, an identifier that can be mapped to the destination terminal device, and a wireless bearer identifier. For example, destination UE1 and destination UE2 will be used as examples. As shown in Figure 11, corresponding to destination UE1, the first data packet includes data1 and may further include DST1 and RB1. Similarly, corresponding to destination UE2, the first data packet includes data2 and may further include DST2 and RB2.

[0163] 1003: The relay UE receives the first data packet that the source terminal device transmits to the destination terminal device.

[0164] The relay UE's PC5-PHY receives Sidelink control information (SCI) transmitted by the source UE, and the relay UE's PC5-MAC layer receives the MAC PDU transmitted by the source UE and then analyzes the MAC PDU to obtain an identifier and logical channel identifier that can be mapped to the destination terminal device corresponding to the first data packet.

[0165] The PC5-MAC layer of the relay terminal device determines the ingress RLC channel associated with the logical channel of the destination terminal device based on the indicator, logical channel indicator, and second configuration information included in the MAC PDU that can be mapped to the destination terminal device.

[0166] The RLC channel at the relay device's entry point transmits the first data packet from the destination terminal device to the SRAP receiving entity.

[0167] 1004: The relay UE determines the exit RLC channel corresponding to the destination terminal device, and among them, the exit RLC channels corresponding to different destination terminals are different.

[0168] The relay terminal equipment then determines the exit RLC channel associated with the RB of the destination terminal equipment based on a marker that can be mapped to the destination terminal equipment, a radio bearer marker, and first configuration information.

[0169] For example, as shown in Figure 11, the SRAP transmission entity of the relay UE determines the exit RLC channel (PC5-RLC1) associated with the RB of destination UE1 based on a marker (DST1) that can be mapped to destination UE1, a radio bearer marker (RB1), and first configuration information, and the SRAP transmission entity of the relay UE determines the exit RLC channel (PC5-RLC2) associated with the RB of destination UE2 based on a marker (DST2) that can be mapped to destination UE2, a radio bearer marker (RB2), and first configuration information.

[0170] 1005: The relay UE transmits a second data packet to the destination terminal device via the confirmed exit RLC channel, and the second data packet contains data that the source terminal device transmits to the destination terminal device.

[0171] In this embodiment, prior to step 1005, the method may further include the following (not shown): generating a second data packet to be transmitted to a different destination terminal device.

[0172] For example, as shown in Figure 11, the relay terminal device receives a first data packet from the source terminal device that the source terminal device transmits to destination UE1, and the data header of the first data packet includes a label (DST1) that can be mapped to destination terminal device 1. The relay terminal device changes the label (DST1) that can be mapped to destination UE1 in the data header of the first data packet to a label (SRC1) that can be mapped to the source terminal device, and the relay terminal device receives a first data packet from the source terminal device that the source terminal device transmits to destination UE2, and the data header of the first data packet includes a label (DST2) that can be mapped to destination UE2. The relay terminal device changes the label (DST2) that can be mapped to destination terminal device 2 in the data header of the first data packet to a label (SRC2) that can be mapped to the source terminal device. This generates the second data packet, which includes data that the source terminal device transmits to the destination terminal device, and may further include a label that can be mapped to the source terminal device and a wireless bearer label.

[0173] When the source terminal device that transmits the first data packet to destination terminal device 1 and destination terminal device 2 is the same, the identifier that can be mapped to the source terminal device (SRC1) and the identifier that can be mapped to the source terminal device (SRC2) are the same. When the source terminal devices that transmit the first data packet to destination terminal device 1 and destination terminal device 2 are different, the identifier that can be mapped to the source terminal device (SRC1) and the identifier that can be mapped to the source terminal device (SRC2) are different.

[0174] 1006: The destination UE determines the entry RLC channel corresponding to the destination terminal device.

[0175] The destination UE then determines the exit RLC channel associated with the RB of the destination terminal device based on the marker, radio bearer marker, and fifth configuration information that can be mapped to the source terminal device.

[0176] For example, as shown in Figure 11, the operation of the MAC layers of destination UE1 and destination UE2 to receive data is the same as the operation of the MAC layer of the relay UE to receive data.

[0177] 1007: The destination UE receives the second data packet via the confirmed entry RLC channel.

[0178] As can be seen from the above embodiment, relaying from one UE to another does not require support for multiplexing data from different destination terminal devices onto the same RLC channel. If multiplexing is not supported, the source UE can send data to different destination UEs via different exit RLC channels, and the relay UE can receive data sent by the source UE to different destination UEs via different ingress channels, and send data sent by the source UE to different destination UEs via different exit RLC channels. The relay terminal device can distinguish between data sent by the source UE to different destination UEs and transmit it via different exit RLC channels.

[0179] As can be seen from the above embodiment, relaying from one UE to another does not require support for multiplexing data from different destination terminal devices onto the same RLC channel. If multiplexing is not supported, the source UE can send data to at least two different destination UEs via different exit RLC channels, and the relay UE can receive data that the source UE sends to different destination UEs via different ingress channels, and send data that the source UE sends to different destination UEs via different exit RLC channels.

[0180] In this embodiment, the implementation of steps 1000 to 1002 and the interpretation of nouns are the same as those described in the embodiments of the third aspect of the present invention, and the relevant contents described above are combined here, and a detailed explanation is omitted here.

[0181] The implementation of steps 1003 to 1005 and the interpretation of nouns are the same as those described in the embodiments of the first aspect of the present invention, and the relevant contents described above are combined here, and a detailed explanation is omitted here.

[0182] The implementation of steps 1006 to 1007 and the interpretation of nouns are the same as those described in the embodiments of the fourth aspect of the present invention, and the relevant contents described above are combined here, and a detailed explanation is omitted here.

[0183] The embodiments described above are for illustrative purposes to illustrate embodiments of the present invention, but the present invention is not limited thereto, and appropriate modifications can be made based on the embodiments described above. For example, the embodiments described above may be used individually, or a combination of several of the embodiments described above may be used.

[0184] Although only the steps of the present invention have been described above, the present invention is not limited thereto. The data receiving method of the present invention may further include other steps, and the specific details of these steps can be found in related technologies.

[0185] <Example of the seventh side view> In embodiments of the present invention, a data transmission / reception device is provided, which is installed in a relay terminal device. This data transmission / reception device is based on the same inventive concept as the data transmission / reception method in the first embodiment provided in this application, and the principle of solving the problem is the same. Therefore, for the implementation of the data transmission / reception device, refer to the implementation of the data transmission / reception method in the first embodiment provided in this application, and redundant descriptions are omitted here. The terms “unit” or “module” used below can realize a combination of software and / or hardware with a predetermined function. The systems described in the following embodiments are preferably implemented by software, but implementation by hardware, or a combination of software and hardware, is also possible and provided.

[0186] As shown in Figure 12, the apparatus includes the following, namely, Receiving unit 1201: Used to receive a first data packet transmitted by a source terminal device to a destination terminal device, the first data packet containing data transmitted by the source terminal device to the destination terminal device; First confirmation unit 1202: Used to confirm the first exit RLC channel corresponding to the destination terminal equipment, of which the first exit RLC channels corresponding to different destination terminals are different; and Transmitting unit 1203: Used to transmit a second data packet to the destination terminal device via the confirmed first exit RLC channel, the second data packet containing the data.

[0187] In some embodiments, the first determination unit is used to determine a first exit RLC channel associated with the radio bearer (RB) of the destination terminal device, such that RBs of different destination terminal devices are associated with different first exit RLC channels.

[0188] In some embodiments, the first data packet further includes a label and a wireless bearer label that can be mapped to a destination terminal device.

[0189] The first determination unit is used to determine a first exit RLC channel associated with the RB of the destination terminal device, based on a marker that can be mapped to the destination terminal device, the radio bearer marker, and first configuration information.

[0190] In some embodiments, the first configuration information includes an exit RLC channel associated with the RB of the destination terminal device, or the RB of the destination terminal device associated with the exit RLC channel.

[0191] In some embodiments, the identifiers that can be mapped to the destination terminal device include the L2 identifier of the source terminal device; or the L2 identifier of the destination terminal device; or a pair of L2 identifiers of the source terminal device and the destination terminal device; or the local identifier of the source terminal device; or the local identifier of the destination terminal device; or a pair of local identifiers of the source terminal device and the destination terminal device; or a pair of local identifiers of the source terminal device and the destination terminal device.

[0192] In some embodiments, the first configuration information is obtained from network equipment and / or from source terminal equipment and / or from the pre-configuration of relay terminal equipment.

[0193] In some embodiments, the first data packet to be sent to the destination terminal device is transmitted by the source terminal device via the same second exit RLC channel.

[0194] In some embodiments, the first data packet to be sent to the destination terminal device is transmitted by the source terminal device via a different second exit RLC channel.

[0195] In some embodiments, as shown in Figure 13, the apparatus further includes a second determination unit 1200, which is used to determine the inlet RLC channel that receives the first data packet based on the L2 indicator of the source terminal equipment and / or the L2 indicator, logical channel indicator and second configuration information of the destination terminal equipment.

[0196] In some embodiments, the second configuration information includes an ingress RLC channel associated with the logical channels of the source terminal device and / or destination terminal device, or a logical channel of the source terminal device and / or destination terminal device associated with the ingress RLC channel.

[0197] In some embodiments, the second configuration information is obtained from network equipment and / or from source terminal equipment and / or from the pre-configuration of relay terminal equipment.

[0198] In some embodiments, the receiving unit is used to receive a first data packet that a source terminal device transmits to a destination terminal device via the established ingress RLC channel.

[0199] In some embodiments, the apparatus further includes a third determinative unit, which is used to determine the inlet RLC channel that receives the first data packet, based on the L2 indicator of the source terminal device and / or the L2 indicator of the destination terminal device, and the logical channel indicator.

[0200] In some embodiments, the second data packet further includes a label that can be mapped to the source terminal device.

[0201] In some embodiments, the labels that can be mapped to the source terminal device include the L2 label of the source terminal device; or the L2 label of the destination terminal device; or a pair of L2 labels of the source terminal device and the L2 label of the destination terminal device; or the local label of the source terminal device; or the local label of the destination terminal device; or a pair of local labels of the source terminal device and the destination terminal device; or a pair of local labels of the source terminal device and the destination terminal device.

[0202] Furthermore, for convenience, Figures 12 and 13 only show the connection relationships or signal directions between each component or module; however, various related technologies such as bus connections may be employed so as can be understood by those skilled in the art. The above-mentioned components or modules may be realized by hardware such as processors, memory devices, transmitters, and receivers, but the implementation of the present invention is not limited to these.

[0203] According to each of the embodiments described above, for data that a source terminal device transmits to different destination terminal devices, each relay terminal device transmits the data to the corresponding destination terminal device via a different exit RLC channel. In the UE-to-UE relay process, whether or not it supports multiplexing data from different destination terminal devices onto the same RLC channel, all relay terminal devices can transmit the data that the source terminal device transmits to different destination terminal devices to the corresponding destination terminal. In particular, when it supports multiplexing data from different destination terminal devices onto the same RLC channel, the method in the embodiments described above can save the number of PC5-RLC channels, reduce the demands on the UE's capabilities, and decrease the complexity of the UE's processing.

[0204] <Example of the eighth side view> In embodiments of the present invention, a data transmission device is provided, which is installed in a source terminal device. This data transmission device is based on the same inventive concept as the data transmission method in the second embodiment provided in this application, and the principle of solving the problem is the same. Therefore, for the implementation of the data transmission device, refer to the implementation of the data transmission method in the first embodiment provided in this application, and redundant descriptions are omitted here. The terms “unit” or “module” used below can realize a combination of software and / or hardware with a predetermined function. The systems described in the following embodiments are preferably implemented by software, but implementation by hardware, or a combination of software and hardware, is also possible and provided.

[0205] As shown in Figure 14, the apparatus includes the following, namely, Confirmation unit 1401: Used to confirm the second exit RLC channel corresponding to the destination terminal device, of which different destination terminal devices correspond to the same second exit RLC channel; and Transmitting unit 1402: Used to transmit data packets to a relay terminal device via the confirmed second exit RLC channel, the data packets containing data that the source terminal device transmits to the destination terminal device.

[0206] In some embodiments, the determination unit is used to determine a second exit RLC channel associated with the RB of the destination terminal device, such that at least two of the destination terminal device RBs are associated with the same second exit RLC channel.

[0207] In some embodiments, the determination unit is used to determine a second exit RLC channel corresponding to a destination terminal device based on third configuration information, the third configuration information includes a second exit RLC channel associated with the RB of the destination terminal device, or the RB of the destination terminal associated with the second exit RLC channel.

[0208] In some embodiments, the third configuration information is derived from network equipment and / or relay terminal equipment and / or from the pre-configuration of the source terminal equipment.

[0209] Furthermore, for convenience, Figure 14 only shows the connection relationships or signal directions between each component or module, but various related technologies such as bus connections may be employed so that those skilled in the art can understand them. The above-mentioned components or modules may be realized by hardware such as processors, memory devices, transmitters, and receivers, but the implementation of the present invention is not limited to these.

[0210] According to the above embodiment, the source terminal device can send data packets to different (at least two) destination terminal devices via the same exit RLC, and it is possible to multiplex data from different destination terminal devices onto the same RLC channel, thereby saving the number of PC5-RLC channels, reducing the demands on the UE's capabilities, and decreasing the complexity of the UE's processing.

[0211] <Example of the ninth side view> In embodiments of the present invention, a data transmission device is provided, which is installed in a source terminal device. This data transmission device is based on the same inventive concept as the data transmission method in the third embodiment provided in this application, and the principle of solving the problem is the same. Therefore, for the implementation of the data transmission device, refer to the implementation of the data transmission method in the first embodiment provided in this application, and redundant descriptions are omitted here. The terms “unit” or “module” used below can realize a combination of software and / or hardware with a predetermined function. The systems described in the following embodiments are preferably implemented by software, but implementation by hardware, or a combination of software and hardware, is also possible and provided.

[0212] As shown in Figure 15, the apparatus includes the following, namely, Confirmation unit 1501: Used to confirm the third exit RLC channel corresponding to the destination terminal device, of which different destination terminal devices correspond to different third exit RLC channels; and Transmitting unit 1502: Used to transmit data packets that the source terminal device transmits to the destination terminal device to the relay terminal device via the confirmed third exit RLC channel, Of these, the data packet includes data transmitted by the source terminal device to the destination terminal device, and a wireless bearer label, but does not include a label that can be mapped to the destination terminal device.

[0213] In some embodiments, the identifiers that can be mapped to the destination terminal device include: an L2 identifier of the source terminal device; or an L2 identifier of the destination terminal device; or a pair of source terminal device L2 identifiers and destination terminal device L2 identifiers; or a local identifier of the source terminal device; or a local identifier of the destination terminal device; or a pair of local identifiers of the source terminal device and destination terminal device; or a pair of local identifiers of the source terminal device and destination terminal device.

[0214] Furthermore, for convenience, Figure 15 only shows the connection relationships or signal directions between each component or module, but various related technologies such as bus connections may be employed so that those skilled in the art can understand them. The above-mentioned components or modules may be realized by hardware such as processors, memory devices, transmitters, and receivers, but the implementation of the present invention is not limited to these.

[0215] According to the embodiment described above, each source terminal device sends data packets to different destination terminal devices via a different exit RLC channel, and does not support multiplexing data from different destination terminal devices onto the same RLC channel. At the first hop, the data packets sent by the source terminal device to the destination terminal device do not need to contain any markers that can be mapped to the destination terminal device, thereby saving overhead.

[0216] <Example of the tenth side> In embodiments of the present invention, a data receiving device is provided, which is located in a destination terminal device. The data transmitting device is based on the same inventive concept as the data receiving method in the fourth embodiment provided in this application, and the principle of solving the problem is the same. Therefore, for the implementation of the data receiving device, refer to the implementation of the data receiving method in the first embodiment provided in this application, and redundant descriptions are omitted here. The terms “unit” or “module” used below can realize a combination of software and / or hardware with a predetermined function. The systems described in the following embodiments are preferably implemented by software, but can also be implemented by hardware, or a combination of software and hardware, and are provided.

[0217] As shown in Figure 16, the apparatus includes the following, namely, Confirmation unit 1601: Confirms the entry RLC channel on which the destination terminal device will receive the second data packet, and the second data packet contains data that the source terminal device will transmit to the destination terminal device; and Receiving unit 1602: Receives the second data packet via the confirmed second inlet RLC channel, In one embodiment, the second data packet includes data transmitted by the source terminal device to the destination terminal device and a wireless bearer identifier, but does not include an identifier that can be mapped to the destination terminal device, or the data packet does not include an identifier that can be mapped to the destination terminal device; or the data packet includes data transmitted by the source terminal device to the destination terminal device, an identifier that can be mapped to the destination terminal device and a wireless bearer identifier, but in another embodiment, the identifier that can be mapped to the destination terminal device is omitted.

[0218] In some embodiments, the second data packet further includes a label that can be mapped to a source terminal device.

[0219] In one embodiment, the labels that can be mapped to the source terminal device include the L2 label of the source terminal device; or the L2 label of the destination terminal device; or a pair of source terminal device L2 labels and destination terminal device L2 labels; or the local label of the source terminal device; or the local label of the destination terminal device; or a pair of local labels of the source terminal device and destination terminal device; or a pair of local labels of the source terminal device and destination terminal device.

[0220] In one embodiment, the determination unit is used to determine the inlet RLC channel associated with the RB of the destination terminal device.

[0221] In one embodiment, the second data packet further includes an identifier and a radio bearer identifier (Radio Bearer ID, RB ID) that can be mapped to a destination terminal device.

[0222] The confirmation unit is used to determine the inlet RLC channel associated with the RB of the destination terminal device, based on the marker that can be mapped to the destination terminal device, the radio bearer marker, and the fourth configuration information.

[0223] In one embodiment, the first configuration information includes an inlet RLC channel associated with the RB of the destination terminal device, or the RB of the destination terminal device associated with the inlet RLC channel.

[0224] For example, the fourth configuration information includes ingress RLC channels associated with the RBs of different destination terminal devices, and the RB of one destination terminal device is associated with one ingress RLC channel; or The fourth configuration information includes the RB of the destination terminal device associated with the inlet RLC channel, and one inlet RLC channel is associated with one destination terminal device's RB.

[0225] In one embodiment, the fourth configuration information is obtained from network equipment and / or from source terminal equipment and / or from the pre-configuration of relay terminal equipment.

[0226] In some embodiments, the inlet RLC channel associated with the RB of the destination terminal device is determined based on a label that can be mapped to the destination terminal device and the radio bearer label.

[0227] Although only the components or modules of the present invention have been described above, the present invention is not limited to these. The data transmission and reception device may further include other components or modules, and the specific details of these components or modules can be found in the relevant technologies. Figure 16 shows only the connection relationships or signal directions between the components or modules, but various related technologies such as bus connections may be employed so that those skilled in the art can understand them. The above-mentioned components or modules may be realized by hardware such as processors, memory devices, transmitters, and receivers, but the implementation of the present invention is not limited to these.

[0228] The embodiments described above are for illustrative purposes to illustrate embodiments of the present invention, but the present invention is not limited thereto, and appropriate modifications can be made based on the embodiments described above. For example, the embodiments described above may be used individually, or a combination of several of the embodiments described above may be used.

[0229] <Example of the eleventh side> An embodiment of the present invention provides a communication system, which can be seen in Figure 2, and which includes a source terminal device 201, a relay terminal device 203, and a destination terminal device 202.

[0230] In embodiments of the present invention, the source terminal device 201 is configured to perform the data transmission method in the second and / or third aspects of the present invention, the details of which are hereby combined and a detailed description thereof is omitted here.

[0231] In embodiments of the present invention, the relay terminal device 203 is configured to perform the data transmission and reception method in the first aspect of the present invention, and its details are summarized herein and omitted here.

[0232] In embodiments of the present invention, the destination terminal device 202 is configured to perform the data reception method according to the fourth aspect of the present invention, the details of which are summarized herein and are omitted here.

[0233] <Example of the twelfth side> An embodiment of the present invention provides a terminal device.

[0234] Figure 17 is a diagram showing the configuration of a terminal device in an embodiment of the present invention. The terminal device may be a remote terminal device. As shown in Figure 17, the terminal device 1700 may include a processor 1701 and a memory unit 1702, the memory unit 1702 storing data and programs and connected to the processor 1701. Note that this figure is merely illustrative, and telecommunications functions or other functions may be realized by supplementing or substituting this configuration with other types of configurations.

[0235] For example, the processor 1701 may be configured to execute a program to implement the data transmission and reception method described in the embodiment of the first aspect. For example, the processor 1701 may be configured to perform the following operations: receive a first data packet transmitted by a source terminal device to a destination terminal device, the first data packet containing data transmitted by the source terminal device to the destination terminal device; determine a first exit RLC channel corresponding to the destination terminal device, of which different first exit RLC channels correspond to different destination terminals; and transmit a second data packet to the destination terminal device via the determined first exit RLC channel, the second data packet containing the data.

[0236] Furthermore, for example, the processor 1701 may be configured to execute a program to implement the data transmission method described in the embodiment of the second aspect. For example, the processor 1701 may be configured to perform the following operations: namely, determining a second exit RLC channel corresponding to a destination terminal device, where different destination terminal devices correspond to the same second exit RLC channel; and transmitting data packets to a relay terminal device via the determined second exit RLC channel, where the source terminal device transmits data to different destination terminal devices, the data packets containing data that the source terminal device transmits to the destination terminal device.

[0237] Furthermore, for example, the processor 1701 may be configured to execute a program to implement the data transmission method described in the embodiment of the third side. For example, the processor 1701 may be configured to perform the following operations: determine a third exit RLC channel corresponding to a destination terminal device, where different destination terminal devices correspond to different third exit RLC channels; and transmit a data packet that the source terminal device transmits to the destination terminal device to a relay terminal device via the determined third exit RLC channel, wherein the data packet includes data that the source terminal device transmits to the destination terminal device and a wireless bearer indicator, but does not include an indicator that can be mapped to a destination terminal device.

[0238] Furthermore, for example, the processor 1701 may be configured to execute a program to implement the data reception method described in the fourth embodiment. For example, the processor 1701 may be configured to perform the following operations: namely, to determine a second inlet RLC channel for receiving a second data packet, the second data packet containing data to be transmitted by a source terminal device to a destination terminal device; and to receive the second data packet through the determined second inlet RLC channel.

[0239] As shown in Figure 17, the terminal device 1700 may further include a communication module 1703, an input unit 1704, a display unit 1705, a power source 1706, and the like. The functions of the above-mentioned components are the same as in the prior art, and a detailed explanation of them is omitted here. Note that the terminal device 1700 does not need to include all the components shown in Figure 17, and the above-mentioned components are not mandatory. Furthermore, the terminal device 1700 may also include components not shown in Figure 17, for which related technologies can be consulted.

[0240] In embodiments of the present invention, a computer-readable program is further provided, and in which, when the program is executed on a relay terminal device, the program causes the computer to execute the data transmission and reception method described in the embodiment of the first aspect of the present invention on the relay terminal device.

[0241] In embodiments of the present invention, a storage medium storing a computer-readable program is further provided, wherein the computer-readable program causes a computer to execute the data transmission and reception method described in the first aspect embodiment of the present invention using a relay terminal device.

[0242] In embodiments of the present invention, a computer-readable program is further provided, in which, when the program is executed on a source terminal device, the program causes the computer to execute the data transmission method described in the second embodiment of the present invention and / or the data transmission method described in the third embodiment of the present invention on the source terminal device.

[0243] In embodiments of the present invention, a storage medium storing a computer-readable program is further provided, wherein the computer-readable program causes a computer to execute the data transmission method described in the second aspect embodiment and / or the data transmission method described in the third aspect embodiment of the present invention on a source terminal device.

[0244] In embodiments of the present invention, a computer-readable program is further provided, in which, when the program is executed on a source terminal device, the program causes the computer to execute the data reception method described in the third embodiment of the present invention on the source terminal device.

[0245] In embodiments of the present invention, a storage medium storing a computer-readable program is further provided, wherein the computer-readable program causes a computer to execute the data transmission and reception method described in the third embodiment of the present invention on a source terminal device.

[0246] Furthermore, the above-described apparatus and method may be implemented by software or hardware, or by a combination of hardware and software. The present invention further relates to a computer-readable program as described below, that is, the program, when executed by a logic component, causes the logic component to implement the above-described apparatus or component, or to the logic component to implement each of the above-described method or step. The logic component may be, for example, an FPGA (Field Programmable Gate Array), a microprocessor, or a processor used in a computer. The present invention further relates to a storage medium storing the above-described program, for example, a hard disk, a magnetic disk, an optical hard disk, a DVD, a flash memory, etc.

[0247] Furthermore, one or more combinations of the functional blocks shown in the drawings and / or one or more combinations of functional blocks may be implemented as a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic component, discrete gate or transistor logic component, discrete hardware assembly or any other suitable combination for performing the functions described herein. Also, one or more combinations of the functional blocks shown in the drawings and / or one or more combinations of functional blocks may further be configured as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors connected to a DSP by communication or any other combination of any other configuration.

[0248] Although preferred embodiments of the present invention have been described above, the present invention is not limited to such embodiments, and any modifications to the present invention that do not deviate from the spirit of the invention fall within the technical scope of the present invention.

[0249] Furthermore, the following additional information is disclosed regarding the above-mentioned embodiments.

[0250] <Data transmission and reception method on the relay terminal side> (Note 1) A data transmission and reception method, applicable to relay terminal equipment, which is The source terminal device receives a first data packet that the destination terminal device transmits, and the first data packet includes data that the source terminal device transmits to the destination terminal device; Determine the first exit RLC channel corresponding to the destination terminal device, and among them, the first exit RLC channels corresponding to different destination terminals will be different; and A method comprising transmitting a second data packet to the destination terminal device via the confirmed first exit RLC channel, wherein the second data packet contains the data.

[0251] (Note 2) The method described in Appendix 1, Determining the first exit RLC channel corresponding to the destination terminal device includes determining the first exit RLC channel associated with the radio bearer (RB) of the destination terminal device, wherein RBs of different destination terminal devices are associated with different first exit RLC channels.

[0252] (Note 3) The method described in Appendix 2, The first data packet further includes a label that can be mapped to a destination terminal device, and a radio bearer label; and / or Determining the first exit RLC channel associated with the RB of the destination terminal device is: The method includes determining a first exit RLC channel associated with the RB of the destination terminal device based on a label that can be mapped to the destination terminal device and the radio bearer label.

[0253] (Note 4) The method described in Appendix 2, The first data packet further includes a label that can be mapped to a destination terminal device and a radio bearer label; and / or Determining the first exit RLC channel associated with the RB of the destination terminal device is: This includes determining a first exit RLC channel associated with the RB of the destination terminal device based on a label that can be mapped to the destination terminal device, the wireless bearer label, and first configuration information. The aforementioned first configuration information includes an exit RLC channel associated with the RB of the destination terminal device, or the RB of the destination terminal device associated with the exit RLC channel.

[0254] (Note 5) The method described in Appendix 3, The identifiers that can be mapped to the destination terminal device include: the L2 identifier of the source terminal device; or the L2 identifier of the destination terminal device; or the L2 identifiers of a pair of source terminal devices and the L2 identifier of the destination terminal device; or the local identifier of the source terminal device; or the local identifier of the destination terminal device; or the local identifier pair of the source terminal device and the destination terminal device; or the pair of local identifiers of the source terminal device and the destination terminal device.

[0255] (Appendix 6) The method described in Appendix 4, where the first setting information is from a network device, and / or from a source terminal device, and / or from the pre-setting of a relay terminal device.

[0256] (Appendix 7) The method described in Appendix 1, where the first data packet to be transmitted to the destination terminal device is transmitted by the source terminal device through the same second egress RLC channel.

[0257] (Appendix 8) The method described in Appendix 1, where the first data packet to be transmitted to the destination terminal device is transmitted by the source terminal device through different second egress RLC channels.

[0258] (Appendix 9a) The method described in Appendix 1, and further including determining the ingress RLC channel for receiving the first data packet.

[0259] (Appendix 9b) The method described in Appendix 9a, where determining the ingress RLC channel for receiving the first data packet includes determining the ingress RLC channel associated with the logical channel of the destination terminal device.

[0260] (Appendix 9) The method described in Appendix 9b, Determining the ingress RLC channel associated with the logical channel of the destination terminal device is: This includes determining the inlet RLC channel for receiving the first data packet based on an indicator that can be mapped to the destination terminal device, a logical channel indicator, and second configuration information.

[0261] (Note 10) The method described in Appendix 9, The second configuration information includes an ingress RLC channel associated with the logical channel of the destination terminal device, or a logical channel of the destination terminal device associated with the ingress RLC channel.

[0262] (Note 10a) The method described in Appendix 9, The labels that can be mapped to the aforementioned destination terminal device are: An L2 indicator of a source terminal device; or an L2 indicator of a destination terminal device; or a pair of L2 indicators of a source terminal device and an L2 indicator of a destination terminal device; or a local indicator of a source terminal device; or a local indicator of a destination terminal device; or a pair of local indicators of a source terminal device and a destination terminal device; or including a pair of local indicators of a source terminal device and a destination terminal device.

[0263] (Note 11) The method described in Appendix 9, The aforementioned second configuration information is derived from network equipment and / or source terminal equipment and / or from the pre-configuration of relay terminal equipment.

[0264] (Note 12) The method described in Appendix 9a, The source terminal device receiving the first data packet that the destination terminal device transmits means that The configuration includes receiving a first data packet that the source terminal device transmits to the destination terminal device via the confirmed entry RLC channel.

[0265] (Note 13) The method described in Appendix 9a, further, Determining an ingress RLC channel for receiving the first data packet based on a label that can be mapped to a destination terminal device and a logical channel label.

[0266] (Appendix 13a) The method according to Appendix 13, wherein The label that can be mapped to the destination terminal device is The L2 label of the source terminal device; or the L2 label of the destination terminal device; or the L2 labels of a pair of source terminal devices and the L2 label of the destination terminal device; or the local label of the source terminal device; or the local label of the destination terminal device; or a pair of local labels of the source terminal device and the destination terminal device; or a pair of local labels of the source terminal device and the destination terminal device.

[0267] (Appendix 14) The method according to Appendix 1, wherein The second data packet further includes a label that can be mapped to the source terminal device.

[0268] (Appendix 15) The method according to Appendix 14, wherein The label that can be mapped to the source terminal device is the L2 label of the source terminal device; or the L2 label of the destination terminal device; or the L2 labels of a pair of source terminal devices and the L2 label of the destination terminal device; or the local label of the source terminal device; or the local label of the destination terminal device; or a pair of local labels of the source terminal device and the destination terminal device; or a pair of local labels of the source terminal device and the destination terminal device.

[0269] <Data transmission method on the source terminal device side> (First part) (Appendix 16) A data transmission method applied to a source terminal device, which Determines a second egress RLC channel corresponding to a destination terminal device, wherein different said destination terminal devices correspond to the same second egress RLC channel; and The data packet includes data that the source terminal device transmits to a different destination terminal device via the confirmed second exit RLC channel, wherein the data packet includes data that the source terminal device transmits to the destination terminal device.

[0270] (Note 17) The method described in Appendix 16, Determining a second exit RLC channel corresponding to the destination terminal device includes determining a second exit RLC channel associated with the RB of the destination terminal device, such that at least two of the RBs of the destination terminal device are associated with the same second exit RLC channel.

[0271] (Note 18) The method described in Appendix 17, Determining the second exit RLC channel associated with the RB of the destination terminal device is: This includes determining a second exit RLC channel corresponding to a destination terminal device based on third configuration information, wherein the third configuration information includes a second exit RLC channel associated with the RB of the destination terminal device, or the RB of the destination terminal associated with the second exit RLC channel.

[0272] (Note 19) The method described in Appendix 18, The aforementioned third configuration information is derived from network equipment and / or relay terminal equipment and / or from the pre-configuration of the source terminal equipment.

[0273] (Second part) (Note 20) A data transmission method, applicable to source terminal equipment, is, Determine the third exit RLC channel corresponding to the destination terminal device, and different destination terminal devices will correspond to different third exit RLC channels; and This includes transmitting data packets that the source terminal device intends to send to the destination terminal device to the relay terminal device via the confirmed third exit RLC channel, Among these, the data packet includes data transmitted by the source terminal device to the destination terminal device, and a wireless bearer label, but does not include a label that can be mapped to the destination terminal device.

[0274] (Note 21) The method described in Appendix 20, The labels that can be mapped to the destination terminal device include: the L2 label of the source terminal device; or the L2 label of the destination terminal device; or a pair of source terminal device L2 labels and destination terminal device L2 labels; or a local label of the source terminal device; or a local label of the destination terminal device; or a pair of local labels of the source terminal device and destination terminal device; or a pair of local labels of the source terminal device and destination terminal device.

[0275] <Relay terminal equipment> (Note 22) Terminal device, Including memory and processing units, The aforementioned memory device stores computer programs, The processor is configured to execute the computer program and implement the data transmission and reception method described in any one of the appendices 1 to 15.

[0276] <Source terminal equipment> (Note 23) Terminal device, Including memory and processing units, The aforementioned memory device stores computer programs, The processor is configured to execute the computer program and implement the data transmission method described in any one of the appendices 16 to 21. Communication system (Note 24) It is a communication system, Source terminal equipment configured to perform the method described in any one of the appendices 16 to 21; A relay terminal device configured to perform the method described in any one of the appendices 1 to 15; and A device including a destination terminal device configured to receive data packets transmitted by the relay terminal device.

Claims

1. A data transmission and reception device, configured as a relay terminal device, the device is A receiving unit that receives a first data packet transmitted by a source terminal device to a destination terminal device, wherein the first data packet includes data transmitted by the source terminal device to the destination terminal device; A first determination unit for determining a first exit RLC channel corresponding to the destination terminal equipment, wherein the first exit RLC channels corresponding to different destination terminals are different; and A transmission unit that transmits a second data packet to a destination terminal device via the confirmed first exit RLC channel, wherein the second data packet includes the data.

2. The apparatus according to claim 1, The first confirmation unit confirms the first exit RLC channel corresponding to the destination terminal device, This includes determining the first exit RLC channel associated with the wireless bearer (RB) of the destination terminal device, The RBs of different destination terminal devices are associated with different first exit RLC channels in the device.

3. The apparatus according to claim 2, The first data packet further includes a label that can be mapped to a destination terminal device and a radio bearer label; and / or The first confirmation unit confirms the first exit RLC channel associated with the wireless bearer (RB) of the destination terminal device, A device that includes determining a first exit RLC channel associated with the RB of the destination terminal device based on a marker that can be mapped to the destination terminal device and the wireless bearer marker.

4. The apparatus according to claim 2, The first data packet further includes a label that can be mapped to a destination terminal device and a radio bearer label; and / or Determining the first exit RLC channel associated with the RB of the destination terminal device is: This includes determining a first exit RLC channel associated with the RB of the destination terminal device based on a marker that can be mapped to the destination terminal device, the wireless bearer marker, and first configuration information. The first configuration information includes an exit RLC channel associated with the RB of a destination terminal device, or an RB of a destination terminal device associated with an exit RLC channel.

5. The apparatus according to claim 3, The device includes, for example, an L2 indicator of a source terminal device, or an L2 indicator of a destination terminal device, or a pair of L2 indicators of a source terminal device and an L2 indicator of a destination terminal device, or a local indicator of a source terminal device, or a local indicator of a destination terminal device, or a pair of local indicators of a source terminal device and a destination terminal device, or a pair of local indicators of a source terminal device and a destination terminal device.

6. The apparatus according to claim 4, The device wherein the aforementioned first configuration information is derived from network equipment and / or from source terminal equipment and / or from the pre-configuration of relay terminal equipment.

7. The apparatus according to claim 1, The first data packet, which the receiving unit receives and which the source terminal device transmits to the destination terminal device, is transmitted by the source terminal device through the same second exit RLC channel.

8. The apparatus according to claim 1, The first data packet, which the receiving unit receives and which the source terminal device transmits to the destination terminal device, is transmitted by the source terminal device via a different second exit RLC channel.

9. The apparatus according to claim 1, The apparatus further includes a second confirmation unit, which is used to perform the following: A device that determines the inlet RLC channel for receiving the first data packet based on the L2 indicator of the source terminal device and / or the L2 indicator, logical channel indicator, and second configuration information of the destination terminal device.

10. The apparatus according to claim 9, The device includes an inlet RLC channel associated with the logical channels of the source terminal device and / or destination terminal device, or a logical channel of the source terminal device and / or destination terminal device associated with the inlet RLC channel.

11. The apparatus according to claim 9, The device wherein the aforementioned second configuration information is derived from network equipment and / or source terminal equipment and / or from the pre-configuration of relay terminal equipment.

12. The apparatus according to claim 9, The receiving unit receives the first data packet that the source terminal device transmits to the destination terminal device. An apparatus that includes receiving a first data packet transmitted by a source terminal device to a destination terminal device via the confirmed ingress RLC channel.

13. The apparatus according to claim 1, The apparatus further includes a third determination unit, which is used to perform the following: A device that determines the inlet RLC channel for receiving the first data packet based on the L2 indicator of the source terminal device and / or the L2 indicator and logical channel indicator of the destination terminal device.

14. The apparatus according to claim 1, The device further includes a second data packet that can be mapped to the source terminal device (SRC ID).

15. The apparatus according to claim 14, The device includes, for example, an L2 indicator of the source terminal device, or an L2 indicator of the destination terminal device, or a pair of L2 indicators of the source terminal device and the destination terminal device, or a local indicator of the source terminal device, or a local indicator of the destination terminal device, or a pair of local indicators of the source terminal device and the destination terminal device, or a pair of local indicators of the source terminal device and the destination terminal device.

16. A data transmission device, which is placed on a source terminal device, A determination unit for determining a second exit RLC channel corresponding to a destination terminal device, wherein different destination terminal devices correspond to the same second exit RLC channel; and A transmission unit that transmits data packets to a relay terminal device via a confirmed second exit RLC channel, wherein the source terminal device transmits data to a different destination terminal device, the data packets include data that the source terminal device transmits to the destination terminal device.

17. The apparatus according to claim 16, The determination unit determines the second exit RLC channel corresponding to the destination terminal device, This includes determining the second exit RLC channel associated with the RB of the destination terminal device, The RBs of at least two of the destination terminal devices are associated with the same second exit RLC channel in the device.

18. The apparatus according to claim 17, The confirmation unit confirms the second exit RLC channel associated with the RB of the destination terminal device, This includes determining the second exit RLC channel corresponding to the destination terminal device based on the third configuration information, The device includes a second exit RLC channel associated with the RB of a destination terminal device, or the RB of a destination terminal associated with the second exit RLC channel.

19. The apparatus according to claim 18, The device wherein the aforementioned third configuration information is derived from network equipment and / or relay terminal equipment and / or from the pre-configuration of the source terminal equipment.

20. A data transmission device, which is placed on a source terminal device, A determination unit for determining a third exit RLC channel corresponding to a destination terminal device, wherein different destination terminal devices correspond to different third exit RLC channels; and Includes a transmission unit that transmits data packets that the source terminal device transmits to the destination terminal device to the relay terminal device via the confirmed third exit RLC channel, The device wherein the data packet includes data transmitted by the source terminal device to the destination terminal device, and a wireless bearer label, but does not include a label that can be mapped to the destination terminal device.

Images