WO2019042032A1 - Data transmission method, rlc entity and pdcp entity - Google Patents

Abstract

The invention relates to a data transmission method, an RLC entity and a PDCP entity. The data transmission method includes the steps of: sending an RLC SDU to a PDCP entity of a receiving terminal, accompanied by RLC identifier information of the RLC SDU, the RLC identifier information being used by the PDCP to determine the RLC SDU successfully issued by the RLC entity.

Description

A data transmission method, an RLC entity and a PDCP entity

Cross-reference to related applications

Priority is claimed on Japanese Patent Application No. 20171076213, filed on Aug.

Technical field

The present disclosure relates to the field of communications technologies, and in particular, to a data transmission method, an RLC entity, and a PDCP entity.

Background technique

Currently, according to the 3rd Generation Partnership Project (3GPP) related standards, the centralized unit (CU) and the distributed unit (DU) architecture protocol stack function is divided into: Splitting between the Packet Data Convergence Protocol (PDCP) layer and the Radio Link Control (RLC) layer, that is, the protocol stack functions of the PDCP layer and the RLC layer are respectively in the CU and Implemented on the DU. At the same time, the 3GPP standard has determined that there is an interface between the CU and the DU on the network side, and the interface name is an F1 interface.

Since the protocol stack functions of the PDCP layer and the RLC layer are implemented on the CU and the DU respectively, and there is an interface between the CU and the DU on the network side, the RLC layer is sent to the receiving end PDCP layer by the RLC layer at the receiving end (network side). The F1 interface needs to be used, and packet loss may occur during the transmission of the interface. Therefore, the PDCP layer at the receiving end cannot successfully receive data.

Summary of the invention

The embodiments of the present disclosure provide a data transmission method, an RLC entity, and a PDCP entity, to solve the problem that an existing receiving end PDCP entity may not successfully receive data.

In a first aspect, an embodiment of the present disclosure provides a data transmission method, which is applied to an RLC entity at a receiving end, and includes:

The RLC SDU is sent to the PDCP entity of the receiving end, and the RLC SDU carries the 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.

After the RLC SDU and the RLC identification information are sent to the PDCP entity at the receiving end, the method further includes:

Receiving the identifier report information sent by the PDCP entity, where the identifier report information carries the RLC identifier information associated with the PDCP identifier information corresponding to the PDCP PDU received by the PDCP entity;

Determining, according to the identifier report information, whether there is a lost RLC SDU in the transmission process of the RLC SDU to the PDCP entity;

Determining RLC identification information of the lost RLC SDU if there is a lost RLC SDU;

Obtaining an RLC PDU corresponding to the RLC identification information of the lost RLC SDU;

Retransmitting the RLC SDU corresponding to the RLC PDU to the PDCP entity.

Optionally, the obtaining the RLC PDU corresponding to the RLC identifier information of the lost RLC SDU includes:

The status report process is triggered, and the status report information is sent to the RLC entity of the sending end, where the status report information carries the RLC identification information of the lost RLC SDU;

Receiving, by the RLC entity of the sending end, an RLC PDU corresponding to the RLC identification information of the lost RLC SDU.

Optionally, the obtaining the RLC PDU corresponding to the RLC identifier information of the lost RLC SDU includes:

The RLC PDU corresponding to the RLC identification information of the lost RLC SDU is selected from the backup data, where the backup data stores an RLC PDU received from the RLC entity of the sending end.

Optionally, after the receiving the identifier report information sent by the PDCP entity, the method further includes:

Obtaining the RLC identification information carried in the identifier report information;

And deleting the RLC PDU corresponding to the obtained RLC identification information in the backup data, where the backup data stores an RLC PDU received from the RLC entity of the sending end.

Optionally, the identifier information is a serial number.

In a second aspect, the embodiment of the present disclosure further provides a data transmission method, which is applied to a PDCP entity at a receiving end, and includes:

The RLC SDU sent by the RLC entity of the receiving end is received, and the RLC identification information of the RLC SDU is carried in 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.

After the receiving the RLC SDU and the RLC identification information sent by the RLC entity of the receiving end, the method further includes:

Associating PDCP identification information with the RLC identification information;

Generating the identifier report information, where the identifier report information carries the RLC identifier information associated with the PDCP identifier information corresponding to the PDCP PDU received by the PDCP entity;

Sending the identification report information to the RLC entity;

Receiving an RLC SDU corresponding to the RLC identification information of the lost RLC SDU retransmitted by the RLC entity.

Optionally, the identifier information is a serial number, and the generating identifier report information includes:

Triggering a reception timer by using a predetermined PDCP sequence number;

If the PDCP PDU carrying the predetermined PDCP sequence number is received within the duration of the receiving timer, the identifier report information is generated or improved, where the identifier report information carries the predetermined PDCP sequence number Linked RLC serial number;

If the PDCP PDU carrying the predetermined PDCP sequence number is not received when the receiving timer expires, but after receiving at least one PDCP PDU carrying the other PDCP sequence number after carrying the predetermined PDCP sequence number, and continuing The PDCP PDU is arranged in an ascending order of the PDCP sequence number to generate or refine the identifier report information, where the identifier report information carries an RLC sequence number associated with the ascending PDCP sequence number;

The state variable to be checked by the receiving timer is the predetermined PDCP sequence number, and the state variable is after each generation of the identifier report information, or after each improvement of the report report information, or after the receiving timer expires. Increase by 1.

In a third aspect, an embodiment of the present disclosure further provides an RLC entity, which is applied to a receiving end, including a processor, a sending interface, and a receiving interface.

