CN110557229B - Data sending method, data receiving method, sending end and receiving end - Google Patents
Data sending method, data receiving method, sending end and receiving end Download PDFInfo
- Publication number
- CN110557229B CN110557229B CN201810552732.XA CN201810552732A CN110557229B CN 110557229 B CN110557229 B CN 110557229B CN 201810552732 A CN201810552732 A CN 201810552732A CN 110557229 B CN110557229 B CN 110557229B
- Authority
- CN
- China
- Prior art keywords
- pdcp
- entity
- data packet
- sending
- receiving
- 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
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1809—Selective-repeat protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
- H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
- H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
- H04L1/1829—Arrangements specially adapted for the receiver end
- H04L1/1835—Buffer management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/565—Conversion or adaptation of application format or content
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Communication Control (AREA)
Abstract
The invention provides a data sending method, a data receiving method, a sending end and a receiving end, wherein the data sending method comprises the following steps: and sending data packet information to an SDAP entity of a sending end, and receiving a data packet retransmitted by the SDAP entity of the sending end according to the data packet information. The scheme of the invention can make sure how to make the SDAP entity retransmit the data packet after introducing the SDAP entity.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a data sending method, a data receiving method, a sending end, and a receiving end.
Background
Currently, in a fourth Generation mobile communication technology (4th-Generation, 4G) system, when a Packet Data Convergence Protocol (PDCP) Entity of a Transmitting end (Transmitting Entity or Transmitting Side) receives a Re-establishment (Re-establishment) request from an Upper layer (Upper layer), the PDCP Entity of the Transmitting end needs to transmit Data, such as a Service Data Unit (SDU) to which a Sequence Number (SN) has been allocated, to a lower layer on an existing link as far as possible, and then Re-establish a new link by performing a Re-establishment Procedure (Re-establishment Procedure). The PDCP Entity of the Receiving end (Receiving Entity or Receiving Side) receives and reassembles the received data packet as much as possible, and delivers the data packet to the higher layer. If the PDCP entity of the receiving end can not receive the data packet correctly, the data packet can be retransmitted only by the upper layer of the PDCP entity of the transmitting end.
However, in almost all scenarios, the transmission and reception quality of the link before the re-establishment is poor, which results in that although the PDCP entity of the transmitting end has already tried to transmit the data packet, the error rate is high due to the poor transmission and reception quality of the link, and the data packet is not necessarily received correctly by the PDCP entity of the receiving end.
For the 5th-Generation (5G) system, a Service Data Adaptation Protocol (SDAP) entity has been proposed, and due to the introduction of the SDAP entity, a processing agent appears in the access layer corresponding to an IP packet. However, after introducing the SDAP entity, it is not clear how to cause the SDAP entity to retransmit the data packet.
Disclosure of Invention
Embodiments of the present invention provide a data sending method, a data receiving method, a sending end, and a receiving end, so as to make it clear how to make an SDAP entity retransmit a data packet after introducing the SDAP entity.
In a first aspect, an embodiment of the present invention provides a data sending method, which is applied to a PDCP entity at a sending end, and includes:
sending data packet information to an SDAP entity of a sending end;
and receiving the data packet retransmitted by the SDAP entity of the sending end according to the data packet information.
In a second aspect, an embodiment of the present invention further provides a data receiving method, which is applied to a PDCP entity of a receiving end, and includes:
receiving a data packet sent by a PDCP entity of a sending end;
delivering correctly received first PDCP SDU and identification value corresponding to the first PDCP SDU to an SDAP entity of a receiving end in sequence, and caching second PDCP SDU and identification value corresponding to the second PDCP SDU, so as to recombine and deliver the cached PDCP SDU after receiving a retransmission data packet;
wherein, the identification value corresponding to the first PDCP SDU is consecutive to the identification value corresponding to the PDCP SDU delivered to the SDAP entity of the receiving end, and the second PDCP SDU is another correctly received PDCP SDU in the received data packet except the first PDCP SDU.
In a third aspect, an embodiment of the present invention further provides a sending end, including a processor;
wherein the processor is configured to: the method comprises the steps of sending data packet information to an SDAP entity of a sending end through a PDCP entity of the sending end, and receiving a data packet retransmitted by the SDAP entity of the sending end according to the data packet information.
In a fourth aspect, an embodiment of the present invention further provides a receiving end, including a processor and a transceiver;
wherein the transceiver is to: receiving a data packet sent by a PDCP entity of a sending end through the PDCP entity of a receiving end;
the processor is configured to: delivering correctly received first PDCP SDU and the identification value corresponding to the first PDCP SDU to an SDAP entity of a receiving end in sequence through a PDCP entity of the receiving end, and caching second PDCP SDU and the identification value corresponding to the second PDCP SDU so as to recombine and deliver the cached PDCP SDU after receiving a retransmission data packet;
and the identification value corresponding to the first PDCP SDU is continuous with the identification value corresponding to the PDCP SDU submitted to the SDAP entity of the receiving end, and the second PDCP SDU is the correctly received PDCP SDU except the first PDCP SDU in the received data packet.
In a fifth aspect, an embodiment of the present invention further provides a data transceiving system, including a transmitting end and a receiving end;
wherein the sending end is configured to: sending data packet information to an SDAP entity of a sending end through a PDCP entity of the sending end, receiving a data packet retransmitted by the SDAP entity of the sending end according to the data packet information, and sending the data packet to the PDCP entity of a receiving end;
the receiving end is used for: receiving a data packet sent by a PDCP entity of a sending end through the PDCP entity of the receiving end, sequentially submitting a correctly received first PDCP SDU and an identification value corresponding to the first PDCP SDU to an SDAP entity of the receiving end, buffering a second PDCP SDU and the identification value corresponding to the second PDCP SDU, and recombining and submitting the buffered PDCP SDU after receiving a retransmission data packet;
and the identification value corresponding to the first PDCP SDU is continuous with the identification value corresponding to the PDCP SDU submitted to the SDAP entity of the receiving end, and the second PDCP SDU is the correctly received PDCP SDU except the first PDCP SDU in the received data packet.
In a sixth aspect, an embodiment of the present invention further provides a communication device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the computer program, when executed by the processor, implements the steps of the data transmission method or the steps of the data reception method.
In a seventh aspect, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the steps of the data sending method or the steps of the data receiving method.
In the embodiment of the invention, the PDCP entity of the sending end sends the data packet information to the SDAP entity of the sending end, and receives the data packet retransmitted by the SDAP entity of the sending end according to the data packet information, so that after the SDAP entity is introduced, how to make the SDAP entity retransmit the data packet is determined.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required to be used in the embodiments of the present invention will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive labor.
Fig. 1 is a flowchart of a data transmission method according to an embodiment of the present invention;
fig. 2 is a flowchart of a data receiving method according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a transmitting end according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a receiving end according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a communication device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1, an embodiment of the present invention provides a data sending method, which is applied to a PDCP entity at a sending end, and includes the following steps:
step 101: and sending the data packet information to the SDAP entity of the sending end.
In this embodiment of the present invention, optionally, the packet information may include one or more of the following combinations:
information of PDCP SDUs that are not transmitted;
identification values corresponding to the PDCP SDUs which are not sent;
information of a successful PDCP Protocol Data Unit (PDU) is not transmitted;
the identification value corresponding to the successful PDCP PDU is not transmitted.
Wherein the identification value may be a serial number SN or a COUNT value. It should be noted that, the SN and the COUNT value corresponding to the PDCP SDU are associated, and the COUNT value corresponding to the SN is usually obtained based on the PDCP SDU; the corresponding SN and COUNT values for the PDCP PDUs are also associated, and are typically derived based on the corresponding SN of the PDCP PDU.
The PDCP SDU information and the PDCP PDU information have the following functions: and enabling the SDAP entity to find the identification information of the SDAP SDU received by the SDAP entity according to the information. For example, the information of the PDCP SDU and the information of the PDCP PDU may use a storage location pointer of the SDAP SDU corresponding to the data packet carried along when the data packet is sent to the PDCP entity by the SDAP entity, or may use the SDAP entity to newly define an SDU identity indication information, and the like, which may be sent to the PDCP entity in an inter-layer primitive manner.
Step 102: and receiving the data packet retransmitted by the SDAP entity of the sending end according to the data packet information.
In this embodiment of the present invention, optionally, when the packet information includes information of a PDCP SDU that is not transmitted and an identifier corresponding to the PDCP SDU that is not transmitted, step 102 may include:
and submitting the information of the PDCP SDUs which are not sent and the identification values corresponding to the PDCP SDUs which are not sent to the SDAP entity of the sending end according to the monotone increasing sequence or the monotone decreasing sequence of the identification values corresponding to the PDCP SDUs which are not sent.
Optionally, when the packet information includes information of the PDCP PDU which has not been successfully transmitted and an identification value corresponding to the PDCP PDU which has not been successfully transmitted, step 102 may include:
and submitting the information of the PDCP PDU which is not successfully transmitted and the identification value corresponding to the PDCP PDU which is not successfully transmitted to the SDAP entity of the transmitting end according to the monotone increasing sequence or the monotone decreasing sequence of the identification value corresponding to the PDCP PDU which is not successfully transmitted.
Optionally, a mode of a Radio Bearer (RB) associated with the PDCP entity at the transmitting end in the embodiment of the present invention is an acknowledged mode AM or an unacknowledged mode UM. Correspondingly, the mode of the radio bearer associated with the receiving side PDCP entity is also AM or UM.
It can be understood that, the AM and UM are RB types corresponding to each PDCP entity in the PDCP protocol, and usually one RB corresponds to one PDCP entity, and each PDCP entity is associated with one or two UM RLC entities or one AM RLC entity, according to the definition of association relationship between RBs and PDCP entities in the protocol. The Radio bearers may include Signaling Radio Bearer (SRB) and Data Radio Bearer (DRB), i.e., the RB may include SRB and DRB.
It can be understood that, in the data transmission method according to the embodiment of the present invention, the PDCP entity of the transmitting end transmits the data packet information to the SDAP entity of the transmitting end, and the SDAP entity of the receiving end receives the data packet retransmitted according to the data packet information, so that after the SDAP entity is introduced, how to retransmit the data packet by the SDAP entity is determined.
In the embodiment of the invention, for the SDAP entity to retransmit the data packet, the retransmission can be triggered after the PDCP entity of the sending end receives the reestablishment request information of the upper layer. Specifically, step 101 may include:
after receiving the reestablishment request information of the upper layer, the PDCP entity of the transmitting end sends packet information to the SDAP entity of the transmitting end. After receiving the reestablishment request message from the upper layer, the PDCP entity of the sending end may stop sending the data packet to the PDCP entity of the receiving end until the PDCP reestablishment procedure is completed.
Correspondingly, before step 102, the method may further include:
and the PDCP entity at the sending end carries out a PDCP rebuilding process according to the rebuilding request information. It should be noted that, before performing the PDCP re-establishment procedure, the PDCP entity at the transmitting end may clear the transmission buffer information therein.
And step 102 may include:
and the PDCP entity of the sending end receives a data packet retransmitted by the SDAP entity of the sending end on the link after the reestablishment according to the data packet information.
In this embodiment of the present invention, optionally, the process of the PDCP entity at the transmitting end receiving the data packet retransmitted by the SDAP entity at the transmitting end on the link after the data packet information is reestablished may be:
a PDCP entity of a sending end receives a status report sent by the PDCP entity of a receiving end; wherein, the status report is used for indicating the condition that the PDCP entity of the receiving end correctly receives the data packet in the PDCP reestablishment process; the status report may include SN information of correctly received data packets, etc.;
and the PDCP entity of the sending end triggers the SDAP entity of the sending end to retransmit the data packet according to the status report, and receives the data packet retransmitted by the SDAP entity of the sending end on the link after the SDAP entity of the sending end is reestablished.
It should be noted that, when the sending end of the SDAP entity is triggered to retransmit the data packet according to the status report, the sending end of the PDCP entity may send the corresponding SN information included in the status report to the SDAP entity.
Therefore, the status report sent by the PDCP entity of the receiving end triggers the SDAP entity of the sending end to retransmit the data packet, the optimization of the PDCP reconstruction process can be realized, the seamless lossless switching of the data packet is realized, the receiving and sending efficiency of the data packet is improved, the realization is simple, and no influence is caused on an air interface.
In this embodiment of the present invention, optionally, after receiving the reestablishment request information of the upper layer (for example, the RLC layer), before sending the data packet information to the SDAP entity of the sending end, the PDCP entity of the sending end may send a notification message to the SDAP entity of the sending end, where the notification message is used to notify the SDAP entity of the sending end to stop sending the data packet. It should be noted that, if the upper layer sends the reestablishment request information (i.e., reestablishment signaling) to the PDCP entity and also sends the reestablishment request information to the SDAP entity, the SDAP entity may stop sending the data packet by itself.
Optionally, after receiving the reestablishment request information of the upper layer and before sending the data packet information to the SDAP entity of the sending end, the PDCP entity of the sending end may allocate a corresponding SN to each received PDCP SDU. Further, the PDCP entity at the transmitting end may record the last SN allocated at the beginning of the PDCP re-establishment procedure. Further, after the PDCP re-establishment is completed, the PDCP entity at the transmitting end may also update the status of the transmitting window according to the last SN and the number of retransmitted data packets reported by the PDCP entity at the receiving end. The number of the retransmitted data packets may be carried in the PDCP entity reported to the sending end in the status report.
Referring to fig. 2, an embodiment of the present invention further provides a data receiving method, which is applied to a PDCP entity of a receiving end, and includes the following steps:
step 201: receiving a data packet sent by a PDCP entity of a sending end;
step 202: delivering correctly received first PDCP SDU and identification value corresponding to the first PDCP SDU to an SDAP entity of a receiving end in sequence, and caching the second PDCP SDU and the identification value corresponding to the second PDCP SDU so as to recombine and deliver the cached PDCP SDU after receiving the retransmission data packet;
wherein, the identification value corresponding to the first PDCP SDU is continuous with the identification value corresponding to the PDCP SDU delivered to the SDAP entity of the receiving end, and the second PDCP SDU is the correctly received PDCP SDU except the first PDCP SDU in the received data packet. After receiving the data packet sent by the PDCP entity of the sending end, the PDCP entity of the receiving end can sort the correctly received PDCP SDUs according to the identification values, and then deliver the sorted PDCP SDUs to the SDAP entity of the receiving end in the correct order; and for the PDCP SDU which is correctly received but can not be recombined due to discontinuous identification value, caching, waiting for receiving the retransmission data packet, and submitting the retransmission data packet to the SDAP entity according to the sequence after correct recombination. The identification value may be a SN or COUNT value. For the buffered second PDCP SDU, the PDCP entity at the receiving end does not perform the reset process in the PDCP re-establishment procedure, and remains unchanged.
Therefore, the data receiving method can realize correct receiving of the data packet.
In this embodiment of the present invention, optionally, the method further includes:
sending a status report to a PDCP entity of a sending end;
the status report is used to indicate the condition that the PDCP entity of the receiving end correctly receives the data packet during the PDCP re-establishment process, so that the PDCP entity of the transmitting end triggers the SDAP entity of the transmitting end to retransmit the data packet according to the status report.
Therefore, the status report sent by the PDCP entity of the receiving end triggers the SDAP entity of the sending end to retransmit the data packet, the optimization of the PDCP reconstruction process can be realized, the seamless lossless switching of the data packet is realized, the receiving and sending efficiency of the data packet is improved, the realization is simple, and no influence is caused on an air interface.
In this embodiment of the present invention, optionally, the radio bearer mode associated with the PDCP entity of the sending end and the PDCP entity of the receiving end is AM or UM.
The above embodiments describe the data transmitting method and receiving method of the present invention, and the transmitting end and the receiving end of the present invention are described below with reference to the embodiments and the drawings.
Referring to fig. 3, an embodiment of the present invention further provides a transmitting end, which includes a processor 31, a transceiver 32, and a memory 33.
Wherein the processor 31 is configured to: the method comprises the steps of sending data packet information to an SDAP entity of a sending end through a PDCP entity of the sending end, and receiving a data packet retransmitted by the SDAP entity of the sending end according to the data packet information.
The sending end of the embodiment of the invention sends the data packet information to the SDAP entity of the sending end through the PDCP entity of the sending end, and receives the data packet retransmitted by the SDAP entity of the sending end according to the data packet information, so that after the SDAP entity is introduced, how to make the SDAP entity retransmit the data packet is clear.
In this embodiment of the present invention, optionally, the packet information includes one or more of the following combinations:
information of PDCP service data units SDU which are not transmitted;
identification values corresponding to the PDCP SDUs which are not sent;
the information of the successful PDCP protocol data unit PDU is not sent;
the identification value corresponding to the successful PDCP PDU is not transmitted.
Optionally, the data packet information includes information of the PDCP SDU that is not sent and an identification value corresponding to the PDCP SDU that is not sent; the processor 31 is specifically configured to:
and submitting the information of the PDCP SDUs which are not sent and the identification values corresponding to the PDCP SDUs which are not sent to the SDAP entity of the sending end according to the monotone increasing sequence or the monotone decreasing sequence of the identification values corresponding to the PDCP SDUs which are not sent by the PDCP entity of the sending end.
Optionally, the data packet information includes information of the PDCP PDU which is not successfully transmitted and an identification value corresponding to the PDCP PDU which is not successfully transmitted; the processor 31 is specifically configured to:
and submitting the information of the PDCP PDU which is not successfully transmitted and the identification value corresponding to the PDCP PDU which is not successfully transmitted to the SDAP entity of the transmitting end according to the monotone increasing sequence or the monotone decreasing sequence of the identification value corresponding to the PDCP PDU which is not successfully transmitted.
Optionally, the identification value is an SN or COUNT value.
Optionally, the processor 31 is specifically configured to: after receiving the reconstruction request information of the upper layer, sending data packet information to the SDAP entity of the sending end through the PDCP entity of the sending end, performing a PDCP reconstruction process according to the reconstruction request information, and receiving a data packet retransmitted by the SDAP entity of the sending end on a link after reconstruction according to the data packet information.
Optionally, the transceiver 32 is configured to: receiving a status report sent by a PDCP entity of a receiving end through the PDCP entity of the sending end, wherein the status report is used for indicating a situation that the PDCP entity of the receiving end correctly receives a data packet in the PDCP re-establishment process;
the processor 31 is specifically configured to: and triggering the SDAP entity of the sending end to retransmit the data packet according to the status report, and receiving the data packet retransmitted by the SDAP entity of the sending end on the link after the SDAP entity of the sending end is reestablished.
Optionally, the processor 31 is further configured to: sending a notification message to the SDAP entity of the sending end through the PDCP entity of the sending end;
wherein, the notification message is used to notify the SDAP entity of the sending end to stop sending data packets.
Optionally, the processor 31 is further configured to: and distributing corresponding SN for each PDCP SDU received by the PDCP entity of the sending end.
Optionally, the processor 31 is further configured to: recording the last SN allocated at the beginning of the PDCP re-establishment process.
Optionally, the processor 31 is further configured to: and updating the state of the sending window according to the last SN and the number of the retransmission data packets reported by the PDCP entity of the receiving end.
Optionally, the mode of the radio bearer associated with the PDCP entity of the sending end is AM or UM.
In FIG. 3, a bus architecture (represented by bus 30), bus 30 may include any number of interconnected buses and bridges, with bus 30 connecting together various circuits including one or more processors, represented by processor 31, and memory, represented by memory 33. The transceiver 32 may include a transmitter and a receiver, which may be connected to the processor 31 and the memory 33 via the bus 30.
The processor 31 is responsible for managing the bus 30 and general processing, while the memory 33 may be used for storing data used by the processor 31 in performing operations.
Referring to fig. 4, an embodiment of the present invention further provides a receiving end, which includes a processor 41, a transceiver 42, and a memory 43.
Wherein the transceiver 42 is configured to: and receiving the data packet sent by the PDCP entity of the sending end through the PDCP entity of the receiving end.
The processor 41 is configured to: delivering correctly received first PDCP SDU and the identification value corresponding to the first PDCP SDU to an SDAP entity of a receiving end in sequence through a PDCP entity of the receiving end, and caching second PDCP SDU and the identification value corresponding to the second PDCP SDU so as to recombine and deliver the cached PDCP SDU after receiving a retransmission data packet;
and the identification value corresponding to the first PDCP SDU is continuous with the identification value corresponding to the PDCP SDU submitted to the SDAP entity of the receiving end, and the second PDCP SDU is the correctly received PDCP SDU except the first PDCP SDU in the received data packet.
The receiving end of the embodiment of the invention can realize correct receiving of the data packet.
In this embodiment of the present invention, optionally, the transceiver 42 is further configured to: sending a status report to a PDCP entity of a sending end through the PDCP entity of the receiving end;
wherein, the status report is used to indicate the condition that the PDCP entity of the receiving end correctly receives the data packet in the PDCP re-establishment process, so that the PDCP entity of the transmitting end triggers the SDAP entity of the transmitting end to retransmit the data packet according to the status report.
Optionally, the identification value is an SN or COUNT value.
Optionally, the mode of the radio bearer associated with the PDCP entity of the sending end and the PDCP entity of the receiving end is AM or UM.
In FIG. 4, a bus architecture (represented by bus 40), bus 40 may include any number of interconnected buses and bridges, with bus 40 connecting together various circuits including one or more processors, represented by processor 41, and memory, represented by memory 43. The transceiver 42 may include a transmitter and a receiver, which may be connected to the processor 41 and the memory 43 via the bus 40.
The processor 41 is responsible for managing the bus 40 and general processing, while the memory 43 may be used for storing data used by the processor 41 in performing operations.
In addition, the embodiment of the invention also provides a data receiving and transmitting system, which comprises a transmitting end and a receiving end.
Wherein the sending end is configured to: sending data packet information to an SDAP entity of a sending end through a PDCP entity of the sending end, receiving a data packet retransmitted by the SDAP entity of the sending end according to the data packet information, and sending the data packet to the PDCP entity of a receiving end;
the receiving end is used for: receiving a data packet sent by a PDCP entity of a sending end through the PDCP entity of the receiving end, sequentially submitting a correctly received first PDCP SDU and an identification value corresponding to the first PDCP SDU to an SDAP entity of the receiving end, buffering a second PDCP SDU and the identification value corresponding to the second PDCP SDU, and recombining and submitting the buffered PDCP SDU after receiving a retransmission data packet;
and the identification value corresponding to the first PDCP SDU is continuous with the identification value corresponding to the PDCP SDU submitted to the SDAP entity of the receiving end, and the second PDCP SDU is the correctly received PDCP SDU except the first PDCP SDU in the received data packet.
In addition, an embodiment of the present invention further provides a communication device, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor, where the computer program, when executed by the processor, may implement each process of the data transmission method embodiment or each process of the data reception method embodiment, and may achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The communication device may be a transmitting end or a receiving end.
Specifically, referring to fig. 5, an embodiment of the present invention further provides a communication device, which includes a bus 51, a transceiver 52, an antenna 53, a bus interface 54, a processor 55, and a memory 56.
In an embodiment of the present invention, the communication device further includes: a computer program stored on the memory 56 and executable on the processor 55. The communication device may be a transmitting end or a receiving end.
Specifically, when the communication device is a transmitting end, the communication device includes a first PDCP entity and a first SDAP entity, and the computer program when executed by the processor 55 can implement the following steps:
and sending data packet information to a first SDAP entity through a first PDCP entity, and receiving a data packet retransmitted by the first SDAP entity according to the data packet information.
When the communication device is a receiver, the communication device comprises a second PDCP entity and a second SDAP entity, and the computer program when executed by the processor 55 is capable of implementing the following steps:
receiving a data packet sent by a PDCP entity of a sending end through a second PDCP entity, delivering a correctly received first PDCP SDU and an identification value corresponding to the first PDCP SDU to a second SDAP entity in sequence, buffering the second PDCP SDU and the identification value corresponding to the second PDCP SDU, and recombining and delivering the buffered PDCP SDU after receiving a retransmission data packet;
and the identification value corresponding to the first PDCP SDU is continuous with the identification value corresponding to the PDCP SDU submitted to a second SDAP entity, and the second PDCP SDU is the correctly received PDCP SDU except the first PDCP SDU in the received data packet.
In fig. 5, a bus architecture (represented by bus 51), bus 51 may include any number of interconnected buses and bridges, with bus 51 linking together various circuits including one or more processors, represented by processor 55, and memory, represented by memory 56. The bus 51 may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. A bus interface 54 provides an interface between the bus 51 and the transceiver 52. The transceiver 52 may be one element or may be multiple elements, such as multiple receivers and transmitters, providing a means for communicating with various other apparatus over a transmission medium. The data processed by the processor 55 is transmitted over a wireless medium via the antenna 53, and further, the antenna 53 receives the data and transmits the data to the processor 55.
The processor 55 is responsible for managing the bus 51 and general processing and may also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. And memory 56 may be used to store data used by processor 55 in performing operations.
Alternatively, the processor 55 may be a CPU, ASIC, FPGA or CPLD.
The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the computer program can implement each process of the data sending method or the data receiving method in the above embodiments, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.
Computer-readable media, which include both non-transitory and non-transitory, removable and non-removable media, may implement the information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.
Claims (26)
1. A data transmission method is applied to a Packet Data Convergence Protocol (PDCP) entity of a transmitting end, and is characterized by comprising the following steps:
sending data packet information to a Service Data Adaptation Protocol (SDAP) entity of a sending end;
receiving a data packet retransmitted by the SDAP entity of the sending end according to the data packet information;
wherein, the sending data packet information to the SDAP entity of the sending end includes:
after receiving the reestablishment request information of the upper layer, sending data packet information to the SDAP entity of the sending end;
before the receiving of the data packet retransmitted by the SDAP entity of the sending end according to the data packet information, the method further includes:
performing a PDCP reestablishment process according to the reestablishment request information;
the receiving of the data packet retransmitted by the SDAP entity of the sending end according to the data packet information includes:
and receiving a data packet retransmitted by the SDAP entity of the sending end on the link after the reestablishment according to the data packet information.
2. The method of claim 1, wherein the packet information comprises one or more of the following combinations:
information of PDCP service data units SDU which are not transmitted;
identification values corresponding to the PDCP SDUs which are not sent;
the information of the successful PDCP protocol data unit PDU is not sent;
the identification value corresponding to the successful PDCP PDU is not transmitted.
3. The method of claim 2, wherein the packet information comprises information of the non-transmitted PDCP SDU and an identification value corresponding to the non-transmitted PDCP SDU;
the sending of the data packet information to the service data adaptation protocol SDAP entity of the sending end includes:
and submitting the information of the PDCP SDUs which are not sent and the identification values corresponding to the PDCP SDUs which are not sent to the SDAP entity of the sending end according to the monotone increasing sequence or the monotone decreasing sequence of the identification values corresponding to the PDCP SDUs which are not sent.
4. The method according to claim 2, wherein the packet information includes information of the PDCP PDU which has not been successfully transmitted and an identification value corresponding to the PDCP PDU which has not been successfully transmitted;
the sending of the data packet information to the service data adaptation protocol SDAP entity of the sending end includes:
and submitting the information of the PDCP PDU which is not successfully transmitted and the identification value corresponding to the PDCP PDU which is not successfully transmitted to the SDAP entity of the transmitting end according to the monotone increasing sequence or the monotone decreasing sequence of the identification value corresponding to the PDCP PDU which is not successfully transmitted.
5. The method according to any of claims 2 to 4, characterized in that the identification value is a sequence number, SN, or a COUNT COUNT value.
6. The method of claim 1, wherein the receiving the data packet retransmitted by the SDAP entity at the sending end on the link after the reestablishment according to the data packet information comprises:
receiving a status report sent by a PDCP entity of a receiving end, wherein the status report is used for indicating the condition that the PDCP entity of the receiving end correctly receives a data packet in the PDCP reestablishment process;
and triggering the SDAP entity of the sending end to retransmit the data packet according to the status report, and receiving the data packet retransmitted by the SDAP entity of the sending end on the link after the SDAP entity of the sending end is reestablished.
7. The method of claim 1, wherein after receiving the upper layer reestablishment request message and before sending the packet message to the SDAP entity of the sender, the method further comprises:
sending a notification message to the SDAP entity of the sending end;
wherein, the notification message is used to notify the SDAP entity of the sending end to stop sending data packets.
8. The method of claim 1, wherein after receiving the upper layer reestablishment request message and before sending the packet message to the SDAP entity of the sender, the method further comprises:
and allocating a corresponding SN for each received PDCP SDU.
9. The method of claim 8, wherein after assigning the corresponding SN for each received PDCP SDU, the method further comprises:
recording the last SN allocated at the beginning of the PDCP re-establishment process.
10. The method of claim 9, wherein after performing the PDCP re-establishment procedure according to the re-establishment request information, the method further comprises:
and updating the state of the sending window according to the last SN and the number of the retransmission data packets reported by the PDCP entity of the receiving end.
11. The method of claim 1, wherein after receiving a re-establishment request message from an upper layer, the PDCP entity of the transmitting side stops transmitting data packets to the PDCP entity of the receiving side until the PDCP re-establishment procedure is completed.
12. The method as claimed in claim 1, wherein the mode of the radio bearer associated with the PDCP entity of the transmitting end is an acknowledged mode AM or an unacknowledged mode UM.
13. A transmitting end, comprising a processor;
wherein the processor is configured to: sending data packet information to an SDAP entity of a sending end through a PDCP entity of the sending end, and receiving a data packet retransmitted by the SDAP entity of the sending end according to the data packet information;
wherein the processor is specifically configured to: after receiving the reconstruction request information of the upper layer, sending data packet information to the SDAP entity of the sending end through the PDCP entity of the sending end, performing a PDCP reconstruction process according to the reconstruction request information, and receiving a data packet retransmitted by the SDAP entity of the sending end on a link after reconstruction according to the data packet information.
14. The sender according to claim 13, wherein the packet information includes one or more of the following combinations:
information of PDCP service data units SDU which are not transmitted;
identification values corresponding to the PDCP SDUs which are not sent;
the information of the successful PDCP protocol data unit PDU is not sent;
the identification value corresponding to the successful PDCP PDU is not transmitted.
15. The transmitting end according to claim 14, wherein the data packet information includes information of the non-transmitted PDCP SDU and an identification value corresponding to the non-transmitted PDCP SDU; the processor is specifically configured to:
and submitting the information of the PDCP SDUs which are not sent and the identification values corresponding to the PDCP SDUs which are not sent to the SDAP entity of the sending end according to the monotone increasing sequence or the monotone decreasing sequence of the identification values corresponding to the PDCP SDUs which are not sent by the PDCP entity of the sending end.
16. The transmitting end according to claim 14, wherein the packet information includes information of the PDCP PDU which has not been successfully transmitted and an identification value corresponding to the PDCP PDU which has not been successfully transmitted; the processor is specifically configured to:
and submitting the information of the PDCP PDU which is not successfully transmitted and the identification value corresponding to the PDCP PDU which is not successfully transmitted to the SDAP entity of the transmitting end according to the monotone increasing sequence or the monotone decreasing sequence of the identification value corresponding to the PDCP PDU which is not successfully transmitted.
17. Transmitting end according to any of claims 14 to 16, characterized in that the identification value is a SN or COUNT value.
18. The transmitting end according to claim 13,
the sending end also comprises a transceiver;
the transceiver is configured to: receiving a status report sent by a PDCP entity of a receiving end through the PDCP entity of the sending end, wherein the status report is used for indicating a situation that the PDCP entity of the receiving end correctly receives a data packet in the PDCP re-establishment process;
the processor is specifically configured to: and triggering the SDAP entity of the sending end to retransmit the data packet according to the status report, and receiving the data packet retransmitted by the SDAP entity of the sending end on the link after the SDAP entity of the sending end is reestablished.
19. The transmitting end according to claim 13,
the processor is further configured to: sending a notification message to the SDAP entity of the sending end through the PDCP entity of the sending end;
wherein, the notification message is used to notify the SDAP entity of the sending end to stop sending data packets.
20. The transmitting end according to claim 13,
the processor is further configured to: and distributing corresponding SN for each PDCP SDU received by the PDCP entity of the sending end.
21. The transmitting end according to claim 20,
the processor is further configured to: recording the last SN allocated at the beginning of the PDCP re-establishment process.
22. The transmitting end according to claim 21,
the processor is further configured to: and updating the state of the sending window according to the last SN and the number of the retransmission data packets reported by the PDCP entity of the receiving end.
23. The transmitting end of claim 13, wherein a mode of a radio bearer associated with the PDCP entity of the transmitting end is AM or UM.
24. A data receiving and transmitting system is characterized by comprising a transmitting end and a receiving end;
wherein the sending end is configured to: sending data packet information to an SDAP entity of a sending end through a PDCP entity of the sending end, receiving a data packet retransmitted by the SDAP entity of the sending end according to the data packet information, and sending the data packet to the PDCP entity of a receiving end;
the receiving end is used for: receiving a data packet sent by a PDCP entity of a sending end through the PDCP entity of the receiving end, sequentially submitting a correctly received first PDCP SDU and an identification value corresponding to the first PDCP SDU to an SDAP entity of the receiving end, buffering a second PDCP SDU and the identification value corresponding to the second PDCP SDU, and recombining and submitting the buffered PDCP SDU after receiving a retransmission data packet;
and the identification value corresponding to the first PDCP SDU is continuous with the identification value corresponding to the PDCP SDU submitted to the SDAP entity of the receiving end, and the second PDCP SDU is the correctly received PDCP SDU except the first PDCP SDU in the received data packet.
25. A communication device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the computer program, when executed by the processor, implements the steps of the data transmission method according to any one of claims 1 to 12.
26. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the data transmission method according to any one of claims 1 to 12.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810552732.XA CN110557229B (en) | 2018-05-31 | 2018-05-31 | Data sending method, data receiving method, sending end and receiving end |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810552732.XA CN110557229B (en) | 2018-05-31 | 2018-05-31 | Data sending method, data receiving method, sending end and receiving end |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110557229A CN110557229A (en) | 2019-12-10 |
| CN110557229B true CN110557229B (en) | 2022-04-29 |
Family
ID=68734039
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810552732.XA Active CN110557229B (en) | 2018-05-31 | 2018-05-31 | Data sending method, data receiving method, sending end and receiving end |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110557229B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111258295A (en) * | 2020-01-15 | 2020-06-09 | 重庆长安汽车股份有限公司 | System and method for verifying big data acquisition and uploading accuracy |
| CN113225361B (en) * | 2020-01-21 | 2022-11-18 | 华为技术有限公司 | Data transmission method and electronic equipment |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101682864A (en) * | 2007-06-18 | 2010-03-24 | 高通股份有限公司 | Method and apparatus for pdcp reordering at handoff |
| US8630259B2 (en) * | 2008-08-04 | 2014-01-14 | Qualcomm Incorporated | PDCP behaviour at handover and connection re-establishment |
| CN107404734A (en) * | 2016-05-18 | 2017-11-28 | 中兴通讯股份有限公司 | Data transmission method for uplink, apparatus and system |
| CN107637123A (en) * | 2017-04-27 | 2018-01-26 | 北京小米移动软件有限公司 | Information transmitting methods, device and computer-readable recording medium |
| WO2018030798A1 (en) * | 2016-08-09 | 2018-02-15 | Samsung Electronics Co., Ltd. | Method and apparatus for managing user plane operation in wireless communication system |
| CN107734547A (en) * | 2016-08-12 | 2018-02-23 | 中兴通讯股份有限公司 | State report generates and system, and status report reception method |
| CN107733577A (en) * | 2016-08-11 | 2018-02-23 | 华为技术有限公司 | The method and apparatus for carrying out retransmission process |
| CN107925665A (en) * | 2015-08-31 | 2018-04-17 | 高通股份有限公司 | Unnecessary protocol Data Unit (PDU) is avoided to transmit |
| EP3319252A1 (en) * | 2016-11-04 | 2018-05-09 | Panasonic Intellectual Property Corporation of America | Efficient multiplexing of control information in transport block |
| CN110121193A (en) * | 2018-02-06 | 2019-08-13 | 中国移动通信有限公司研究院 | A kind of inter-layer data transmission method, device, medium and equipment |
-
2018
- 2018-05-31 CN CN201810552732.XA patent/CN110557229B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101682864A (en) * | 2007-06-18 | 2010-03-24 | 高通股份有限公司 | Method and apparatus for pdcp reordering at handoff |
| US8630259B2 (en) * | 2008-08-04 | 2014-01-14 | Qualcomm Incorporated | PDCP behaviour at handover and connection re-establishment |
| CN107925665A (en) * | 2015-08-31 | 2018-04-17 | 高通股份有限公司 | Unnecessary protocol Data Unit (PDU) is avoided to transmit |
| CN107404734A (en) * | 2016-05-18 | 2017-11-28 | 中兴通讯股份有限公司 | Data transmission method for uplink, apparatus and system |
| WO2018030798A1 (en) * | 2016-08-09 | 2018-02-15 | Samsung Electronics Co., Ltd. | Method and apparatus for managing user plane operation in wireless communication system |
| CN107733577A (en) * | 2016-08-11 | 2018-02-23 | 华为技术有限公司 | The method and apparatus for carrying out retransmission process |
| CN107734547A (en) * | 2016-08-12 | 2018-02-23 | 中兴通讯股份有限公司 | State report generates and system, and status report reception method |
| EP3319252A1 (en) * | 2016-11-04 | 2018-05-09 | Panasonic Intellectual Property Corporation of America | Efficient multiplexing of control information in transport block |
| CN107637123A (en) * | 2017-04-27 | 2018-01-26 | 北京小米移动软件有限公司 | Information transmitting methods, device and computer-readable recording medium |
| CN110121193A (en) * | 2018-02-06 | 2019-08-13 | 中国移动通信有限公司研究院 | A kind of inter-layer data transmission method, device, medium and equipment |
Non-Patent Citations (3)
| Title |
|---|
| "3GPP TS 38.323 V15.1.0";MCCSupport;《3GPP TS 38.323 V15.1.0》;20180402;第10-15页5.1，5.2，5.4小节，第20-21页6.2.2小节 * |
| "TP from email discussion [101#03][NR] 38.331 CR part 3 (Huawei)";Rapporteur (Huawei);《R2-1804127 TSGR2_101》;20180315;全文 * |
| "UDN部署下的多连接技术研究";海涵;《中国优秀硕士学位论文全文数据库信息科技辑》;20180315;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110557229A (en) | 2019-12-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP4387393B2 (en) | Method and apparatus for processing control PDU upon re-establishment of transmitting side in wireless communication system | |
| US11206538B2 (en) | Control signaling processing method, device, and system | |
| US11672046B2 (en) | Data receiving status reporting method and apparatus | |
| CN110430599B (en) | Data transmission method and device | |
| WO2017008555A1 (en) | Data transmission method, sending device, and reception device | |
| TW201914339A (en) | Apparatus and method for processing bearer type change for radio bearer | |
| CN110557229B (en) | Data sending method, data receiving method, sending end and receiving end | |
| CN112703716A (en) | Shared radio bearer and management of UE radio ID and RAN path | |
| US11889356B2 (en) | Method and a device for data retransmission | |
| CN109428684B (en) | Data transmission method, RLC entity and PDCP entity | |
| CN113765626A (en) | Data transmission method and device of mobile communication system | |
| JP2007129723A (en) | Method and apparatus for processing protocol error in radio communication system | |
| CN109525374B (en) | Data transmission method, wireless access point, user equipment and transmission equipment | |
| WO2018141241A1 (en) | Device switching method and device, bearing configuration method and device, and communication system | |
| EP4311300A1 (en) | Data transmission method and apparatus | |
| CN110891326B (en) | Control plane connection reestablishing method, communication equipment, target base station and source base station | |
| CN111095980A (en) | Method and device for remapping QoS flow and computer storage medium | |
| TW201911918A (en) | Device and method of handling a secondary node change in dual connectivity | |
| WO2021004207A1 (en) | Data processing method and device | |
| CN116963175A (en) | Data transmission method, device and system | |
| CN111510263B (en) | Remapping method, terminal and network side equipment | |
| JP2021100288A (en) | Wireless communication device, wireless communication method, and wireless communication system | |
| CN109729554B (en) | Uplink enhanced data transmission method and device and user equipment | |
| US20220014965A1 (en) | Wireless lan communication device and wireless lan communication method | |
| US20240129802A1 (en) | Method and a device for data retransmission |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |