Data transmission method and system, remote and relay user terminals, base station

By generating and sending radio link control status reports through relay user terminals, the problem of data loss caused by the lack of consideration for multi-hop links in the NR PDCP design is solved, and lossless data transmission and service continuity of remote UEs are achieved.

CN119210660BActive Publication Date: 2026-06-26CHINA TELECOM CORP LTD

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
CHINA TELECOM CORP LTD
Filing Date
2023-06-25
Publication Date
2026-06-26

AI Technical Summary

Technical Problem

In relay access scenarios, the NR PDCP design did not consider multi-hop links, resulting in data loss at the remote UE, especially during path handover, where lossless data transmission cannot be guaranteed.

Method used

By generating and sending a radio link control status report through the relay user terminal, indicating unsuccessfully transmitted data packets, the report assists the remote user terminal and the base station in retransmitting data packets, thereby ensuring the integrity of data transmission.

Benefits of technology

It enables lossless data transmission to remote UEs during path switching, ensuring the continuity of user services and avoiding data loss.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119210660B_ABST
    Figure CN119210660B_ABST
Patent Text Reader

Abstract

The present disclosure relates to a data transmission method and system, a remote user terminal and a relay user terminal, and a base station. The data transmission method comprises: generating first identification information in the case of receiving indication information sent by a remote user terminal or satisfying a pre-configured trigger condition, wherein the first identification information indicates data in uplink data of the remote user terminal which is successfully received by a relay user terminal and has not been confirmed by a base station, the uplink being a communication path from the remote user terminal to the base station; and sending the first identification information to the remote user terminal so that the remote user terminal determines data which is not successfully transmitted to the base station according to the first identification information and re-sends the data which is not successfully transmitted to the base station. The present disclosure ensures that data transmission of the remote UE is not lost.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to the field of wireless communication, and in particular to a data transmission method and system, remote and relay user terminals, and base stations. Background Technology

[0002] With the development of wireless multimedia services, people's demand for high data rates and user experience is increasing, which also places higher demands on the system capacity and coverage of wireless networks. In addition to communicating directly with target nodes (such as base stations or other terminal devices), mobile terminals can also achieve data transmission with target nodes through relay devices based on SL (Sidelink), thereby supporting a wider range of applications and services, expanding high-frequency coverage, and improving power consumption.

[0003] PDCP (Packet Data Convergence Protocol) status reports can be used in AM (Acknowledged Mode) and DRB (Data Resource Block). The PDCP status report includes FMC (First Missing Count) and a bitmap, used to inform the network-side user equipment which data was correctly received and which data was lost.

[0004] In Radio Link Control (RLC) AM, a device can send data as a sequence of Protocol Data Units (PDUs), some of which may not have been successfully transmitted, to a receiving device. As part of the error control process employed by AM, the receiving device can send an RLC status report to the transmitting device. The RLC status report may include indications of which PDUs were successfully received (ACK) and which PDUs failed to be received (NACK). Summary of the Invention

[0005] The inventors discovered through research that NR (New Radio) PDCP only considers single-hop links in its design. In relay access scenarios, due to hop-by-hop RLC ARQ (Automatic Repeat Request), the reception status of the relay UE (User Equipment) does not actually reflect the reception status of the remote UE or base station. Data packets acknowledged by the relay UE at PC5 RLC but not actually reaching the base station (Uu RLC acknowledgment) will not be retransmitted to the target base station, resulting in UL (Uplink) data loss. Here, PC5 is the direct communication interface, i.e., the direct communication interface between terminals, and Uu is the cellular network communication interface, i.e., the communication interface between the terminal and the base station.

[0006] In view of at least one of the above technical problems, this disclosure provides a data transmission method and system, a remote and relay user terminal, and a base station to ensure that data transmission of the remote UE is not lost.

[0007] According to one aspect of this disclosure, a data transmission method is provided, comprising:

[0008] Upon receiving an indication message from a remote user terminal or meeting a pre-configured triggering condition, a first identification message is generated. The first identification message indicates data in the uplink data of the remote user terminal that has been successfully received by the relay user terminal but has not yet been confirmed by the base station. The uplink is the communication path from the remote user terminal to the base station.

[0009] The first identification information is sent to the remote user terminal so that the remote user terminal can determine the data that was not successfully transmitted to the base station based on the first identification information.

[0010] In some embodiments of this disclosure, the data transmission method further includes:

[0011] Upon receiving an indication message from a remote user terminal or upon meeting a pre-configured triggering condition, a second identification message is generated. The second identification message indicates data in the downlink data of the remote user terminal that has been successfully received by the relay user terminal but has not yet been acknowledged by the remote user terminal. The downlink is the communication path from the base station to the remote user terminal.

[0012] The second identification information is sent to the base station so that the base station can determine the data that was not successfully transmitted to the remote user terminal based on the second identification information.

[0013] In some embodiments of this disclosure, sending the first identification information to the remote user terminal includes:

[0014] Generate a first radio link control status report, wherein the first radio link control status report includes the first identification information;

[0015] The first identification information is sent to the remote user terminal via the first wireless link control status report.

[0016] In some embodiments of this disclosure, sending the second identification information to the base station includes:

[0017] Generate a second radio link control status report, wherein the second radio link control status report includes the second identification information;

[0018] The second identification information is sent to the remote user terminal via the second wireless link control status report.

[0019] In some embodiments of this disclosure, the data transmission method further includes:

[0020] The first and second identifier bits in the radio link control status report are used to represent the first identification information or the second identification information. The first identifier bit is used to indicate whether the second identifier bit is enabled. Enabling the second identifier bit indicates that the data packet of the first or second identification information was not successfully transmitted to the final target node. The final target node corresponding to the first identifier information is the base station, and the final target node corresponding to the second identifier information is the remote user terminal. The second identifier bit is also used to indicate whether the relay user terminal received the data packet.

[0021] In some embodiments of this disclosure, the indication information sent by the remote user terminal is as follows:

[0022] The remote user terminal sends a request message after receiving a handover command from the source base station.

[0023] In some embodiments of this disclosure, the indication information sent by the remote user terminal is as follows:

[0024] When the handover conditions for switching from an indirect path to a direct path or from one indirect path to another are met, the remote user terminal actively sends a handover trigger message. Here, the direct path is the path through which the remote user terminal directly communicates with the base station, and the indirect path is the path through which the remote user terminal communicates with the base station through a relay user terminal.

[0025] In some embodiments of this disclosure, the indication information sent by the remote user terminal is: trigger information sent by the remote user terminal when it determines, based on the measurement report, that the current signal quality is lower than a pre-configured threshold.

[0026] In some embodiments of this disclosure, the pre-configured triggering condition is: meeting a predetermined time interval, or judging from a measurement report that the current signal quality is lower than a pre-configured threshold.

[0027] According to another aspect of this disclosure, a data transmission method is provided, comprising:

[0028] Upon receiving an indication message from a remote user terminal or upon meeting a pre-configured triggering condition, a second identification message is generated. The second identification message indicates data in the downlink data of the remote user terminal that has been successfully received by the relay user terminal but has not yet been acknowledged by the remote user terminal. The downlink is the communication path from the base station to the remote user terminal.

[0029] The second identification information is sent to the base station so that the base station can determine the data that was not successfully transmitted to the remote user terminal based on the second identification information.

[0030] According to another aspect of this disclosure, a data transmission method is provided, comprising:

[0031] The system receives first identification information sent by a relay user terminal, wherein the first identification information indicates data in the uplink data of the remote user terminal that has been successfully received by the relay user terminal but has not yet been confirmed by the base station. The uplink is the communication path from the remote user terminal to the base station. The first identification information is generated by the relay user terminal when it receives the indication information sent by the remote user terminal or when a pre-configured trigger condition is met.

[0032] Based on the first identification information, data that was not successfully transmitted to the base station is determined.

[0033] In some embodiments of this disclosure, the data transmission method further includes: retransmitting the data that was not successfully transmitted to the base station.