The processor is configured to determine RLC identification information of the RLC SDU sent by the RLC entity;

The sending interface is configured to send, to the PDCP entity of the receiving end, the RLC SDU, and the RLC SDU carries the RLC identification information of the RLC SDU, where the RLC identification information is used by the PDCP entity to determine that the RLC entity is successful. The RLC SDU sent.

The receiving interface is configured to receive the identifier report information that is sent by the PDCP entity, where the identifier report information carries the RLC identifier information associated with the PDCP identifier information corresponding to the PDCP PDU received by the PDCP entity;

The processor is further configured to determine, according to the identifier report information, whether there is a lost RLC SDU in the transmission process of the RLC SDU, and determine, when there is a lost RLC SDU, the RLC identifier information of the lost RLC SDU. Obtaining an RLC PDU corresponding to the RLC identification information of the lost RLC SDU;

The sending interface is further configured to retransmit the RLC SDU to the PDCP entity.

Optionally, the processor is further configured to trigger a status reporting process;

The sending interface is further configured to send the status report information to the RLC entity of the sending end, where the status report information carries the RLC identification information of the lost RLC SDU;

The receiving interface is further configured to receive, by the RLC entity of the sending end, an RLC PDU corresponding to the RLC identification information of the lost RLC SDU.

Optionally, the processor is further configured to: select, from the backup data, an RLC PDU corresponding to the RLC identifier information of the lost RLC SDU, where the backup data stores an RLC received from an RLC entity of the sending end. PDU.

Optionally, the processor is further configured to obtain the RLC identifier information that is carried in the identifier report information, and delete the RLC PDU corresponding to the obtained RLC identifier information in the backup data, where the backup data is stored. There are RLC PDUs received from the RLC entity at the transmitting end.

Optionally, the identifier information is a serial number.

In a fourth aspect, the embodiment of the present disclosure further provides a PDCP entity, which is applied to a receiving end, including a processor, a sending interface, and a receiving interface.

The receiving interface is configured to receive the RLC SDU sent by the RLC entity of the receiving end, and the RLC identification information is used by the RLC SDU to determine the RLC entity of the RLC SDU. Successfully sent RLC SDU.

The processor is configured to associate the PDCP identification information with the RLC identification information to generate the identifier report information, where the identifier report information is associated with the PDCP identifier information corresponding to the PDCP PDU received by the PDCP entity. RLC identification information;

The sending interface is configured to send the identifier report information to the RLC entity;

The receiving interface is further configured to receive an RLC SDU corresponding to the RLC identification information of the lost RLC SDU that is retransmitted by the RLC entity.

Optionally, the processor is further configured to trigger a receiving timer by using a predetermined PDCP sequence number; when the PDCP PDU carrying the predetermined PDCP sequence number is received within the duration of the receiving timer, generating or refining the Identifying report information, wherein the identifier report information carries an RLC sequence number associated with the predetermined PDCP sequence number; or, when the receiving timer expires, does not receive the predetermined PDCP sequence number a PDCP PDU, but after receiving at least one consecutive PDCP PDU carrying another PDCP sequence number after the PDCP PDU carrying the predetermined PDCP sequence number, the identity report information is generated or improved according to the ascending order of the PDCP sequence number. The identifier report information carries an RLC sequence number associated with the other predetermined PDCP sequence numbers;

The state variable to be checked by the receiving timer is the predetermined PDCP sequence number, and the state variable is after each generation of the identifier report information, or after each improvement of the report report information, or after the receiving timer expires. Increase by 1.

In a fifth aspect, an embodiment of the present disclosure further provides a receiving end, including a memory, a processor, and a data transmission program stored on the memory and operable on the processor, where the data transmission program is The steps in the above-described data transmission method applied to the receiving end are implemented when the processor executes.

In a sixth aspect, an embodiment of the present disclosure further provides a computer readable storage medium having stored thereon a data transmission program, where the data transmission program is executed by a processor to implement the steps in the data transmission method applied to the receiving end.

In the data transmission method of the embodiment of the present disclosure, the RLC SDU is sent to the PDCP entity of the receiving end, and the RLC identification information is used by the PDCP entity to determine that the RLC SDU carries the RLC identification information of the RLC SDU. The RLC SDU is successfully sent by the RLC entity, so that the PDCP entity at the receiving end can determine the successfully transmitted RLC SDU and feed back to the RLC entity of the receiving end, so as to ensure that the PDCP entity at the receiving end correctly receives the data.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings to be used in the embodiments of the present disclosure will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present disclosure, Those skilled in the art can also obtain other drawings based on these drawings without paying for creative labor.

1 is a flow chart showing a data transmission method according to an embodiment of the present disclosure;

2 is a flow chart showing another data transmission method of an embodiment of the present disclosure;

FIG. 3 is a flowchart showing still another data transmission method according to an embodiment of the present disclosure;

4 is a schematic structural diagram of an RLC entity according to an embodiment of the present disclosure;

FIG. 5 is a schematic structural diagram of a PDCP entity according to an embodiment of the present disclosure;

FIG. 6 is a schematic structural diagram of a receiving end of an embodiment of the present disclosure.

Detailed ways

The technical solutions in the embodiments of the present disclosure are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present disclosure. It is obvious that the described embodiments are a part of the embodiments of the present disclosure, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present disclosure without departing from the inventive scope are the scope of the disclosure.

As shown in FIG. 1 , an embodiment of the present disclosure provides a data transmission method, which is applied to an RLC entity at a receiving end, and includes the following steps:

Step 101: Send an RLC SDU to the PDCP entity at the receiving end.

At the same time, the RLC SDU (Service Data Unit) carries the 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 the scenario applicable to the embodiment of the present disclosure is that the terminal transmits data to the network side device, and the receiving end is specifically a network side device. An interface (F1 interface) exists between the CU and the DU of the network side device. Therefore, when the network side device functions as the receiving end, the RLC entity needs to pass the F1 interface in the process of sending the RLC SDU (that is, the PDCP PDU) to the PDCP entity. Packet loss may occur during the transmission of the F1 interface, and the RLC SDU to be transmitted may be lost. Therefore, the PDCP entity cannot receive data successfully.

In the data transmission method of the embodiment of the present disclosure, the RLC SDU is sent to the PDCP entity of the receiving end, and the RLC identification information is used by the PDCP entity to determine that the RLC SDU carries the RLC identification information of the RLC SDU. The RLC SDU is successfully sent by the RLC entity, so that the PDCP entity at the receiving end can determine the successfully transmitted RLC SDU and feed back to the RLC entity of the receiving end, so as to ensure that the PDCP entity at the receiving end successfully receives the data.

In the embodiment of the present disclosure, in order to further ensure that the PDCP entity correctly receives data, in the case that there is a lost RLC SDU, the RLC entity at the receiving end may retransmit the lost RLC SDU to the PDCP entity at the receiving end. Specifically, referring to FIG. 2, after step 101, the data transmission method may further include the following steps:

Step 102: Receive identifier report information sent by the PDCP entity at the receiving end.

The identifier report information carries the RLC identifier information associated with the PDCP identifier information corresponding to the PDCP PDU (Protocol Data Unit) received by the PDCP entity. In this way, the RLC SDU successfully sent by the RLC entity can be determined by using the identifier report information. The RLC SDU sent by the RLC entity is a PDCP PDU received by the PDCP entity, which is a different name in the RLC entity and the PDCP entity.

Step 103: Determine, according to the identifier report information, whether there is a lost RLC SDU in the transmission process of the RLC SDU.

The method for determining whether there is a lost RLC SDU in the transmission process of the RLC SDU according to the identifier report information may be: the RLC identifier information carried in the identifier report information and the RLC of the sent RLC SDU The identifier information is compared. If there is RLC identification information that is not carried by the identifier report information, and any identifier report information that has been received has more RLC identifier information than the missing RLC identifier information, the identifier information is not The RLC SDU corresponding to the carried RLC identification information is a lost (transmission failed) RLC SDU. The lost RLC SDU may be lost during air interface and F1 interface transmission.

Step 104: Determine the RLC identification information of the lost RLC SDU if there is a lost RLC SDU.

Step 105: Acquire an RLC PDU corresponding to the RLC identification information of the lost RLC SDU.

The RLC PDU obtained in step 105 is retransmitted data. The RLC PDU can be processed by packet header to obtain the corresponding RLC SDU.

Step 106: Retransmit the RLC SDU to the PDCP entity.

In this way, the data retransmission process can further ensure that the PDCP entity successfully receives data.

In the embodiment of the present disclosure, when the retransmission data is obtained, the RLC entity at the receiving end may be obtained by using at least the following two methods, as follows.

method one

By the way, the RLC entity at the receiving end obtains the retransmission data from the RLC entity of the sending end through the status reporting process. 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 sending end, where the status report information carries the RLC identification information of the lost RLC SDU;

The RLC entity at the receiving end receives the RLC PDU corresponding to the RLC identification information of the lost RLC SDU sent by the RLC entity of the sending end.

The RLC entity at the receiving end may directly trigger the status reporting process when determining that there is a missing RLC SDU. If the RLC identification information is the RLC sequence number, the RLC entity at the receiving end may add the RLC sequence number of the lost RLC SDU to the sequence number list in the status report information to be sent to reacquire the lost RLC SDU.

In the related art, when re-acquiring data from the transmitting end, an ARQ (Automatic Repeat-reQuest) process is required, and the existing ARQ process feedback is too slow, so the embodiment of the present disclosure determines that there is a loss. When the RLC SDU is used, the status report process is triggered directly, which can make up for the slow feedback of the ARQ process in the related technology and shorten the time for obtaining the retransmitted data.

Way two

In mode 2, the RLC entity at the receiving end obtains the retransmitted data by using the backup data. Specifically, step 105 may include:

The RLC entity at the receiving end selects an RLC PDU corresponding to the RLC identification information of the lost RLC SDU from the backup data.

The backup data stores an RLC PDU received from an RLC entity at the transmitting end.

In this way, the retransmission data is directly selected from the backup data without being re-acquired from the RLC entity at the sending end, which can further shorten the time for obtaining the retransmitted data and implement fast retransmission.

Further, in order to prevent the receiving end from buffering too much data and affecting the performance of the receiving end, the RLC entity at the receiving end may delete the successfully transmitted data in the backup data. Specifically, after the step 102, the data transmission method may further include:

The RLC entity at the receiving end acquires the RLC identification information carried in the identifier report information;

The RLC entity at the receiving end deletes the RLC PDU corresponding to the obtained RLC identification information in the backup data, where the backup data stores an RLC PDU received from the RLC entity of the sending end.

In this way, the successfully transmitted data in the backup data is deleted in real time, which can prevent the receiving end from buffering too much data and improve the performance of the receiving end.

Referring to FIG. 3, an embodiment of the present disclosure further provides a data transmission method, which is applied to a PDCP entity at a receiving end, and includes the following steps:

Step 301: Receive an RLC SDU sent by an RLC entity at the receiving end.

