CN109428684B - Data transmission method, RLC entity and PDCP entity - Google Patents

Data transmission method, RLC entity and PDCP entity Download PDF

Info

Publication number
CN109428684B
CN109428684B CN201710762133.6A CN201710762133A CN109428684B CN 109428684 B CN109428684 B CN 109428684B CN 201710762133 A CN201710762133 A CN 201710762133A CN 109428684 B CN109428684 B CN 109428684B
Authority
CN
China
Prior art keywords
rlc
pdcp
entity
identification information
identification
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
CN201710762133.6A
Other languages
Chinese (zh)
Other versions
CN109428684A (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.)
China Mobile Communications Group Co Ltd
China Mobile Communications Ltd Research Institute
Original Assignee
China Mobile Communications Group Co Ltd
China Mobile Communications Ltd Research Institute
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 China Mobile Communications Group Co Ltd, China Mobile Communications Ltd Research Institute filed Critical China Mobile Communications Group Co Ltd
Priority to CN201710762133.6A priority Critical patent/CN109428684B/en
Priority to PCT/CN2018/095963 priority patent/WO2019042032A1/en
Publication of CN109428684A publication Critical patent/CN109428684A/en
Application granted granted Critical
Publication of CN109428684B publication Critical patent/CN109428684B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements 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/1607—Details of the supervisory signal
    • H04L1/1671—Details of the supervisory signal the supervisory signal being transmitted together with control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

The invention provides a data transmission method, an RLC entity and a PDCP entity, wherein the data transmission method comprises the following steps: and sending RLC SDU to a PDCP entity of a receiving end, wherein the RLC SDU carries RLC identification information of the RLC SDU, and the RLC identification information is used for the PDCP entity to determine the RLC SDU successfully sent by the RLC entity. The scheme of the invention can facilitate the PDCP entity of the receiving end to determine the RLC SDU which is successfully sent and feed back the RLC entity of the receiving end, thereby ensuring that the PDCP entity of the receiving end correctly receives data.

Description