[0034] In some embodiments of this disclosure, determining the data that was not successfully transmitted to the base station based on the first identification information includes: when a remote user terminal switches from a source base station to a target base station, determining the data that was not successfully transmitted to the source base station based on the first identification information and a packet data aggregation protocol report received from the target base station.

[0035] In some embodiments of this disclosure, retransmitting the data that was not successfully transmitted to the base station includes: when a remote user terminal switches from a source base station to a target base station, retransmitting the data that was not successfully transmitted to the source base station to the target base station.

[0036] According to another aspect of this disclosure, a data transmission method is provided, comprising:

[0037] The system receives second identification information sent by a relay user terminal, wherein the second identification information indicates data in the downlink data of a remote user terminal that has been successfully received by the relay user terminal but has not yet been acknowledged by the remote user terminal. The downlink is the communication path from the base station to the remote user terminal. The second identification information is determined by the relay user terminal when it receives an indication information sent by the remote user terminal or when a pre-configured trigger condition is met.

[0038] The data that was not successfully transmitted to the remote user terminal is determined based on the second identification information.

[0039] In some embodiments of this disclosure, the data transmission method further includes:

[0040] In the event that the remote user terminal switches from the source base station to the target base station, the data that was not successfully transmitted to the remote user terminal is forwarded to the target base station.

[0041] According to another aspect of this disclosure, a relay user terminal is provided, comprising:

[0042] The first identification information determination module is configured to generate first identification information when receiving indication information sent by a remote user terminal or when a pre-configured trigger condition is met. The first identification information indicates data in the uplink data of the remote user terminal that has been successfully received by the relay user terminal but has not yet been confirmed by the base station. The uplink is the communication path from the remote user terminal to the base station.

[0043] The first sending module is configured to send the first identification information to a remote user terminal so that the remote user terminal can determine, based on the first identification information, the data that was not successfully transmitted to the base station.

[0044] According to another aspect of this disclosure, a relay user terminal is provided, comprising:

[0045] The second identification information determination module is configured to generate second identification information when receiving indication information sent by a remote user terminal or when a pre-configured trigger condition is met. The second identification information indicates data in the downlink data of the remote user terminal that has been successfully received by the relay user terminal but has not yet been confirmed by the remote user terminal. The downlink is the communication path from the base station to the remote user terminal.

[0046] The second sending module is configured to send second identification information to the base station so that the base station can determine, based on the second identification information, the data that was not successfully transmitted to the remote user terminal.

[0047] According to another aspect of this disclosure, a remote user terminal is provided, comprising:

[0048] The first identification information receiving module is configured to receive first identification information sent by the relay user terminal. The first identification information indicates data in the uplink data of the remote user terminal that has been successfully received by the relay user terminal but has not yet been confirmed by the base station. The uplink is the communication path from the remote user terminal to the base station. The first identification information is generated by the relay user terminal when it receives the indication information sent by the remote user terminal or when a pre-configured trigger condition is met.

[0049] The first data determination module is configured to determine data that was not successfully transmitted to the base station based on the first identification information.

[0050] According to another aspect of this disclosure, a base station is provided, comprising:

[0051] The second identification information receiving module is configured to receive second identification information sent by the relay user terminal. The second identification information indicates data in the downlink data of the remote user terminal that has been successfully received by the relay user terminal but has not yet been confirmed by the remote user terminal. The downlink is the communication path from the base station to the remote user terminal. The second identification information is determined by the relay user terminal when it receives the indication information sent by the remote user terminal or when a pre-configured trigger condition is met.

[0052] The second data determination module is configured to determine, based on the second identification information, data that was not successfully transmitted to the remote user terminal.

[0053] According to another aspect of this disclosure, an electronic device is provided, comprising:

[0054] The memory is configured to store instructions;

[0055] The processor is configured to execute the instructions, causing the electronic device to perform operations implementing the data transmission method as described in any of the above embodiments.

[0056] According to another aspect of this disclosure, a data transmission system is provided, including a relay user terminal as described in any of the above embodiments, a remote user terminal as described in any of the above embodiments, and a base station as described in any of the above embodiments.

[0057] According to another aspect of this disclosure, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions that, when executed by a processor, implement the data transmission method as described in any of the above embodiments.

[0058] This disclosure ensures that data transmission at the remote UE is not lost. Attached Figure Description

[0059] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0060] Figure 1 This is a schematic diagram of some embodiments of the data transmission method disclosed herein.

[0061] Figure 2 This is a schematic diagram of some other embodiments of the data transmission method disclosed herein.

[0062] Figure 3 This is a schematic diagram of some other embodiments of the data transmission method disclosed herein.

[0063] Figure 4 This is a schematic diagram of some other embodiments of the data transmission method disclosed herein.

[0064] Figure 5 This is a schematic diagram of some other embodiments of the data transmission method disclosed herein.

[0065] Figure 6 This is a schematic diagram of some other embodiments of the data transmission method disclosed herein.

[0066] Figure 7 This is a schematic diagram of UL data transmission in some embodiments of this disclosure.

[0067] Figure 8 The diagram shows data in the PDCP buffer at the remote UE in some embodiments of this disclosure.

[0068] Figure 9 This is a schematic diagram of DL data transmission in some embodiments of this disclosure.

[0069] Figure 10 This is a schematic diagram of the data in the PDCP buffer in some embodiments of this disclosure.

[0070] Figure 11 This is a schematic diagram of an RLC status report in some embodiments of related technologies.

[0071] Figure 12 This is a schematic diagram of RLC status reporting in some embodiments of this disclosure.

[0072] Figure 13 This is a schematic diagram of some embodiments of the relay user terminal disclosed herein.

[0073] Figure 14 This is a schematic diagram of some other embodiments of the relay user terminal disclosed herein.

[0074] Figure 15 This is a schematic diagram of some embodiments of the relay user terminal disclosed herein.

[0075] Figure 16 This is a schematic diagram of some embodiments of the remote user terminal disclosed herein.

[0076] Figure 17 This is a schematic diagram of some embodiments of the base station disclosed herein.

[0077] Figure 18 This is a schematic diagram of the structure of some embodiments of the electronic device disclosed herein.

[0078] Figure 19 This is a schematic diagram of the structure of some embodiments of the data transmission system disclosed herein. Detailed Implementation

[0079] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit this disclosure or its application or use. All other embodiments obtained by those skilled in the art based on the embodiments of this disclosure without creative effort are within the scope of protection of this disclosure.

[0080] Unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps set forth in these embodiments do not limit the scope of this disclosure.

[0081] At the same time, it should be understood that, for ease of description, the dimensions of the various parts shown in the accompanying drawings are not drawn according to actual scale.

[0082] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and equipment should be considered part of the specification.

[0083] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values.

[0084] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.

[0085] The inventors also discovered through research that during indirect-to-direct or indirect-to-indirect-path handovers, when the source base station forwards all DL (Down Link) data acknowledged by the relay UE rather than the remote UE to the target base station, DL data loss may occur. Related technology NR PDCP only considered single-hop links in its design.

[0086] In view of at least one of the above technical problems, this disclosure provides a data transmission method and system, a remote and relay user terminal, and a base station. This disclosure provides a new standardized mechanism to ensure that the data transmission of the remote UE is not lost during the UL and DL data transmission during the path handover between the UE and the base station of the network relay.

[0087] The present disclosure will now be described through specific embodiments.

[0088] Figure 1 This is a schematic diagram of some embodiments of the data transmission method of this disclosure. Preferably, this embodiment can be executed by a relay user terminal, an electronic device, or a data transmission system of this disclosure. The method includes at least one step of steps 11 to 12, wherein:

[0089] Step 11: Upon receiving an indication message from a remote user terminal or meeting a pre-configured triggering condition, generate first identification information. The first identification information indicates data in the uplink data of the remote user terminal that has been successfully received by the relay user terminal but has not yet been confirmed by the base station. The uplink is the communication path from the remote user terminal to the base station.

