WO2019034130A1 - 传输方法、发送端和接收端 - Google Patents

传输方法、发送端和接收端 Download PDF

Info

Publication number
WO2019034130A1
WO2019034130A1 PCT/CN2018/100932 CN2018100932W WO2019034130A1 WO 2019034130 A1 WO2019034130 A1 WO 2019034130A1 CN 2018100932 W CN2018100932 W CN 2018100932W WO 2019034130 A1 WO2019034130 A1 WO 2019034130A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdcp
length
data packets
data
packet
Prior art date
Application number
PCT/CN2018/100932
Other languages
English (en)
French (fr)
Inventor
王刚
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2019034130A1 publication Critical patent/WO2019034130A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols

Definitions

  • the present application relates to the field of communications, and more particularly to a transmission method, a transmitting end, and a receiving end.
  • the media access control (MAC) layer schedules a radio link control (RLC) layer to perform cascading processing on the packet based on the size of the authorized resource. Since the cascading packet requires a certain processing overhead, the number of cascading packets is limited when cascading the packet, so as to prevent the packet from being sent at the time when the packet cannot be bound by the authorization because the cascading cannot be completed on time. Although the way to limit the number of cascading packets can avoid errors in many cases, this approach may result in insufficient authorization and reduce data transmission efficiency.
  • RLC radio link control
  • the RLC layer In order to improve data transmission efficiency, the RLC layer needs to cascade a larger number of packets based on the time of the authorization constraint, and this requires reducing the cascading processing overhead of the RLC layer. Therefore, how to reduce the cascading processing overhead of the RLC layer becomes a technical problem that needs to be solved.
  • the present application provides a transmission method, a transmitting end, and a receiving end, which can reduce the processing overhead of the RLC layer and improve the data transmission efficiency.
  • a transmission method for a transmitting end, the method comprising:
  • the first packet data convergence protocol (PDCP) entity at the transmitting end performs cascading processing on a plurality of consecutive data packets on the first radio bearer to obtain a packet data convergence protocol service data unit (packet data convergence protocol service data unit) , PDCP SDU), the length of the PDCP SDU is less than or equal to the first preset length;
  • PDCP packet data convergence protocol
  • the first PDCP entity performs PDCP processing on the PDCP SDU to obtain a packet data convergence protocol protocol data unit PDCP PDU;
  • the first PDCP entity transmits the PDCP PDU to the first radio link control RLC entity of the transmitting end.
  • the PDCP PDU includes only one PDCP sequence numbering (SN).
  • the plurality of data packets subjected to the cascade processing may be user plane data or control plane data.
  • the first radio bearer may be a data radio bearer (DRB) or a signaling radio bearer (SRB).
  • the PDCP processing of the user plane data by the first PDCP entity may include: header compression, encryption, and addition of PDCP header processing.
  • the PDCP processing of the control plane data by the first PDCP entity may include: integrity protection, encryption, and addition of PDCP header processing. Header compression, encryption, integrity protection, and adding PDCP header processing.
  • the PDCP processing of the PDCP SDU by the first PDCP entity can be specifically referred to the prior art.
  • the PDCP processing of the user plane data and the control plane data by the foregoing first PDCP entity is only an exemplary description, and the present application does not limit the PDCP processing of the user plane data and the control plane data by the first PDCP entity, for example, With the development of technology, the PDCP processing of the user plane data and the control plane data by the first PDCP entity can also evolve and change accordingly.
  • the first preset length is not specifically limited in the embodiment of the present application.
  • the first preset length can be 1500 bytes or 1630 bytes.
  • the PDCP layer performs cascading processing on the small packets, and cascading the small packets into large packets, so that the number of data packets based on the authorized cascading of the RLC layer can be reduced.
  • the RLC layer cascading processing overhead can be reduced, and data transmission efficiency is improved.
  • the cascading processing of the small packets through the PDCP layer can reduce the overhead of the PDCP/RLC header, thereby further improving the transmission efficiency.
  • the PDCP header of the PDCP PDU includes a cascading indication field, and the information in the cascading indication field is used to indicate that the PDCP PDU is a PDCP PDU obtained after performing cascading processing.
  • the cascading indication field may occupy one bit. Thereby, it is possible to save overhead.
  • the multiple data packets are data packets whose length is less than or equal to a second preset length.
  • the second preset length is not specifically limited in the embodiment of the present application.
  • the second preset length can be 255 bytes or 127 bytes.
  • the PDCP PDU includes multiple length indication fields, where the multiple length indication fields are in one-to-one correspondence with the plurality of data packets, and the information in the length indication field is used to indicate corresponding The length of the packet.
  • the length indication field may be adjacent to the corresponding data packet.
  • the plurality of length indication fields are located in the PDCP header.
  • the length of the other data packets except the last one of the plurality of data packets is not greater than the third preset length.
  • the third preset length is not specifically limited in the embodiment of the present application.
  • the third preset length may be 255 bytes or 127 bytes.
  • the PDCP PDU includes a plurality of length indication fields and a plurality of extension indication fields, where the plurality of length indication fields are in one-to-one correspondence with the plurality of extension indication fields, and the extension indication field and the corresponding length indication field Adjacent, the plurality of length indication fields are in one-to-one correspondence with other data packets except the last one of the plurality of data packets, and the information in the length indication field is used to indicate the length of the corresponding data packet.
  • the information in the extension indication field is used to indicate whether there is an extension indication field and a length indication field corresponding to a next data packet of the corresponding data packet.
  • the length indication field or the corresponding extension indication field is adjacent to the corresponding data packet, or the multiple length indication field and the multiple extension indication fields are located in a PDCP header of the PDCP PDU.
  • the method may further include:
  • the first PDCP entity starts a drop timer when receiving the Mth data packet of the plurality of data packets, where M is an integer greater than or equal to 1;
  • the first PDCP entity If the first PDCP entity has not sent the PDCP PDU to the first RLC entity, the first PDCP entity performs packet loss processing on the PDCP PDU.
  • the transition delay and queuing phenomenon of the transmitter at the transmitting end can be prevented.
  • the method further includes:
  • the sending end receives configuration information, where the configuration information is used to instruct the sending end to perform cascading processing on the multiple data packets on the first radio bearer;
  • the first packet data convergence protocol PDCP entity of the sending end performs concatenation processing on multiple consecutive data packets on the first radio bearer, including:
  • the first PDCP entity performs concatenation processing on the plurality of data packets according to the configuration information.
  • a transmission method for a receiving end, the method comprising:
  • the second packet data convergence protocol PDCP entity of the receiving end receives the packet data convergence protocol service data unit PDCP PDU sent by the second radio link control RLC entity of the receiving end;
  • the second PDCP entity performs PDCP reverse processing on the PDCP PDU to obtain a PDCP SDU, where the length of the PDCPSDU is less than or equal to a first preset length;
  • the second PDCP entity performs cascading reverse processing on the PDCP SDU to obtain a plurality of consecutive data packets
  • the second PDCP entity sends the plurality of data packets to an upper layer application of the receiving end.
  • the PDCP layer performs cascading processing on the small packets, and cascading the small packets into large packets, so that the number of data packets based on the authorized cascading of the RLC layer can be reduced.
  • the RLC layer cascading processing overhead can be reduced, and data transmission efficiency is improved.
  • the cascading processing of the small packets through the PDCP layer can reduce the overhead of the PDCP/RLC header, thereby further improving the transmission efficiency.
  • the PDCP header of the PDCP PDU includes a cascading indication field, and the information in the cascading indication field is used to indicate that the PDCP PDU is a PDCP PDU obtained after performing cascading processing;
  • the second PDCP entity performs cascading reverse processing on the PDCP SDU, including:
  • the second PDCP entity performs cascading reverse processing on the PDCP SDU according to the information in the cascading indication field.
  • the multiple data packets are data packets whose length is less than or equal to a second preset length.
  • the PDCP PDU includes multiple length indication fields, where the multiple length indication fields are in one-to-one correspondence with the plurality of data packets, and information in the length indication field is used to indicate corresponding The length of the packet.
  • the length of the other data packets except the last one of the plurality of data packets is not greater than the third preset length.
  • the PDCP PDU includes multiple length indication fields and a plurality of extension indication fields, where the multiple length indication fields are in one-to-one correspondence with the multiple extension indication fields, and the extension indication field Adjacent to the corresponding length indication field, the plurality of length indication fields are in one-to-one correspondence with other data packets except the last one of the plurality of data packets, and the information in the length indication field is used to indicate corresponding The length of the data packet, the information in the extension indication field is used to indicate whether there is an extension indication field and a length indication field corresponding to the next data packet of the corresponding data packet.
  • the method before the second packet data convergence protocol PDCP entity at the receiving end receives the packet data convergence protocol service data unit PDCPPDU sent by the second radio link control RLC entity of the receiving end, the method also includes:
  • the receiving end sends configuration information, where the configuration information is used to instruct the sending end to perform cascading processing on the multiple data packets on the first radio bearer.
  • a transmitting end is provided, the transmitting end having a function of implementing a transmitting end in the method design of the above first aspect.
  • These functions can be implemented in hardware or in software by executing the corresponding software.
  • the hardware or software includes one or more units corresponding to the functions described above.
  • a receiving end is provided, the receiving end having the function of implementing the receiving end in the method design of the second aspect above.
  • These functions can be implemented in hardware or in software by executing the corresponding software.
  • the hardware or software includes one or more units corresponding to the functions described above.
  • a transmitting end including a transceiver, a processor, and a memory.
  • the processor is for controlling transceiver transceiver signals for storing a computer program for calling and running the computer program from the memory such that the transmitting end performs the method of the first aspect above.
  • a receiving end including a transceiver, a processor, and a memory.
  • the processor is for controlling transceiver transceiver signals for storing a computer program for calling and running the computer program from the memory such that the receiving end performs the method of the second aspect.
  • a computer program product comprising: computer program code, causing a computer to perform the method of the above aspects when the computer program code is run on a computer.
  • a computer readable medium storing program code for causing a computer to perform the method of the above aspects when the computer program code is run on a computer.
  • a chip system comprising a processor for supporting a communication device to implement the functions involved in the above aspects, for example, generating, receiving, transmitting, or processing data involved in the above method and / or information.
  • the chip system further comprises a memory for storing program instructions and data necessary for the transmitting end.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • a chip system comprising a processor for supporting a communication device to implement the functions involved in the above, for example, generating, receiving, transmitting, or processing data involved in the above method and/or Or information.
  • the chip system further includes a memory for storing necessary program instructions and data at the receiving end.
  • the chip system can be composed of chips, and can also include chips and other discrete devices.
  • FIG. 1 is a schematic diagram of a communication system applied to the present application.
  • FIG. 2 is a schematic flowchart of a transmission method according to an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a format of a PDCP PDU according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a format of a PDCP PDU according to another embodiment of the present application.
  • FIG. 5 is a schematic diagram of a format of a PDCP PDU according to an embodiment of the present application.
  • FIG. 6 is a schematic diagram of a format of a PDCP PDU according to another embodiment of the present application.
  • FIG. 7 is a schematic block diagram of a transmitting end of an embodiment of the present application.
  • FIG. 8 is a schematic block diagram of a receiving end of an embodiment of the present application.
  • FIG. 9 is a schematic block diagram of a transmitting end of an embodiment of the present application.
  • FIG. 10 is a schematic block diagram of a receiving end of an embodiment of the present application.
  • GSM global system of mobile communication
  • CDMA code division multiple access
  • WCDMA Wideband code division multiple access
  • GPRS general packet radio service
  • LTE long term evolution
  • LTE-A advanced long term evolution
  • UMTS universal mobile telecommunication system
  • 5G system can also be called a new radio access technology (NR) system.
  • NR new radio access technology
  • FIG. 1 is a schematic diagram of a communication system 100 suitable for use in a transmission method of an embodiment of the present application.
  • the communication system 100 includes at least two communication devices, such as a network device 110 and a terminal device 120, wherein data communication can be performed between the network device 110 and the terminal device 120 through a wireless connection.
  • the network device 110 may be a base station (Base Transceiver Station, BTS) in Global System for Mobile Communications (GSM) or Code Division Multiple Access (CDMA), or may be a base station in Wideband Code Division Multiple Access (WCDMA).
  • BTS Base Transceiver Station
  • GSM Global System for Mobile Communications
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • NodeB, NB may also be an Evolutionary Node B (eNB or eNodeB) in Long Term Evolution (LTE), or a relay station, an access point, or a remote radio unit (RRU), or a vehicle
  • the device and the wearable device may also be a wireless controller in a cloud radio access network (CRAN) scenario, and a network side device in a future 5G system, such as a transmission point (TP), and a transmission.
  • a transmission reception point (TRP), a base station (gNodeB, gNB), a small base station device, and the like are not specifically limited in
  • terminal device 120 may also be referred to as user equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, A wireless communication device, user agent, or user device.
  • UE user equipment
  • the terminal device may be a station (station, ST) in a wireless local area network (WLAN), and may be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, or a wireless local loop (wireless local Loop, WLL) station, personal digital assistant (PDA) device, handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device, wearable device, and next-generation communication system,
  • PDA personal digital assistant
  • the terminal device in the 5G network or the terminal device in the public land mobile network (PLMN) network in the future is not limited in this embodiment.
  • FIG. 1 is merely a simplified schematic diagram for ease of understanding.
  • Other communication devices and/or terminal devices may also be included in the communication system 100, which are not shown in FIG.
  • the network device provides a service for the cell
  • the terminal device communicates with the network device by using a transmission resource (for example, a frequency domain resource, or a spectrum resource) used by the cell
  • a transmission resource for example, a frequency domain resource, or a spectrum resource
  • the cell may be a network device.
  • the cell may belong to a macro base station, or may belong to a base station corresponding to a small cell (Small Cell), where the small cell may include: a metro cell, a micro cell, and a pico cell. (Pico cell), femto cell, etc.
  • These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
  • the cell may also be a hypercell.
  • Hypercell adopts User Centric No Cell Radio Access (UCNC) technology, that is, the terminal device no longer accesses a fixed physical site (for example, TRP), but accesses a group.
  • TRP's Logical Entity (LE) is used to obtain services.
  • This logical entity can be called Hypercell.
  • the boundaries of the Hypercell are flexible and can vary depending on network load and user distribution. All the TRPs in the Hypercell are transparent to the terminal device. The terminal device only needs to access the Hypercell ID to obtain the TRP service in the Hypercell, and no longer connect to a TRP.
  • the media access control (MAC) layer schedules the radio link control (RLC) layer to perform cascading processing on the packet based on the size of the authorized resource.
  • RLC radio link control
  • the RLC layer needs to cascade a larger number of packets based on the time of the authorization constraint, and this requires lowering the RLC layer cascading processing overhead. Therefore, how to reduce the processing overhead of the RLC layer becomes a technical problem that needs to be solved.
  • the present application provides a transmission method, by introducing a cascading function in the PDCP layer, cascading packets by the PDCP layer, and cascading the packets into large packets, thereby reducing the RLC layer based on the authorization level.
  • the number of connected data packets can further reduce the processing overhead of the RLC layer and improve data transmission efficiency.
  • Big package and small package are relative concepts. Large packets are longer than small packets. For example, a packet with a length of 1500 bytes can be considered as a large packet, and a packet with a length of 255 bytes can be considered as a small packet. .
  • a packet whose length is less than or equal to 255 bytes is called a packet
  • a packet whose length is greater than 255 bytes is called a large packet.
  • this embodiment of the present application does not limit this.
  • the sending end in the embodiment of the present application may be a terminal device, and the receiving end may be a network device.
  • the sender may be a network device, and the receiver may be a terminal device.
  • FIG. 2 is a schematic flowchart of a transmission method of an embodiment of the present application, showing detailed communication steps or operations of the method, but the steps or operations are only examples, and the embodiment of the present application may also be performed. Other operations or variations of the various operations in FIG. Moreover, the various steps in the figures may be performed in a different order than that presented in FIG. 2, and it is possible that not all operations in FIG. 2 are to be performed.
  • FIG. 2 is a schematic flow chart of a transmission method according to the present application.
  • the method shown in FIG. 2 may include steps S210 to S270.
  • the first PDCP entity at the transmitting end performs concatenation processing on a plurality of consecutive data packets on the first radio bearer to obtain a packet data convergence protocol service data unit PDCP SDU.
  • the length of the PDCP SDU is less than or equal to a first preset length.
  • the first PDCP entity may be any PDCP entity at the transmitting end.
  • the consecutive plurality of data packets refer to a plurality of adjacent data packets, that is, a plurality of data packets arranged in sequence.
  • the first PDCP entity caches consecutive data packets on the first radio bearer, and performs cascading processing on the buffered multiple data packets, that is, the multiple data packets are concatenated in the order of the data packets, and the cascading is performed. Process the result as a PDCP SDU.
  • the first PDCP may refer to the cascading processing of the RLC SDU by the RLC entity in the prior art, and perform cascading processing on the multiple data packets.
  • the first preset length may be equal to the sum of the lengths of the plurality of data packets.
  • the embodiment of the present application does not limit whether the concatenation processing of the multiple data packets by the first PDCP entity is the same as the concatenation processing of the RLC entity in the prior art.
  • the first PDCP entity performs concatenation processing on the buffered data packet until a packet whose length is greater than a third preset length (not described here, which will be described in detail later) is encountered, or until a reception time is encountered. Stops when the packet of the first predetermined time is received later than the reception time of the first packet processed by the cascade, or when the sum of the length of the already cascaded packet and the length of the current packet is greater than the packet length threshold The cascading process continues on the currently concatenated packets. Then, the first PDCP entity treats the result of the concatenation process as a PDCP SDU.
  • a third preset length not described here, which will be described in detail later
  • the first preset length may be 1500 bytes, but the first preset length is not limited by the embodiment of the present application.
  • the first preset length may also be 1600 bytes. It should be understood that the first preset length may be set according to the size of the buffer area of the first PDCP entity. Generally, the first preset length is less than or equal to the size of the buffer area of the first PDCP entity.
  • the first preset time and the packet length threshold are not limited in this embodiment of the present application.
  • the first preset time may be 10 milliseconds (ms), or 5 ms.
  • the packet length threshold may or may not be equal to the first preset length, for example, the packet length threshold may be 1500 bytes, or 1630 bytes.
  • the method may further include: the sending end receiving the configuration information sent by the receiving end, where the configuration information is used to instruct the sending end to perform the cascading processing on the multiple data packets on the first radio bearer .
  • step S210 is specifically: the first PDCP entity performs concatenation processing on the plurality of data packets according to the configuration information.
  • the receiving end may indicate whether the PDCP entity at the transmitting end performs cascading processing on the data packet on a certain bearer, and the receiving end indicates that the PDCP entity at the transmitting end performs cascading processing on the data packet on the bearer for the PDCP entity.
  • the PDCP entity performs concatenation processing on the data packets on the bearer.
  • the receiving end may instruct the first PDCP entity to perform cascading processing on the data packet on the first bearer, indicating that the second PDCP entity does not perform cascading processing on the data packet on the second bearer, or the receiving end does not indicate the second PDCP.
  • the entity performs the concatenation processing on the data packet on the second bearer, and the second PDCP entity does not perform the concatenation processing on the data packet on the second bearer by default.
  • the first PDCP entity performs the data on the first bearer according to the indication of the receiving end.
  • the packet is subjected to cascading processing, and the second PDCP entity does not perform cascading processing on the data packet on the second bearer according to the indication of the receiving end.
  • the first PDCP entity performs PDCP processing on the PDCP SDU to obtain a packet data convergence protocol protocol data unit PDCP PDU.
  • the first PDCP entity performs PDCP processing on the PDCP SDU obtained in step S210 to obtain a PDCP PDU having only one PDCP SN.
  • the plurality of data packets subjected to the cascade processing may be user plane data or control plane data.
  • the first radio bearer may be a data radio bearer DRB or a signaling radio bearer SRB.
  • the PDCP processing of the user plane data by the first PDCP entity may include: header compression, encryption, and addition of PDCP header processing.
  • the PDCP processing of the control plane data by the first PDCP entity may include: integrity protection, encryption, and addition of PDCP header processing. Header compression, encryption, integrity protection, and adding PDCP header processing.
  • the PDCP processing of the PDCP SDU by the first PDCP entity may be specifically referred to the prior art. For brevity, no further details are provided herein.
  • the PDCP processing of the user plane data and the control plane data by the foregoing first PDCP entity is only an exemplary description, and the present application does not limit the PDCP processing of the user plane data and the control plane data by the first PDCP entity, for example, With the development of technology, the PDCP processing of the user plane data and the control plane data by the first PDCP entity can also evolve and change accordingly.
  • the first PDCP entity sends the PDCP PDU to a first RLC entity at the sending end.
  • the first RLC entity After receiving the PDCP PDU, the first RLC entity processes and transmits the PDCP PDU according to the prior art.
  • the small packets are cascaded by the PDCP layer, and the small packets are cascaded into large packets, so that the RLC layer can be reduced based on the authorized cascading data packets.
  • the quantity can further reduce the processing overhead of the RLC layer and improve the data transmission efficiency.
  • the cascading processing of the small packets through the PDCP layer can reduce the overhead of the PDCP/RLC header, thereby further improving the transmission efficiency.
  • the PDCP header of the PDCP PDU includes a cascading indication field, where the information in the cascading indication field is used to indicate that the PDCP PDU is a PDCP PDU obtained after performing cascading processing. That is to say, the cascading indication field can distinguish whether the PDCP PDU is obtained after performing cascading processing.
  • the cascading indication field can occupy one bit. Thereby, it is possible to save overhead.
  • bit when the bit is 1, it indicates that the PDCP PDU is obtained after the cascading process, and when the bit is 0, it indicates that the PDCP PDU is obtained after the cascading process is not performed, that is, the conventional PDCP PDU.
  • the present application does not limit the number of bits occupied by the concatenation indication field, nor the meaning of the bit value in the concatenation indication field.
  • the bit is 1 or 0 to indicate that the PDCP PDU is obtained after the cascading process. Accordingly, if the bit is 0 or 1, the PDCP PDU can be represented as Obtained after the cascade processing.
  • the plurality of data packets are data packets whose length is less than or equal to a second preset length.
  • the second preset length may be 255 bytes
  • the first preset length may be 1500 bytes.
  • the first PDCP entity may perform cascading processing on consecutive data packets not exceeding 255 bytes in length if the obtained PDCP SDU does not exceed 1500 bytes.
  • the second preset length is not specifically limited in the embodiment of the present application.
  • the second preset length can also be, for example, 127 bytes.
  • the PDCP PDU may further include multiple length indication fields.
  • the plurality of length indication fields are in one-to-one correspondence with the plurality of data packets, and the information in the length indication field is used to indicate the length of the corresponding data packet.
  • the length indication field is adjacent to the corresponding data packet, or the multiple length indication fields are located in the PDCP header.
  • Figure 3 shows a schematic diagram of a PDCP PDU format.
  • the length indication field is adjacent to the corresponding data packet.
  • the PDCP PDU is concatenated with n consecutive data packets, the PDCP PDU including a PDCP header and a PDCP SDU portion.
  • the PDCP header includes the following (1) to (5), and the PDCP SDU includes (LI1+Data1) to (LIn+Datan).
  • the PDCP PDU will be described in detail below with reference to FIG. 3.
  • D/C A data type indication field for indicating that Data1 to Datan are control plane data or user plane data.
  • D/C when D/C is 0, it indicates that Data1 to Datan are control plane data, and when D/C is 1, it indicates that Data1 to Datan are user plane data.
  • P Polling indication, indicating whether the network device triggers a PDCP status report for LTE Wireless Local Area Network Aggregation (LWA).
  • LWA LTE Wireless Local Area Network Aggregation
  • a concatenation indication field which is used to indicate whether the PDCP PDU is a PDCP PDU obtained after the concatenation process.
  • PDCP SN PDCP serial number, the specific meaning can be seen in the prior art. It should be understood that the bits occupied by the PDCP SN (cont.) are also PDCP SNs. The PDCP SN and the PDCP SN (cont.) as shown in 3 together represent the PDCP SN, and the PDCP SN occupies a total of 18 bits.
  • LI1 is used to indicate the length of Data1
  • LI2 is used to indicate the length of Data2
  • LIn is used to indicate the length of Datan.
  • Datai The i-th data packet cascaded by the PDCP entity.
  • Data1 represents the first data packet concatenated by the PDCP entity
  • Data2 represents the second data packet concatenated by the PDCP entity
  • Datan represents the nth data packet concatenated by the PDCP entity.
  • each line in the format shown in FIG. 3 is one byte.
  • the contents of Data1 to Datan are not shown in FIG. 3, but it should be understood that the lengths of Data1 to Datan are not greater than the second preset length, and the length of the PDCP SDU is not greater than the first preset length.
  • LIi has a length of 8 bits, so the second preset length is 255 bytes, that is, the length of Data1 to Datan does not exceed 255 bytes.
  • Figure 4 shows a schematic diagram of another PDCP PDU format.
  • the PDCP header includes a plurality of length indication fields.
  • the PDCP PDU is concatenated with n consecutive data packets, the PDCP PDU including a PDCP header and a PDCP SDU portion.
  • the PDCP header includes the following (1) to (6), and the PDCP SDU includes Data1 to Datan.
  • each line in the format shown in FIG. 4 is one byte.
  • the contents of Data1 to Datan are not shown in FIG. 4, but it should be understood that the lengths of Data1 to Datan are not greater than the second preset length, and the length of the PDCP SDU is not greater than the first preset length.
  • the length of LIi is 8 bits, so the second preset length is 255 bytes, that is, the length of Data1 to Datan does not exceed 255 bytes.
  • the length of the other data packets except the last one of the plurality of data packets is not greater than a third preset length, and a length of the last one of the plurality of data packets is greater than the first Three preset lengths.
  • the third preset length may be equal to the second preset length or may not be equal.
  • the third preset length may be, for example, 127 bytes, which is not limited in this embodiment of the present application.
  • the PDCP PDU includes a plurality of length indication fields and a plurality of extension indication fields.
  • the plurality of length indication fields are in one-to-one correspondence with the plurality of extension indication fields, where the extension indication field is adjacent to a corresponding length indication field, and the plurality of length indication fields and the last one of the plurality of data packets Other data packets correspond one by one. That is, in addition to the last concatenated packet, each packet has a length indication field that indicates the length of the packet.
  • the information in the length indication field is used to indicate the length of the corresponding data packet, and the length indication field or the corresponding extended indication field is adjacent to the corresponding data packet, where the information in the extension indication field is used to indicate whether there is a corresponding The extension indication field and the length indication field corresponding to the next packet of the data packet.
  • the length indication field or the corresponding extension indication field is adjacent to the corresponding data packet, or the multiple length indication field and the multiple extension indication fields are located in a PDCP header of the PDCP PDU.
  • Figure 5 shows a schematic diagram of another PDCP PDU format.
  • the length indication field or the corresponding extension indication field is adjacent to the corresponding data packet.
  • the PDCP PDU is concatenated with n consecutive data packets, the PDCP PDU including a PDCP header and a PDCP SDU portion.
  • the PDCP header includes the following (1) to (5), and the PDCP SDU includes (E+LI1+Data1) to Datan.
  • the PDCP PDU will be described in detail below with reference to FIG. 5.
  • D/C A data type indication field for indicating that Data1 to Datan are control plane data or user plane data.
  • D/C when D/C is 1, it indicates that Data1 to Datan are control plane data, and when D/C is 0, it indicates that Data1 to Datan are user plane data.
  • P Polling indication, indicating whether the network device triggers a PDCP status report for the LWA.
  • a concatenation indication field which is used to indicate whether the PDCP PDU is a PDCP PDU obtained after the concatenation process.
  • PDCP SN PDCP serial number, the specific meaning can be seen in the prior art. It should be understood that the bits occupied by the PDCP SN (cont.) are also PDCP SNs. The PDCP SN and the PDCP SN (cont.) as shown in 3 together represent the PDCP SN, and the PDCP SN occupies a total of 18 bits.
  • (6) E an extended indication field, configured to indicate whether there is an extended indication field and a length indication field corresponding to a next data packet of the corresponding data packet.
  • 0 means that the current E+LI+Data is followed by another Data
  • 1 means that the current E+LI+Data is followed by another E+LI+Data.
  • the values of the first n-2 Es are all 1, and the value of the n-1th E is 0.
  • LI1 is used to indicate the length of Data1
  • LI2 is used to indicate the length of Data2
  • LIn is used to indicate the length of Datan.
  • Datai The i-th data packet cascaded by the PDCP entity.
  • Data1 represents the first data packet concatenated by the PDCP entity
  • Data2 represents the second data packet concatenated by the PDCP entity
  • Datan represents the nth data packet concatenated by the PDCP entity.
  • each line in the format shown in FIG. 5 is one byte.
  • the contents of Data1 to Datan are not shown in FIG. 5, but it should be understood that the lengths of Data1 to Data(n-1) are not greater than the third preset length, and the length of the PDCP SDU is not greater than the first preset length.
  • the length of LIi is 7 bits, so the third preset length is 127 bytes, so the length of Data1 ⁇ Data(n-1) does not exceed 127 bytes, but the last packet (ie, Datan) can be longer than 127 bytes.
  • Figure 6 shows a schematic diagram of another PDCP PDU format.
  • the length indication field and the extension indication field are located in the PDCP header of the PDCP PDU.
  • the PDCP PDU is concatenated with n consecutive data packets, the PDCP PDU including a PDCP header and a PDCP SDU portion.
  • the PDCP header includes the following (1) to (7), and the PDCP SDU includes Data1 to Datan.
  • each line in the format shown in FIG. 6 is one byte.
  • the contents of Data1 to Datan are not shown in FIG. 6, but it should be understood that the lengths of Data1 to Data(n-1) are not greater than the third preset length, and the length of the PDCP SDU is not greater than the first preset length.
  • the length of LIi is 7 bits, so the third preset length is 127 bytes, so the length of Data1 ⁇ Data(n-1) does not exceed 127 bytes, but the last packet (ie, Datan) can be longer than 127 bytes.
  • the method may further include:
  • the first PDCP entity starts a drop timer when receiving the Mth data packet of the plurality of data packets, where M is an integer greater than or equal to 1; if the drop timer expires, if the first PDCP entity further The PDCP PDU is not sent to the first RLC entity, and the first PDCP entity performs packet loss processing on the PDCP PDU.
  • the number of the plurality of data packets is five, and the first PDCP entity may start the discard timer when receiving the third data packet. If the discard timer expires, the first PDCP entity has not yet The first RLC entity sends the PDCP PDU after the concatenation process and the PDCP process, and the first PDCP entity discards the PDCP PDU as a whole.
  • the first PDCP entity may start the discard timer at the 5th second, if the discard timer is exceeded. At the same time, the first PDCP entity has not sent the PDCP PDU after the concatenation processing and the PDCP processing to the first RLC entity, and the first PDCP entity discards the PDCP PDU as a whole.
  • the discard timer may be a Discard_Timer timer, but the embodiment of the present application does not limit this.
  • the transition delay and queuing phenomenon of the transmitter at the transmitting end can be prevented.
  • the PDCP second PDCP entity at the receiving end receives the PDCP PDU sent by the second RLC entity at the receiving end.
  • the PDCP PDU here is the PDCP PDU sent by the first PDCP entity to the first RLC entity.
  • the first RLC entity of the sending end may perform RLC processing on the PDCP PDU according to the prior art, for example, performing cascading or splitting, adding an RLC header, and the like.
  • the RLC PDU, and then the first RLC entity sends the RLC PDU to the first MAC entity.
  • the first MAC entity may perform MAC processing on the RLC PDU according to the prior art, for example, performing a MAC header operation to obtain a transport block, and then the first MAC entity sends the transport block to the physical layer.
  • the physical layer performs modulation and coding operations on the transport block, and transmits the transport block processed by the physical layer to the receiving end.
  • the receiving end After receiving the physical layer processed transport block sent by the transmitting end, the receiving end performs demodulation and decoding operations on the transport block processed by the physical layer to obtain the transport block, and then sends the transport block to the second MAC entity of the receiving end.
  • the second MAC entity may perform MAC reverse processing on the transport block according to the prior art, for example, perform a MAC header operation, and send the processing result to the second RLC entity.
  • the second RLC entity may perform RLC reverse processing on the processing result by referring to the prior art, for example, performing a splitting process to obtain a PDCP PDU, and then the second RLC entity sends the PDCP PDU to the second PDCP entity.
  • the PDCP PDU received by the second PDCP entity is the PDCP PDU sent by the first PDCP entity to the first RLC entity.
  • the second PDCP entity performs PDCP reverse processing on the PDCP PDU to obtain the PDCP SDU.
  • the PDCP reverse processing is a process of obtaining a PDCP SDU from a PDCP PDU, and may include, for example, a PDCP header, decryption, and the like.
  • the reverse processing of the PDCP can be specifically referred to the prior art. For brevity, details are not described herein again.
  • the second PDCP entity performs cascade reverse processing on the PDCP SDU to obtain the multiple data packets.
  • the cascaded reverse processing is a process of obtaining multiple data packets from a PDCP SDU.
  • the second PDCP entity may perform operations such as de-PDCP header, decryption, and the like to obtain a PDCP SDU. Then, the second PDCP entity performs cascade reverse processing on the PDCP SDU, and splits the PDCP SDU into multiple consecutive data packets.
  • the second PDCP entity may refer to the cascading reverse processing of the RLC SDU in the RLC entity in the prior art, and perform cascading reverse processing on the PDCP SDU.
  • the second PDCP entity may perform split processing on the PDCP SDU according to the cascading indication field according to any format shown in FIG. 3-6, to obtain multiple consecutive data packets, that is, Data1 to Datan.
  • the second PDCP entity sends the multiple data packets to an upper layer application of the receiving end.
  • the PDCP layer performs cascading processing on the small packets, and cascading the small packets into large packets, so that the number of data packets based on the authorized cascading of the RLC layer can be reduced.
  • the RLC layer cascading processing overhead can be reduced, and data transmission efficiency is improved.
  • the cascading processing of the small packets through the PDCP layer can reduce the overhead of the PDCP/RLC header, thereby further improving the transmission efficiency.
  • FIG. 7 is a schematic block diagram of a transmitting end 700 according to an embodiment of the present application. As shown in FIG. 7, the transmitting end 700 includes: a processing unit 710 and a transceiver unit 720.
  • the processing unit 710 is configured to perform cascading processing on multiple consecutive data packets on the first radio bearer to obtain a packet data convergence protocol service data unit PDCP SDU, where the length of the PDCP SDU is less than or equal to the first preset length.
  • the processing unit 710 is further configured to perform PDCP processing on the PDCP SDU to obtain a packet data convergence protocol protocol data unit PDCP PDU.
  • the transceiver unit 720 is configured to send a PDCP PDU to the first radio link control RLC entity at the transmitting end.
  • the PDCP header of the PDCP PDU includes a cascading indication field, and the information in the cascading indication field is used to indicate that the PDCP PDU is a PDCP PDU obtained after performing cascading processing.
  • the plurality of data packets are data packets whose length is less than or equal to a second preset length.
  • the PDCP PDU includes a plurality of length indication fields, where the plurality of length indication fields are in one-to-one correspondence with the plurality of data packets, and the information in the length indication field is used to indicate the length of the corresponding data packet.
  • the length of the other data packets except the last one of the plurality of data packets is not greater than a third preset length.
  • the PDCP PDU includes a plurality of length indication fields and a plurality of extension indication fields, where the plurality of length indication fields are in one-to-one correspondence with the plurality of extension indication fields, and the extension indication field is adjacent to the corresponding length indication field, and the plurality of length indications
  • the field corresponds to one of the plurality of data packets except the last data packet.
  • the information in the length indication field is used to indicate the length of the corresponding data packet, and the information in the extended indication field is used to indicate whether the data packet exists and corresponds.
  • the extension indicator field and the length indication field corresponding to the next packet of the data packet.
  • processing unit 710 is further configured to:
  • the discard timer is started, where M is an integer greater than or equal to 1;
  • the discard timer expires, if the sending unit has not sent the PDCP PDU to the first RLC entity, the PDCP PDU is subjected to packet loss processing.
  • the transceiver unit 720 is further configured to: receive configuration information, where the configuration information is used to instruct the sending end to perform cascading processing on multiple data packets on the first radio bearer.
  • the processing unit 710 is specifically configured to: perform cascading processing on multiple data packets according to the configuration information.
  • the transmitting end 700 herein is embodied in the form of a functional unit.
  • the term "unit” as used herein may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (eg, a shared processor, a proprietary processor, or a group) for executing one or more software or firmware programs. Processors, etc.) and memory, merge logic, and/or other suitable components that support the described functionality.
  • ASIC application specific integrated circuit
  • the sending end 700 may be specifically the sending end in the foregoing embodiment, and the sending end 700 may be used to perform various processes corresponding to the sending end in the foregoing method embodiment and/or Steps, to avoid repetition, will not be repeated here.
  • FIG. 8 is a schematic block diagram of a receiving end 800 of an embodiment of the present application. As shown in FIG. 8, the receiving end 800 includes a transceiver unit 810 and a processing unit 820.
  • the transceiver unit 810 is configured to receive a packet data convergence protocol service data unit PDCP PDU sent by the second radio link control RLC entity of the receiving end.
  • the processing unit 820 is configured to perform PDCP reverse processing on the PDCP PDU to obtain a PDCP SDU, where the length of the PDCP SDU is less than or equal to the first preset length.
  • the processing unit 820 is further configured to perform cascading reverse processing on the PDCP SDU to obtain a plurality of consecutive data packets.
  • the transceiver unit 810 is further configured to send multiple data packets to an upper layer application at the receiving end.
  • the PDCP header of the PDCP PDU includes a cascading indication field, and the information in the cascading indication field is used to indicate that the PDCP PDU is a PDCP PDU obtained after performing cascading processing.
  • the processing unit 820 is configured to perform cascading reverse processing on the PDCP SDU according to the information in the cascading indication field.
  • the plurality of data packets are data packets whose length is less than or equal to a second preset length.
  • the PDCP PDU includes a plurality of length indication fields, where the plurality of length indication fields are in one-to-one correspondence with the plurality of data packets, and the information in the length indication field is used to indicate the length of the corresponding data packet.
  • the length of the other data packets except the last one of the plurality of data packets is not greater than a third preset length.
  • the PDCP PDU includes a plurality of length indication fields and a plurality of extension indication fields, where the plurality of length indication fields are in one-to-one correspondence with the plurality of extension indication fields, and the extension indication field is adjacent to the corresponding length indication field, and the plurality of length indications
  • the field corresponds to one of the plurality of data packets except the last data packet.
  • the information in the length indication field is used to indicate the length of the corresponding data packet, and the information in the extended indication field is used to indicate whether the data packet exists and corresponds.
  • the extension indicator field and the length indication field corresponding to the next packet of the data packet.
  • the transceiver unit 810 is further configured to: send configuration information, where the configuration information is used to instruct the sending end to perform cascading processing on multiple data packets on the first radio bearer.
  • the receiving end 800 herein is embodied in the form of a functional unit.
  • the term "unit” as used herein may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (eg, a shared processor, a proprietary processor, or a group) for executing one or more software or firmware programs. Processors, etc.) and memory, merge logic, and/or other suitable components that support the described functionality.
  • ASIC application specific integrated circuit
  • processor eg, a shared processor, a proprietary processor, or a group
  • memory merge logic, and/or other suitable components that support the described functionality.
  • the receiving end 800 may be specifically the receiving end in the foregoing embodiment, and the receiving end 800 may be used to perform various processes corresponding to the receiving end in the foregoing method embodiment and/or Steps, to avoid repetition, will not be repeated here.
  • FIG. 9 is a schematic block diagram of another transmitting end 900 according to an embodiment of the present application.
  • the transmitting end 900 includes a processor 910, a transceiver 920, and a memory 930.
  • the processor 910, the transceiver 920, and the memory 930 communicate with each other through an internal connection path.
  • the memory 930 is configured to store instructions, and the processor 910 is configured to execute instructions stored in the memory 930 to control the transceiver 920 to send signals and / or receive signals.
  • the processor 910 is configured to perform cascading processing on multiple consecutive data packets on the first radio bearer to obtain a packet data convergence protocol service data unit PDCP SDU, where the length of the PDCP SDU is less than or equal to the first preset length. ;
  • the processor 910 is further configured to perform PDCP processing on the PDCP SDU to obtain a packet data convergence protocol protocol data unit PDCP PDU;
  • the transceiver 920 is configured to send the PDCP PDU to a first radio link control RLC entity of the sending end.
  • the sending end 900 may be specifically the sending end in the foregoing embodiment, and may be used to perform various steps and/or processes corresponding to the sending end in the foregoing method embodiment.
  • the memory 930 can include read only memory and random access memory and provide instructions and data to the processor. A portion of the memory may also include a non-volatile random access memory.
  • the memory can also store information of the device type.
  • the processor 910 can be configured to execute instructions stored in a memory, and when the processor 910 executes instructions stored in the memory, the processor 910 is configured to perform the various steps of the method embodiment corresponding to the transmitting end and/or Or process.
  • FIG. 10 is a schematic block diagram of another receiving end 1000 of the embodiment of the present application.
  • the receiving end 1000 includes a processor 1010, a transceiver 1020, and a memory 1030.
  • the processor 1010, the transceiver 1020, and the memory 1030 communicate with each other through an internal connection path.
  • the memory 1030 is configured to store instructions, and the processor 1010 is configured to execute instructions stored by the memory 1030 to control the transceiver 1020 to send signals and / or receive signals.
  • the transceiver 1020 is configured to receive a packet data convergence protocol service data unit PDCP PDU sent by the second radio link control RLC entity of the receiving end;
  • the processor 1010 is configured to perform PDCP reverse processing on the PDCP PDU to obtain a PDCP SDU, where the length of the PDCP SDU is less than or equal to a first preset length;
  • the processor 1010 is further configured to perform cascading reverse processing on the PDCP SDU to obtain a plurality of consecutive data packets.
  • the transceiver 1020 is further configured to send the multiple data packets to an upper layer application of the receiving end.
  • the receiving end 1000 may be specifically the transmitting end in the foregoing embodiment, and may be used to perform various steps and/or processes corresponding to the receiving end in the foregoing method embodiments.
  • the memory 1030 can include read only memory and random access memory and provides instructions and data to the processor. A portion of the memory may also include a non-volatile random access memory.
  • the memory can also store information of the device type.
  • the processor 1010 can be configured to execute instructions stored in a memory, and when the processor 1010 executes instructions stored in the memory, the processor 1010 is configured to perform the various steps of the method embodiment corresponding to the receiving end and/or Or process.
  • the processor may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSPs), and dedicated integration.
  • DSPs digital signal processors
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory (ROM), a programmable read only memory (ROMM), an erasable programmable read only memory (erasable PROM, EPROM), or an electrical Erase programmable EPROM (EEPROM) or flash memory.
  • the volatile memory can be a random access memory (RAM) that acts as an external cache.
  • RAM random access memory
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • synchronous dynamic randomness synchronous dynamic randomness.
  • Synchronous DRAM SDRAM
  • DDR SDRAM double data rate synchronous DRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous connection dynamic random access memory Take memory
  • DR RAM direct memory bus random access memory
  • the above embodiments may be implemented in whole or in part by software, hardware, firmware or any other combination.
  • the above-described embodiments may be implemented in whole or in part in the form of a computer program product.
  • the computer program product comprises one or more computer instructions or computer programs.
  • the processes or functions described in accordance with embodiments of the present application are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that contains one or more sets of available media.
  • the usable medium can be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium.
  • the semiconductor medium can be a solid state hard drive.
  • the size of the sequence numbers of the foregoing processes does not mean the order of execution sequence, and the order of execution of each process should be determined by its function and internal logic, and should not be applied to the embodiment of the present application.
  • the implementation process constitutes any limitation.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product.
  • the technical solution of the present application which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product, which is stored in a storage medium, including The instructions are used to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