Data transmission method, RLC entity and PDCP entity
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a data transmission method, an RLC entity, and a PDCP entity.
Background
Currently, according to the 3rd Generation Partnership Project (3 GPP) related standard, the partition manner of the Central Unit (CU) and Distributed Unit (DU) architecture protocol stack function is as follows: the Packet Data Convergence Protocol (PDCP) layer and the Radio Link Control (RLC) layer are partitioned, that is, the Protocol stack functions of the PDCP layer and the RLC layer are implemented on the CU and the DU, respectively. Meanwhile, the 3GPP standard has determined that there is an interface between the CU and DU on the network side, which is named F1 interface.
Since the protocol stack functions of the PDCP layer and the RLC layer are implemented in the CU and the DU, respectively, and an interface exists between the CU and the DU on the network side, when the RLC layer of the receiving end (on the network side) sends RLC SDUs to the PDCP layer of the receiving end, an F1 interface is needed, and packet loss may occur during interface transmission, so that it is not possible to ensure correct data reception of the PDCP layer of the receiving end.
Disclosure of Invention
The embodiment of the invention provides a data transmission method, an RLC entity and a PDCP entity, aiming at solving the problem that the traditional PDCP entity at a receiving end can not receive data correctly.
In a first aspect, an embodiment of the present invention provides a data transmission method, which is applied to an RLC entity at a receiving end, and includes:
and sending RLC SDU to a PDCP entity of a receiving end, wherein the RLC SDU carries RLC identification information of the RLC SDU, and the RLC identification information is used for the PDCP entity to determine the RLC SDU successfully sent by the RLC entity.
Optionally, after sending RLC SDU to PDCP entity of the receiving end, the method further includes:
receiving identification report information sent by the PDCP entity, wherein the identification report information carries RLC identification information associated with PDCP identification information corresponding to the PDCP PDU received by the PDCP entity;
judging whether a lost RLC SDU exists in the transmission process of the RLC SDU according to the identification report information;
if the RLC SDU is lost, determining RLC identification information of the lost RLC SDU;
acquiring RLC PDU corresponding to the RLC identification information of the lost RLC SDU;
retransmitting the RLC PDU to the PDCP entity.
Optionally, the acquiring the RLC PDU corresponding to the RLC identification information of the lost RLC SDU includes:
triggering a status report process and sending status report information to an RLC entity of a sending end, wherein the status report information carries RLC identification information of the lost RLC SDU;
and receiving the RLC PDU which is sent by the RLC entity of the sending end and corresponds to the RLC identification information of the lost RLC SDU.
Optionally, the acquiring the RLC PDU corresponding to the RLC identification information of the lost RLC SDU includes:
and selecting the RLC PDU corresponding to the RLC identification information of the lost RLC SDU from backup data, wherein the RLC PDU received from an RLC entity of a sending end is stored in the backup data.
Optionally, after receiving the identification report information sent by the PDCP entity, the method further includes:
acquiring RLC identification information carried in the identification report information;
and deleting the RLC PDU corresponding to the acquired RLC identification information in the backup data, wherein the RLC PDU received from the RLC entity of the sending end is stored in the backup data.
Optionally, the identification information is a serial number.
In a second aspect, an embodiment of the present invention further provides a data transmission method, which is applied to a PDCP entity at a receiving end, and includes:
receiving RLC SDU sent by an RLC entity of a receiving end, wherein the RLC SDU carries RLC identification information of the RLC SDU, and the RLC identification information is used for the PDCP entity to determine the RLC SDU successfully sent by the RLC entity.
Optionally, after receiving the RLC SDU sent by the RLC entity of the receiving end, the method further includes:
associating PDCP identification information with the RLC identification information;
generating identification report information, wherein the identification report information carries RLC identification information associated with PDCP identification information corresponding to the PDCP PDU received by the PDCP entity;
sending the identification report information to the RLC entity;
and receiving the RLC PDU retransmitted by the RLC entity and corresponding to the RLC identification information of the lost RLC SDU.
Optionally, the identification information is a serial number, and the generating identification report information includes:
triggering a reception timer using a predetermined PDCP sequence number;
if the PDCP PDU carrying the predetermined PDCP sequence number is received within the time length of the receiving timer, generating the identification report information, wherein the identification report information carries an RLC sequence number associated with the predetermined PDCP sequence number;
if the PDCP PDU carrying the predetermined PDCP sequence number is not received when the receiving timer is overtime, but at least one PDCP PDU which carries other predetermined PDCP sequence numbers and is positioned behind and continuous with the PDCP PDU carrying the predetermined PDCP sequence number is received, the identification report information is sequentially generated according to the ascending order of the at least one other predetermined PDCP sequence number, wherein the identification report information carries RLC sequence numbers which are associated with the other predetermined PDCP sequence numbers;
wherein, the state variable of the receiving timer is the predetermined PDCP sequence number, and the state variable of the receiving timer is increased by 1 after generating the identification report information each time or after the receiving timer is overtime.
In a third aspect, an embodiment of the present invention further provides an RLC entity, which is applied to a receiving end, and includes a processor, a sending interface, and a receiving interface;
the processor is configured to determine RLC identification information of an RLC SDU sent by the RLC entity;
the sending interface is used for sending RLC SDU to a PDCP entity of a receiving end, wherein the RLC SDU carries RLC identification information of the RLC SDU, and the RLC identification information is used for the PDCP entity to determine the RLC SDU successfully sent by the RLC entity.
Optionally, the receiving interface is configured to receive identification report information sent by the PDCP entity, where the identification report information carries RLC identification information associated with PDCP identification information corresponding to a PDCP PDU received by the PDCP entity;
the processor is further configured to determine whether a missing RLC SDU exists in the transmission process of the RLC SDU according to the identification report information, determine RLC identification information of the missing RLC SDU when the missing RLC SDU exists, and acquire an RLC PDU corresponding to the RLC identification information of the missing RLC SDU;
the transmitting interface is further configured to retransmit the RLC PDU to the PDCP entity.
Optionally, the processor is further configured to trigger a status reporting procedure;
the sending interface is further configured to send status report information to an RLC entity of a sending end, where the status report information carries RLC identification information of the lost RLC SDU;
the receiving interface is further configured to receive an RLC PDU sent by the RLC entity of the sending end and corresponding to the RLC identification information of the missing RLC SDU.
Optionally, the processor is further configured to select an RLC PDU corresponding to the RLC identification information of the lost RLC SDU from backup data, where the RLC PDU received from an RLC entity of the sending end is stored in the backup data.
Optionally, the processor is further configured to obtain RLC identification information carried in the identification report information, and delete an RLC PDU corresponding to the obtained RLC identification information in backup data, where the RLC PDU received from an RLC entity of the sending end is stored in the backup data.
Optionally, the identification information is a serial number.
In a fourth aspect, an embodiment of the present invention further provides a PDCP entity, which is applied to a receiving end and includes a processor, a sending interface, and a receiving interface;
the receiving interface is used for receiving RLC SDU sent by an RLC entity of a receiving end, wherein the RLC SDU carries RLC identification information of the RLC SDU, and the RLC identification information is used for the PDCP entity to determine the RLC SDU successfully sent by the RLC entity.
Optionally, the processor is configured to associate PDCP identification information with the RLC identification information, and generate identification report information, where the identification report information carries RLC identification information associated with PDCP identification information corresponding to a PDCP PDU received by the PDCP entity;
the sending interface is used for sending the identification report information to the RLC entity;
the receiving interface is further configured to receive an RLC PDU retransmitted by the RLC entity and corresponding to RLC identification information of the missing RLC SDU.
Optionally, the processor is further configured to trigger a receive timer using a predetermined PDCP sequence number; when receiving the PDCP PDU carrying the predetermined PDCP sequence number within the duration of the receiving timer, generating the identification report information, wherein the identification report information carries an RLC sequence number associated with the predetermined PDCP sequence number; or, when the PDCP PDU carrying the predetermined PDCP sequence number is not received when the receiving timer expires, but at least one PDCP PDU carrying another predetermined PDCP sequence number is received after and consecutive PDCP PDUs carrying the predetermined PDCP sequence number, sequentially generating the identification report information according to an ascending order of the at least one other predetermined PDCP sequence number, where the identification report information carries RLC sequence numbers associated with the other predetermined PDCP sequence numbers;
wherein, the state variable of the receiving timer is the predetermined PDCP sequence number, and the state variable of the receiving timer is increased by 1 after generating the identification report information each time or after the receiving timer is overtime.
In a fifth aspect, an embodiment of the present invention further provides a receiving end, including a memory, a processor, and a data transmission program stored on the memory and executable on the processor, where the data transmission program, when executed by the processor, implements the steps in the data transmission method applied to the receiving end.
In a sixth aspect, an embodiment of the present invention further provides a computer-readable storage medium, on which a data transmission program is stored, where the data transmission program, when executed by a processor, implements the steps in the data transmission method applied to the receiving end.
In the data transmission method of the embodiment of the invention, the RLC SDU is sent to the PDCP entity of the receiving end, and the RLC identification information is used for the PDCP entity to determine the RLC SDU successfully sent by the RLC entity because the RLC SDU carries the RLC identification information of the RLC SDU, so that the PDCP entity of the receiving end can conveniently determine the RLC SDU successfully sent and feed back the RLC SDU to the RLC entity of the receiving end, thereby ensuring that the PDCP entity of the receiving end can correctly receive data.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required to be used in the embodiments of the present invention will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive labor.
FIG. 1 is a flow chart of a data transmission method according to an embodiment of the invention;
FIG. 2 is a flow chart of another data transmission method according to an embodiment of the present invention;
FIG. 3 is a flow chart of a further data transmission method according to an embodiment of the invention;
FIG. 4 is a diagram illustrating an RLC entity according to an embodiment of the present invention;
FIG. 5 is a diagram illustrating a PDCP entity according to an embodiment of the present invention;
fig. 6 is a schematic structural diagram of a receiving end according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, 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.
Referring to fig. 1, an embodiment of the present invention provides a data transmission method, which is applied to an RLC entity at a receiving end, and includes the following steps:
step 101: and sending the RLC SDU to a PDCP entity of a receiving end.
The RLC SDU (service data unit) carries RLC identification information of the RLC SDU, and the RLC identification information is used by the PDCP entity to determine the RLC SDU successfully sent by the RLC entity. Specifically, the identification information may be a serial number.
It should be noted that, a scenario in which the embodiment of the present invention is applied is that a terminal transmits data to a network side device, and a related receiving end is specifically the network side device. Since there is an interface (F1 interface) between the CU and the DU of the network side device, when the network side device is used as a receiving end, the RLC entity of the network side device needs to pass through the F1 interface in the process of sending RLC SDU (i.e. PDCP PDU) to the PDCP entity, and since packet loss may occur during the transmission process of the F1 interface, the RLC SDU to be transmitted is lost, so that the PDCP entity cannot receive data correctly.
In the data transmission method of the embodiment of the invention, the RLC SDU is sent to the PDCP entity of the receiving end, and the RLC identification information is used for the PDCP entity to determine the RLC SDU successfully sent by the RLC entity because the RLC SDU carries the RLC identification information of the RLC SDU, so that the PDCP entity of the receiving end can conveniently determine the RLC SDU successfully sent and feed back the RLC SDU to the RLC entity of the receiving end, thereby ensuring that the PDCP entity of the receiving end can correctly receive data.
In the embodiment of the invention, in order to further ensure that the PDCP entity correctly receives data, the RLC entity of the receiving end can retransmit the missing RLC SDU to the PDCP entity of the receiving end under the condition that the missing RLC SDU exists. Specifically, referring to fig. 2, after step 101, the data transmission method may further include the following steps:
step 102: and receiving the identification report information sent by the PDCP entity of the receiving end.
The identification report information carries RLC identification information associated with PDCP identification information corresponding to a PDCP PDU (Protocol Data Unit) received by the PDCP entity. In this way, the RLC SDU successfully transmitted by the RLC entity can be determined by the identification report information. The RLC SDU sent by the RLC entity is the PDCP PDU received by the PDCP entity and is called in different ways in the RLC entity and the PDCP entity.
Step 103: and judging whether the RLC SDU is lost in the transmission process of the RLC SDU or not according to the identification report information.
The manner of determining whether there is a missing RLC SDU in the RLC SDU transmission process according to the identifier report information may be: and comparing the RLC identification information carried in the identification report information with the RLC identification information of the RLC SDU which is sent, wherein if the RLC identification information which is not carried by the identification report information exists, the RLC SDU corresponding to the RLC identification information which is not carried is the lost (sending failure) RLC SDU. The missing RLC SDU may be lost during transmission over the air interface and F1 interface.
Step 104: and if the RLC SDU is lost, determining the RLC identification information of the lost RLC SDU.
Step 105: and acquiring the RLC PDU corresponding to the RLC identification information of the lost RLC SDU.
The RLC PDU obtained in step 105 is the retransmission data. The RLC SDU is subjected to packet header processing and the like to obtain corresponding RLC PDU.
Step 106: retransmitting the RLC PDU to the PDCP entity.
Thus, the correct data reception of the PDCP entity can be further ensured through the data retransmission process.
In the embodiment of the present invention, when acquiring the retransmission data, the RLC entity at the receiving end may be acquired in at least the following two manners, which are described in detail below.
In a first mode
In this way, the RLC entity of the receiving end acquires retransmission data from the RLC entity of the transmitting end through a status report procedure. Specifically, step 105 may include:
the RLC entity of the receiving end triggers a status report process and sends status report information to the RLC entity of the transmitting end, wherein the status report information carries RLC identification information of the lost RLC SDU;
and the RLC entity of the receiving end receives the RLC PDU which is sent by the RLC entity of the sending end and corresponds to the RLC identification information of the lost RLC SDU.
Wherein, the RLC entity at the receiving end directly triggers the status report process when determining that there is a missing RLC SDU. If the RLC identification information is the RLC sequence number, the RLC entity of the receiving end may add the RLC sequence number of the missing RLC SDU to a sequence number list in the status report information to be sent, so as to reacquire the missing RLC SDU.
In the prior art, when data is reacquired from a sending end, an Automatic Repeat-reQuest (ARQ) process is needed, and the feedback of the ARQ process is too slow, so that the embodiment of the invention directly triggers the status report process when the existence of the lost RLC SDU is determined, can solve the problem that the feedback of the existing ARQ process is too slow, and shortens the time for acquiring retransmitted data.
Mode two
In the second mode, the RLC entity at the receiving end acquires the retransmission data through the backup data. Specifically, step 105 may include:
and the RLC entity of the receiving end selects the RLC PDU corresponding to the RLC identification information of the lost RLC SDU from the backup data.
The backup data stores RLC PDUs received from an RLC entity of a sending end.
Therefore, the retransmission data is directly selected from the backup data without being obtained from the RLC entity of the sending end again, the time for obtaining the retransmission data can be further shortened, and the quick retransmission is realized.
Further, in order to avoid the receiving end from caching too much data and affecting the performance of the receiving end, the RLC entity of the receiving end may delete the successfully sent data in the backup data. Specifically, after step 102, the data transmission method may further include:
the RLC entity of the receiving end acquires the RLC identification information carried in the identification report information;
and the RLC entity of the receiving end deletes the RLC PDU corresponding to the acquired RLC identification information in the backup data, wherein the RLC PDU received from the RLC entity of the transmitting end is stored in the backup data.
Therefore, successfully sent data in the backup data is deleted in real time, the receiving end can be prevented from caching excessive data, and the performance of the receiving end is improved.
Referring to fig. 3, an embodiment of the present invention further provides a data transmission method, which is applied to a PDCP entity at a receiving end, and includes the following steps:
step 301: and receiving RLC SDU sent by the RLC entity of the receiving end.
The RLC SDU carries RLC identification information of the RLC SDU, and the RLC identification information is used for the PDCP entity to determine the RLC SDU successfully sent by the RLC entity.
In the data transmission method of the embodiment of the invention, the RLC SDU sent by the RLC entity of the receiving end is received, and the RLC identification information is used for the PDCP entity to determine the RLC SDU successfully sent by the RLC entity because the RLC SDU carries the RLC identification information of the RLC SDU, so that the PDCP entity of the receiving end can conveniently determine the RLC SDU successfully sent and feed back the RLC SDU to the RLC entity of the receiving end, and the PDCP entity of the receiving end can be ensured to correctly receive data.
In this embodiment of the present invention, after step 301, the data transmission method may further include:
the PDCP entity of the receiving end associates the PDCP identification information with the RLC identification information; if the identification information is a sequence number, the PDCP entity of the receiving end can associate the PDCP sequence number with the corresponding RLC sequence number;
a PDCP entity of a receiving end generates identification report information; wherein, the identification report information carries RLC identification information associated with PDCP identification information corresponding to the PDCP PDU received by the PDCP entity; the RLC SDU sent by the RLC entity is the PDCP PDU received by the PDCP entity;
a PDCP entity of a receiving end sends the identification report information to the RLC entity;
and the PDCP entity of the receiving end receives the RLC PDU which is retransmitted by the RLC entity and corresponds to the RLC identification information of the lost RLC SDU.
Therefore, by means of the association of the PDCP identification information and the RLC identification information and the feedback of the identification report information, the RLC entity at the receiving end can conveniently judge whether the missing RLC SDU exists or not, and when the missing RLC SDU exists, the retransmission of corresponding data is carried out, and the PDCP entity is further ensured to correctly receive the data.
In the embodiment of the present invention, when generating the identification report information, the PDCP entity at the receiving end may detect packet loss during transmission between an air interface and an F1 interface by using a newly added receiving Timer (t-Reception Timer) therein, and generate corresponding identification report information. In this case, the identification information is a sequence number, the state variable (Reception _ PDCP _ RX _ SN) of the Reception timer is a predetermined PDCP sequence number, and the state variable of the Reception timer is incremented by 1 every time the identification report information is generated or the Reception timer expires. The duration of the receive timer may be configured by higher layer signaling. For the same PDCP entity, at most one receive timer can be running at the same time. The initial value of the state variable of the reception timer is 0 at the time of PDCP entity setup.
Specifically, the process of generating the identification report information by the PDCP entity at the receiving end by means of the receiving timer may be:
a PDCP entity of a receiving end triggers a receiving timer by using a preset PDCP sequence number; at this time, the receiving timer is in a running state;
if the PDCP PDU carrying the preset PDCP sequence number is received within the time length of the receiving timer, the PDCP entity of the receiving end generates the identification report information; wherein, the identification report information carries an RLC sequence number associated with the predetermined PDCP sequence number, and is used to notify an RLC entity that an RLC SDU (i.e., PDCP PDU) corresponding to the RLC sequence number is successfully received; in this case, the state variable of the reception timer is increased by 1, and the reception timer is stopped and reset;
if the PDCP PDU carrying the predetermined PDCP sequence number is not received by the PDCP entity at the receiving end when the receiving timer is overtime, but at least one PDCP PDU carrying other predetermined PDCP sequence numbers and being behind and continuous with the PDCP PDU carrying the predetermined PDCP sequence number is received, the identification report information is sequentially generated according to the ascending sequence of the at least one other predetermined PDCP sequence number; wherein, the identification report information carries RLC sequence numbers associated with the other predetermined PDCP sequence numbers, and is used to notify an RLC entity that RLC SDUs (i.e. PDCP PDUs) corresponding to the RLC sequence numbers are successfully received; for example, if the predetermined PDCP sequence number is 5, the other predetermined PDCP sequence numbers may be 6, 7, and 8, or 6 and 7, etc. In this case, when the PDCP PDU carrying the predetermined PDCP sequence number is not received, the state variable of the reception timer is increased by 1 every time the identification report information is generated, and when the state variable of the reception timer is increased by 1, the reception timer is stopped and reset.
It should be noted that, if the PDCP entity of the receiving end does not receive the PDCP PDU carrying the predetermined PDCP sequence number when the receiving timer expires, the state variable of the receiving timer is increased by 1, and the receiving timer is stopped and reset. When the receiving timer is not running (including the situation that the receiving timer stops), if at least one PDCP PDU exists in the buffer of the PDCP entity of the receiving end, the receiving timer is started. And in the running process of the receiving timer, if the duration of the receiving timer is reconfigured by the high-level signaling, stopping and restarting the receiving timer.
The above embodiments describe the data transmission method of the present invention, and the RLC entity and the PDCP entity applied to the receiving end of the present invention will be described with reference to the embodiments and the drawings.
Referring to fig. 4, an RLC entity applied to a receiving end according to an embodiment of the present invention includes a processor 41, a transmitting interface 42, and a receiving interface 43.
Wherein, the processor 41 is configured to determine RLC identification information of the RLC SDU sent by the RLC entity.
The sending interface 42 is configured to send an RLC SDU to a PDCP entity of a receiving end, where the RLC SDU carries RLC identification information of the RLC SDU, and the RLC identification information is used by the PDCP entity to determine an RLC SDU successfully sent by the RLC entity.
The RLC entity of the receiving end of the embodiment of the invention sends the RLC SDU to the PDCP entity of the receiving end, and the RLC identification information is used for the PDCP entity to determine the RLC SDU successfully sent by the RLC entity because the RLC SDU carries the RLC identification information of the RLC SDU, so that the PDCP entity of the receiving end can conveniently determine the RLC SDU successfully sent and feed back the RLC SDU to the RLC entity of the receiving end, and the PDCP entity of the receiving end can be ensured to correctly receive data.
In this embodiment of the present invention, the receiving interface 43 may be configured to receive identification report information sent by the PDCP entity, where the identification report information carries RLC identification information associated with PDCP identification information corresponding to a PDCP PDU received by the PDCP entity.
The processor 41 is further configured to determine RLC identification information of the missing RLC SDU and acquire an RLC PDU corresponding to the RLC identification information of the missing RLC SDU, when the missing RLC SDU exists in the RLC SDU transmission process according to the identification report information.
The transmitting interface 42 is also used for retransmitting the RLC PDU to the PDCP entity.
Optionally, the processor 41 further triggers a status reporting procedure.
The sending interface 42 is further configured to send status report information to an RLC entity of a sending end, where the status report information carries RLC identification information of the missing RLC SDU.
The receiving interface 43 is further configured to receive an RLC PDU sent by the RLC entity of the sending end and corresponding to the RLC identification information of the missing RLC SDU.
Optionally, the processor 42 is further configured to select an RLC PDU corresponding to the RLC identification information of the lost RLC SDU from backup data, where the RLC PDU received from an RLC entity of the sending end is stored in the backup data.
Optionally, the processor 42 is further configured to obtain RLC identification information carried in the identification report information, and delete an RLC PDU corresponding to the obtained RLC identification information in backup data, where the RLC PDU received from an RLC entity of the sending end is stored in the backup data.
Optionally, the identification information is a serial number.
In FIG. 4, a bus architecture (represented by bus 40), bus 40 may include any number of interconnected buses and bridges, with bus 40 connecting together various circuits including one or more processors, represented by processor 41, and memory, represented by memory 44. The transmitting interface 42 and the receiving interface 43 may be a transceiving interface, and the transmitting interface 42 and the receiving interface 43 may be connected to the processor 41 and the memory 44 through the bus 40.
Processor 41 is responsible for managing bus 40 and general processing, while memory 44 may be used to store data used by processor 41 in performing operations.
Referring to fig. 5, an embodiment of the present invention further provides a PDCP entity applied to a receiving end, which includes a processor 51, a sending interface 52, and a receiving interface 53.
The receiving interface 53 is configured to receive an RLC SDU sent by an RLC entity of a receiving end, where the RLC SDU carries RLC identification information of the RLC SDU, and the RLC identification information is used by the PDCP entity to determine the RLC SDU successfully sent by the RLC entity.
The PDCP entity of the receiving end of the embodiment of the invention receives the RLC SDU sent by the RLC entity of the receiving end, and the RLC identification information is used for the PDCP entity to determine the RLC SDU successfully sent by the RLC entity because the RLC SDU carries the RLC identification information of the RLC SDU, so that the PDCP entity of the receiving end can conveniently determine the RLC SDU successfully sent and feed back the RLC SDU to the RLC entity of the receiving end, thereby ensuring that the PDCP entity of the receiving end can correctly receive data.
In this embodiment of the present invention, the processor 51 may be configured to associate PDCP identification information with the RLC identification information, and generate identification report information, where the identification report information carries RLC identification information associated with PDCP identification information corresponding to a PDCP PDU received by the PDCP entity.
The sending interface 52 is configured to send the identification report information to the RLC entity.
The receiving interface 53 is configured to receive the RLC PDU retransmitted by the RLC entity and corresponding to the RLC identification information of the missing RLC SDU.
Optionally, the processor 51 is further configured to trigger a reception timer by using a predetermined PDCP sequence number; when receiving the PDCP PDU carrying the predetermined PDCP sequence number within the duration of the receiving timer, generating the identification report information, wherein the identification report information carries an RLC sequence number associated with the predetermined PDCP sequence number; or, when the PDCP PDU carrying the predetermined PDCP sequence number is not received when the receiving timer expires, but at least one PDCP PDU carrying another predetermined PDCP sequence number is received after and consecutive PDCP PDUs carrying the predetermined PDCP sequence number, sequentially generating the identification report information according to an ascending order of the at least one other predetermined PDCP sequence number, where the identification report information carries RLC sequence numbers associated with the other predetermined PDCP sequence numbers;
wherein, the state variable of the receiving timer is the predetermined PDCP sequence number, and the state variable of the receiving timer is increased by 1 after generating the identification report information each time or after the receiving timer is overtime.
In FIG. 5, a bus architecture (represented by bus 50), bus 50 may include any number of interconnected buses and bridges, with bus 50 connecting together various circuits including one or more processors, represented by processor 51, and memory, represented by memory 54. The transmitting interface 52 and the receiving interface 53 may be a transceiving interface, and the transmitting interface 52 and the receiving interface 53 may be connected to the processor 51 and the memory 54 through the bus 50.
The processor 51 is responsible for managing the bus 50 and general processing, while the memory 54 may be used for storing data used by the processor 51 in performing operations.
In addition, an embodiment of the present invention further provides a receiving end, which includes a memory, a processor, and a data transmission program stored in the memory and executable on the processor, where the data transmission program, when executed by the processor, can implement the steps in the data transmission method applied to the RLC entity and the PDCP entity.
Specifically, referring to fig. 6, the embodiment of the present invention further provides a receiving end, where the receiving end includes a bus 61, a transceiver 62, an antenna 63, a bus interface 64, a processor 65, and a memory 66. In addition, the receiving end further includes an RLC entity and a PDCP entity.
In this embodiment of the present invention, the receiving end further includes: a data transfer program stored on the memory 66 and executable on the processor 601, in particular, the data transfer program when executed by the processor 65, may implement the steps of: determining RLC identification information of RLC SDU sent by an RLC entity, and sending the RLC SDU to a PDCP entity of a receiving end, wherein the RLC identification information of the RLC SDU is carried in the RLC SDU, and the RLC identification information is used for the PDCP entity to determine the RLC SDU successfully sent by the RLC entity.
Optionally, when executed by the processor 65, the data transmission program further implements the following steps: receiving identification report information sent by the PDCP entity, wherein the identification report information carries RLC identification information associated with the PDCP identification information corresponding to the PDCP PDU received by the PDCP entity, judging whether a lost RLC SDU exists in the transmission process of the RLC SDU according to the identification report information, determining the RLC identification information of the lost RLC SDU if the lost RLC SDU exists, acquiring the RLC PDU corresponding to the RLC identification information of the lost RLC SDU, and retransmitting the RLC PDU to the PDCP entity.
Optionally, when executed by the processor 65, the data transmission program further implements the following steps: and triggering a status report process and controlling the transceiver 62 to send status report information to the RLC entity of the sending end, wherein the status report information carries the RLC identification information of the missing RLC SDU, and the transceiver 62 is controlled to receive the RLC PDU which is sent by the RLC entity of the sending end and corresponds to the RLC identification information of the missing RLC SDU.
Optionally, when executed by the processor 65, the data transmission program further implements the following steps: and selecting the RLC PDU corresponding to the RLC identification information of the lost RLC SDU from backup data, wherein the RLC PDU received from an RLC entity of a sending end is stored in the backup data.
Optionally, when executed by the processor 65, the data transmission program further implements the following steps: and acquiring RLC identification information carried in the identification report information, and deleting RLC PDUs (protocol data units) corresponding to the acquired RLC identification information in backup data, wherein the RLC PDUs received from an RLC entity of a sending end are stored in the backup data.
Optionally, the identification information is a serial number.
Specifically, when executed by the processor 65, the data transmission program may implement the following steps: receiving RLC SDU sent by an RLC entity of a receiving end, wherein the RLC SDU carries RLC identification information of the RLC SDU, and the RLC identification information is used for the PDCP entity to determine the RLC SDU successfully sent by the RLC entity.
Optionally, when executed by the processor 65, the data transmission program further implements the following steps: and associating PDCP identification information with the RLC identification information to generate identification report information, wherein the identification report information carries RLC identification information associated with the PDCP identification information corresponding to the PDCP PDU received by the PDCP entity, sending the identification report information to the RLC entity, and receiving the RLC PDU retransmitted by the RLC entity and corresponding to the RLC identification information of the lost RLC SDU.
Optionally, when executed by the processor 65, the data transmission program further implements the following steps: triggering a receiving timer by using a preset PDCP sequence number, generating the identification report information if the PDCP PDU carrying the preset PDCP sequence number is received within the time length of the receiving timer, wherein the identification report information carries an RLC sequence number associated with the preset PDCP sequence number, if the PDCP PDU carrying the preset PDCP sequence number is not received when the receiving timer is overtime, but at least one continuous PDCP PDU carrying other preset PDCP sequence numbers and behind the PDCP PDU carrying the preset PDCP sequence number is received, sequentially generating the identification report information according to the ascending order of the at least one other preset PDCP sequence number, wherein the identification report information carries the RLC sequence number associated with the other preset PDCP sequence numbers, and the state variable of the receiving timer is the preset PDCP sequence number, and the state variable of the receiving timer is increased by 1 after the identification report information is generated every time or the receiving timer is overtime.
In fig. 6, a bus architecture (represented by bus 61), bus 61 may include any number of interconnected buses and bridges, bus 61 linking together various circuits including one or more processors, represented by processor 65, and memory, represented by memory 66. The bus 61 may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. A bus interface 64 provides an interface between the bus 61 and the transceiver 62. The transceiver 62 may be one element or a plurality of elements, such as a plurality of receivers and transmitters, providing a means for communicating with various other apparatus over a transmission medium. The data processed by the processor 65 is transmitted over a wireless medium via the antenna 63, and further, the antenna 63 receives the data and transmits the data to the processor 65.
The processor 65 is responsible for managing the bus 61 and general processing and may also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. And the memory 66 may be used to store data used by the processor 65 in performing operations.
Alternatively, the processor 65 may be a CPU, ASIC, FPGA or CPLD.
The embodiment of the present invention further provides a computer-readable storage medium, where a data transmission program is stored, and when the data transmission program is executed by a processor, the data transmission program implements the processes of the data transmission method embodiment, and can achieve the same technical effects, and in order to avoid repetition, the details are not repeated here.
Specifically, the data transmission program may be executed by the processor to implement the following steps: and sending RLC SDU to a PDCP entity of a receiving end, wherein the RLC SDU carries RLC identification information of the RLC SDU, and the RLC identification information is used for the PDCP entity to determine the RLC SDU successfully sent by the RLC entity.
Optionally, the data transmission program when executed by the processor may further implement the steps of: receiving identification report information sent by the PDCP entity, wherein the identification report information carries RLC identification information associated with the PDCP identification information corresponding to the PDCP PDU received by the PDCP entity, judging whether a lost RLC SDU exists in the transmission process of the RLC SDU according to the identification report information, determining the RLC identification information of the lost RLC SDU if the lost RLC SDU exists, acquiring the RLC PDU corresponding to the RLC identification information of the lost RLC SDU, and retransmitting the RLC PDU to the PDCP entity.
Optionally, the data transmission program when executed by the processor may further implement the steps of: and triggering a status report process and sending status report information to an RLC entity of a sending end, wherein the status report information carries RLC identification information of the lost RLC SDU, and receiving an RLC PDU which is sent by the RLC entity of the sending end and corresponds to the RLC identification information of the lost RLC SDU.
Optionally, when executed by the processor, the data transmission program further implements the following steps: and selecting the RLC PDU corresponding to the RLC identification information of the lost RLC SDU from backup data, wherein the RLC PDU received from an RLC entity of a sending end is stored in the backup data.
Optionally, when executed by the processor, the data transmission program further implements the following steps: and acquiring RLC identification information carried in the identification report information, and deleting RLC PDUs (protocol data units) corresponding to the acquired RLC identification information in backup data, wherein the RLC PDUs received from an RLC entity of a sending end are stored in the backup data.
Optionally, the identification information is a serial number.
Specifically, when executed by the processor, the data transmission program implements the following steps: receiving RLC SDU sent by an RLC entity of a receiving end, wherein the RLC SDU carries RLC identification information of the RLC SDU, and the RLC identification information is used for the PDCP entity to determine the RLC SDU successfully sent by the RLC entity.
Optionally, when executed by the processor, the data transmission program further implements the following steps: and associating PDCP identification information with the RLC identification information to generate identification report information, wherein the identification report information carries RLC identification information associated with the PDCP identification information corresponding to the PDCP PDU received by the PDCP entity, sending the identification report information to the RLC entity, and receiving the RLC PDU retransmitted by the RLC entity and corresponding to the RLC identification information of the lost RLC SDU.
Optionally, when executed by the processor, the data transmission program further implements the following steps: triggering a receiving timer by using a preset PDCP sequence number, generating the identification report information if the PDCP PDU carrying the preset PDCP sequence number is received within the time length of the receiving timer, wherein the identification report information carries an RLC sequence number associated with the preset PDCP sequence number, if the PDCP PDU carrying the preset PDCP sequence number is not received when the receiving timer is overtime, but at least one continuous PDCP PDU carrying other preset PDCP sequence numbers and behind the PDCP PDU carrying the preset PDCP sequence number is received, sequentially generating the identification report information according to the ascending order of the at least one other preset PDCP sequence number, wherein the identification report information carries the RLC sequence number associated with the other preset PDCP sequence numbers, and the state variable of the receiving timer is the preset PDCP sequence number, and the state variable of the receiving timer is increased by 1 after the identification report information is generated every time or the receiving timer is overtime.
Computer-readable media, which include both non-transitory and non-transitory, removable and non-removable media, may implement the information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.

