WO2018126450A1 - 无线通信的方法和设备 - Google Patents

无线通信的方法和设备 Download PDF

Info

Publication number
WO2018126450A1
WO2018126450A1 PCT/CN2017/070472 CN2017070472W WO2018126450A1 WO 2018126450 A1 WO2018126450 A1 WO 2018126450A1 CN 2017070472 W CN2017070472 W CN 2017070472W WO 2018126450 A1 WO2018126450 A1 WO 2018126450A1
Authority
WO
WIPO (PCT)
Prior art keywords
data packet
sequence number
identifier
status report
status
Prior art date
Application number
PCT/CN2017/070472
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 华为技术有限公司
Priority to PCT/CN2017/070472 priority Critical patent/WO2018126450A1/zh
Publication of WO2018126450A1 publication Critical patent/WO2018126450A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40Network security protocols

Definitions

  • the present application relates to the field of communications and, more particularly, to a method and apparatus for wireless communication.
  • the communication cell With the continuous use of high-frequency spectrum, the communication cell becomes smaller and smaller, and the appearance of hotspot cells further aggravates the frequency of communication cell handover. Then, before the user equipment (User Equipment, UE for short) is switched, the user equipment first receives a Packet Data Convergence Protocol Service Data Unit (PDCP SDU) from the source base station, and starts to target from the target after the handover.
  • PDCP SDU Packet Data Convergence Protocol Service Data Unit
  • the base station receives the PDCP SDU (some of which are forwarded by the source base station to the target base station, and some PDCP SDUs are sent by the source base station to the terminal but have not yet been acknowledged).
  • the handover occurs, the communication will be temporarily interrupted.
  • the PDCP layer of the packet data convergence protocol at the receiving end will accumulate some discontinuous data packets, and the PDCP layer at the transmitting end resumes communication. After the first time, it will be uncertain whether the receiving end will receive the data packet and resend the data packet. After the communication is restored, the receiving end constructs a PDCP status report in the PDCP layer according to the received data packet, and delivers the PDCP status report to the Radio Link Control (RLC), and the receiving end sends the packet in the RLC layer. To the sender, after receiving the PDCP status report, the sender cancels the transmission of the data packet that the receiver has received.
  • RLC Radio Link Control
  • the delay required for the transmitting end to collect a complete PDCP status report at the radio link control RLC layer may become larger. .
  • the embodiment of the invention provides a method and a device for wireless communication, which reduces retransmission of data packets, improves data transmission efficiency, and saves air interface bandwidth.
  • an embodiment of the present application provides a method for wireless communication, including: receiving end After the communication with the transmitting end changes from the interruption to the recovery, a plurality of radio link control RLC protocol data units are generated, each of the plurality of RLC protocol data units including a first status report, each of the RLCs
  • the first status report included in the protocol data unit is used to indicate status information of multiple consecutive data packets sent by the sending end, and a sequence number of a starting data packet in the multiple consecutive data packets, where the multiple The status information of the continuous data packet is used to indicate whether each of the plurality of consecutive data packets is received by the receiving end; the receiving end sends the multiple RLC protocol data units to the transmitting end.
  • each RLC protocol data unit in the plurality of RLC protocol data units that are sent by the receiving end after the communication is restored includes a first status report, where the first status report is used to indicate the sending end.
  • the serial number of the plurality of consecutive data packets determines whether the receiving end receives the data packet sent by the transmitting end during the communication interruption process, does not collect the complete status report, reduces the delay, cancels unnecessary data packet repeated transmission, and improves The data transmission rate saves air interface bandwidth.
  • each of the first status reports indicates a sequence number of the start data packet by using a first identifier and a second identifier, where the first identifier is Determining, by the sending end, a sequence number of the first received data packet or the first lost data packet in the data packet sent by the sending end, where the second identifier is the start in each of the first status reports The offset of the sequence number of the packet from the first identifier.
  • the first identifier is an FMS, where the FMS is a sequence number of a first received data packet at the receiving end or a serial number of the first lost data packet at the receiving end, optionally, the first The second identifier is a Segment Offset (SO).
  • FMS is a sequence number of a first received data packet at the receiving end or a serial number of the first lost data packet at the receiving end
  • SO Segment Offset
  • each of the first status reports indicates a sequence number of the start data packet by using a third identifier, where the third identifier is an FMS.
  • the first status report is generated by adding indication information indicating the sequence number of the start data packet in each sub-state report, so that the transmitting end receives the sequence number indicating the start data packet. Determining, according to the sequence number of the start data packet, a sequence number of other data packets in each RLC protocol data unit according to the sequence number of the start data packet, according to status information included in each RLC protocol data unit. And the sequence number of the plurality of consecutive data packets in each of the RLC protocol data units may directly process the first status report, without waiting to collect a complete second status report, reducing the time when the sub-state report is processed The delay reduces the retransmission of data packets, improves the efficiency of data transmission, and saves air interface bandwidth.
  • the indication information may be the first identifier and the second identifier, and the indication information may also be the third identifier.
  • the delay caused by the one-time transmission status report is avoided, the transmission efficiency is improved, the transmission delay is reduced, and the user experience is improved.
  • the first status report is prioritized when the RLC protocol data unit is constructed.
  • the each RLC protocol data unit only includes the first status report.
  • each of the plurality of the first status reports sets a fourth identifier, where the fourth identifier is used to indicate Whether each of the first status reports is the initial status report.
  • each RLC protocol data unit indicating whether each of the first status reports is the initial status report, so that the sending end can process the status report in an out-of-order manner, reducing the status. Reporting the stay at the sender increases the data transmission efficiency.
  • the embodiment of the present application provides a method for wireless communication, including: receiving, by a transmitting end, a plurality of radio link control RLC protocol data units that are sent by a receiving end after the communication with the sending end is changed from being interrupted to being restored.
  • Each of the plurality of RLC protocol data units includes a first status report, and the first status report included in each RLC protocol data unit is used to indicate multiple consecutive transmissions by the sending end.
  • State information of the data packet and a sequence number of the start data packet in the plurality of consecutive data packets the state information of the plurality of consecutive data packets being used to indicate whether each of the plurality of consecutive data packets is Receiving, by the receiving end, determining, according to each of the RLC protocol data units, status information of the plurality of consecutive data packets; stopping transmitting the plurality of consecutive data according to status information of the plurality of consecutive data packets The packet received by the receiving end in the packet.
  • the transmitting end determines, according to the received sequence number of the start data packet indicated in the first status report included in the multiple RLC protocol data units, other data packets in each RLC protocol data unit. a sequence number, according to the first status report included in each RLC protocol data unit, indicating status information of multiple consecutive data packets sent by the sending end, and the multiple consecutive data in each RLC protocol data unit. The sequence number of the packet determines the status information of the plurality of consecutive data packets, without waiting for a complete status report, reducing the stay of the status report at the transmitting end, and improving data transmission efficiency.
  • each of the first status reports indicates a sequence number of the start data packet by using a first identifier and a second identifier, where the first identifier is Place Determining, by the sending end, the first received data packet or the first lost data packet in the data packet sent by the receiving end, where the second identifier is an offset of the initial data packet from the first identifier Determining, according to the each RLC protocol data unit, the status information of the multiple consecutive data packets, including: determining, according to the first identifier and the second identifier, that each of the RLC protocol data units includes The sequence number of the start data packet and the sequence number of the other data packet in the first status report; determining the sequence information of the start data packet and the sequence information corresponding to the sequence number of the other data packet.
  • the first status report indicates a sequence number of the start data packet by using a third identifier included, and according to each of the RLC protocol data units, Determining the status information of the plurality of consecutive data packets, including: determining, according to the third identifier, a sequence of the start data packet and other data in the first status report included in each RLC protocol data unit a sequence number of the packet; determining status information corresponding to the sequence number of the start data packet and the sequence number of the other data packet.
  • the third identifier in the first status report included in the starting RLC protocol data unit of the multiple RLC protocol data units is the sending The sequence number of the first received data packet or the first lost data packet in the data packet sent by the terminal to the receiving end, and the first RLC protocol data unit after the initial RLC protocol data unit includes the first
  • the third identifier in the status report is the sequence number of the first received data packet or the first lost data packet after the last data packet in the first status report included in the previous RLC protocol data unit;
  • the transmitting end determines that the receiving end has received the sequence number is smaller than the start a data packet of the data packet, and stopping transmitting the data packet whose sequence number is smaller than the start data packet; or when the third identifier included in the initial status report is a serial number of the received data packet, Determining, by the sending end, that the receiving end loses a data packet whose sequence number is smaller than the starting data packet, and continues to send the data packet whose sequence number is smaller than the data packet of the initial data packet that is not repeatedly sent; Or determining, when the third identifier in each of the first status reports other than the initial status report is a sequence number of the received data packet, determining a start in the each of the other first status reports The packet between the packet and the last packet in the previous status report is the number of lost packets.
  • the third identifier in the first status report of the starting RLC protocol data unit of the multiple RLC protocol data units is the sending end a sequence number of a first received data packet or a first lost data packet in a data packet sent to the receiving end, and a first state included by the other RLC protocol data unit after the initial RLC protocol data unit
  • the third identifier in the report is the sequence number of the first received data packet or the first lost data packet after the last data packet indicated by the first status report in the previous RLC protocol data unit;
  • Each of the RLC protocol data units includes a fourth identifier, where the fourth identifier is used to indicate whether the first status report in each of the RLC protocol data units is a start status report;
  • the sending end determines that the receiving end has received the sequence The number is smaller than the data packet of the start data packet, and stops sending the data packet whose sequence number is smaller than the start data packet; or when the fourth identifier indicates that the first status report is a start status report, And the third identifier is a sequence number of the received data packet, the sending end determines that the receiving end loses a data packet whose sequence number is smaller than the start data packet, and continues to send the sequence number smaller than the A packet in a packet of a start packet that is not repeatedly transmitted.
  • the embodiment of the present application provides a receiving end device, which includes a processing module and a sending module, and can perform the method in any of the optional implementations of the first aspect or the first aspect.
  • the embodiment of the present application provides a sending end device, which includes a receiving module and a determining module, and can perform the method in any of the optional implementations of the second aspect or the second aspect.
  • a receiving end device comprising a memory, a transceiver, and a processor, the program storing code for indicating execution of the first or any optional implementation thereof, the transceiver for The specific signal transceiving is performed under the driving of the processor, and when the code is executed, the processor can implement the method in which the terminal device performs various operations.
  • a sixth aspect provides a transmitting device, including a memory, a transceiver, and a processor, Stored on the memory with program code that can be used to indicate execution of the second or any optional implementation thereof, the transceiver for performing specific signal transceiving under the drive of the processor, when the code is executed,
  • the processor can implement the method in which the terminal device performs various operations.
  • a computer storage medium is provided, the program storage code being stored in the computer storage medium, the program code being operative to indicate a method of performing the above first aspect or any optional implementation of the first aspect .
  • a computer storage medium stores program code, and the program code can be used to indicate a method in performing any of the foregoing second aspect or any optional implementation of the second aspect .
  • FIG. 1 is a schematic diagram of a communication system for wireless communication using an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a method for wireless communication according to an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of a method for wireless communication according to an embodiment of the present application.
  • FIG. 4 is a schematic flowchart of a method for wireless communication according to an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of a method for wireless communication according to an embodiment of the present application.
  • FIG. 6 is a schematic block diagram of a receiving device according to an embodiment of the present application.
  • FIG. 7 is a schematic block diagram of a transmitting device according to an embodiment of the present application.
  • FIG. 8 shows a schematic block diagram of a communication device of an embodiment of the present application.
  • the communication system 100 includes a network device 102, which may include multiple antennas, such as antennas 104, 106, 108, 110, 112, and 114. Additionally, network device 102 may additionally include a transmitter chain and a receiver chain, as will be understood by those of ordinary skill in the art, which may include multiple components related to signal transmission and reception (eg, processor, modulator, multiplexer) , demodulator, demultiplexer or antenna, etc.).
  • a network device 102 may include multiple antennas, such as antennas 104, 106, 108, 110, 112, and 114.
  • network device 102 may additionally include a transmitter chain and a receiver chain, as will be understood by those of ordinary skill in the art, which may include multiple components related to signal transmission and reception (eg, processor, modulator, multiplexer) , demodulator, demultiplexer or antenna, etc.).
  • Network device 102 can communicate with a plurality of terminal devices, such as terminal device 116 and terminal device 122. However, it will be appreciated that network device 102 can communicate with any number of target terminal devices similar to terminal device 116 or 122.
  • terminal device 116 is in communication with antennas 112 and 114, wherein antennas 112 and 114 transmit information to terminal device 116 over forward link 118 and receive information from terminal device 116 over reverse link 120.
  • terminal device 122 is in communication with antennas 104 and 106, wherein antennas 104 and 106 transmit information to terminal device 122 over forward link 124 and receive information from terminal device 122 over reverse link 126.
  • the forward link 118 can use a different frequency band than the reverse link 120, and the forward link 124 can be used differently than the reverse link 126. Frequency band.
  • FDD Frequency Division Duplex
  • the forward link 118 and the reverse link 120 can use a common frequency band, a forward link 124, and a reverse link.
  • Link 126 can use a common frequency band.
  • Each antenna (or set of antennas consisting of multiple antennas) and/or regions designed for communication is referred to as a sector of network device 102.
  • the antenna group can be designed to communicate with terminal devices in sectors of the network device 102 coverage area.
  • the transmit antenna of network device 102 may utilize beamforming to improve the signal to noise ratio of forward links 118 and 124.
  • the network device 102 uses beamforming to transmit signals to the randomly dispersed terminal devices 116 and 122 in the relevant coverage area, the network device 102 uses a single antenna to transmit signals to all of its terminal devices. Mobile devices are subject to less interference.
  • network device 102, terminal device 116, or terminal device 122 may be a wireless communication transmitting device and/or a wireless communication receiving device.
  • the wireless communication transmitting device can encode the data for transmission.
  • the wireless communication transmitting device may acquire (eg, generate, receive from other communication devices, or store in memory, etc.) a certain number of target data bits to be transmitted to the wireless communication receiving device over the channel.
  • Such data bits may be included in a transport block (or multiple transport blocks) of data that may be segmented to produce multiple code blocks.
  • the communication system 100 may be a public land mobile network (English full name may be: Public Land Mobile Network, English abbreviation may be: PLMN) network or D2D (Device to Device) network or M2M (Machine to Machine) network or other Network,
  • PLMN Public Land Mobile Network
  • D2D Device to Device
  • M2M Machine to Machine
  • FIG. 1 is only a simplified schematic diagram of an example, and other network devices may also be included in the network, which are not shown in FIG.
  • the network device may be in communication with the terminal device.
  • Devices such as base stations or base station controllers.
  • Each network device can provide communication coverage for a specific geographic area, and can communicate with terminal devices (eg, UEs) located within the coverage area (cell), the network device can support different standard communication protocols, or can support different Communication mode.
  • the network device may be a base station (Base Transceiver Station, abbreviated as "BTS”) in a GSM system or a CDMA system, or may be a base station (NodeB, referred to as "NB”) in a WCDMA system, or may be an LTE system.
  • BTS Base Transceiver Station
  • NodeB NodeB
  • WCDMA Wireless Fidelity
  • An evolved Node B (“eNB” or “eNodeB”), or a wireless controller in a Cloud Radio Access Network (CRAN), or the network device may be Network equipment in the future 5G network or network equipment in the future evolution of the Public Land Mobile Network (PLMN).
  • eNB evolved Node B
  • CRAN Cloud Radio Access Network
  • PLMN Public Land Mobile Network
  • the terminal device may refer to an access terminal, a user equipment (User Equipment, referred to as “UE”), a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, and a remote terminal.
  • UE User Equipment
  • the access terminal may be a cellular phone, a cordless phone, a Session Initiation Protocol ("SSIP”) phone, a Wireless Local Loop (WLL) station, and a personal digital processing (Personal Digital) Assistant, referred to as "PDA"), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in the Internet of Things, virtual reality devices, future 5G networks
  • PLMN Public Land Mobile Network
  • the method and device for wireless communication may be applied to a terminal device, where the terminal device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer.
  • the hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and a memory (also referred to as main memory).
  • the operating system may be any one or more computer operating systems that implement business processing through a process, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a Windows operating system.
  • the application layer includes applications such as a browser, an address book, word processing software, and instant messaging software.
  • a computer readable medium can include, but It is not limited to: a magnetic storage device (for example, a hard disk, a floppy disk, or a magnetic tape), an optical disk (for example, a compact disc (CD), a digital versatile disc (DVD), etc.), a smart card, and a flash memory device (for example, Erasable Programmable Read-Only Memory (EPROM), card, stick or key driver, etc.).
  • a magnetic storage device for example, a hard disk, a floppy disk, or a magnetic tape
  • an optical disk for example, a compact disc (CD), a digital versatile disc (DVD), etc.
  • a smart card for example, Erasable Programmable Read-Only Memory (EPROM), card, stick or key driver, etc.
  • EPROM Erasable Programmable Read-Only Memory
  • various storage media described herein can represent one or more devices and/or other machine-readable media for storing information.
  • the term "machine-readable medium” may include, but is not limited to, a variety of media capable of storing, containing, and/or carrying instructions and/or data.
  • the sending end in the embodiment of the present application may be a network device or a terminal device
  • the receiving end may be a network device or a terminal device.
  • FIG. 2 is a schematic flowchart of a method 2000 for wireless communication according to an embodiment of the present application. As shown in FIG. 2, the method 2000 includes the following.
  • each RLC protocol data unit of the multiple RLC protocol data units includes a first status report.
  • the first status report included in each RLC protocol data unit is used to indicate status information of multiple consecutive data packets sent by the sending end and a sequence number of a starting data packet in the multiple consecutive data packets.
  • status information of the plurality of consecutive data packets is used to indicate whether each of the plurality of consecutive data packets is received by the receiving end.
  • the receiving end After the communication between the receiving end and the transmitting end is changed from the interrupt to the recovery, the receiving end first receives the Packet Data Convergence Protocol Service Data Unit (PDCP SDU) from the source base station before the receiving end switches. After the handover, the PDCP SDU is received from the target base station (some of the PDCP SDUs are transferred from the source base station to the target base station, and some PDCP SDUs are sent by the source base station to the terminal but have not been acknowledged). When the handover occurs, the communication will be temporarily interrupted. According to the current Long Term Evolution (LTE), the PDCP layer of the packet data convergence protocol at the receiving end will accumulate some discontinuous data packets, and the PDCP layer at the transmitting end resumes communication. After the first time, it will be uncertain whether the receiving end will receive the data packet and resend the data packet.
  • LTE Long Term Evolution
  • each of the first status reports indicates a sequence number of the start data packet by using the first identifier and the second identifier, where the first identifier is data sent by the sending end to the receiving end.
  • the serial number of the first received packet or the first lost packet in the packet, the second identifier And an offset of the sequence number of the start data packet in the first status report relative to the first identifier.
  • the receiving end constructs a second status report in the PDCP layer according to some discontinuous data packets accumulated by the PDCP layer of the packet data convergence protocol, where the second status report is a PDCP status report; 2111, The receiving end transmits the PDCP status report to a Radio Link Control (RLC); 2112, and the receiving end is in the RLC layer according to a Radio Link Control Protocol Data Unit (Radio Link Control Protocol Data Unit).
  • RLC PDU The maximum allowable length, the status report is split, and when the status report cannot be accommodated in an RLC PDU, the status report is directly split and reported in each split substate.
  • the first identifier is a FMS
  • the second identifier is a segment offset (SO).
  • the FMS is used to indicate the first missing sequence number of the data packet sent by the sending end, or the FMS definition may be modified, that is, the FMS is used to indicate that the sending end is the first one received.
  • the serial number of the packet The specific meaning of the FMS can be specified in the protocol between the receiving end and the transmitting end, which is not limited by the present invention.
  • the segmentation offset SO is an integer multiple of 8 according to the provisions of the Internet Protocol.
  • Table 1 shows the format of the control packet for the PDCP status report.
  • the PDCP PDU is a bit string arranged in bytes, that is, an integer multiple of 8 bits.
  • the bit order of each parameter field in the PDCP PDU is the highest bit in the leftmost bit and the lowest bit in the rightmost bit.
  • the first D/C on the left side is used to indicate whether the PDU is a control PDU or a data PDU, and the next three bits are used to indicate the PDU type.
  • the PDU is a PDCP status report, and the value is 001.
  • the PDU is a feedback packet of the ROHC that is scattered, and when the value is 010-111, the PDU is reserved.
  • the last four bits of the first byte and the first bit of the second byte are reserved bits R, respectively.
  • the last seven and third bytes of the second byte are FMS, and FMS refers to the sequence number of the first packet that the receiver did not receive.
  • Bitmap is a bitmap, the length is variable, and the value of the Bitmap indicates the status information of the corresponding data packet. If the Bitmap value is 1, it indicates that the corresponding sequence number of the data packet is received or if the Bitmap value is 0, indicating the corresponding sequence number. The packet was not received.
  • the highest bit of the first byte of the Bitmap indicates whether the packet with the sequence number (FMS+1) is received by the receiving end, and the lowest bit of the first byte of the Bitmap indicates that the sequence number is (FMS+8). Whether the packet was received by the receiver.
  • the receiving end splits the status report at the RLC layer, and the prior art split format is as shown in Table 2.
  • the format of the acknowledge mode data unit is the format of the split status report.
  • the receiving end when the status report cannot be accommodated in one RLC PDU, the receiving end adds the FMS and the SO in each sub-state report when the RLC layer splits the status report, and generates a first status report, wherein the FMS is used to indicate a sequence number of the first lost data packet at the transmitting end.
  • the sender receives the first status report of the class, the sender can directly process the complete second status report. as shown in Table 3.
  • R1 is used to indicate whether there is an FMS. If the FMS exists, the transmitting end directly sends the first status report to the PDCP layer when receiving the first status report.
  • the receiving end does not receive the data packet with the sequence number 5, and the data packet transmitting end that is smaller than the serial number 5 has been received.
  • the status information of the other data packets whose sequence number is greater than 5 included in the status report has an indication of the value in the Bitmap. “0” means that the receiving end does not receive the data packet, and “1” represents that the receiving end receives the data packet.
  • the second sub-state report if the initial sub-state report has transmitted 24 packets, the second sub-state reports that the first lost packet has a sequence number of 29, then the FMS is 5 and SO is a byte.
  • the first lost packet indicated by the second sub-state report is offset from the first lost packet of the initial status report by 24 bits, ie the second sub-
  • the first lost packet of the status report is offset by 3 bytes from the first lost packet of the initial substate report, and SO is 3. Therefore, the FMS (value is 5) and the SO (value 3) are added to the second sub-state report to generate a first status report, when the sending end receives the first status report sent by the receiving end.
  • the first status report can be directly processed according to the indication information of the FMS and the SO without waiting to receive the complete second status report.
  • the data packet indicated by the FMS is defined as the first lost data packet only by way of example and not limitation.
  • the FMS can also indicate the first received data packet at the receiving end.
  • the FMS indicates the serial number of the first received data packet at the receiving end
  • the FMS of the initial substate report is 5
  • the receiving end receives the data packet with the sequence number of 5
  • the data packet of the smaller than the serial number 5 is not received.
  • the processing of subsequent Bitmaps is consistent with the above method. “0” means that the receiving end does not receive the data packet, and “1” represents that the receiving end receives the data packet. For the sake of brevity, it will not be repeated here.
  • the sending end receives the first status report sent by the receiving end except the initial status report
  • the sequence number of the indicated starting data packet may be determined according to the values of the FMS and the SO, and the sending end receives The starting data packet determined by the values of FMS and SO.
  • sequence number of the start data packet of each sub-state report is indicated according to the third identifier, where the third identifier is an FMS.
  • the receiving end splits the status report at the RLC layer, and when the status report is split, joins each sub-state report.
  • the FMS is used to indicate the sequence number of the first lost data packet in each of the sub-state reports.
  • the data packet indicated by the FMS is defined as the first lost data packet only by way of example and not limitation.
  • the FMS can also indicate the first received data packet at the receiving end.
  • the receiving end constructs a plurality of the first status reports in the PDCP layer according to the preset construction length according to the state information of the data packet sent by the sending end in the communication interruption process, where the multiple first Each of the first status reports in the status report has indication information indicating a sequence number of the start data packet of each of the first status reports; generating the plurality of RLCs according to the plurality of the first status reports Protocol data unit.
  • the indication information may be a third identifier, where the third identifier is an FMS, where the FMS is start data in multiple consecutive data packets indicated in the first status report to which the third identifier belongs.
  • the serial number of the package may be a third identifier, where the third identifier is an FMS, where the FMS is start data in multiple consecutive data packets indicated in the first status report to which the third identifier belongs. The serial number of the package.
  • the sender can limit the length of the status report to reduce the delay when constructing the status report, and avoid the sender resending unnecessary data packets. For example, limit the byte of the status report to 1500 bytes. When the status report's Bitmap reaches 1500 bytes, stop constructing the status report and start building the next status report. Report.
  • the maximum transmission unit is typically 1500 bytes, so the status report is limited to 1500 bytes, but the length is for example only and is not intended to limit the invention.
  • the sequence number of the start data packet indicated by the initial status report is a sequence number of the first received data packet or a sequence number of the first lost data packet, after the initial status report
  • the sequence number of the initial data packet in each of the other first status reports is the serial number of the first received data packet or the first lost data after the last data packet of the previous first status report.
  • the serial number of the package is the serial number of the package.
  • the receiving end determines the first lost data packet in the PDCP layer, and uses the sequence number of the first lost data packet as the FMS to construct a starting state report according to the preset length.
  • the plurality of the first status reports other than the initial status report report the sequence number of the first lost data packet after the last data packet reported from the current first status as the first state of the FMS constructing the preset length Reporting, until the plurality of the first status reports constructed indicate status information of some discontinuous data packets accumulated by all PDCP layers; 2121, the receiving end transmits the plurality of first status reports to the RLC layer.
  • each status report of the multiple status reports sets a fourth identifier, as shown in Table 4, where F is used to indicate whether the first status report in each RLC protocol data unit is an initial status. report.
  • F is used to indicate whether the first status report in each RLC protocol data unit is an initial status. report.
  • the receiving end determines the first lost data packet at the PDCP layer, and uses the sequence number of the first lost data packet as the FMS to construct a starting state report according to the preset length.
  • the value of F in the initial status report is 1, and the next first status reports the sequence number of the first lost packet after the last packet reported from the current first status as the FMS construction preset.
  • a first status report of the length, and F in the first status report other than the initial status report takes a value of 0 until the constructed plurality of first status reports indicate some discontinuous data accumulated by all PDCP layers a packet; 2131, the receiving end transmits the plurality of first status reports to the RLC layer.
  • the indication information may also be a first identifier and a second identifier, where the first identifier is an FMS, the second identifier is an SO, and the FMS is a sequence number of the first lost data packet.
  • the receiving end sends the multiple RLC protocol data units to the sending end.
  • the receiving end sends, to the sending end, a plurality of RLC protocol data units including FMS and SO.
  • the receiving end sends, to the sending end, multiple RLC protocol data units including an FMS.
  • the receiving end sends, to the sending end, multiple RLC protocol data units including FMS and F.
  • the sending end receives multiple RLC protocol data units sent by the receiving end.
  • the sending end receives, by the receiving end, multiple RLC protocol data units that include a first status report, where each first status report includes an FMS and an SO.
  • the transmitting end transmits the first status report from the RLC layer to the PDCP layer in the receiving order.
  • the sending end receives, by the receiving end, a plurality of RLC protocol data units that include a first status report, where each first status report includes an FMS, and Arranging a plurality of the first status reports in a receiving order of the plurality of first status reports, and in 2321, the transmitting end transmits the first status report in a receiving order from an RLC layer Give the PDCP layer.
  • the sending end receives, by the receiving end, a plurality of RLC protocol data units that include a first status report, where each first status report includes an FMS and an SO.
  • the sender sends the plurality of the first status reports from the RLC layer to the PDCP layer in an out-of-order manner.
  • each of the plurality of RLC protocol data units is used to indicate status information of the plurality of consecutive data packets and a sequence number of the start data packet in the plurality of consecutive data packets, where The status information of the plurality of consecutive data packets is used to indicate whether the data packet is received by the receiving end; and the status information of the plurality of consecutive data packets is determined according to each of the RLC protocol data units.
  • the sending end determines, according to the first identifier and the second identifier, a sequence number and other data packet of the start data packet in the first status report included in each RLC protocol data unit. a sequence number; determining status information corresponding to a sequence number of the start data packet and a sequence number of the other data packet.
  • the transmitting end receives the RLC protocol data unit at an RLC layer, and when the first status report included in the RLC protocol data unit includes an FMS and an SO, the sending end reports the first status. Passing from the RLC layer to the PDCP layer, when the first identifier FMS represents the sequence number of the first unreceived data packet, if SO is 0, the sub-state report is reported as the first sub-state report. The data packet of the sequence number corresponding to the FMS is lost, and the data packet before the sequence number corresponding to the first identifier is received.
  • the status information of the data packet before the sequence number of the first identifier FMS is not determined, and only the information of the status report is processed. Determining, according to the FMS and the SO, a sequence number of the first data packet in each of the sub-state reports, adding a SO ⁇ 8 to the sequence number corresponding to the first identifier FMS The serial number of the first lost packet, because the offset unit is one byte as specified in the Internet Protocol. The sequence number of each data packet corresponding to the bitmap information is determined, that is, the corresponding byte is added to the sequence number corresponding to the re-determined FMS to indicate the serial number of the corresponding data packet.
  • the transmitting end stops transmitting the data packet received by the receiving end according to the determined state information of the data packet in the communication switching process of the receiving end
  • the plurality of the first status reports included in the multiple RLC protocol data units are arranged in a receiving order of the multiple RLC protocol data units. Determining, according to the third identifier, a sequence of the start data packet and a sequence number of other data packets in the first status report included in each RLC protocol data unit; determining a sequence of the start data packet Status information corresponding to the serial number of the other data packet.
  • the transmitting end receives the rearrangement of the first status report in the receiving order of the first status report at the RLC layer.
  • the transmitting end delivers the first status report to the PDCP layer in the order of reception.
  • the FMS represents a sequence number of a data packet that is not received by the first one in the first status report, and in 2420, the transmitting end determines that the receiving end receives an FMS corresponding to the initial status report.
  • the data packet of the serial number and the data packet of the sequence number corresponding to the FMS are lost by the receiving end, and the sending end determines the other one in the first status report according to the information of the first status report and the corresponding serial number. Status information of the packet.
  • the sending end determines that the receiving end receives the sequence number of the last data packet of the previous status report and the latter status report. a data packet between the serial number of the first data packet between each sub-state report and the receiving end losing the data packet of the serial number corresponding to the FMS, the transmitting end reporting according to the first status The information and the corresponding serial number determine status information of other data packets indicated by the first status report.
  • each of the plurality of protocol RLC data units includes a fourth identifier, where the fourth identifier is used to indicate whether the first status report in each of the RLC protocol data units is Is a start status report; when the fourth identifier indicates that the first status report is the start status report, and the third identifier is a sequence number of a lost data packet, the sending end determines the Receiving, by the receiving end, a data packet whose sequence number is smaller than the starting data packet, and stopping sending the data packet whose sequence number is smaller than the starting data packet; or when the fourth identifier indicates the When the first status report is a start status report, and the third identifier is a sequence number of the received data packet, the sending end determines that the receiving end loses a data packet whose sequence number is smaller than the start data packet. And continuing to send the data packet whose sequence number is smaller than the data packet of the start data packet that is not repeatedly transmitted.
  • the fourth identifier is used to indicate whether the first status report in each of the RLC protocol data units
  • the transmitting end receives a plurality of RLC protocol data units sent by the transmitting end, decompresses the plurality of RLC protocol data units, and obtains a plurality of first status reports.
  • the transmitting end transmits the first status report to the PDCP layer in the RLC layer in the order of receiving the status report according to the fourth identifier.
  • the sending end determines that the receiving end receives a data packet that is smaller than a sequence number corresponding to the FMS of the initial status report.
  • the receiving end loses the data packet of the sequence number corresponding to the FMS
  • the sending end determines the state information of the other data packet indicated by the status report according to the information of the initial state report and the corresponding sequence number.
  • the sending end determines that the receiving end loses a data packet of a sequence number corresponding to the FMS, and the sending end Determining status information of other data packets indicated by the status report according to the status report information and the corresponding serial number.
  • the first status other than the initial status report reports the last one of the previous status reports.
  • the transmitting end directly transmits the status report to the PDCP layer when the RLC layer receives the status report.
  • the plurality of status reports are not sorted.
  • the sending end determines, according to the identifier information, whether the first status report is a start status report, and when the first status report is a start status report, The transmitting end determines that the receiving end receives a data packet smaller than the sequence number corresponding to the FMS, and the receiving end does not receive the data packet of the sequence number corresponding to the FMS; when the first status report is not When the initial status is reported, the sending end determines that the receiving end receives the data packet of the serial number corresponding to the FMS.
  • the sending end may directly cancel sending the data packet of the sequence number corresponding to the FMS to the receiving end, further reducing the retransmission of the data packet. , improve the efficiency of data transfer.
  • the method in the embodiment of the present application reduces the status report by sending the indication of the first status report when constructing the status report, or carrying the indication information when splitting the status report.
  • the dwell time of the terminal cancels the retransmission of unnecessary data packets, improves the efficiency of data transmission, and saves the air interface bandwidth.
  • FIG. 6 is a schematic block diagram of a receiving device 600 in accordance with an embodiment of the present application. As shown in FIG. 6, the receiving device 600 includes:
  • the processing module 610 is configured to generate, by the receiving end, a plurality of radio link control RLC protocol data units after the communication with the transmitting end changes from the interruption to the recovery, where each of the plurality of RLC protocol data units includes the first a status report, the first status report included in each RLC protocol data unit is used to indicate status information of multiple consecutive data packets sent by the sending end, and start data in the multiple consecutive data packets a sequence number of the packet, the status information of the plurality of consecutive data packets is used to indicate whether each of the plurality of consecutive data packets is received by the receiving end;
  • the sending module 620 is configured to send, by the sending end, the multiple RLC protocol data units to the sending end.
  • processing module 610 and the sending module 620 are used to perform various operations of the method 2000 for wireless communication in the embodiment of the present application. For brevity, details are not described herein again.
  • FIG. 7 is a schematic block diagram of a transmitting device 700 in accordance with an embodiment of the present application. As shown in FIG. 7, the sending device 700 includes:
  • the receiving module 710 is configured to: receive, by the transmitting end, a plurality of radio link control RLC protocol data units that are sent by the receiving end after the communication with the sending end is changed from being interrupted to being restored, and each RLC of the plurality of RLC protocol data units
  • the protocol data unit includes a first status report, where the first status report included in each RLC protocol data unit is used to indicate status information of the plurality of consecutive data packets sent by the sending end, and the multiple consecutive data packets. a sequence number of the start data packet in which the status information of the plurality of consecutive data packets is used to indicate whether each of the plurality of consecutive data packets is received by the receiving end.
  • a determining module 720 configured to determine, according to each of the RLC protocol data units, status information of the plurality of consecutive data packets; the determining module is further configured to stop sending according to the status information of the multiple consecutive data packets A data packet received by the receiving end in a plurality of consecutive data packets.
  • the receiving module 710 and the determining module 720 are used to perform various operations of the method 2000 for wireless communication in the embodiment of the present application. For brevity, details are not described herein again.
  • FIG. 8 is a schematic block diagram of a communication device 800 provided by an embodiment of the present application.
  • the communication device 800 includes:
  • a memory 810 configured to store a program, where the program includes a code
  • transceiver 820 configured to communicate with other devices
  • the processor 830 is configured to execute program code in the memory 810.
  • the processor 830 may implement the operations of the receiving device or the sending device in the method 2000.
  • the communication device 800 can be a receiving device or a transmitting device.
  • the transceiver 820 is configured to perform specific signal transceiving under the driving of the processor 830.
  • the processor 830 may further implement the operations of the receiving device or the sending device in the method 2000.
  • the communication device 800 can be a receiving device or a transmitting device.
  • the processor 830 may be a central processing unit (“CPU"), and the processor 830 may also be other general-purpose processors, digital signal processors ( DSP), application specific integrated circuit (ASIC), off-the-shelf programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory 810 can include read only memory and random access memory and provides instructions and data to the processor 830. A portion of the memory 810 may also include a non-volatile random access memory. For example, the memory 810 can also store information of the device type.
  • the transceiver 820 can be used to implement signal transmission and reception functions, such as frequency modulation and demodulation functions or up-conversion and down-conversion functions.
  • At least one step of the above method may be performed by an integrated logic circuit of hardware in the processor 830, or the integrated logic circuit may perform the at least one step driven by an instruction in a software form.
  • communication device 800 can be a chip or chipset.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented as a hardware processor, or may be performed by 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 830 reads the information in the memory and completes the steps of the above method in combination with the hardware thereof. To avoid repetition, it will not be described in detail here.
  • the size of the serial numbers of the above processes does not mean The order of execution, the order of execution of each process should be determined by its function and internal logic, and should not be construed as limiting the implementation process of the embodiments of the present application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Communication Control (AREA)

Abstract

本申请实施例提供了一种无线通信的方法和设备,减少了状态报告在发送端的时延,发送端能够更早收到和处理状态报告,取消接收端已经收到的数据包的重发,节省了空口带宽。所述方法包括:接收端在与发送端的通信从中断变为恢复后,生成多个无线链路控制RLC协议数据单元,所述多个RLC协议数据单元中的每个RLC协议数据单元包括第一状态报告,所述每个RLC协议数据单元包括的所述第一状态报告用于指示所述发送端发送的多个连续数据包的状态信息和所述多个连续数据包中的起始数据包的序列号,所述多个连续数据包的状态信息用于指示所述多个连续数据包中的每个数据包是否被所述接收端接收到,所述接收端向所述发送端发送所述多个RLC协议数据单元。

Description

无线通信的方法和设备 技术领域
本申请涉及通信领域,并且更具体地,涉及一种无线通信的方法和设备。
背景技术
随着高频频谱的不断使用,通信小区变得越来越小,热点小区的出现,进一步加剧了通信小区切换的频率。那么当用户设备(User Equipment,简称UE)发生切换前,用户设备先从源基站接收一些分组数据汇聚协议的业务数据单元(Packet Data Convergence Protocol Service Data Unit,简称PDCP SDU),切换后开始从目标基站接收PDCP SDU(其中一些PDCP SDU是由源基站转给目标基站,并且有一些PDCP SDU是源基站已发给终端但尚未得到确认的)。切换出现时,通信会有短暂的中断,按当前长期演进协议(Long Term Evolution,简称LTE),接收端的分组数据汇聚协议PDCP层会堆积一些不连续的数据包,而发送端的PDCP层在恢复通信后第一时间将不确定接收端是否收到数据包而重发数据包。通信恢复后,接收端根据已经收到的数据包在PDCP层构建PDCP状态报告,并将PDCP状态报告递交给无线链路控制层(Radio Link Control,简称RLC),接收端在RLC层组包发给发送端,发送端收到PDCP状态报告后,取消接收端已经收到的数据包的发送。
但是,从接收端构建并发送PDCP状态报告到发送端取消相应数据包的发送,时延偏大,还是会有不少数据包被重传出去,浪费了空口带宽。尤其随着PDCP速率不断提高,发送窗口不断变大,PDCP状态报告的长度也在不断变大,发送端在无线链路控制RLC层收集齐完整的PDCP状态报告需要的时延可能越来越大。
因此,如何让发送端尽快收到PDCP状态报告,降低时延,取消不必要的数据包重复发送,提高数据传输速率,是一项亟待解决的问题。
发明内容
本发明实施例提供了一种无线通信的方法和设备,减少了数据包的重发,提高了数据传递的效率,节省了空口带宽。
第一方面,本申请实施例提供了一种无线通信的方法,包括:接收端在 与发送端的通信从中断变为恢复后,生成多个无线链路控制RLC协议数据单元,所述多个RLC协议数据单元中的每个RLC协议数据单元包括第一状态报告,所述每个RLC协议数据单元包括的所述第一状态报告用于指示所述发送端发送的多个连续数据包的状态信息和所述多个连续数据包中的起始数据包的序列号,所述多个连续数据包的状态信息用于指示所述多个连续数据包中的每个数据包是否被所述接收端接收到;所述接收端向所述发送端发送所述多个RLC协议数据单元。
因此,在本申请实施例中,通过接收端在通信恢复后,发送的多个RLC协议数据单元中的每个RLC协议数据单元中包含第一状态报告,该第一状态报告用于指示发送端发送的多个连续数据包的状态信息和所述多个连续数据包中的起始数据包的序列号,从而发送端可以根据所述第一状态指示的起始数据包的序列号确定所述每个RLC协议数据单元中其他数据包的序列号,使得发送端在收到所述RLC协议数据单元时可以直接根据所述RLC协议数据单元包括的状态信息,以及所述每个RLC协议数据单元中所述多个连续数据包的序列号确定接收端在通信中断过程中是否接收到发送端发送的数据包,不用收集完整的状态报告,降低时延,取消不必要的数据包重复发送,提高数据传输速率,节省了空口带宽。
可选地,在第一方面的一种实现方式中每个所述第一状态报告通过包括的第一标识和第二标识指示所述起始数据包的序列号,所述第一标识为所述发送端发送给所述接收端的数据包中第一个接收的数据包或第一个丢失的数据包的序列号,所述第二标识为所述每个第一状态报告中所述起始数据包的序列号相对所述第一标识的偏移量。
可选地,所述第一标识为FMS,所述FMS为接收端第一个收到的数据包的序列号或接收端第一个丢失的数据包的序列号,可选地,所述第二标识为分段偏移量(Segment Offset,简称SO)。
可选地,在第一方面的一种实现方式中,所述每个第一状态报告通过包括的第三标识指示所述起始数据包的序列号,所述第三标识为FMS。
可选地,在第一方面的一种实现方式中,根据所述接收端缓存的所述发送端发送的数据包,确定所述第一个接收的数据包或所述第一个丢失的数据包;根据所述第一个接收的数据包或所述第一个丢失的数据包之后的数据包是否被接收,在PDCP层构建第二状态报告,所述第二状态报告包括所述第 一标识,以及包括所述第一个接收的数据包或所述第一个丢失的数据包之后的数据包的状态信息;根据RLC协议数据单元的最大允许长度,对所述第二状态报告进行拆分处理,得到多个长度为所述RLC协议数据单元的最大允许长度的子状态报告,其中,所述多个子状态报告中的起始子状态报告包括所述第一标识;在所述起始子状态报告中加入所述第二标识,生成一个所述第一状态报告,并根据所述一个所述第一状态报告,生成所述多个RLC协议数据单元中的起始RLC协议数据单元;在所述多个子状态报告中除所述起始子状态报告之外的其他至少一个子状态报告中的每个子状态报告中,加入所述第一标识和所述第二标识,生成至少一个所述第一状态报告,并根据所述至少一个所述第一状态报告,生成除所述起始RLC协议数据单元之外的其他至少一个RLC协议数据单元。
此时,通过在每个子状态报告中加入用于指示所述起始数据包的序列号的指示信息生成第一状态报告,使得发送端在收到包含指示所述起始数据包的序列号的指示信息的第一状态报告时,根据所述起始数据包的序列号,确定所述每个RLC协议数据单元中其他数据包的序列号,根据所述每个RLC协议数据单元包括的状态信息以及所述每个RLC协议数据单元中所述多个连续数据包的序列号可以直接处理所述第一状态报告,不用等待收集完整的第二状态报告,减少了处理所述子状态报告的时延,减少了数据包的重发,提高了数据传递的效率,节省了空口带宽。
可选地,在第一方面的一种实现方式中,所述指示信息可以是所述第一标识和所述第二标识,所述指示信息还可以是所述第三标识。
可选地,在第一方面的一种实现方式中,根据所述接收端缓存的所述发送端发送的数据包,确定所述发送端发送给所述接收端的数据包中第一个接收的数据包或第一个丢失的数据包;根据所述第一个接收的数据包或所述第一个丢失的数据包之后的数据包是否被接收,按照预设长度,在PDCP层构建多个所述第一状态报告;其中,多个所述第一状态报告中的起始状态报告指示的所述起始数据包的序列号为所述第一个接收的数据包的序列号或所述第一个丢失的数据包的序列号,所述起始状态报告之后的其他每个所述第一状态报告中的所述起始数据包的序列号为前一个第一状态报告的最后一个数据包之后的第一个接收数据包的序列号或第一个丢失的数据包的序列号;根据所述多个第一状态报告,生成所述多个RLC协议数据单元。
此时,通过限制状态报告的大小,避免了一次性传输状态报告带来的时延,提高了传输效率,减少了传输时延,提高了用户体验。
可选地,在第一方面的一种实现方式中,当构建RLC协议数据单元时优先级联所述第一状态报告。
可选地,在第一方面的一种实现方式中,所述每个RLC协议数据单元只包含所述第一状态报告。
可选地,在第一方面的一种实现方式中,所述多个所述第一状态报告中的每个所述第一状态报告设置第四标识,其中,所述第四标识用于指示所述每个所述第一状态报告是否为所述起始状态报告。
此时,通过在每个RLC协议数据单元中设置第四标识用于指示每个所述第一状态报告是否是所述起始状态报告,使得发送端可以乱序处理所述状态报告,减少状态报告在所述发送端的停留,提高了数据传输效率。
第二方面,本申请实施例提供了一种无线通信的方法,包括:发送端接收接收端在与所述发送端的通信从中断变为恢复后发送的多个无线链路控制RLC协议数据单元,所述多个RLC协议数据单元中的每个RLC协议数据单元包括第一状态报告,所述每个RLC协议数据单元包括的所述第一状态报告用于指示所述发送端发送的多个连续数据包的状态信息和所述多个连续数据包中的起始数据包的序列号,所述多个连续数据包的状态信息用于指示所述多个连续数据包中的每个数据包是否被所述接收端接收到;根据所述每个RLC协议数据单元,确定所述多个连续数据包的状态信息;根据所述多个连续数据包的状态信息,停止发送所述多个连续数据包中所述接收端收到的数据包。
此时,发送端根据接收到的所述多个RLC协议数据单元包括的第一状态报告中指示的所述起始数据包的序列号,确定所述每个RLC协议数据单元中其他数据包的序列号,根据所述每个RLC协议数据单元包括的第一状态报告指示所述发送端发送的多个连续数据包的状态信息,以及所述每个RLC协议数据单元中所述多个连续数据包的序列号,确定所述多个连续数据包的状态信息,不用在等待完整的状态报告,减少了状态报告在所述发送端的停留,提高了数据传输效率。
可选地,在第二方面的一种实现方式中,每个所述第一状态报告通过包括的第一标识和第二标识指示所述起始数据包的序列号,所述第一标识为所 述发送端发送给所述接收端的数据包中第一个接收的数据包或第一个丢失的数据包,所述第二标识为所述起始数据包相对所述第一标识的偏移量;所述根据所述每个RLC协议数据单元,确定所述多个连续数据包的状态信息,包括:根据所述第一标识和所述第二标识,确定所述每个RLC协议数据单元包括的所述第一状态报告中所述起始数据包的序列号和其他数据包的序列号;确定所述起始数据包的序列号和所述其他数据包的序列号对应的状态信息。
可选地,在第二方面的一种实现方式中,所述第一状态报告通过包括的第三标识指示所述起始数据包的序列号;所述根据所述每个RLC协议数据单元,确定所述多个连续数据包的状态信息,包括:根据所述第三标识,确定所述每个RLC协议数据单元包括的所述第一状态报告中所述起始数据包的序列和其他数据包的序列号;确定所述起始数据包的序列号和所述其他数据包的序列号对应的状态信息。
可选地,在第二方面的一种实现方式中,所述多个RLC协议数据单元中的起始RLC协议数据单元包括的所述第一状态报告中的所述第三标识为所述发送端发送给所述接收端的数据包中第一个接收的数据包或第一个丢失的数据包的序列号,所述起始RLC协议数据单元之后的其他所述RLC协议数据单元包括的第一状态报告中的所述第三标识为前一个RLC协议数据单元包括的第一状态报告中的最后一个数据包之后的第一个接收的数据包或第一个丢失的数据包的序列号;
按所述多个RLC协议数据单元的接收顺序排列所述多个RLC协议数据单元包括的多个第一状态报告;
当所述多个第一状态报告的起始状态报告包括的所述第三标识为丢失的数据包的序列号时,所述发送端确定所述接收端已接收到序列号小于所述起始数据包的数据包,并停止发送所述序列号小于所述起始数据包的数据包;或当所述起始状态报告包括的所述第三标识为接收到的数据包的序列号时,所述发送端确定所述接收端丢失了序列号小于所述起始数据包的数据包,并继续发送所述序列号小于所述起始数据包的数据包中未被重复发送的数据包;或当所述起始状态报告之外的其他每个第一状态报告中的所述第三标识为接收到的数据包的序列号时,确定所述其他每个第一状态报告中的起始数据包与前一个状态报告中的最后一个数据包之间的数据包为丢失的数 据包,并继续发送所述丢失的数据包中未被重复发送的数据包;或,当所述其他每个第一状态报告中的所述第三标识为丢失的数据包的序列号时,确定所述其他每个第一状态报告中的起始数据包与前一个状态报告中的最后一个数据包之间的数据包为收到的数据包,并停止发送所述收到的数据包。
可选地,在第二方面的一种实现方式中,所述多个RLC协议数据单元中的起始RLC协议数据单元的所述第一状态报告中的所述第三标识为所述发送端发送给所述接收端的数据包中第一个接收的数据包或第一个丢失的数据包的序列号,所述起始RLC协议数据单元之后的其他所述RLC协议数据单元包括的第一状态报告中的所述第三标识为前一个RLC协议数据单元中第一状态报告指示的最后一个数据包之后的第一个接收的数据包或第一个丢失的数据包的序列号;所述多个RLC协议数据单元中的每个RLC协议数据单元包含第四标识,其中,所述第四标识用于指示所述每个RLC协议数据单元中的第一状态报告是否是起始状态报告;
当所述第四标识指示所述第一状态报告是所述起始状态报告,且所述第三标识为丢失的数据包的序列号时,所述发送端确定所述接收端已接收到序列号小于所述起始数据包的数据包,并停止发送所述序列号小于所述起始数据包的数据包;或当所述第四标识指示所述第一状态报告是起始状态报告,且所述第三标识为接收到的数据包的序列号时,所述发送端确定所述接收端丢失了序列号小于所述起始数据包的数据包,并继续发送所述序列号小于所述起始数据包的数据包中未被重复发送的数据包。
第三方面,本申请实施例提供了一种接收端设备,其特征在于,包括处理模块和发送模块,可以执行第一方面或第一方面的任一可选的实现方式中的方法。
第四方面,本申请实施例提供了一种发送端设备,其特征在于,包括接收模块和确定模块,可以执行第二方面或第二方面的任一可选的实现方式中的方法。
第五方面,提供了一种接收端设备,包括存储器、收发器和处理器,所述存储器上存储有可以用于指示执行上述第一或其任意可选的实现方式的程序代码,收发器用于在处理器的驱动下执行具体的信号收发,当所述代码被执行时,所述处理器可以实现方法中终端设备执行各个操作。
第六方面,提供了一种发送端设备,包括存储器、收发器和处理器,所 述存储器上存储有可以用于指示执行上述第二或其任意可选的实现方式的程序代码,收发器用于在处理器的驱动下执行具体的信号收发,当所述代码被执行时,所述处理器可以实现方法中终端设备执行各个操作。
第七方面,提供了一种计算机存储介质,所述计算机存储介质中存储有程序代码,所述程序代码可以用于指示执行上述第一方面或第一方面的任意可选的实现方式中的方法。
第八方面,提供了一种计算机存储介质,所述计算机存储介质中存储有程序代码,所述程序代码可以用于指示执行上述第二方面或第二方面的任意可选的实现方式中的方法。
附图说明
图1是使用本申请实施例的一种无线通信的通信系统的示意图。
图2是根据本申请实施例的一种无线通信的方法的示意性流程图。
图3是根据本申请实施例的一种无线通信的方法的示意性流程图。
图4是根据本申请实施例的一种无线通信的方法的示意性流程图。
图5是根据本申请实施例的一种无线通信的方法的示意性流程图。
图6是根据本申请实施例的接收设备的示意性框图。
图7是根据本申请实施例的发送设备的示意性框图。
图8示出了本申请实施例的通信装置的示意性框图。
具体实施方式
下面将结合附图,对本申请实施例中的技术方案进行描述。
图1是使用本申请的一种无线通信的方法的示意图。如图1所示,所述通信系统100包括网络设备102,网络设备102可包括多个天线例如,天线104、106、108、110、112和114。另外,网络设备102可附加地包括发射机链和接收机链,本领域普通技术人员可以理解,它们均可包括与信号发送和接收相关的多个部件(例如处理器、调制器、复用器、解调器、解复用器或天线等)。
网络设备102可以与多个终端设备(例如终端设备116和终端设备122)通信。然而,可以理解,网络设备102可以与类似于终端设备116或122的任意数目标终端设备通信。
如图1所示,终端设备116与天线112和114通信,其中天线112和114通过前向链路118向终端设备116发送信息,并通过反向链路120从终端设备116接收信息。此外,终端设备122与天线104和106通信,其中天线104和106通过前向链路124向终端设备122发送信息,并通过反向链路126从终端设备122接收信息。
例如,在频分双工(FDD,Frequency Division Duplex)系统中,例如,前向链路118可与反向链路120使用不同的频带,前向链路124可与反向链路126使用不同的频带。
再例如,在时分双工(TDD,Time Division Duplex)系统和全双工(Full Duplex)系统中,前向链路118和反向链路120可使用共同频带,前向链路124和反向链路126可使用共同频带。
被设计用于通信的每个天线(或者由多个天线组成的天线组)和/或区域称为网络设备102的扇区。例如,可将天线组设计为与网络设备102覆盖区域的扇区中的终端设备通信。在网络设备102通过前向链路118和124分别与终端设备116和122进行通信的过程中,网络设备102的发射天线可利用波束成形来改善前向链路118和124的信噪比。此外,与网络设备通过单个天线向它所有的终端设备发送信号的方式相比,在网络设备102利用波束成形向相关覆盖区域中随机分散的终端设备116和122发送信号时,相邻小区中的移动设备会受到较少的干扰。
在给定时间,网络设备102、终端设备116或终端设备122可以是无线通信发送装置和/或无线通信接收装置。当发送数据时,无线通信发送装置可对数据进行编码以用于传输。具体地,无线通信发送装置可获取(例如生成、从其它通信装置接收、或在存储器中保存等)要通过信道发送至无线通信接收装置的一定数目标数据比特。这种数据比特可包含在数据的传输块(或多个传输块)中,传输块可被分段以产生多个码块。
此外,所述通信系统100可以是公共陆地移动网络(英文全称可以为:Public Land Mobile Network,英文简称可以为:PLMN)网络或者D2D(Device to Device)网络或者M2M(Machine to Machine)网络或者其他网络,图1只是举例的简化示意图,网络中还可以包括其他网络设备,图1中未予以画出。
可选地,在本申请实施例中,所述网络设备可以是与终端设备进行通信 的设备,例如,基站或基站控制器等。每个网络设备可以为特定的地理区域提供通信覆盖,并且可以与位于所述覆盖区域(小区)内的终端设备(例如UE)进行通信,网络设备可以支持不同制式的通信协议,或者可以支持不同的通信模式。例如,所述网络设备可以是GSM系统或CDMA系统中的基站(Base Transceiver Station,简称“BTS”),也可以是WCDMA系统中的基站(NodeB,简称“NB”),还可以是LTE系统中的演进型基站(Evolutional Node B,简称“eNB”或“eNodeB”),或者是云无线接入网络(Cloud Radio Access Network,简称“CRAN”)中的无线控制器,或者所述网络设备可以为未来5G网络中的网络设备或者未来演进的公共陆地移动网络(Public Land Mobile Network,简称“PLMN”)中的网络设备等。
可选地,在本申请实施例中,终端设备可以指接入终端、用户设备(User Equipment,简称为“UE”)、用户单元、用户站、移动站、移动台、远方站、远程终端、移动终端、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol,简称为“SIP”)电话、无线本地环路(Wireless Local Loop,简称为“WLL”)站、个人数字处理(Personal Digital Assistant,简称为“PDA”)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、物联网中的终端设备、虚拟现实设备、未来5G网络中的终端设备或者未来演进的公共陆地移动网络(Public Land Mobile Network,简称为“PLMN”)中的终端设备等。
本申请实施例提供的无线通信的方法和设备,可以应用于终端设备,所述终端设备包括硬件层、运行在硬件层之上的操作系统层,以及运行在操作系统层上的应用层。所述硬件层包括中央处理器(Central Processing Unit,CPU)、内存管理单元(MMU,Memory Management Unit)和内存(也称为主存)等硬件。所述操作系统可以是任意一种或多种通过进程(Process)实现业务处理的计算机操作系统,例如,Linux操作系统、Unix操作系统、Android操作系统、iOS操作系统或windows操作系统等。所述应用层包含浏览器、通讯录、文字处理软件、即时通信软件等应用。
此外,本申请的各个方面或特征可以实现成方法、装置或使用标准编程和/或工程技术的制品。本申请中使用的术语“制品”涵盖可从任何计算机可读器件、载体或介质访问的计算机程序。例如,计算机可读介质可以包括,但 不限于:磁存储器件(例如,硬盘、软盘或磁带等),光盘(例如,压缩盘(Compact Disc,CD)、数字通用盘(Digital Versatile Disc,DVD)等),智能卡和闪存器件(例如,可擦写可编程只读存储器(Erasable Programmable Read-Only Memory,EPROM)、卡、棒或钥匙驱动器等)。另外,本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读介质”可包括但不限于,能够存储、包含和/或承载指令和/或数据的各种介质。
应理解,本申请实施例中的发送端可以是网络设备也可以是终端设备,接收端可以是网络设备也可以是终端设备。
应理解,本申请实施例的技术方案可以应用于LTE系统,作为示例而非限定。为了更好地理解本申请,以LTE系统为例对本申请实施例进行说明。
图2是根据本申请实施例的一种无线通信的方法的2000的示意性流程图。如图2所示,所述方法2000包括以下内容。
2100,接收端在与发送端的通信从中断变为恢复后,生成多个无线链路控制RLC协议数据单元,所述多个RLC协议数据单元中的每个RLC协议数据单元包括第一状态报告,所述每个RLC协议数据单元包括的所述第一状态报告用于指示所述发送端发送的多个连续数据包的状态信息和所述多个连续数据包中的起始数据包的序列号,所述多个连续数据包的状态信息用于指示所述多个连续数据包中的每个数据包是否被所述接收端接收到。
接收端与发送端的通信从中断变为恢复后具体为,接收端发生切换前,接收端先从源基站接收一些分组数据汇聚协议的业务数据单元(Packet Data Convergence Protocol Service Data Unit,简称PDCP SDU),切换后开始从目标基站接收PDCP SDU(其中一些PDCP SDU是由源基站转给目标基站,并且有一些PDCP SDU是源基站已发给终端但尚未得到确认的)。切换出现时,通信会有短暂的中断,按当前长期演进协议(Long Term Evolution,简称LTE),接收端的分组数据汇聚协议PDCP层会堆积一些不连续的数据包,而发送端的PDCP层在恢复通信后第一时间将不确定接收端是否收到数据包而重发数据包。
可选地,每个所述第一状态报告通过包括的第一标识和第二标识指示所述起始数据包的序列号,所述第一标识为所述发送端发送给所述接收端的数据包中第一个接收的数据包或第一个丢失的数据包的序列号,所述第二标识 为所述每个第一状态报告中所述起始数据包的序列号相对所述第一标识的偏移量。
具体而言,如图3中的2110,接收端根据分组数据汇聚协议PDCP层堆积的一些不连续的数据包在PDCP层构建第二状态报告,所述第二状态报告为PDCP状态报告;2111,接收端将所述PDCP状态报告传递给无线链路控制层(Radio Link Control,简称RLC);2112,接收端在RLC层根据无线链路控制层RLC协议数据单元(Radio Link Control Protocol Data Unit,简称RLC PDU)最大允许长度,对所述状态报告进行拆分处理,当所述状态报告不能容纳在一个RLC PDU中时,直接将所述状态报告拆分,并在每个拆分的子状态报告中携带第一标识和第二标识,所述第一标识为FMS,所述第二标识为分段偏移量(Segment Offset,简称SO)。
可选地,所述FMS用于指示发送端发送的数据包中第一个丢失的数据包序列号,或者,也可以修改FMS定义,即FMS用于指示所述发送端第一个收到的数据包的序列号。在接收端和发送端之间的协议里可以规定FMS的具体含义,本发明对此不做限定。
根据因特网协议的规定,所述分段偏移量SO为8的整数倍。
例如,表1为PDCP状态报告的控制数据包的格式,PDCP PDU是一个长度按字节排列的比特串,即8位的整数倍。PDCP PDU中每个参数字段的比特顺序都是以最左位为最高位,最右位为最低位。其中左边第一位D/C用于指示PDU为控制PDU还是数据PDU,接下来的三位用于指示PDU类型,当取值为000时,所述PDU为PDCP状态报告,当取值为001,所述PDU为零散的ROHC的反馈包,当取值为010-111,所述PDU预留。第一个字节的后四位和第二个字节的第一位分别为预留位R。第二个字节的后七位和第三个字节为FMS,FMS指接收端没有收到的第一个数据包的序列号。Bitmap为位图,长度可变,Bitmap的取值指示相应的数据包的状态信息,如果Bitmap取值为1,说明相应的序号的数据包收到或如果Bitmap取值为0,说明相应的序号的数据包没有收到。例如,Bitmap的第一个字节的最高位表示序列号为(FMS+1)的数据包是否被接收端收到,Bitmap的第一个字节的最低位表示序列号为(FMS+8)的数据包是否被接收端收到。
表1.PDCP状态报告的控制数据包的格式
Figure PCTCN2017070472-appb-000001
当所述状态报告不能容纳在一个RLC PDU中时,所述接收端在RLC层将所述状态报告拆分,现有技术的拆分格式如表2所示。所述确认模式数据单元的格式为拆分的状态报告的格式。当发送端接收到所述拆分的子状态报告时,不能确定数据包的序列号,不能直接处理,必须收集完整的所述状态报告才能处理,在等待接收的时间段,所述发送端还是会将不少数据包重传出去,浪费了空口带宽。
表2.现有技术确认模式数据单元的格式
Figure PCTCN2017070472-appb-000002
在本申请的实施例中,当所述状态报告不能容纳在一个RLC PDU中时,所述接收端在RLC层将所述状态报告拆分时,在每个子状态报告中加入FMS和SO,生成第一状态报告,其中所述FMS用于指示所述发送端第一个丢失的数据包的序列号。发送端在收到所述类的第一状态报告时,可以直接处理,不用收集完整的所述第二状态报告。如表3所示。
表3.本申请实施例确认模式数据单元的格式
Figure PCTCN2017070472-appb-000003
在表3中,R1用于指示是否存在FMS,如果FMS存在,所述发送端在收到所述第一状态报告时,直接将所述第一状态报告发送给PDCP层。
具体而言,当所述起始子状态报告的FMS为5时,代表接收端没有收到序列号为5的数据包,小于序列号5的数据包发送端都已收到。所述状态报告包含的其他序列号大于5的数据包的状态信息有Bitmap中的取值指示。“0”代表接收端没有收到所述数据包,“1”代表接收端收到所述数据包。在第二个子状态报告中,假如起始子状态报告已经传输了24个数据包,第二个子状态报告的第一个丢失的数据包的序列号为29,则FMS为5,SO为字节数,每个字节8比特,所述第二个子状态报告指示的第一个丢失的数据包与起始状态报告的第一个丢失的数据包偏移了24比特,即所述第二个子状态报告的第一个丢失的数据包与起始子状态报告的第一个丢失的的数据包偏移了3个字节,SO为3。因此,在所述第二个子状态报告中加入FMS(取值为5)和SO(取值为3)生成一个第一状态报告,当发送端收到接收端发送的所述第一状态报告时,可以根据FMS和SO的指示信息直接处理所述第一状态报告,不用等待接收完整的第二状态报告。
应理解,本申请实施例中,将所述FMS指示的数据包定义为第一个丢失的数据包仅作为举例,并非限定。FMS还可以指示所述接收端第一个收到的数据包。
具体而言,FMS指示所述接收端第一个收到的数据包的序列号时,当所 述起始子状态报告的FMS为5时,代表接收端收到序列号为5的数据包,小于序列号5的数据包发送端都没有收到。后续Bitmap的处理与上述方法一致。“0”代表接收端没有收到所述数据包,“1”代表接收端收到所述数据包。为了简洁,此处不再赘述。当发送端收到接收端发送的除所述起始状态报告以外的所述第一状态报告时,可以根据FMS和SO的取值确定指示的起始数据包的序列号,所述发送端接收到所述由FMS和SO的取值确定的起始数据包。
可选地,根据第三标识指示每一个子状态报告的所述起始数据包的序列号,所述第三标识为FMS。
具体而言,当所述状态报告不能容纳在一个RLC PDU中时,所述接收端在RLC层将所述状态报告拆分,在拆分所述状态报告时,在每个子状态报告中加入所述FMS,所述FMS用于指示所述每个子状态报告中的第一个丢失的数据包的序列号。
应理解,本申请实施例中,将所述FMS指示的数据包定义为第一个丢失的数据包仅作为举例,并非限定。FMS还可以指示所述接收端第一个收到的数据包。
可选地,所述接收端根据通信中断过程中发送端发送的数据包的状态信息,按照预设构建长度,在PDCP层构建多个所述第一状态报告,其中,所述多个第一状态报告中每个所述第一状态报告有用于指示所述每个第一状态报告的起始数据包的序列号的指示信息;根据多个所述第一状态报告,生成所述多个RLC协议数据单元。
可选地,所述指示信息可以是第三标识,所述第三标识为FMS,所述FMS为所述第三标识所属的第一状态报告中指示的多个连续数据包中的起始数据包的序列号。
具体而言,当所述接收端在PDCP层构建的状态报告太大,所述接收端将所述状态报告传递到RLC层时,所述状态报告的长度超出了RLC PDU的长度,接收端在RLC层对所述状态报告进行拆分,这一过程会导致较大的时延,使得发送端重传了接收端已经收到的数据包。因此,发送端在构建状态报告时可以限制状态报告的长度来减小时延,避免发送端重发不必要的数据包。比如,将所述状态报告的字节限制在1500字节。当所述状态报告的Bitmap达到1500字节时,停止构建所述状态报告,开始构建下一条状态报 告。
应理解,因为在数据链路层对数据帧的长度都有一个限制,也就是链路层所能承受的最大数据长度,这个值称为最大传输单元。以太网为例,最大传输单元通常是1500字节,因此将所述状态报告限制在1500字节,但所述长度只用来举例,并非对本发明的限定。
可选地,根据所述发送端发送的数据包的发送顺序以及状态信息,确定所述发送端发送给所述接收端的数据包中第一个丢失的数据包;根据所述第一个接收的数据包或所述第一个丢失的数据包之后的数据包是否被接收,按照预设长度,在PDCP层构建多个所述第一状态报告;其中,多个所述第一状态报告中的起始状态报告指示的所述起始数据包的序列号为所述第一个接收的数据包的序列号或所述第一个丢失的数据包的序列号,所述起始状态报告之后的其他每个所述第一状态报告中的所述起始数据包的序列号为前一个第一状态报告的最后一个数据包之后的第一个接收数据包的序列号或第一个丢失的数据包的序列号。
具体而言,如图4中的2120,接收端在PDCP层确定第一个丢失的数据包,将所述第一个丢失的数据包的序列号作为FMS根据预设长度构建起始状态报告,除起始状态报告以外的其他多个所述第一状态报告从当前的第一状态报告的最后一个数据包之后的第一个丢失的数据包的序列号作为FMS构建预设长度的第一状态报告,直到构建的多个所述第一状态报告指示了全部PDCP层堆积的一些不连续的数据包的状态信息;2121,接收端将所述多个第一状态报告传递给RLC层。
可选地,所述多个状态报告的每个状态报告设置第四标识,如表4所示,其中F用来指示所述每个RLC协议数据单元中的第一状态报告是否是起始状态报告。当所述状态报告中的F取值为1时,所述第一状态报告为起始状态报告,当所述状态报告中的F取值为0时,所述第一状态报告不是起始状态报告。
表4.PDCP状态报告的控制数据包的格式
Figure PCTCN2017070472-appb-000004
Figure PCTCN2017070472-appb-000005
具体而言,如图5中的2130,接收端在PDCP层确定第一个丢失的数据包,将所述第一个丢失的数据包的序列号作为FMS根据预设长度构建起始状态报告,在所述起始状态报告中的F取值为1,下一条第一状态报告从当前的第一状态报告的最后一个数据包之后的第一个丢失的数据包的序列号作为FMS构建预设长度的第一状态报告,并且,除了起始状态报告以外的其他第一状态报告中的F取值为0,直到构建的多个第一状态报告指示了全部PDCP层堆积的一些不连续的数据包;2131,接收端将所述多个第一状态报告传递给RLC层。
可选地,所述指示信息还可以是第一标识和第二标识,所述第一标识为FMS,所述第二标识为SO,所述FMS指第一个丢失的数据包的序列号。
2200,所述接收端向所述发送端发送所述多个RLC协议数据单元。
可选地,如图3所示,在2210中,所述接收端向所述发送端发送多个包含FMS和SO的RLC协议数据单元。
可选地,如图4所示,在2220中,所述接收端向所述发送端发送包含FMS的多个RLC协议数据单元。
可选地,如图5所示,在2230中,所述接收端向所述发送端发送包含FMS和F的多个RLC协议数据单元。
2300,发送端接收接收端发送的多个RLC协议数据单元。
可选地,如图3所示,在2310中,所述发送端接收所述接收端发送的包含第一状态报告的多个RLC协议数据单元,所述每个第一状态报告包含FMS和SO,在2311中,所述发送端从RLC层将所述第一状态报告按接收顺序传递给PDCP层。
可选地,如图4所示,在2320中,所述发送端接收所述接收端发送的包含第一状态报告的多个RLC协议数据单元,所述每个第一状态报告包括FMS,并且按所述多个第一状态报告的接收顺序排列多个所述第一状态报告,在2321中,所述发送端从RLC层将所述第一状态报告按接收顺序传递 给PDCP层。
可选地,如图5所示,在2330中,所述发送端接收所述接收端发送的包含第一状态报告的多个RLC协议数据单元,所述每个第一状态报告包括FMS和SO,在2331中,所述发送端从RLC层将多个所述第一状态报告可以乱序传递给PDCP层。
2400,根据所述每个RLC协议数据单元,确定所述多个连续数据包的状态信息。
可选地,所述多个RLC协议数据单元中的每个RLC协议数据单元用于指示多个连续数据包的状态信息和所述多个连续数据包中的起始数据包的序列号,所述多个连续数据包的状态信息用于指示所述数据包是否被所述接收端接收到;根据所述每个RLC协议数据单元,确定所述多个连续数据包的状态信息。
可选地,发送端根据所述第一标识和所述第二标识,确定所述每个RLC协议数据单元包括的所述第一状态报告中所述起始数据包的序列号和其他数据包的序列号;确定所述起始数据包的序列号和所述其他数据包的序列号对应的状态信息。
具体而言,如图3所示。在2410中,所述发送端在RLC层接收到所述RLC协议数据单元,当所述RLC协议数据单元包含的第一状态报告包括FMS和SO时,所述发送端将所述第一状态报告从RLC层传递到PDCP层,当所述第一标识FMS代表第一个没有收到的的数据包的序列号时,如果SO为0时,代表所述子状态报告为第一个子状态报告,所述FMS对应的序列号的数据包丢失,在所述第一标识对应的序列号之前的数据包都已接收。根据所述第一标识FMS对应的序列号确定位图信息对应的每个数据包的序列号,在FMS对应的序列号上加相应的字节则表示对应的数据包的序列号。如果所述序列号的位图信息为“1”,代表所述接收端收到所述数据包,如果所述序列号的位图信息为“0”,代表所述接收端没有收到所述数据包。如图3中的2411,如果所述第二标识SO不为0,代表所述状态报告分片不是起始子状态报告,发送端确定所述第一标识FMS对应的序列号的数据包丢失,所述第一标识FMS的序列号之前的数据包的状态信息不确定,仅处理所述状态报告的信息。根据FMS和SO,确定所述每个子状态报告中所述第一个数据包的序列号,在第一标识FMS对应的序列号加上SO×8为所述状态报 告中的第一个丢失数据包的序列号,因为因特网协议中规定,偏移单位为一个字节。确定位图信息对应的每个数据包的序列号,即在重新确定的FMS对应的序列号上加相应的字节则表示对应的数据包的序列号。相应地,如果所述序列号的位图信息为“1”,代表所述接收端收到所述数据包,如果所述序列号的位图信息为“0”,代表所述接收端没有收到所述数据包。发送端根据确定的所述接收端在通信切换过程中的所述数据包的状态信息,停止发送所述接收端收到的数据包
可选地,按所述多个RLC协议数据单元的接收顺序排列所述多个RLC协议数据单元包括的多个所述第一状态报告。根据所述第三标识,确定所述每个RLC协议数据单元包括的所述第一状态报告中所述起始数据包的序列和其他数据包的序列号;确定所述起始数据包的序列号和所述其他数据包的序列号对应的状态信息。
具体而言,如图4所示。在2320中,发送端在RLC层按所述第一状态报告的接收顺序接收重新排列所述第一状态报告。在2321中,发送端按接收顺序将所述第一状态报告传递给PDCP层。所述FMS代表所述第一状态报告中第一个没有收到的数据包的序列号,在2420中,所述发送端确定所述接收端接收到小于所述起始状态报告的FMS对应的序列号的数据包和所述接收端丢失所述FMS对应的序列号的数据包,所述发送端根据所述第一状态报告的信息以及对应的序列号,确定所述第一状态报告中其他数据包的状态信息。在2421中,如果所述第一状态报告不是所述起始状态报告,所述发送端确定所述接收端收到所述前一个状态报告的最后一个数据包的序列号与后一个状态报告之间的第一个数据包的序列号之间的数据包每一个子状态报告的和所述接收端丢失所述FMS对应的序列号的数据包,所述发送端根据所述第一状态报告的信息以及对应的序列号,确定所述第一状态报告指示的其他数据包的状态信息。
可选地,所述多个协议RLC数据单元中的每个RLC协议数据单元包含第四标识,其中,所述第四标识用于指示所述每个RLC协议数据单元中的第一状态报告是否是起始状态报告;当所述第四标识指示所述第一状态报告是所述起始状态报告,且所述第三标识为丢失的数据包的序列号时,所述发送端确定所述接收端已接收到序列号小于所述起始数据包的数据包,并停止发送所述序列号小于所述起始数据包的数据包;或当所述第四标识指示所述 第一状态报告是起始状态报告,且所述第三标识为接收到的数据包的序列号时,所述发送端确定所述接收端丢失了序列号小于所述起始数据包的数据包,并继续发送所述序列号小于所述起始数据包的数据包中未被重复发送的数据包。
具体而言,如图5所示。在2330中,发送端接收发送端发送的多个RLC协议数据单元,解压所述多个RLC协议数据单元,得到多个第一状态报告。在2331中,发送端根据第四标识,在RLC层将所述第一状态报告可以不按接收所述状态报告的顺序传递给PDCP层。在2430中,当所述第四标识指示所述第一状态报告是所述起始状态报告,所述发送端确定所述接收端接收到小于起始状态报告的FMS对应的序列号的数据包和所述接收端丢失所述FMS对应的序列号的数据包,所述发送端根据所述起始状态报告的信息以及对应的序列号,确定所述状态报告指示的其他数据包的状态信息。在2431中,当所述第四标识指示所述第一状态报告不是所述起始状态报告,所述发送端确定所述接收端丢失所述FMS对应的序列号的数据包,所述发送端根据所述状态报告的信息以及对应的序列号,确定所述状态报告指示的其他数据包的状态信息。
可选地,当所述起始状态报告以所述接收端第一个丢失的数据包的序列号作为FMS,除所述起始状态报告以外的其他第一状态报告以前一个状态报告的最后一个数据包之后的所述接收端收到的第一个接收数据包的序列号作为FMS时,所述发送端在RLC层收到所述状态报告时,直接将所述状态报告传递给PDCP层,不用将所述多个状态报告排序,在PDCP层,所述发送端根据标识信息,判断所述第一状态报告是否为起始状态报告,当所述第一状态报告是起始状态报告时,所述发送端确定所述接收端收到小于所述FMS对应的序列号的数据包,并且所述接收端没有收到所述FMS对应的序列号的数据包;当所述第一状态报告不是起始状态报告时,所述发送端确定所述接收端收到所述FMS对应的序列号的数据包。
此时,所述发送端在所述状态报告不是所述起始状态报告时,可以直接取消向所述接收端发送所述FMS对应的序列号的数据包,更进一步减少了数据包的重发,提高了传递数据的效率。
本申请实施例中的方法,通过在构建状态报告时限制所述第一状态报告的大小,或者在拆分所述状态报告时携带指示信息,减少了状态报告在发送 端的停留时间,取消了不必要的数据包的重发,提高了数据传递的效率,节省了空口带宽。
图6是根据本申请实施例的接收设备600的示意性框图。如图6所示,所述接收设备600包括:
处理模块610,用于接收端在与发送端的通信从中断变为恢复后,生成多个无线链路控制RLC协议数据单元,所述多个RLC协议数据单元中的每个RLC协议数据单元包括第一状态报告,所述每个RLC协议数据单元包括的所述第一状态报告用于指示所述发送端发送的多个连续数据包的状态信息和所述多个连续数据包中的起始数据包的序列号,所述多个连续数据包的状态信息用于指示所述多个连续数据包中的每个数据包是否被所述接收端接收到;
发送模块620,用于所述发送端向所述发送端发送所述多个RLC协议数据单元。
可选地,所述处理模块610和所述发送模块620用于执行本申请实施例的一种无线通信的方法2000的各个操作,为了简洁,在此不再赘述。
图7是根据本申请实施例的发送设备700的示意性框图。如图7所示,所述发送设备700包括:
接收模块710,用于发送端接收接收端在与所述发送端的通信从中断变为恢复后发送的多个无线链路控制RLC协议数据单元,所述多个RLC协议数据单元中的每个RLC协议数据单元包括第一状态报告,所述每个RLC协议数据单元包括的所述第一状态报告用于指示所述发送端发送的多个连续数据包的状态信息和所述多个连续数据包中的起始数据包的序列号,所述多个连续数据包的状态信息用于指示所述多个连续数据包中的每个数据包是否被所述接收端接收到。
确定模块720,用于根据所述每个RLC协议数据单元,确定所述多个连续数据包的状态信息;所述确定模块还用于根据所述多个连续数据包的状态信息,停止发送所述多个连续数据包中所述接收端收到的数据包。
可选地,所述接收模块710和所述确定模块720用于执行本申请实施例的一种无线通信的方法2000的各个操作,为了简洁,在此不再赘述。
图8示出了本申请实施例提供的通信设备800的示意性框图,所述通信装置800包括:
存储器810,用于存储程序,所述程序包括代码;
收发器820,用于和其他设备进行通信;
处理器830,用于执行存储器810中的程序代码。
可选地,当所述代码被执行时,所述处理器830可以实现方法2000中接收设备或发送设备执行各个操作,为了简洁,在此不再赘述。此时,通信装置800可以为接收设备或发送设备。收发器820用于在处理器830的驱动下执行具体的信号收发。
可选地,当所述代码被执行时,所述处理器830还可以实现方法2000中接收设备或发送设备执行各个操作,为了简洁,在此不再赘述。此时,通信装置800可以为接收设备或发送设备。
应理解,在本申请实施例中,所述处理器830可以是中央处理单元(Central Processing Unit,简称为“CPU”),所述处理器830还可以是其他通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者所述处理器也可以是任何常规的处理器等。
所述存储器810可以包括只读存储器和随机存取存储器,并向处理器830提供指令和数据。存储器810的一部分还可以包括非易失性随机存取存储器。例如,存储器810还可以存储设备类型的信息。
收发器820可以是用于实现信号发送和接收功能,例如频率调制和解调功能或叫上变频和下变频功能。
在实现过程中,上述方法的至少一个步骤可以通过处理器830中的硬件的集成逻辑电路完成,或所述集成逻辑电路可在软件形式的指令驱动下完成所述至少一个步骤。因此,通信装置800可以是个芯片或者芯片组。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成,或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器,闪存、只读存储器,可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。所述存储介质位于存储器,处理器830读取存储器中的信息,结合其硬件完成上述方法的步骤。为避免重复,这里不再详细描述。
应理解,在本申请的各种实施例中,上述各过程的序号的大小并不意味 着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本申请实施例的实施过程构成任何限定。
所属领的技术人员可以清楚地了解到,为描述的方便和简洁,上述描述的系统、装置和单元的具体工作过程,可以参考前述方法实施例中的对应过程,在此不再赘述。
以上所述,仅为本申请的具体实施方式,但本申请的保护范围并不局限于此,任何熟悉本技术领的技术人员在本申请揭露的技术范围内,可轻易想到变化或替换,都应涵盖在本申请的保护范围之内。因此,本申请的保护范围应以所述权利要求的保护范围为准。

Claims (22)

  1. 一种无线通信的方法,其特征在于,包括:
    接收端在与发送端的通信从中断变为恢复后,生成多个无线链路控制RLC协议数据单元,所述多个RLC协议数据单元中的每个RLC协议数据单元包括第一状态报告,所述每个RLC协议数据单元包括的所述第一状态报告用于指示所述发送端发送的多个连续数据包的状态信息和所述多个连续数据包中的起始数据包的序列号,所述多个连续数据包的状态信息用于指示所述多个连续数据包中的每个数据包是否被所述接收端接收到;
    所述接收端向所述发送端发送所述多个RLC协议数据单元。
  2. 根据权利要求1所述的方法,其特征在于,每个所述第一状态报告通过包括的第一标识和第二标识指示所述起始数据包的序列号,所述第一标识为所述发送端发送给所述接收端的数据包中第一个接收的数据包或第一个丢失的数据包的序列号,所述第二标识为所述每个第一状态报告中所述起始数据包的序列号相对所述第一标识的偏移量。
  3. 根据权利要求1所述的方法,其特征在于,所述每个第一状态报告通过包括的第三标识指示所述起始数据包的序列号。
  4. 根据权利要求2所述的方法,其特征在于,所述生成多个RLC协议数据单元,包括:
    根据所述接收端缓存的所述发送端发送的数据包,确定所述第一个接收的数据包或所述第一个丢失的数据包;
    根据所述第一个接收的数据包或所述第一个丢失的数据包之后的数据包是否被接收,在PDCP层构建第二状态报告,所述第二状态报告包括所述第一标识,以及包括所述第一个接收的数据包或所述第一个丢失的数据包之后的数据包的状态信息;
    根据RLC协议数据单元的最大允许长度,对所述第二状态报告进行拆分处理,得到多个长度为所述RLC协议数据单元的最大允许长度的子状态报告,其中,所述多个子状态报告中的起始子状态报告包括所述第一标识;
    在所述起始子状态报告中加入所述第二标识,生成一个所述第一状态报告,并根据所述一个所述第一状态报告,生成所述多个RLC协议数据单元中的起始RLC协议数据单元;
    在所述多个子状态报告中除所述起始子状态报告之外的其他至少一个 子状态报告中的每个子状态报告中,加入所述第一标识和所述第二标识,生成至少一个所述第一状态报告,并根据所述至少一个所述第一状态报告,生成除所述起始RLC协议数据单元之外的其他至少一个RLC协议数据单元。
  5. 根据权利要求3所述的方法,其特征在于,所述生成多个RLC协议数据单元,包括:
    根据所述接收端缓存的所述发送端发送的数据包,确定所述发送端发送给所述接收端的数据包中第一个接收的数据包或第一个丢失的数据包;
    根据所述第一个接收的数据包或所述第一个丢失的数据包之后的数据包是否被接收,按照预设长度,在PDCP层构建多个所述第一状态报告;
    其中,多个所述第一状态报告中的起始状态报告指示的所述起始数据包的序列号为所述第一个接收的数据包的序列号或所述第一个丢失的数据包的序列号,所述起始状态报告之后的其他每个所述第一状态报告中的所述起始数据包的序列号为前一个第一状态报告的最后一个数据包之后的第一个接收数据包的序列号或第一个丢失的数据包的序列号;
    根据所述多个第一状态报告,生成所述多个RLC协议数据单元。
  6. 根据权利要求5所述的方法,其特征在于,所述多个所述第一状态报告中的每个所述第一状态报告设置第四标识,其中,所述第四标识用于指示所述每个所述第一状态报告是否为所述起始状态报告。
  7. 一种无线通信的方法,其特征在于,包括:
    发送端接收接收端在与所述发送端的通信从中断变为恢复后发送的多个无线链路控制RLC协议数据单元,所述多个RLC协议数据单元中的每个RLC协议数据单元包括第一状态报告,所述每个RLC协议数据单元包括的所述第一状态报告用于指示所述发送端发送的多个连续数据包的状态信息和所述多个连续数据包中的起始数据包的序列号,所述多个连续数据包的状态信息用于指示所述多个连续数据包中的每个数据包是否被所述接收端接收到;
    根据所述每个RLC协议数据单元,确定所述多个连续数据包的状态信息;
    根据所述多个连续数据包的状态信息,停止发送所述多个连续数据包中所述接收端收到的数据包。
  8. 根据权利要求7所述的方法,其特征在于,每个所述第一状态报告 通过包括的第一标识和第二标识指示所述起始数据包的序列号,所述第一标识为所述发送端发送给所述接收端的数据包中第一个接收的数据包的序列号或第一个丢失的数据包序列号,所述第二标识为所述起始数据包相对所述第一标识的偏移量;
    所述根据所述每个RLC协议数据单元,确定所述多个连续数据包的状态信息,包括:
    根据所述第一标识和所述第二标识,确定所述每个RLC协议数据单元包括的所述第一状态报告中所述起始数据包的序列号和其他数据包的序列号;
    确定所述起始数据包的序列号和所述其他数据包的序列号对应的状态信息。
  9. 根据权利要求7所述的方法,其特征在于,所述第一状态报告通过包括的第三标识指示所述起始数据包的序列号;
    所述根据所述每个RLC协议数据单元,确定所述多个连续数据包的状态信息,包括:
    根据所述第三标识,确定所述每个RLC协议数据单元包括的所述第一状态报告中所述起始数据包的序列和其他数据包的序列号;
    确定所述起始数据包的序列号和所述其他数据包的序列号对应的状态信息。
  10. 根据权利要求9所述的方法,其特征在于,所述多个RLC协议数据单元中的起始RLC协议数据单元包括的所述第一状态报告中的所述第三标识为所述发送端发送给所述接收端的数据包中第一个接收的数据包或第一个丢失的数据包的序列号,所述起始RLC协议数据单元之后的其他所述RLC协议数据单元包括的第一状态报告中的所述第三标识为前一个RLC协议数据单元包括的第一状态报告中的最后一个数据包之后的第一个接收的数据包或第一个丢失的数据包的序列号;
    所述方法还包括:
    按所述多个RLC协议数据单元的接收顺序排列所述多个RLC协议数据单元包括的多个第一状态报告;
    当所述多个第一状态报告的起始状态报告包括的所述第三标识为丢失的数据包的序列号时,所述发送端确定所述接收端已接收到序列号小于所述 起始数据包的数据包,并停止发送所述序列号小于所述起始数据包的数据包;或
    当所述起始状态报告包括的所述第三标识为接收到的数据包的序列号时,所述发送端确定所述接收端丢失了序列号小于所述起始数据包的数据包,并继续发送所述序列号小于所述起始数据包的数据包中未被重复发送的数据包;或
    当所述起始状态报告之外的其他每个第一状态报告中的所述第三标识为接收到的数据包的序列号时,确定所述其他每个第一状态报告中的起始数据包与前一个状态报告中的最后一个数据包之间的数据包为丢失的数据包,并继续发送所述丢失的数据包中未被重复发送的数据包;或,
    当所述其他每个第一状态报告中的所述第三标识为丢失的数据包的序列号时,确定所述其他每个第一状态报告中的起始数据包与前一个状态报告中的最后一个数据包之间的数据包为收到的数据包,并停止发送所述收到的数据包。
  11. 根据权利要求9所述的方法,其特征在于,所述多个RLC协议数据单元中的起始RLC协议数据单元的所述第一状态报告中的所述第三标识为所述发送端发送给所述接收端的数据包中第一个接收的数据包或第一个丢失的数据包的序列号,所述起始RLC协议数据单元之后的其他所述RLC协议数据单元包括的第一状态报告中的所述第三标识为前一个RLC协议数据单元中第一状态报告指示的最后一个数据包之后的第一个接收的数据包或第一个丢失的数据包的序列号;所述多个协议RLC数据单元中的每个RLC协议数据单元包含第四标识,其中,所述第四标识用于指示所述每个RLC协议数据单元中的第一状态报告是否是起始状态报告;
    所述方法还包括:
    当所述第四标识指示所述第一状态报告是所述起始状态报告,且所述第三标识为丢失的数据包的序列号时,所述发送端确定所述接收端已接收到序列号小于所述起始数据包的数据包,并停止发送所述序列号小于所述起始数据包的数据包;或
    当所述第四标识指示所述第一状态报告是起始状态报告,且所述第三标识为接收到的数据包的序列号时,所述发送端确定所述接收端丢失了序列号小于所述起始数据包的数据包,并继续发送所述序列号小于所述起始数据包 的数据包中未被重复发送的数据包。
  12. 一种无线通信的设备,其特征在于,包括:
    处理模块,用于接收端在与发送端的通信从中断变为恢复后,生成多个无线链路控制RLC协议数据单元,所述多个RLC协议数据单元中的每个RLC协议数据单元包括第一状态报告,所述每个RLC协议数据单元包括的所述第一状态报告用于指示所述发送端发送的多个连续数据包的状态信息和所述多个连续数据包中的起始数据包的序列号,所述多个连续数据包的状态信息用于指示所述多个连续数据包中的每个数据包是否被所述接收端接收到;
    发送模块,用于所述接收端向所述发送端发送所述多个RLC协议数据单元。
  13. 根据权利要求12所述的设备,其特征在于,所述处理模块还用于通过包括的第一标识和第二标识指示所述起始数据包的序列号,所述第一标识为所述发送端发送给所述接收端的数据包中第一个接收的数据包或第一个丢失的数据包的序列号,所述第二标识为所述每个第一状态报告中所述起始数据包的序列号相对所述第一标识的偏移量。
  14. 根据权利要求12所述的设备,其特征在于,所述处理模块还用于通过包括的第三标识指示所述起始数据包的序列号。
  15. 根据权利要求13所述的设备,其特征在于,所述处理模块具体用于:
    根据所述接收端缓存的所述发送端发送的数据包,确定所述第一个接收的数据包或所述第一个丢失的数据包;
    根据所述第一个接收的数据包或所述第一个丢失的数据包之后的数据包是否被接收,在PDCP层构建第二状态报告,所述第二状态报告包括所述第一标识,以及包括所述第一个接收的数据包或所述第一个丢失的数据包之后的数据包的状态信息;
    根据RLC协议数据单元的最大允许长度,对所述第二状态报告进行拆分处理,得到多个长度为所述RLC协议数据单元的最大允许长度的子状态报告,其中,所述多个子状态报告中的起始子状态报告包括所述第一标识;
    在所述起始子状态报告中加入所述第二标识,生成一个所述第一状态报告,并根据所述一个所述第一状态报告,生成所述多个RLC协议数据单元 中的起始RLC协议数据单元;
    在所述多个子状态报告中除所述起始子状态报告之外的其他至少一个子状态报告中的每个子状态报告中,加入所述第一标识和所述第二标识,生成至少一个所述第一状态报告,并根据所述至少一个所述第一状态报告,生成除所述起始RLC协议数据单元之外的其他至少一个RLC协议数据单元。
  16. 根据权利要求14所述的设备,其特征在于,所述处理模块还用于:
    根据所述接收端缓存的所述发送端发送的数据包,确定所述发送端发送给所述接收端的数据包中第一个接收的数据包或第一个丢失的数据包;
    根据所述第一个接收的数据包或所述第一个丢失的数据包之后的数据包是否被接收,按照预设长度,在PDCP层构建多个所述第一状态报告;
    其中,多个所述第一状态报告中的起始状态报告指示的所述起始数据包的序列号为所述第一个接收的数据包的序列号或所述第一个丢失的数据包的序列号,所述起始状态报告之后的其他每个所述第一状态报告中的所述起始数据包的序列号为前一个第一状态报告的最后一个数据包之后的第一个接收数据包的序列号或第一个丢失的数据包的序列号;
    根据所述多个第一状态报告,生成所述多个RLC协议数据单元。
  17. 根据权利要求16所述的设备,其特征在于,所述处理模块还用于在多个所述第一状态报告中的每个所述第一状态报告设置第四标识,其中,所述第四标识用于指示所述每个所述第一状态报告是否为所述起始状态报告。
  18. 一种无线通信的设备,其特征在于,包括:
    接收模块,用于发送端接收接收端在与所述发送端的通信从中断变为恢复后发送的多个无线链路控制RLC协议数据单元,所述多个RLC协议数据单元中的每个RLC协议数据单元包括第一状态报告,所述每个RLC协议数据单元包括的所述第一状态报告用于指示所述发送端发送的多个连续数据包的状态信息和所述多个连续数据包中的起始数据包的序列号,所述多个连续数据包的状态信息用于指示所述多个连续数据包中的每个数据包是否被所述接收端接收到;
    确定模块,用于根据所述每个RLC协议数据单元,确定所述多个连续数据包的状态信息;
    所述确定模块还用于根据所述多个连续数据包的状态信息,停止发送所 述多个连续数据包中所述接收端收到的数据包。
  19. 根据权利要求18所述的设备,其特征在于,每个所述第一状态报告通过包括的第一标识和第二标识指示所述起始数据包的序列号,所述第一标识为所述发送端发送给所述接收端的数据包中第一个接收的数据包的序列号或第一个丢失的数据包的序列号,所述第二标识为所述起始数据包相对所述第一标识的偏移量;
    所述确定模块具体用于:
    根据所述第一标识和所述第二标识,确定所述每个RLC协议数据单元包括的所述第一状态报告中所述起始数据包的序列号和其他数据包的序列号;
    确定所述起始数据包的序列号和所述其他数据包的序列号对应的状态信息。
  20. 根据权利要求18所述的设备,其特征在于,所述第一状态报告通过包括的第三标识指示所述起始数据包的序列号;
    所述确定模块还用于:
    根据所述第三标识,确定所述每个RLC协议数据单元包括的所述第一状态报告中所述起始数据包的序列和其他数据包的序列号;
    确定所述起始数据包的序列号和所述其他数据包的序列号对应的状态信息。
  21. 根据权利要求20所述的设备,其特征在于,所述多个RLC协议数据单元中的起始RLC协议数据单元包括的所述第一状态报告中的所述第三标识为所述发送端发送给所述接收端的数据包中第一个接收的数据包或第一个丢失的数据包的序列号,所述起始RLC协议数据单元之后的其他所述RLC协议数据单元包括的第一状态报告中的所述第三标识为前一个RLC协议数据单元包括的第一状态报告中的最后一个数据包之后的第一个接收的数据包或第一个丢失的数据包的序列号;
    所述确定模块还用于:
    按所述多个RLC协议数据单元的接收顺序排列所述多个RLC协议数据单元包括的多个第一状态报告;
    当所述多个第一状态报告的起始状态报告包括的所述第三标识为丢失的数据包的序列号时,所述发送端确定所述接收端已接收到序列号小于所述 起始数据包的数据包,并停止发送所述序列号小于所述起始数据包的数据包;或
    当所述起始状态报告包括的所述第三标识为接收到的数据包的序列号时,所述发送端确定所述接收端丢失了序列号小于所述起始数据包的数据包,并继续发送所述序列号小于所述起始数据包的数据包中未被重复发送的数据包;或
    当所述起始状态报告之外的其他每个第一状态报告中的所述第三标识为接收到的数据包的序列号时,确定所述其他每个第一状态报告中的起始数据包与前一个状态报告中的最后一个数据包之间的数据包为丢失的数据包,并继续发送所述丢失的数据包中未被重复发送的数据包;或,
    当所述其他每个第一状态报告中的所述第三标识为丢失的数据包的序列号时,确定所述其他每个第一状态报告中的起始数据包与前一个状态报告中的最后一个数据包之间的数据包为收到的数据包,并停止发送所述收到的数据包。
  22. 根据权利要求20所述的设备,其特征在于,所述多个RLC协议数据单元中的起始RLC协议数据单元的所述第一状态报告中的所述第三标识为所述发送端发送给所述接收端的数据包中第一个接收的数据包或第一个丢失的数据包的序列号,所述起始RLC协议数据单元之后的其他所述RLC协议数据单元包括的第一状态报告中的所述第三标识为前一个RLC协议数据单元中第一状态报告指示的最后一个数据包之后的第一个接收的数据包的序列号或第一个丢失的数据包的序列号;所述多个协议RLC数据单元中的每个RLC协议数据单元包含第四标识,其中,所述第四标识用于指示所述每个RLC协议数据单元中的第一状态报告是否是起始状态报告;
    所述确定模块还用于:
    当所述第四标识指示所述第一状态报告是所述起始状态报告,且所述第三标识为丢失的数据包的序列号时,所述发送端确定所述接收端已接收到序列号小于所述起始数据包的数据包,并停止发送所述序列号小于所述起始数据包的数据包;或
    当所述第四标识指示所述第一状态报告是起始状态报告,且所述第三标识为接收到的数据包的序列号时,所述发送端确定所述接收端丢失了序列号小于所述起始数据包的数据包,并继续发送所述序列号小于所述起始数据包 的数据包中未被重复发送的数据包。
PCT/CN2017/070472 2017-01-06 2017-01-06 无线通信的方法和设备 WO2018126450A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/070472 WO2018126450A1 (zh) 2017-01-06 2017-01-06 无线通信的方法和设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/070472 WO2018126450A1 (zh) 2017-01-06 2017-01-06 无线通信的方法和设备

Publications (1)

Publication Number Publication Date
WO2018126450A1 true WO2018126450A1 (zh) 2018-07-12

Family

ID=62788870

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/070472 WO2018126450A1 (zh) 2017-01-06 2017-01-06 无线通信的方法和设备

Country Status (1)

Country Link
WO (1) WO2018126450A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113676844A (zh) * 2021-09-27 2021-11-19 北京星网船电科技有限公司 一种基于北斗短报文的多点数据通信方法及系统
WO2023221117A1 (zh) * 2022-05-20 2023-11-23 北京小米移动软件有限公司 报文接收方法、装置、存储介质及电子设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101296485A (zh) * 2007-04-28 2008-10-29 中兴通讯股份有限公司 状态查询方法和切换方法
CN101753277A (zh) * 2008-12-16 2010-06-23 中兴通讯股份有限公司 无线链路控制层报文状态报告的发送方法
US20100189006A1 (en) * 2009-01-29 2010-07-29 Samsung Electronics Co., Ltd. Method and system for computing and sending resource requests and avoiding deadlock situations in mobile communication system
CN101997660A (zh) * 2009-08-14 2011-03-30 中兴通讯股份有限公司 一种避免上行数据丢失的方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101296485A (zh) * 2007-04-28 2008-10-29 中兴通讯股份有限公司 状态查询方法和切换方法
CN101753277A (zh) * 2008-12-16 2010-06-23 中兴通讯股份有限公司 无线链路控制层报文状态报告的发送方法
US20100189006A1 (en) * 2009-01-29 2010-07-29 Samsung Electronics Co., Ltd. Method and system for computing and sending resource requests and avoiding deadlock situations in mobile communication system
CN101997660A (zh) * 2009-08-14 2011-03-30 中兴通讯股份有限公司 一种避免上行数据丢失的方法及装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113676844A (zh) * 2021-09-27 2021-11-19 北京星网船电科技有限公司 一种基于北斗短报文的多点数据通信方法及系统
WO2023221117A1 (zh) * 2022-05-20 2023-11-23 北京小米移动软件有限公司 报文接收方法、装置、存储介质及电子设备

Similar Documents

Publication Publication Date Title
WO2018202064A1 (zh) 发送数据的方法及其装置
RU2730002C1 (ru) Способ передачи данных, оконечное устройство и сетевое устройство
WO2018202037A1 (zh) 传输数据的方法、终端设备和网络设备
TWI741147B (zh) 傳輸回饋訊息的方法和終端設備
WO2018227555A1 (zh) 用于传输数据的方法、终端设备和网络设备
TWI762702B (zh) 資料傳輸的方法、發射端設備和接收端設備
EP3567930B1 (en) Wireless communication method and device
WO2018145301A1 (zh) 一种传输数据的方法和装置
EP3634076B1 (en) Method and device for processing data
WO2020056608A1 (zh) 用于侧行链路的通信方法和设备
WO2019191912A1 (zh) 数据传输的方法、终端设备和网络设备
WO2018166517A1 (zh) 一种数据传输方法、数据发送设备及数据接收设备
TW201832534A (zh) 用於信息傳輸的方法和設備
US11671870B2 (en) Compression processing method, decompression processing method and related devices
WO2020057044A1 (zh) 一种连接释放方法、数据处理方法、设备及存储介质
WO2019101122A1 (zh) 传输数据的方法和装置
WO2018126450A1 (zh) 无线通信的方法和设备
WO2018120107A1 (zh) 通信方法、网络设备和终端设备
US20130114748A1 (en) Method, Apparatus and Device for Transmitting Data Blocks
JP2022520347A (ja) 無線通信方法及び装置
JP2019504516A (ja) データ伝送方法、端末及び基地局
TW201832503A (zh) 通信方法、終端設備和網絡設備
JP6389126B2 (ja) 無線通信装置及び送信フレーム制御方法
CN111654360B (zh) 一种非激活态的切换处理方法及通信设备
US10009212B2 (en) Method and apparatus for activation and deactivation of radio network functionality

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

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

Country of ref document: EP

Kind code of ref document: A1