CN101729524B - Data processing method, data processing device, RLC entity and PDCP entity - Google Patents

Data processing method, data processing device, RLC entity and PDCP entity Download PDF

Info

Publication number
CN101729524B
CN101729524B CN200810225500XA CN200810225500A CN101729524B CN 101729524 B CN101729524 B CN 101729524B CN 200810225500X A CN200810225500X A CN 200810225500XA CN 200810225500 A CN200810225500 A CN 200810225500A CN 101729524 B CN101729524 B CN 101729524B
Authority
CN
China
Prior art keywords
pdcp
data
rlc
pdu
entity
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
CN200810225500XA
Other languages
Chinese (zh)
Other versions
CN101729524A (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 Academy of Telecommunications Technology CATT
Datang Mobile Communications Equipment Co Ltd
Original Assignee
China Academy of Telecommunications Technology CATT
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 Academy of Telecommunications Technology CATT filed Critical China Academy of Telecommunications Technology CATT
Priority to CN200810225500XA priority Critical patent/CN101729524B/en
Publication of CN101729524A publication Critical patent/CN101729524A/en
Application granted granted Critical
Publication of CN101729524B publication Critical patent/CN101729524B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Mobile Radio Communication Systems (AREA)

Abstract

The invention provides a data processing method, a data processing device, an RLC entity and a PDCP entity. The method comprises that: the radio link control RLC entity transmits data from the packet data convergence protocol PDCP entity and then transmits a data transmission notice to the PDCP entity; and the PDCP entity receives the data transmission notice, searches for the corresponding data from the cached data of the PDCP entity according to the data transmission notice and deletes the searched data. The data processing method is favorable for saving a storage space of the PDCP entity and improving the utilization ratio of the memory resources of the PDCP entity.

Description

Data processing method, device, RLC entity and PDCP entity
Technical Field
The present invention relates to network communication technologies, and in particular, to a data processing method and apparatus, a Radio Link Control (RLC) entity, and a Packet Data Convergence Protocol (PDCP) entity.
Background
At present, in a network communication technology, in order to ensure the effectiveness of data transmission, generally, after a PDCP layer, specifically, a PDCP entity receives a PDCP Service Data Unit (SDU) from an upper layer, the PDCP entity stores the PDCP SDU, where the PDCP SDU is a data transport block on a corresponding transport channel, where the PDCP entity stores the PDCP SDU, and its purpose is to send the received data according to an indication of a bottom layer, and if the bottom layer sends an indication that PDCP SDU information (which carries a sequence number of the PDCP SDU) is needed to the PDCP entity, the PDCP entity searches for the corresponding PDCP SDU in the stored PDCP SDU, and then a specific processing method can be referred to fig. 1, where fig. 1 is a flowchart of an existing data processing method, as shown in fig. 1, the process includes the following steps:
step 101, the PDCP entity starts a discard timer corresponding to the PDCP SDU.
Before executing step 101, the PDCP entity may determine each PDCP SDU to be received in advance, and then set a corresponding discard timer for each PDCP SDU, so that step 101 specifically includes: after the PDCP entity stores the currently received PDCP SDU, the discard timer corresponding to the PDCP SDU is started.
In step 102, the PDCP entity converts the PDCP SDU into a corresponding PDCP Protocol Data Unit (PDU), and sends the PDCP PDU to the RLC.
Here, the PDCP entity transforms the PDCP PDU into a corresponding PDCP PDU according to a transformation rule specified in the PDCP protocol, where the PDCP PDU is a data block used for transmission by the PDCP entity, and thus the RLC, specifically the RLC entity, receives a PDCP PDU from the PDCP entity (generally, when the PDCP PDU reaches the RLC, the PDCP PDU is referred to as an RLC SDU), and stores the received PDCP PDU.
It should be noted that, after the RLC entity receives the PDCP PDU, the RLC entity may also send the PDCP PDU, which may specifically be: the RLC entity firstly converts the PDCP PDU to be sent into the corresponding RLC PDU according to the protocol rule and then sends the RLC PDU.
Step 103, the PDCP entity determines whether the started discard timer exceeds a preset time, if so, deletes all PDCP SDUs corresponding to the discard timer stored in step 101, and executes step 104, otherwise, the PDCP entity continues to determine whether the started discard timer is overtime, until the PDCP entity determines that the started discard timer is overtime.
Here, the preset time of the discard timer depends on a network delay between the PDCP entity and the RLC entity.
Step 104, the PDCP entity carries the deleted PDCP SDU information in a deletion notification and sends the deletion notification to the RLC entity.
Here, the deleted PDCP SDU information may include: and the deleted PDCP SDU corresponds to the sequence number.
Step 105, the RLC entity receives the deletion notification, searches the PDCP PDU which corresponds to the PDCP SDU information in the deletion notification and does not form the RLC PDU in the received data, and deletes the searched PDCP PDU.
In this way, the RLC entity stops transmission of the PDCP pdu corresponding to the PDCP SDU information in the erasure notification.
It can be seen that, in the data processing flow in the prior art, after the PDCP entity receives the PDCP SDU, the related information of the PDCP SDU needs to be stored until it is determined that the started corresponding discard timer is expired. Thus, there is a problem that if the PDCP entity receives a PDCP SDU from an upper layer, it immediately forms a PDCP PDU and sends the PDCP PDU to the RLC entity, the RLC entity quickly forms a total time of 50ms for sending the RLC PDU, and the preset time length of the discard timer is 1500ms, so that, by using the data processing method in the prior art, the PDCP entity will store 1500-50 ms more for the PDCP SDU, which is 1450ms, and thus, memory resources of the PDCP entity are greatly wasted.
Disclosure of Invention
The invention provides a data processing method, a data processing device, an RLC entity and a PDCP entity, so as to improve the utilization rate of memory resources of the PDCP entity.
A method of data processing, the method comprising:
after sending data from a PDCP entity, the RLC sends a data transmission notice to the PDCP;
and the PDCP receives the data transmission notice, searches corresponding data in the data cached by the PDCP according to the data transmission notice, and deletes the searched data.
A data processing apparatus comprising: an RLC entity and a PDCP entity, wherein,
after the RLC entity sends data from a PDCP entity, sending a data transmission notice to the PDCP entity;
and the PDCP entity receives the data transmission notice, searches corresponding data in the data cached by the PDCP entity according to the data transmission notice, and deletes the searched data.
An RLC entity, comprising: a receiving unit and a transmitting unit; wherein,
the data receiving unit is used for receiving data from a PDCP entity;
the sending unit is configured to send the data received by the data receiving unit, and send a data transmission notification to the PDCP entity after sending the data.
A PDCP entity, comprising: a notification receiving unit and a processing unit; wherein,
the notification receiving unit is used for receiving a data transmission notification sent by an RLC entity;
the processing unit is used for searching corresponding data in the data cached by the processing unit according to the data transmission notice and deleting the searched data.
In the above technical solution, in the data processing method, the apparatus, the RLC entity and the PDCP entity provided by the present invention, after data from the PDCP is sent by the RLC, a data transmission notification is sent to the PDCP; and the PDCP receives the data transmission notice, searches corresponding data in the data cached by the PDCP according to the data transmission notice, and deletes the searched data. The RLC sends the data transmission notice to the PDCP in time after sending the data from the PDCP, so that compared with the prior art, the PDCP can be ensured to know the data sending condition of the RLC in time, the PDCP can delete the corresponding data stored in the PDCP in time according to the known data sending condition of the RLC, the storage space of the PDCP is saved, and the utilization rate of the memory resource of the PDCP is improved.
Drawings
FIG. 1 is a flow chart of a data processing method in the prior art;
FIG. 2 is a basic flowchart of a data processing method according to an embodiment of the present invention;
FIG. 3 is a detailed flowchart of a data processing method according to an embodiment of the present invention;
FIG. 4 is a block diagram of a data processing apparatus according to an embodiment of the present invention;
fig. 5 is a structural diagram of an RLC entity according to an embodiment of the present invention;
fig. 6 is a structure of a PDCP entity according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in detail with reference to the accompanying drawings and specific embodiments.
The data processing method provided by the present invention is applied between PDCP and RLC, and establishes a connection between PDCP and RLC, as shown in fig. 2, fig. 2 is a basic flow chart of the data processing method provided by the embodiment of the present invention, as shown in fig. 2, the method mainly includes the following steps:
in step 201, the RLC transmits data from the PDCP.
In step 202, the RLC sends a data transmission notification to the PDCP.
In step 203, the PDCP entity receives the data transmission notification, searches for corresponding data in the data cached in the PDCP entity according to the data transmission notification, and deletes the searched data.
The above-mentioned method provided by the present invention is described in detail below with reference to specific examples.
Fig. 3 is a detailed flowchart of a data processing method according to an embodiment of the present invention. In this embodiment, the RLC operating mode may have various forms, such as an acknowledged mode or an unacknowledged mode, and the present embodiment takes the RLC operating mode as the acknowledged mode, and after the PDCP layer receives PDCP SDUs from a higher layer, the higher layer refers to an application layer because the PDCP layer only exists in a user interface, as shown in fig. 3, the process may include the following steps:
in step 301, the PDCP buffer stores the received PDCP SDU.
Specifically, step 301 may buffer the received PDCP SDUs for the PDCP entity.
Step 302, the PDCP converts the PDCP SDU into corresponding PDCP PDU, and sends the PDCP PDU to the RLC.
In this embodiment, the PDCP may segment or concatenate the PDCP SDU to form a PDCP PDU corresponding to the PDCP SDU, and specifically, the PDCP SDU may be transformed into the corresponding PDCP PDU according to a transformation method in the prior art, which is not described herein again.
Specifically, step 302 can transform the PDCP SDU into a corresponding PDCP PDU for PDCP, and transmit the PDCP PDU to the RLC entity.
In step 303, the RLC receives the PDCP PDU and transforms the PDCP PDU into a corresponding RLC PDU.
In this embodiment, the RLC may segment or concatenate the PDCP PDU to form an RLC PDU corresponding to the PDCP PDU, and specifically, the PDCP PDU may be transformed into the corresponding RLC PDU according to a transformation method in the prior art, which is not described herein again.
In this embodiment, the number of the PDCP PDUs converted into the corresponding RLC PDUs may be one or multiple, which is not limited in this embodiment.
In step 304, the RLC sends RLC PDUs to the peer.
Here, the opposite end may be an end that needs to receive RLC PDUs transmitted from the RLC, and may also be an RLC corresponding to another cell.
In this step, if the number of the PDCP PDUs converted into the corresponding RLC PDUs is one, the RLC sends the whole RLC PDU to the opposite terminal; if the number of the PDCP PDUs transformed into the corresponding RLC PDUs is multiple, the RLC can sequentially send the RLC PDUs to the opposite terminal.
In step 305, the RLC determines whether the currently transmitted RLC PDU is successfully received by the peer end, if so, executes step 306, otherwise, ends the procedure.
Here, since the operation mode of the RLC in this embodiment is an acknowledged mode, the RLC needs to determine whether the currently transmitted RLC PDU is successfully received by the peer end, specifically, the operation of the RLC determining whether the currently transmitted RLC PDU is successfully received by the peer end may include: if the opposite terminal receives the RLC PDU sent by the RLC, sending a confirmation notice to the RLC, judging that the currently sent RLC PDU is successfully received by the opposite terminal when the RLC receives the confirmation notice within the preset time, otherwise, judging that the currently sent RLC PDU is not successfully received by the opposite terminal, and ending the process.
In this embodiment, if the RLC operation mode is the unacknowledged mode, step 305 may be omitted.
In step 306, the RLC sends a data transmission notification to the PDCP.
Here, the data transmission notification includes all PDCP PDU information corresponding to the RLC PDU currently transmitted by the RLC, where the PDCP PDU information may be a sequence number corresponding to the PDCP PDU.
Step 307, the PDCP receives the data transmission notification, and obtains all PDCP PDU information corresponding to the rlc PDU included in the data transmission notification.
Step 308, the PDCP searches the PDCP SDUs buffered in itself according to the sequence number corresponding to the PDCP PDU contained in the PDCP PDU information.
In step 309, the PDCP deletes the found PDCP SDU.
Thus, the flow of the data processing method provided by the embodiment is realized.
Preferably, in this embodiment, when the working mode of the RLC is the acknowledged mode, step 308 may further determine whether sequence numbers corresponding to PDCP PDUs included in the PDCP PDU information provided by the RLC are consecutive, and if so, may continue to perform the operation of searching for corresponding PDCP SDUs in the PDCP SDUs cached by itself; otherwise, the operation of searching the corresponding PDCP SDU in the PDCP SDU buffered by the RLC is not executed until the sequence numbers corresponding to the PDCP PDUs contained in the PDCP PDU information provided by the RLC are continuous. Certainly, in this embodiment, the PDCP may also directly search the PDCP SDU in the PDCP SDU cached by the PDCP SDU after receiving the sequence number corresponding to the PDCP PDU included in the PDCP PDU information provided by the RLC, which is not limited in this embodiment.
It should be noted that, in order to further improve the memory resource utilization of the PDCP, in this embodiment, step 301 may be replaced with: the PDCP buffers the received PDCP SDU and starts a timer corresponding to the PDCP SDU. The step 301 after replacement may specifically be that the PDCP buffers the received PDCP sdu and starts an idle timer in a timer preset in the PDCP pdu; or, the PDCP buffer buffers the received PDCP SDU, and creates and starts a timer corresponding to the received PDCP SDU when the timer corresponding to the received PDCP SDU does not currently exist.
In addition, before the operation of receiving the data transmission notification in step 307, the PDCP further needs to determine in real time whether the started timer does not exceed a preset time, if so, after receiving the data transmission notification, execute the operation of obtaining all PDCP PDUs corresponding to the RLC PDUs included in the data transmission notification in step 307, and searching all PDCP SDUs corresponding to the PDCP PDUs in the PDCP SDUs cached in step 308, and deleting the searched PDCP SDUs, otherwise, process the PDCP SDUs corresponding to the overtime timer according to the method in the prior art. The other steps are not changed and are not described in detail here.
The above is a detailed description of the method provided by the present invention, and the following is a description of the data processing apparatus provided by the present invention. Fig. 4 is a structural diagram of a data processing apparatus according to an embodiment of the present invention, and as shown in fig. 4, the apparatus includes: an RLC entity 401 and a PDCP entity 402.
After sending the data from the PDCP entity 402, the RLC entity 401 sends a data transmission notification to the PDCP entity 402.
The PDCP entity 402 receives the data transmission notification, searches for corresponding data in the data cached in itself according to the data transmission notification, and deletes the searched data.
Preferably, the RLC entity can be implemented in various structures. Referring to fig. 5, fig. 5 is a detailed structural diagram of an RLC entity, which may include, as shown in fig. 5: a data receiving unit 501 and a transmitting unit 502.
The data receiving unit 501 is configured to receive data from a PDCP entity.
The sending unit 502 is configured to send the data received by the data receiving unit 501, and send a data transmission notification to the PDCP entity after sending the data.
Preferably, the data receiving unit 501 may receive PDCP PDUs from the PDCP entity.
As shown by the dotted line in fig. 5, the RLC entity may further include: a first transformation unit 503.
The first transforming unit 503 is configured to transform the PDCP PDUs received by the data receiving unit 501 into corresponding RLC PDUs.
The transmitting unit 502 transmits the RLC PDU.
Preferably, if the current operation mode is the acknowledged mode, as shown by the dotted line in fig. 5, the RLC entity further includes: a judging unit 504.
The determining unit 504 is configured to determine whether the currently transmitted RLC PDU is successfully received by the peer end, and if so, send a success notification to the sending unit 502.
After receiving the success notification, the sending unit 502 sends a data transmission notification to the PDCP entity.
Wherein, the data transmission notice contains PDCP PDU corresponding to RLC PDU currently transmitted.
When the PDCP entity is implemented, there may be various structures. Referring to fig. 6, fig. 6 is a specific structural diagram of a PDCP entity, which, as shown in fig. 6, may include: a notification receiving unit 601 and a processing unit 602.
The notification receiving unit 601 is configured to receive a data transmission notification sent by an RLC entity.
The processing unit 602 is configured to search for corresponding data in the data cached in the processing unit according to the data transmission notification, and delete the searched data.
Preferably, the notification receiving unit is further configured to receive a PDCP service data unit SDU from a higher layer; wherein the high layer may be an application layer in a user interaction interface.
As shown by the dotted line in fig. 6, the PDCP entity may further include: a buffer unit 603 and a second transformation unit 604.
Wherein, the buffer unit 603 is configured to store the PDCP SDU received by the notification receiving unit 601.
The second transforming unit 604 is configured to transform the PDCP SDU received by the notification receiving unit into a corresponding PDCP protocol data unit PDU, and transmit the PDCP PDU to the RLC entity.
Preferably, the data transmission notification includes PDCP PDU information corresponding to an RLC PDU sent by an RLC entity, where the PDCP PDU information includes a sequence number corresponding to a PDCP PDU.
The processing unit may include: an acquisition sub-unit 6021 and a processing sub-unit 6022.
The obtaining subunit 6021 is configured to obtain PDCP PDU information corresponding to the RLC PDU included in the data transmission notification.
The processing subunit 6022 searches all corresponding PDCP SDUs from the PDCP SDUs stored in the buffer 603 according to the sequence number corresponding to the PDCP PDU contained in the PDCP PDU information acquired by the acquiring subunit 6021, and deletes the searched PDCP SDUs.
Preferably, as shown by the dotted line in fig. 6, the PDCP entity further comprises: a creation unit 605, a control unit 606, and a timer 607.
Wherein, the creating unit 605 is configured to create the PDCP SDU corresponding to the received PDCP SDU when there is no timer corresponding to the PDCP SDU received by the notifying receiving unit 601 currently.
When the buffer unit stores the PDCP SDU, the control unit 606 starts the timer corresponding to the PDCP SDU created by the creation unit 605, and before the notification receiving unit receives the data transmission notification, it determines in real time whether the started timer does not exceed a preset time, if so, after the notification receiving unit 601 receives the data transmission notification, it triggers the operation of the acquiring subunit 6021 to acquire the PDCP PDU corresponding to the transmitted RLC PDU contained in the data transmission notification, and controls the timer 60 to stop, otherwise, it sends the processing notification to the processing subunit.
The processing sub-unit 6022 directly deletes the PDCP SDU corresponding to the expired timer according to the method in the prior art.
As can be seen from the above description, in the data processing method, apparatus, RLC entity and PDCP entity provided in the present invention, after data from the PDCP entity is sent through the RLC, a data transmission notification is sent to the PDCP entity; and the PDCP receives the data transmission notice, searches corresponding data in the data cached by the PDCP according to the data transmission notice, and deletes the searched data. The RLC sends the data transmission notice to the PDCP in time after sending the data from the PDCP, so that compared with the prior art, the PDCP can be ensured to know the data sending condition of the RLC in time, the PDCP can delete the corresponding data stored in the PDCP in time according to the known data sending condition of the RLC, the storage space of the PDCP is saved, and the utilization rate of the memory resource of the PDCP is improved.
For example, if the PDCP entity receives a PDCP SDU from the higher layer, it immediately forms a PDCP PDU to be sent to the RLC, the RLC quickly forms an RLC PDU and sends the RLC PDU out with a total time of 50ms, and the preset time length of the discard timer is 1500ms, so that, assuming that the current service is a high-speed service and its speed is 9Mbps, a 9Mbits service will be received within 1s, if the PDCP entity can quickly send out the service data, if the method of the prior art is adopted, the storage capacity of the PDCP entity needs at least >1 mbyte, and if the method of the present invention is adopted, the buffer information of the PDCP SDU is adjusted by the data sending condition timely known by the RLC entity, then the buffer capacity of the PDCP entity can be reduced to about 9Mbits x 50ms — 56 kbytes. Compared with the prior art, the invention can greatly save the PDCP, particularly the storage space of the PDCP entity, improve the utilization rate of the memory resource of the PDCP entity, and is easier for the base station side to simultaneously process a plurality of UE.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.

Claims (10)

1. A method of data processing, the method comprising:
the PDCP buffers the received packet data convergence protocol PDCP service data unit SDU, converts the PDCP SDU into a corresponding PDCP protocol data unit PDU, and sends the PDCP PDU to a radio link control RLC;
the working mode of the RLC is an unacknowledged mode, the RLC converts the PDCP PDU into a corresponding RLC PDU after receiving the PDCP PDU, sends the RLC PDU, and sends a data transmission notice to the PDCP after sending;
and the PDCP receives the data transmission notice, searches corresponding data in the data cached by the PDCP according to the data transmission notice, and deletes the searched data.
2. The method of claim 1, wherein the data transmission notification comprises all PDCP PDU information corresponding to an RLC PDU currently transmitted by an RLC, wherein the PDCP PDU information includes a sequence number corresponding to a PDCP PDU;
the PDCP entity searches for corresponding data in the data cached in the PDCP entity according to the data transmission notification:
the PDCP acquires all PDCP PDU information corresponding to the RLC PDU contained in the data transmission notice;
the PDCP searches the corresponding PDCP SDU in the PDCP SDU buffered by the PDCP PDU according to the sequence number corresponding to the PDCP PDU contained in the PDCP PDU information.
3. The method of claim 1, wherein if the RLC operating mode is ack mode, the RLC sending a data transmission notification to the PDCP comprises:
the RLC judges whether the currently sent RLC PDU is successfully received by the opposite terminal, and if so, the RLC sends the data transmission notice to the PDCP.
4. The method of claim 1, wherein the PDCP buffering the received PDCP SDUs further comprises: if the timer corresponding to the received PDCP SDU does not exist currently, the timer corresponding to the received PDCP SDU is established and started;
before receiving the data transmission notification, the PDCP further comprises: and judging whether the started timer does not exceed the preset time in real time, if so, after receiving a data transmission notice, executing the operation of searching corresponding data in the data cached in the self according to the data transmission notice, and stopping the timer, otherwise, directly deleting the PDCP SDU corresponding to the overtime timer.
5. A data processing apparatus, characterized in that the apparatus comprises: an RLC entity and a PDCP entity, wherein,
the PDCP entity buffers the received packet data convergence protocol PDCP service data unit SDU, converts the PDCP SDU into a corresponding PDCP protocol data unit PDU and sends the PDCP PDU to the RLC entity;
the RLC entity operates in an unacknowledged mode and receives PDCP PDUs before transmitting the PDCP PDUs
The PDU is transformed into a corresponding RLC PDU, the RLC PDU is sent, and after the RLC PDU is sent, a data transmission notice is sent to the PDCP entity;
and the PDCP entity receives the data transmission notice, searches corresponding data in the data cached by the PDCP entity according to the data transmission notice, and deletes the searched data.
6. An RLC entity, comprising: a data receiving unit, a first conversion unit and a transmitting unit; wherein,
the data receiving unit is used for receiving data from a PDCP entity; the PDCP entity transmits data by: the PDCP entity buffers the received PDCP service data unit SDU, transforms the PDCP SDU into a corresponding PDCP protocol data unit PDU and sends the PDCP PDU to the RLC entity;
the first conversion unit is used for converting the PDCP PDU received by the data receiving unit into a corresponding RLC PDU;
and the sending unit sends the RLC PDU when the working mode of the RLC entity is an unacknowledged mode, and sends a data transmission notice to the PDCP entity after sending.
7. The RLC entity of claim 6, wherein if the current operating mode is the acknowledged mode, the RLC entity further comprises: a judgment unit; wherein,
the judging unit is used for judging whether the currently sent RLC PDU is successfully received by the opposite terminal, and if so, sending a success notice to the sending unit;
and after receiving the successful notification, the sending unit sends a data transmission notification to the PDCP entity, wherein the data transmission notification contains PDCP PDU information corresponding to the currently sent RLC PDU.
8. A PDCP entity, comprising: the device comprises a notification receiving unit, a cache unit, a second conversion unit and a processing unit; wherein,
the notification receiving unit is used for receiving a PDCP service data unit SDU from a higher layer;
the buffer unit is used for storing the PDCP SDU received by the notification receiving unit;
the second conversion unit is used for converting the PDCP SDU received by the notification receiving unit into a corresponding PDCP protocol data unit PDU and sending the PDCP PDU to an RLC entity;
the notification receiving unit is further configured to receive a data transmission notification sent by the RLC entity;
the processing unit is used for searching corresponding data in the data cached by the processing unit according to the data transmission notice and deleting the searched data.
9. The PDCP entity of claim 8, wherein the data transmission notification comprises PDCP PDU information corresponding to an RLC PDU sent by an RLC entity, wherein the PDCP PDU information comprises a sequence number corresponding to a PDCP PDU;
the processing unit includes: an acquisition subunit and a processing subunit; wherein,
the acquiring subunit is configured to acquire PDCP PDU information corresponding to the RLC PDU included in the data transmission notification;
the processing subunit searches all corresponding PDCP SDUs in the PDCP SDUs stored in the cache unit according to the sequence number corresponding to the PDCP PDU contained in the PDCP PDU information acquired by the acquiring subunit, and deletes the searched PDCP SDUs.
10. The PDCP entity of claim 9, wherein the PDCP entity further comprises: a creation unit, a control unit and a timer; wherein,
the creating unit is configured to create the PDCP SDU corresponding to the notification received by the receiving unit when there is no timer corresponding to the PDCP SDU currently received by the receiving unit;
the control unit starts the timer created by the creation unit when the buffer unit stores the PDCP SDU, judges in real time whether the started timer does not exceed a preset time before the notification receiving unit receives the data transmission notification, if so, after the notification receiving unit receives the data transmission notification, triggers the acquiring subunit to acquire the PDCP PDU corresponding to the transmitted RLC PDU included in the data transmission notification, and controls the timer to stop, otherwise, sends the processing notification to the processing subunit;
and the processing subunit directly deletes the PDCP SDU corresponding to the overtime timer.
CN200810225500XA 2008-11-03 2008-11-03 Data processing method, data processing device, RLC entity and PDCP entity Active CN101729524B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN200810225500XA CN101729524B (en) 2008-11-03 2008-11-03 Data processing method, data processing device, RLC entity and PDCP entity

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN200810225500XA CN101729524B (en) 2008-11-03 2008-11-03 Data processing method, data processing device, RLC entity and PDCP entity

Publications (2)

Publication Number Publication Date
CN101729524A CN101729524A (en) 2010-06-09
CN101729524B true CN101729524B (en) 2012-12-12

Family

ID=42449733

Family Applications (1)

Application Number Title Priority Date Filing Date
CN200810225500XA Active CN101729524B (en) 2008-11-03 2008-11-03 Data processing method, data processing device, RLC entity and PDCP entity

Country Status (1)

Country Link
CN (1) CN101729524B (en)

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102316516B (en) * 2010-06-30 2016-04-06 重庆重邮信科通信技术有限公司 A kind of LTE uplink data transmission structure construction method
CN102300259B (en) * 2011-09-16 2015-06-10 电信科学技术研究院 Data block concatenation and splitting processing method, device and system
CN102395156B (en) * 2011-09-28 2015-05-20 电信科学技术研究院 Data transmission methods and device applied between packet data convergence protocol (PDCP) entity and radio link control (RLC) entity
KR101667507B1 (en) * 2012-11-29 2016-10-18 후아웨이 테크놀러지 컴퍼니 리미티드 Method, apparatus and system for controlling data transmission
CN104837163B (en) * 2014-02-08 2019-10-25 夏普株式会社 Method and base station for deleting radio link control service data unit
CN104935413B (en) * 2014-03-19 2019-12-27 夏普株式会社 Packet data convergence protocol PDCP entity and execution method thereof
CN106101286B (en) * 2016-08-22 2019-06-25 中国移动通信有限公司研究院 Data transmission method and device, UM RLC entity based on the unidirectional RB of total and fractional RLC
CN106101285B (en) * 2016-08-22 2019-08-13 中国移动通信有限公司研究院 Distributed data transport method and device, TM RLC entity based on TM rlc protocol
US10999019B2 (en) 2017-03-31 2021-05-04 Samsung Electronics Co., Ltd. Apparatus and buffer control method thereof in a wireless communication system
KR102293999B1 (en) * 2017-03-31 2021-08-27 삼성전자 주식회사 Apparatus and buffer controlling method thereof in a wireless communication system
CN108934044B (en) * 2017-05-27 2020-10-09 华为技术有限公司 Data packet transmission method and device
US11558494B2 (en) 2017-06-19 2023-01-17 Beijing Xiaomi Mobile Software Co., Ltd. Method and apparatus for processing data, user equipment and computer-readable storage medium
CN109429555B (en) * 2017-06-22 2019-08-23 北京小米移动软件有限公司 Data transmission method, device, user equipment and base station
CN109413692A (en) * 2017-08-18 2019-03-01 深圳市海思半导体有限公司 Transmission method, transmitting terminal and receiving end
CN107708153B (en) * 2017-09-29 2019-11-15 重庆邮电大学 A kind of radio modem ascending packet data processing method
WO2019095293A1 (en) * 2017-11-17 2019-05-23 Oppo广东移动通信有限公司 Method and device for processing data
CN110011925B (en) * 2018-01-04 2022-09-13 维沃移动通信有限公司 SDU processing method and communication equipment
CN111163081B (en) * 2019-12-26 2022-04-22 展讯通信(上海)有限公司 Data transmission method, device, equipment and storage medium
CN114126084A (en) * 2020-08-26 2022-03-01 中兴通讯股份有限公司 Data processing method, base station, terminal and storage medium

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1949698A (en) * 2005-10-10 2007-04-18 华为技术有限公司 Automatic retransmission method, transmitter and receiver for use in LTE technology
CN101018109A (en) * 2006-02-09 2007-08-15 中兴通讯股份有限公司 A mobility management method of the automatic retransfer request
CN101132609A (en) * 2006-08-22 2008-02-27 华为技术有限公司 Method and system for repeating data during switching course

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1949698A (en) * 2005-10-10 2007-04-18 华为技术有限公司 Automatic retransmission method, transmitter and receiver for use in LTE technology
CN101018109A (en) * 2006-02-09 2007-08-15 中兴通讯股份有限公司 A mobility management method of the automatic retransfer request
CN101132609A (en) * 2006-08-22 2008-02-27 华为技术有限公司 Method and system for repeating data during switching course

Also Published As

Publication number Publication date
CN101729524A (en) 2010-06-09

Similar Documents

Publication Publication Date Title
CN101729524B (en) Data processing method, data processing device, RLC entity and PDCP entity
JP4440300B2 (en) Separation-type medium access control protocol structure of wireless communication system, data transmission / reception method using the same, handover method and system thereof
KR100982688B1 (en) Apparatus and method for buffering packets in a multi-hop relay system supporting hop-by-hop retransmission
WO2018127238A1 (en) Information processing method and apparatus
US7826368B2 (en) Apparatus and method for moving a receive window in a radio access network
US8817806B2 (en) Method and apparatus for flow control between RLC and PDCP in a communication
US20060062323A1 (en) System and method for polling a protocol data unit of a transmission buffer
EP2575321B1 (en) A radio receiving apparatus
KR102141389B1 (en) Method and apparatus for sending radio link control status report for sending in a communication system based on a multi-radio access technologies
US20050152350A1 (en) System and method for transmitting/receiving automatic repeat request
JP2006311543A (en) Method and device for polling transmission state in radio communication system
CN1437368A (en) Data transmission confirming method
US8837310B2 (en) Method and system for determining an end time of uplink back propagation
WO2013053304A1 (en) Method and device for implementing tcp transmission
US9900802B2 (en) Data transmission method and apparatus, base station, and user equipment
CN107959555B (en) Data transmission method, device and storage medium based on LWAAP
CN102316516A (en) LTE uplink data transmission structure and control method
KR101640105B1 (en) Method and apparatus for content delivery in radio access networks
US8943362B2 (en) Control and monitoring for fast millimeter-wave link using out-of-band wireless channel
CN106993311B (en) Base station data optimized transmission method and system
CN108200605B (en) Data transmission method and device for base station
WO2017133595A1 (en) Data processing method and apparatus
JP2003274445A (en) Wireless packet communication apparatus and wireless packet communication method
CN100589431C (en) Mobile communication system interface flow control method
CN110062418B (en) Air interface switching method and node equipment

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
ASS Succession or assignment of patent right

Owner name: INST OF TELECOMMUNICATION SCIENCE AND TECHNOLGOY

Free format text: FORMER OWNER: DATANG MOBILE COMMUNICATION EQUIPMENT CO., LTD.

Effective date: 20110708

C41 Transfer of patent application or patent right or utility model
COR Change of bibliographic data

Free format text: CORRECT: ADDRESS; FROM: 100083 NO. 29, XUEYUAN ROAD, HAIDIAN DISTRICT, BEIJING TO: 100191 NO. 40, XUEYUAN ROAD, HAIDIAN DISTRICT, BEIJING

TA01 Transfer of patent application right

Effective date of registration: 20110708

Address after: 100191 Haidian District, Xueyuan Road, No. 40,

Applicant after: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY

Address before: 100083 Haidian District, Xueyuan Road, No. 29,

Applicant before: DATANG MOBILE COMMUNICATIONS EQUIPMENT Co.,Ltd.

C14 Grant of patent or utility model
GR01 Patent grant
CP01 Change in the name or title of a patent holder
CP01 Change in the name or title of a patent holder

Address after: 100191 No. 40, Haidian District, Beijing, Xueyuan Road

Patentee after: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY

Address before: 100191 No. 40, Haidian District, Beijing, Xueyuan Road

Patentee before: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY

TR01 Transfer of patent right
TR01 Transfer of patent right

Effective date of registration: 20210608

Address after: 100085 1st floor, building 1, yard 5, Shangdi East Road, Haidian District, Beijing

Patentee after: DATANG MOBILE COMMUNICATIONS EQUIPMENT Co.,Ltd.

Address before: 100191 No. 40, Haidian District, Beijing, Xueyuan Road

Patentee before: CHINA ACADEMY OF TELECOMMUNICATIONS TECHNOLOGY