[0090] In some embodiments of this disclosure, the pre-configured triggering conditions may include at least one of the following conditions: the relay user terminal determines that a predetermined time interval is met, or determines that the current signal quality is lower than a pre-configured threshold based on a measurement report.

[0091] In some embodiments of this disclosure, when the relay user terminal determines that a predetermined time interval has been met, or when it determines, based on a measurement report, that the current signal quality is below a pre-configured threshold, the situation may be either a path switching scenario or a path that remains unchanged.

[0092] In some embodiments of this disclosure, the indication information sent by the remote user terminal is a trigger message sent by the remote user terminal when it determines, based on a measurement report, that the current signal quality is below a pre-configured threshold. This can be in the case of path switching or path invariance.

[0093] In some embodiments of this disclosure, the indication information sent by the remote user terminal is: a request message sent by the remote user terminal when it receives a handover command sent by the source base station.

[0094] In some embodiments of this disclosure, the indication information sent by the remote user terminal is: a handover trigger message actively sent by the remote user terminal when the handover conditions of indirect path to direct path or one indirect path to another are met, wherein the direct path is the path through which the remote user terminal directly communicates with the base station, and the indirect path is the path through which the remote user terminal communicates with the base station through a relay user terminal.

[0095] In some embodiments of this disclosure, the indirect path to direct path can be: the path of a remote user terminal communicating with a base station via a relay user terminal is switched to the path of the remote user terminal communicating directly with the base station, that is, the base station in the path remains unchanged, but the relay user terminal is removed; the indirect path to direct path can also be: the path of a remote user terminal communicating with a base station via a relay user terminal is switched to the direct path of the remote user terminal communicating directly with another target medium.

[0096] In some embodiments of this disclosure, the indirect path to another indirect path can be: a base station handover, i.e., the path for the terminal to communicate with the source base station via a relay user terminal is changed to the path for the terminal to communicate with the target base station via a relay user terminal; a relay terminal handover, i.e., the path for the terminal to communicate with the base station via a first relay user terminal is changed to the path for the terminal to communicate with the base station via a second relay user terminal; or a relay terminal addition, i.e., the path for the terminal to communicate with the base station via a first relay user terminal is changed to the path for the terminal to communicate with the base station via both a first and a second relay user terminal; at least two of the following changes occur simultaneously: a base station handover, a relay terminal handover, and a relay terminal addition.

[0097] Step 12: Send the first identification information to the remote user terminal so that the remote user terminal can determine the data that was not successfully transmitted to the base station based on the first identification information.

[0098] In some embodiments of this disclosure, sending the first identification information to a remote user terminal includes: generating a first radio link control status report, wherein the first radio link control status report includes the first identification information; and sending the first identification information to the remote user terminal through the first radio link control status report.

[0099] In some embodiments of this disclosure, when a remote user terminal switches from a source base station to a target base station, the remote user terminal is configured to determine, based on the first identification information and a packet data aggregation protocol report received from the target base station, the data that was not successfully transmitted to the source base station, and retransmit the data that was not successfully transmitted to the source base station to the target base station.

[0100] According to relevant technical standards, lossless transmission of uplink and downlink data for Inter-gNB (inter-base station) indirect path handover scenarios cannot be avoided. In particular, if sequential transmission is configured on the gNB side, UL data may be interrupted while the target gNB is waiting for lost data packets.

[0101] The method described in the above embodiments of this disclosure uses the RLC status report information reported by the relay UE to determine the UL data packets that have been received by the relay UE but have not yet been successfully confirmed by the base station. This assists the remote UE in retransmitting data packets after handover, which can prevent the remote UE from losing data during indirect path handover, achieve lossless data transmission, and ensure the continuity of user services.

[0102] Figure 2 This is a schematic diagram of some other embodiments of the data transmission method of this disclosure. Preferably, this embodiment can be executed by a relay user terminal, an electronic device, or a data transmission system of this disclosure. The method includes at least one step of steps 21 to 22, wherein:

[0103] Step 21: Upon receiving an indication message from the remote user terminal or meeting a pre-configured triggering condition, generate second identification information. The second identification information indicates data in the downlink data of the remote user terminal that has been successfully received by the relay user terminal but has not yet been acknowledged by the remote user terminal. The downlink is the communication path from the base station to the remote user terminal.

[0104] In some embodiments of this disclosure, the pre-configured triggering conditions may include at least one of the following conditions: the relay user terminal determines that a predetermined time interval is met, or determines that the current signal quality is lower than a pre-configured threshold based on a measurement report.

[0105] In some embodiments of this disclosure, when the relay user terminal determines that a predetermined time interval has been met, or when it determines, based on a measurement report, that the current signal quality is below a pre-configured threshold, the situation may be either a path switching scenario or a path that remains unchanged.

[0106] In some embodiments of this disclosure, the indication information sent by the remote user terminal is a trigger message sent by the remote user terminal when it determines, based on a measurement report, that the current signal quality is below a pre-configured threshold. This can be in the case of path switching or path invariance.

[0107] In some embodiments of this disclosure, the indication information sent by the remote user terminal is: a request message sent by the remote user terminal when it receives a handover command sent by the source base station.

[0108] In some embodiments of this disclosure, the indication information sent by the remote user terminal is: a handover trigger message actively sent by the remote user terminal when the handover conditions of indirect path to direct path or one indirect path to another are met, wherein the direct path is the path through which the remote user terminal directly communicates with the base station, and the indirect path is the path through which the remote user terminal communicates with the base station through a relay user terminal.

[0109] Step 22: Send the second identification information to the base station so that the base station can determine the data that was not successfully transmitted to the remote user terminal based on the second identification information.

[0110] In some embodiments of this disclosure, the step of sending the second identification information to the base station includes: generating a second radio link control status report, wherein the second radio link control status report includes the second identification information; and sending the second identification information to a remote user terminal through the second radio link control status report.

[0111] In some embodiments of this disclosure, when a remote user terminal switches from a source base station to a target base station, the source base station is used to forward the data that was not successfully transmitted to the remote user terminal to the target base station.

[0112] The method described in the above embodiments of this disclosure uses the RLC status report information reported by the relay UE to determine the DL data packets that have been received by the relay UE but have not yet been successfully confirmed by the remote UE. The auxiliary base station retransmits the data packets after the handover, which can avoid the remote UE from losing data during the indirect path handover, realize lossless data transmission and ensure the continuity of user services.

[0113] Figure 3 This is a schematic diagram illustrating further embodiments of the data transmission method of this disclosure. Preferably, this embodiment can be executed by a relay user terminal, an electronic device, or a data transmission system of this disclosure. The method includes at least one step from step 31 to step 33, wherein:

[0114] Step 31: Upon receiving an indication message from the remote user terminal or meeting a pre-configured triggering condition, generate either a first identification message or a second identification message. The first identification message indicates uplink data from the remote user terminal that has been successfully received by the relay user terminal but has not yet been acknowledged by the base station. The uplink is the communication path from the remote user terminal to the base station. The second identification message indicates downlink data from the remote user terminal that has been successfully received by the relay user terminal but has not yet been acknowledged by the remote user terminal. The downlink is the communication path from the base station to the remote user terminal.

[0115] In some embodiments of this disclosure, the pre-configured triggering conditions may include at least one of the following conditions: the relay user terminal determines that a predetermined time interval is met, or determines that the current signal quality is lower than a pre-configured threshold based on a measurement report.

[0116] In some embodiments of this disclosure, when the relay user terminal determines that a predetermined time interval has been met, or when it determines, based on a measurement report, that the current signal quality is below a pre-configured threshold, the situation may be either a path switching scenario or a path that remains unchanged.

[0117] In some embodiments of this disclosure, the indication information sent by the remote user terminal is a trigger message sent by the remote user terminal when it determines, based on a measurement report, that the current signal quality is below a pre-configured threshold. This can be in the case of path switching or path invariance.