Claims (16)

1. A data transmission method is applied to a Radio Link Control (RLC) entity at a receiving end, and is characterized by comprising the following steps:
sending an RLC Service Data Unit (SDU) to a Packet Data Convergence Protocol (PDCP) entity of a receiving end, wherein the RLC SDU carries RLC identification information of the RLC SDU, and the RLC identification information is used for the PDCP entity to determine the RLC SDU successfully sent by the RLC entity; the receiving end is network side equipment;
after transmitting the RLC SDU to the PDCP entity of the receiving end, the method further includes:
receiving identification report information sent by the PDCP entity, wherein the identification report information carries RLC identification information associated with PDCP identification information corresponding to a PDCP protocol data unit PDU received by the PDCP entity;
judging whether a lost RLC SDU exists in the transmission process of the RLC SDU according to the identification report information;
if the RLC SDU is lost, determining RLC identification information of the lost RLC SDU;
acquiring RLC PDU corresponding to the RLC identification information of the lost RLC SDU;
retransmitting the RLC PDU to the PDCP entity.
2. The method of claim 1, wherein the obtaining the RLC PDU corresponding to the RLC identification information of the missing RLC SDU comprises:
triggering a status report process and sending status report information to an RLC entity of a sending end, wherein the status report information carries RLC identification information of the lost RLC SDU;
and receiving the RLC PDU which is sent by the RLC entity of the sending end and corresponds to the RLC identification information of the lost RLC SDU.
3. The method of claim 1, wherein the obtaining the RLC PDU corresponding to the RLC identification information of the missing RLC SDU comprises:
and selecting the RLC PDU corresponding to the RLC identification information of the lost RLC SDU from backup data, wherein the RLC PDU received from an RLC entity of a sending end is stored in the backup data.
4. The method as claimed in claim 1, wherein after receiving the identification report information sent by the PDCP entity, the method further comprises:
acquiring RLC identification information carried in the identification report information;
and deleting the RLC PDU corresponding to the acquired RLC identification information in the backup data, wherein the RLC PDU received from the RLC entity of the sending end is stored in the backup data.
5. The method according to any of claims 1 to 4, wherein the RLC identification information is a sequence number and the PDCP identification information is a sequence number.
6. A data transmission method is applied to a Packet Data Convergence Protocol (PDCP) entity of a receiving end, and is characterized by comprising the following steps:
receiving an RLC Service Data Unit (SDU) sent by a Radio Link Control (RLC) entity of a receiving end, wherein the RLC SDU carries RLC identification information of the RLC SDU, and the RLC identification information is used for the PDCP entity to determine the RLC SDU successfully sent by the RLC entity; the receiving end is network side equipment;
after receiving the RLC SDU sent by the RLC entity of the receiving end, the method further includes:
associating PDCP identification information with the RLC identification information;
generating identification report information, wherein the identification report information carries RLC identification information associated with PDCP identification information corresponding to a PDCP Protocol Data Unit (PDU) received by the PDCP entity;
sending the identification report information to the RLC entity;
and receiving the RLC PDU retransmitted by the RLC entity and corresponding to the RLC identification information of the lost RLC SDU.
7. The method of claim 6 wherein the RLC identification information is a sequence number and the PDCP identification information is a sequence number; the generating identification report information includes:
triggering a reception timer using a predetermined PDCP sequence number;
if the PDCP PDU carrying the predetermined PDCP sequence number is received within the time length of the receiving timer, generating the identification report information, wherein the identification report information carries an RLC sequence number associated with the predetermined PDCP sequence number;
if the PDCP PDU carrying the predetermined PDCP sequence number is not received when the receiving timer is overtime, but at least one PDCP PDU which carries other predetermined PDCP sequence numbers and is positioned behind and continuous with the PDCP PDU carrying the predetermined PDCP sequence number is received, the identification report information is sequentially generated according to the ascending order of the at least one other predetermined PDCP sequence number, wherein the identification report information carries RLC sequence numbers which are associated with the other predetermined PDCP sequence numbers;
wherein, the state variable of the receiving timer is the predetermined PDCP sequence number, and the state variable of the receiving timer is increased by 1 after generating the identification report information each time or after the receiving timer is overtime.
8. A Radio Link Control (RLC) entity is applied to a receiving end, and is characterized in that the receiving end is a network side device and comprises a processor and a sending interface;
the processor is configured to determine RLC identification information of an RLC service data unit SDU sent by the RLC entity;
the sending interface is used for sending RLC SDU to a packet data convergence protocol PDCP entity of a receiving end, wherein the RLC SDU carries RLC identification information of the RLC SDU, and the RLC identification information is used for the PDCP entity to determine the RLC SDU successfully sent by the RLC entity;
the RLC entity further comprises a receiving interface;
the receiving interface is configured to receive identification report information sent by the PDCP entity, where the identification report information carries RLC identification information associated with PDCP identification information corresponding to a PDCP protocol data unit PDU received by the PDCP entity;
the processor is further configured to determine whether a missing RLC SDU exists in the transmission process of the RLC SDU according to the identification report information, determine RLC identification information of the missing RLC SDU when the missing RLC SDU exists, and acquire an RLC PDU corresponding to the RLC identification information of the missing RLC SDU;
the transmitting interface is further configured to retransmit the RLC PDU to the PDCP entity.
9. The RLC entity of claim 8, wherein:
the processor is further configured to trigger a status reporting procedure;
the sending interface is further configured to send status report information to an RLC entity of a sending end, where the status report information carries RLC identification information of the lost RLC SDU;
the receiving interface is further configured to receive an RLC PDU sent by the RLC entity of the sending end and corresponding to the RLC identification information of the missing RLC SDU.
10. The RLC entity of claim 8, wherein:
the processor is further configured to select an RLC PDU corresponding to the RLC identification information of the lost RLC SDU from backup data, where the RLC PDU received from an RLC entity of the sending end is stored in the backup data.
11. The RLC entity of claim 8, wherein:
the processor is further configured to obtain RLC identification information carried in the identification report information, and delete RLC PDUs corresponding to the obtained RLC identification information in backup data, where the RLC PDUs received from an RLC entity of a sending end are stored in the backup data.
12. The RLC entity according to any of claims 8 to 11, wherein the RLC identification information is a sequence number and the PDCP identification information is a sequence number.
13. A packet data convergence protocol PDCP entity is applied to a receiving end, and is characterized in that the receiving end is a network side device and comprises a receiving interface;
the receiving interface is used for receiving an RLC Service Data Unit (SDU) sent by a Radio Link Control (RLC) entity of a receiving end, wherein the RLC SDU carries RLC identification information of the RLC SDU, and the RLC identification information is used for the PDCP entity to determine the RLC SDU successfully sent by the RLC entity;
the PDCP entity further comprises a processor and a transmit interface;
the processor is configured to associate PDCP identification information with the RLC identification information, and generate identification report information, where the identification report information carries RLC identification information associated with PDCP identification information corresponding to a PDCP protocol data unit PDU received by the PDCP entity;
the sending interface is used for sending the identification report information to the RLC entity;
the receiving interface is further configured to receive an RLC PDU retransmitted by the RLC entity and corresponding to RLC identification information of the missing RLC SDU.
14. The PDCP entity of claim 13, wherein:
the processor is further configured to trigger a receive timer with a predetermined PDCP sequence number; when receiving the PDCP PDU carrying the predetermined PDCP sequence number within the duration of the receiving timer, generating the identification report information, wherein the identification report information carries an RLC sequence number associated with the predetermined PDCP sequence number; or, when the PDCP PDU carrying the predetermined PDCP sequence number is not received when the receiving timer expires, but at least one PDCP PDU carrying another predetermined PDCP sequence number is received after and consecutive PDCP PDUs carrying the predetermined PDCP sequence number, sequentially generating the identification report information according to an ascending order of the at least one other predetermined PDCP sequence number, where the identification report information carries RLC sequence numbers associated with the other predetermined PDCP sequence numbers;
wherein, the state variable of the receiving timer is the predetermined PDCP sequence number, and the state variable of the receiving timer is increased by 1 after generating the identification report information each time or after the receiving timer is overtime.
15. A receiving end, comprising a memory, a processor and a data transmission program stored in the memory and executable on the processor, wherein the receiving end is a network side device, and the data transmission program, when executed by the processor, implements the steps in the data transmission method according to any one of claims 1 to 7.
16. A computer-readable storage medium having a data transmission program stored thereon, wherein the computer-readable storage medium is applied to a network-side device, and the data transmission program, when executed by a processor, implements the steps in the data transmission method according to any one of claims 1 to 7.
CN201710762133.6A 2017-08-30 2017-08-30 Data transmission method, RLC entity and PDCP entity Active CN109428684B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201710762133.6A CN109428684B (en) 2017-08-30 2017-08-30 Data transmission method, RLC entity and PDCP entity
PCT/CN2018/095963 WO2019042032A1 (en) 2017-08-30 2018-07-17 Data transmission method, rlc entity and pdcp entity

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710762133.6A CN109428684B (en) 2017-08-30 2017-08-30 Data transmission method, RLC entity and PDCP entity