The RLC identification information is used to carry the 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 data transmission method of the embodiment of the present disclosure is configured to receive the RLC SDU sent by the RLC entity at the receiving end, and the RLC identification information is used by the PDCP entity to determine that the RLC SDU carries the RLC identification information of the RLC SDU. The RLC SDU successfully sent by the RLC entity, so that the PDCP entity at the receiving end can determine the successfully transmitted RLC SDU and feed back to the RLC entity of the receiving end, so as to ensure that the PDCP entity at the receiving end successfully receives the data.

In the embodiment of the present disclosure, after the step 302, the data transmission method may further include:

The PDCP entity at the receiving end associates the PDCP identification information with the RLC identification information; wherein, if the identification information is a serial number, the PDCP entity at the receiving end may associate the PDCP serial number with the corresponding RLC serial number;

The PDCP entity at the receiving end generates the identifier report information, where the identifier report information carries the RLC identifier information associated with the PDCP identifier information corresponding to the PDCP PDU received by the PDCP entity; the RLC SDU sent by the RLC entity is PDCP PDU received by the PDCP entity;

Transmitting, by the PDCP entity at the receiving end, the identifier report information to the RLC entity;

The PDCP entity at the receiving end receives the RLC SDU corresponding to the RLC identification information of the lost RLC SDU retransmitted by the RLC entity.

In this way, the association between the PDCP identification information and the RLC identification information and the feedback of the identification report information can facilitate the RLC entity at the receiving end to determine whether there is a lost RLC SDU, and perform retransmission of the corresponding data when there is a lost RLC SDU. Ensure that the PDCP entity successfully receives data.

In the embodiment of the present disclosure, when generating the identifier report information, the PDCP entity at the receiving end can detect the packet loss in the transmission process of the air interface and the F1 interface by using the newly added receiving timer (t-Reception Timer), and generate a corresponding identifier. Report information. In this case, the identification information is a serial number, and the state variable (Reception_PDCP_RX_SN) that the receiving timer needs to check is a predetermined PDCP serial number, and the state variable is generated after each time the identification report information is generated, or after each time the identification report information is improved. Or increase by 1 after the timer expires. The duration of the receiving timer can be configured by higher layer signaling. For the same PDCP entity, there can be at most one receive timer running at the same time. When the PDCP entity is established, the initial value of the state variable of the receiving timer is zero.

Specifically, the process of the PDCP entity at the receiving end generating the identifier report information by using the receiving timer may be:

The PDCP entity at the receiving end triggers the receiving timer by using the check scheduled PDCP sequence number; at this time, the receiving timer is in the running state;

The PDCP entity at the receiving end receives or generates the PDCP PDU carrying the predetermined PDCP sequence number within the duration of the receiving timer, and generates or refines the identifier report information; wherein the identifier report information carries the predetermined information The RLC sequence number associated with the PDCP sequence number is used to notify the RLC entity that the RLC SDU (ie, PDCP PDU) corresponding to the RLC sequence number is successfully received; in this case, the state variable of the receiving timer is incremented by 1, stopping and Reset the receiving timer;

The PDCP entity at the receiving end does not receive the PDCP PDU carrying the predetermined PDCP sequence number when the receiving timer expires, but after receiving at least one PDCP PDU carrying the other PDCP sequence number and carrying the predetermined PDCP sequence number And the consecutive PDCP PDUs are arranged in ascending order of the PDCP sequence number, and the identifier report information is generated or improved; wherein the identifier report information carries an RLC sequence number associated with the other predetermined PDCP sequence numbers, and is used for The RLC SDU (ie PDCP PDU) corresponding to the RLC sequence number is notified to be successfully received by the RLC entity; for example, if the predetermined PDCP sequence number is 5 and the other received PDCP sequence numbers are 6 and 7. In this case, when the PDCP PDU carrying the predetermined PDCP sequence number is not received, if the receiving timer expires, the state variable of the receiving timer is incremented by 1, and the received PDCP sequence numbers are 6 and 7. The PDCP PDU generates or refines the identification report information; each time the identification report information is generated or refined, the state variable of the reception timer is incremented by 1, and when the state variable of the reception timer is incremented by 1, the reception timer is stopped and reset. . Therefore, after the above operation is completed, the reserved PDCP serial number becomes 8.

It should be noted that if the PDCP entity at 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 incremented by 1, and the receiving timer is stopped and reset. When the receiving timer is not running (including the case where the receiving timer is stopped), if there is at least one PDCP PDU in the buffer of the PDCP entity of the receiving end, the receiving timer is started. During the running of the receiving timer, if the duration of the receiving timer is reconfigured by the higher layer signaling, the receiving timer is stopped and restarted.

The above embodiment describes the data transmission method of the present disclosure. The RLC entity and the PDCP entity applied to the receiving end of the present disclosure will be described below with reference to the embodiments and the accompanying drawings.

As shown in FIG. 4, an embodiment of the present disclosure further provides an RLC entity, which is applied to a receiving end, and includes a processor 41, a sending interface 42, and a receiving interface 43.

The processor 41 is configured to determine RLC identification information that is sent by the RLC entity along with the RLC SDU.

The sending interface 42 is configured to send, to the PDCP entity of the receiving end, an RLC SDU, where the RLC SDU carries the RLC identification information of the RLC SDU, where the RLC identification information is used by the PDCP entity to determine the RLC. The RLC SDU that the entity successfully sent.

The RLC entity of the receiving end of the present disclosure sends the RLC SDU to the PDCP entity of the receiving end, and the RLC identification information is used by the PDCP entity to determine that the RLC SDU carries the RLC identification information of the RLC SDU. The RLC SDU successfully sent by the RLC entity, so that the PDCP entity at the receiving end can determine the successfully transmitted RLC SDU and feed back to the RLC entity of the receiving end, so as to ensure that the PDCP entity at the receiving end successfully receives the data.

