WO2018166517A1 - Procédé de transmission de données, dispositif de transmission de données et dispositif de réception de données - Google Patents

Procédé de transmission de données, dispositif de transmission de données et dispositif de réception de données Download PDF

Info

Publication number
WO2018166517A1
WO2018166517A1 PCT/CN2018/079251 CN2018079251W WO2018166517A1 WO 2018166517 A1 WO2018166517 A1 WO 2018166517A1 CN 2018079251 W CN2018079251 W CN 2018079251W WO 2018166517 A1 WO2018166517 A1 WO 2018166517A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdu
pdcp
data
rlc
entity
Prior art date
Application number
PCT/CN2018/079251
Other languages
English (en)
Chinese (zh)
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 WO2018166517A1 publication Critical patent/WO2018166517A1/fr

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
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0028—Formatting
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0078—Avoidance of errors by organising the transmitted data in a format specifically designed to deal with errors, e.g. location
    • H04L1/0079—Formats for control data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0078—Avoidance of errors by organising the transmitted data in a format specifically designed to deal with errors, e.g. location
    • H04L1/0079—Formats for control data
    • H04L1/0082—Formats for control data fields explicitly indicating existence of error in data being transmitted, e.g. so that downstream stations can avoid decoding erroneous packet; relays
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • 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 technologies, and in particular, to a data transmission method, a data transmitting device, and a data receiving device.
  • the user plane data is in the Internet Protocol (IP) packet format, and the Packet Data Convergence Protocol (PDCP) layer and the Radio Link Control (RLC) are used.
  • IP Internet Protocol
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • the layer, the MAC (Media Access Control) layer, and the physical (PHY) layer are transmitted between the data transmitting end and the data receiving end.
  • the working modes of data transmission at the RLC layer mainly include Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM).
  • TM mode the data sent by the PDCP layer or the MAC layer is directly delivered to the MAC layer or the PDCP layer without any processing at the RLC layer.
  • UM mode there is no feedback on the transmitted packets.
  • AM mode the transmitted data has corresponding feedback information from the opposite end.
  • the data that the PDCP layer delivers to the MAC layer is segmented and cascaded through the RLC layer, and the data that the MAC layer delivers to the PDCP layer is reorganized, reordered, and repeatedly detected through the RLC layer. And assigning a corresponding sequence number (SN) to distinguish different RLC Protocol Data Units (PDUs).
  • SN sequence number
  • data transmission at the RLC layer may not require cascading of data.
  • the RLC entity no longer performs cascading of data.
  • the header overhead of the data packet is increased, which affects the data transmission efficiency.
  • the embodiment of the present application provides a data transmission method, a data sending device, and a data receiving device, so as to reduce header overhead of data packets and improve data transmission efficiency.
  • a data transmission method in which a PDCP entity at a data transmitting end sends a PDCP PDU to an RLC entity of a data transmitting end, and an RLC entity at a data transmitting end receives a PDCP PDU sent by a PDCP entity at a data transmitting end, and A corresponding RLC PDU is generated according to the PDCP PDU, and the PDCP PDU and the RLC PDU use a sequence number assigned by the PDCP entity.
  • the RLC entity of the data transmitting end sends the RLC PDU to the RLC entity of the data receiving end.
  • the RLC entity at the data receiving end receives the RLC PDU sent by the RLC entity at the data transmitting end, and uses the sequence number to perform repeated packet detection or packet ordering.
  • the RLC entity at the data receiving end sends the RLC SDU to the PDCP entity at the data receiving end, which can reduce redundant information in the data transmission process and improve data transmission efficiency.
  • the PDCP data PDU and the PDCP control PDU each include a sequence number SN. If the RLC PDU is a complete RLC PDU, the RLC PDU does not include a sequence number SN, if the RLC The PDU is a segmented RLC PDU, and the RLC PDU includes a sequence number SN.
  • the RLC entity of the data receiving end performs repeated packet detection or data packet ordering using the PDCP data PDU and the sequence number SN included in the PDCP control PDU, and if the RLC PDU is a segment RLC PDU, the data receiving The RLC entity of the end uses the sequence number SN included in the RLC PDU for repeated packet detection or data packet ordering. With this design, the RLC PDU does not include the sequence number SN allocated by the RLC entity, which can reduce the RLC PDU during data transmission. Redundant information to improve data transmission efficiency.
  • the PDCP data PDU includes a sequence number SN
  • the PDCP control PDU does not include a sequence number SN
  • the RLC PDU corresponds to the RLC PDU, if the RLC PDU is a complete RLC PDU.
  • the RLC PDU does not include the sequence number SN
  • the RLC entity of the data receiving end uses the sequence number SN included in the PDCP data PDU to perform repeated packet detection or data packet ordering.
  • the RLC PDU is a segment RLC PDU
  • the RLC PDU includes a sequence number SN
  • the RLC PDU corresponding to the PDCP control PDU does not include a sequence number SN
  • the RLC entity of the data receiving end uses the RLC
  • the sequence number SN included in the PDU is subjected to repeated packet detection or packet ordering.
  • the RLC PDU does not include the sequence number SN allocated by the RLC entity, which can reduce the redundancy information of the RLC PDU during data transmission and improve the data transmission efficiency.
  • the PDCP data PDU and the PDCP control PDU do not include a sequence number SN, and the RLC PDU corresponding to the PDCP data PDU includes a sequence number SN; The RLC PDU does not contain the sequence number SN.
  • the PDCP PDU does not include the serial number SN, and the RLC PDU includes the serial number SN allocated by the PDCP entity, which can reduce the redundancy information of the PDCP PDU data packet during data transmission and improve the data transmission efficiency.
  • the RLC PDU includes a bit for indicating that the PDCP PDU is a PDCP Control PDU or a PDCP Data PDU, and the RLC entity of the data receiving end sends first indication information to the PDCP entity of the data receiving end, where the first indication information And configured to indicate that the PDCP PDU is a PDCP Control PDU or a PDCP Data PDU, so that the RLC entity of the data receiving end determines whether the PDCP sequence number needs to be parsed, and if it is determined that the PDCP PDU is a PDCP Data PDU, parsing the Read PDCP Data PDU includes The PDCP sequence number, in the case where it is determined that the PDCP PDU is a PDCP Control P
  • the RLC entity includes a first RLC entity and a second RLC entity, where the first RLC entity and the second RLC entity belong to the same or different data senders. And if the PDCP entity of the data sending end sends a PDCP PDU to the first RLC entity and the second RLC entity, the RLC PDU further includes indication information, where the indication information is a bit used to indicate whether there is a gap GAP. a PDCP PDU that is received by the first RLC entity and the second RLC entity is non-contiguous, and there is no GAP to characterize the PDCP received by the first RLC entity and the second RLC entity.
  • the PDU is contiguous; if the indication information indicates that there is a GAP bit, the RLC PDU further includes a GAP value, where the GAP value is used to indicate a GAP value between two adjacent PDCP PDUs received by the same RLC entity. To avoid double-link situations, the RLC entity at the data receiving end does not need feedback for feedback.
  • the RLC PDU further includes an interval GAP value, where the GAP value is used to indicate a GAP value between two adjacent PDCP PDUs received by the RLC entity, to avoid a dual link situation.
  • the RLC entity at the data receiving end feeds back without feedback.
  • the RLC entity of the data sending end receives the PDCP PDU sent by the PDCP entity of the data sending end
  • the RLC entity of the data receiving end sends the sequence number SN corresponding to the PDCP data PDU to the PDCP entity of the data receiving end, so that the RLC entity of the data sending end can accurately determine the PDCP sequence number included in the segment RLC PDU. Value.
  • the RLC entity of the data sending end before the RLC entity of the data sending end generates the corresponding RLC PDU according to the PDCP PDU data, the RLC entity of the data sending end receives the first indication information sent by the PDCP entity of the data sending end,
  • the first indication information is used to indicate that the PDCP PDU is indication information of a PDCP Control PDU or a PDCP Data PDU, so that the RLC entity of the data sending end can accurately identify whether the PDCP PDU included in the RLC PDU is a PDCP Control PDU or a PDCP Data PDU.
  • the second aspect provides a data sending device, where the data sending device is configured to implement the function of the RLC entity in the data sending end in the foregoing method design, and the function may be implemented by using hardware or by executing corresponding software through hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the modules can be software and/or hardware.
  • the data transmitting device includes a receiving unit, a processing unit, and a sending unit, and the functions of the receiving unit, the processing unit, and the sending unit may correspond to each method step, the data format of the RLC PDU and the data of the PDCP PDU.
  • the format is also the same as the format involved in the above method, and will not be described here.
  • the data transmitting device comprises a processor, a memory, a receiver and a transmitter, wherein the processor, the memory, the receiver and the transmitter can be connected by a bus system.
  • the memory is for storing a program for executing a program in the memory to perform a method performed by an RLC entity of a data transmitting end in the first aspect or any possible design of the first aspect.
  • a data receiving device is provided, and the data receiving device is provided with a function of implementing an RLC entity in a data receiving end in the above method design, and the function may be implemented by using hardware or by executing corresponding software by hardware.
  • the hardware or software includes one or more modules corresponding to the functions described above.
  • the modules can be software and/or hardware.
  • the data receiving device includes a receiving unit and a processing unit, and may also include a sending unit, and the functions of the receiving unit, the processing unit, and the sending unit may correspond to each method step, and the data format of the RLC PDU and the PDCP
  • the data format of the PDU is also the same as the format involved in the foregoing method, and details are not described herein.
  • the data receiving device comprises a processor, a memory, a receiver and a transmitter, wherein the processor, the memory, the receiver and the transmitter can be connected by a bus system.
  • the memory is for storing a program for executing a program in the memory to perform a method performed by an RLC entity of a data receiving end in the first aspect or any possible design of the first aspect.
  • a data transmitting device comprising a processor and a memory, wherein the memory is used to store a program, and the processor calls a program stored in the memory to perform any of the first aspect or the first aspect of the present application.
  • the data transmitting device may be a data transmitting end or a chip on the data transmitting end, wherein the data sending end may be a terminal or a network device.
  • a data receiving device comprising a processor and a memory, wherein the memory is used to store a program, and the processor calls a program stored in the memory to perform any of the first aspect or the first aspect of the present application.
  • the data receiving device may be a data receiving end, or may be a chip on the data receiving end, wherein the data receiving end may be a terminal or a network device.
  • a data transmitting device comprising a processor, and an interface.
  • the processor performs the functions of the processing unit in the second aspect.
  • the interface performs the functions of the receiving unit/transmitting unit in the second aspect.
  • an embodiment of the present application provides a data receiving device, where the data receiving device includes a processor and an interface.
  • the processor performs the functions of the processing unit in the third aspect.
  • the interface performs the functions of the receiving unit/transmitting unit in the third aspect.
  • the embodiment of the present application provides a communication system, where the communication system includes the data transmitting device of the sixth aspect and the data receiving device of the seventh aspect.
  • the embodiment of the present application provides a computer readable storage medium or computer program product for storing a computer program for performing the first aspect or the A method performed by a data transmitting end or a data receiving end in any possible design on the one hand.
  • the data transmission method provided by the present application the data receiving device and the data transmitting device perform data transmission, and the PDCP PDU and the RLC entity generated by the PDCP entity use the serial number assigned by the PDCP entity according to the RLC PDU generated by the PDCP PDU, which can reduce the data transmission process. Redundant information in the data to improve data transmission efficiency.
  • FIG. 1 is a structural diagram of a wireless communication system to which a data transmission method according to an embodiment of the present application is applied;
  • FIG. 2 is a schematic diagram of a transmission process of data transmission between a data transmitting end and a data receiving end in a wireless communication system
  • FIG. 3 is a schematic flowchart of a data transmission method according to an embodiment of the present disclosure
  • FIG. 4 is a schematic diagram 1 of a format of a PDCP control PDU packet including a sequence number according to an embodiment of the present application;
  • FIG. 5 is a second schematic diagram of a format of a PDCP control PDU packet including a sequence number according to an embodiment of the present disclosure
  • FIG. 6 is a third schematic diagram of a format of a PDCP control PDU packet including a sequence number according to an embodiment of the present disclosure
  • FIG. 7 is a schematic diagram 4 of a format of a PDCP control PDU packet including a sequence number according to an embodiment of the present disclosure
  • FIG. 8 is a schematic diagram 5 of a format of a PDCP control PDU packet including a sequence number according to an embodiment of the present disclosure
  • FIG. 9 is a schematic diagram 6 of a format of a PDCP control PDU packet including a sequence number according to an embodiment of the present disclosure
  • FIG. 10 is a schematic diagram 7 of a format of a PDCP control PDU packet including a sequence number according to an embodiment of the present disclosure
  • FIG. 11 is a schematic diagram 8 of a format of a PDCP control PDU packet including a sequence number according to an embodiment of the present disclosure
  • FIG. 12 is a schematic diagram 1 of a format of an RLC PDU packet that does not include an RLC sequence number according to an embodiment of the present disclosure
  • FIG. 13 is a second schematic diagram of a format of an RLC PDU packet that does not include an RLC sequence number according to an embodiment of the present disclosure
  • FIG. 14 is a third schematic diagram of a format of an RLC PDU packet not including an RLC sequence number according to an embodiment of the present disclosure
  • FIG. 15 is a schematic diagram 4 of a format of an RLC PDU packet that does not include an RLC sequence number according to an embodiment of the present disclosure
  • FIG. 16 is a schematic diagram 5 of a format of an RLC PDU packet that does not include an RLC sequence number according to an embodiment of the present disclosure
  • FIG. 17 is another schematic flowchart of a data transmission method according to an embodiment of the present application.
  • FIG. 18 is still another schematic flowchart of a data transmission method according to an embodiment of the present application.
  • FIG. 19 is a schematic diagram of a PDCP entity sending a PDCP PDU through a dual link according to an embodiment of the present disclosure
  • 20 is a schematic diagram 6 of a format of an RLC PDU packet that does not include an RLC sequence number according to an embodiment of the present disclosure
  • FIG. 21 is a schematic diagram 7 of a format of an RLC PDU packet not including an RLC sequence number according to an embodiment of the present disclosure
  • FIG. 22 is a schematic diagram 8 of a format of an RLC PDU packet not including an RLC sequence number according to an embodiment of the present disclosure
  • FIG. 23 is a schematic diagram 9 of a format of an RLC PDU packet not including an RLC sequence number according to an embodiment of the present disclosure
  • FIG. 24 is a schematic diagram 1 of a format of a PDCP data PDU packet that does not include a PDCP sequence number according to an embodiment of the present disclosure
  • 25 is a second schematic diagram of a format of a PDCP data PDU packet that does not include a PDCP sequence number according to an embodiment of the present disclosure
  • FIG. 26 is a schematic diagram 1 of a format of a PDCP control PDU packet without a sequence number according to an embodiment of the present disclosure
  • FIG. 27 is a second schematic diagram of a format of a PDCP control PDU packet without a sequence number according to an embodiment of the present disclosure
  • FIG. 28 is a schematic diagram 1 of a format of an RLC PDU packet including a PDCP sequence number according to an embodiment of the present disclosure
  • FIG. 29 is a second schematic diagram of a format of an RLC PDU packet including a PDCP sequence number according to an embodiment of the present disclosure
  • FIG. 30 is a schematic structural diagram of a data sending device according to an embodiment of the present disclosure.
  • FIG. 31 is a schematic structural diagram of another data sending device according to an embodiment of the present disclosure.
  • FIG. 32 is a schematic structural diagram of a data receiving device according to an embodiment of the present disclosure.
  • FIG. 33 is a schematic structural diagram of another data receiving device according to an embodiment of the present disclosure.
  • the data transmission method provided by the embodiment of the present application can be applied to data transmission in a wireless communication system, where the data receiving end and the data transmitting end perform data interaction through a radio access network (RAN) and a core network.
  • RAN radio access network
  • FIG. 1 in a wireless communication system, a data exchange is performed between a terminal and a network device, and the terminal accesses the RAN through an air interface and is connected to the network device via a core network, where the network between the terminal and the RAN may be referred to as wireless.
  • the network, the network between the RAN and the network device may be referred to as a wired network.
  • a TCP connection is established between the network device and the terminal for data transmission.
  • the wireless communication system is a network that provides wireless communication functions.
  • the wireless communication system can employ different communication technologies, such as code division multiple access (CDMA), wideband code division multiple access (WCDMA), and time division multiple access (TDMA).
  • Code division multiple access CDMA
  • WCDMA wideband code division multiple access
  • TDMA time division multiple access
  • Frequency division multiple access (FDMA) orthogonal frequency-division multiple access
  • OFDMA orthogonal frequency-division multiple access
  • SC-FDMA single carrier frequency division multiple access
  • the network can be divided into 2G (English: generation) network, 3G network, 4G network or future evolution network, such as 5G network.
  • a typical 2G network includes a global system for mobile communications/general packet radio service (GSM) network or a general packet radio service (GPRS) network.
  • GSM global system for mobile communications/general packet radio service
  • GPRS general packet radio service
  • a typical 3G network includes a universal mobile communication system (universal mobile communication system).
  • a typical 4G network includes a long term evolution (LTE) network.
  • the UMTS network may also be referred to as a universal terrestrial radio access network (UTRAN).
  • the LTE network may also be referred to as an evolved universal terrestrial radio access network (E-).
  • E- evolved universal terrestrial radio access network
  • UTRAN Universal Terrestriality
  • 2G, 3G and 4G networks are all cellular communication networks. It should be understood by those skilled in the art that as the technology advances, the technical solutions provided by the embodiments of the present invention are equally applicable to other wireless communication networks, such as 4.5G or 5G networks, or other non-cellular communication networks.
  • the network device involved in FIG. 1 may be referred to as a Radio Access Network (RAN) device, and is a device that accesses a terminal to a wireless network, including but not limited to: an evolved type.
  • Node B evolved Node B, eNB
  • Radio Network Controller RNC
  • Node B Node B, NB
  • Base Station Controller BSC
  • Base Transceiver Station Base Transceiver Station, BTS
  • home base station for example, Home evolved NodeB, or Home Node B, HNB
  • BBU BaseBand Unit
  • WIFI Wireless Fidelity
  • AP transmission point
  • transmission point transmission and receiver point
  • TRP Transmission and receiver point
  • TP transmission point
  • UE 1 is a device that provides voice and/or data connectivity to a user, and may include various handheld devices with wireless communication capabilities, in-vehicle devices, wearable devices, computing devices, or connected to a wireless modem.
  • FIG. 2 is a schematic diagram showing a transmission process of transmitting data between a data transmitting end and a data receiving end in a wireless communication system.
  • the data transmitting end sends data to the data receiving end in the wireless communication system
  • the data is started by the application layer of the data transmitting end, and after passing through the PDCP layer, the RLC layer, the MAC layer, and the PHY layer of the data transmitting end, the PHY is transmitted to the data receiving end via the transmission link.
  • the layer, through the MAC layer, the RLC layer, and the PDCP layer of the data receiving end finally reaches the application layer of the data receiving end.
  • the transmission process of the data receiving end transmitting data to the data transmitting end in the wireless communication system is opposite to the transmission process of the data transmitting end transmitting data to the data receiving end, and details are not described herein again.
  • the PDCP layer in FIG. 2 is only an illustrative description of the application layer, and is not limited thereto.
  • the PDCP layer may be a Radio Resource Control (RRC) signaling.
  • RRC Radio Resource Control
  • each layer of the protocol is performed by the entity of the corresponding layer.
  • the entity that implements the RLC layer protocol is referred to as an RLC entity in the following embodiments, and the RLC entity belongs to the RLC layer and corresponds to the RLC layer.
  • An entity that implements the PDCP layer protocol is called a PDCP entity, and a PDCP entity belongs to the PDCP layer and corresponds to the PDCP layer.
  • the description of the processing procedure of the protocol layer between the two protocol entity units may be omitted, for example, the RLC entity of the data sending end and the data receiving end
  • the description of the processing procedure of the MAC/PHY layer of the data receiving end and the data transmitting end is omitted.
  • FIG. 3 is a flowchart of a data transmission method according to an embodiment of the present application. Referring to FIG. 3, the method includes:
  • the PDCP entity of the data sending end sends the PDCP PDU to the RLC entity of the data sending end.
  • the PDCP PDU includes a PDCP data PDU and a PDCP control PDU.
  • the RLC entity of the data sending end receives the PDCP PDU sent by the PDCP entity of the data sending end, and generates a corresponding RLC PDU according to the PDCP PDU.
  • the sequence numbers included in the PDCP PDU and the RLC PDU are allocated by the PDCP entity, and the data receiving end can use the sequence number to perform repeated packet detection or data packet ordering.
  • the RLC entity of the data sending end sends the RLC PDU to the RLC entity of the data receiving end.
  • the RLC entity at the data receiving end receives the RLC PDU sent by the RLC entity of the data sending end, and uses the sequence number to perform repeated packet detection or data packet ordering.
  • the RLC entity at the data receiving end sends an RLC Service Data Unit (SDU) to the PDCP entity at the data receiving end.
  • SDU RLC Service Data Unit
  • the sequence numbers included in the PDCP PDU and the RLC PDU are allocated by the PDCP entity.
  • the PDCP PDU and the RLC PDU use the PDCP sequence number.
  • the case where the RLC PDU uses the PDCP sequence number can be understood as the RLC PDU. Contains the case of the RLC serial number.
  • sequence number assigned by the PDCP entity is referred to as a PDCP sequence number
  • sequence number assigned by the RLC entity is referred to as an RLC sequence number
  • the PDCP data PDU includes the PDCP sequence number allocated by the PDCP entity, and the PDCP control PDU may or may not include the PDCP sequence number.
  • the PDCP data PDU and the PDCP control PDU both contain the PDCP sequence number
  • the RLC PDU is a complete RLC PDU
  • the RLC PDU does not include the PDCP sequence number.
  • the RLC PDU is a segmented RLC PDU, the RLC PDU includes the PDCP sequence number.
  • the RLC PDU is a complete RLC PDU for the RLC PDU corresponding to the PDCP data PDU, the RLC PDU is not The sequence number SN is included. If the RLC PDU is a segment RLC PDU, the RLC PDU includes a sequence number SN; and the RLC PDU corresponding to the PDCP control PDU does not include a sequence number SN.
  • the PDCP data PDU and the PDCP control PDU both include a PDCP sequence number, and the data packet format of the PDCP data PDU can use the current existing PDCP PDU data packet format, and details are not described herein again.
  • the format of the RLC PDU is illustrated.
  • the PDCP Control PDU can use the packet format shown in FIG. 4.
  • the PDCP Control PDU includes the sequence number SN.
  • the Data/Control (D/C) field is used to indicate whether the PDCP PDU is a PDCP Data PDU or a PDCP Control PDU.
  • the PDCP PDU is indicated as a PDCP Control PDU.
  • the PDU Type field is used to indicate the type of the PDCP control PDU.
  • the data of the Data field corresponding to different PDU types is different.
  • the reserved bit (R) indicates that the bit is a vacant bit and is reserved for future use.
  • SN is the serial number. Data is data.
  • the PDU Type, the reserved bit, the length of the SN, the Data, and the order of the different domains are not limited, and FIG. 4 is only an exemplary description.
  • the PDCP control PDU may be a Robust Header Compression (ROHC) feedback data packet PDCP control PDU, or may be a status report PDCP control PDU.
  • ROHC Robust Header Compression
  • the possible packet format of the ROHC feedback packet PDCP control PDU including the PDCP sequence number is as shown in FIG. 5, FIG. 6, FIG. 7, and FIG. Show.
  • the ROHC feedback packet is ROHC feedback information.
  • the possible data packet format of the status report PDCP control PDU is as shown in FIG. 9, FIG. 10 and FIG.
  • the first Missing SN indicates the serial number with the smallest serial number in the data packet currently lost at the data receiving end.
  • the bitmap indicates which packets are successfully received from the next serial number of the FMS. The packet was not received successfully.
  • the length of the field in the data packet format and the order of the different domains in the data packet format are not limited in all embodiments of the present application.
  • the data packet format involved in all the embodiments of the present application may include a domain for other functions in addition to the domain given in the present application, which is not limited herein.
  • the possible structure of the RLC PDU is as follows:
  • FIG. 12 is a schematic diagram of a format of a complete RLC PDU according to an embodiment of the present application.
  • a Data/Control (D/C) field is used to indicate whether the RLC PDU is an RLC data PDU or an RLC control PDU.
  • the Segmentation Flag (SF) field is used to indicate whether the RLC PDU contains a complete PDCP PDU or a fragmented PDCP PDU. If the complete PDCP PDU is included, the RLC PDU is called a complete RLC PDU.
  • the RLC PDU is called a complete RLC PDU.
  • Polling bit (P) is used to indicate whether the peer feedback status report is required.
  • a reserved bit (R) indicating that the bit is a vacant bit.
  • the Data Field Length (Length, L) field is used to indicate the length of the Data Field (Data). In addition, the L domain is optional.
  • the Data field is part of the RLC SDU or RLC SDU.
  • the RLC entity of the data transmitting end sends the complete RLC PDU by using the data packet format shown in FIG.
  • Performing repeated packet detection or packet sequencing by using the PDCP sequence number included in the PDCP data PDU and the PDCP control PDU, and using the read PDCP data PDU and the PDCP sequence number included in the PDCP control PDU. Or feedback.
  • the PDCP data PDU and the PDCP control PDU both include a PDCP sequence number. If the RLC entity of the data transmitting end needs to segment the RLC SDU, the RLC PDU is a segment RLC PDU, and the segment RLC PDU includes a PDCP sequence number, and A segment offset (SO) is included, and the SO is used to indicate the location of the data portion of the first byte of the segment RLC PDU data portion in the RLC SDU before the segmentation, as shown in FIG.
  • FIG. 13 is a schematic diagram of a format of a segmented RLC PDU according to an embodiment of the present disclosure.
  • the length of the SN and the length of the SO are not limited, and the L domain is optional, and the domains may have different orders.
  • the SF value is 1 to indicate that the RLC PDU is a segmented RLC PDU.
  • a last segment flag (LSF) is used to indicate whether the last byte of the data portion of the segment RLC PDU is the last byte of data in the RLC PDU before the segmentation.
  • the value of the SN is the value of the PDCP sequence number allocated by the PDCP entity, and SO is the location of the data part of the first byte of the segment RLC PDU data part before the unsegmented RLC PDU.
  • the PDCP data PDU contains the PDCP sequence number and the PDCP control PDU does not contain the PDCP sequence number
  • the PDCP data PDU and the PDCP Control PDU may follow the corresponding packet structure in the prior art.
  • the packet structure of the RLC PDU is as follows:
  • the RLC PDU generated by the RLC entity of the data transmitting end corresponds to the PDCP data PDU and is a complete RLC PDU, the RLC PDU does not include the PDCP sequence number. If the RLC PDU generated by the RLC entity of the data transmitting end corresponds to the PDCP data PDU and is a segment RLC PDU, the RLC PDU includes a PDCP sequence number. If the RLC PDU generated by the RLC entity of the data transmitting end corresponds to the PDCP Control PDU, since the PDCP Control PDU does not include the sequence number SN, the RLC PDU does not include the sequence number SN.
  • the RLC entity of the receiving end needs to parse the complete RLC PDU corresponding to the PDCP data PDU.
  • the PDCP sequence number included in the PDCP data PDU is read, and when the RLC PDU corresponding to the PDCP control PDU is parsed, the PDCP sequence number of the PDCP control PDU is not required to be read because the PDCP control PDU does not include the PDCP sequence number.
  • the RLC entity at the transmitting end needs to mark whether the two RLC PDUs are corresponding to the PDCP data PDU or the PDCP control PDU.
  • the PDCP control PDU only needs to include the SO domain when performing segmentation, and does not need to include the SN. Because the PDCP control PDU does not include the SN, the RLC entity cannot reuse the SN of the PDCP control PDU. Therefore, the RLC of the transmitting end is required.
  • the entity marks whether the foregoing RLC PDU is corresponding to the PDCP data PDU or the PDCP control PDU.
  • the RLC PDU may include the PDCP PDU corresponding to the RLC PDU as the PDCP control.
  • the bit of the PDU or the PDCP data PDU so that the RLC entity of the data receiving end determines whether the PDCP sequence number needs to be parsed, and if it is determined that the PDCP PDU is a PDCP data PDU, parsing the PDCP sequence number included in the read PDCP data PDU, determining In the case where the PDCP PDU is a PDCP Control PDU, there is no need to parse and read the PDCP sequence number.
  • a data packet format including an RLC PDU indicating that the PDCP PDU corresponding to the RLC PDU is a PDCP Control PDU or a PDCP Data PDU bit may be in the structural diagram shown in FIG. 12 or FIG.
  • a reserved bit is used as a bit for indicating that the PDCP PDU corresponding to the RLC PDU is a PDCP Control PDU or a PDCP Data PDU.
  • the second reserved bit is selected in the structural diagram shown in FIG. As a bit for indicating that the PDCP PDU corresponding to the RLC PDU is a PDCP Control PDU or a PDCP Data PDU.
  • the segmented RLC PDU corresponding to the PDCP data PDU is as shown in FIG. 15, and the segment RLC PDU corresponding to the PDCP control PDU is as shown in FIG. 16.
  • the PDCP entity of the data sending end in the embodiment of the present application may send, to the RLC entity of the data sending end, indication information indicating that the PDCP PDU is a PDCP Control PDU or a PDCP Data PDU, so that the RLC entity of the data sending end is used.
  • the PDCP PDU included in the RLC PDU can be accurately identified as a PDCP control PDU or a PDCP data PDU.
  • S201, S203, S204, S205, and S206 are the same as S101, S102, S103, S104, and S105 in FIG. 3, and are not described here again, except that:
  • the PDCP entity of the data sending end sends the first indication information to the RLC entity of the data sending end, and the RLC entity of the data sending end receives the first indication information sent by the PDCP entity of the data sending end, where the first indication information is used to indicate the
  • the PDCP PDU is a PDCP Control PDU or a PDCP Data PDU.
  • the RLC entity of the data receiving end sends the first indication information to the PDCP entity of the data receiving end, where the first indication information is used to indicate that the PDCP PDU is a PDCP Control PDU or a PDCP Data PDU.
  • the PDCP entity of the data sending end may further send the PDCP sequence number associated with the PDCP PDU to the RLC entity of the data sending end, so that the RLC entity of the data sending end can accurately determine the included in the segment RLC PDU.
  • the value of the PDCP serial number may be implemented on the basis of the method shown in FIG. 3 or may be implemented on the basis of the method shown in FIG. The embodiment of the present application is described by taking the method shown in FIG. 17 as an example, and is shown in FIG. 18. In the data transmission method shown in FIG.
  • S301, S303, S304, S305, S306, S307, and S308 are the same as S201, S202, S203, S204, S205, S206, and S207 in FIG. 2, and details are not described herein again. the difference lies in:
  • the PDCP entity of the data sending end may send the PDCP sequence number associated with the PDCP PDU to the RLC entity of the data sending end, and the RLC entity of the data sending end receives the PDCP sequence number associated with the PDCP PDU sent by the PDCP entity of the data sending end.
  • the RLC entity of the data receiving end sends the PDCP sequence number associated with the PDCP PDU to the PDCP entity of the data receiving end.
  • S309 is an optional step. For example, if the PDCP PDU includes a sequence number, the PDCP entity can directly read the sequence number of the PDCP PDU without sending the RLC entity to the PDCP entity.
  • the RLC PDU format provided by the foregoing embodiment of the present application can be applied to the case of a single link, that is, the PDCP entity applicable to one logical channel of the data transmitting end sends the generated PDCP PDU to one RLC entity.
  • the PDCP entity of one logical channel of the data transmitting end sends the generated PDCP PDU to the two RLC entities, and the two RLC entities are respectively referred to as the first RLC entity and the second RLC entity for convenience of description.
  • 19 is a schematic diagram of a PDCP PDU sent by a PDCP entity through a dual link, where a PDCP entity of a data transmitting end has five PDCP PDUs transmitted through two links to a first RLC entity and a second RLC of the data transmitting end respectively.
  • the first RLC entity and the second RLC entity of the data receiving end need to feed back the situation that the RLC PDU is received on the respective link, but if the first RLC entity and the second RLC entity of the data sending end do not allocate the sequence to the RLC PDU.
  • the sequence number included in the RLC PDU is a PDCP sequence number, so that the sequence numbers of the RLC PDUs received by the first RLC entity and the second RLC entity of the data receiving end are discontinuous, for example, the first end of the data receiving end.
  • the RLC entity receives the PDCP PDU1 and the PDCP PDU 3 in sequence, and does not receive the PDCP PDU2.
  • the first RLC entity of the data receiving end needs to provide feedback.
  • the PDCP PDU2 is received by the second RLC entity of the data receiving end.
  • the first RLC entity at the data receiving end does not actually need to provide feedback.
  • the RLC entity of the data receiving end does not need to perform feedback.
  • the RLC PDU may be set to indicate whether there is an interval (GAP).
  • GAP interval
  • the indication information wherein the presence of the GAP characterization that the first RLC entity and the second RLC entity receive the PDCP PDU is non-contiguous, and the absence of the GAP characterization of the first RLC entity and the second RLC entity receiving The PDCP PDUs arrived are contiguous.
  • the indication information indicating whether the GAP is present may be implemented by setting a bit in the RLC PDU packet format, for example, setting one bit as the indication information indicating whether the GAP exists, and indicating whether the GAP exists by using different values of the bit. .
  • the RLC PDU further includes a GAP value, where the GAP value is used to indicate a GAP value between two adjacent PDCP PDUs received by the same RLC entity. If the indication information indicates that there is no GAP bit, there is no need to set a GAP value or set a GAP value of 0 or 1.
  • the RLC PDU is a complete RLC PDU, and the data packet format diagram of the RLC PDU can be as shown in the figure. 20 is shown.
  • the RLC PDU is a segmented RLC PDU
  • the data packet format diagram of the RLC PDU can be as follows.
  • Figure 21 shows.
  • the RLC PDU is a complete RLC PDU, and the data packet format diagram of the RLC PDU may be as follows.
  • Figure 22 shows.
  • the RLC PDU further includes a GAP value, which is represented by Gap in FIG.
  • the Gap value is 1.
  • the first RLC entity of the data transmitting end uses the data packet format shown in FIG. 22, and after transmitting the RLC PDU3 to the first RLC entity of the data receiving end, the first RLC entity of the data receiving end can determine the PDCP when receiving the PDCP PDU3. There is a PDCP PDU between the PDU3 and the PDCP PDU1 that is not sent by the first RLC entity of the data transmitting end, and thus no feedback is needed.
  • the RLC PDU is a segmented RLC PDU, and the data packet format diagram of the RLC PDU may be As shown in Figure 23.
  • the RLC entity of the data receiving end does not need to perform feedback when the dual link is avoided.
  • the GLC may not be set in the RLC PDU. Instructing the information, but setting the GAP value directly in the RLC PDU, the GAP value is used to indicate the GAP value between the two adjacent PDCP PDUs received by the RLC entity, and the GAP value is used to determine whether the GAP exists. If the GAP value is 0, there is no GAP. If the GAP value is non-zero, there is a GAP, and the size of the existing GAP is the GAP value.
  • the data packet format including the GAP value or the GAP indication information in the embodiment of the present application may also include a bit for indicating that the PDCP PDU is a PDCP Control PDU or a PDCP Data PDU, and the specific structure may be the structure shown in FIG. 20 to FIG. Selecting one reserved bit as a bit for indicating that the PDCP PDU is a PDCP Control PDU or a PDCP Data PDU, and setting a process for indicating that the PDCP PDU is a PDCP Control PDU or a PDCP Data PDU bit, refer to FIG. 14
  • the embodiment of setting the PD/C bit is shown in FIG. 16, and details are not described herein again.
  • the PDCP PDU does not include the PDCP sequence number and the RLC PDU contains the PDCP sequence number.
  • the PDCP PDU does not include the PDCP sequence number.
  • the PDCP entity allocates a PDCP sequence number to the PDCP data PDU, and does not allocate a PDCP sequence number for the PDCP control PDU.
  • the PDCP data PDU and the PDCP control PDU do not include the PDCP.
  • the serial number, the PDCP entity indicates the PDCP sequence number corresponding to the PDCP data PDU to the RLC entity, such that the RLC PDU corresponding to the PDCP data PDU includes a PDCP sequence number; the RLC PDU corresponding to the PDCP control PDU does not include the PDCP sequence No. This reduces the packet header overhead of the PDCP PDU.
  • the PDCP PDU does not include the PDCP sequence number.
  • the PDCP entity allocates the PDCP sequence number to both the PDCP data PDU and the PDCP control PDU.
  • the PDCP data PDU and the PDCP control PDU do not contain the PDCP sequence number.
  • the entity indicates the PDCP sequence number corresponding to the PDCP data PDU and the PDCP sequence number corresponding to the PDCP control PDU to the RLC entity, such that the RLC PDU corresponding to the PDCP data PDU includes a PDCP sequence number; and the RLC corresponding to the PDCP control PDU
  • the PDU also contains the PDCP sequence number.
  • the PDCP PDU includes a PDCP data PDU and a PDCP control PDU
  • the PDCP data PDU may be used to encapsulate data of the user plane, and may also be used to encapsulate data of the signaling plane.
  • a PDCP data PDU for encapsulating user plane data is referred to as a user plane PDCP data PDU
  • a PDCP data PDU for encapsulating signaling plane data is referred to as a signaling plane PDCP data PDU.
  • the user plane PDCP data PDU and/or the signaling plane PDCP data PDU sent by the PDCP entity of the data sending end to the RLC entity of the data sending end in the embodiment of the present application does not include the PDCP sequence number, and the signaling plane PDCP data PDU that does not include the PDCP sequence number.
  • the packet format is shown in Figure 24.
  • the signaling plane PDCP data PDU shown in Figure 24 contains only the data field (Data) and the message authentication code for Integrity (MAC-I). ).
  • the packet format of the user plane PDCP data PDU not including the PDCP sequence number is as shown in FIG. 25, and the user plane PDCP data PDU shown in FIG. 25 contains only the data field (Data).
  • the PDCP data PDU sent by the PDCP entity of the data sending end to the RLC entity of the data sending end does not include the PDCP sequence number, so the PDCP entity of the data sending end may send the PDCP sequence associated with the PDCP data PDU to the RLC entity of the data sending end.
  • the RLC entity of the data sending end receives the PDCP sequence number associated with the PDCP data PDU sent by the PDCP entity of the data sending end.
  • the RLC entity of the data receiving end After receiving the RLC PDU sent by the RLC entity of the data sending end, the RLC entity of the data receiving end parses the PDCP sequence number associated with the PDCP data PDU, and sends the PDCP serial number associated with the PDCP data PDU to the PDCP entity of the data receiving end. Therefore, the RLC entity of the subsequent data receiving end can use the associated PDCP sequence number to perform repeated packet detection or data packet sorting, and the implementation process is as shown in FIG. 18.
  • the PDCP control PDU may be a ROHC feedback data packet PDCP control PDU, or may be a PDCP control PDU of a package status report.
  • the data packet format of the ROHC feedback data packet PDCP control PDU is shown in FIG. 26.
  • the PDCP control PDU of the ROHC feedback data packet only includes ROHC feedback information, PDU type, and M reserved bits (R), M. Greater than or equal to 0.
  • the data packet format of the PDCP control PDU of the status report is as shown in FIG. 27.
  • the status report PDCP control PDU includes only the PDU type, the SN of the first lost PDCP data PDU, and the N-bit bitmap, and N is greater than or equal to zero.
  • the PDCP entity of the data sending end may send the first indication information to the RLC entity of the data sending end, and the RLC entity of the data sending end receives the first indication information sent by the PDCP entity of the data sending end, where the first indication information is And indicating that the PDCP PDU is a PDCP control PDU or a PDCP data PDU, and the RLC entity of the data receiving end receives the RLC PDU sent by the RLC entity of the data sending end, and then obtains the first indication information, and the RLC entity of the data receiving end sends the PDCP to the data receiving end.
  • the entity sends the first indication information, where the first indication information is used to indicate that the PDCP PDU is a PDCP control PDU or a PDCP data PDU, and the RLC entity of the data sending end includes, in the generated RLC PDU, the indication that the PDCP PDU is a PDCP.
  • the PDCP entity of the data receiving end can determine whether the PDCP PDU is a PDCP Control PDU or a PDCP Data PDU.
  • the process can be seen in Figure 17.
  • the PD/C is used to indicate that the PDCP PDU is a PDCP Control PDU or a PDCP Data PDU, R is a reserved bit, and SN is a PDCP serial number.
  • . 29 is a schematic diagram of a data packet format of an RLC PDU generated by an RLC entity in a dual-link scenario.
  • the data packet format of the RLC PDU involved in the embodiment of the present application including the PDCP sequence number may use the current packet format of the RLC PDU or a format similar to the packet format of the RLC PDU including the PDCP sequence number involved in the foregoing embodiment. Therefore, the data packet format of the RLC PDU is not described here.
  • the method for transmitting redundant information in the process of reducing data transmission provided by the present application, the data receiving end and the data transmitting end performing data transmission, the PDCP PDU generated by the PDCP entity and the RLC entity generated by the RLC entity according to the PDCP PDU are allocated by using the PDCP entity
  • the serial number to reduce redundant information during data transmission and improve data transmission efficiency.
  • the solution provided by the embodiment of the present invention is mainly introduced from the perspective of interaction between the data receiving end and the data sending end. It can be understood that, in order to implement the above functions, the data receiving end and the data transmitting end include corresponding hardware structures and/or software modules for performing respective functions.
  • the embodiments of the present invention can be implemented in a combination of hardware or hardware and computer software in combination with the elements and algorithm steps of the various examples described in the embodiments disclosed herein. Whether a function is implemented in hardware or computer software to drive hardware depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the technical solutions of the embodiments of the present invention.
  • the embodiment of the present invention may perform functional unit division on the data receiving end and the data sending end according to the foregoing method example.
  • each functional unit may be divided according to each function, or two or more functions may be integrated into one processing unit. in.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present invention is schematic, and is only a logical function division, and the actual implementation may have another division manner.
  • the embodiment of the present application further provides an apparatus for implementing any of the above methods, for example, providing an apparatus including a unit for implementing each step performed by a data transmitting end in any of the above methods ( Or means).
  • an apparatus including means (or means) for implementing the various steps performed by the data receiving end of any of the above methods.
  • the embodiment of the present application provides a data sending device, which can be applied to a chip in a data sending end or a data sending end.
  • the data sending end can be a network device or a terminal.
  • FIG. 30 shows a schematic structural diagram of a possible data transmitting apparatus 100.
  • the data transmitting device 100 may include a receiving unit 101, a processing unit 102, and a sending unit 103, where the receiving unit 101 is configured to receive a PDCP protocol data unit PDU sent by a packet data convergence protocol PDCP entity of the data transmitting device.
  • the processing unit 102 is configured to generate a corresponding RLC PDU according to the PDCP PDU received by the receiving unit 101.
  • the sending unit 103 is configured to send, to the RLC entity of the data receiving device, the RLC PDU generated by the processing unit 102.
  • the PDCP PDU includes a PDCP data PDU and a PDCP control PDU.
  • the PDCP data PDU and the PDCP control PDU each include a sequence number SN. If the RLC PDU is a complete RLC PDU, the RLC PDU does not include a sequence number SN, and if the RLC PDU is a segment RLC PDU, Then, the RLC PDU includes a sequence number SN. Alternatively, the PDCP data PDU includes a sequence number SN, the PDCP control PDU does not include a sequence number SN, and the RLC PDU corresponding to the PDCP data PDU, if the RLC PDU is a complete RLC PDU, the RLC PDU The serial number SN is not included.
  • the RLC PDU is a segmented RLC PDU
  • the RLC PDU includes a sequence number SN
  • the RLC PDU corresponding to the PDCP control PDU does not include a sequence number SN.
  • the PDCP data PDU and the PDCP control PDU do not include a sequence number SN
  • the RLC PDU corresponding to the PDCP data PDU includes a sequence number SN
  • the RLC PDU corresponding to the PDCP control PDU does not include a sequence. No. SN.
  • the PDCP control PDU does not include a sequence number SN, or the PDCP data PDU and the PDCP control PDU do not include a sequence number SN,
  • the RLC PDU includes a bit for indicating that the PDCP PDU is a PDCP Control PDU or a PDCP Data PDU.
  • the RLC entity includes a first RLC entity and a second RLC entity, where the first RLC entity and the second RLC entity belong to the same or different data sending device. And if the PDCP entity of the data sending device sends a PDCP PDU to the first RLC entity and the second RLC entity, the RLC PDU further includes indication information, where the indication information is used to indicate whether there is a gap GAP. Bit. The presence of the GAP to indicate that the PDCP PDU received by the first RLC entity and the second RLC entity is non-contiguous, and the absence of the GAP to characterize the PDCP PDU received by the first RLC entity and the second RLC entity is continuously. If the indication information indicates that there is a GAP bit, the RLC PDU further includes a GAP value, where the GAP value is used to indicate a GAP value between two adjacent PDCP PDUs received by the same RLC entity.
  • the RLC PDU further includes an interval GAP value, where the GAP value is used to indicate a GAP value between two adjacent PDCP PDUs received by the RLC entity.
  • the receiving unit 101 is further configured to: after receiving the PDCP PDU sent by the PDCP entity of the data sending end, receive the SN associated with the PDCP PDU sent by the PDCP entity of the data sending end.
  • the receiving unit 101 is further configured to: before the processing unit 102 generates a corresponding RLC PDU according to the PDCP PDU data, receive the first sent by the PDCP entity of the data sending end. Instructing information, the first indication information is used to indicate that the PDCP PDU is indication information of a PDCP Control PDU or a PDCP Data PDU.
  • the receiving unit 101 may be a communication interface, a receiver, a transceiver circuit, etc.
  • the processing unit 102 may be a processor or a controller.
  • the sending unit 103 can be a communication interface, a transmitter, a transceiver circuit, etc., wherein the communication interface is a collective name and can include one or more interfaces.
  • the data transmitting device 100 When the receiving unit 101 is a receiver, the processing unit 102 is a processor, and the transmitting unit 103 is a transmitter, the data transmitting device 100 according to the embodiment of the present application may be the data transmitting device shown in FIG.
  • the data sending device shown in FIG. 31 may be a network device or a terminal.
  • FIG. 31 is a schematic diagram of a data sending device 1000 according to an embodiment of the present application.
  • the data transmitting device 1000 can be used to execute an execution method of an RLC entity of the data transmitting end involved in FIG. 3, FIG. 17, or FIG.
  • the data transmitting device 1000 includes a processor 1001, a memory 1002, a receiver 1003, and a transmitter 1004, wherein a processor 1001, a memory 1002, a receiver 1003, and a transmitter 1004 can pass between The bus system is connected.
  • the memory 1002 is configured to store programs, instructions, or code.
  • the processor 1001 is configured to execute a program in the memory 1002, generate a PDCP PDU and an RLC PDU having the data format involved in the foregoing embodiment, and control the receiver 1003 and the transmitter 1004 to perform PDCP PDU and RLC PDU.
  • the steps and functions performed by the RLC entity for receiving and transmitting, and implementing the data transmitting end in the foregoing embodiment are not described herein.
  • the specific implementations of the foregoing processor 1001, the receiver 1003, and the transmitter 1004 may be referred to the specific descriptions of the receiving unit 101, the processing unit 102, and the transmitting unit 103 in the foregoing embodiment of FIG. 30, and details are not described herein again.
  • the embodiment of the present application further provides a data receiving device, which can be applied to a chip in a data receiving end or a data receiving end.
  • the data receiving end can be a network device or a terminal.
  • FIG. 32 shows a schematic structural diagram of a possible data transmitting and receiving apparatus 200.
  • the data receiving device 200 may include a receiving unit 201 and a processing unit 202.
  • the receiving unit 201 is configured to receive an RLC protocol data unit PDU sent by a radio link control RLC entity of the data transmitting device.
  • the processing unit 202 is configured to perform repeated packet detection or data packet ordering using the sequence number SN received by the receiving unit 201.
  • the RLC PDU is generated by the RLC entity of the data sending device according to a PDCP PDU sent by a packet data convergence protocol PDCP entity of the data sending device, where the PDCP PDU includes a PDCP data PDU and a PDCP control PDU.
  • the PDCP data PDU and the PDCP control PDU each include a sequence number SN, and the RLC PDU is a complete RLC PDU, and the RLC entity of the data receiving device uses the PDCP data PDU and the PDCP control PDU to include
  • the sequence number SN is subjected to repeated packet detection or packet ordering.
  • the RLC entity of the data receiving device performs repeated packet detection or data using the sequence number SN included in the RLC PDU. Packet ordering; or, the PDCP data PDU includes a sequence number SN, and the PDCP control PDU does not include a sequence number SN.
  • the RLC entity of the data receiving device performs the repeated packet detection or the data packet sorting by using the sequence number SN included in the PDCP data PDU, if the RLC PDU corresponds to the PDCP data PDU, and the RLC PDU is Segmenting the RLC PDU, the RLC entity of the data receiving device performs repeated packet detection or data packet ordering using the sequence number SN included in the RLC PDU; or the PDCP data PDU and the PDCP control PDU do not include The sequence number SN, if the RLC PDU corresponds to the PDCP data PDU and includes the sequence number SN, the RLC entity of the data receiving device performs repeated packet detection or data packet ordering using the sequence number SN included in the RLC PDU.
  • the data receiving device further includes a sending unit 203, where the sending unit 203 is configured to: after the receiving unit 201 receives the RLC PDU sent by the RLC entity of the data sending device, if the PDCP The data PDU includes a sequence number SN, the PDCP control PDU does not include the sequence number SN, or the PDCP data PDU and the PDCP control PDU do not include the sequence number SN, and the first indication information is sent to the PDCP entity of the data receiving device.
  • the first indication information is used to indicate that the PDCP PDU is a PDCP Control PDU or a PDCP Data PDU.
  • the data receiving device further includes a sending unit 203, where the sending unit 203 is configured to: after the receiving unit 201 receives the RLC PDU sent by the RLC entity of the data sending device, if the PDCP The data PDU and the PDCP control PDU do not include a sequence number SN, and the RLC PDU corresponds to the PDCP data PDU, and the RLC entity of the data receiving device sends the PDCP data PDU to the PDCP entity of the data receiving device. Corresponding serial number SN.
  • the receiving unit 201 may be a communication interface, a receiver, a transceiver circuit, etc.
  • the processing unit 202 may be a processor or a controller.
  • the sending unit 203 can be a communication interface, a transmitter, a transceiver circuit, etc., wherein the communication interface is a collective name and can include one or more interfaces.
  • the data receiving device 200 When the receiving unit 201 is a receiver, the processing unit 202 is a processor, and the sending unit 203 is a transmitter, the data receiving device 200 according to the embodiment of the present application may be the data receiving device shown in FIG.
  • the data receiving device shown in FIG. 31 may be a network device.
  • FIG. 33 is a schematic diagram of a data receiving device 2000 according to an embodiment of the present application.
  • the data receiving device 2000 can be used to perform an execution method of the RLC entity of the data receiving end involved in FIG. 3, FIG. 17, or FIG.
  • the data receiving device 2000 includes a processor 2001, a memory 2002, a receiver 2003, and a transmitter 2004, wherein the processor 2001, the memory 2002, the receiver 2003, and the transmitter 2004 can pass between The bus system is connected.
  • the memory 2002 is used to store programs, instructions or code.
  • the processor 2001 is configured to execute a program in the memory 2002, generate a PDCP PDU and an RLC PDU having the data format involved in the foregoing embodiment, and control the receiver 2003 and the transmitter 2004 to perform PDCP PDU and RLC PDU.
  • the steps and functions performed by the RLC entity for receiving and transmitting, and implementing the data receiving end in the foregoing embodiments are not described herein.
  • the embodiment of the present application only shows a simplified design of the data transmitting device and the data receiving device.
  • the data transmitting device and the data receiving device are not limited to the above-mentioned structure, and may include any number of receivers, transmitters, processors, memories, etc., respectively, in actual applications, and all terminals that can implement the embodiments of the present application All of them are within the protection scope of the embodiments of the present application.
  • the data transmitting device and the data receiving device may be used to implement the corresponding functions of the RLC entity of the data sending end and the RLC entity of the data receiving end in the foregoing method embodiment of the embodiment of the present invention.
  • the description of the embodiments of the present invention is not exhaustive, and the description of the related embodiments is omitted.
  • each unit in the device may all be implemented by software in the form of processing component calls; or may be implemented entirely in hardware; some units may be implemented in software in the form of processing component calls, and some units may be implemented in hardware.
  • each unit may be a separately set processing element, or may be integrated in one chip of the device, or may be stored in a memory in the form of a program, which is called by a processing element of the device and executes the unit.
  • all or part of these units can be integrated or implemented independently.
  • the processing elements described herein can in turn be a processor and can be an integrated circuit with signal processing capabilities.
  • each step of the above method or each of the above units may be implemented by an integrated logic circuit of hardware in the processor element or by software in the form of a processing component call.
  • the units in any of the above devices may be one or more integrated circuits configured to implement the above methods, such as: one or more application specific integrated circuits (ASICs), or one or A plurality of digital singnal processors (DSPs), or one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms.
  • ASICs application specific integrated circuits
  • DSPs digital singnal processors
  • FPGAs field programmable gate arrays
  • a unit in a device can be implemented in the form of a processing component scheduler
  • the processing element can be a general purpose processor, such as a central processing unit (CPU) or other processor that can invoke the program.
  • CPU central processing unit
  • these units can be integrated and implemented in the form of a system-on-a-chip (SOC).
  • SOC system-on-a-chip
  • the above receiving unit for receiving is an interface circuit of the device for receiving signals from other devices.
  • the receiving unit is an interface circuit that the chip uses to receive signals from other chips or devices.
  • the above transmitting unit for transmitting is an interface circuit of the device for transmitting signals to other devices.
  • the transmitting unit is an interface circuit that the chip uses to transmit signals to other chips or devices.
  • the program for performing the method performed by the data transmitting end or the data receiving end in the above method may be a storage element on a different chip than the processing element, ie, an off-chip storage element.
  • the processing component calls or loads the program from the off-chip storage component on the on-chip storage component to invoke and execute the method performed by the data transmitting end or the data receiving end in the above method embodiment.
  • the data transmitting end or the data receiving end implementing the steps in the above steps may be configured as one or more processing elements, where the processing elements may be integrated circuits, such as one or more ASICs. Or, one or more DSPs, or one or more FPGAs, or a combination of these types of integrated circuits. These integrated circuits can be integrated to form a chip.
  • the data transmitting end or the data receiving end can realize the unit of each step in the above method, and can be implemented in the form of a system-on-a-chip (SOC) for implementing the above method.
  • SOC system-on-a-chip
  • At least one processing element and a storage element may be integrated in the chip, and the method executed by the above terminal is implemented by the processing element calling the stored program of the storage element; or at least one integrated circuit may be integrated in the chip for implementing the above data transmission.
  • the method performed by the terminal or the data receiving end; or, in combination with the above implementation manner, the functions of the partial units are implemented by the processing component calling program, and the functions of the partial units are implemented by the form of an integrated circuit.
  • the above-mentioned device can include at least one processing element and interface circuit, wherein at least one processing element is used to perform the method performed by any of the data transmitting end or the data receiving end provided by the above method embodiment.
  • the processing element may perform some or all of the steps performed by the data transmitting end or the data receiving end in a manner of calling the program stored by the storage element; or in a second manner: by hardware in the processor element
  • the integrated logic circuit performs part or all of the steps performed by the data transmitting end or the data receiving end in combination with the instruction; of course, part or all of the steps performed by the data transmitting end or the data receiving end may be performed in combination with the first mode and the second mode. .
  • the processing elements herein, as described above, may be general purpose processors, such as a CPU, or may be one or more integrated circuits configured to implement the above methods, such as one or more ASICs, or one or more microprocessors.
  • processors involved in the embodiment of the present application may be a central processing unit (Central Processing Unit (CPU), or other general-purpose processor, digital signal processor (DSP), dedicated. Integrated circuit (ASIC), off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the storage element can be a memory or a collective name for a plurality of storage elements.
  • the memory 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. For example, the memory can also store information of the device type.
  • the bus system may also include a power bus, a control bus, and a status signal bus.
  • the various buses are labeled as bus systems in the figure.
  • the steps involved in the foregoing method embodiments may be completed by using an integrated logic circuit of hardware in the processor or an instruction in a form of software.
  • the steps of the message processing method disclosed in the embodiment of the present application may be directly implemented by the hardware processor, or may be performed by using a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory, and the processor reads the information in the memory and combines the hardware to complete the steps involved in the foregoing method embodiments. To avoid repetition, it will not be described in detail here.
  • the embodiment of the present application provides a communication system including the data transmitting device and the data receiving device involved above.
  • the embodiment of the present application provides a computer readable storage medium or computer program product for storing a computer program for performing the data transmission method involved above.
  • the data transmission method provided by the present application the data receiving device and the data transmitting device perform data transmission, and the PDCP PDU and the RLC entity generated by the PDCP entity use the serial number assigned by the PDCP entity according to the RLC PDU generated by the PDCP PDU, which can reduce the data transmission process. Redundant information in the data to improve data transmission efficiency.
  • embodiments of the present application can be provided as a method, system, or computer program product. Therefore, the embodiments of the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Moreover, embodiments of the present application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present application. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG.
  • These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

L'invention concerne un procédé de transmission de données, un dispositif de transmission de données et un dispositif de réception de données permettant de réduire le surdébit d'en-tête de paquets de données et d'augmenter l'efficacité de transmission de données. Dans le procédé de transmission de données, une entité d'un dispositif de contrôle de liaison radioélectrique (RLC) d'une extrémité de transmission de données reçoit une unité de données de protocole (PDU) de protocole de convergence de données par paquets (PDCP) transmise par une entité PDCP de l'extrémité de transmission de données, et génère une PDU de RLC correspondante en fonction de la PDU de PDCP, la PDU de PDCP et la PDU de RLC comprenant des numéros de série attribués par l'entité PDCP ; l'entité RLC de l'extrémité de transmission de données transmet la PDU de RLC à une entité RLC d'une extrémité de réception de données ; l'entité RLC de l'extrémité de réception de données reçoit la PDU de RLC transmise par l'entité RLC de l'extrémité de transmission de données ; et l'entité RLC de l'extrémité de réception de données utilise des numéros de série pour la détection de paquets en double ou le tri de paquets de données.
PCT/CN2018/079251 2017-03-17 2018-03-16 Procédé de transmission de données, dispositif de transmission de données et dispositif de réception de données WO2018166517A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710161099.7 2017-03-17
CN201710161099.7A CN108632899B (zh) 2017-03-17 2017-03-17 一种数据传输方法、数据发送设备及数据接收设备

Publications (1)

Publication Number Publication Date
WO2018166517A1 true WO2018166517A1 (fr) 2018-09-20

Family

ID=63522823

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/079251 WO2018166517A1 (fr) 2017-03-17 2018-03-16 Procédé de transmission de données, dispositif de transmission de données et dispositif de réception de données

Country Status (2)

Country Link
CN (1) CN108632899B (fr)
WO (1) WO2018166517A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021230800A1 (fr) * 2020-05-13 2021-11-18 Telefonaktiebolaget Lm Ericsson (Publ) Support radio à surdébit réduit

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111435930B (zh) * 2019-01-11 2022-09-16 中国移动通信有限公司研究院 一种控制pdu发送方法、装置、电子设备及存储介质
CN110278058B (zh) * 2019-06-05 2020-11-03 华为技术有限公司 一种冗余信息反馈方法及通信装置
CN110995750B (zh) * 2019-12-18 2021-09-28 展讯通信（上海）有限公司 终端设备
CN113840281A (zh) * 2020-06-23 2021-12-24 展讯通信（上海）有限公司 数据传输方法、设备、装置及存储介质
CN114554544B (zh) * 2020-11-20 2023-08-15 中国移动通信有限公司研究院 一种传输方法、通知方法、传输单元和网络侧设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101330492A (zh) * 2007-06-19 2008-12-24 上海贝尔阿尔卡特股份有限公司 数据发送方法、数据接收方法和设备
CN101848489A (zh) * 2009-03-25 2010-09-29 中兴通讯股份有限公司 Pdu的发送/接收方法和装置
WO2010126068A1 (fr) * 2009-04-27 2010-11-04 日本電気株式会社 Dispositif de réception, procédé de réception et programme
CN102395156A (zh) * 2011-09-28 2012-03-28 电信科学技术研究院 应用于pdcp实体和rlc实体间的数据传输方法及装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101222484A (zh) * 2007-01-09 2008-07-16 中兴通讯股份有限公司 一种无线链路控制层协议数据单元的实现方法
CN101364990B (zh) * 2007-08-08 2012-06-27 华为技术有限公司 一种减少数据头开销的方法
JP6231837B2 (ja) * 2013-09-24 2017-11-15 株式会社Ｎｔｔドコモ 移動通信方法及び無線基地局
CN104798320B (zh) * 2013-11-11 2018-11-09 华为技术有限公司 数据传输方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101330492A (zh) * 2007-06-19 2008-12-24 上海贝尔阿尔卡特股份有限公司 数据发送方法、数据接收方法和设备
CN101848489A (zh) * 2009-03-25 2010-09-29 中兴通讯股份有限公司 Pdu的发送/接收方法和装置
WO2010126068A1 (fr) * 2009-04-27 2010-11-04 日本電気株式会社 Dispositif de réception, procédé de réception et programme
CN102395156A (zh) * 2011-09-28 2012-03-28 电信科学技术研究院 应用于pdcp实体和rlc实体间的数据传输方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "reusing PDCP SN in RLC UM", 3GPP TSG-RAN WG2 MEETING #59 R2-073168, 24 August 2007 (2007-08-24), XP050135892 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021230800A1 (fr) * 2020-05-13 2021-11-18 Telefonaktiebolaget Lm Ericsson (Publ) Support radio à surdébit réduit

Also Published As

Publication number Publication date
CN108632899A (zh) 2018-10-09
CN108632899B (zh) 2020-09-29

Similar Documents

Publication Publication Date Title
CN108809596B (zh) 一种基于反转服务流特性的通信方法及装置
WO2018166517A1 (fr) Procédé de transmission de données, dispositif de transmission de données et dispositif de réception de données
WO2018059590A1 (fr) Procédé, dispositif et système de traitement de données
ES2901374T3 (es) Procedimiento y aparato para realizar una función de capa 2 eficiente en un sistema de comunicación móvil
WO2018202037A1 (fr) Procédé de transmission de données, dispositif terminal et dispositif de réseau
US11647417B2 (en) Method, apparatus, computer program product and computer program
WO2020192783A1 (fr) Procédé, appareil et système de configuration de porteuse radio
WO2018059438A1 (fr) Procédé, dispositif et système de transmission de messages
WO2019149248A1 (fr) Procédé et dispositif de communication
US10841042B2 (en) Method and apparatus for providing hybrid automatic repeat request (HARQ) transmission, to meet transmissions requirements of different services
TWI670954B (zh) 處理承載型態改變的裝置
TWI706652B (zh) 處理用於資料複本的暫存器狀態回報的裝置及方法
WO2018227566A1 (fr) Procédé et dispositif de transmission d'informations
WO2018027674A1 (fr) Appareil, procédé et système de communication de rapport d'état de transmission
US20220377781A1 (en) Method, apparatus, computer program product and computer program
WO2018227567A1 (fr) Procédé de transmission de données, dispositif terminal et dispositif de réseau
JP2012533204A (ja) Ａｒｑフィードバック情報伝送及び受信方法
CN110178403B (zh) 用于5g nr通信系统中的非对称上行链路/下行链路协议栈和帧结构的方法和装置
EP3300424B1 (fr) Équipement d'utilisateur, station de base et procédé de communication
US8315192B2 (en) Method and system for configuring a media access control header to reduce a header overhead
WO2023030452A1 (fr) Procédé de transmission de données et dispositif associé
EP3282770A1 (fr) Procédé de transmission d'informations de découverte, dispositif et système de communication
JP2020519178A (ja) データが破損しているかどうかを判断するための方法および装置
WO2018126450A1 (fr) Procédé et dispositif de communication sans fil
WO2018202204A1 (fr) Procédé et dispositif de communication fondés sur des caractéristiques de flux de service réfléchissantes

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: 18767861

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: 18767861

Country of ref document: EP

Kind code of ref document: A1