[0118] In some embodiments of this disclosure, the indication information sent by the remote user terminal is: a request message sent by the remote user terminal when it receives a handover command sent by the source base station.

[0119] In some embodiments of this disclosure, the indication information sent by the remote user terminal is: a handover trigger message actively sent by the remote user terminal when the handover conditions of indirect path to direct path or one indirect path to another are met, wherein the direct path is the path through which the remote user terminal directly communicates with the base station, and the indirect path is the path through which the remote user terminal communicates with the base station through a relay user terminal.

[0120] In some embodiments of this disclosure, step 31 may include: the relay UE generating a first RLC status report and a second RLC status report based on the indication information sent by the remote UE or when the network pre-configured triggering conditions are met, wherein the first RLC status report is used to indicate to the remote UE RLC PDU data that has not yet been acknowledged by the base station, and the second RLC status report is used to indicate to the base station RLC PDU data that has not yet been acknowledged by the remote UE.

[0121] Step 32: Send the first identification information to the remote user terminal so that the remote user terminal can determine the data that was not successfully transmitted to the base station based on the first identification information.

[0122] In some embodiments of this disclosure, sending the first identification information to the remote user terminal includes: sending the first RLC status report to the remote user terminal.

[0123] In some embodiments of this disclosure, when a remote user terminal switches from a source base station to a target base station, the remote user terminal is configured to determine, based on the first identification information and a packet data aggregation protocol report received from the target base station, the data that was not successfully transmitted to the source base station, and retransmit the data that was not successfully transmitted to the source base station to the target base station.

[0124] Step 33: Send the second identification information to the base station so that the base station can determine the data that was not successfully transmitted to the remote user terminal based on the second identification information.

[0125] In some embodiments of this disclosure, the step of sending the second identification information to the base station includes: sending the second RLC status report to the source base station.

[0126] In some embodiments of this disclosure, when a remote user terminal switches from a source base station to a target base station, the source base station is used to forward the data that was not successfully transmitted to the remote user terminal to the target base station.

[0127] The method described in the above embodiments of this disclosure uses the RLC status report information reported by the relay UE to determine the UL / DL data packets that have been received by the relay UE but have not yet been successfully confirmed by the base station / remote UE. This assists the base station / remote UE in retransmitting data packets after handover, which can prevent the remote UE from losing data during indirect path handover, achieve lossless data transmission, and ensure the continuity of user services.

[0128] Figure 4 This is a schematic diagram illustrating some embodiments of the data transmission method of this disclosure. Preferably, this embodiment can be executed by a remote user terminal, an electronic device, or a data transmission system of this disclosure. The method includes at least one step from step 41 to step 42, wherein:

[0129] Step 41: Receive first identification information sent by the relay user terminal, wherein the first identification information indicates data in the uplink data of the remote user terminal that has been successfully received by the relay user terminal but has not yet been confirmed by the base station. The uplink is the communication path from the remote user terminal to the base station. The first identification information is generated by the relay user terminal when it receives the indication information sent by the remote user terminal or when the pre-configured triggering conditions are met.

[0130] In some embodiments of this disclosure, step 41 may include: receiving a first RLC status report sent by a relay user terminal, wherein the first RLC status report includes first identification information.

[0131] Step 42: Determine the data that was not successfully transmitted to the base station based on the first identification information;

[0132] In some embodiments of this disclosure, step 42 may include: in the case where the remote user terminal switches from the source base station to the target base station, determining the data that was not successfully transmitted to the source base station based on the first identification information and the packet data aggregation protocol report received from the target base station.

[0133] In some embodiments of this disclosure, such as Figure 4 As shown, the data transmission method of this disclosure may further include step 43, wherein:

[0134] Step 43: Resend the data that was not successfully transmitted to the base station.

[0135] In some embodiments of this disclosure, step 43 may include: retransmitting the data that was not successfully transmitted to the source base station to the target base station when the remote user terminal switches from the source base station to the target base station.

[0136] The method described in the above embodiments of this disclosure uses the RLC status report information reported by the relay UE to determine the UL data packets that have been received by the relay UE but have not yet been successfully confirmed by the base station. This assists the remote UE in retransmitting data packets after handover, which can prevent the remote UE from losing data during indirect path handover, achieve lossless data transmission, and ensure the continuity of user services.

[0137] Figure 5 This is a schematic diagram illustrating further embodiments of the data transmission method of this disclosure. Preferably, this embodiment can be executed by the base station, electronic device, or data transmission system of this disclosure. The method includes at least one step from step 51 to step 52, wherein:

[0138] Step 51: Receive second identification information sent by the relay user terminal, wherein the second identification information indicates data in the downlink data of the remote user terminal that has been successfully received by the relay user terminal but has not yet been confirmed by the remote user terminal, the downlink being the communication path from the base station to the remote user terminal, and the second identification information is determined by the relay user terminal when it receives the indication information sent by the remote user terminal or when the pre-configured triggering conditions are met.

[0139] In some embodiments of this disclosure, step 51 may include: receiving a second RLC status report sent by a relay user terminal, wherein the second RLC status report includes second identification information.

[0140] Step 52: Determine the data that was not successfully transmitted to the remote user terminal based on the second identification information.

[0141] In some embodiments of this disclosure, such as Figure 5 As shown, the data transmission method may further include step 53, wherein:

[0142] Step 53: If the remote user terminal switches from the source base station to the target base station, forward the data that was not successfully transmitted to the remote user terminal to the target base station.

[0143] The method described in the above embodiments of this disclosure uses the RLC status report information reported by the relay UE to determine the DL data packets that have been received by the relay UE but have not yet been successfully confirmed by the remote UE. The auxiliary base station retransmits the data packets after the handover, which can avoid the remote UE from losing data during the indirect path handover, realize lossless data transmission and ensure the continuity of user services.

[0144] Figure 6 This is a schematic diagram illustrating further embodiments of the data transmission method of this disclosure. Preferably, this embodiment can be executed by the electronic device or data transmission system of this disclosure. The method includes at least one step from step 0 to step 6, wherein:

[0145] Step 0: The remote UE accesses the network through a relay UE.

[0146] Step 1: The remote UE receives the Radio Resource Control (RRC) connection reconfiguration message from the source base station, parses the RRC connection reconfiguration signaling, and obtains the parsing result. When it confirms that it has received the handover command, it can send indication information to the source relay UE to request a data transmission status report.

[0147] In some embodiments of this disclosure, such as Figure 6 As shown, the RRC connection reconfiguration signaling is a Handover Command.

[0148] Step 2: After the relay UE receives the indication information sent by the remote UE, or when the network pre-configured triggering conditions are met, it generates the first RLC status report and the second RLC status report.

[0149] In some embodiments of this disclosure, the first RLC status report (for UL data of a remote UE) includes at least one of the following: identification information of a PC5 RLC PDU successfully received at the relay UE, identification information of a PC5 RLC PDU not successfully received at the relay UE, identification information of a Uu RLC PDU successfully received at the base station, and identification information of a UuRLC PDU successfully received at the relay UE but not acknowledged by the base station.

[0150] In some embodiments of this disclosure, the second RLC status report (for DL ​​data of the remote UE) includes at least one of the following: identification information of a Uu RLC PDU successfully received at the relay UE, identification information of a Uu RLC PDU that was not successfully received at the relay UE, identification information of a PC5 RLC PDU successfully received at the remote UE, and identification information of a PC5 RLC PDU that was successfully received at the relay UE but not acknowledged by the remote UE.

[0151] Step 3: The relay UE sends the first RLC status report and the second RLC status report to the remote UE and the source base station, respectively.

[0152] Step 4: The source base station determines the PDCP SDU data packet to be forwarded to the remote UE at the target base station based on the received second RLC status report. The source base station sends an SN STATUS TRANSFER message to the target base station to transfer the uplink and downlink PDCP SN (Sequence Number) and HFN (Hyper Frame Number) states. The source base station forwards the downlink PDCP SDU from the UPF to the target base station, whose SN corresponds to the PDCP PDU that the remote UE has not yet acknowledged, where Data Forwarding refers to data forwarding.