In the embodiment of the present disclosure, the receiving interface 43 may be configured to receive the identifier report information that is sent by the PDCP entity, where the identifier report information carries the PDCP identifier information corresponding to the PDCP PDU received by the PDCP entity. Linked RLC identification information.

The processor 41 is further configured to determine, according to the identifier report information, whether there is a lost RLC SDU in the transmission process of the RLC SDU. When there is a lost RLC SDU, the RLC identification information of the lost RLC SDU is determined, and an RLC PDU corresponding to the RLC identification information of the lost RLC SDU is obtained.

The sending interface 42 is further configured to retransmit the RLC SDU to the PDCP entity.

Optionally, the processor 41 also triggers a status reporting process.

The sending interface 42 is further configured to send status report information to the RLC entity of the sending end, where the status report information carries the RLC identification information of the lost RLC SDU.

The receiving interface 43 is further configured to receive, by the RLC entity of the sending end, an RLC SDU corresponding to the RLC identification information of the lost RLC SDU.

Optionally, the processor 42 is further configured to: select, from the backup data, an RLC PDU corresponding to the RLC identifier information of the lost RLC SDU, where the backup data is stored in the RLC entity received from the sending end. RLC PDU.

Optionally, the processor 42 is further configured to obtain the RLC identifier information that is carried in the identifier report information, and delete the RLC PDU corresponding to the obtained RLC identifier information in the backup data, where the backup data is included in the backup data. The RLC PDU received from the RLC entity of the transmitting end is stored.

Optionally, the identifier 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, and bus 40 will include one or more processors represented by processor 41 and memory represented by memory 44. The various circuits are connected together. 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 via the bus 40.

The processor 41 is responsible for managing the bus 40 and the usual processing, and the memory 44 can be used to store data used by the processor 41 when performing operations.

As shown in FIG. 5, an embodiment of the present disclosure further provides a PDCP entity, which is applied to a receiving end, and includes a processor 51, a sending interface 52, and a receiving interface 53.

The receiving interface 53 is configured to receive the RLC SDU sent by the RLC entity of the receiving end, where the RLC SDU carries the 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 present disclosure receives the RLC SDU sent by the RLC entity of the receiving end, and the RLC identification information is used by the PDCP entity because the RLC SDU carries the RLC identification information of the RLC SDU. Determining the RLC SDU successfully sent by the RLC entity, so that the PDCP entity at the receiving end can determine the successfully transmitted RLC SDU and feed back to the RLC entity of the receiving end, so as to ensure that the PDCP entity at the receiving end correctly receives the data.

In the embodiment of the present disclosure, the processor 51 may be configured to associate the PDCP identification information with the RLC identification information to generate the identifier report information, where the identifier report information carries the PDCP received by the PDCP entity. The RLC identification information associated with the PDCP identification information corresponding to the PDU.

The sending interface 52 is configured to send the identifier report information to the RLC entity.

The receiving interface 53 is configured to receive an RLC SDU corresponding to the RLC identification information of the lost RLC SDU that is retransmitted by the RLC entity.

Optionally, the processor 51 is further configured to: use a predetermined PDCP sequence number to trigger a receiving timer; when the PDCP PDU carrying the predetermined PDCP sequence number is received within the duration of the receiving timer, generate the identifier. Reporting information, wherein the identifier report information carries an RLC sequence number associated with the predetermined PDCP sequence number; or, when the receiving timer expires, does not receive the PDCP carrying the predetermined PDCP sequence number The PDU, but after receiving at least one consecutive PDCP PDU that carries the PDCP PDU carrying the predetermined PDCP sequence number, is arranged in ascending order of the PDCP sequence number to generate or improve the identifier report information. The identifier report information carries an RLC sequence number associated with the other predetermined PDCP sequence numbers;

The state variable to be checked by the receiving timer is the predetermined PDCP sequence number, and the state variable is after each generation of the identifier report information, or after each improvement of the report report information, or after the receiving timer expires. Increase by 1.

In FIG. 5, a bus architecture (represented by bus 50), bus 50 may include any number of interconnected buses and bridges, and bus 50 will include one or more processors represented by processor 51 and memory represented by memory 54. The various circuits are connected together. Transmit interface 52 and receive interface 53 may be a transceiving interface, and transmit interface 52 and receive interface 53 may be coupled to processor 51 and memory 54 via bus 50.

The processor 51 is responsible for managing the bus 50 and the usual processing, and the memory 54 can be used to store data used by the processor 51 when performing operations.

In addition, an embodiment of the present disclosure further provides a receiving end, including a memory, a processor, and a data transmission program stored on the memory and operable on the processor, wherein the data transmission program is The steps in the data transmission method applied to the RLC entity and the PDCP entity described above may be implemented when the processor executes.

Specifically, as shown in FIG. 6, the embodiment of the present disclosure further provides a receiving end, and 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 the embodiment of the present disclosure, the receiving end further includes: a data transfer program stored on the memory 66 and operable on the processor 601. Specifically, when the data transfer program is executed by the processor 65, the following steps may be implemented. Determining the RLC identification information associated with the RLC SDU sent by the RLC entity, and sending the RLC SDU to the PDCP entity of the receiving end, where the RLC identification information is used for the RLC SDU. The PDCP entity determines the RLC SDU successfully sent by the RLC entity.

