CN109698736B - Repeating data transmission method and device - Google Patents

Repeating data transmission method and device Download PDF

Info

Publication number
CN109698736B
CN109698736B CN201711002557.9A CN201711002557A CN109698736B CN 109698736 B CN109698736 B CN 109698736B CN 201711002557 A CN201711002557 A CN 201711002557A CN 109698736 B CN109698736 B CN 109698736B
Authority
CN
China
Prior art keywords
data
rlc entity
branch
receiving end
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201711002557.9A
Other languages
Chinese (zh)
Other versions
CN109698736A (en
Inventor
李亚娟
池连刚
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Potevio Information Technology Co Ltd
Original Assignee
Potevio Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Potevio Information Technology Co Ltd filed Critical Potevio Information Technology Co Ltd
Priority to CN201711002557.9A priority Critical patent/CN109698736B/en
Publication of CN109698736A publication Critical patent/CN109698736A/en
Application granted granted Critical
Publication of CN109698736B publication Critical patent/CN109698736B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867Arrangements specially adapted for the transmitter end
    • H04L1/189Transmission or retransmission of more than one copy of a message
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607Details of the supervisory signal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867Arrangements specially adapted for the transmitter end
    • H04L1/1896ARQ related signaling
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055Physical resource allocation for ACK/NACK

Abstract

The embodiment of the invention provides a method and a device for transmitting repeated data, wherein the repeated data comprises the following steps: first branch data and second branch data, the method comprising: a first RLC entity of a data sending end receives first feedback information of a third RLC entity of a data receiving end; after receiving the first feedback information, the first RLC entity sends first notification information to a second RLC entity of a data sending end; wherein the first feedback information is used to indicate that the first branch data has been received by the third RLC entity; the first notification information is used to instruct the second RLC entity to stop sending second branch data. The embodiment of the invention can avoid unnecessary retransmission of repeated data and simultaneously improve the reliability of data transmission.

Description

Repeating data transmission method and device
Technical Field
The embodiment of the invention relates to the technical field of communication, in particular to a method and a device for transmitting repeated data.
Background
To meet The increasing demand of people for communication, 5G (The 5)thGeneration) standards have been in the fierce setting. 5G is called NR (New radio) in the 3GPP standard. Since the application scenario of the 5G technology includes a high-reliability Low Latency Communication (URLLC) scenario, which has strict requirements on the reliability and transmission Latency of Data transmission, a Packet Data Convergence Protocol (PDCP) technique is proposed in the 3GPP standard to increase the reliability of Data transmission and shorten the delay of Data transmission.
The PDCP duty is configured by Radio Resource Control (RRC), and one Radio Bearer (RB) corresponds to two Radio Link Control (RLC) entities and two Logical Channels (LCH) to simultaneously process duplicate PDCP PDUs (Packet Data units, PDUs).
The duplicate is to transmit the same PDCP PDU twice, one is transmitted in the original RLC entity (original RLC entity) and the other is transmitted in the additional RLC entity (additional RLC entity), so that the PDCP PDU is transmitted twice. The PDCP duty can be applied to both Carrier Aggregation (CA) mode and Dual Connectivity (DC) mode. The CA mode uses the same Media Access Control (MAC) entity, and the DC mode uses different MAC entities.
FIG. 7 is a diagram illustrating a transmission procedure of a PDCP PDU of the related art. As shown in fig. 7, in the prior art, as in the LTE standard, PDCP PDUs are segmented/packed and headed at the RLC layer and then transferred to the MAC layer, which may contain one or more RLC PDUs. The RLC layer may retransmit the data packet according to the report of the lower layer, and the MAC also has HARQ to increase the transmission times of the data packet, so as to improve the reliability of the data packet transmission.
As can be seen from the above, the conventional PDCP duty technology has the following disadvantages: if one of the two PDCP PDUs sent by the sending end is correctly received by the receiving end, the other PDCP PDU will still be transmitted/retransmitted for the sending end until the other PDCP PDU is also successfully transmitted, resulting in unnecessary retransmission. In addition, if only one MAC entity transmits two PDCP PDUs, the two PDCP PDUs in duplicate may be transmitted in the same MAC PDU, which reduces the reliability of data transmission.
Disclosure of Invention
In order to solve the above disadvantages in the prior art, embodiments of the present invention provide a method and an apparatus for transmitting duplicate data.
In a first aspect, an embodiment of the present invention provides a method for transmitting duplicate data, where the duplicate data includes a first branch data and a second branch data, and the method includes:
a first RLC entity of a data sending end receives first feedback information of a third RLC entity of a data receiving end;
after receiving the first feedback information, the first RLC entity sends first notification information to a second RLC entity of a data sending end;
wherein the first feedback information is used to indicate that the first branch data has been received by the third RLC entity; the first notification information is used to instruct the second RLC entity to stop sending second branch data.
In a second aspect, an embodiment of the present invention further provides a method for transmitting duplicate data, where the duplicate data includes a first branch data and a second branch data, and the method includes:
after receiving the first branch data, a third RLC entity of the data receiving end sends first feedback information to a first RLC entity of the data sending end; and sending second notification information to a fourth RLC entity of the data receiving end;
the fourth RLC entity stops receiving second branch data according to the second notification information;
wherein the first feedback information is used to indicate that the first branch data has been received by the third RLC entity; the second notification information is used to instruct the fourth RLC entity to stop receiving second branch data.
In a third aspect, an embodiment of the present invention provides an electronic device, including: the system comprises a first memory and a first processor, wherein the first processor and the first memory are communicated with each other through a first bus; the first memory stores program instructions executable by the first processor, the first processor invoking the program instructions to perform a method comprising: a first RLC entity of a data sending end receives first feedback information of a third RLC entity of a data receiving end; after receiving the first feedback information, the first RLC entity sends first notification information to a second RLC entity of a data sending end; wherein the first feedback information is used to indicate that the first branch data has been received by the third RLC entity; the first notification information is used to instruct the second RLC entity to stop sending second branch data.
In a fourth aspect, an embodiment of the present invention further provides an electronic device, where the electronic device includes: the second processor and the second memory complete communication with each other through a second bus; the second memory stores program instructions executable by the second processor, the second processor invoking the program instructions to perform the method of: after receiving the first branch data, a third RLC entity of a data receiving end sends first feedback information to a first RLC entity of a data sending end, so that the first RLC entity sends first notification information to a second RLC entity of the data sending end according to the first feedback information; and sending second notification information to a fourth RLC entity of the data receiving end; the fourth RLC entity stops receiving second branch data according to the second notification information; wherein the first feedback information is used to indicate that the first branch data has been received by the third RLC entity; the second notification information is used to instruct the fourth RLC entity to stop receiving second branch data.
In a fifth aspect, an embodiment of the present invention provides a computer readable storage medium, on which a first computer program is stored, where the first computer program, when executed by a processor, implements the following method: a first RLC entity of a data sending end receives first feedback information of a third RLC entity of a data receiving end; after receiving the first feedback information, the first RLC entity sends first notification information to a second RLC entity of a data sending end; wherein the first feedback information is used to indicate that the first branch data has been received by the third RLC entity; the first notification information is used to instruct the second RLC entity to stop sending second branch data.
In a sixth aspect, an embodiment of the present invention provides a computer-readable storage medium, on which a second computer program is stored, where the second computer program, when executed by a processor, implements the following method: after receiving the first branch data, a third RLC entity of the data receiving end sends first feedback information to a first RLC entity of the data sending end; and sending second notification information to a fourth RLC entity of the data receiving end; the fourth RLC entity stops receiving second branch data according to the second notification information; wherein the first feedback information is used to indicate that the first branch data has been received by the third RLC entity; the second notification information is used to instruct the fourth RLC entity to stop receiving second branch data.
According to the method and the device for transmitting the repeated data, provided by the embodiment of the invention, if the sending end and the receiving end of the repeated data know that one branch data of the repeated data is successfully received by the receiving end and the other branch data is not completely transmitted, the PDCP layer or the RLC layer of the sending end and the receiving end informs the RLC entity transmitting the other branch data not to send or receive any more, so that unnecessary retransmission of the repeated data is avoided, and meanwhile, the reliability of data transmission is improved.
Drawings
Fig. 1 is a schematic flowchart of a data repeat transmission method according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of a data repeat transmission method according to another embodiment of the present invention;
fig. 3 is a transmission diagram of configuring a dedicated MAC entity according to an embodiment of the present invention;
fig. 4 is a transmission diagram of sharing the same MAC entity according to an embodiment of the present invention;
fig. 5 is a block diagram of an electronic device according to an embodiment of the present invention;
fig. 6 is a block diagram of an electronic device according to another embodiment of the present invention;
FIG. 7 is a diagram illustrating a conventional PDCP PDU transmission process.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some embodiments, but not all embodiments, of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Fig. 1 is a schematic flowchart of a data repeat transmission method according to an embodiment of the present invention. The repeated data in the embodiment of the present invention includes a first branch data and a second branch data, and as shown in fig. 1, the repeated data transmission method includes the following steps:
s101, a first RLC entity of a data sending end receives first feedback information of a third RLC entity of a data receiving end;
s102, after receiving the first feedback information, the first RLC entity sends first notification information to a second RLC entity of a data sending end;
wherein the first feedback information is used to indicate that the first branch data has been received by the third RLC entity; the first notification information is used to instruct the second RLC entity to stop sending second branch data.
Specifically, if a data sending end (called a sending end for short) is a base station and a data receiving end (called a receiving end for short) is a user terminal, there are two situations: firstly, the first RLC entity and the second RLC entity are both in the same base station, and the base station is carrier aggregation for the terminal; second, the first RLC entity and the second RLC entity are on two different base stations (hereinafter, base station a and base station B) respectively, and base stations a and B are dual-connected for the user terminal. The first RLC entity of the base station A is responsible for sending first branch data to the user terminal, the second RLC entity of the base station B is responsible for sending second branch data to the user terminal, and the third RLC entity of the user terminal is responsible for receiving the first branch data or the second branch data. And when the third RLC entity receives the first branch data, first feedback information is sent to the first RLC entity, the first RLC entity receives the first feedback information, after the first RLC entity learns that the first branch data is received by the third RLC, first notification information is sent to the second RLC entity, the second RLC entity is notified that the repeated data is correctly received by the user terminal, and the second RLC entity stops sending the second branch data after receiving the first notification information, so that unnecessary retransmission is avoided. Wherein the first RLC entity and the second RLC entity communicate over an interface between base station a and base station B. For the case of carrier aggregation, base station a and base station B are actually the same base station, in which case the communication between the first RLC entity and the second RLC entity is the intra-base station communication.
If the sending end is a user terminal and the receiving end is a base station, the first RLC entity and the second RLC entity are both on the RLC layer of the user terminal, the third RLC entity is located in the base station, and other processes are the same as the above processes, which is not described herein again.
It should be noted that all expressions using "first", "second" and "third" in the embodiments of the present invention are used for distinguishing three entities with the same name but different names or different parameters, and it is understood that "first", "second" and "third" are only for convenience of description and should not be construed as limiting the embodiments of the present invention.
In the method for transmitting the repeated data provided by the embodiment of the invention, if the sending end and the receiving end know that one branch data of the repeated data is successfully received by the receiving end and the other branch data is not completely transmitted, the RLC entity which successfully transmits the data informs the RLC entity which transmits the other branch data not to transmit any more; therefore, on the basis of ensuring the reliability of data transmission by adopting the first branch data and the second branch data to transmit the repeated data, unnecessary retransmission in the repeated data transmission is avoided, the time delay of the repeated data transmission is reduced, and the data transmission efficiency between the sending end and the receiving end is improved.
On the basis of the above embodiment, the method comprises the following steps: after receiving the first feedback information, the first RLC entity sends first notification information to a second RLC entity of the data sending end, specifically:
after receiving the first feedback information, the first RLC entity sends first indication information to a first PDCP layer of a data sending end;
the first PDCP layer sends first notification information to a second RLC entity of a data sending end according to the first indication information;
wherein the first indication information is used for indicating that the first branch data is received by a data receiving end.
Specifically, the originating first RLC entity and the second RLC entity communicate through the originating first PDCP layer: a first RLC entity of a transmitting end sends first branch data to a third RLC entity of a receiving end, and the third RLC entity successfully receives the first branch data and sends first feedback information to the first RLC entity; after the first RLC entity receives the first feedback information and learns that the first branch data is received by the third RLC, the first RLC entity sends first indication information to the first PDCP layer to notify the first PDCP layer that the first branch data is received by the receiving end, and then the first PDCP layer sends first notification information to a second RLC entity responsible for sending the second branch data to notify the second RLC entity to stop sending the second branch data.
From the above, it can be seen that: according to the repeated data transmission method provided by the embodiment of the invention, the first branch data and the second branch data are adopted for transmitting the repeated data, and on the premise that the first branch data is correctly transmitted, if the second branch data is not successfully transmitted, the second branch data can not be continuously transmitted for the transmitting end, so that on the basis of ensuring the reliability of data transmission, unnecessary retransmission in repeated data transmission is avoided, and the data transmission efficiency between the transmitting end and the receiving end is improved.
On the basis of the above embodiments, the method further includes: and the second RLC entity receives second feedback information sent by a fourth RLC entity of a data receiving end, wherein the second feedback information is used for indicating that the repeated data is received by the third RLC entity.
Specifically, a first RLC entity of the sending end is configured to send first branch data, and a second RLC entity of the sending end is configured to send second branch data; correspondingly, the third RLC entity of the receiving end is configured to receive the first branch data, and the fourth RLC entity of the receiving end is configured to receive the second branch data. Different from the foregoing embodiment, the second RLC entity of the sending end receives the first notification information of the first RLC entity of the sending end, and also receives the second feedback information of the fourth RLC entity of the receiving end, so as to ensure information peer-to-peer and consistency between the sending end and the receiving end, and implement reliable transmission of repeated data.
It should be noted that all expressions using "first", "second", "third" and "fourth" in the embodiments of the present invention are used for distinguishing four entities with the same name but different names or different parameters, and it is understood that "first", "second", "third" and "fourth" are merely for convenience of description and should not be construed as limitations on the embodiments of the present invention, and the following embodiments do not describe any more.
On the basis of the above embodiment, the method further includes: if the first PDCP layer knows that the working mode of the data sending end is the carrier aggregation CA mode, the media access control MAC layer of the data sending end sends the second branch data in the preconfigured first dedicated MAC entity, so that the media access control MAC layer of the data receiving end receives the second branch data in the preconfigured second dedicated MAC entity.
Specifically, if the originating terminal is a base station, the working mode of the base station includes two modes: carrier aggregation CA mode and dual connectivity DC mode. Generally, the dual connectivity refers to a connection method for providing a service to a user by concentrating radio resources of a plurality of base stations to meet the capacity requirement and coverage requirement of the user because bandwidth resources and coverage of a single base station are limited. The carrier aggregation mode is based on the concentration of radio resources between a plurality of cells of the same base station. Correspondingly, if the originating terminal is a user terminal, if the user terminal has simultaneous connections with multiple (generally 2) base stations, the working mode of the user terminal is a dual connection mode; otherwise, if the user terminal only has connection with one base station at the same time, the user terminal is said to be in the carrier aggregation mode.
If the transmitting end works in the CA mode, in the prior art, the transmitting end uses the same MAC entity to transmit two identical first branch data and second branch data from the RLC entity, so that two identical data packets may be transmitted in the same MAC PDU, and the requirement for improving the reliability of data transmission cannot be met. Therefore, the embodiment of the present invention configures a first dedicated MAC entity for the originating side in advance, and correspondingly configures a second dedicated MAC entity for the terminating side in advance. The first dedicated MAC entity is configured to transmit second branch data of duplicate data, the second dedicated MAC entity is configured to receive second branch data of duplicate data, and the first and second dedicated MAC entities are not configured to transmit other packets of non-duplicate data. At the originating end, the first dedicated MAC entity and the original MAC entity are mapped to the same physical channel. The first dedicated MAC entity may have the same function as the original MAC entity, or may only include partial functions, for example, functions including channel mapping and HARQ (hybrid automatic repeat request), and the configuration of HARQ may be consistent with the original MAC entity, and other functions (such as a scheduling request SR function, a buffer status report BSR function, etc.) may be omitted. At the receiving end, the second dedicated MAC entity and the original MAC entity are mapped to the same physical channel. The second dedicated MAC may have the same function as the original MAC entity, or may only include partial functions, for example, the functions include channel mapping and HARQ (hybrid automatic repeat request), and the configuration of HARQ may be consistent with the original MAC entity, and other functions (such as scheduling request SR function, buffer status report BSR function, etc.) may be omitted.
Therefore, if the first PDCP layer of the transmitting end learns that the transmitting end works in a CA mode, the first branch data is sent to the original MAC entity, and the second branch data is sent to the special MAC entity, so that errors of the first branch data and the second branch data in the transmission of the MAC layer are avoided, and the reliability of repeated data transmission is improved.
It should be added that the dedicated MAC entity exists along with the duplicate data transmission function, and if the duplicate data transmission function is deactivated, the dedicated MAC entity will not transmit data.
On the basis of the above embodiments, the method further includes: and if the first PDCP layer learns that the first branch data and the second branch data are transmitted in the same Media Access Control (MAC) layer in a pre-configuration mode, allocating a first temporary PDCP identifier for the first branch data and allocating a second temporary PDCP identifier for the second branch data so that the Media Access Control (MAC) layer allocates a first MAC PDU for the first branch data and allocates a second MAC PDU for the second branch data.
Specifically, before the first PDCP layer of the originating terminal transmits the duplicate data, the condition of the MAC layer resource allocated by the originating terminal is known, and if the originating terminal pre-configures the first branch data and the second branch data for transmission in the same MAC layer, the first PDCP layer may allocate a temporary PDCP identifier to the first branch data and the second branch data when performing the processes such as packing or heading the first branch data and the second branch data, so that the MAC layer may allocate different MAC PDUs according to the respective temporary PDCP identifiers when receiving the first branch data and the second branch data, thereby using the same MAC layer to transmit the duplicate data without causing transmission failure, and improving reliability of data transmission.
On the basis of the above embodiments, the method further includes: the data sending end sends the activation information of the repeated data to the data receiving end through a first MAC control element so that the data receiving end can carry out repeated data transmission after receiving the activation information; the activation information includes a first PDCP PDU SN parameter, where the first PDCP PDU SN parameter is used to indicate a sequence number of an initial PDCP data packet for synchronous repeated data transmission between the data transmitting end and the data receiving end.
Specifically, before the sending end and the receiving end perform data transmission, in order to enable the sending end and the receiving end to maintain synchronous transceiving, the sending end first sends activation information to the receiving end through an MAC control element (MAC CE for short), where the activation information carries a PDCP PDU SN parameter used to indicate a starting PDCP data packet sequence number in the repeated data, and after receiving the activation information, the receiving end obtains the PDCP PDU SN parameter carried in the MAC CE by analyzing the activation information, and receives the repeated data from the starting PDCP data packet, so as to maintain data transmission synchronization with the sending end, and ensure reliability of data transmission.
On the basis of the above embodiment, the method further includes: the data sending end sends the deactivation information of the repeated data to the data receiving end through a second MAC control element, so that the data receiving end stops repeated data transmission after receiving the deactivation information; wherein the deactivation information includes a second PDCP PDU SN parameter, and the second PDCP PDU SN parameter is used to indicate a sequence number of a terminating PDCP data packet in which the data transmitting end and the data receiving end synchronously stop repeated data transmission.
Specifically, after all data packets in the repeated data are completely transmitted or when the transmission process of the repeated data needs to be stopped, the sending end may send deactivation information to the receiving end through the MAC control element, where the deactivation information carries a PDCP PDU SN parameter used to indicate a termination of a sequence number of a PDCP data packet in the repeated data, and after receiving the deactivation information, the receiving end obtains the PDCP PDU SN parameter carried in the MAC CE by analyzing the deactivation information, so that the receiving of the repeated data is stopped after receiving the termination of the PDCP data packet, and data transmission synchronization is maintained with the sending end, thereby ensuring reliability of data transmission.
Fig. 2 is a flowchart illustrating a data repeat transmission method according to another embodiment of the present invention. As shown in fig. 2, the method comprises the steps of:
s201, after receiving the first branch data, a third RLC entity of a data receiving end sends first feedback information to a first RLC entity of a data sending end, so that the first RLC entity sends first notification information to a second RLC entity of the data sending end according to the first feedback information; and sending second notification information to a fourth RLC entity of the data receiving end;
s202, the fourth RLC entity stops receiving second branch data according to the second notification information;
wherein the first feedback information is used to indicate that the first branch data has been received by the third RLC entity; the second notification information is used to instruct the fourth RLC entity to stop receiving second branch data.
Specifically, the third RLC entity of the receiving end is configured to receive the first branch data sent by the sending end, and the fourth RLC entity of the receiving end is configured to receive the second branch data sent by the sending end; after receiving the first branch data, the third RLC entity sends first feedback information to the first RLC entity of a sending end to inform the first RLC entity, and if the first RLC entity knows that the transmission of the first branch data is finished after receiving the first feedback information, the first RLC entity sends first informing information to the second RLC entity to inform the second RLC entity to stop sending the second branch data; meanwhile, the third RLC entity also sends second notification information to the fourth RLC entity to inform the fourth RLC entity to stop continuously receiving the second branch data; and the fourth RLC entity stops receiving the second branch data after receiving the second notification message.
Therefore, on the premise that the transmission of the first branch data is completed, the third RLC entity of the receiving end informs the second RLC entity of the sending end of stopping sending the second branch data through the first feedback information, and informs the fourth RLC entity of the receiving end of stopping receiving the second branch data through the second notification information, so that the information equality and consistency between the receiving end and the sending end are ensured, unnecessary retransmission in repeated data transmission is avoided, and meanwhile, the reliability of data transmission is ensured.
On the basis of the above embodiment, after receiving the first branch data, the third RLC entity of the data receiving end of the method sends second notification information to the fourth RLC entity of the data receiving end, specifically:
after receiving the first branch data, a third RLC entity of the data receiving end sends second indication information to a second PDCP layer of the data receiving end;
the second PDCP layer sends second notification information to the fourth RLC entity according to the second indication information;
wherein the second indication information is used for indicating that the third RLC entity has received the first branch data.
Specifically, the third RLC entity and the fourth RLC entity of the receiving end communicate through the second PDCP layer of the receiving end: the first RLC entity sends first branch data to a third RLC entity of a receiving end, the third RLC entity sends second indication information to a second PDCP layer after successfully receiving the first branch data to inform the second PDCP layer that the first branch data is received, then the second PDCP layer sends second informing information to a fourth RLC entity which is in charge of receiving the second branch data to inform the fourth RLC entity of stopping receiving the second branch data.
From the above, it can be seen that: according to the repeated data transmission method provided by the embodiment of the invention, the first branch data and the second branch data are adopted to transmit the repeated data, and on the premise that the first branch data is correctly transmitted, if the second branch data is not successfully transmitted, for the receiving end, the second branch data can not be received, so that on the basis of ensuring the reliability of data transmission, unnecessary retransmission in repeated data transmission is avoided, and the data transmission efficiency between the sending end and the receiving end is improved.
On the basis of the above embodiments, the method further includes: and the fourth RLC entity sends second feedback information to a second RLC entity of the repeated sending end, wherein the second feedback information is used for indicating that the repeated data are received by the third RLC entity.
Specifically, a first RLC entity of the sending end is configured to send first branch data, and a second RLC entity of the sending end is configured to send second branch data; correspondingly, the third RLC entity of the receiving end is configured to receive the first branch data, and the fourth RLC entity of the receiving end is configured to receive the second branch data. Different from the foregoing embodiment, the third RLC entity of the receiving end sends the first feedback information to the first RLC entity of the sending end, so that the first RLC entity sends the first notification information to the second RLC entity, and the fourth RLC entity of the receiving end also sends the second feedback information to the second RLC entity of the sending end, thereby ensuring information peer-to-peer and consistency between the sending end and the receiving end, and realizing reliable transmission of repeated data.
In order to better explain the technical solution of the present invention, 3 specific embodiments are provided below, and a specific interaction process between a base station as an originating terminal and a user terminal as a receiving terminal is described as an example:
embodiment 1, the operation mode of the base station is CA mode
Fig. 3 is a transmission diagram of configuring a dedicated MAC entity according to an embodiment of the present invention.
Step one, a base station sends activation (or configuration) information of repeated data to a user equipment (UE for short). The activation information is transmitted by the MAC CE, which includes PDCP PDU SN used for receiving and transmitting both ends synchronization. Optionally, if the activation information does not include the PDCP PDU SN, the user terminal immediately prepares to receive the repeated data after receiving the activation information;
step two, the UE starts a repeated data transmission mode from the PDCP PDU SN, preferably, two branch data of the repeated data are sent by the same PDCP PDU SN, so as to reduce the complexity of data combination at the receiving end;
step three, the base station transmits first branch data through an original MAC entity and transmits second branch data through a pre-configured first special MAC entity; the user terminal receives the first branch data through the original MAC entity and receives the second branch data through the pre-configured second special entity;
and step four, when the first branch data of the sending end is correctly received by the receiving end and the second branch data is not successfully transmitted at the moment, informing the second RLC entity which is not successfully transmitted that the corresponding data is correctly received, and stopping the transmission of the data packet by the second RLC entity at the moment. When the receiving end correctly receives the first branch data, the receiving end internally notifies the fourth RLC entity that the corresponding data is correctly received, thus ensuring the synchronization of the receiving end and the receiving end.
Wherein, the procedure of the PDCP layer responsible for notification is as follows: and (3) originating: after receiving the indication of correct transmission of the first branch data by the first RLC entity, the first PDCP layer notifies the second RLC entity that the repeated data has been successfully received by the receiving end. And (3) receiving: after receiving the indication information of the third RLC entity that the first branch data is correctly received, the second PDCP layer notifies the fourth RLC entity that the repeated data has been correctly received. When the second RLC entity and the fourth RLC entity receive the indication of the correct transmission, they do not continue to transmit and receive the second branch data, and refresh the RLC transmission related parameters, such as the receiving state variable VR, the transmitting state variable VT, and the like.
The RLC layer is responsible for the notification as follows: the difference from the procedure responsible for notification by the PDCP layer is that the other RLC entity is directly notified by the correctly transmitting/receiving RLC entity that the PDCP pdu x has been correctly transmitted/received. For example, the first RLC entity directly notifies the second RLC entity that duplicate data has been correctly transmitted; the third RLC entity directly informs the fourth RLC entity that the duplicate data has been correctly received.
Step five, when the transmission process of the repeated data needs to be stopped, the base station sends deactivation information to the UE, the deactivation information is transmitted through the MAC CE, and the MAC CE comprises PDCP PDU SN so that the receiving and transmitting ends definitely stop transmission when. And if the deactivation information does not contain the PDCP PDU SN, the UE immediately stops receiving after receiving the deactivation information.
Embodiment 2, pre-configuring to transmit in the same MAC entity
Fig. 4 is a transmission diagram of sharing the same MAC entity according to an embodiment of the present invention.
Difference between example 2 and example 1: the base station and the user terminal do not need to be pre-configured with special MAC entities, and two branches of repeated data are supported to be transmitted in the same MAC layer, namely the same MAC entity is used. The specific process is as follows: the first PDCP layer of the base station adds a temporary identifier to the PDCP PDU so as to ensure that the RLC entity of the RLC layer confirms the corresponding relation between the two branch data of the repeated data and the MAC entity distributes different MAC PDUs for the two branch data, and the MAC entity is prevented from putting the two branch data in the same MAC PDU. The rest of the procedure is the same as in example 1 and will not be described here.
Embodiment 3, the operation mode of the base station is a dual connection mode
When the base station works in the dual connectivity mode, since the MAC layer may use different MAC entities to transmit the first branch data and the second branch data, that is, it is not necessary to pre-configure a dedicated MAC entity, and it is also not necessary to allocate temporary PDCP identifiers for the first branch data and the second branch data in the PDCP layer, the procedure of the MAC layer is the same as the procedure after configuring the dedicated MAC entity, and details are not repeated here.
Fig. 5 is a block diagram of an electronic device according to an embodiment of the present invention. As shown in fig. 5, the electronic apparatus includes: a first memory 502 and a first processor 501, wherein the first processor 501 and the first memory 502 are communicated with each other through a first bus 503; the first memory 502 stores program instructions executable by the processor, which the first processor 501 calls to perform a method, for example comprising: a first RLC entity of a data sending end receives first feedback information of a third RLC entity of a data receiving end; after receiving the first feedback information, the first RLC entity sends first notification information to a second RLC entity of a data sending end; wherein the first feedback information is used to indicate that the first branch data has been received by the third RLC entity; the first notification information is used to instruct the second RLC entity to stop sending second branch data.
Fig. 6 is a block diagram of an electronic device according to another embodiment of the present invention. As shown in fig. 6, the electronic apparatus includes: a second memory 602 and a second processor 601, wherein the second processor 601 and the second memory 602 complete communication with each other through a second bus 603; the second memory 602 stores program instructions executable by the processor, and the second processor 601 calling the program instructions is capable of performing a method, for example, comprising: after receiving the first branch data, a third RLC entity of a data receiving end sends first feedback information to a first RLC entity of a data sending end, so that the first RLC entity sends first notification information to a second RLC entity of the data sending end according to the first feedback information; and sending second notification information to a fourth RLC entity of the data receiving end; the fourth RLC entity stops receiving second branch data according to the second notification information; wherein the first feedback information is used to indicate that the first branch data has been received by the third RLC entity; the second notification information is used to instruct the fourth RLC entity to stop receiving second branch data.
Embodiments of the present invention also provide a computer first program product, the computer first program product comprising a first computer program stored on a non-transitory computer readable storage medium, the first computer program comprising program instructions, which when executed by a computer, enable the computer to perform the method provided by the above-mentioned method embodiments, for example, including: a first RLC entity of a data sending end receives first feedback information of a third RLC entity of a data receiving end; after receiving the first feedback information, the first RLC entity sends first notification information to a second RLC entity of a data sending end; wherein the first feedback information is used to indicate that the first branch data has been received by the third RLC entity; the first notification information is used to instruct the second RLC entity to stop sending second branch data.
Embodiments of the present invention also provide a second computer program product, which includes a second computer program stored on a non-transitory computer-readable storage medium, where the second computer program includes program instructions, and when the program instructions are executed by a computer, the computer can execute the method provided by the above-mentioned method embodiments, for example, including: after receiving the first branch data, a third RLC entity of a data receiving end sends first feedback information to a first RLC entity of a data sending end, so that the first RLC entity sends first notification information to a second RLC entity of the data sending end according to the first feedback information; and sending second notification information to a fourth RLC entity of the data receiving end; the fourth RLC entity stops receiving second branch data according to the second notification information; wherein the first feedback information is used to indicate that the first branch data has been received by the third RLC entity; the second notification information is used to instruct the fourth RLC entity to stop receiving second branch data.
An embodiment of the present invention further provides a first computer-readable storage medium, where the first computer-readable storage medium stores a first computer program, and the first computer program causes the computer to execute the method provided in each of the above method embodiments, for example, the method includes: a first RLC entity of a data sending end receives first feedback information of a third RLC entity of a data receiving end; after receiving the first feedback information, the first RLC entity sends first notification information to a second RLC entity of a data sending end; wherein the first feedback information is used to indicate that the first branch data has been received by the third RLC entity; the first notification information is used to instruct the second RLC entity to stop sending second branch data.
An embodiment of the present invention further provides a second computer-readable storage medium, where the second computer-readable storage medium stores a second computer program, and the second computer program enables the computer to execute the methods provided in the foregoing method embodiments, for example, the method includes: after receiving the first branch data, a third RLC entity of a data receiving end sends first feedback information to a first RLC entity of a data sending end, so that the first RLC entity sends first notification information to a second RLC entity of the data sending end according to the first feedback information; and sending second notification information to a fourth RLC entity of the data receiving end; the fourth RLC entity stops receiving second branch data according to the second notification information; wherein the first feedback information is used to indicate that the first branch data has been received by the third RLC entity; the second notification information is used to instruct the fourth RLC entity to stop receiving second branch data.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.