[0153] Step 5: After the remote UE accesses the target base station, it confirms the PDCP SDU data packets that were not successfully transmitted to the source base station based on the first RLC status report received from the relay UE and the PDCP status report received from the target base station, and then retransmits the data packets to the target base station.

[0154] Step 6: After the remote UE accesses the network, the target base station determines the downlink PDCP data packets to be transmitted based on the PDCP status report from the remote UE.

[0155] The related technology NR PDCP only considered single-hop links during its design.

[0156] The embodiments of this disclosure provide a new standardized mechanism to ensure that data transmission of the remote UE is not lost during the UL and DL data transmission during the inter-base station path handover from the UE to the network relay.

[0157] The embodiments of this disclosure provide a data transmission method and device for relay communication. The method includes: a relay UE generating a first RLC status report and a second RLC status report based on indication information sent by a remote UE or when a pre-configured network trigger condition is met. The first RLC status report indicates to the remote UE RLC PDU data that has not yet been acknowledged by the source base station, and the second RLC status report indicates to the source base station RLC PDU data that has not yet been acknowledged by the remote UE. The remote UE acknowledges PDCP SDU (Service Data Unit) data packets that were not successfully transmitted to the source base station based on the first RLC status report and a PDCP status report received from the target base station. The source base station determines, based on the second RLC status report, which should forward PDCP SDU data packets to the remote UE under the target base station. The method described in the embodiments of this disclosure can prevent the remote UE from losing uplink or downlink data packets during indirect path handover, achieving lossless data transmission and ensuring service continuity for users.

[0158] The present disclosure will now be described through specific embodiments.

[0159] First type of specific embodiment

[0160] Figure 7 This is a schematic diagram of UL data transmission in some embodiments of this disclosure. Figure 7 In this context, CN stands for Core Network, S-gNB is the source base station, T-gNB is the target base station, Relay UE is the relay user terminal, Remote UE is the remote user terminal, and # indicates uplink data packets. Normal Xn / NG-HO indicates a handover between the standard Xn interface and the NG interface, HO indicates a handover, the NG interface is the interface between the radio access network and the 5G core network, and the Xn interface is the network interface between NG-RAN nodes (gNB or ng-eNB).

[0161] like Figure 7 As shown, UL data transmission may include four steps, among which:

[0162] Step 7-1 is when the remote user terminal receives the handover command (HO command), where the indication signaling is the indication signal sent by the remote user terminal to the relay user terminal after receiving the handover command.

[0163] Step 7-2 involves the relay user terminal sending an RLC status report (the first RLC status report) to the remote user terminal before the remote user terminal performs the handover. The source base station sends an SN STATUSTRANSFER message to the target base station to transfer the uplink and downlink PDCP sequence numbers and superframe numbers.

[0164] Step 7-3 involves the remote UE, after accessing the target base station, confirming the PDCP SDU data packets that were not successfully transmitted to the source base station based on the first RLC status report received from the relay UE and the PDCP status report received from the target base station.

[0165] Step 7-4 is when, after the path handover is completed, the remote UE starts from the #3 data packet and retransmits the data packet to the target base station. Here, Start UL is the uplink data packet that starts to be retransmitted.