When the data transmission program is executed by the processor 65, the method further includes the following steps: receiving the identifier report information sent by the PDCP entity, where the identifier report information carries the PDCP corresponding to the PDCP PDU received by the PDCP entity. Determining, according to the identifier report information, whether there is a lost RLC SDU in the transmission process of the RLC SDU, and if there is a lost RLC SDU, determining the RLC identifier of the lost RLC SDU. And obtaining an RLC PDU corresponding to the RLC identification information of the lost RLC SDU, and retransmitting the RLC PDU to the PDCP entity.

Optionally, when the data transmission program is executed by the processor 65, the following steps are further implemented: triggering a status reporting process and controlling the transceiver 62 to send status report information to the RLC entity of the sending end, where the status report information carries The RLC identification information of the lost RLC SDU is controlled, and the control transceiver 62 receives the RLC PDU corresponding to the RLC identification information of the lost RLC SDU sent by the RLC entity of the sending end.

Optionally, when the data transmission program is executed by the processor 65, the method further includes: selecting, from the backup data, an RLC PDU corresponding to the RLC identification information of the lost RLC SDU, where the backup data is stored The RLC PDU received from the RLC entity at the transmitting end.

Optionally, when the data transmission program is executed by the processor 65, the following steps are performed: acquiring the RLC identification information carried in the identifier report information, and deleting the RLC PDU corresponding to the obtained RLC identifier information in the backup data. And storing, in the backup data, an RLC PDU received from an RLC entity at the transmitting end.

Optionally, the identifier information is a serial number.

Specifically, when the data transmission program is executed by the processor 65, the following steps may be implemented: receiving an RLC SDU sent by the RLC entity of the receiving end, where the RLC SDU carries the RLC identification information of the RLC SDU, The RLC identification information is used by the PDCP entity to determine an RLC SDU successfully sent by the RLC entity.

Optionally, when the data transmission program is executed by the processor 65, the following steps are further performed: associating the PDCP identification information with the RLC identification information to generate identifier report information, where the identifier report information carries And the RLC identification information associated with the PDCP identifier information corresponding to the PDCP PDU received by the PDCP entity, and the identifier report information is sent to the RLC entity, and the RLC identifier information corresponding to the lost RLC SDU that is retransmitted by the RLC entity is received. RLC SDU.

Optionally, when the data transmission program is executed by the processor 65, the method further includes: triggering, by using a predetermined PDCP sequence number, a receiving timer, if the predetermined PDCP serial number is received within the duration of the receiving timer The PDCP PDU is configured to generate the identifier report information, where the identifier report information carries an RLC sequence number associated with the predetermined PDCP sequence number, and if the subscription timer expires, the bearer is not received. a PDCP PDU of a PDCP sequence number, but receiving at least one PDCP PDU that carries other PDCP sequence numbers after the PDCP PDU carrying the predetermined PDCP sequence number, is arranged in ascending order of the PDCP sequence number, generates or refines the And the identifier report information, where the identifier report information carries an RLC sequence number associated with the other predetermined PDCP sequence numbers, and the state variable checked by the receiving timer is the predetermined PDCP sequence number, and the receiving timing is The state variable of the device is incremented by one after each generation of the identification report information or after each improvement of the identification report information or after the reception timer expires.

In Figure 6, a bus architecture (represented by bus 61), bus 61 may include any number of interconnected buses and bridges, and bus 61 will include one or more processors represented by processor 65 and memory represented by memory 66. The various circuits are linked together. The bus 61 can also link various other circuits, such as peripherals, voltage regulators, and power management circuits, as is known in the art, and therefore, will not be further described herein. Bus interface 64 provides an interface between bus 61 and transceiver 62. Transceiver 62 can be an element or a plurality of elements, such as multiple receivers and transmitters, providing means for communicating with various other devices on a transmission medium. Data processed by processor 65 is transmitted over the wireless medium via antenna 63. Further, antenna 63 also receives the data and transmits the data to processor 65.

The processor 65 is responsible for managing the bus 61 and the usual processing, and can also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. The memory 66 can be used to store data used by the processor 65 when performing operations.

Alternatively, the processor 65 may be a CPU, an ASIC, an FPGA, or a CPLD.

The embodiment of the present disclosure further provides a computer readable storage medium, where a data transmission program is stored, and the data transmission program is executed by a processor to implement various processes of the foregoing data transmission method embodiment, and can achieve the same technology. The effect, to avoid repetition, will not be repeated here.

Specifically, when the data transmission procedure is executed by the processor, the following steps may be implemented: sending an RLC SDU to the PDCP entity of the receiving end, where the RLC identifier is accompanied by the RLC identifier of the RLC SDU. The information is used by the PDCP entity to determine an RLC SDU successfully sent by the RLC entity.

When the data transmission program is executed by the processor, the following steps may be implemented: receiving the identifier report information sent by the PDCP entity, where the identifier report information carries the PDCP corresponding to the PDCP PDU received by the PDCP entity. Determining, according to the identifier report information, whether there is a lost RLC SDU in the transmission process of the RLC SDU, and if there is a lost RLC SDU, determining the RLC identifier of the lost RLC SDU. And obtaining an RLC PDU corresponding to the RLC identifier information of the lost RLC SDU, and retransmitting the RLC SDU to the PDCP entity.

Optionally, when the data transmission program is executed by the processor, the following steps may be implemented: triggering a status reporting process and sending status report information to the RLC entity of the sending end, where the status report information carries the lost RLC The RLC identification information of the SDU receives the RLC SDU corresponding to the RLC identification information of the lost RLC SDU sent by the RLC entity of the sending end.

Optionally, when the data transmission program is executed by the processor, the method further includes: selecting, from the backup data, an RLC PDU corresponding to the RLC identification information of the lost RLC SDU, where the backup data stores The RLC PDU received by the RLC entity at the transmitting end.