Claims (12)

1. A method of data transfer of duplicate data, wherein the duplicate data includes a first branch data and a second branch data, the method comprising:
a first RLC entity of a data sending end receives first feedback information of a third RLC entity of a data receiving end;
after receiving the first feedback information, the first RLC entity sends first notification information to a second RLC entity of a data sending end;
wherein the first feedback information is used to indicate that the first branch data has been received by the third RLC entity; the first notification information is used for indicating the second RLC entity to stop sending second branch data;
the first branch data is a repeated PDCP packet data unit sent to a first RLC entity, and the second branch data is a repeated PDCP packet data unit sent to a second RLC entity;
if the data sending end is a base station and the data receiving end is a user terminal, the first RLC entity and the second RLC entity are located in the base station; if the data sending end is a user terminal and the data receiving end is a base station, the first RLC entity and the second RLC entity are located at the user terminal;
the third RLC entity is located at a data receiving end, and is configured to receive the first branch data or the second branch data.
2. The method of claim 1, wherein after receiving the first feedback information, the first RLC entity sends first notification information to a second RLC entity of a data sending end, specifically:
after receiving the first feedback information, the first RLC entity sends first indication information to a first PDCP layer of a data sending end;
the first PDCP layer sends first notification information to a second RLC entity of a data sending end according to the first indication information;
wherein the first indication information is used for indicating that the first branch data is received by a data receiving end.
3. The method of claim 1, further comprising:
and the second RLC entity receives second feedback information sent by a fourth RLC entity of a data receiving end, wherein the second feedback information is used for indicating that the repeated data is received by the third RLC entity.
4. The method of claim 1, further comprising:
if the first PDCP layer knows that the working mode of the data sending end is the carrier aggregation CA mode, the media access control MAC layer of the data sending end sends the second branch data in the preconfigured first dedicated MAC entity, so that the media access control MAC layer of the data receiving end receives the second branch data in the preconfigured second dedicated MAC entity.
5. The method of claim 1, further comprising:
and if the first PDCP layer learns that the first branch data and the second branch data are transmitted in the same Media Access Control (MAC) layer in a pre-configuration mode, allocating a first temporary PDCP identifier for the first branch data and allocating a second temporary PDCP identifier for the second branch data so that the Media Access Control (MAC) layer allocates a first MAC PDU for the first branch data and allocates a second MAC PDU for the second branch data.
6. The method of any of claims 1-5, further comprising:
the data sending end sends the activation information of the repeated data to the data receiving end through a first MAC control element so that the data receiving end can carry out repeated data transmission after receiving the activation information;
the activation information includes a first PDCP PDU SN parameter, where the first PDCP PDU SN parameter is used to indicate a sequence number of an initial PDCP data packet for synchronous repeated data transmission between the data transmitting end and the data receiving end.
7. The method of claim 6, further comprising:
the data sending end sends the deactivation information of the repeated data to the data receiving end through a second MAC control element, so that the data receiving end stops repeated data transmission after receiving the deactivation information;
wherein the deactivation information includes a second PDCP PDU SN parameter, and the second PDCP PDU SN parameter is used to indicate a sequence number of a terminating PDCP data packet in which the data transmitting end and the data receiving end synchronously stop repeated data transmission.
8. A method of data transfer of duplicate data, wherein the duplicate data includes a first branch data and a second branch data, the method comprising:
after receiving the first branch data, a third RLC entity of a data receiving end sends first feedback information to a first RLC entity of a data sending end, so that the first RLC entity sends first notification information to a second RLC entity of the data sending end according to the first feedback information; and sending second notification information to a fourth RLC entity of the data receiving end;
the fourth RLC entity stops receiving second branch data according to the second notification information;
wherein the first feedback information is used to indicate that the first branch data has been received by the third RLC entity; the second notification information is used for indicating the fourth RLC entity to stop receiving second branch data;
the first branch data is a repeated PDCP packet data unit sent to a first RLC entity, and the second branch data is a repeated PDCP packet data unit sent to a second RLC entity;
if the data sending end is a base station and the data receiving end is a user terminal, the first RLC entity and the second RLC entity are located in the base station; if the data sending end is a user terminal and the data receiving end is a base station, the first RLC entity and the second RLC entity are located at the user terminal;
the third RLC entity and the fourth RLC entity are located at a data receiving end, the third RLC entity is configured to receive the first branch data, and the fourth RLC entity is configured to receive the second branch data;
the first notification information is used to instruct the second RLC entity to stop sending second branch data.
9. The method of claim 8, wherein after receiving the first branch data, a third RLC entity at the data receiving end sends second notification information to a fourth RLC entity at the data receiving end, specifically:
after receiving the first branch data, a third RLC entity of the data receiving end sends second indication information to a second PDCP layer of the data receiving end;
the second PDCP layer sends second notification information to the fourth RLC entity according to the second indication information;
wherein the second indication information is used for indicating that the third RLC entity has received the first branch data.
10. The method of claim 8 or 9, further comprising:
and the fourth RLC entity sends second feedback information to a second RLC entity of the data sending end, wherein the second feedback information is used for indicating that the repeated data are received by the third RLC entity.
11. An electronic device, comprising:
the processor and the memory are communicated with each other through a bus; the memory stores program instructions executable by the processor, the processor invoking the program instructions to perform the method of any of claims 1 to 10.
12. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1 to 10.
CN201711002557.9A 2017-10-24 2017-10-24 Repeating data transmission method and device Active CN109698736B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201711002557.9A CN109698736B (en) 2017-10-24 2017-10-24 Repeating data transmission method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201711002557.9A CN109698736B (en) 2017-10-24 2017-10-24 Repeating data transmission method and device