Landscapes

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

Abstract

本申请提供一种传输方法、发送端和接收端，能够降低RLC层级联处理时间开销，提高数据传输效率。该方法包括：发送端的第一PDCP实体对第一无线承载上连续的多个数据包进行级联处理，得到PDCP SDU，该PDCP SDU的长度小于或等于第一预设长度；第一PDCP实体对该PDCP SDU进行PDCP处理，得到分组数据汇聚协议协议数据单元PDCP PDU；第一PDCP实体向所述发送端的第一RLC实体发送该PDCP PDU。

Description

传输方法、发送端和接收端
本申请要求于2017年08月18日提交中国专利局、申请号为201710714171.4、申请名称为“传输方法、发送端和接收端”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，并且更具体地，涉及一种传输方法、发送端和接收端。
背景技术
无线技术的不断发展使得人们对通信速率和时延的要求越来越高。随着速率的提升和各种应用的层出不穷，通信系统中的小包越来越多，而通信系统的内存和处理时延往往与数据包的数量密切相关，小包的增加对处理时延和内存都构成了挑战。
现有技术中，媒体接入控制(media access control，MAC)层在收到授权后，基于授权资源大小调度无线链路控制(radio link control，RLC)层对小包进行级联处理。由于级联小包需要一定的处理开销，因此在级联小包时会限制级联的小包的数量，以防止因无法按时完成级联导致数据包无法按授权约束的时间发送的情况。虽然限制级联小包的数量的方式在很多情况下能够避免出错，但是这种方式可能导致授权使用不充分，降低数据传输效率。
为了提高数据传输效率，RLC层需要基于授权约束的时间级联更多数量的小包，而这就需要降低RLC层的级联处理开销。因此，如何降低RLC层的级联处理开销，成为亟需解决的技术问题。
发明内容
本申请提供一种传输方法、发送端和接收端，能够降低RLC层级联处理开销，提高数据传输效率。
第一方面，提供了一种传输方法，用于发送端，该方法包括：
发送端的第一分组数据汇聚协议(packet data convergence protocol，PDCP)实体对第一无线承载上连续的多个数据包进行级联处理，得到分组数据汇聚协议服务数据单元(packet data convergence protocol service data unit，PDCP SDU)，该PDCP SDU的长度小于或等于第一预设长度；
第一PDCP实体对该PDCP SDU进行PDCP处理，得到分组数据汇聚协议协议数据单元PDCP PDU；
第一PDCP实体向所述发送端的第一无线链路控制RLC实体发送该PDCP PDU。
应理解，该PDCP PDU仅包括一个PDCP序列号(sequence numbering，SN)
还应理解，被进行级联处理的多个数据包可以是用户面数据，也可以是控制面数据。 也就是说，第一无线承载可以是数据无线承载(data radio bearer，DRB)，也可以是信令无线承载(signaling radio bearer，SRB)。第一PDCP实体对用户面数据的PDCP处理可以包括：头压缩、加密和添加PDCP头处理。第一PDCP实体对控制面数据的PDCP处理可以包括：完整性保护、加密和添加PDCP头处理。头压缩、加密、完整性保护和添加PDCP头处理。第一PDCP实体对PDCP SDU的PDCP处理具体地可以参照现有技术。还应理解，上述第一PDCP实体对用户面数据以及控制面数据的PDCP处理仅为示例性说明，本申请并不限定第一PDCP实体对用户面数据以及控制面数据的PDCP处理，比如，随着技术的发展，第一PDCP实体可以对用户面数据以及控制面数据的PDCP处理也可以随之演进和改变。
本申请实施例不对第一预设长度作具体限定。例如，第一预设长度可以是1500字节或1630字节。
本申请实施例的传输方法，通过在PDCP层引入级联功能，由PDCP层对小包进行级联处理，将小包级联为大包，这样能够降低RLC层基于授权级联的数据包的数量，进而能够降低RLC层级联处理开销，提高数据传输效率。另一方面，由于减少了RLC层级联的数据包的数量，因此也能够减少内存的占用。再一方面，通过PDCP层对小包进行级联处理，能够降低PDCP/RLC头的开销，进而能够进一步提高传输效率。
在一种可能的实现方式中，该PDCP PDU的PDCP头包括级联指示字段，该级联指示字段中的信息用于指示该PDCP PDU为进行级联处理后得到的PDCP PDU。
可选地，该级联指示字段可以占用一个比特。从而，能够节省开销。
在一种可能的实现方式中，所述多个数据包均为长度小于或等于第二预设长度的数据包。
本申请实施例不对第二预设长度作具体限定。例如，第二预设长度可以是255字节或127字节。
在一种可能的实现方式中，该PDCP PDU包括多个长度指示字段，所述多个长度指示字段与所述多个数据包一一对应，所述长度指示字段中的信息用于指示对应的数据包的长度。
可选地，该长度指示字段可以与对应的数据包相邻。或者，该多个长度指示字段位于PDCP头中。
在一种可能的实现方式中，所述多个数据包中除最后一个数据包外的其他数据包的长度均不大于第三预设长度。
本申请实施例不对第三预设长度作具体限定。例如，第三预设长度可以是255字节或127字节。
进一步地，所述PDCP PDU包括多个长度指示字段和多个扩展指示字段，所述多个长度指示字段与所述多个扩展指示字段一一对应，所述扩展指示字段与对应的长度指示字段相邻，所述多个长度指示字段与所述多个数据包中除最后一个数据包外的其他数据包一一对应，所述长度指示字段中的信息用于指示对应的数据包的长度，所述扩展指示字段中的信息用于指示是否存在与对应的数据包的下一个数据包对应的扩展指示字段和长度指示字段。
可选地，所述长度指示字段或对应的扩展指示字段与对应的数据包相邻，或者，所述 多个长度指示字段和所述多个扩展指示字段位于该PDCP PDU的PDCP头中。
可选地，该方法还可以包括：
第一PDCP实体在接收到所述多个数据包中的第M个数据包时启动丢弃定时器，M为大于或等于1的整数；
在丢弃定时器超时的情况下，若第一PDCP实体还未向所述第一RLC实体发送所述PDCP PDU，第一PDCP实体对所述PDCP PDU进行丢包处理。
本申请实施例中，通过设计超时丢弃机制，可以防止发送端的发射机的过渡时延和排队现象。
可选地，在所述发送端的第一分组数据汇聚协议PDCP实体对第一无线承载上连续的多个数据包进行级联处理之前，所述方法还包括：
所述发送端接收配置信息，所述配置信息用于指示所述发送端对所述第一无线承载上的所述多个数据包进行级联处理；
其中，所述发送端的第一分组数据汇聚协议PDCP实体对第一无线承载上连续的多个数据包进行级联处理，包括：
所述第一PDCP实体根据所述配置信息对所述多个数据包进行级联处理。
第二方面，提供了一种传输方法，用于接收端，该方法包括：
接收端的第二分组数据汇聚协议PDCP实体接收接收端的第二无线链路控制RLC实体发送的分组数据汇聚协议服务数据单元PDCP PDU；
第二PDCP实体对所述PDCP PDU进行PDCP逆向处理，得到PDCP SDU，所述PDCPSDU的长度小于或等于第一预设长度；
第二PDCP实体对所述PDCP SDU进行级联逆向处理，得到连续的多个数据包；
第二PDCP实体向所述接收端的上层应用发送所述多个数据包。
本申请实施例的传输方法，通过在PDCP层引入级联功能，由PDCP层对小包进行级联处理，将小包级联为大包，这样能够降低RLC层基于授权级联的数据包的数量，进而能够降低RLC层级联处理开销，提高数据传输效率。另一方面，由于减少了RLC层级联的数据包的数量，因此也能够减少内存的占用。再一方面，通过PDCP层对小包进行级联处理，能够降低PDCP/RLC头的开销，进而能够进一步提高传输效率。
在一种可能的实现方式中，所述PDCP PDU的PDCP头包括级联指示字段，所述级联指示字段中的信息用于指示所述PDCP PDU为进行级联处理后得到的PDCP PDU；
其中，第二PDCP实体对所述PDCP SDU进行级联逆向处理，包括：
第二PDCP实体根据所述级联指示字段中的信息对所述PDCP SDU进行级联逆向处理。
在一种可能的实现方式中，所述多个数据包均为长度小于或等于第二预设长度的数据包。
在一种可能的实现方式中，所述PDCP PDU包括多个长度指示字段，所述多个长度指示字段与所述多个数据包一一对应，所述长度指示字段中的信息用于指示对应的数据包的长度。
在一种可能的实现方式中，所述多个数据包中除最后一个数据包外的其他数据包的长度均不大于第三预设长度。
在一种可能的实现方式中，所述PDCP PDU包括多个长度指示字段和多个扩展指示字段，所述多个长度指示字段与所述多个扩展指示字段一一对应，所述扩展指示字段与对应的长度指示字段相邻，所述多个长度指示字段与所述多个数据包中除最后一个数据包外的其他数据包一一对应，所述长度指示字段中的信息用于指示对应的数据包的长度，所述扩展指示字段中的信息用于指示是否存在与对应的数据包的下一个数据包对应的扩展指示字段和长度指示字段。
在一种可能的实现方式中，在所述接收端的第二分组数据汇聚协议PDCP实体接收所述接收端的第二无线链路控制RLC实体发送的分组数据汇聚协议服务数据单元PDCPPDU之前，所述方法还包括：
所述接收端发送配置信息，所述配置信息用于指示所述发送端对第一无线承载上的所述多个数据包进行级联处理。
第三方面，提供了一种发送端，所述发送端具有实现上述第一方面的方法设计中的发送端的功能。这些功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元。
第四方面，提供了一种接收端，所述接收端具有实现上述第二方面的方法设计中的接收端的功能。这些功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的单元。
第五方面，提供了一种发送端，包括收发器、处理器和存储器。该处理器用于控制收发器收发信号，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得该发送端执行上述第一方面中的方法。
第六方面，提供了一种接收端，包括收发器、处理器和存储器。该处理器用于控制收发器收发信号，该存储器用于存储计算机程序，该处理器用于从存储器中调用并运行该计算机程序，使得该接收端执行第二方面中的方法。
第七方面，提供了一种计算机程序产品，所述计算机程序产品包括：计算机程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述各方面中的方法。
第八方面，提供了一种计算机可读介质，所述计算机可读介质存储有程序代码，当所述计算机程序代码在计算机上运行时，使得计算机执行上述各方面中的方法。
第九方面，提供了一种芯片系统，该芯片系统包括处理器，用于支持通信装置实现上述方面中所涉及的功能，例如，生成，接收，发送，或处理上述方法中所涉及的数据和/或信息。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存发送端必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第十方面，提供了一种芯片系统，该芯片系统包括处理器，用于支持通信装置实现上述中所涉及的功能，例如，生成，接收，发送，或处理上述方法中所涉及的数据和/或信息。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存接收端必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
附图说明
图1是应用于本申请的一个通信系统的示意图。
图2是本申请实施例的传输方法的示意性流程图。
图3是本申请一个实施例的PDCP PDU的格式示意图。
图4是本申请另一实施例的PDCP PDU的格式示意图。
图5是本申请一个实施例的PDCP PDU的格式示意图。
图6是本申请另一实施例的PDCP PDU的格式示意图。
图7是本申请实施例的发送端的示意性框图。
图8是本申请实施例的接收端的示意性框图。
图9是本申请实施例的发送端的示意性框图。
图10是本申请实施例的接收端的示意性框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
应理解，本申请的技术方案可以应用于各种通信系统，例如：全球移动通信(global system of mobile communication，GSM)系统、码分多址(code division multiple access，CDMA)系统、宽带码分多址(wideband code division multiple access，WCDMA)系统、通用分组无线业务(general packet radio service，GPRS)、长期演进(long term evolution，LTE))系统、先进的长期演进(advanced long term evolution，LTE-A)系统、通用移动通信系统(universal mobile telecommunication system，UMTS)或下一代通信系统(例如，第五代通信(fifth-generation，5G)系统)等。其中，5G系统也可以称为新一代无线接入技术(new radio access technology，NR)系统。
为便于理解本申请实施例，首先结合图1简单介绍适用于本申请实施例的通信系统。图1是适用于本申请实施例的传输方法的通信系统100的示意图。如图1所示，该通信系统100包括至少两个通信设备，例如，网络设备110和终端设备120，其中，网络设备110与终端设备120之间可以通过无线连接进行数据通信。
其中，应理解，该网络设备110可以是全球移动通信(GSM)或码分多址(CDMA)中的基站(Base Transceiver Station，BTS)，也可以是宽带码分多址(WCDMA)中的基站(NodeB，NB)，还可以是长期演进(LTE)中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者中继站、接入点或射频拉远单元(remote radio unit，RRU)，或者车载设备、可穿戴设备，还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器，以及未来5G系统中的网络侧设备，如传输点(transmission point，TP)、发送接收点(transmission reception point，TRP)、基站(gNodeB，gNB)、小基站设备等，本申请实施例对此并未特别限定。
还应理解，终端设备120也可以称为用户设备(user equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端设备可以是无线局域网(wireless local area networks，WLAN)中的站点(station，ST)，可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字处理(personal digital assistant，PDA)设备、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备以及下一代通信 系统，例如，5G网络中的终端设备或者未来演进的公共陆地移动网络(public land mobile network，PLMN)网络中的终端设备等，本申请实施例对此并未特别限定。
还应理解，图1仅为便于理解而示例的简化示意图，该通信系统100中还可以包括其他网络设备和/或终端设备，图1中未予以画出。
另外，在本申请实施例中，网络设备为小区提供服务，终端设备通过该小区使用的传输资源(例如，频域资源，或者说，频谱资源)与网络设备进行通信，该小区可以是网络设备(例如基站)对应的小区，小区可以属于宏基站，也可以属于小小区(Small Cell)对应的基站，这里的小小区可以包括：城市小区(Metro cell)、微小区(Micro cell)、微微小区(Pico cell)、毫微微小区(Femto cell)等，这些小小区具有覆盖范围小、发射功率低的特点，适用于提供高速率的数据传输服务。另外，该小区还可以是超级小区(Hypercell)。Hypercell采用用户为中心的无蜂窝无线接入(User Centric No Cell Radio Access，UCNC)技术，即终端设备不再接入某一个固定的物理站点(例如，TRP)，而是接入一个包含一组TRP的逻辑实体(Logical Entity，LE)来获得服务，这种逻辑实体可以称为Hypercell。Hypercell的边界是灵活的，可以根据网络负载、用户分布的变化而变化。Hypercell内的所有TRP对于终端设备都是透明的，终端设备只需要根据Hypercell ID接入，就可以获得Hypercell内TRP的服务，而不再固定与某个TRP连接。
LTE协议架构中，媒体接入控制(media access control，MAC)层在收到授权后，基于授权资源大小调度无线链路控制(radio link control，RLC)层对小包进行级联处理由于级联小包需要一定的时间开销，因此在级联小包时会限制级联的小包的数量，以防止因无法按时完成级联导致数据包无法按授权约束的时间发送的情况。虽然限制级联小包的数量的方式在很多情况下能够避免出错，但是这种方式可能导致授权使用不充分，降低数据传输效率。因此，为提高数据传输效率，RLC层需要基于授权约束的时间级联更多数量的小包，而这就需要降低RLC层级联处理开销。因此，如何降低RLC层级联处理开销，成为亟需解决的技术问题。
有鉴于此，本申请提供了一种传输方法，该方法通过在PDCP层引入级联功能，由PDCP层对小包进行级联处理，将小包级联为大包，这样能够降低RLC层基于授权级联的数据包的数量，进而能够降低RLC层级联处理开销，提高数据传输效率。
首先对本申请涉及的“大包”和“小包”进行简要解释。
“大包”和“小包”是相对的概念，大包相对于小包长度较长，比如，长度为1500字节的数据包可以认为是大包，长度为255字节的数据包可以认为是小包。
一般地，长度小于或等于255字节的数据包都称为小包，长度大于255字节的数据包称为大包。但本申请实施例对此不作限定。
以下，结合图2对本申请实施例的传输方法进行详细描述。应理解，本申请实施例中的发送端可以是终端设备，接收端可以是网络设备。或者，发送端可以是网络设备，接收端可以是终端设备。
还应理解，图2是本申请一个实施例的传输方法的示意性流程图，示出了该方法的详细的通信步骤或操作，但这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者图2中的各种操作的变形。此外，图中的各个步骤可以分别按照与图2所呈现的不同的顺序来执行，并且有可能并非要执行图2中的全部操作。
图2是根据本申请的传输方法的示意性流程图。图2所示的方法可以包括步骤S210～S270。
S210，发送端的第一PDCP实体对第一无线承载上连续的多个数据包进行级联处理，得到分组数据汇聚协议服务数据单元PDCP SDU。其中，所述PDCP SDU的长度小于或等于第一预设长度。
应理解，第一PDCP实体可以是发送端的任一PDCP实体。所述连续多个数据包是指相邻的多个数据包，即顺序排列的多个数据包。
具体而言，第一PDCP实体缓存第一无线承载上连续的数据包，并对缓存的多个数据包进行级联处理，即按照数据包的顺序将该多个数据包串联起来，将级联处理结果作为PDCP SDU。例如，第一PDCP可以参照现有技术中RLC实体对RLC SDU的级联处理，对所述多个数据包进行级联处理。并且，在此情况下，第一预设长度可以等于所述多个数据包的长度之和。但应理解，本申请实施例并不限定第一PDCP实体对所述多个数据包的级联处理是否与现有技术中RLC实体的级联处理相同。
又如，第一PDCP实体对缓存的数据包进行级联处理，直到遇到长度大于第三预设长度(此处暂不作介绍，下文中将详细描述)的数据包，或者直到遇到接收时间比被进行级联处理的第一个数据包的接收时间晚第一预设时间的数据包，或者已经级联的数据包的长度与当前数据包的长度之和大于包长度阈值时，则停止在当前所级联的数据包上继续进行级联处理。然后，第一PDCP实体将级联处理的结果作为PDCP SDU。
可选地，第一预设长度可以是1500字节，但本申请实施例并不限定第一预设长度，比如，第一预设长度还可以是1600字节。应理解，第一预设长度可以根据第一PDCP实体的缓存区的大小设置，一般情况下，第一预设长度小于或等于第一PDCP实体的缓存区的大小。
应理解，本申请实施例对第一预设时间和包长度阈值不作限定。比如，第一预设时间可以是10毫秒(ms)，或者5ms。包长度阈值可以与第一预设长度相等，也可以不相等，例如包长度阈值可以是1500字节，或者1630字节。
可选地，在步骤S210之前，该方法还可以包括：发送端接收接收端发送的配置信息，该配置信息用于指示发送端对第一无线承载上的所述多个数据包进行级联处理。在此情况下，步骤S210具体为：第一PDCP实体根据该配置信息对所述多个数据包进行级联处理。
也就是说，接收端可以指示发送端的PDCP实体是否对于某一承载上的数据包进行级联处理，在接收端指示发送端的PDCP实体对该PDCP实体对该承载上的数据包进行级联处理时，该PDCP实体才对该承载上的数据包进行级联处理。
比如，接收端可以指示第一PDCP实体对第一承载上的数据包进行级联处理，指示第二PDCP实体对第二承载上的数据包不进行级联处理，或者接收端不指示第二PDCP实体对第二承载上的数据包进行级联处理而第二PDCP实体默认不对第二承载上的数据包进行级联处理，那么，第一PDCP实体根据接收端的指示，对第一承载上的数据包进行级联处理，第二PDCP实体根据接收端的指示，不对第二承载上的数据包进行级联处理。
S220，第一PDCP实体对所述PDCP SDU进行PDCP处理，得到分组数据汇聚协议协议数据单元PDCP PDU。
第一PDCP实体对步骤S210中得到的PDCP SDU进行PDCP处理，得到只有一个 PDCP SN的PDCP PDU。
应理解，被进行级联处理的多个数据包可以是用户面数据，也可以是控制面数据。也就是说，第一无线承载可以是数据无线承载DRB，也可以是信令无线承载SRB。第一PDCP实体对用户面数据的PDCP处理可以包括：头压缩、加密和添加PDCP头处理。第一PDCP实体对控制面数据的PDCP处理可以包括：完整性保护、加密和添加PDCP头处理。头压缩、加密、完整性保护和添加PDCP头处理。第一PDCP实体对PDCP SDU的PDCP处理具体地可以参照现有技术，为了简洁，此处不再赘述。
还应理解，上述第一PDCP实体对用户面数据以及控制面数据的PDCP处理仅为示例性说明，本申请并不限定第一PDCP实体对用户面数据以及控制面数据的PDCP处理，比如，随着技术的发展，第一PDCP实体可以对用户面数据以及控制面数据的PDCP处理也可以随之演进和改变。
S230，第一PDCP实体向发送端的第一RLC实体发送所述PDCP PDU。
第一RLC实体接收到该PDCP PDU后，参照现有技术对该PDCP PDU进行处理和发送。
因此，本申请实施例的传输方法，通过在PDCP层引入级联功能，由PDCP层对小包进行级联处理，将小包级联为大包，这样能够降低RLC层基于授权级联的数据包的数量，进而能够降低RLC层级联处理开销，提高数据传输效率。另一方面，由于减少了RLC层级联的数据包的数量，因此也能够减少内存的占用。再一方面，通过PDCP层对小包进行级联处理，能够降低PDCP/RLC头的开销，进而能够进一步提高传输效率。
可选地，该PDCP PDU的PDCP头包括级联指示字段，该级联指示字段中的信息用于指示该PDCP PDU为进行级联处理后得到的PDCP PDU。也就是说，通过级联指示字段可以区分PDCP PDU是否为进行级联处理后得到的。
进一步地，级联指示字段可以占用一个比特。从而，能够节省开销。
示例性的，当该比特为1时，表示PDCP PDU为进行级联处理后得到的，当该比特为0时，表示PDCP PDU为未进行级联处理后得到的，即为常规的PDCP PDU。
应理解，本申请并不限定级联指示字段所占用的比特数，也不限定级联指示字段中的比特值的含义。比如，当级联指示字段占用1个比特时，该比特为1或为0都可以表示PDCP PDU为进行级联处理后得到的，相应地，该比特为0或为1都可以表示PDCP PDU为未进行级联处理后得到的。
可选地，所述多个数据包均为长度小于或等于第二预设长度的数据包。
例如，第二预设长度可以是255字节，第一预设长度可以是1500字节。在此情况下，第一PDCP实体在保证得到的PDCP SDU不超过1500字节的情况下，可以对长度不超过255字节的连续多个数据包进行级联处理。
应理解，本申请实施例对第二预设长度不作特殊限定。第二预设长度例如还可以是127字节。
进一步地，该PDCP PDU还可以包括多个长度指示字段。该多个长度指示字段与该多个数据包一一对应，该长度指示字段中的信息用于指示对应的数据包的长度。
其中，该长度指示字段与对应的数据包相邻，或者该多个长度指示字段位于PDCP头中。
下面，结合图3和图4，对本申请实施例所设计的两种PDCP PDU的格式进行说明。
图3示出了一种PDCP PDU格式的示意图。图3所示的PDCP PDU中，长度指示字段与对应的数据包相邻。该PDCP PDU级联了n个连续的数据包，该PDCP PDU包括PDCP头和PDCP SDU部分。其中，PDCP头包括下述(1)～(5)，PDCP SDU包括(LI1+Data1)～(LIn+Datan)。下面，结合图3，对该PDCP PDU进行详细说明。
(1)D/C：数据类型指示字段，用于指示Data1～Datan为控制面数据或用户面数据。
比如，当D/C为0时，表示Data1～Datan为控制面数据，当D/C为1时，表示Data1～Datan为用户面数据。
(2)P：轮询指示，表示网络设备是否为LTE无线局域网聚合(LTE Wireless Local AreaNetwork Aggregation，LWA)触发了一个PDCP状态报告。具体地可以参照现有技术，为了简洁，此处不再赘述。
(3)R：预留字段。
(4)C：级联指示字段，用于指示该PDCP PDU是否为经过级联处理后得到的PDCPPDU。
(5)PDCP SN：PDCP序列号，具体含义可以参见现有技术。应理解，PDCP SN(cont.)所占的比特也是PDCP SN。如3所示的PDCP SN和PDCP SN(cont.)共同表示PDCP SN，PDCP SN共占18个比特。
(6)LIi：长度指示字段，用于指示Datai的长度，其中i＝1,2，……n。例如，LI1用于指示Data1的长度，LI2用于指示Data2的长度，LIn用于指示Datan的长度。
(7)Datai：PDCP实体所级联的第i个数据包。例如，Data1表示PDCP实体所级联的第1个数据包，Data2表示PDCP实体所级联的第2个数据包，Datan表示PDCP实体所级联的第n个数据包。
需要说明的是，图3所示的格式中每行的长度为一个字节。图3中并未示出Data1～Datan的全部内容，但应理解，Data1～Datan的长度均不大于第二预设长度，且PDCP SDU的长度不大于第一预设长度。
图3所示的PDCP PDU格式中，LIi的长度为8比特，因此第二预设长度为255字节，即Data1～Datan的长度不超过255字节。
应理解，图3中各字段所占用的比特数仅为一个具体示例，本申请并不限定图3所示的各字段所占用的比特数。
图4示出了另一PDCP PDU格式的示意图。图4所示的PDCP PDU中，PDCP头包括多个长度指示字段。该PDCP PDU级联了n个连续的数据包，该PDCP PDU包括PDCP头和PDCP SDU部分。其中，PDCP头包括下述(1)～(6)，PDCP SDU包括Data1～Datan。
图4中各字段的含义可以参照上文中对图3中的各字段的解释说明，为了简洁，此处不再赘述。
需要说明的是，图4所示的格式中每行的长度为一个字节。图4中并未示出Data1～Datan的全部内容，但应理解，Data1～Datan的长度均不大于第二预设长度，且PDCP SDU的长度不大于第一预设长度。
图4所示的PDCP PDU格式中，LIi的长度为8比特，因此第二预设长度为255字节，即Data1～Datan的长度不超过255字节。
应理解，图4中各字段所占用的比特数仅为一个具体示例，本申请并不限定图4所示的各字段所占用的比特数。
可选地，所述多个数据包中除最后一个数据包外的其他数据包的长度均不大于第三预设长度，所述多个数据包中的最后一个数据包的长度大于所述第三预设长度。
第三预设长度可以和第二预设长度相等，也可以不相等。第三预设长度例如可以是127字节，本申请实施例对此不作限定。
进一步地，该PDCP PDU包括多个长度指示字段和多个扩展指示字段。该多个长度指示字段与该多个扩展指示字段一一对应，该扩展指示字段与对应的长度指示字段相邻，该多个长度指示字段与该多个数据包中除最后一个数据包外的其他数据包一一对应。也就是说，除最后一个级联的数据包外，每个数据包都有一个长度指示字段，用于指示该数据包的长度。该长度指示字段中的信息用于指示对应的数据包的长度，该长度指示字段或对应的扩展指示字段与对应的数据包相邻，该扩展指示字段中的信息用于指示是否存在与对应的数据包的下一个数据包对应的扩展指示字段和长度指示字段。
其中，所述长度指示字段或对应的扩展指示字段与对应的数据包相邻，或者，所述多个长度指示字段和所述多个扩展指示字段位于该PDCP PDU的PDCP头中。
下面，结合图5和图6，对本申请实施例所设计的另两种PDCP PDU的格式进行说明。
图5示出了另一PDCP PDU格式的示意图。图5所示的PDCP PDU中，长度指示字段或对应的扩展指示字段与对应的数据包相邻。该PDCP PDU级联了n个连续的数据包，该PDCP PDU包括PDCP头和PDCP SDU部分。其中，PDCP头包括下述(1)～(5)，PDCP SDU包括(E+LI1+Data1)～Datan。下面，结合图5，对该PDCP PDU进行详细说明。
(1)D/C：数据类型指示字段，用于指示Data1～Datan为控制面数据或用户面数据。
比如，当D/C为1时，表示Data1～Datan为控制面数据，当D/C为0时，表示Data1～Datan为用户面数据。
(2)P：轮询指示，表示网络设备是否为LWA触发了一个PDCP状态报告。具体地可以参照现有技术，为了简洁，此处不再赘述。
(3)R：预留字段。
(4)C：级联指示字段，用于指示该PDCP PDU是否为经过级联处理后得到的PDCPPDU。
(5)PDCP SN：PDCP序列号，具体含义可以参见现有技术。应理解，PDCP SN(cont.)所占的比特也是PDCP SN。如3所示的PDCP SN和PDCP SN(cont.)共同表示PDCP SN，PDCP SN共占18个比特。
(6)E：扩展指示字段，用于指示是否存在与对应的数据包的下一个数据包对应的扩展指示字段和长度指示字段。
比如，0表示当前的E+LI+Data之后直接跟随另一Data，1表示当前的E+LI+Data之后跟随另一E+LI+Data。在此情况下，本申请实施例中，前n-2个E的值均为1，第n-1个E的值为0。
(7)LIi：长度指示字段，用于指示Datai的长度，其中i＝1,2，……n。例如，LI1用于指示Data1的长度，LI2用于指示Data2的长度，LIn用于指示Datan的长度。
(8)Datai：PDCP实体所级联的第i个数据包。例如，Data1表示PDCP实体所级联的第1个数据包，Data2表示PDCP实体所级联的第2个数据包，Datan表示PDCP实体所级联的第n个数据包。
需要说明的是，图5所示的格式中每行的长度为一个字节。图5中并未示出Data1～Datan的全部内容，但应理解，Data1～Data(n-1)的长度均不大于第三预设长度，PDCP SDU的长度不大于第一预设长度。
图5所示的PDCP PDU格式中，LIi的长度为7比特，因此第三预设长度为127字节，因此Data1～Data(n-1)的长度不超过127字节，但最后一个数据包(即，Datan)的长度可以大于127字节。
应理解，图5中各字段所占用的比特数仅为一个具体示例，本申请并不限定图5所示的各字段所占用的比特数。还应理解，图5中所示的E和LIi的位置也可以互换，本申请实施例对此不作限定。
图6示出了另一PDCP PDU格式的示意图。图6所示的PDCP PDU中，长度指示字段和扩展指示字段位于该PDCP PDU的PDCP头中。该PDCP PDU级联了n个连续的数据包，该PDCP PDU包括PDCP头和PDCP SDU部分。其中，PDCP头包括下述(1)～(7)，PDCP SDU包括Data1～Datan。
图6中各字段的含义可以参照上文中对图5中的各字段的解释说明，为了简洁，此处不再赘述。
需要说明的是，图6所示的格式中每行的长度为一个字节。图6中并未示出Data1～Datan的全部内容，但应理解，Data1～Data(n-1)的长度均不大于第三预设长度，PDCP SDU的长度不大于第一预设长度。
图6所示的PDCP PDU格式中，LIi的长度为7比特，因此第三预设长度为127字节，因此Data1～Data(n-1)的长度不超过127字节，但最后一个数据包(即，Datan)的长度可以大于127字节。
应理解，图6中各字段所占用的比特数仅为一个具体示例，本申请并不限定图6所示的各字段所占用的比特数。还应理解，图6中所示的E和LIi的位置也可以互换，本申请实施例对此不作限定。
可选地，该方法还可以包括：
第一PDCP实体在接收到所述多个数据包中的第M个数据包时启动丢弃定时器，M为大于或等于1的整数；在丢弃定时器超时的情况下，若第一PDCP实体还未向第一RLC实体发送所述PDCP PDU，第一PDCP实体对所述PDCP PDU进行丢包处理。
比如，所述多个数据包的个数为5个，第一PDCP实体在接收到第三个数据包时，可以启动丢弃定时器，若在丢弃定时器超时时，第一PDCP实体还没有向第一RLC实体发送经过级联处理和PDCP处理后的到的PDCP PDU，则第一PDCP实体将PDCP PDU作为一个整体进行丢弃。
又如，在第一PDCP实体对10毫秒(ms)内连续接收到的数据包进行级联处理的情况下，第一PDCP实体可以在第5秒时启动丢弃定时器，若在丢弃定时器超时时，第一PDCP实体还没有向第一RLC实体发送经过级联处理和PDCP处理后的到的PDCP PDU，则第一PDCP实体将PDCP PDU作为一个整体进行丢弃。
应理解，所述丢弃定时器可以是Discard_Timer定时器，但本申请实施例对此不作限定。
本申请实施例中，通过设计超时丢弃机制，可以防止发送端的发射机的过渡时延和排队现象。
S240，接收端的PDCP第二PDCP实体接收接收端的第二RLC实体发送的PDCP PDU。
应理解，这里的PDCP PDU即为第一PDCP实体发送至第一RLC实体的PDCP PDU。
具体来讲，发送端的第一RLC实体接收到第一PDCP实体发送的PDCP PDU后，可以按照现有技术对该PDCP PDU进行RLC处理，例如，进行级联或拆分、添加RLC头等操作，得到RLC PDU，然后第一RLC实体将该RLC PDU发送至第一MAC实体。第一MAC实体可以按照现有技术对该RLC PDU进行MAC处理，例如进行添加MAC头操作，得到传输块，然后第一MAC实体将该传输块发送至物理层。物理层对该传输块进行调制编码等操作，将经过物理层处理后的传输块发送至接收端。接收端接收到的发送端发送的经过物理层处理后的传输块后，对该经过物理层处理后的传输块进行解调解码等操作，得到该传输块，然后发送至接收端的第二MAC实体。第二MAC实体可以按照现有技术对该传输块进行MAC逆向处理，例如进行去MAC头操作，并将处理结果发送至第二RLC实体。第二RLC实体可以参照现有技术对该处理结果进行RLC逆向处理，例如进行拆分处理，得到PDCP PDU，然后第二RLC实体将该PDCP PDU发送至第二PDCP实体。第二PDCP实体接收到的PDCP PDU即为第一PDCP实体发送至第一RLC实体的PDCPPDU。
S250，第二PDCP实体对该PDCP PDU进行PDCP逆向处理，得到所述PDCP SDU。
应理解，所述PDCP逆向处理是从PDCP PDU得到PDCP SDU的过程，例如可以包括去PDCP头、解密等操作。PDCP逆向处理具体地可以参照现有技术，为了简洁，此处不再赘述。
S260，第二PDCP实体对所述PDCP SDU进行级联逆向处理，得到所述多个数据包。
应理解，所述级联逆向处理是从PDCP SDU得到多个数据包的过程。
具体地，第二PDCP实体接收到该PDCP PDU后，可以进行去PDCP头、解密等操作，得到PDCP SDU。然后，第二PDCP实体对该PDCP SDU进行级联逆向处理，将该PDCP SDU拆分为多个连续的数据包。比如，第二PDCP实体可以参照现有技术中RLC实体对RLC SDU的级联逆向处理，对该PDCP SDU进行级联逆向处理。又如，第二PDCP实体可以基于图3-图6所示的任一格式，根据级联指示字段，对该PDCP SDU进行拆分处理，得到多个连续的数据包，即Data1～Datan。
S270，第二PDCP实体向接收端的上层应用发送所述多个数据包。
至此，即完成了接收端对所述多个数据包的调度。
本申请实施例的传输方法，通过在PDCP层引入级联功能，由PDCP层对小包进行级联处理，将小包级联为大包，这样能够降低RLC层基于授权级联的数据包的数量，进而能够降低RLC层级联处理开销，提高数据传输效率。另一方面，由于减少了RLC层级联的数据包的数量，因此也能够减少内存的占用。再一方面，通过PDCP层对小包进行级联处理，能够降低PDCP/RLC包头的开销，进而能够进一步提高传输效率。
图7是本申请实施例的发送端700的示意性框图。如图7所示，该发送端700包括： 处理单元710和收发单元720。
处理单元710，用于对第一无线承载上连续的多个数据包进行级联处理，得到分组数据汇聚协议服务数据单元PDCP SDU，PDCP SDU的长度小于或等于第一预设长度。
处理单元710还用于，对PDCP SDU进行PDCP处理，得到分组数据汇聚协议协议数据单元PDCP PDU。
收发单元720，用于向发送端的第一无线链路控制RLC实体发送PDCP PDU。
可选地，PDCP PDU的PDCP头包括级联指示字段，级联指示字段中的信息用于指示PDCP PDU为进行级联处理后得到的PDCP PDU。
可选地，所述多个数据包均为长度小于或等于第二预设长度的数据包。
进一步地，该PDCP PDU包括多个长度指示字段，多个长度指示字段与多个数据包一一对应，长度指示字段中的信息用于指示对应的数据包的长度。
可选地，所述多个数据包中除最后一个数据包外的其他数据包的长度均不大于第三预设长度。
进一步地，该PDCP PDU包括多个长度指示字段和多个扩展指示字段，多个长度指示字段与多个扩展指示字段一一对应，扩展指示字段与对应的长度指示字段相邻，多个长度指示字段与多个数据包中除最后一个数据包外的其他数据包一一对应，长度指示字段中的信息用于指示对应的数据包的长度，扩展指示字段中的信息用于指示是否存在与对应的数据包的下一个数据包对应的扩展指示字段和长度指示字段。
可选地，处理单元710还用于：
在收发单元接收到多个数据包中的第M个数据包时启动丢弃定时器，M为大于或等于1的整数；
在丢弃定时器超时的情况下，若发送单元还未向第一RLC实体发送PDCP PDU，对PDCP PDU进行丢包处理。
可选地，收发单元720还用于：接收配置信息，配置信息用于指示发送端对第一无线承载上的多个数据包进行级联处理。其中，处理单元710具体用于：根据配置信息对多个数据包进行级联处理。
应理解，这里的发送端700以功能单元的形式体现。这里的术语“单元”可以指应用特有集成电路(application specific integrated circuit，ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。在一个可选例子中，本领域技术人员可以理解，发送端700可以具体为上述实施例中的发送端，发送端700可以用于执行上述方法实施例中与发送端对应的各个流程和/或步骤，为避免重复，在此不再赘述。
图8是本申请实施例的接收端800的示意性框图。如图8所示，该接收端800包括：收发单元810和处理单元820。
收发单元810，用于接收所述接收端的第二无线链路控制RLC实体发送的分组数据汇聚协议服务数据单元PDCP PDU。
处理单元820，用于对PDCP PDU进行PDCP逆向处理，得到PDCP SDU，PDCP SDU的长度小于或等于第一预设长度。
处理单元820还用于，对PDCP SDU进行级联逆向处理，得到连续的多个数据包。
收发单元810还用于，向接收端的上层应用发送多个数据包。
可选地，该PDCP PDU的PDCP头包括级联指示字段，级联指示字段中的信息用于指示PDCP PDU为进行级联处理后得到的PDCP PDU。其中，处理单元820用于：根据级联指示字段中的信息对PDCP SDU进行级联逆向处理。
可选地，所述多个数据包均为长度小于或等于第二预设长度的数据包。
进一步地，该PDCP PDU包括多个长度指示字段，多个长度指示字段与多个数据包一一对应，长度指示字段中的信息用于指示对应的数据包的长度。
可选地，所述多个数据包中除最后一个数据包外的其他数据包的长度均不大于第三预设长度。
进一步地，该PDCP PDU包括多个长度指示字段和多个扩展指示字段，多个长度指示字段与多个扩展指示字段一一对应，扩展指示字段与对应的长度指示字段相邻，多个长度指示字段与多个数据包中除最后一个数据包外的其他数据包一一对应，长度指示字段中的信息用于指示对应的数据包的长度，扩展指示字段中的信息用于指示是否存在与对应的数据包的下一个数据包对应的扩展指示字段和长度指示字段。
可选地，收发单元810还用于：发送配置信息，配置信息用于指示发送端对第一无线承载上的多个数据包进行级联处理。
应理解，这里的接收端800以功能单元的形式体现。这里的术语“单元”可以指应用特有集成电路(application specific integrated circuit，ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。在一个可选例子中，本领域技术人员可以理解，接收端800可以具体为上述实施例中的接收端，接收端800可以用于执行上述方法实施例中与接收端对应的各个流程和/或步骤，为避免重复，在此不再赘述。
图9是本申请实施例的另一发送端900的示意性框图。如图9所示，该发送端900包括处理器910、收发器920和存储器930。其中，处理器910、收发器920和存储器930通过内部连接通路互相通信，该存储器930用于存储指令，该处理器910用于执行该存储器930存储的指令，以控制该收发器920发送信号和/或接收信号。
其中，处理器910，用于对第一无线承载上连续的多个数据包进行级联处理，得到分组数据汇聚协议服务数据单元PDCP SDU，所述PDCP SDU的长度小于或等于第一预设长度；
所述处理器910还用于，对所述PDCP SDU进行PDCP处理，得到分组数据汇聚协议协议数据单元PDCP PDU；
收发器920，用于向所述发送端的第一无线链路控制RLC实体发送所述PDCP PDU。
应理解，发送端900可以具体为上述实施例中的发送端，并且可以用于执行上述方法实施例中与发送端对应的各个步骤和/或流程。可选地，该存储器930可以包括只读存储器和随机存取存储器，并向处理器提供指令和数据。存储器的一部分还可以包括非易失性随机存取存储器。例如，存储器还可以存储设备类型的信息。该处理器910可以用于执行存储器中存储的指令，并且当该处理器910执行存储器中存储的指令时，该处理器910用于执行上述与该发送端对应的方法实施例的各个步骤和/或流程。
图10是本申请实施例的另一接收端1000的示意性框图。如图10所示，该接收端1000 包括处理器1010、收发器1020和存储器1030。其中，处理器1010、收发器1020和存储器1030通过内部连接通路互相通信，该存储器1030用于存储指令，该处理器1010用于执行该存储器1030存储的指令，以控制该收发器1020发送信号和/或接收信号。
其中，收发器1020，用于接收所述接收端的第二无线链路控制RLC实体发送的分组数据汇聚协议服务数据单元PDCP PDU；
处理器1010，用于对所述PDCP PDU进行PDCP逆向处理，得到PDCP SDU，所述PDCP SDU的长度小于或等于第一预设长度；
所述处理器1010还用于，对所述PDCP SDU进行级联逆向处理，得到连续的多个数据包；
所述收发器1020还用于，向所述接收端的上层应用发送所述多个数据包。
应理解，接收端1000可以具体为上述实施例中的发送端，并且可以用于执行上述方法实施例中与接收端对应的各个步骤和/或流程。可选地，该存储器1030可以包括只读存储器和随机存取存储器，并向处理器提供指令和数据。存储器的一部分还可以包括非易失性随机存取存储器。例如，存储器还可以存储设备类型的信息。该处理器1010可以用于执行存储器中存储的指令，并且当该处理器1010执行存储器中存储的指令时，该处理器1010用于执行上述与该接收端对应的方法实施例的各个步骤和/或流程。
应理解，本申请实施例中，上述处理器可以为中央处理单元(central processing unit，CPU)，该处理器还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还应理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的随机存取存储器(random access memory，RAM)可用，例如静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
上述实施例，可以全部或部分地通过软件、硬件、固件或其他任意组合来实现。当使用软件实现时，上述实施例可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令或计算机程序。在计算机上加载或执行所述计算机指令或计算机程序时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以为通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可 以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集合的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质。半导体介质可以是固态硬盘。
应理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，这些修改 或替换都应涵盖在本申请的保护范围之内。都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (30)

  1. 一种传输方法，其特征在于，用于发送端，所述方法包括：
    所述发送端的第一分组数据汇聚协议PDCP实体对第一无线承载上连续的多个数据包进行级联处理，得到分组数据汇聚协议服务数据单元PDCP SDU，所述PDCP SDU的长度小于或等于第一预设长度；
    所述第一PDCP实体对所述PDCP SDU进行PDCP处理，得到分组数据汇聚协议协议数据单元PDCP PDU；
    所述第一PDCP实体向所述发送端的第一无线链路控制RLC实体发送所述PDCP PDU。
  2. 如权利要求1所述的方法，其特征在于，所述PDCP PDU的PDCP头包括级联指示字段，所述级联指示字段中的信息用于指示所述PDCP PDU为进行级联处理后得到的PDCP PDU。
  3. 如权利要求1或2所述的方法，其特征在于，所述多个数据包均为长度小于或等于第二预设长度的数据包。
  4. 如权利要求3所述的方法，其特征在于，所述PDCP PDU包括多个长度指示字段，所述多个长度指示字段与所述多个数据包一一对应，所述长度指示字段中的信息用于指示对应的数据包的长度。
  5. 如权利要求1或2所述的方法，其特征在于，所述多个数据包中除最后一个数据包外的其他数据包的长度均不大于第三预设长度。
  6. 如权利要求5所述的方法，其特征在于，所述PDCP PDU包括多个长度指示字段和多个扩展指示字段，所述多个长度指示字段与所述多个扩展指示字段一一对应，所述扩展指示字段与对应的长度指示字段相邻，所述多个长度指示字段与所述多个数据包中除最后一个数据包外的其他数据包一一对应，所述长度指示字段中的信息用于指示对应的数据包的长度，所述扩展指示字段中的信息用于指示是否存在与对应的数据包的下一个数据包对应的扩展指示字段和长度指示字段。
  7. 如权利要求1至6中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一PDCP实体在接收到所述多个数据包中的第M个数据包时启动丢弃定时器，M为大于或等于1的整数；
    在所述丢弃定时器超时的情况下，若所述第一PDCP实体还未向所述第一RLC实体发送所述PDCP PDU，所述第一PDCP实体对所述PDCP PDU进行丢包处理。
  8. 如权利要求1至7中任一项所述的方法，其特征在于，在所述发送端的第一分组数据汇聚协议PDCP实体对第一无线承载上连续的多个数据包进行级联处理之前，所述方法还包括：
    所述发送端接收配置信息，所述配置信息用于指示所述发送端对所述第一无线承载上的所述多个数据包进行级联处理；
    其中，所述发送端的第一分组数据汇聚协议PDCP实体对第一无线承载上连续的多个数据包进行级联处理，包括：
    所述第一PDCP实体根据所述配置信息对所述多个数据包进行级联处理。
  9. 一种传输方法，其特征在于，用于接收端，所述方法包括：
    所述接收端的第二分组数据汇聚协议PDCP实体接收所述接收端的第二无线链路控制RLC实体发送的分组数据汇聚协议服务数据单元PDCP PDU；
    所述第二PDCP实体对所述PDCP PDU进行PDCP逆向处理，得到PDCP SDU，所述PDCP SDU的长度小于或等于第一预设长度；
    所述第二PDCP实体对所述PDCP SDU进行级联逆向处理，得到连续的多个数据包；
    所述第二PDCP实体向所述接收端的上层应用发送所述多个数据包。
  10. 如权利要求9所述的方法，其特征在于，所述PDCP PDU的PDCP头包括级联指示字段，所述级联指示字段中的信息用于指示所述PDCP PDU为进行级联处理后得到的PDCP PDU；
    其中，所述第二PDCP实体对所述PDCP SDU进行级联逆向处理，包括：
    所述第二PDCP实体根据所述级联指示字段中的信息对所述PDCP SDU进行级联逆向处理。
  11. 如权利要求9或10所述的方法，其特征在于，所述多个数据包均为长度小于或等于第二预设长度的数据包。
  12. 如权利要求11所述的方法，其特征在于，所述PDCP PDU包括多个长度指示字段，所述多个长度指示字段与所述多个数据包一一对应，所述长度指示字段中的信息用于指示对应的数据包的长度。
  13. 如权利要求9或10所述的方法，其特征在于，所述多个数据包中除最后一个数据包外的其他数据包的长度均不大于第三预设长度。
  14. 如权利要求13所述的方法，其特征在于，所述PDCP PDU包括多个长度指示字段和多个扩展指示字段，所述多个长度指示字段与所述多个扩展指示字段一一对应，所述扩展指示字段与对应的长度指示字段相邻，所述多个长度指示字段与所述多个数据包中除最后一个数据包外的其他数据包一一对应，所述长度指示字段中的信息用于指示对应的数据包的长度，所述扩展指示字段中的信息用于指示是否存在与对应的数据包的下一个数据包对应的扩展指示字段和长度指示字段。
  15. 如权利要求9至14中任一项所述的方法，其特征在于，在所述接收端的第二分组数据汇聚协议PDCP实体接收所述接收端的第二无线链路控制RLC实体发送的分组数据汇聚协议服务数据单元PDCP PDU之前，所述方法还包括：
    所述接收端发送配置信息，所述配置信息用于指示所述发送端对第一无线承载上的所述多个数据包进行级联处理。
  16. 一种发送端，其特征在于，包括：
    处理单元，用于对第一无线承载上连续的多个数据包进行级联处理，得到分组数据汇聚协议服务数据单元PDCP SDU，所述PDCP SDU的长度小于或等于第一预设长度；
    所述处理单元还用于，对所述PDCP SDU进行PDCP处理，得到分组数据汇聚协议协议数据单元PDCP PDU；
    收发单元，用于向所述发送端的第一无线链路控制RLC实体发送所述PDCP PDU。
  17. 如权利要求16所述的发送端，其特征在于，所述PDCP PDU的PDCP头包括级 联指示字段，所述级联指示字段中的信息用于指示所述PDCP PDU为进行级联处理后得到的PDCP PDU。
  18. 如权利要求16或17所述的发送端，其特征在于，所述多个数据包均为长度小于或等于第二预设长度的数据包。
  19. 如权利要求18所述的发送端，其特征在于，所述PDCP PDU包括多个长度指示字段，所述多个长度指示字段与所述多个数据包一一对应，所述长度指示字段中的信息用于指示对应的数据包的长度。
  20. 如权利要求16或17所述的发送端，其特征在于，所述多个数据包中除最后一个数据包外的其他数据包的长度均不大于第三预设长度。
  21. 如权利要求20所述的发送端，其特征在于，所述PDCP PDU包括多个长度指示字段和多个扩展指示字段，所述多个长度指示字段与所述多个扩展指示字段一一对应，所述扩展指示字段与对应的长度指示字段相邻，所述多个长度指示字段与所述多个数据包中除最后一个数据包外的其他数据包一一对应，所述长度指示字段中的信息用于指示对应的数据包的长度，所述扩展指示字段中的信息用于指示是否存在与对应的数据包的下一个数据包对应的扩展指示字段和长度指示字段。
  22. 如权利要求16至21中任一项所述的发送端，其特征在于，所述处理单元还用于：
    在所述收发单元接收到所述多个数据包中的第M个数据包时启动丢弃定时器，M为大于或等于1的整数；
    在所述丢弃定时器超时的情况下，若所述发送单元还未向所述第一RLC实体发送所述PDCP PDU，对所述PDCP PDU进行丢包处理。
  23. 如权利要求16至22中任一项所述的发送端，其特征在于，所述收发单元还用于：
    接收配置信息，所述配置信息用于指示所述发送端对所述第一无线承载上的所述多个数据包进行级联处理；
    其中，所述处理单元具体用于：
    根据所述配置信息对所述多个数据包进行级联处理。
  24. 一种接收端，其特征在于，包括：
    收发单元，用于接收所述接收端的第二无线链路控制RLC实体发送的分组数据汇聚协议服务数据单元PDCP PDU；
    处理单元，用于对所述PDCP PDU进行PDCP逆向处理，得到PDCP SDU，所述PDCP SDU的长度小于或等于第一预设长度；
    所述处理单元还用于，对所述PDCP SDU进行级联逆向处理，得到连续的多个数据包；
    所述收发单元还用于，向所述接收端的上层应用发送所述多个数据包。
  25. 如权利要求24所述的接收端，其特征在于，所述PDCP PDU的PDCP头包括级联指示字段，所述级联指示字段中的信息用于指示所述PDCP PDU为进行级联处理后得到的PDCP PDU；
    其中，所述处理单元用于：
    根据所述级联指示字段中的信息对所述PDCP SDU进行级联逆向处理。
  26. 如权利要求24或25所述的接收端，其特征在于，所述多个数据包均为长度小于 或等于第二预设长度的数据包。
  27. 如权利要求26所述的接收端，其特征在于，所述PDCP PDU包括多个长度指示字段，所述多个长度指示字段与所述多个数据包一一对应，所述长度指示字段中的信息用于指示对应的数据包的长度。
  28. 如权利要求24或25所述的接收端，其特征在于，所述多个数据包中除最后一个数据包外的其他数据包的长度均不大于第三预设长度。
  29. 如权利要求28所述的接收端，其特征在于，所述PDCP PDU包括多个长度指示字段和多个扩展指示字段，所述多个长度指示字段与所述多个扩展指示字段一一对应，所述扩展指示字段与对应的长度指示字段相邻，所述多个长度指示字段与所述多个数据包中除最后一个数据包外的其他数据包一一对应，所述长度指示字段中的信息用于指示对应的数据包的长度，所述扩展指示字段中的信息用于指示是否存在与对应的数据包的下一个数据包对应的扩展指示字段和长度指示字段。
  30. 如权利要求24至29中任一项所述的接收端，其特征在于，所述收发单元还用于：
    发送配置信息，所述配置信息用于指示所述发送端对第一无线承载上的所述多个数据包进行级联处理。
PCT/CN2018/100932 2017-08-18 2018-08-17 传输方法、发送端和接收端 WO2019034130A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710714171.4A CN109413692A (zh) 2017-08-18 2017-08-18 传输方法、发送端和接收端
CN201710714171.4 2017-08-18

Publications (1)

Publication Number Publication Date
WO2019034130A1 true WO2019034130A1 (zh) 2019-02-21

Family

ID=65362133

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/100932 WO2019034130A1 (zh) 2017-08-18 2018-08-17 传输方法、发送端和接收端

Country Status (2)

Country Link
CN (1) CN109413692A (zh)
WO (1) WO2019034130A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3996341A4 (en) * 2019-07-25 2022-07-13 Guangdong Oppo Mobile Telecommunications Corp., Ltd. METHOD OF TRANSMITTING DATA, TRANSMIT-SIDE DEVICE AND RECEIVE-SIDE DEVICE
WO2023066114A1 (zh) * 2021-10-19 2023-04-27 维沃移动通信有限公司 数据处理方法、装置及终端
WO2023217013A1 (zh) * 2022-05-09 2023-11-16 维沃移动通信有限公司 数据包级联的处理方法、装置、终端及可读存储介质

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112770267B (zh) * 2019-10-21 2022-05-13 华为技术有限公司 一种通信方法、装置和系统
CN110995750B (zh) * 2019-12-18 2021-09-28 展讯通信（上海）有限公司 终端设备
CN111163081B (zh) * 2019-12-26 2022-04-22 展讯通信（上海）有限公司 数据传输方法、装置、设备及存储介质
CN115334588A (zh) * 2021-05-10 2022-11-11 华为技术有限公司 一种数据传输方法及装置
CN117082005A (zh) * 2022-05-09 2023-11-17 维沃移动通信有限公司 数据包丢弃的处理方法、装置、终端及可读存储介质
CN117202257A (zh) * 2022-05-31 2023-12-08 荣耀终端有限公司 一种用户数据处理方法和装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101729524A (zh) * 2008-11-03 2010-06-09 大唐移动通信设备有限公司 一种数据处理方法、装置、rlc实体及pdcp实体
CN101932128A (zh) * 2009-06-25 2010-12-29 大唐移动通信设备有限公司 一种数据链路层的数据收发处理方法及设备
CN102104535A (zh) * 2009-12-18 2011-06-22 华为技术有限公司 一种pdcp数据发送方法、装置及系统
CN102300259A (zh) * 2011-09-16 2011-12-28 电信科学技术研究院 一种数据块级联和拆解处理方法、装置及系统
WO2017030348A1 (ko) * 2015-08-14 2017-02-23 엘지전자 주식회사 무선 통신 시스템에서 v2x 메시지 송수신 방법 및 이를 위한 장치

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104581824A (zh) * 2013-10-17 2015-04-29 中兴通讯股份有限公司 一种数据包分流传输的方法及系统
CN104168214B (zh) * 2014-08-21 2018-02-27 京信通信系统（中国）有限公司 一种丢弃分组数据的方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101729524A (zh) * 2008-11-03 2010-06-09 大唐移动通信设备有限公司 一种数据处理方法、装置、rlc实体及pdcp实体
CN101932128A (zh) * 2009-06-25 2010-12-29 大唐移动通信设备有限公司 一种数据链路层的数据收发处理方法及设备
CN102104535A (zh) * 2009-12-18 2011-06-22 华为技术有限公司 一种pdcp数据发送方法、装置及系统
CN102300259A (zh) * 2011-09-16 2011-12-28 电信科学技术研究院 一种数据块级联和拆解处理方法、装置及系统
WO2017030348A1 (ko) * 2015-08-14 2017-02-23 엘지전자 주식회사 무선 통신 시스템에서 v2x 메시지 송수신 방법 및 이를 위한 장치

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3996341A4 (en) * 2019-07-25 2022-07-13 Guangdong Oppo Mobile Telecommunications Corp., Ltd. METHOD OF TRANSMITTING DATA, TRANSMIT-SIDE DEVICE AND RECEIVE-SIDE DEVICE
WO2023066114A1 (zh) * 2021-10-19 2023-04-27 维沃移动通信有限公司 数据处理方法、装置及终端
WO2023217013A1 (zh) * 2022-05-09 2023-11-16 维沃移动通信有限公司 数据包级联的处理方法、装置、终端及可读存储介质

Also Published As

Publication number Publication date
CN109413692A (zh) 2019-03-01

Similar Documents

Publication Publication Date Title
WO2019034130A1 (zh) 传输方法、发送端和接收端
US11477307B2 (en) Media access control protocol data unit processing method and apparatus
WO2018227814A1 (zh) 数据指示方法、装置、通信系统
WO2019019224A1 (zh) 命令接收方法、装置及通信系统
WO2019072170A1 (zh) 通信方法和通信装置
TW201906443A (zh) 用於傳輸數據的方法、終端設備和網絡設備
WO2019056277A1 (zh) 传输信息的方法和设备
WO2018228558A1 (zh) 一种传输数据的方法、网络设备和终端设备
WO2021081824A1 (zh) 无线通信方法和终端设备
WO2018121227A1 (zh) 发送控制信息的方法和装置及接收控制信息的方法和装置
TW201911901A (zh) 資料傳輸的方法、終端設備和網路設備
WO2019076347A1 (zh) 通信方法和通信装置
WO2020223976A1 (zh) 无线通信方法、终端设备和网络设备
WO2019079973A1 (zh) 传输数据的方法、终端设备和网络设备
WO2020087258A1 (zh) 指示pdcp复制数据的状态的方法、终端设备和网络设备
WO2019084800A1 (zh) 上报射频能力的方法、终端设备和网络设备
WO2018120107A1 (zh) 通信方法、网络设备和终端设备
WO2022152092A1 (zh) 数据传输控制方法和装置
WO2022151980A1 (zh) 资源指示方法、装置和存储介质
WO2019157719A1 (zh) 无线通信方法和设备
WO2018053685A1 (zh) 数据封装方法、装置以及通信系统
WO2022056877A1 (zh) 信息传输方法、终端设备和网络设备
WO2018126450A1 (zh) 无线通信的方法和设备
WO2022032515A1 (zh) 无线通信方法、终端设备和网络设备
WO2021142767A1 (zh) 通信方法和通信装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18846474

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18846474

Country of ref document: EP

Kind code of ref document: A1