Optionally, when the data transmission program is executed by the processor, the following steps are performed: acquiring the RLC identification information carried in the identifier report information, and deleting the RLC PDU corresponding to the obtained RLC identifier information in the backup data, The backup data stores an RLC PDU received from an RLC entity at the transmitting end.

Optionally, the identifier information is a serial number.

Specifically, when the data transmission program is executed by the processor, the following steps are performed: receiving an RLC SDU sent by the RLC entity of the receiving end, where the RLC identifier is accompanied by the RLC identifier of the RLC SDU. The information is used by the PDCP entity to determine an RLC SDU successfully sent by the RLC entity.

Optionally, when the data transmission program is executed by the processor, the following steps are further performed: associating the PDCP identification information with the RLC identification information to generate the identifier report information, where the identifier report information carries the The RLC identification information associated with the PDCP identification information corresponding to the PDCP PDU received by the PDCP entity, and the identifier report information is sent to the RLC entity, and the RLC identifier information corresponding to the lost RLC SDU that is retransmitted by the RLC entity is received. RLC SDU.

Optionally, when the data transmission program is executed by the processor, the method further includes: triggering a receiving timer by using a predetermined PDCP sequence number, and receiving a PDCP carrying the predetermined PDCP sequence number within a duration of the receiving timer The PDU, the identifier report information is generated, where the identifier report information carries an RLC sequence number associated with the predetermined PDCP sequence number, and if the receiving timer expires, the predetermined PDCP is not received. a PDCP PDU of the serial number, but receiving at least one PDCP PDU that carries the PDCP PDU carrying the predetermined PDCP sequence number and consecutive PDCP PDUs, arranged in ascending order of the PDCP sequence number, generating or perfecting the identifier Reporting information, wherein the identifier report information carries an RLC sequence number associated with the other predetermined PDCP sequence number, and the state variable checked by the receiving timer is the predetermined PDCP sequence number, and the receiving timer The state variable is incremented by one after each generation of the identification report information or after each improvement of the identification report information or after the reception timer expires.

Computer readable media includes both permanent and non-persistent, removable and non-removable media, and information storage can be implemented by any method or technology. The information can be computer readable instructions, data structures, modules of programs, 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 disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary storage of computer readable media, such as modulated data signals and carrier waves.

It is to be understood that the term "comprises", "comprising", or any other variants thereof, is intended to encompass a non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes those elements. It also includes other elements that are not explicitly listed, or elements that are inherent to such a process, method, article, or device. An element that is defined by the phrase "comprising a ..." does not exclude the presence of additional equivalent elements in the process, method, item, or device that comprises the element.

The above-mentioned serial numbers of the embodiments of the present disclosure are merely for the description, and do not represent the advantages and disadvantages of the embodiments.

Through the description of the above embodiments, those skilled in the art can clearly understand that the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is better. Implementation. Based on such understanding, portions of the technical solution of the present disclosure that contribute substantially or to the prior art may be embodied in the form of a software product stored in a storage medium (eg, ROM/RAM, disk, The optical disc includes a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the methods described in various embodiments of the present disclosure.

The above description is only a preferred embodiment of the present disclosure, and it should be noted that those skilled in the art can also make several improvements and retouchings without departing from the principles of the present disclosure. It should be considered as the scope of protection of this disclosure.

Claims (20)

A data transmission method is applied to a radio link control RLC entity at a receiving end, including: Transmitting, by the packet data convergence protocol PDCP entity of the receiving end, an RLC service data unit (SDU), wherein the RLC SDU carries the RLC identification information of the RLC SDU, where the RLC identification information is used by the PDCP entity to determine the RLC The RLC SDU that the entity successfully sent. The method of claim 1, wherein after the RLC SDU is sent to the PDCP entity at the receiving end, the method further comprises: Receiving, by the PDCP entity, the identifier report information, where the identifier report information carries the RLC identifier information associated with the PDCP identifier information corresponding to the PDCP protocol data unit PDU received by the PDCP entity; Determining, according to the identifier report information, whether there is a lost RLC SDU in the transmission process of the RLC SDU; Determining RLC identification information of the lost RLC SDU if there is a lost RLC SDU; Obtaining an RLC PDU corresponding to the RLC identification information of the lost RLC SDU; Retransmitting the RLC SDU to the PDCP entity. The method of claim 2, wherein the obtaining the RLC PDU corresponding to the RLC identification information of the lost RLC SDU comprises: The status report process is triggered, and the status report information is sent to the RLC entity of the sending end, where the status report information carries the RLC identification information of the lost RLC SDU; Receiving, by the RLC entity of the sending end, an RLC PDU corresponding to the RLC identification information of the lost RLC SDU. The method of claim 2, wherein the obtaining the RLC PDU corresponding to the RLC identification information of the lost RLC SDU comprises: The RLC PDU corresponding to the RLC identification information of the lost RLC SDU is selected from the backup data, where the backup data stores an RLC PDU received from the RLC entity of the sending end. The method of claim 2, wherein after the receiving the identifier report information sent by the PDCP entity, the method further comprises: Obtaining the RLC identification information carried in the identifier report information; And deleting the RLC PDU corresponding to the obtained RLC identification information in the backup data, where the backup data stores an RLC PDU received from the RLC entity of the sending end. The method according to any one of claims 1 to 5, wherein the identification information is a serial number. A data transmission method is applied to a PDCP entity at a receiving end, including: Receiving, by the RLC SDU, the RLC SDU sent by the RLC entity of the receiving end, wherein the RLC SDU carries the 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 method of claim 7, wherein after the receiving the RLC SDU sent by the RLC entity of the receiving end, the method further comprises: Associating PDCP identification information with the RLC identification information; Generating the identifier report information, where the identifier report information carries the RLC identifier information associated with the PDCP identifier information corresponding to the PDCP PDU received by the PDCP entity; Sending the identification report information to the RLC entity; Receiving an RLC SDU corresponding to the RLC identification information of the lost RLC SDU retransmitted by the RLC entity. The method of claim 8, wherein the identification information is a serial number, and the generating the identification report information comprises: Triggering a reception timer by using a predetermined PDCP sequence number; And generating the identifier report information, where the identifier report information is associated with the predetermined PDCP sequence number, if the PDCP PDU carrying the predetermined PDCP sequence number is received within the duration of the receiving timer. RLC serial number; If the PDCP PDU carrying the predetermined PDCP sequence number is not received when the receiving timer expires, but after receiving at least one PDCP PDU carrying the other PDCP sequence number after carrying the predetermined PDCP sequence number, and continuing The PDCP PDUs are arranged in an ascending order of the PDCP sequence number to generate or refine the identifier report information, where the identifier report information carries an RLC sequence number associated with the other predetermined PDCP sequence numbers; The state variable of the receiving timer check is the predetermined PDCP sequence number, and the state variable is incremented by one after each generation of the identifier report information or after each improvement of the identifier report information or after the receiving timer expires. An RLC entity is applied to a receiving end, including a processor and a sending interface; The processor is configured to determine RLC identification information associated with the RLC SDU sent by the RLC entity; The sending interface is configured to send, to the PDCP entity of the receiving end, an RLC SDU, where the RLC SDU carries the RLC identification information of the RLC SDU, where the RLC identification information is used by the PDCP entity to determine the RLC entity. Successfully sent RLC SDU. The RLC entity according to claim 10, wherein the RLC entity further comprises a receiving interface; The receiving interface is configured to receive the identifier report information that is sent by the PDCP entity, where the identifier report information carries the RLC identifier information associated with the PDCP identifier information corresponding to the PDCP PDU received by the PDCP entity; The processor is further configured to determine, according to the identifier report information, whether there is a lost RLC SDU in the transmission process of the RLC SDU, and determine, when there is a lost RLC SDU, the RLC identifier information of the lost RLC SDU. Obtaining an RLC PDU corresponding to the RLC identification information of the lost RLC SDU; The sending interface is further configured to retransmit the RLC SDU to the PDCP entity. The RLC entity of claim 11 wherein: The processor is further configured to trigger a status reporting process; The sending interface is further configured to send the status report information to the RLC entity of the sending end, where the status report information carries the RLC identification information of the lost RLC SDU; The receiving interface is further configured to receive, by the RLC entity of the sending end, an RLC PDU corresponding to the RLC identification information of the lost RLC SDU. The RLC entity of claim 11 wherein: The processor is further configured to select, from the backup data, an RLC PDU corresponding to the RLC identification information of the lost RLC SDU, where the backup data stores an RLC PDU received from an RLC entity of the sending end. The RLC entity of claim 11 wherein: The processor is further configured to obtain the RLC identification information carried in the identifier report information, and delete the RLC PDU corresponding to the obtained RLC identifier information in the backup data, where the backup data is stored in the backup data. RLC PDU received by the RLC entity. The RLC entity according to any one of claims 10 to 14, wherein the identification information is a serial number. A PDCP entity is applied to a receiving end, including a receiving interface; The receiving interface is configured to receive an RLC SDU that is sent by the RLC entity of the receiving end, where the RLC SDU carries the RLC identification information of the RLC SDU, and the RLC identification information is used by the PDCP entity to determine the RLC. The RLC SDU that the entity successfully sent. The PDCP entity of claim 16, wherein the PDCP entity further comprises a processor and a transmit interface; The processor is configured to associate the PDCP identification information with the RLC identification information to generate the identifier report information, where the identifier report information is associated with the PDCP identifier information corresponding to the PDCP PDU received by the PDCP entity. RLC identification information; The sending interface is configured to send the identifier report information to the RLC entity; The receiving interface is further configured to receive an RLC SDU corresponding to the RLC identification information of the lost RLC SDU that is retransmitted by the RLC entity. The PDCP entity of claim 17 wherein: The processor is further configured to: trigger a receiving timer by using a predetermined PDCP sequence number; and generate the identifier report information when receiving a PDCP PDU carrying the predetermined PDCP sequence number within a duration of the receiving timer, where The identifier report information carries an RLC sequence number associated with the predetermined PDCP sequence number; or, when the receiving timer expires, the PDCP PDU carrying the predetermined PDCP sequence number is not received, but is received Generating or refining the identification report information according to the PDCP sequence number in ascending order when at least one PDCP PDU following the PDCP PDU carrying the predetermined PDCP sequence number carrying other PDCP sequence numbers is arranged in an ascending order. The report information carries an RLC serial number associated with the other predetermined PDCP serial number; The state variable of the receiving timer check is the predetermined PDCP sequence number, and the state variable is incremented by one after each generation of the identifier report information or after each improvement of the identifier report information or after the receiving timer expires. A receiving end comprising a memory, a processor, and a data transfer program stored on the memory and operable on the processor, wherein the data transfer program is implemented by the processor as claimed in claim 1 The steps in the data transmission method according to any one of the preceding claims. A computer readable storage medium having stored thereon a data transfer program, wherein the data transfer program is executed by a processor to implement the steps of the data transfer method according to any one of claims 1 to 9.

Images