Publications (2)

Publication Number Publication Date
CN109428684A CN109428684A (en) 2019-03-05
CN109428684B true CN109428684B (en) 2020-11-27

Family

ID=65503817

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710762133.6A Active CN109428684B (en) 2017-08-30 2017-08-30 Data transmission method, RLC entity and PDCP entity

Country Status (2)

Country Link
CN (1) CN109428684B (en)
WO (1) WO2019042032A1 (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111756482B (en) * 2019-03-29 2023-01-13 中国移动通信有限公司研究院 Acknowledgement feedback method, device and computer readable storage medium
CN113875284A (en) * 2020-04-30 2021-12-31 华为技术有限公司 Method and communication device for processing data packet
CN111935794B (en) * 2020-07-02 2021-06-04 四川创智联恒科技有限公司 Data processing method for shortening switching time delay

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102395156A (en) * 2011-09-28 2012-03-28 电信科学技术研究院 Data transmission methods and device applied between packet data convergence protocol (PDCP) entity and radio link control (RLC) entity

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100433716C (en) * 2005-08-16 2008-11-12 中兴通讯股份有限公司 System and method for supporting multi-carrier downlink high-speed data packet access
CN101047484B (en) * 2006-06-21 2010-10-13 华为技术有限公司 Transmission layer retransmission method and system
CN101132609B (en) * 2006-08-22 2010-04-21 华为技术有限公司 Method and system for repeating data during switching course
CN101127586A (en) * 2007-09-25 2008-02-20 中兴通讯股份有限公司 A method for triggering automatic retransfer request status report
CN101809924B (en) * 2007-12-29 2013-08-21 中兴通讯股份有限公司 Method for reset control of radio link control entity
CN101483505B (en) * 2008-01-08 2013-02-27 中兴通讯股份有限公司 Service data unit discarding method
CN101547141B (en) * 2008-03-25 2012-06-27 华为技术有限公司 Method, system and device for data transmission
CN104935413B (en) * 2014-03-19 2019-12-27 夏普株式会社 Packet data convergence protocol PDCP entity and execution method thereof
US20150305041A1 (en) * 2014-04-16 2015-10-22 Electronics And Telecommunications Research Institute Method and apparatus for providing service using radio resource aggregation
KR20170041658A (en) * 2014-08-07 2017-04-17 엘지전자 주식회사 Method for processing a packet data convergence protocol packet data unit at a user equipment in a dual connectivity systme and device therefor

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102395156A (en) * 2011-09-28 2012-03-28 电信科学技术研究院 Data transmission methods and device applied between packet data convergence protocol (PDCP) entity and radio link control (RLC) entity

Also Published As

Publication number Publication date
CN109428684A (en) 2019-03-05
WO2019042032A1 (en) 2019-03-07

Similar Documents

Publication Publication Date Title
CN108631954B (en) Data transmission method and device
US11533651B2 (en) Transmission control method and device
JP5215413B2 (en) Status report for retransmission protocol
KR102335821B1 (en) Data transmission method and device
CN109428684B (en) Data transmission method, RLC entity and PDCP entity
RU2701523C1 (en) System and method of providing synchronization in transmissions in a mode without connection
CN108886713B (en) Data transmission method, data receiving equipment and data sending equipment
KR20090053505A (en) Connection identifier synchronization system and method in a communication system
EP3606134A1 (en) Method for processing radio link failure, and terminal device and network device
JP2019527503A (en) Data retransmission method and apparatus
CN110557229B (en) Data sending method, data receiving method, sending end and receiving end
US20190394642A1 (en) Key change procedure
CN110808917B (en) Multilink aggregation data retransmission method and transmitting equipment
CN110266446B (en) Method and device for adjusting out-of-order time length based on SACK mode
US11316620B2 (en) Enhanced HARQ algorithm for large round trip delay links
CN112118594A (en) Data uploading method, data downloading method, electronic equipment and storage medium
CN111543079B (en) Radio Link Control (RLC) Acknowledged Mode (AM) data reception
CN107959554B (en) A kind of repeating method and device of data
CN110891326B (en) Control plane connection reestablishing method, communication equipment, target base station and source base station
CN116963175A (en) Data transmission method, device and system
JP2021100288A (en) Wireless communication device, wireless communication method, and wireless communication system
CN112218390A (en) Data processing method and device
CN102056231A (en) Method and equipment for guaranteeing reliable transmission of LTE (Long Term Evolution) location protocol data
KR101732548B1 (en) Apparatus and method for transmitting data usnig random access preamble
CN113783665B (en) Communication method and device

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