Publications (2)

Publication Number Publication Date
CN109698736A CN109698736A (en) 2019-04-30
CN109698736B true CN109698736B (en) 2021-08-06

Family

ID=66228109

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201711002557.9A Active CN109698736B (en) 2017-10-24 2017-10-24 Repeating data transmission method and device

Country Status (1)

Country Link
CN (1) CN109698736B (en)

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102611537A (en) * 2011-01-25 2012-07-25 华为技术有限公司 Retransmission method and retransmission device of data package
CN102801502A (en) * 2012-08-31 2012-11-28 哈尔滨工业大学 Packet loss method in LTE and LTE-A system based on RED algorithm
CN103888222A (en) * 2014-03-21 2014-06-25 电信科学技术研究院 Data packet processing method and device
CN104184553A (en) * 2014-09-02 2014-12-03 广东欧珀移动通信有限公司 Low-power-dissipation Bluetooth data transmission method, device and equipment
CN104935414A (en) * 2014-03-21 2015-09-23 上海贝尔股份有限公司 Method for transmitting information in dual connection system and device
CN106559183A (en) * 2015-09-25 2017-04-05 普天信息技术有限公司 Data transmission method, device and system
CN107147479A (en) * 2017-04-27 2017-09-08 电信科学技术研究院 A kind of method and apparatus for carrying out repeating transmission control
CN107241164A (en) * 2017-05-05 2017-10-10 电信科学技术研究院 A kind of radio bearer repeats the processing method and processing device of transmission

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150305041A1 (en) * 2014-04-16 2015-10-22 Electronics And Telecommunications Research Institute Method and apparatus for providing service using radio resource aggregation
US9906332B2 (en) * 2015-05-29 2018-02-27 Apple Inc. Radio link control recovery based on medium access feedback
US11382081B2 (en) * 2015-10-16 2022-07-05 Samsung Electronics Co., Ltd. Method and apparatus for system information acquisition in wireless communication system
US11032031B2 (en) * 2016-01-18 2021-06-08 Qualcomm Incorporated HARQ LLR buffer and reordering buffer management

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102611537A (en) * 2011-01-25 2012-07-25 华为技术有限公司 Retransmission method and retransmission device of data package
CN102801502A (en) * 2012-08-31 2012-11-28 哈尔滨工业大学 Packet loss method in LTE and LTE-A system based on RED algorithm
CN103888222A (en) * 2014-03-21 2014-06-25 电信科学技术研究院 Data packet processing method and device
CN104935414A (en) * 2014-03-21 2015-09-23 上海贝尔股份有限公司 Method for transmitting information in dual connection system and device
CN104184553A (en) * 2014-09-02 2014-12-03 广东欧珀移动通信有限公司 Low-power-dissipation Bluetooth data transmission method, device and equipment
CN106559183A (en) * 2015-09-25 2017-04-05 普天信息技术有限公司 Data transmission method, device and system
CN107147479A (en) * 2017-04-27 2017-09-08 电信科学技术研究院 A kind of method and apparatus for carrying out repeating transmission control
CN107241164A (en) * 2017-05-05 2017-10-10 电信科学技术研究院 A kind of radio bearer repeats the processing method and processing device of transmission

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
Feedback for PDCP duplication;Fujitsu;《3GPP R2-1706563》;20170616;全文 *
LTE-Advanced系统中异构网双连接关键技术的研究;李先栋;《中国优秀硕士学位论文全文数据库信息科技辑》;20150831;全文 *
Technical Specification Group Radio Access Network;佚名;《3GPP R2-1710693 38300-101》;20170929;全文 *