[0166] For UL data transmission, such as Figure 7 As shown, assuming that when the remote UE receives the handover command, the data in the PDCP buffer at the remote UE is as follows: Figure 8 As shown (where # represents the PDCP PDU serial number). Figure 8 The diagram shows data in the PDCP buffer at the remote UE in some embodiments of this disclosure.

[0167] like Figure 7 and Figure 8 As shown, all RLC data packets corresponding to data packets #1 and #2 were successfully received by the source base station.

[0168] All RLC packets corresponding to packets #3 and #4 were successfully received by the source relay UE, but these RLC data have not yet been acknowledged by the source base station (i.e., packets that have been submitted to the lower layer of the SRAP layer but have not yet been transmitted over the air interface, or packets that have been transmitted over the air interface between the source relay UE and the source base station but have not yet received acknowledgment feedback).

[0169] The source relay UE has not yet received RLC packets corresponding to #5 and thereafter.

[0170] In the relevant technical methods, from the perspective of the remote UE, #1 to #4 have been successfully transmitted because #1 to #4 have all been acknowledged by the source relay UE at the RLC level. When the remote UE receives a handover command containing an indication to re-establish PDCP, the remote UE only retransmits data #5 and beyond to the target base station.

[0171] Using the improved method of this disclosure, the remote UE can determine from the RLC status report received from the relay UE that data packets #3 and #4 have not been successfully transmitted to the source base station. When the remote UE receives a handover command containing an indication to re-establish PDCP, the remote UE retransmits data #3 and subsequent data to the target base station.

[0172] Second type of specific embodiment

[0173] Figure 9 This is a schematic diagram of DL data transmission in some embodiments of this disclosure. Here, # represents a downlink data packet.

[0174] like Figure 9 As shown, DL data transmission may include four steps, among which:

[0175] Step 9-1 is when the remote user terminal receives the handover command (HO command), where the indication signaling is the indication signal sent by the remote user terminal to the relay user terminal after receiving the handover command.

[0176] Step 9-2 involves the relay user terminal sending an RLC status report (i.e., the second RLC status report) to the source base station before the remote user terminal performs the handover. The source base station then performs data forwarding and sends an SN STATUS TRANSFER message to the target base station, forwarding the downlink PDCP SDU from the UPF. The SN of this message corresponds to the PDCP PDU that the remote UE has not yet acknowledged.

[0177] Step 9-3 involves the target base station determining the downlink PDCP data packets to be transmitted based on the PDCP status report from the remote UE after the remote UE has accessed the network.

[0178] Step 9-4 is when, after the path handover is completed, the target base station retransmits data packets to the remote UE starting from data packet #4, where Start DL is the downlink data packet that begins to be retransmitted.

[0179] For DL ​​data transmission, such as Figure 9As shown, the RLC packets corresponding to the PDCP data packets sent by the source gNB may have been acknowledged by the source relay UE, but when HO occurs, they may be waiting to be transmitted to the remote UE via the PC5 link. A problem similar to packet loss during path handover from an indirect link, as described in UL, may occur. Using the improved method of this disclosure, the source base station can know from the RLC status report received from the relay UE that the #3 and #4 data packets have not yet been successfully transmitted to the remote UE. Therefore, it forwards the data received from the UPF after #3 to the target base station through a data forwarding procedure, and after the remote UE re-accesses, the target base station acknowledges and retransmits the unreceived data to the remote UE. The target base station knows from the PDCP status sent by the remote UE that the remote UE has successfully received the #3 data packet, and thus the target base station retransmits the unreceived data, i.e., the #4 and subsequent data packets, to the remote UE.

[0180] Third type of specific embodiment

[0181] In some embodiments of this disclosure, Figures 1 to 6 In the embodiment, the data transmission method may further include: using a first identifier bit and a second identifier bit in the Radio Link Control (RLC) status report to represent the first identifier information or the second identifier information, wherein the first identifier bit is used to indicate whether the second identifier bit is enabled, and the enabling of the second identifier bit is used to indicate that the data packet of the first identifier information or the second identifier information has not been successfully transmitted to the final target node, the final target node corresponding to the first identifier information is the base station, the final target node corresponding to the second identifier information is the remote user terminal, and the second identifier bit is also used to indicate whether the relay user terminal has received the data packet.

[0182] In some embodiments of this disclosure, the first identifier bit may be the reserved field R in the RLC status report following E1 in ACK_SN.

[0183] In some embodiments of this disclosure, the second identifier can be the reserved field R after NACK_SN in the RLC status report, which is changed to the E4 field.

[0184] Figure 10 This is a schematic diagram of the data in the PDCP buffer in some embodiments of this disclosure. For example... Figure 10 As shown, dark colors represent data packets that have been received, while white colors represent data packets that have not been received.

[0185] Figure 11 This is a schematic diagram of RLC status reporting in some embodiments of related technologies. For example... Figure 11 The image shows a PDU status report with a 12-bit serial number.

[0186] like Figure 11As shown, the meaning of the D / C field is: a D / C field value of 0 indicates a control PDU, and a D / C field value of 1 indicates a data PDU.

[0187] like Figure 11 As shown, the CPT field is used to represent different types of control data packets. If the CPT field is 000, it indicates a Protocol Data Unit Status (STATUS PDU).

[0188] like Figure 11 As shown, ACK_SN indicates that data packets with this sequence number and subsequent sequences were not received, and there was no explicit indication that they were not received.

[0189] like Figure 11 As shown, E1 indicates whether a NACK_SN / E1 / E2 / E3 field should follow it. Currently, 1 can be entered.

[0190] like Figure 11 As shown, NACK_SN represents a lost data packet.

[0191] like Figure 11 As shown, E2 indicates whether SoStart and SoEnd are followed. This is mainly used for cases where data packets are not received completely, which is not relevant in this scenario.

[0192] like Figure 11 As shown, the E3 field indicates whether it is followed by a series of messages about unreceived RLC SDUs. It also indicates whether a range field is present.

[0193] like Figure 11 As shown, the NACK range field indicates that there are several consecutive RLC SDUs lost, starting from NACK_SN (including NACK_SN).

[0194] The final data packet looks like the one shown in Table 1.

[0195]

[0196] Table 1

[0197] Figure 8 The diagram shows data in the PDCP buffer in some embodiments of this disclosure. Figure 8 As shown, all RLC data packets corresponding to data packets #1 and #2 were successfully received by the final target node (base station {UL scenario} or remote UE {DL scenario}); all RLC data packets corresponding to data packets #3 and #4 were successfully received by the intermediate node (source relay UE), but these RLC data packets have not yet been acknowledged by the final destination node; the source relay UE has not yet received RLC data packets corresponding to #5 and thereafter.

[0198] ACK_SN indicates that this sequence number and subsequent data packets have not been received. (That is, the identification information of the PC5 RLC PDU that was not successfully received at the relay UE in this disclosure {first status report, UL case}, or the identification information of the Uu RLC PDU that was not successfully received at the relay UE {second status report, DL case}).

[0199] Figure 12 This is a schematic diagram of RLC status reporting in some embodiments of this disclosure. For example... Figure 12 As shown, the reserved field R after E1 in ACK_SN is used to indicate the type of NACK_SN (whether E4 is enabled): when NACK_SN type is 1, it indicates that the data packet was lost (or not delivered) at the final destination (i.e., the identification information of the Uu RLC PDU that was not successfully received at the base station, or the identification information of the PC5 RLC PDU that was not successfully received at the remote UE); when NACK_SN type is 0, it follows the behavior defined by the traditional standard.

[0200] In some embodiments of this disclosure, such as Figure 12 As shown, the reserved field R after NACK_SN becomes the E4 field. The meaning of the E4 value is as follows: when E4 is 0, it means that the current node (relay UE) did not receive the data packet. When E4 is 0, it means that the current node (relay UE) successfully received the RLC PDU but it was not confirmed by the final target node. That is, the relay UE successfully received the Uu RLC PDU but it was not confirmed by the base station, or the relay UE successfully received the PC5 RLC PDU but it was not confirmed by the remote UE.

[0201] In some embodiments of this disclosure, such as Figure 12 The final data packet, once filled in, looks like the one shown in Table 2.

[0202]

[0203] Table 2

[0204] The embodiments described above are applicable to P-RAN (Pre-Range Radio Service). The methods described above can ensure lossless transmission of user data during indirect path handover, guaranteeing service continuity for users and thus improving the practicality of relay access in coverage expansion applications.

[0205] Figure 13 This is a schematic diagram illustrating some embodiments of the relay user terminal disclosed herein. For example... Figure 13 As shown, the relay user terminal of this disclosure may include a first identification information determination module 110 and a first transmission module 120, wherein:

[0206] The first identification information determination module 110 is configured to generate first identification information when receiving indication information sent by a remote user terminal or when a pre-configured trigger condition is met. The first identification information indicates data in the uplink data of the remote user terminal that has been successfully received by the relay user terminal but has not yet been confirmed by the base station. The uplink is the communication path from the remote user terminal to the base station.

[0207] The first sending module 120 is configured to send the first identification information to a remote user terminal so that the remote user terminal can determine the data that was not successfully transmitted to the base station based on the first identification information.

[0208] In some embodiments of this disclosure, the relay user terminal of this disclosure can be configured to perform any of the above embodiments of this disclosure (e.g., Figures 1-3 Any embodiment, Figure 6 The data transmission method described in steps 2-3 of the embodiment.

[0209] The embodiments described above use the RLC status report information reported by the relay UE to determine the UL data packets that have been received by the relay UE but have not yet been successfully confirmed by the base station. This assists the remote UE in retransmitting data packets after handover, which can prevent the remote UE from losing data during indirect path handover, achieve lossless data transmission, and ensure the continuity of user services.

[0210] Figure 14 This is a schematic diagram illustrating other embodiments of the relay user terminal disclosed herein. For example... Figure 14 As shown, the relay user terminal of this disclosure may include a second identification information determination module 130 and a second transmission module 140, wherein:

[0211] The second identification information determination module 130 is configured to generate second identification information when receiving indication information sent by a remote user terminal or when a pre-configured trigger condition is met. The second identification information indicates data in the downlink data of the remote user terminal that has been successfully received by the relay user terminal but has not yet been confirmed by the remote user terminal. The downlink is the communication path from the base station to the remote user terminal.

[0212] The second sending module 140 is configured to send second identification information to the base station so that the base station can determine, based on the second identification information, data that was not successfully transmitted to the remote user terminal.

[0213] In some embodiments of this disclosure, the relay user terminal of this disclosure can be configured to perform any of the above embodiments of this disclosure (e.g., Figures 1-3 Any embodiment, Figure 6 The data transmission method described in steps 2-3 of the embodiment.

[0214] The embodiments described above use the RLC status report information reported by the relay UE to determine the DL data packets that have been received by the relay UE but have not yet been successfully confirmed by the remote UE. The auxiliary base station retransmits the data packets after the handover, which can prevent the remote UE from losing data during the indirect path handover, achieve lossless data transmission, and ensure the continuity of user services.

[0215] Figure 15 This is a schematic diagram illustrating some further embodiments of the relay user terminal disclosed herein. For example... Figure 15 As shown, the relay user terminal of this disclosure may include a first identification information determination module 110, a first transmission module 120, a second identification information determination module 130, and a second transmission module 140, wherein:

[0216] The first identification information determination module 110 is configured to generate first identification information when receiving indication information sent by a remote user terminal or when a pre-configured trigger condition is met. The first identification information indicates data in the uplink data of the remote user terminal that has been successfully received by the relay user terminal but has not yet been confirmed by the base station. The uplink is the communication path from the remote user terminal to the base station.

[0217] The first sending module 120 is configured to send the first identification information to a remote user terminal so that the remote user terminal can determine the data that was not successfully transmitted to the base station based on the first identification information.

[0218] The second identification information determination module 130 is configured to generate second identification information when receiving indication information sent by a remote user terminal or when a pre-configured trigger condition is met. The second identification information indicates data in the downlink data of the remote user terminal that has been successfully received by the relay user terminal but has not yet been confirmed by the remote user terminal. The downlink is the communication path from the base station to the remote user terminal.

[0219] The second sending module 140 is configured to send second identification information to the base station so that the base station can determine, based on the second identification information, data that was not successfully transmitted to the remote user terminal.

[0220] In some embodiments of this disclosure, the relay user terminal of this disclosure can be configured to perform any of the above embodiments of this disclosure (e.g., Figures 1-3 Any embodiment, Figure 6 The data transmission method described in steps 2-3 of the embodiment.

[0221] In the embodiments described above, the relay UE generates a first RLC status report and a second RLC status report based on the indication information sent by the remote UE or when the network pre-configured triggering conditions are met. The first RLC status report is used to indicate to the remote UE RLC PDU data that has not yet been acknowledged by the base station, and the second RLC status report is used to indicate to the base station RLC PDU data that has not yet been acknowledged by the remote UE.

[0222] The embodiments described above can use the RLC status report information reported by the relay UE to determine UL / DL data packets that have been received by the relay UE but have not yet been successfully confirmed by the base station / remote UE. This assists the base station / remote UE in retransmitting data packets after handover, which can prevent the remote UE from losing data during indirect path handover, achieve lossless data transmission, and ensure the continuity of user services.

[0223] Figure 16 This is a schematic diagram illustrating some embodiments of the remote user terminal disclosed herein. For example... Figure 16 As shown, the remote user terminal of this disclosure may include a first identification information receiving module 210 and a first data determining module 220, wherein:

[0224] The first identification information receiving module 210 is configured to receive first identification information sent by a relay user terminal. The first identification information indicates data in the uplink data of a remote user terminal that has been successfully received by the relay user terminal but has not yet been confirmed by the base station. The uplink is the communication path from the remote user terminal to the base station. The first identification information is generated by the relay user terminal when it receives indication information sent by the remote user terminal or when a pre-configured trigger condition is met.

[0225] The first data determination module 220 is configured to determine data that was not successfully transmitted to the base station based on the first identification information.

[0226] In some embodiments of this disclosure, the remote user terminal of this disclosure can be configured to execute any of the above embodiments of this disclosure (e.g., Figure 4 Implementation examples Figure 6 The data transmission method described in steps 0-1 and 5 of the embodiment.

[0227] In the embodiments described above, the remote UE sends indication information to the relay UE to request a data transmission status report.

[0228] In the embodiments described above, the remote UE confirms PDCP SDU data packets that were not successfully transmitted to the base station based on the first RLC status report and the PDCP status report received from the target base station.

[0229] The embodiments described above use the RLC status report information reported by the relay UE to determine the UL data packets that have been received by the relay UE but have not yet been successfully confirmed by the base station. This assists the remote UE in retransmitting data packets after handover, which can prevent the remote UE from losing data during indirect path handover, achieve lossless data transmission, and ensure the continuity of user services.

[0230] Figure 17 This is a schematic diagram of some embodiments of the base station disclosed herein. For example... Figure 17 As shown, the base station disclosed herein may include a second identification information receiving module 310 and a second data determining module 320, wherein:

[0231] The second identification information receiving module 310 is configured to receive second identification information sent by a relay user terminal. The second identification information indicates data in the downlink data of a remote user terminal that has been successfully received by the relay user terminal but has not yet been acknowledged by the remote user terminal. The downlink is the communication path from the base station to the remote user terminal. The second identification information is determined by the relay user terminal when it receives an indication message sent by the remote user terminal or when a pre-configured trigger condition is met.

[0232] The second data determination module 320 is configured to determine, based on the second identification information, data that was not successfully transmitted to the remote user terminal.

[0233] In some embodiments of this disclosure, the base station of this disclosure can be configured to perform any of the above embodiments of this disclosure (e.g., Figure 5 Implementation examples Figure 6 The data transmission method described in step 4) of the embodiment.

[0234] According to the above embodiments of this disclosure, the base station determines, based on the second RLC status report, which PDCP SDU data packets should be forwarded to the remote UE under the target base station.

[0235] The embodiments described above use the RLC status report information reported by the relay UE to determine the DL data packets that have been received by the relay UE but have not yet been successfully confirmed by the remote UE. The auxiliary base station retransmits the data packets after the handover, which can prevent the remote UE from losing data during the indirect path handover, achieve lossless data transmission, and ensure the continuity of user services.

[0236] Figure 18 This is a schematic diagram illustrating the structure of some embodiments of the electronic device disclosed herein. For example... Figure 13 As shown, the electronic device includes a memory 91 and a processor 92.

[0237] Memory 91 is used to store instructions, and processor 92 is coupled to memory 91. Processor 92 is configured to execute instructions stored in memory to implement the above embodiments (e.g., Figures 1-6 The data transmission method described in any embodiment.

[0238] In some embodiments of this disclosure, the processor 92 executes any of the above embodiments of this disclosure (e.g. Figure 5 Implementation examples Figure 6 In the case of the data transmission method described in steps 2-3) of the embodiment, the electronic device can be implemented as a relay user terminal.

[0239] In some embodiments of this disclosure, the processor 92 executes any of the above embodiments of this disclosure (e.g. Figure 5 Implementation examples Figure 6 In the case of the data transmission method described in step 4) of the embodiment, the electronic device can be implemented as a base station.

[0240] In some embodiments of this disclosure, the processor 92 executes any of the above embodiments of this disclosure (e.g. Figure 5 Implementation examples Figure 6 In the case of the data transmission method described in steps 0-1 and 5 of the embodiment, the electronic device can be implemented as a remote user terminal.

[0241] like Figure 18 As shown, the electronic device also includes a communication interface 93 for exchanging information with other devices. Additionally, the electronic device includes a bus 94, through which the processor 92, communication interface 93, and memory 91 communicate with each other.

[0242] Memory 91 may include high-speed RAM, and may also include non-volatile memory, such as at least one disk drive. Memory 91 may also be a memory array. Memory 91 may also be divided into blocks, and the blocks may be combined into virtual volumes according to certain rules.

[0243] Furthermore, processor 92 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present disclosure.

[0244] Figure 19 These are schematic diagrams illustrating the structure of some embodiments of the data transmission system disclosed herein. For example... Figure 19 As shown, the data transmission system disclosed herein may include a relay user terminal 100, a remote user terminal 200, and a base station 300, wherein:

[0245] Relay user terminal 100 is as described in any of the above embodiments (e.g.) Figures 13 to 15 The relay user terminal described in any embodiment.

[0246] The remote user terminal 200 is as described in any of the above embodiments (e.g.) Figure 16 The remote user terminal described in the embodiment).

[0247] Base station 300 is as described in any of the above embodiments (e.g.) Figure 17 The base station described in the example).

[0248] According to another aspect of this disclosure, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions that, when executed by a processor, implement any of the embodiments described above (e.g., Figures 1-11 The data transmission method described in any embodiment.

[0249] In some embodiments of this disclosure, the computer-readable storage medium may be a non-transitory computer-readable storage medium.

[0250] Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, apparatus, or computer program products. Therefore, this disclosure can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this disclosure can take the form of a computer program product embodied on one or more computer-usable non-transitory storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0251] This disclosure is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0252] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0253] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0254] The relay user terminal, first identification information determination module, first transmission module, second identification information determination module, second transmission module, remote user terminal, first identification information receiving module, first data determination module, first data retransmission module, base station, second identification information receiving module and second data determination module described above can be implemented as a general-purpose processor, programmable logic controller (PLC), digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component or any suitable combination thereof for performing the functions described in this application.

[0255] This concludes the detailed description of the present disclosure. To avoid obscuring the concept of the disclosure, some details known in the art have not been described. Those skilled in the art will fully understand how to implement the technical solutions disclosed herein based on the above description.

[0256] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware, or by a program instructing the relevant hardware to implement them. The program can be stored in a non-transitory computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0257] The description in this disclosure is provided for illustrative and descriptive purposes only and is not intended to be exhaustive or to limit the disclosure to its forms. Many modifications and variations will be apparent to those skilled in the art. The embodiments were chosen and described in order to better illustrate the principles and practical application of this disclosure and to enable those skilled in the art to understand this disclosure and to design various embodiments with various modifications suitable for a particular purpose.

Claims

1. A data transmission method, comprising: Upon receiving an indication message from a remote user terminal or meeting a pre-configured triggering condition, a first identification message is generated. The first identification message indicates data in the uplink data of the remote user terminal that has been successfully received by the relay user terminal but has not yet been confirmed by the base station. The uplink is the communication path from the remote user terminal to the base station. The first identification information is sent to the remote user terminal so that the remote user terminal can determine the data that was not successfully transmitted to the base station based on the first identification information; Upon receiving an indication message from a remote user terminal or upon meeting a pre-configured triggering condition, a second identification message is generated. The second identification message indicates data in the downlink data of the remote user terminal that has been successfully received by the relay user terminal but has not yet been acknowledged by the remote user terminal. The downlink is the communication path from the base station to the remote user terminal. The second identification information is sent to the base station so that the base station can determine the data that was not successfully transmitted to the remote user terminal based on the second identification information; Sending the first identification information to the remote user terminal includes: Generate a first radio link control status report, wherein the first radio link control status report includes the first identification information; The first identification information is sent to the remote user terminal via the first wireless link control status report.

2. The data transmission method according to claim 1, wherein, Sending the second identification information to the base station includes: Generate a second radio link control status report, wherein the second radio link control status report includes the second identification information; The second identification information is sent to the remote user terminal via the second wireless link control status report.

3. The data transmission method according to claim 1 further includes: The first and second identifier bits in the radio link control status report are used to represent the first identification information or the second identification information. The first identifier bit is used to indicate whether the second identifier bit is enabled. Enabling the second identifier bit indicates that the data packet of the first or second identification information was not successfully transmitted to the final target node. The final target node corresponding to the first identifier information is the base station, and the final target node corresponding to the second identifier information is the remote user terminal. The second identifier bit is also used to indicate whether the relay user terminal received the data packet.

4. The data transmission method according to claim 1, wherein, The indication information sent by the remote user terminal is: The request message sent by the remote user terminal upon receiving the handover command from the source base station; or, When the handover conditions for switching from an indirect path to a direct path or from one indirect path to another are met, the remote user terminal actively sends a handover trigger message. Here, the direct path is the path through which the remote user terminal directly communicates with the base station, and the indirect path is the path through which the remote user terminal communicates with the base station through a relay user terminal. or, Trigger information sent by the remote user terminal when it determines, based on the measurement report, that the current signal quality is below the pre-configured threshold.

5. The data transmission method according to claim 1, wherein, The pre-configured triggering conditions are: meeting a predetermined time interval, or judging from the measurement report that the current signal quality is lower than the pre-configured threshold.

6. A data transmission method applied to a relay UE, comprising: Upon receiving an indication message from a remote user terminal or upon meeting a pre-configured triggering condition, a second identification message is generated. This second identification message indicates data in the downlink data of the remote user terminal that has been successfully received by the relay user terminal but has not yet been acknowledged by the remote user terminal. The downlink is the communication path from the base station to the remote user terminal. The second identification message is fed back through a second radio link control status report. The second identification information is sent to the base station so that the base station can determine the data that was not successfully transmitted to the remote user terminal based on the second identification information.

7. A data transmission method, comprising: The system receives first identification information sent by a relay user terminal, wherein the first identification information indicates data in the uplink data of a remote user terminal that has been successfully received by the relay user terminal but has not yet been confirmed by the base station. The uplink is the communication path from the remote user terminal to the base station. The first identification information is generated by the relay user terminal when it receives an indication information sent by the remote user terminal or when a pre-configured trigger condition is met. The first identification information is fed back through a first radio link control status report. Based on the first identification information, data that was not successfully transmitted to the base station is determined.

8. The data transmission method according to claim 7, further comprising: Resend the data that was not successfully transmitted to the base station.

9. The data transmission method according to claim 8, wherein: The step of determining the data that was not successfully transmitted to the base station based on the first identification information includes: when a remote user terminal switches from a source base station to a target base station, determining the data that was not successfully transmitted to the source base station based on the first identification information and the packet data aggregation protocol report received from the target base station; The retransmission of the data that was not successfully transmitted to the base station includes: when the remote user terminal switches from the source base station to the target base station, retransmitting the data that was not successfully transmitted to the source base station to the target base station.

10. A data transmission method, comprising: The relay user terminal receives second identification information fed back through the second wireless link control status report. The second identification information indicates data in the downlink data of the remote user terminal that has been successfully received by the relay user terminal but has not yet been confirmed by the remote user terminal. The downlink is the communication path from the base station to the remote user terminal. The second identification information is determined by the relay user terminal when it receives the indication information sent by the remote user terminal or when the pre-configured triggering conditions are met. The data that was not successfully transmitted to the remote user terminal is determined based on the second identification information.

11. The data transmission method according to claim 10, further comprising: In the event that the remote user terminal switches from the source base station to the target base station, the data that was not successfully transmitted to the remote user terminal is forwarded to the target base station.

12. A relay user terminal, comprising: The first identification information determination module is configured to generate first identification information when receiving indication information sent by a remote user terminal or when a pre-configured trigger condition is met. The first identification information indicates data in the uplink data of the remote user terminal that has been successfully received by the relay user terminal but has not yet been confirmed by the base station. The uplink is the communication path from the remote user terminal to the base station. The first sending module is configured to send the first identification information to a remote user terminal so that the remote user terminal can determine the data that was not successfully transmitted to the base station based on the first identification information. When receiving an indication message from a remote user terminal or when a pre-configured trigger condition is met, a second identification message is generated. The second identification message indicates data in the downlink data of the remote user terminal that has been successfully received by the relay user terminal but has not yet been confirmed by the remote user terminal. The downlink is the communication path from the base station to the remote user terminal. The second identification information is sent to the base station so that the base station can determine the data that was not successfully transmitted to the remote user terminal based on the second identification information; Sending the first identification information to the remote user terminal includes: Generate a first radio link control status report, wherein the first radio link control status report includes the first identification information; The first identification information is sent to the remote user terminal via the first wireless link control status report.

13. A relay user terminal, comprising: The second identification information determination module is configured to generate second identification information upon receiving indication information sent by a remote user terminal or upon meeting a pre-configured triggering condition. The second identification information indicates data in the downlink data of the remote user terminal that has been successfully received by the relay user terminal but has not yet been acknowledged by the remote user terminal. The downlink is the communication path from the base station to the remote user terminal. The second identification information is fed back through the second wireless link control status report. The second sending module is configured to send second identification information to the base station so that the base station can determine, based on the second identification information, the data that was not successfully transmitted to the remote user terminal.

14. A remote user terminal, comprising: The first identification information receiving module is configured to receive first identification information sent by a relay user terminal. The first identification information indicates data in the uplink data of a remote user terminal that has been successfully received by the relay user terminal but has not yet been confirmed by the base station. The uplink is the communication path from the remote user terminal to the base station. The first identification information is generated by the relay user terminal when it receives indication information sent by the remote user terminal or when a pre-configured trigger condition is met. The first identification information is fed back through a first radio link control status report. The first data determination module is configured to determine data that was not successfully transmitted to the base station based on the first identification information.

15. A base station, comprising: The second identification information receiving module is configured to receive second identification information fed back by the relay user terminal through the second wireless link control status report. The second identification information indicates data in the downlink data of the remote user terminal that has been successfully received by the relay user terminal but has not yet been confirmed by the remote user terminal. The downlink is the communication path from the base station to the remote user terminal. The second identification information is determined by the relay user terminal when it receives the indication information sent by the remote user terminal or when a pre-configured trigger condition is met. The second data determination module is configured to determine, based on the second identification information, data that was not successfully transmitted to the remote user terminal.

16. An electronic device comprising: The memory is configured to store instructions; A processor is configured to execute the instructions, causing the electronic device to perform operations implementing the data transmission method as described in any one of claims 1-11.

17. A data transmission system comprising a relay user terminal as claimed in claim 12 or 13, a remote user terminal as claimed in claim 14, and a base station as claimed in claim 15.

18. A computer-readable storage medium, wherein, The computer-readable storage medium stores computer instructions that, when executed by a processor, implement the data transmission method as described in any one of claims 1-11.