Also Published As

Publication number Publication date
CN109698736A (en) 2019-04-30

Similar Documents

Publication Publication Date Title
CN111357387B (en) Multi-connection method and related device
CN107667559B (en) Apparatus and method for providing multiple connections using different radio connection technologies in a wireless communication system
CN110603803B (en) Method and apparatus for communication between network entities in a cloud local area network environment
JP7279778B2 (en) Side link data transmission and setting method and device
US11844147B2 (en) Method and apparatus for resource allocation for network coordination
WO2017054633A1 (en) Resource allocation method, apparatus, and wireless access system
CN106992846B (en) Data sending method, data receiving method and device
EP3637846B1 (en) Method and device for use in configuring novel quality of service architecture in dual connectivity system
EP3989674A1 (en) Methods and devices for network access
WO2016192517A1 (en) Radio frequency processing device and processing method
JP2018510548A (en) RLC data packet offload method and base station
US20230224914A1 (en) Method and Apparatus for Configuring Transmission Time Interval, Data Transmission Method and Apparatus and System
CN111713134B (en) Method and apparatus for efficient operation upon packet repetition activation and deactivation in next generation wireless communication systems
WO2020119013A1 (en) Sidelink communication method and apparatus
WO2022110188A1 (en) Sidelink carrier management method, apparatus and system
US11197223B2 (en) Method and apparatus for determining transmission path of packet in wireless communication
EP3534662B1 (en) Bearer configuration method and related product
JP2023505642A (en) Information transmission method and related products
CN109698736B (en) Repeating data transmission method and device
WO2019082319A1 (en) Wireless communication system, base station, mobile station, and wireless communication method
KR102129026B1 (en) A method and system for switching and synchronizing grant intervals in adaptive grant and polling service
CN116349259A (en) Communication method and device
WO2023202660A1 (en) Method for communication across distributed units (dus), and related apparatus
WO2022105925A1 (en) Transmission method, notification method, transmission unit, and network-side device
CN112152764B (en) Method for reporting repeated transmission activation state, method for confirming repeated transmission activation state and related equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant