WO2018202133A1 - 数据处理方法及设备 - Google Patents

数据处理方法及设备 Download PDF

Info

Publication number
WO2018202133A1
WO2018202133A1 PCT/CN2018/085611 CN2018085611W WO2018202133A1 WO 2018202133 A1 WO2018202133 A1 WO 2018202133A1 CN 2018085611 W CN2018085611 W CN 2018085611W WO 2018202133 A1 WO2018202133 A1 WO 2018202133A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdu
data
scheduling request
sdu
deleting
Prior art date
Application number
PCT/CN2018/085611
Other languages
English (en)
French (fr)
Inventor
王宏
权威
张戬
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2018202133A1 publication Critical patent/WO2018202133A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1854—Scheduling and prioritising arrangements
    • 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/0006—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission format
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1848—Time-out mechanisms
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • 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 processing method and device.
  • LTE Long Term Evolution
  • PDCP Packet Data Convergence Protocol
  • IP Internet Protocol
  • RLC Radio Link Control
  • MAC Media Access Control
  • PHY Physical
  • the data packet In the process of data transmission, the data packet has certain timeliness, such as voice call service, which requires high timeliness of data packets; while web browsing service requires less timeliness of data packets. Therefore, the PDCP layer of the device initiates a timer corresponding to the service characteristics of the PDCP SDU for the PDCP SDU (Service Data Unit (SDU) of the PDCP layer). If the timer expires, the PDCP layer will The PDCP SDU discards and sends an indication message to the RLC layer, instructing the RLC layer to discard the received Protocol Data Unit (PDU) of the PDCP layer (which is obtained by the PDCP layer to encapsulate the PDCP SDU) because the aging requirement is exceeded. After that, it is meaningless to transfer this packet.
  • SDU Service Data Unit
  • the RLC layer has a cascading function, that is, the RLC layer can receive multiple PDCP PDUs from the PDCP layer, and concatenate multiple PDCP PDUs into one RLC PDU; for example, PDCP PDU 3, PDCP PDU 4 and PDCP PDU 5 are cascaded into one RLC PDU. If the RLC layer receives the indication information sent by the PDCP layer, the indication information indicates that the RLC layer discards the PDCP PDU 4. Since the generated RLC PDU includes the PDCP PDU 3 and the PDCP PDU 5 in addition to the PDCP PDU 4, the RLC is included. The PDU will not be discarded, and the RLC layer will normally transmit the RLC PDU, thereby causing the data that does not need to be transmitted to be included in the data packet for transmission, thereby causing waste of wireless communication resources.
  • the embodiment of the present invention provides a data processing method and device, which can delete data that does not need to be transmitted according to different data deletion modes, thereby saving wireless communication resources.
  • an embodiment of the present application provides a data processing method, including:
  • the data deletion manner includes: deleting the SDU, or deleting the first protocol data unit PDU encapsulated by the SDU, or deleting the data domain in the first PDU .
  • the SDU is a radio link control service data unit RLC SDU
  • the PDU is a radio link control protocol data unit RLC PDU.
  • the RLC layer of the device (which may be the user equipment or the network device) receives the RLC SDU from the PDCP layer of the local device, if the RLC layer receives the indication information sent by the PDCP layer to indicate the deletion of the RLC SDU, the RLC layer may The data is deleted according to the above data deletion manner, thereby avoiding the waste of wireless communication resources caused by transmitting data that does not need to be transmitted in the subsequent retransmission process.
  • the first PDU corresponds to only one SDU.
  • the data processing method is only applicable to the case where the RLC layer does not use the cascading manner to generate a PDU. That is, the RLC layer does not concatenate multiple SDUs into one PDU, that is, the first PDU only Corresponds to an SDU.
  • the method further includes:
  • the first PDU is identified as the PDU obtained by the SDU encapsulation by using the first sequence number, so that after the RLC layer receives the indication information for deleting the SDU, the first PDU may be obtained according to the first sequence number. And performing data deletion on the first PDU.
  • the encapsulating the SDU into the first PDU includes:
  • the N sub-packets are encapsulated into N PDUs.
  • the SDU may be segmented into N sub-packets, and then correspondingly encapsulated into N PDUs to make it a data frame suitable for the basic network transmission.
  • the deleting the data field in the first PDU includes:
  • the data fields in the N PDUs are deleted.
  • the RLC layer allocates the first sequence number to the SDU, the N PDUs obtained after the segmentation are identified by the first sequence number, so that all the PDUs whose sequence number is the first sequence number can be obtained. , delete the data fields of these PDUs.
  • the data deletion manner further includes:
  • the PDUs other than the second PDU of the N PDUs are deleted.
  • the method further includes:
  • deleting the first protocol data unit PDU encapsulated by the SDU includes:
  • a third PDU is constructed, the third PDU comprising a third header, the sequence number contained in the third header being the same as the first sequence number.
  • the configured third PDU may only include a packet header, and when the third PDU is retransmitted to the data receiving end, the data receiving end may be correctly completed according to the first sequence number included therein, and At the same time, it is avoided that data that has lost timeliness in the first PDU is retransmitted and wastes wireless communication resources.
  • the deleting data according to the data deletion manner includes:
  • the indication information is used to indicate that the RLC layer deletes the SDU; and when the indication information is received, deleting data according to the data deletion manner; or
  • the data is deleted according to the data deletion manner.
  • the RLC layer may start the timer when the SDU is acquired. If the timer expires, the data deletion operation is performed to prevent the data from being deleted in time due to the above delay.
  • the method further includes:
  • the status report including the first serial number.
  • the device may generate the first PDU for instructing to avoid the first PDU when the data receiving end performs data packet sorting.
  • deleting the first protocol data unit PDU encapsulated by the SDU includes:
  • the method further includes:
  • the status report including the first serial number.
  • the device may generate a status report for indicating that the N PDUs are deleted, in order to prevent the data receiving end from performing data packet sorting and continuously waiting for the N PDUs. Send the status report to the data receiver.
  • the status report further includes indication information used to indicate that the status report is a control PDU of an RLC layer;
  • the status includes further including a bitmap, where the bitmap is used to indicate whether a PDU adjacent to the first PDU is deleted;
  • the status report further includes a value for indicating the number of consecutively deleted PDUs including the first PDU.
  • the status report can be set such that the status report can inform the data receiving end that more than one PDU is deleted.
  • the data deletion method further includes: deleting the SDU;
  • the method further includes:
  • the method further includes:
  • the SDU is deleted before being encapsulated into a PDU, and the sequence number assigned to the SDU may be reassigned to the next SDU, or a PDU containing only the header may be generated for the serial number to maintain the serial number consecutively. It is beneficial for data receivers to sort packets.
  • an embodiment of the present application provides a data processing method, including:
  • the sequence number included in the status report is the first sequence number, it is determined that the PDU whose sequence number is the first sequence number is received.
  • an embodiment of the present application provides a data processing method, including:
  • the PDUs of the M RLC layers are deleted, and the PDU whose sequence number is the first sequence number is determined to be received.
  • the embodiment of the present application provides a network device, including:
  • An acquiring unit configured to acquire a service data unit SDU of a radio link control RLC layer
  • a deleting unit configured to delete data according to a data deletion manner, where the data deletion manner includes: deleting the SDU obtained by the acquiring unit, or deleting the first protocol data unit PDU encapsulated by the SDU, or Deleting the data field in the first PDU.
  • the network device provided by the present application may include a unit for performing the steps in the above method design.
  • the unit may be software and/or hardware.
  • the network device provided by the application includes a processor and a transceiver, and the processor is configured to support the network device to perform a corresponding function in the foregoing method.
  • the transceiver is configured to support communication between the network device and the terminal, and send information or messages involved in the foregoing method to the terminal.
  • the network device can also include a memory for coupling with the processor that holds program messages and data necessary for the network device.
  • a communication interface may also be included in the network device for communicating with other network devices.
  • an embodiment of the present application provides a terminal, including:
  • An acquiring unit configured to acquire a service data unit SDU of a radio link control RLC layer
  • a deleting unit configured to delete data according to a data deletion manner, where the data deletion manner includes: deleting the SDU obtained by the acquiring unit, or deleting the first protocol data unit PDU encapsulated by the SDU, or Deleting the data field in the first PDU.
  • the terminal provided by the present application may include a unit for performing the steps in the above method design.
  • the unit may be software and/or hardware.
  • the structure of the terminal provided by the application includes a processor and a transceiver, and the processor is configured to support the terminal to perform a corresponding function in the foregoing method.
  • the transceiver is configured to support communication between the access network device and the terminal, and send information or a message involved in the foregoing method to the access network device.
  • the terminal may also include a memory for coupling with the processor, which stores program messages and data necessary for the terminal.
  • an embodiment of the present application provides a computer program product comprising a message, when executed on a computer, causing a computer to perform the method described in the above aspects.
  • an embodiment of the present application provides a computer readable storage medium, wherein the computer readable storage medium stores a message, and when executed on a computer, causes the computer to perform the method described in the above aspects.
  • the embodiment of the present application further provides a computer program product comprising instructions, which when executed, perform the method described in the above aspects.
  • the radio link control layer of the device can delete data that does not need to be transmitted according to different data deletion modes, thereby saving wireless communication resources.
  • FIG. 1A is a schematic diagram of an application scenario of a communication system according to an embodiment of the present application.
  • FIG. 1B is a schematic diagram of interaction of a user plane protocol stack according to an embodiment of the present application.
  • 1C is a schematic diagram of interaction between a PDCP layer and an RLC layer according to an embodiment of the present disclosure
  • FIG. 1D is a schematic structural diagram of an RLC PDU according to an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a data processing method disclosed in an embodiment of the present application.
  • FIG. 3 is a schematic flowchart of another data processing method disclosed in an embodiment of the present application.
  • FIG. 5 is a schematic flowchart diagram of still another data processing method disclosed in the embodiment of the present application.
  • FIG. 6A is a schematic flowchart diagram of still another data processing method according to an embodiment of the present application.
  • 6B is a schematic diagram of a status report format disclosed in an embodiment of the present application.
  • 6C is a schematic diagram of another status report format disclosed in an embodiment of the present application.
  • 6D is a schematic diagram of still another status report format disclosed in the embodiment of the present application.
  • FIG. 7 is a schematic diagram of another application scenario of a communication system according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic flow chart of still another data processing method disclosed in the embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of a device 900 according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of a base station 1000 according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of a terminal 1100 according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic diagram of an application scenario of a communication system according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic diagram of a configuration of a scheduling request resource according to an embodiment of the present application.
  • FIG. 14 is a schematic diagram of another scheduling request resource according to an embodiment of the present disclosure.
  • FIG. 15 is a schematic diagram of a scheduling request repeated transmission according to an embodiment of the present disclosure.
  • 16 is a schematic diagram of conflicting scheduling requests according to an embodiment of the present application.
  • FIG. 17 is a schematic flowchart of a method for sending a scheduling request according to an embodiment of the present disclosure
  • FIG. 18 is a schematic diagram of still another scheduling request sending method according to an embodiment of the present disclosure.
  • FIG. 19 is a schematic diagram of still another scheduling request sending method according to an embodiment of the present disclosure.
  • FIG. 20 is a schematic diagram of still another scheduling request sending method according to an embodiment of the present disclosure.
  • FIG. 21 is a schematic flowchart of a method for receiving a scheduling request according to an embodiment of the present disclosure
  • FIG. 22 is a schematic structural diagram of a terminal device according to an embodiment of the present disclosure.
  • FIG. 23 is a schematic structural diagram of a network device according to an embodiment of the present disclosure.
  • FIG. 24 is another schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 25 is still another schematic block diagram of a network device according to an embodiment of the present application.
  • FIG. 1A is a schematic diagram of an application scenario of a communication system according to an embodiment of the present application.
  • the communication system can be applied to an LTE network or a 5G network.
  • the user terminal accesses the core network through an evolved Node B (eNB), and implements data transmission and reception by interacting with the eNB.
  • eNB evolved Node B
  • the base station can also be a 5G base station gNB.
  • the foregoing user equipment may be a mobile phone, a smart terminal, a multimedia device, a streaming media device, etc., and is not limited in this embodiment.
  • the eNB is a bridge between the user terminal in the LTE network and the Evolved Packet Core (EPC).
  • the eNBs are connected through the X2 interface.
  • the main functions are: radio resource management, IP header compression, and User data stream encryption, Mobility Management Entity (MME) selection when user terminal is attached, routing of user plane data to Serving Gateway (S-GW), organization and transmission of paging messages, broadcast messages Organization and transmission, measurement and measurement report configuration for mobility or scheduling purposes.
  • MME Mobility Management Entity
  • FIG. 1B is a schematic diagram of interaction of a user plane protocol stack according to an embodiment of the present application.
  • user plane data is transmitted between a user equipment and a network device in an IP packet format via a PDCP layer, an RLC layer, a MAC layer, and a PHY layer.
  • the arrows in the figure indicate the flow of data packets when the user equipment sends data to the eNB.
  • the data packets generally need to pass through the PDCP layer, the RLC layer, the MAC layer, and the PHY layer layer by layer. It can be understood that when the eNB sends data to the user equipment, the transmission of the data packet flows in the reverse direction.
  • the IP data packet is transmitted from the PDCP layer of the device to the RLC layer of the device, if the PDCP layer sends indication information to the RLC layer to instruct the RLC layer to discard the lost time-sensitive data packet, and the RLC layer transmits the data packet to the other After the data packets are encapsulated into one RLC PDU (that is, the PDU of the RLC layer), the RLC layer cannot perform the operation of discarding the data packet, and the RLC PDU carrying the data packet is normally transmitted, thereby causing waste of wireless communication resources.
  • FIG. 1C is a schematic diagram of interaction between a PDCP layer and an RLC layer according to an embodiment of the present application.
  • the PDCP layer sends a PDCP PDU 4 (ie, a PDU of a PDCP layer having a Sequence Number (SN) of 4) to the RCL layer.
  • the RCL layer allocates a sequence number 8 of the RLC layer to the RCL layer.
  • the data packet is encapsulated into an RLC PDU8 (ie, a PDU of the RLC layer with a serial number of 8).
  • FIG. 1D is a schematic structural diagram of an RLC PDU according to an embodiment of the present disclosure.
  • the structure of the RLC PDU includes a packet header and a data domain. .
  • the RLC layer transmits the encapsulated RLC PDU 8 to the MAC layer of the device.
  • the RLC layer will send ACK information to the MAC layer that has not received feedback from the data receiver (the ACK information indicates that the data receiver successfully received a certain data packet)
  • the RLC PDU 8 is saved to the retransmission memory.
  • the PDCP layer of the device indicates to the RLC layer to discard the PDCP PDU8 at this time, when the RLC layer does not cascade the RLC SDU, one RLC PDU corresponds to only one RLC SDU, and the following FIG. 2 can be applied.
  • the method of Figure 6D and Figure 8 performs a data deletion operation.
  • the RLC SDU may also lose the timeliness.
  • the PDCP layer sends the PDCP PDU 1 and the PDCP PDU 2 (corresponding to the RLC SDU 5 and the RLC SDU 6 respectively) to the RLC layer, and the RLC SDU 6 corresponds to the PDCP PDU 1 corresponding to the RLC SDU 6 in the process of transmitting the RLC SDU 5 to the opposite end.
  • the timer expires.
  • the PDCP layer indicates that the PDCP PDU 1 is discarded, that is, the RLC SDU 5 is discarded. It can be seen that in this case, the RLC PDU corresponding to the RLC SDU 6 is not sent to the MAC layer, and is not stored in the retransmission memory. In this case, the following methods are equally applicable.
  • the indication information of the PDCP layer is received, and the indication is corresponding.
  • the PDCP PDU is discarded.
  • the present invention is also applicable to Unacknowledged Mode (UM).
  • UM Unacknowledged Mode
  • FIG. 2 is a schematic flowchart diagram of a data processing method disclosed in an embodiment of the present application.
  • the executor of the data processing method may be a user terminal or a network device.
  • the embodiment of the present application is described by taking a user terminal as an example.
  • the RLC layer of the user terminal receives the PDCP PDU 4 transmitted by the PDCP layer of the user terminal, and after the PDCP PDU arrives at the RLC layer, it is called an RLC SDU.
  • the RLC layer may directly delete the RLC SDU 8 and then generate the RLC PDU 8.
  • the foregoing SDU is encapsulated into a first PDU, where the first PDU includes a data field and a first packet header, and the first packet header includes a first sequence number.
  • the RLC layer saves the RLC PDU 8 sent to the MAC layer of the local device and does not receive the ACK information fed back by the data receiver (such as the network device) into the retransmission memory. It is optional to save the data packet in the retransmission memory, that is, in the RLC UM mode, after transmitting the data packet (such as the above RLC PDU 8) to the MAC layer, it is not necessary to store the data packet. Alternatively, in the RLC AM mode, a data packet (such as the RLC PDU 8 described above) may be discarded before being sent to the MAC layer.
  • the indication information indicates that the RLC layer deletes the PDCP PDU 4 (since the PDCP layer is set for the PDCP PDU 4) If the timer expires, indicating that the PDCP PDU 4 has lost the timeliness, the RLC layer searches the retransmission memory for the RLC PDU 8 obtained by encapsulating the PDCP PDU 4 according to the sequence number, and deletes the data field of the RLC PDU 8 only The header of the RLC PDU8 is reserved.
  • the indication information indicates that the RLC layer deletes the PDCP PDU 4, and the RLC layer sets the RLC PDU 8 The data field is deleted, and only the header of the RLC PDU 8 is reserved.
  • the indication information indicates that the RLC layer deletes the PDCP PDU 4, and the RLC layer deletes the PDCP PDU 4. And generating a header of the RLC PDU 8 corresponding to the PDCP PDU 4.
  • the RLC layer of the user equipment retransmits only the RLC PDU 8 of the packet header, avoids retransmitting the data that has lost time (ie, the data domain part), and saves wireless communication resources.
  • FIG. 3 is a schematic flowchart diagram of still another data processing method disclosed in the embodiment of the present application.
  • the RLC layer of the user terminal receives the PDCP PDU 4 transmitted by the PDCP layer of the user terminal, and after the PDCP PDU arrives at the RLC layer, it is called an RLC SDU.
  • the RLC layer of the user terminal allocates the sequence number 8 of the RLC layer to the RLC SDU.
  • the RLC SDU Before the RLC SDU is encapsulated into an RLC PDU, if the data contained in the RLC SDU is too long and the data packet is too large, the RLC SDU needs to be segmented into N sub-packets (N is greater than or equal to 2), and then encapsulated separately. Sub-package. It should be noted that the sequence number of the RLC layer of the N sub-packets after the PDCP PDU 4 segmentation is 8.
  • the indication information indicates that the RLC layer deletes the PDCP PDU 4 (since the PDCP layer is set to the PDCP PDU 4)
  • the timer expires, indicating that the PDCP PDU 4 has lost the timeliness; and the RLC layer searches for the RLC PDU with the RLC layer sequence number 8 (ie, the above N RLC PDUs) in the retransmission memory according to the sequence number, and the above N
  • the data fields of the RLC PDUs are deleted, and only the headers of the N RLC PDUs are reserved.
  • the indication information indicates that the RLC layer deletes the PDCP PDU 4, and the RLC layer will have N
  • the data field of the RLC PDU8 is deleted, and only the headers of the N RLC PDUs 8 are reserved.
  • the RLC layer of the user equipment retransmits only the N PDUs of the packet header, avoiding retransmission of data that has lost time (ie, the data domain portion of the N PDUs), and saving wireless communication resources.
  • FIG. 4 is a schematic flowchart diagram of still another data processing method disclosed in the embodiment of the present application.
  • the RLC layer of the user equipment may delete the N RLC PDUs encapsulated into pieces into only one RLC PDU, and the remaining data fields of the RLC PDU are also The deletion is performed, so that only the header of the remaining RLC PDU needs to be transmitted during retransmission, thereby achieving the purpose of saving wireless communication resources.
  • the RLC layer of the user equipment may randomly select one PDU from the N PDUs as the second PDU.
  • the RLC layer may select one PDU with the smallest header as the second PDU from the N PDUs, so that if the packet header of the second PDU is only retransmitted during retransmission, the wireless communication may be further reduced.
  • the consumption of resources may be selected one PDU with the smallest header as the second PDU from the N PDUs, so that if the packet header of the second PDU is only retransmitted during retransmission, the wireless communication may be further reduced. The consumption of resources.
  • the indication information indicating whether the second PDU is segmented in the second header of the second PDU is modified to indicate The second PDU is not segmented.
  • the second header of the second PDU is deleted to indicate a segmentation offset (SO). Field.
  • the foregoing method may be further applicable to: when a part of the RLC PDUs 8 of the N RLC PDUs 8 are sent to the MAC layer, the RLC layer receives the indication information of the PDCP, indicating that the PDCP PDU 4 is discarded. The RLC layer processes another part of the RLC PDU 8 corresponding to the PDCP PDU 4 that has not been sent to the MAC layer. The processing is as follows:
  • Manner 1 Delete this part of the RLC PDU 8 that is not sent to the MAC layer, and generate an RLC PDU 8 that only contains the RLC PDU header, that is, an RLC PDU with a sequence number of 8.
  • Manner 2 In this part of the RLC PDU 8 that is not sent to the MAC layer, one RLC PDU 8 is randomly selected as the third PDU, and the other RLC PDUs 8 are deleted, and the data field of the third PDU is deleted. Other similar steps are as described above.
  • the data packet may be sorted according to the sequence number included in the packet header.
  • FIG. 5 is a schematic flowchart diagram of still another data processing method disclosed in the embodiment of the present application.
  • the steps 501-504 reference may be made to the description of the steps 201-204 in FIG. 2, and the embodiments of the present application are not described herein.
  • the method described in FIG. 5 deletes the entire first PDU, and reconstructs a third PDU that does not contain a data domain or a data domain to replace the first PDU, thereby To save the role of wireless communication resources.
  • the foregoing SDU is encapsulated into a first PDU, where the first PDU includes a data field and a first packet header, and the first packet header includes a first sequence number.
  • the RLC layer may store the first PDU into the retransmission memory.
  • the RLC layer constructs a third PDU, and the third PDU does not include a data field, and at least includes a sequence number, and the sequence number is the same as the first sequence number.
  • the third PDU is transmitted instead of the first PDU, thereby avoiding the transmission of redundant data and saving the wireless communication resources.
  • FIG. 6A is a schematic flowchart diagram of still another data processing method according to an embodiment of the present application.
  • the implementation of the steps 601-604 may refer to the description of the steps 201-204 in FIG. 2, and the embodiments of the present application are not described herein.
  • the foregoing SDU is encapsulated into a first PDU, where the first PDU includes a data field and a first packet header, and the first packet header includes a first sequence number.
  • the RLC layer may store the first PDU into the retransmission memory.
  • the user terminal sends the status report to the data receiver, and when the data receiver performs the data packet sorting, according to the status report, the deleted data packet can be skipped and the data packet is sorted normally.
  • FIG. 6B is a schematic diagram of a status report format disclosed in an embodiment of the present application.
  • the status report includes at least a D/C field for indicating that the status report is an RLC control PDU; in addition, a sequence number Discard SN field for indicating the discarded data packet is included.
  • the status report further includes a PDU Type field, which is used to indicate that the RLC control PDU is a status report, and more specifically, for indicating The RLC Control PDU is a status report of dropped packets.
  • FIG. 6C is a schematic diagram of another status report format disclosed in the embodiment of the present application.
  • the status report may further include a bitmap for indicating the start of the data packet with the sequence number Discard SN or the serial number. For the next packet of the Discard SN, which packets are dropped (ie deleted) and which packets are not discarded.
  • bitmap 100100
  • a PDU Type field may be further included to indicate that the RLC Control PDU is a status report, and more specifically, to indicate that the RLC Control PDU is a status report of a dropped data packet.
  • FIG. 6D is a schematic diagram of still another status report format disclosed in the embodiment of the present application.
  • the status report may further include a number field for indicating the start of the data packet with the serial number of Discard SN (or from Discard). The next packet of the SN packet begins with the number of consecutively dropped packets.
  • the RLC layer as the data sender's device uses the status report to indicate the discarded RLC SDU or RLC PDU.
  • the data receiver receives the status report, it will not wait for the discarded data packet, and can perform normal packet ordering. .
  • a PDU Type field may be further included to indicate that the RLC Control PDU is a status report, and more specifically, to indicate that the RLC Control PDU is a status report of a dropped data packet.
  • FIG. 7 is a schematic diagram of another application scenario of a communication system according to an embodiment of the present application.
  • the physical component of the network device is a CU-DU architecture.
  • the PDCP layer may be located in a centralized unit (CU), and the RLC layer, the MAC layer, and the PHY layer are located in a DU (Distributed Unit, Distributed unit).
  • CU Centralized Unit
  • DU Distributed Unit
  • FIG. 8 is a schematic flowchart diagram of still another data processing method disclosed in the embodiment of the present application.
  • the CU sends a PDCP PDU to the DU, and the PDCP PDU is also called an RLC SDU.
  • an RLC SDU After the PDCP PDU arrives at the RLC layer in the DU, it is called an RLC SDU.
  • the DU starts a timing operation when receiving the RLC SDU.
  • a timer for the RLC PDU is set at the RLC layer, and a timer for the RLC PDU is started when the DU receives the RLC SDU.
  • the DU may also start a timing operation when the foregoing RLC SDU is encapsulated into an RLC PDU.
  • the RLC layer in the DU encapsulates the RLC SDU or the RLC SDU into an RLC PDU for data deletion.
  • the RLC layer in the DU deletes the RLC PDU corresponding to the RLC SDU or the RLC SDU.
  • the foregoing preset time threshold is determined according to characteristics such as timeliness requirements of data included in the RLC SDU. For example, if the data included in the RLC SDU is voice service data, and the timeliness requirement is strong, the preset time threshold should be set to be short; if the data included in the RLC SDU is web browsing service data, the time limit is If the sexual requirements are weak, the above preset time threshold should be set longer.
  • the data deletion manner in step 703 may refer to the operations performed on the RLC PDU in FIG. 2 to FIG. 5.
  • the RLC layer has not yet encapsulated the RLC SDU into an RLC PDU, the RLC SDU is directly deleted.
  • the delay of data transmission between the CU and the DU can be avoided, so that the RLC layer in the DU cannot perform the data deletion operation in time.
  • the RLC layer of the base station is according to any of the above-mentioned FIG. 2 to FIG. 6D and FIG.
  • the data packet obtained after the data processing is represented by the MAC layer, the PHY layer and the communication link arrives at the user terminal as the data receiver.
  • the RLC layer of the user terminal receives the RLC PDU or status report, as follows:
  • Case 1 When the RLC layer receives the RLC PDU with sequence number x and the data field of the RLC PDU is empty, the RLC layer considers (or determines) that the RLC PDU (or SDU) with the sequence number x is received, no longer Waiting for the PDU with the sequence number x, and receiving the PDU whose sequence number is not equal to x, or not feeding back the PDU with the sequence number x in the status report generating the feedback to the data sender.
  • Case 2 The RLC entity receives the RLC PDU with the sequence number x, and the RLC entity has received several RLC PDUs with sequence number x before receiving the RLC PDU, if the data field of the RLC PDU received at this time Empty, that is, the RLC entity deletes all data in the RLC PDU or RLC PDU with sequence number x, and considers (or determines) that the RLC SDU with sequence number x is received.
  • Case 3 The RLC entity receives the status report, and the RLC entity parses the status report to obtain the information that the data packet with the sequence number x is discarded, and considers (or determines) that the data packet x indicated in the status report is received.
  • FIG. 9 is a schematic structural diagram of a device 900 according to an embodiment of the present application.
  • the device 900 may include an obtaining unit 901 and a deleting unit 902.
  • the obtaining unit 901 is configured to acquire a service data unit SDU of the radio link control RLC layer.
  • the deleting unit 902 is configured to delete the data according to the data deletion manner, where the data deletion manner includes: deleting the SDU obtained by the acquiring unit, or deleting the first protocol data unit PDU encapsulated by the SDU, or The data field in the PDU is deleted.
  • each of the above units may also correspond to the corresponding description of the method embodiments shown in FIG. 2 to FIG. 6D and FIG.
  • the radio link control layer of the device 900 can delete data that does not need to be transmitted according to different data deletion modes, thereby saving wireless communication resources.
  • FIG. 10 is a schematic structural diagram of a base station 1000 according to an embodiment of the present application.
  • Base station 1000 can perform the operations in the methods of Figures 2 through 6D and Figure 8.
  • the base station 1000 includes one or more remote radio units (RRUs) 1001 and one or more baseband units (BBUs) 1002.
  • the RRU 1001 described above may be referred to as a transceiver unit, a transceiver, a transceiver circuit, or a transceiver, etc., which may include at least one antenna 1011 and a radio frequency unit 1012.
  • the RRU1001 part is mainly used for transmitting and receiving radio frequency signals and converting radio frequency signals and baseband signals.
  • the above BBU 1002 part is mainly used for performing baseband processing, controlling a base station, and the like.
  • the RRU 1001 and the BBU 1002 may be physically disposed together or physically separated, that is, distributed base stations.
  • the BBU 1002 is a control center of a base station, and may also be referred to as a processing unit, and is mainly used to perform baseband processing functions such as channel coding, multiplexing, modulation, spreading, and the like.
  • the above BBU processing unit
  • the BBU 1002 may be configured by one or more boards, and multiple boards may jointly support a single access standard radio access network (such as an LTE network), or may support different access modes of the wireless connection. Network access.
  • the BBU 1002 described above also includes a memory 1021 and a processor 1022.
  • the above memory 1021 is used to store necessary messages and data.
  • the processor 1022 is configured to control the base station to perform necessary operations, such as controlling the base station to perform the processes shown in FIG. 2 to FIG. 6D and FIG.
  • the above memory 1021 and processor 1022 can serve one or more boards. That is, the memory and processor can be individually set on each board. It is also possible that multiple boards share the same memory and processor.
  • the necessary circuits are also provided on each board.
  • FIG. 11 is a schematic structural diagram of a terminal 1100 according to an embodiment of the present application.
  • the terminal can perform the operations of the terminals in the methods illustrated in FIGS. 2 to 6D and 8.
  • FIG. 11 shows only the main components of the terminal.
  • the terminal 1100 includes a processor, a memory, a control circuit, an antenna, and an input and output device.
  • the processor is mainly used for processing the communication protocol and the communication data, and controlling the entire user equipment, executing the software program, and processing the data of the software program, for example, for supporting the terminal to execute the processes described in FIG. 2 to FIG. 6D and FIG. .
  • Memory is primarily used to store software programs and data.
  • the control circuit is mainly used for converting baseband signals and radio frequency signals and processing radio frequency signals.
  • the control circuit together with the antenna can also be called a transceiver, and is mainly used for transmitting and receiving RF signals in the form of electromagnetic waves.
  • the terminal 1100 also has input and output devices, such as a touch screen, a display screen, a keyboard, and the like, which are mainly used for receiving data input by a user and outputting data to the user.
  • the processor can read the software program in the storage unit, interpret and execute the software program, and process the data of the software program.
  • the processor performs baseband processing on the data to be sent, and then outputs the baseband signal to the radio frequency circuit.
  • the radio frequency circuit performs radio frequency processing on the baseband signal, and then sends the radio frequency signal to the outside through the antenna in the form of electromagnetic waves.
  • the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor, which converts the baseband signal into data and processes the data.
  • FIG. 11 shows only one memory and processor for ease of illustration. In an actual terminal, there may be multiple processors and memories.
  • the memory may also be referred to as a storage medium or a storage device, and the like.
  • the processor may include a baseband processor and a central processing unit, and the baseband processor is mainly used to process communication protocols and communication data, and the central processing unit is mainly used to control the entire terminal and execute the software.
  • the processor in FIG. 11 integrates the functions of the baseband processor and the central processing unit.
  • the baseband processor and the central processing unit can also be independent processors and interconnected by technologies such as a bus.
  • the terminal may include multiple baseband processors to accommodate different network standards.
  • the terminal may include multiple central processors to enhance its processing capabilities, and various components of the terminal may be connected through various buses.
  • the above baseband processor can also be expressed as a baseband processing circuit or a baseband processing chip.
  • the central processing unit described above can also be expressed as a central processing circuit or a central processing chip.
  • the functions of processing the communication protocol and the communication data may be built in the processor, or may be stored in the storage unit in the form of a software program, and the processor executes the software program to implement the baseband processing function.
  • the antenna and control circuit having the transceiving function can be regarded as the transceiving unit 1101 of the terminal 1100, and the processor having the processing function is regarded as the processing unit 1102 of the terminal 1100.
  • the terminal 1100 includes a transceiver unit 1101 and a processing unit 1102.
  • the transceiver unit can also be referred to as a transceiver, a transceiver, a transceiver, and the like.
  • the device for implementing the receiving function in the transceiver unit 1101 can be regarded as a receiving unit, and the device for implementing the sending function in the transceiver unit 1101 is regarded as a sending unit, that is, the transceiver unit 1101 includes a receiving unit and a sending unit.
  • the receiving unit may also be referred to as a receiver, a receiver, a receiving circuit, etc.
  • the transmitting unit may be referred to as a transmitter, a transmitter, or a transmitting circuit or the like.
  • the radio link control layer of the terminal 1100 can delete data that does not need to be transmitted according to different data deletion modes, thereby saving wireless communication resources.
  • the embodiment of the present application discloses a scheduling request sending method and device, where the method includes: the terminal device receives a scheduling request configuration message sent by the network device, where the configuration message includes a repeated sending duration of the scheduling request, and a scheduling request resource period.
  • the scheduling request prohibits the timer duration; the terminal device repeatedly sends the first scheduling request and the second scheduling request according to the scheduling request configuration message, where the terminal device starts the repeating transmission of the first scheduling request.
  • the scheduling request prohibition timer the terminal device sends the second scheduling request after the scheduling request prohibition timer expires, and after the first scheduling request is sent.
  • a scheduling request sending method comprising:
  • the terminal device receives a scheduling request configuration message sent by the network device, where the configuration message includes a repetition sending duration of the scheduling request, a scheduling request resource period, and a scheduling request prohibiting timer duration;
  • the terminal device repeatedly sends the first scheduling request and the second scheduling request according to the scheduling request configuration message, where the terminal device starts the scheduling request prohibiting timer when starting to repeatedly send the first scheduling request, After the scheduling request prohibition timer expires, the terminal device sends the second scheduling request after the first scheduling request is sent.
  • the repeated transmission duration is less than or equal to the scheduling request prohibition timer duration.
  • the repeated transmission duration is greater than the scheduling request prohibition timer duration
  • the terminal device sends the second scheduling request after the first scheduling request is sent, including:
  • the terminal device abandons the use of the scheduling request resource that occurs when the first scheduling request is repeatedly sent to send the scheduling request; or the terminal device sends the first scheduling request within the scheduling request prohibiting timer duration and Or the second scheduling request; or the media access control layer of the terminal device discards the sending of the scheduling request to the physical layer when the physical layer repeatedly sends the first scheduling request.
  • the prohibition timer duration is a product of the scheduling request resource period and a non-negative integer
  • the scheduling request resource period includes a first scheduling request resource period and a The second scheduling request resource period, where the first scheduling request resource period is greater than the second scheduling request resource period, the non-negative integer includes a first non-negative integer and a second non-negative integer, the first non-negative An integer is greater than the second non-negative integer;
  • the duration of the repeated transmission is less than or equal to the duration of the scheduling request prohibition timer, including:
  • the scheduling request prohibiting timer duration is a product of the first scheduling request resource period and the non-negative integer; or the scheduling request prohibiting timer duration is the prohibit timer duration and the first non-negative The product of integers.
  • a scheduling request receiving method comprising:
  • the network device sends a scheduling request configuration message to the terminal device, where the configuration message includes a repetition sending duration of the scheduling request, a scheduling request resource period, and a scheduling request prohibiting timer duration;
  • the network device receives, according to the scheduling request configuration message, a first scheduling request and a second scheduling request that are repeatedly sent by the terminal device, where the repeated sending duration is less than or equal to the scheduling request prohibiting timer duration.
  • the prohibition timer duration is a product of the scheduling request resource period and a non-negative integer
  • the scheduling request resource period includes a first scheduling request resource period and a The second scheduling request resource period, where the first scheduling request resource period is greater than the second scheduling request resource period, the non-negative integer includes a first non-negative integer and a second non-negative integer, the first non-negative An integer is greater than the second non-negative integer;
  • the duration of the repeated transmission is less than or equal to the duration of the scheduling request prohibition timer, including:
  • the scheduling request prohibiting timer duration is a product of the first scheduling request resource period and the non-negative integer; or the scheduling request prohibiting timer duration is the prohibit timer duration and the first non-negative The product of integers.
  • a terminal device comprising:
  • the receiving unit is configured to receive a scheduling request configuration message sent by the network device, where the configuration message includes a repetition sending duration of the scheduling request, a scheduling request resource period, and a scheduling request prohibiting timer duration;
  • the sending unit is configured to repeatedly send the first scheduling request and the second scheduling request according to the scheduling request configuration message, where the sending unit starts the scheduling request prohibiting timing when starting to repeatedly send the first scheduling request.
  • the sending unit sends the second scheduling request after the scheduling request prohibition timer expires, and after the first scheduling request is sent.
  • the repeated transmission duration is less than or equal to the scheduling request prohibition timer duration.
  • the repeated transmission duration is greater than the scheduling request prohibition timer duration
  • the sending unit sends the second scheduling request after the first scheduling request is sent, including:
  • the prohibition timer duration is a product of the scheduling request resource period and a non-negative integer
  • the scheduling request resource period includes a first scheduling request resource period and a The second scheduling request resource period, where the first scheduling request resource period is greater than the second scheduling request resource period, the non-negative integer includes a first non-negative integer and a second non-negative integer, the first non-negative An integer is greater than the second non-negative integer;
  • the duration of the repeated transmission is less than or equal to the duration of the scheduling request prohibition timer, including:
  • the scheduling request prohibiting timer duration is a product of the first scheduling request resource period and the non-negative integer; or the scheduling request prohibiting timer duration is the prohibit timer duration and the first non-negative The product of integers.
  • a network device comprising:
  • the sending unit is configured to send a scheduling request configuration message to the terminal device, where the configuration message includes a repetition sending duration of the scheduling request, a scheduling request resource period, and a scheduling request prohibiting timer duration;
  • the receiving unit is configured to receive, according to the scheduling request configuration message, a first scheduling request and a second scheduling request that are repeatedly sent by the terminal device, where the repeated sending duration is less than or equal to the scheduling request prohibiting timer duration.
  • the prohibition timer duration is a product of the scheduling request resource period and a non-negative integer
  • the scheduling request resource period includes a first scheduling request resource period and a The second scheduling request resource period, where the first scheduling request resource period is greater than the second scheduling request resource period, the non-negative integer includes a first non-negative integer and a second non-negative integer, the first non-negative An integer is greater than the second non-negative integer;
  • the duration of the repeated transmission is less than or equal to the duration of the scheduling request prohibition timer, including:
  • the scheduling request prohibiting timer duration is a product of the first scheduling request resource period and the non-negative integer; or the scheduling request prohibiting timer duration is the prohibit timer duration and the first non-negative The product of integers.
  • a user equipment (or a terminal device) needs to send uplink data to an evolved Node B (eNB)
  • the UE needs to request resources from the eNB, that is, send the buffer to the eNB.
  • a Buffer Status Report (BSR) is used to indicate the current amount of data of the UE. If the UE does not send the resources of the BSR at this time, the UE needs to send a Scheduling Request (SR) to the eNB to request the eNB to send the resources of the BSR.
  • SR Scheduling Request
  • the eNB configures resources for each UE to send SRs.
  • the UE can transmit the completed SR in one subframe, and in the Machine Type Communication (MTC), the UE is in a region with poor signal coverage, and the UE It is necessary to repeatedly send an SR to the eNB.
  • MTC Machine Type Communication
  • the UE if the UE does not receive the resource allocation message of the eNB after the SR is repeatedly transmitted, the UE sends a new SR to the eNB again when the SR resource occurs, if the UE repeats
  • the time for sending the SR is longer than the period of the SR resource, or the time for the UE to repeatedly send the SR is longer than the interval for the eNB to allow the UE to send the SR. If the UE does not send the previous SR, the new SR will be triggered.
  • the SR sends a collision and reduces the success rate of the eNB receiving the SR.
  • the embodiment of the present application provides a method and a device for sending a scheduling request.
  • the collision of the scheduling request can be avoided, and the success rate of receiving the scheduling request is improved.
  • the embodiment of the present application provides a scheduling request sending method, including:
  • the terminal device receives a scheduling request configuration message sent by the network device, where the configuration message includes a repetition sending duration of the scheduling request, a scheduling request resource period, and a scheduling request prohibiting timer duration;
  • the terminal device repeatedly sends the first scheduling request and the second scheduling request according to the scheduling request configuration message, where the terminal device starts the scheduling request prohibiting timer when starting to repeatedly send the first scheduling request, After the scheduling request prohibition timer expires, the terminal device sends the second scheduling request after the first scheduling request is sent.
  • the repeated transmission duration is less than or equal to the scheduling request prohibition timer duration.
  • the repeated transmission duration is greater than the scheduling request prohibition timer duration; after the scheduling request prohibition timer expires, and after the first scheduling request is sent, the terminal device Sending the second scheduling request includes:
  • the terminal device abandons using a scheduling request resource that occurs when the first scheduling request is repeatedly sent to send a scheduling request
  • the repeated transmission duration is greater than the scheduling request prohibition timer duration; after the scheduling request prohibition timer expires, and after the first scheduling request is sent, the terminal device Sending the second scheduling request includes:
  • the terminal device sends the first scheduling request and/or the second scheduling request within the scheduling request prohibiting timer duration;
  • the repeated transmission duration is greater than the scheduling request prohibition timer duration; after the scheduling request prohibition timer expires, and after the first scheduling request is sent, the terminal device Sending the second scheduling request includes:
  • the medium access control layer of the terminal device abandons sending a scheduling request to the physical layer when the physical layer repeatedly sends the first scheduling request.
  • the forbidden timer duration is a product of the scheduling request resource period and a non-negative integer, where the scheduling request resource period includes a first scheduling request resource period and a second scheduling request resource period, The first scheduling request resource period is greater than the second scheduling request resource period, the non-negative integer includes a first non-negative integer and a second non-negative integer, and the first non-negative integer is greater than the second Non-negative integer;
  • the duration of the repeated transmission is less than or equal to the duration of the scheduling request prohibition timer, including:
  • the scheduling request prohibiting timer duration is a product of the first scheduling request resource period and the non-negative integer
  • the forbidden timer duration is a product of the scheduling request resource period and a non-negative integer, where the scheduling request resource period includes a first scheduling request resource period and a second scheduling request resource period, The first scheduling request resource period is greater than the second scheduling request resource period, the non-negative integer includes a first non-negative integer and a second non-negative integer, and the first non-negative integer is greater than the second Non-negative integer;
  • the duration of the repeated transmission is less than or equal to the duration of the scheduling request prohibition timer, including:
  • the scheduling request prohibition timer duration is a product of the prohibition timer duration and the first non-negative integer.
  • the application provides a scheduling request receiving method, including:
  • the network device sends a scheduling request configuration message to the terminal device, where the configuration message includes a repetition sending duration of the scheduling request, a scheduling request resource period, and a scheduling request prohibiting timer duration;
  • the network device receives, according to the scheduling request configuration message, a first scheduling request and a second scheduling request that are repeatedly sent by the terminal device, where the repeated sending duration is less than or equal to the scheduling request prohibiting timer duration.
  • the forbidden timer duration is a product of the scheduling request resource period and a non-negative integer, where the scheduling request resource period includes a first scheduling request resource period and a second scheduling request resource period, The first scheduling request resource period is greater than the second scheduling request resource period, the non-negative integer includes a first non-negative integer and a second non-negative integer, and the first non-negative integer is greater than the second Non-negative integer;
  • the duration of the repeated transmission is less than or equal to the duration of the scheduling request prohibition timer, including:
  • the scheduling request prohibiting timer duration is a product of the first scheduling request resource period and the non-negative integer
  • the forbidden timer duration is a product of the scheduling request resource period and a non-negative integer, where the scheduling request resource period includes a first scheduling request resource period and a second scheduling request resource period, The first scheduling request resource period is greater than the second scheduling request resource period, the non-negative integer includes a first non-negative integer and a second non-negative integer, and the first non-negative integer is greater than the second Non-negative integer;
  • the duration of the repeated transmission is less than or equal to the duration of the scheduling request prohibition timer, including:
  • the scheduling request prohibition timer duration is a product of the prohibition timer duration and the first non-negative integer.
  • the application provides a terminal device, including:
  • the receiving unit is configured to receive a scheduling request configuration message sent by the network device, where the configuration message includes a repetition sending duration of the scheduling request, a scheduling request resource period, and a scheduling request prohibiting timer duration;
  • the sending unit is configured to repeatedly send the first scheduling request and the second scheduling request according to the scheduling request configuration message, where the sending unit starts the scheduling request prohibiting timing when starting to repeatedly send the first scheduling request.
  • the sending unit sends the second scheduling request after the scheduling request prohibition timer expires, and after the first scheduling request is sent.
  • the repeated transmission duration is less than or equal to the scheduling request prohibition timer duration.
  • the repeated transmission duration is greater than the scheduling request prohibition timer duration
  • the sending unit sends the second scheduling request after the first scheduling request is sent, including:
  • the sending unit abandons using a scheduling request resource that occurs when the first scheduling request is repeatedly sent to send a scheduling request
  • the repeated transmission duration is greater than the scheduling request prohibition timer duration
  • the sending unit sends the second scheduling request after the first scheduling request is sent, including:
  • the sending unit sends the first scheduling request and/or the second scheduling request within the scheduling request prohibiting timer duration
  • the repeated transmission duration is greater than the scheduling request prohibition timer duration
  • the sending unit sends the second scheduling request after the first scheduling request is sent, including:
  • the medium access control layer of the terminal device abandons sending a scheduling request to the physical layer when the physical layer repeatedly sends the first scheduling request.
  • the forbidden timer duration is a product of the scheduling request resource period and a non-negative integer, where the scheduling request resource period includes a first scheduling request resource period and a second scheduling request resource period, The first scheduling request resource period is greater than the second scheduling request resource period, the non-negative integer includes a first non-negative integer and a second non-negative integer, and the first non-negative integer is greater than the second Non-negative integer;
  • the duration of the repeated transmission is less than or equal to the duration of the scheduling request prohibition timer, including:
  • the scheduling request prohibiting timer duration is a product of the first scheduling request resource period and the non-negative integer
  • the forbidden timer duration is a product of the scheduling request resource period and a non-negative integer, where the scheduling request resource period includes a first scheduling request resource period and a second scheduling request resource period, The first scheduling request resource period is greater than the second scheduling request resource period, the non-negative integer includes a first non-negative integer and a second non-negative integer, and the first non-negative integer is greater than the second Non-negative integer;
  • the duration of the repeated transmission is less than or equal to the duration of the scheduling request prohibition timer, including:
  • the scheduling request prohibition timer duration is a product of the prohibition timer duration and the first non-negative integer.
  • the application provides a network device, including:
  • the sending unit is configured to send a scheduling request configuration message to the terminal device, where the configuration message includes a repetition sending duration of the scheduling request, a scheduling request resource period, and a scheduling request prohibiting timer duration;
  • the receiving unit is configured to receive, according to the scheduling request configuration message, a first scheduling request and a second scheduling request that are repeatedly sent by the terminal device, where the repeated sending duration is less than or equal to the scheduling request prohibiting timer duration.
  • the forbidden timer duration is a product of the scheduling request resource period and a non-negative integer, where the scheduling request resource period includes a first scheduling request resource period and a second scheduling request resource period, The first scheduling request resource period is greater than the second scheduling request resource period, the non-negative integer includes a first non-negative integer and a second non-negative integer, and the first non-negative integer is greater than the second Non-negative integer;
  • the duration of the repeated transmission is less than or equal to the duration of the scheduling request prohibition timer, including:
  • the scheduling request prohibiting timer duration is a product of the first scheduling request resource period and the non-negative integer
  • the forbidden timer duration is a product of the scheduling request resource period and a non-negative integer, where the scheduling request resource period includes a first scheduling request resource period and a second scheduling request resource period, The first scheduling request resource period is greater than the second scheduling request resource period, the non-negative integer includes a first non-negative integer and a second non-negative integer, and the first non-negative integer is greater than the second Non-negative integer;
  • the duration of the repeated transmission is less than or equal to the duration of the scheduling request prohibition timer, including:
  • the scheduling request prohibition timer duration is a product of the prohibition timer duration and the first non-negative integer.
  • the terminal device and the network device provided by the present application may include a unit for performing the steps in the foregoing method design.
  • the unit may be software and/or hardware.
  • the structure of the terminal device and the network device provided by the present application includes a processor and a transceiver, and the processor is configured to support the terminal device and the network device to perform corresponding functions in the foregoing methods.
  • the transceiver is configured to support communication between the network device and the terminal device, and send information or a message involved in the foregoing method to the network device.
  • a memory may also be included in the terminal device for coupling with the processor, which stores program messages and data necessary for the terminal device.
  • an embodiment of the present application provides a computer program product comprising a message, when executed on a computer, causing a computer to perform the method described in the above aspects.
  • an embodiment of the present application provides a computer readable storage medium, wherein the computer readable storage medium stores a message, and when executed on a computer, causes the computer to perform the method described in the above aspects.
  • the conflict of sending the scheduling request can be avoided, and the success rate of the scheduling request receiving is improved.
  • FIG. 12 is a schematic diagram of an application scenario of a communication system according to an embodiment of the present application.
  • the communication system can apply an LTE network or a Next Generation (NR or 5G) network.
  • the terminal device accesses the network through a network device, such as an evolved base station (Evolved Node B, eNB) in LTE, and implements data transmission and reception by interacting with the eNB.
  • a network device such as an evolved base station (Evolved Node B, eNB) in LTE, and implements data transmission and reception by interacting with the eNB.
  • the base station can also be a 5G base station gNB.
  • the foregoing terminal device may be a mobile phone, a smart terminal, a multimedia device, a streaming media device, etc., and is not limited in this embodiment.
  • the eNB is a bridge between the user terminal in the LTE network and the Evolved Packet Core (EPC).
  • the eNBs are connected through the X2 interface.
  • the main functions are: radio resource management, IP header compression, and User data stream encryption, Mobility Management Entity (MME) selection when user terminal is attached, routing of user plane data to Serving Gateway (S-GW), organization and transmission of paging messages, broadcast messages Organization and transmission, measurement and measurement report configuration for mobility or scheduling purposes.
  • MME Mobility Management Entity
  • FIG. 13 is a schematic diagram of a configuration of a Scheduling Request (SR) resource in the prior art related to the embodiment of the present application.
  • SR Scheduling Request
  • UE user equipment
  • eNB evolved Node B
  • a Buffer Status Report (BSR) is used to indicate the current amount of data of the UE. If the UE does not send the resources of the BSR at this time, the UE needs to send a Scheduling Request (SR) to the eNB to request the eNB to send the resources of the BSR.
  • SR Scheduling Request
  • the eNB configures the resources for sending SR to each UE, and the resource configuration manner is as shown in FIG.
  • the eNB configures a period (SR PERIODICITY ) and an offset (N OFFSET, SR ) of the SR resource for the UE, and the UE satisfies the following formula in the system frame number (SFN) and the subframe number (Subframe, sf).
  • Send SR :
  • the UE can transmit the SR on the sub-frame 1 and the subframe 6 of each system frame.
  • N OFFSET, SR and S RPERIODICITY can also be configured with other values, as shown in Table 1.
  • the current SR resource maximum period is 80 milliseconds (millisecond, ms).
  • the eNB also configures a scheduling request prohibition timer (sr-ProhibitTimer) for the UE.
  • sr-ProhibitTimer a scheduling request prohibition timer
  • the UE starts to send the SR
  • the UE starts the timer, and during this timer operation, the UE may not send the SR, even if The current UE has a valid SR resource. Only when the timer expires, the UE can send the SR when the UE needs to send the SR and the UE has valid SR resources.
  • the duration of the timer is determined by the product of the SR period and the non-negative integer. The current non-negative integer ranges from [0, 1, 2, 3, 4, 5, 6, 7 ].
  • the UE can complete the SR transmission in one subframe, and in the Machine Type Communication (MTC), since the UE is in an area with poor signal coverage, The UE needs to repeatedly send the SR to the eNB.
  • MTC Machine Type Communication
  • the eNB configures the SR resource shown in FIG. 14 for the UE.
  • the UE needs to send the SR, for example, the UE starts in the first subframe of the 12th system frame.
  • the SR is sent. Since the UE is in a weak signal area, the UE needs to repeatedly send an SR to the eNB.
  • the eNB configures the UE to send the SR times 10 times. As shown in FIG.
  • the UE receives the first number from the 12th system frame.
  • the frame starts to transmit the SR, and the SR is continuously transmitted 9 times in the next 9 subframes (or 10 uplink effective subframes), that is, the SR is transmitted 10 times in total.
  • the number of times the eNB configures the UE to repeatedly send SRs may be 16, 32, 64, 128.
  • the SR resource configured by the eNB for the UE is periodically generated. If the UE does not receive the resource allocation message of the eNB after the SR is repeatedly sent, the UE will generate the SR resource and the scheduling request prohibit timer expires. The new SR is sent again to the eNB.
  • the non-negative integer is 1, that is, the scheduling request prohibit timer is one SR period.
  • the UE will trigger a new SR when the previous SR has not been sent yet.
  • the transmission causes the SR to transmit a collision, and reduces the success rate of the eNB receiving the SR.
  • the eNB configures the SR period to be 5 ms, the offset is 1 subframe, that is, 1 ms, the number of SR repeated transmissions is 8, and the scheduling request prohibition timer duration is 5 ms.
  • the UE starts transmitting the SR in the first subframe of the No.
  • the present application discloses the following embodiments for solving the above conflict problem.
  • FIG. 17 is a schematic flowchart diagram of a scheduling request sending method according to an embodiment of the present application.
  • the execution body of the method is a terminal device.
  • the terminal device receives a scheduling request configuration message sent by the network device, where the configuration message includes a repetition sending duration of the scheduling request, a scheduling request resource period, and a scheduling request prohibiting timer duration.
  • the terminal device is exemplified by a UE, and the network device is described by taking an eNB as an example.
  • the eNB configures periodic SR resources of the UE.
  • the UE receives a Radio Resource Control (RRC) connection reconfiguration message (RRCConnectionReconfiguration) sent by the eNB, and includes a scheduling request configuration message (schedulingRequestConfig), specifically, a repetition sending duration of the scheduling request, and a scheduling request resource.
  • RRC Radio Resource Control
  • RRCConnectionReconfiguration Radio Resource Control
  • schedulingRequestConfig scheduling request configuration message
  • the period and the scheduling request prohibit the timer duration.
  • the information may be included in a message or may be included in multiple messages.
  • the present application is not limited. These messages are collectively referred to as a scheduling request configuration message.
  • the repeated transmission duration of the scheduling request may be the number of repeated transmissions of the scheduling request. Because the scheduling request is sent on the Physical Uplink Control Channel (PUCCH), the number of repeated transmissions of the scheduling request may also be PUCCH. Repeat the number of times sent. Here, it can be understood that the number of times corresponds to the number of subframes, for example, 10 times of repeated transmission, that is, 10 times in 10 subframes. Alternatively, the repeated transmission duration may be the time elapsed from the first transmission to the last transmission, that is, the scheduling request may be sent on consecutive uplink subframes, such as FDD, or may be on non-contiguous uplink subframes.
  • the transmitted resource such as TDD, can be obtained by looking up the table.
  • the eNB can configure an index of the resource period corresponding to the scheduling request of the UE, and the UE determines the scheduling request resource period by using the index value, as shown in Table F1.
  • the scheduling request prohibition timer duration may be a specific length of time, or may be determined by a product of a scheduling request resource period and a non-negative integer.
  • the scheduling request prohibition timer duration can be understood as a continuous time, and can also be understood as the time of several non-contiguous uplink subframes.
  • the terminal device repeatedly sends the first scheduling request and the second scheduling request according to the scheduling request configuration message, where the terminal device starts the scheduling request prohibiting timer when starting to repeatedly send the first scheduling request. After the scheduling request prohibition timer expires, the terminal device sends the second scheduling request after the first scheduling request is sent.
  • the first scheduling request is the SR that is sent by the UE at the beginning or the previous time
  • the second scheduling request is after the UE repeatedly sends the first scheduling request (or the UE is in the process of repeatedly sending the first scheduling request), because the first scheduling request is not received.
  • the resource allocation message of the eNB when the UE has a valid SR resource, and the scheduling request prohibition timer expires, the SR is sent by the UE again.
  • the UE may send the second scheduling request after the first scheduling request is sent, and after the scheduling request prohibition timer expires.
  • the conflict of sending the scheduling request can be avoided, and the success rate of the scheduling request receiving is improved.
  • FIG. 18 is a schematic diagram of still another scheduling request sending method disclosed in the embodiment of the present application.
  • the repeated transmission duration is less than or equal to the scheduling request prohibition timer duration.
  • the SR repeat transmission duration is 6 subframes, that is, 6 ms.
  • the SR inhibit timer has a duration of 10 subframes, that is, 10 ms.
  • the SR does not trigger a new SR transmission during the SR inhibit timer operation.
  • the UE can repeat the transmission of the SR before triggering the next SR repeated transmission, that is, the previous SR repeated transmission does not be repeated with the subsequent SR transmission. conflict.
  • the UE can normally trigger and send the second scheduling request (that is, the next SR).
  • the conflict of sending the scheduling request can be avoided, and the success rate of the scheduling request receiving is improved.
  • FIG. 19 is a schematic diagram of still another scheduling request sending method disclosed in the embodiment of the present application.
  • the repeated transmission duration is greater than the scheduling request prohibition timer duration.
  • the SR repeated transmission duration configured by the eNB is 7 subframes, that is, 7 ms.
  • the SR inhibit timer has a duration of 5 subframes, that is, 5 ms.
  • the UE will not trigger a new SR transmission.
  • the UE continues to trigger and send the SR on the valid SR resource.
  • the UE first triggers SR transmission on the first subframe of the No. 12 system frame, and repeatedly transmits the SR for seven consecutive subframes. On the sixth subframe of the system frame No.
  • the UE will trigger the SR transmission again because the SR prohibition timer has timed out, and this will be repeated with the previous one.
  • the sent SR generates a conflict.
  • the UE may relinquish the SR resources that occurred during the previous SR transmission process, that is, the UE continues to send the previous SR that has not been sent (ie, the first SR). .
  • the SR duration actually sent by the UE is the same as the SR transmission duration configured by the eNB to the UE.
  • the UE If the UE completes the repeated transmission of the previous SR (ie, the first SR), but still does not receive the resource configuration message of the eNB, that is, the UE does not receive the resources of the eNB before the first subframe of the 13th system frame.
  • the configuration message on the first subframe of the 13th system frame, the UE can continue to trigger and send the next SR (ie, the second SR).
  • the completion of the first scheduling request transmission in the first embodiment can be understood as that the UE sends the SR according to the SR repeated transmission duration configured by the eNB, and the transmission is completed, that is, the duration of actually transmitting the SR is equal to the duration of the SR that is configured to be sent.
  • the conflict of sending the scheduling request can be avoided, and the success rate of the scheduling request receiving is improved.
  • the SR repeated transmission duration configured by the eNB is 7 subframes, that is, 7 ms.
  • the SR inhibit timer has a duration of 5 subframes, that is, 5 ms.
  • the UE will not trigger a new SR transmission.
  • the UE continues to trigger and send the SR on the valid SR resource.
  • the UE first triggers SR transmission on the first subframe of the No. 12 system frame, and repeatedly transmits the SR for seven consecutive subframes. On the sixth subframe of the system frame No.
  • the UE will trigger the SR transmission again because the SR prohibition timer has timed out, and this will be repeated with the previous one.
  • the sent SR generates a conflict.
  • the UE may abandon the previous SR (ie, the first SR) transmission, and the UE triggers and sends the next SR (ie, the second SR). In this way, the SR duration actually sent by the UE is smaller than the SR transmission duration configured by the eNB to the UE.
  • the UE can continue to trigger and send the next SR (ie, the second SR).
  • the completion of the first scheduling request in the first embodiment can be understood as that the UE sends the SR according to the duration of the SR prohibition timer configured by the eNB.
  • the UE stops sending the current SR ie, the first SR.
  • the conflict of sending the scheduling request can be avoided, and the success rate of the scheduling request receiving is improved.
  • the SR repeated transmission duration configured by the eNB is 7 subframes, that is, 7 ms.
  • the SR inhibit timer has a duration of 5 subframes, that is, 5 ms.
  • the UE will not trigger a new SR transmission.
  • the trigger is that the Media Access Control (MAC) layer of the UE sends an SR to the Physical (PHY) layer of the UE.
  • the SR prohibit timer expires, if the UE has not received the resource configuration message of the eNB, the UE continues to trigger and send the SR on the valid SR resource.
  • MAC Media Access Control
  • PHY Physical
  • the UE first triggers SR transmission on the first subframe of the No. 12 system frame, and repeatedly transmits the SR for seven consecutive subframes.
  • the UE On the sixth subframe of the system frame No. 12, if the UE does not receive the resource configuration message of the eNB, the UE will trigger the SR transmission again because the SR prohibition timer has timed out, and this will be repeated with the previous one.
  • the sent SR generates a conflict.
  • the media access control layer of the UE sends a message to the physical layer to send the next SR when the physical layer repeatedly transmits the previous SR (that is, the first SR).
  • the MAC layer instructs the PHY layer to send the next SR (ie, the second SR).
  • the SR duration actually sent by the UE is equal to the SR transmission duration configured by the eNB to the UE.
  • the MAC layer of the UE may continue to send the next SR (ie, the second SR) to the PHY indication.
  • the completion of the first scheduling request transmission in the first embodiment can be understood as that the UE sends the SR according to the SR repeated transmission duration configured by the eNB, and the transmission is completed, that is, the duration of actually transmitting the SR is equal to the duration of the SR that is configured to be sent.
  • the conflict of sending the scheduling request can be avoided, and the success rate of the scheduling request receiving is improved.
  • the forbidden timer duration is a product of the scheduling request resource period and a non-negative integer
  • the scheduling request resource period includes a first scheduling request resource period and a second
  • the scheduling request resource period that is, the eNB configurable candidate scheduling request resource period includes at least two values, one of which is referred to as a first scheduling request resource period and the other is referred to as a second scheduling request resource period.
  • the first scheduling request resource period is greater than the second scheduling request resource period
  • the non-negative integer includes a first non-negative integer and a second non-negative integer
  • the first non-negative integer is greater than the second Non-negative integer
  • the duration of the repeated transmission is less than or equal to the duration of the scheduling request prohibition timer, including:
  • the scheduling request prohibiting timer duration is a product of the first scheduling request resource period and the non-negative integer
  • the eNB configures the scheduling request prohibition timer duration and the repeated transmission duration of the UE, it is ensured that the repetition transmission duration is less than or equal to the scheduling request prohibition timer duration, so that the first SR and the second SR do not collide.
  • the transmission duration is repeated, and the number of repeated transmissions may also be used. If the eNB has multiple options for configuring the SR inhibit timer duration and the SR period, that is, the non-negative integer is large or small, and/or the SR period is large or small. If the eNB is configured with a non-negative integer, it is necessary to specify that the eNB uses a larger period value, that is, the first scheduling request resource period, when configuring the SR period.
  • the forbidden timer duration is a product of the scheduling request resource period and a non-negative integer
  • the scheduling request resource period includes a first scheduling request resource period and a
  • the second scheduling request resource period that is, the eNB configurable candidate scheduling request resource period includes at least two values, one of which is referred to as a first scheduling request resource period and the other is referred to as a second scheduling request resource period.
  • the first scheduling request resource period is greater than the second scheduling request resource period
  • the non-negative integer includes a first non-negative integer and a second non-negative integer
  • the first non-negative integer is greater than the second Non-negative integer
  • the duration of the repeated transmission is less than or equal to the duration of the scheduling request prohibition timer, including:
  • the scheduling request prohibition timer duration is a product of the prohibition timer duration and the first non-negative integer.
  • the eNB configures the scheduling request prohibition timer duration and the repeated transmission duration of the UE, it is ensured that the repetition transmission duration is less than or equal to the scheduling request prohibition timer duration, so that the first SR and the second SR do not collide.
  • the transmission duration is repeated, and the number of repeated transmissions may also be used. If the eNB has multiple options for configuring the SR inhibit timer duration and the SR period, that is, the non-negative integer is large or small, and/or the SR period is large or small. If the eNB configuration SR period is not limited, it is required to specify that the eNB uses a larger integer, that is, the first non-negative integer when configuring a non-negative integer.
  • the conflict of sending the scheduling request can be avoided, and the success rate of the scheduling request receiving is improved.
  • FIG. 21 is a schematic flowchart of a scheduling request sending method according to an embodiment of the present application.
  • the execution body of the method is a network device.
  • the network device sends a scheduling request configuration message to the terminal device, where the configuration message includes a repetition sending duration of the scheduling request, a scheduling request resource period, and a scheduling request prohibiting timer duration.
  • the network device receives, according to the scheduling request configuration message, a first scheduling request and a second scheduling request that are repeatedly sent by the terminal device, where the repeated sending duration is less than or equal to the scheduling request prohibiting timer duration.
  • This step is similar to S102 of Embodiment 1, and is not described herein.
  • the conflict of sending the scheduling request can be avoided, and the success rate of the scheduling request receiving is improved.
  • the forbidden timer duration is a product of the scheduling request resource period and a non-negative integer
  • the scheduling request resource period includes a first scheduling request resource period and a second Scheduling a request resource period, wherein the first scheduling request resource period is greater than the second scheduling request resource period, and the non-negative integer includes a first non-negative integer and a second non-negative integer, the first non-negative integer Greater than the second non-negative integer;
  • the duration of the repeated transmission is less than or equal to the duration of the scheduling request prohibition timer, including:
  • the scheduling request prohibiting timer duration is a product of the first scheduling request resource period and the non-negative integer
  • the conflict of sending the scheduling request can be avoided, and the success rate of the scheduling request receiving is improved.
  • the forbidden timer duration is a product of the scheduling request resource period and a non-negative integer, where the scheduling request resource period includes a first scheduling request resource period and a The second scheduling request resource period, where the first scheduling request resource period is greater than the second scheduling request resource period, the non-negative integer includes a first non-negative integer and a second non-negative integer, the first non-negative An integer is greater than the second non-negative integer;
  • the duration of the repeated transmission is less than or equal to the duration of the scheduling request prohibition timer, including:
  • the scheduling request prohibition timer duration is a product of the prohibition timer duration and the first non-negative integer.
  • the conflict of sending the scheduling request can be avoided, and the success rate of the scheduling request receiving is improved.
  • FIG. 22 is a schematic structural diagram of a terminal device 2200 according to an embodiment of the present disclosure.
  • the terminal device includes a receiving unit 2201 and a transmitting unit 2202.
  • the receiving unit is configured to receive a scheduling request configuration message sent by the network device, where the configuration message includes a repetition sending duration of the scheduling request, a scheduling request resource period, and a scheduling request prohibiting timer duration;
  • the sending unit is configured to repeatedly send the first scheduling request and the second scheduling request according to the scheduling request configuration message, where the sending unit starts the scheduling request prohibiting timing when starting to repeatedly send the first scheduling request.
  • the sending unit sends the second scheduling request after the scheduling request prohibition timer expires, and after the first scheduling request is sent.
  • the repeated transmission duration is less than or equal to the scheduling request prohibition timer duration.
  • the terminal device at this time is referred to as 210.
  • the repeated transmission duration is greater than the scheduling request prohibition timer duration
  • the sending unit sends the second scheduling request after the first scheduling request is sent, including:
  • the sending unit abandons the use of the scheduling request resource that occurs when the first scheduling request is repeatedly sent to send the scheduling request. For details, see Embodiment 3.
  • the repeated transmission duration is greater than the scheduling request prohibition timer duration
  • the sending unit sends the second scheduling request after the first scheduling request is sent, including:
  • the sending unit sends the first scheduling request and/or the second scheduling request within the scheduling request prohibiting timer duration. For details, refer to the third embodiment.
  • the forbidden timer duration is a product of the scheduling request resource period and a non-negative integer
  • the scheduling request resource period includes a first scheduling request resource. a period and a second scheduling request resource period, where the first scheduling request resource period is greater than the second scheduling request resource period, and the non-negative integer includes a first non-negative integer and a second non-negative integer, the a non-negative integer is greater than the second non-negative integer;
  • the duration of the repeated transmission is less than or equal to the duration of the scheduling request prohibition timer, including:
  • the scheduling request prohibiting timer duration is a product of the first scheduling request resource period and the non-negative integer. For details, see Embodiment 3.
  • the forbidden timer duration is a product of the scheduling request resource period and a non-negative integer
  • the scheduling request resource period includes a first scheduling request resource. a period and a second scheduling request resource period, where the first scheduling request resource period is greater than the second scheduling request resource period, and the non-negative integer includes a first non-negative integer and a second non-negative integer, the a non-negative integer is greater than the second non-negative integer;
  • the duration of the repeated transmission is less than or equal to the duration of the scheduling request prohibition timer, including:
  • the scheduling request prohibition timer duration is a product of the prohibition timer duration and the first non-negative integer. For details, see Embodiment 3.
  • FIG. 23 is a schematic structural diagram of a network device 2300 according to an embodiment of the present disclosure.
  • the network device includes a transmitting unit 2301 and a receiving unit 2302.
  • the sending unit is configured to send a scheduling request configuration message to the terminal device, where the configuration message includes a repetition sending duration of the scheduling request, a scheduling request resource period, and a scheduling request prohibiting timer duration;
  • the receiving unit is configured to receive, according to the scheduling request configuration message, a first scheduling request and a second scheduling request that are repeatedly sent by the terminal device, where the repeated sending duration is less than or equal to the scheduling request prohibiting timer duration.
  • the forbidden timer duration is a product of the scheduling request resource period and a non-negative integer
  • the scheduling request resource period includes the first a scheduling request resource period and a second scheduling request resource period, where the first scheduling request resource period is greater than the second scheduling request resource period, and the non-negative integer includes a first non-negative integer and a second non-negative integer.
  • the first non-negative integer is greater than the second non-negative integer;
  • the duration of the repeated transmission is less than or equal to the duration of the scheduling request prohibition timer, including:
  • the scheduling request prohibiting timer duration is a product of the first scheduling request resource period and the non-negative integer. For details, see Embodiment 4.
  • the forbidden timer duration is a product of the scheduling request resource period and a non-negative integer
  • the scheduling request resource period includes a a scheduling request resource period and a second scheduling request resource period, wherein the first scheduling request resource period is greater than the second scheduling request resource period, and the non-negative integer includes a first non-negative integer and a second non-negative integer The first non-negative integer is greater than the second non-negative integer;
  • the duration of the repeated transmission is less than or equal to the duration of the scheduling request prohibition timer, including:
  • the scheduling request prohibition timer duration is a product of the prohibition timer duration and the first non-negative integer. For details, see Embodiment 4.
  • the device can perform functions similar to processor 1102 in FIG.
  • the device includes a processor 2410, a transmit data processor 2420, and a receive data processor 2430.
  • the processor 1102 in the above embodiment may be the processor 2410 in FIG. 24 and perform the corresponding functions.
  • the control circuit 1101 in the above embodiment may be the transmit data processor 2420 of Fig. 24, and/or the receive data processor 2430.
  • a channel coder and a channel decoder are shown in FIG. 24, it is to be understood that these modules are not intended to be limiting, and are merely illustrative.
  • Fig. 25 shows another form of network device of this embodiment.
  • the processing device 2500 includes modules such as a modulation subsystem, a central processing subsystem, and a peripheral subsystem.
  • the network device in this embodiment can be used as a modulation subsystem therein.
  • the modulation subsystem may include a processor 2503, an interface 2504.
  • the processor 2503 performs the functions of the processor 1102 described above, and the interface 2504 performs the functions of the control circuit 1101 described above.
  • the modulation subsystem includes a memory 2506, a processor 2503, and a program stored on the memory 2506 and operable on the processor, and the processor 2503 executes the program to implement the terminal device side in the above method embodiment. Methods.
  • the memory 2506 may be non-volatile or volatile, and its location may be located inside the modulation subsystem or in the processing device 2500 as long as the memory 2506 can be connected to the The processor 2503 can be.
  • a program executable on a processor, the processor executing the program to implement the method of any one of the embodiments of the present invention.
  • a computer readable storage medium having stored thereon instructions that, when executed, perform the method of any of the embodiments of the present invention.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the above computer program product includes one or more computer messages.
  • the processes or functions described in accordance with embodiments of the present application are generated in whole or in part.
  • the above computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the above computer message may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer message may be wired from a website site, computer, server or data center (for example, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.) to another website site, computer, server or data center.
  • the computer readable storage medium described above can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the above usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).
  • the described systems, devices, and methods, and the schematic diagrams of various embodiments may be combined or integrated with other systems, modules, techniques or methods without departing from the scope of the present application.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in electronic, mechanical or other form.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the above computer program product includes one or more computer messages.
  • the processes or functions described in accordance with embodiments of the present application are generated in whole or in part.
  • the above computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the above computer message may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer message may be wired from a website site, computer, server or data center (for example, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.) to another website site, computer, server or data center.
  • the computer readable storage medium described above can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the above usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).
  • the described systems, devices, and methods, and the schematic diagrams of various embodiments may be combined or integrated with other systems, modules, techniques or methods without departing from the scope of the present application.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in electronic, mechanical or other form.

Landscapes

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

Abstract

本申请实施例公开了一种数据处理方法与设备。其中，该方法包括：获取无线链路控制RLC层的服务数据单元SDU；按照数据删除方式删除数据，所述数据删除方式包括：将所述SDU封装成的第一协议数据单元PDU删除，或者，将所述第一PDU中的数据域删除。采用本申请实施例，可以根据不同的数据删除方式，将不需要传输的数据删除，节省了无线通信资源。

Description

数据处理方法及设备 技术领域
本申请涉及通信技术领域，尤其涉及一种数据处理方法及设备。
背景技术
在长期演进(Long Term Evolution,LTE)网络中，用户面数据以网络互连协议(Internet Protocol，IP)数据包的格式经由设备的分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层、无线链路控制(Radio Link Control，RLC)层、媒体接入控制(Media Access Control，MAC)层、物理(Physical，PHY)层在用户设备和网络设备之间进行传输。
在数据传输的过程中，数据包具有一定的时效性，例如语音通话业务，对数据包的时效性要求较高；而网页浏览业务，则对数据包的时效性要求较低。因此，设备的PDCP层会针对PDCP SDU(PDCP层的服务数据单元(Service Data Unit,SDU))启动一个对应于该PDCP SDU的业务特性的定时器，若定时器超时，则PDCP层会将这个PDCP SDU丢弃，并向RLC层发送指示信息，指示RLC层丢弃接收到的PDCP层的协议数据单元(Protocol Data Unit，PDU)(该PDU由PDCP层将上述PDCP SDU封装获得)，因为超过时效要求后，再传输这个数据包已经没有意义。
在LTE技术中，RLC层具有级联功能，即RLC层可以从PDCP层接收多个PDCP PDU，将多个PDCP PDU级联到一个RLC PDU之中；举例来说，将PDCP PDU 3，PDCP PDU 4和PDCP PDU 5级联到一个RLC PDU之中。若RLC层接收到PDCP层发送的指示信息，该指示信息指示RLC层丢弃PDCP PDU 4，由于生成的RLC PDU中除了包含PDCP PDU 4之外，还包含PDCP PDU 3和PDCP PDU 5，因此该RLC PDU不会被丢弃，RLC层会正常传输该RLC PDU，从而造成本不需要传输的数据包含在该数据包中进行了传输，造成了无线通信资源浪费。
发明内容
本申请实施例提供了一种数据处理方法及设备，可以根据不同的数据删除方式，将不需要传输的数据删除，节省了无线通信资源。
第一方面，本申请实施例提供了一种数据处理方法，包括：
获取无线链路控制RLC层的服务数据单元SDU；
按照数据删除方式删除数据，所述数据删除方式包括：将所述SDU删除，或者，将所述SDU封装成的第一协议数据单元PDU删除，或者，将所述第一PDU中的数据域删除。
在该实施方式中，上述SDU即为无线链路控制服务数据单元RLC SDU，上述PDU即为无线链路控制协议数据单元RLC PDU。当设备(可为用户设备或网络设备)的RLC层从本设备的PDCP层接收到RLC SDU之后，若RLC层接收到PDCP层发送的用于指示删除所述RLC SDU的指示信息，RLC层可根据上述数据删除方式删除数据，从而避免在之后的重传过程中，传输不需要传输的数据而造成无线通信资源浪费。
作为一种可选的实施方式，所述第一PDU仅对应一个SDU。
在该实施方式中，该数据处理方法仅适用于RLC层不采用级联的方式生成PDU的情况，也就是说，RLC层不会将多个SDU级联到一个PDU里，即第一PDU仅对应一个SDU。
作为一种可选的实施方式，所述获取无线链路控制RLC层的服务数据单元SDU之后，所述按照数据删除方式删除数据之前，所述方法还包括：
为所述SDU分配第一序列号；
将所述SDU封装成所述第一PDU，所述第一PDU包含数据域和第一包头，所述第一包头中包含所述第一序列号；
将所述第一PDU传输至媒体接入控制MAC层之后，存储所述第一PDU。
在该实施方式中，通过第一序列号识别出第一PDU为上述SDU封装后得到的PDU，从而当RLC层接收到删除该SDU的指示信息后，可以根据第一序列号获取到第一PDU并对第一PDU进行数据删除的操作。
作为一种可选的实施方式，所述将所述SDU封装成所述第一PDU，包括：
所述SDU被分段为N个子数据包的情况下，将所述N个子数据包封装成N个PDU。
在该实施方式中，若数据包SDU过大，则可将SDU分段为N个子数据包，再对应封装为N个PDU，以使其成为适合基础网络传输的数据帧。
作为一种可选的实施方式，所述将所述第一PDU中的数据域删除，包括：
将所述N个PDU中的数据域删除。
在该实施方式中，若RLC层为SDU分配第一序列号，则分段后再封装得到的N个PDU均通过第一序列号进行标识，因此可以获取所有序列号为第一序列号的PDU，将这些PDU的数据域删除。
作为一种可选的实施方式，所述数据删除方式还包括：
在所述N个PDU中确定一个PDU作为第二PDU；
将所述第二PDU中的数据域删除；
将所述N个PDU中除所述第二PDU以外的PDU删除。
在该实施方式中，将N个PDU中除第二PDU以外的PDU均删除，可以进一步减少发送时的冗余数据。
作为一种可选的实施方式，所述按照数据删除方式删除数据之后，所述方法还包括：
修改所述第二PDU的第二包头中用于指示所述第二PDU是否分段的指示信息，以指示所述第二PDU不分段。
在该实施方式中，将N个PDU中除第二PDU以外的PDU均删除之后，在重传中，只有第二PDU会被发送，从而到达数据接收端。因此，修改第二包头以指示第二PDU不分段，有助于数据接收端正常进行数据包排序。
作为一种可选的实施方式，所述将所述SDU封装成的第一协议数据单元PDU删除，包括：
删除所述第一PDU；
构造第三PDU，所述第三PDU包含第三包头，所述第三包头中包含的序列号与所述第 一序列号相同。
在该实施方式中，构造的第三PDU可以仅包含包头，当第三PDU被重传至数据接收端时，可以根据其中包含的第一序列号帮助数据接收端正确完成数据包排序，与此同时，避免了第一PDU中已失去时效性的数据被重传而浪费无线通信资源。
作为一种可选的实施方式，所述按照数据删除方式删除数据，包括：
接收分组数据汇聚协议PDCP层发送的指示信息，所述指示信息用于指示所述RLC层删除所述SDU；在接收到所述指示信息的情况下，按照所述数据删除方式删除数据；或者，
从获取到所述SDU时启动计时操作，所述计时操作的时间超过预设时间阈值的情况下，按照所述数据删除方式删除数据。
在该实施方式中，PDCP层向RLC层发送用于指示SDU中包含的数据已失去时效性的指示信息时，可能具有一定的时延；因此，RLC层可以从获取到SDU时启动计时器，若计时器超时，则执行数据删除操作，避免由于上述时延而未能及时删除数据。
作为一种可选的实施方式，若所述数据删除方式为所述将所述SDU封装成的第一协议数据单元PDU删除，所述按照数据删除方式删除数据之后，所述方法还包括：
生成用于指示所述第一PDU已被删除的状态报告，所述状态报告包括所述第一序列号。
在该实施方式中，若第一PDU整个被删除(第一包头、数据域均被删除)，为避免数据接收端进行数据包排序时持续等待第一PDU，设备可以生成用于指示第一PDU已被删除的状态报告，并将该状态报告发送至数据接收端。
作为一种可选的实施方式，所述将所述SDU封装成的第一协议数据单元PDU删除，包括：
将所述N个PDU删除；
若所述数据删除方式为所述将所述SDU封装成的第一协议数据单元PDU删除，所述按照数据删除方式删除数据之后，所述方法还包括：
生成用于指示所述N个PDU已被删除的状态报告，所述状态报告包括所述第一序列号。
在该实施方式中，若上述N个PDU均被删除，为避免数据接收端进行数据包排序时持续等待上述N各PDU，设备可以生成用于指示上述N个PDU均被删除的状态报告，并将该状态报告发送至数据接收端。
作为一种可选的实施方式，所述状态报告还包括用于指示所述状态报告为RLC层的控制PDU的指示信息；
和/或，所述状态包括还包括比特图，所述比特图用于指示与所述第一PDU临近的PDU是否被删除；
和/或，所述状态报告还包括数值，所述数值用于指示包括所述第一PDU在内连续删除的PDU的个数。
在该实施方式中，可以通过对状态报告进行设定，使得状态报告能够通知数据接收端多于一个PDU被删除的信息。
作为一种可选的实施方式，所述数据删除方法还包括：将所述SDU删除；
所述获取无线链路控制RLC层的服务数据单元SDU之后，所述按照数据删除方式删除 数据之前，所述方法还包括：
为所述SDU分配第一序列号；
若所述数据删除方法为所述将所述SDU删除，所述按照数据删除方式删除数据之后，所述方法还包括：
生成包含第四包头的第四PDU，所述第四包头包含所述第一序列号；或者，
将所述第一序列号重新分配给所述SDU之后获取的第一个SDU。
在该实施方式中，SDU在被封装成为PDU之前即被删除，则为SDU分配的序列号可以重新分配给下一个SDU，或者针对该序列号生成仅包含包头的PDU，以保持序列号的连续，有利于数据接收方进行数据包排序。
第二方面，本申请实施例提供了一种数据处理方法，包括：
接收无线链路控制RLC层的状态报告；
获取所述状态报告中包含的序列号；
所述状态报告中包含的序列号为第一序列号的情况下，确定序列号为所述第一序列号的PDU为已接收。
第三方面，本申请实施例提供了一种数据处理方法，包括：
接收M个无线链路控制RLC层的PDU，所述M个RLC层的PDU包含的序列号为第一序列号的情况下，确定所述M个RLC层的PDU为RLC层的服务数据单元SDU分段后封装的PDU；
所述M个RLC层的PDU中存在至少一个PDU的数据域为空的情况下，将所述M个RLC层的PDU删除，确定序列号为所述第一序列号的PDU为已接收。
第四方面，本申请实施例提供了一种网络设备，包括：
获取单元，用于获取无线链路控制RLC层的服务数据单元SDU；
删除单元，用于按照数据删除方式删除数据，所述数据删除方式包括：将所述获取单元获取的所述SDU删除，或者，将所述SDU封装成的第一协议数据单元PDU删除，或者，将所述第一PDU中的数据域删除。
作为一种可选的实施方式，本申请提供的网络设备可以包含用于执行上述方法设计中步骤的单元。所述单元可以是软件和/或是硬件。可选地，本申请提供的网络设备的结构中包括处理器和收发器，所述处理器被配置为支持网络设备执行上述方法中相应的功能。所述收发器用于支持网络设备与终端之间的通信，向终端发送上述方法中所涉及的信息或者消息。网络设备中还可以包括存储器，所述存储器用于与处理器耦合，其保存网络设备必要的程序消息和数据。网络设备中还可以包括通信接口，所述通信接口用于与其他网络设备通信。
第五方面，本申请实施例提供了一种终端，包括：
获取单元，用于获取无线链路控制RLC层的服务数据单元SDU；
删除单元，用于按照数据删除方式删除数据，所述数据删除方式包括：将所述获取单 元获取的所述SDU删除，或者，将所述SDU封装成的第一协议数据单元PDU删除，或者，将所述第一PDU中的数据域删除。
作为一种可选的实施方式，本申请提供的终端可以包含用于执行上述方法设计中步骤的单元。所述单元可以是软件和/或是硬件。可选地，本申请提供的终端的结构中包括处理器和收发器，所述处理器被配置为支持终端执行上述方法中相应的功能。所述收发器用于支持接入网设备与终端之间的通信，向接入网设备发送上述方法中所涉及的信息或者消息。终端中还可以包括存储器，所述存储器用于与处理器耦合，其保存终端必要的程序消息和数据。
第六方面，本申请实施例提供了一种包含消息的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第七方面，本申请实施例提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有消息，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第八方面，本申请实施例还提供了一种包含指令的计算机程序产品，该指令被执行时执行上述各方面所述的方法。
通过实施本申请实施例，设备的无线链路控制层可以根据不同的数据删除方式，将不需要传输的数据删除，节省了无线通信资源。
附图说明
为了更清楚地说明本申请实施例或背景技术中的技术方案，下面将对本申请实施例或背景技术中所需要使用的附图进行说明。
图1A为本申请实施例公开的一种通信***应用场景的示意图；
图1B为本申请实施例公开的一种用户面协议栈的交互示意图；
图1C是本申请实施例公开的一种PDCP层与RLC层交互的示意图；
图1D为本申请实施例公开的一种RLC PDU的结构示意图；
图2是本申请实施例公开的一种数据处理方法的流程示意图；
图3是本申请实施例公开的另一种数据处理方法的流程示意图；
图4是本申请实施例公开的又一种数据处理方法的流程示意图；
图5是本申请实施例公开的又一种数据处理方法的流程示意图；
图6A为本申请实施例公开的又一种数据处理方法的流程示意图；
图6B为本申请实施例公开的一种状态报告格式的示意图；
图6C为本申请实施例公开的另一种状态报告格式的示意图；
图6D为本申请实施例公开的又一种状态报告格式的示意图；
图7为本申请实施例公开的另一种通信***应用场景的示意图；
图8是本申请实施例公开的又一种数据处理方法的流程示意图；
图9为本申请实施例公开的一种设备900的结构示意图；
图10为本申请实施例公开的一种基站1000的结构示意图；
图11为本申请实施例公开的一种终端1100的结构示意图；
图12为本申请实施例公开的一种通信***应用场景的示意图；
图13为本申请实施例公开的一种调度请求资源的配置示意图；
图14为本申请实施例公开的另一种调度请求资源的配置示意图；
图15为本申请实施例公开的一种调度请求重复发送的示意图；
图16为本申请实施例公开的一种调度请求相冲突的示意图；
图17为本申请实施例公开的一种调度请求发送方法的流程示意图；
图18为本申请实施例公开的又一种调度请求发送方法的示意图；
图19为本申请实施例公开的又一种调度请求发送方法的示意图；
图20为本申请实施例公开的又一种调度请求发送方法的示意图；
图21为本申请实施例公开的一种调度请求接收方法的流程示意图；
图22为本申请实施例公开的一种终端设备的结构示意图；
图23为本申请实施例公开的一种网络设备的结构示意图；
图24为本申请实施例提供的网络设备的另一示意性框图；
图25为本申请实施例提供的网络设备的再一示意性框图。
具体实施方式
下面结合本申请实施例中的附图对本申请实施例进行描述。
请参阅图1A，图1A为本申请实施例公开的一种通信***应用场景的示意图。该通信***可应用LTE网络或5G网络。如图1A所示，用户终端通过演进型基站(evolved Node B，eNB)接入核心网络，通过与eNB进行交互实现数据的发送和接收。在5G***中，基站还可以为5G基站gNB。
上述用户设备可为手机、智能终端、多媒体设备和流媒体设备等，本申请实施例不做限定。而上述eNB是LTE网络中用户终端和演进后的分组核心网(Evolved Packet Core，EPC)之间的桥梁，eNB之间通过X2接口进行连接，其主要功能有：无线资源管理、IP头压缩及用户数据流加密、用户终端附着时的移动性管理实体(Mobility Management Entity，MME)选择、路由用户面数据至服务网关(Serving Gateway，S-GW)、寻呼消息的组织和发送、广播消息的组织和发送、以移动性或调度为目的的测量及测量报告配置等。
请参阅图1B，图1B为本申请实施例公开的一种用户面协议栈的交互示意图。在LTE网络中，用户面数据以IP数据包格式经由PDCP层、RLC层、MAC层和PHY层在用户设备和网络设备之间进行传输。图中的箭头表示用户设备向eNB发送数据时，数据包的传输流向，数据包一般需逐层经过PDCP层、RLC层、MAC层和PHY层。可以理解的是，当eNB向用户设备发送数据时，数据包的传输流向反向。当IP数据包从设备的PDCP层传输至本设备的RLC层时，若PDCP层向RLC层发送指示信息以指示RLC层丢弃该失去时效性的数据包，而 RLC层将该数据包与其他多个数据包级联后封装为一个RLC PDU(即RLC层的PDU)，则RLC层不能执行丢弃该数据包的操作，携带该数据包的RLC PDU会正常进行传输，造成无线通信资源的浪费。
请参阅图1C，图1C是本申请实施例公开的一种PDCP层与RLC层交互的示意图。PDCP层向RCL层发送PDCP PDU 4(即序列号(Sequence Number,SN)为4的PDCP层的PDU)，RCL层接收到PDCP PDU 4后，为其分配RLC层的序列号8，之后将该数据包封装成RLC PDU8(即序列号为8的RLC层的PDU)，请参阅图1D，图1D为本申请实施例公开的一种RLC PDU的结构示意图，RLC PDU的结构包括包头和数据域。
在此之后，RLC层将封装成的RLC PDU 8传输至本设备的MAC层。在应答-重传模式(Acknowledged Mode,AM)中，RLC层会将发送到MAC层的、且未收到数据接收方反馈的ACK信息(ACK信息表示数据接收方成功接收到某个数据包)的RLC PDU 8保存到重传存储器内。在这样的情况下，若本设备的PDCP层在此时刻向RLC层指示丢弃PDCP PDU8，则在RLC层不对RLC SDU进行级联时，一个RLC PDU只对应一个RLC SDU，可以应用如下图2至图6D以及图8的方法来进行数据删除操作。
此外，在AM模式中，在RLC层向MAC层发送RLC PDU时，也会有RLC SDU失去时效性。例如PDCP层向RLC层发送PDCP PDU 1和PDCP PDU2(分别对应RLC SDU 5和RLC SDU 6)，在RLC层向对端发送RLC SDU 5的过程中，RLC SDU 6对应的PDCP PDU 1所关联的定时器超时了，这时PDCP层指示丢弃PDCP PDU 1，即丢弃RLC SDU 5。可见，在这种情况下，RLC SDU 6对应的RLC PDU并没有发送到MAC层，也就没有存储到重传存储器中。在这种情况下，以下方法同样适用。
此外，在AM模式下，若RLC层在发送RLC PDU分段时，且该分段对应的RLC SDU的所有分段还没有全部发送到对端时，收到PDCP层的指示信息，指示将对应的PDCP PDU丢弃，以下方法同样适用。
此外，本发明还适用于非应答模式(Unacknowledged Mode,UM)。
请参阅图2，图2是本申请实施例公开的一种数据处理方法的流程示意图。该数据处理方法的执行主体可为用户终端或网络设备，本申请实施例以用户终端为例来进行说明。
201、获取RLC层的SDU。
结合图1C来进行说明，用户终端的RLC层接收用户终端的PDCP层传输的PDCP PDU 4，该PDCP PDU到达RLC层后，即被称为RLC SDU。
202、为上述SDU分配第一序列号。
用户终端的RLC层为该RLC SDU分配RLC层的序列号(Sequence Number,SN)8，即该RLC SDU的SN＝8。
若RLC层将RLC SDU 8封装成RLC PDU 8之前，RLC层接收到PDCP层发送的指示信息以使RLC层删除PDCP PDU 4，则RLC层可直接将RLC SDU 8删除，之后生成RLC PDU 8，其中，RLC PDU 8不包含数据域仅包含包头，且包头中携带序列号SN＝8；或者，RLC层将RLC SDU 8删除之后，在接收到PDCP PDU 5和PDCP PDU 6时，将序列号8重新分配给PDCP PDU 5，将序列号9分配给PDCP PDU 6，之后依次类推。
203、将上述SDU封装成第一PDU，第一PDU包含数据域和第一包头，第一包头中包含第一序列号。
将该RLC SDU封装为RLC PDU 8，在RLC PDU 8的包头中，包含上述分配的序列号SN＝8。
在应答-重传模式中，RLC层会将发送到本设备MAC层的、且未收到数据接收方(比如网络设备)反馈的ACK信息的RLC PDU 8保存到重传存储器内。将数据包保存到重传存储器内为可选的，即在RLC UM模式下，在将数据包(比如上述RLC PDU 8)传输至MAC层后，不需要存储该数据包。或者，在RLC AM模式中，数据包(比如上述RLC PDU 8)在发送至MAC层之前即有可能被丢弃。
204、将第一PDU中的数据域删除。
若用户设备的RLC层将RLC PDU 8保存到重传存储器内之后，接收到本设备的PDCP层传输的指示信息，该指示信息指示RLC层删除PDCP PDU 4(由于PDCP层为PDCP PDU 4设定的定时器超时，表示PDCP PDU 4已失去时效性)，则RLC层根据序列号在重传存储器中查找到将PDCP PDU 4封装后得到的RLC PDU 8，将RLC PDU 8的数据域删除，仅保留RLC PDU8的包头。
若用户设备的RLC层还没有将RLC PDU 8保存到重传存储器内，接收到本设备的PDCP层发送的指示信息，该指示信息指示RLC层删除PDCP PDU 4，则RLC层将RLC PDU 8的数据域删除，仅保留RLC PDU 8的包头。
若用户设备的RLC层还没有将PDCP PDU 4封装成RLC PDU 8，接收到本设备的PDCP层发送的指示信息，该指示信息指示RLC层删除PDCP PDU 4，则RLC层将PDCP PDU 4删除，并生成对应PDCP PDU 4的RLC PDU 8的包头。
在应答-重传模式下，用户设备的RLC层重传仅包含包头的RLC PDU 8，避免重传已经失去时效的数据(即数据域部分)，节省无线通信资源。
请参阅图3，图3是本申请实施例公开的又一种数据处理方法的流程示意图。
301、获取RLC层的SDU。
结合图1C来进行说明，用户终端的RLC层接收用户终端的PDCP层传输的PDCP PDU 4，该PDCP PDU到达RLC层后，即被称为RLC SDU。
302、为上述SDU分配序列号。
用户终端的RLC层为该RLC SDU分配RLC层的序列号8。
303、将上述SDU分段为N个子数据包。
在将RLC SDU封装成RLC PDU之前，若RLC SDU包含的数据过长，造成数据包过大，则需要将RLC SDU分段为N子数据包(N大于等于2)，再分别封装分段后的子数据包。需要说明的是，上述PDCP PDU 4分段后的N个子数据包，其RLC层的序列号均为8。
304、将上述N个子数据包封装成N个RLC PDU。
305、将上述N个RLC PDU的数据域均删除。
若用户设备的RLC层将上述N个PDU保存到重传存储器内之后，接收到本设备的PDCP层传输的指示信息，该指示信息指示RLC层删除PDCP PDU 4(由于PDCP层为PDCP PDU 4设定的定时器超时，表示PDCP PDU 4已失去时效性)；则RLC层根据序列号在重传存储器 中查找到RLC层序列号为8的RLC PDU(即上述N个RLC PDU)，将上述N个RLC PDU的数据域均删除，仅保留N个RLC PDU的包头。
若用户设备的RLC层还没有将N个RLC PDU 8保存到重传存储器内，接收到本设备的PDCP层传输的指示信息，该指示信息指示RLC层删除PDCP PDU 4，则RLC层将N个RLC PDU8的数据域删除，仅保留N个RLC PDU 8的包头。
在应答-重传模式下，用户设备的RLC层重传仅包含包头的N个PDU，避免重传已经失去时效的数据(即N个PDU的数据域部分)，节省无线通信资源。
请参阅图4，图4是本申请实施例公开的又一种数据处理方法的流程示意图。本申请实施例中，步骤401～404的实现可以参考图3中步骤301～304的描述，本申请实施例在下文中不做赘述。在图3的基础上，为了进一步节省无线通信资源，用户设备的RLC层可以将分段后封装成的N个RLC PDU删除到仅余一个RLC PDU，并且将剩余的这个RLC PDU的数据域也进行删除，从而在重传时，仅需传输该剩余的RLC PDU的包头，从而达到了节省无线通信资源的目的。
401、获取RLC层的SDU。
402、为上述SDU分配序列号.
403、将上述SDU分段为N个子数据包。
404、将上述N个子数据包封装成N个RLC PDU。
405、在上述N个RLC PDU中确定一个RLC PDU作为第二PDU。
在本申请实施例中，用户设备的RLC层可从上述N个PDU中随机选择一个PDU作为第二PDU。
作为一种可选的实施方式，RLC层可从上述N个PDU中选择一个包头最小的PDU作为第二PDU，从而在重传时，若只重传第二PDU的包头，可以进一步降低无线通信资源的消耗。
406、将第二PDU中的数据域删除。
407、将上述N个PDU中除第二PDU以外的PDU删除。
作为一种可选的实施方式，在将上述N个PDU中除第二PDU以外的PDU删除之后，修改第二PDU的第二包头中用于指示第二PDU是否分段的指示信息，以指示第二PDU不分段。
作为一种可选的实施方式，在将上述N个PDU中除第二PDU以外的PDU删除之后，删除第二PDU的第二包头中用于指示分段偏移量(Segmentation Offset,SO)的字段。
作为一种可选的实施方式，上述方法还可以适用于，当N个RLC PDU 8中的部分RLC PDU8发送到MAC层时，RLC层接收到PDCP的指示信息，指示丢弃PDCP PDU 4，此时，RLC层将PDCP PDU 4对应的、还没有发往MAC层的另一部分RLC PDU 8进行处理，处理过程如下：
方式一：删除这部分没有发往MAC层的RLC PDU 8，并生成只包含RLC PDU包头的RLC PDU 8，即序列号为8的RLC PDU。
方式二：在这部分没有发往MAC层的RLC PDU 8中，随机选择一个RLC PDU 8作为第三PDU，并删除其他RLC PDU 8，删除第三PDU的数据域，其他类似步骤如上所述。
实施本申请实施例，数据接收方(比如网络设备)接收到仅包含包头的第二PDU后， 可以根据包头中包含的序列号完成数据包排序。
请参阅图5，图5是本申请实施例公开的又一种数据处理方法的流程示意图。其中，步骤501～504的实现可以参考图2中步骤201～204的描述，本申请实施例在下文中不做赘述。与图2中描述的数据处理方法相比，图5中所描述的方法将第一PDU整个删除，再重新构造不包含数据域或数据域极小的第三PDU来替代第一PDU，从而起到节省无线通信资源的作用。
501、获取RLC层的SDU。
502、为上述SDU分配第一序列号。
503、将上述SDU封装成第一PDU，第一PDU包含数据域和第一包头，第一包头中包含第一序列号。
作为一种可选的实施方式，将第一PDU传输至MAC层后，RLC层可将第一PDU存储至重传存储器。
504、将上述第一PDU删除。
505、构造第三PDU，第三PDU包含第三包头，第三包头中包含的序列号与第一序列号相同。
本申请实施例中，RLC层构造第三PDU，且第三PDU不包含数据域，至少包含序列号，而序列号与第一序列号相同。在重传时，传输第三PDU来替代第一PDU，从而起到避免发送冗余数据，节省无线通信资源的作用。
请参阅图6A，图6A为本申请实施例公开的又一种数据处理方法的流程示意图。本申请实施例中，步骤601～604的实现可以参考图2中步骤201～204的描述，本申请实施例在下文中不做赘述。
601、获取RLC层的SDU。
602、为上述SDU分配第一序列号。
603、将上述SDU封装成第一PDU，第一PDU包含数据域和第一包头，第一包头中包含第一序列号。
作为一种可选的实施方式，将第一PDU传输至MAC层后，RLC层可将第一PDU存储至重传存储器。
604、接收到PDCP层用于指示RLC层删除上述SDU的指示信息之后，删除第一PDU。
605、生成用于指示第一PDU已被删除的状态报告，上述状态报告包括第一序列号。
本申请实施例中，用户终端将该状态报告发送至数据接收方，数据接收方在进行数据包排序时，根据该状态报告可以跳过被删除的数据包正常进行数据包排序。
请参阅图6B，图6B为本申请实施例公开的一种状态报告格式的示意图。如图6B所示，状态报告至少包含D/C域，用于指示状态报告为RLC控制PDU；除此之外，还包括用于指示丢弃的数据包的序列号Discard SN域。
作为一种可选的实施方式，若存在多种类型的PDU，则状态报告中还需包括PDU类型(PDU Type)域，用于指示该RLC控制PDU为状态报告，更具体地，用于指示该RLC控制PDU为丢弃数据包的状态报告。
请参阅图6C，图6C为本申请实施例公开的另一种状态报告格式的示意图。如图6C所示，状态报告中除了D/C域和Discard SN域之外，还可以再包含一个比特图(bitmap)，用于指示从序列号为Discard SN的数据包开始，或从序列号为Discard SN的下一个数据包开始，哪些数据包被丢弃(即删除)，哪些数据包没有被丢弃。
举例来说，若Discard SN＝8，bitmap＝100100，则表示序列号为8以及序列号为11的数据包被丢弃，即bitmap中的6个比特，从左到右(或从右到左)分别对应序列号8至13的状态，“1”(或“0“)表示该数据包被丢弃，“0”(或“1”)表示该数据包未被丢弃。
在图6C的基础上，还可以包括PDU类型(PDU Type)域，用于指示该RLC控制PDU为状态报告，更具体地，用于指示该RLC控制PDU为丢弃数据包的状态报告。
请参阅图6D，图6D为本申请实施例公开的又一种状态报告格式的示意图。如图6D所示，状态报告中除了D/C域和Discard SN域之外，还可以再包含一个个数(Number)域，用于指示从序列号为Discard SN的数据包开始(或从Discard SN的数据包的下一个数据包开始)连续丢弃的数据包的个数。
举例来说，若Discard SN＝8，Number＝3，则表示序列号为8，9，10的三个数据包都被丢弃(或表示序列号为8，9，10，11的四个数据包都被丢弃)。
作为数据发送方的设备的RLC层使用状态报告来指示丢弃的RLC SDU或RLC PDU，当数据接受方接收到该状态报告时，不会再等待被丢弃的数据包，能够进行正常的数据包排序。
在图6D的基础上，还可以包括PDU类型(PDU Type)域，用于指示该RLC控制PDU为状态报告，更具体地，用于指示该RLC控制PDU为丢弃数据包的状态报告。
请参阅图7，图7为本申请实施例公开的另一种通信***应用场景的示意图。在5G网络中，网络设备的物理组成为CU-DU架构，在这种架构中，PDCP层可能位于集中式单元(Centralized Unit，CU)，RLC层、MAC层和PHY层位于DU(Distributed Unit，分布式单元)。在这种情况下，仍可应用上述图2～图6D中的数据处理方法。
然而，考虑到CU和DU之间的数据传输会带来较大时延，若PDCP层指示RLC层删除数据包，由于CU和DU之间的数据传输带来的时延可能导致数据包不能及时删除。因此，可以考虑在RLC层设置定时器，以及时执行数据删除操作。
请参阅图8，图8是本申请实施例公开的又一种数据处理方法的流程示意图。
801、CU向DU发送PDCP PDU，PDCP PDU也称作RLC SDU。
在本申请实施例中，上述PDCP PDU到达DU中的RLC层后，即被称作RLC SDU。
802、DU接收到RLC SDU时启动计时操作。
即在RLC层设置针对该RLC PDU的定时器，在DU接收到RLC SDU时启动针对该RLC PDU的定时器。
作为一种可选的实施方式，DU也可在将上述RLC SDU封装成RLC PDU时启动计时操作。
803、若上述计时操作的时间超过预设时间阈值，DU中的RLC层对RLC SDU或RLC SDU封装成RLC PDU进行数据删除。
即当上述针对该RLC SDU的定时器超时时，DU中的RLC层删除RLC SDU或RLC SDU对应的RLC PDU。
作为一种可选的实施方式，上述预设时间阈值根据RLC SDU中包含的数据的时效性要求等特性确定。举例来说，若RLC SDU中包含的数据为语音业务数据，其时效性要求强，则上述预设时间阈值应当设定得较短；若RLC SDU中包含的数据为网页浏览业务数据，其时效性要求弱，则上述预设时间阈值应当设定得较长。
作为一种可选的实施方式，步骤703中的数据删除方式可以参考图2～图5中对RLC PDU执行的操作。除此以外，若此时RLC层还未把RLC SDU封装为RLC PDU，则直接将该RLC SDU删除。
通过图8中所描述的数据处理方法，可以避免CU和DU之间进行数据传输的时延使得DU中的RLC层不能及时执行数据删除操作。
此外，上述实施例还适用于图1的网络架构。
除此之外，在数据传输的过程中，举例来说，若基站作为数据发送方，用户终端作为数据接收方，则基站的RLC层根据上述图2至图6D以及图8中任意一项所示的方法进行数据处理后获得的数据包经MAC层、PHY层和通信链路之后到达作为数据接收方的用户终端。
用户终端的RLC层接收到RLC PDU或状态报告，具体情况有以下几种：
情况一：RLC层接收到序列号为x的RLC PDU，并且该RLC PDU的数据域为空，则RLC层认为(或确定)序列号为x的RLC PDU(或SDU)为已接收，不再等待序列号为x的PDU，转而接收序列号不等于x的PDU，或在生成反馈给数据发送方的状态报告中不对序列号为x的PDU进行反馈。
情况二：RLC实体接收到序列号为x的RLC PDU，并且RLC实体在接收到该RLC PDU之前，已经接收到若干个序列号为x的RLC PDU，若此时接收到的RLC PDU的数据域为空，即RLC实体将所有序列号为x的RLC PDU或RLC PDU中的数据删除，并且认为(或确定)序列号为x的RLC SDU为已接收。
情况三：RLC实体接收到状态报告，RLC实体解析该状态报告后获取到序列号为x的数据包被丢弃的信息，认为(或确定)状态报告中指示被丢弃的数据包x为已接收。
请参阅图9，图9为本申请实施例公开的一种设备900的结构示意图。如图9所示，设备900可以包括获取单元901和删除单元902。
获取单元901，用于获取无线链路控制RLC层的服务数据单元SDU。
删除单元902，用于按照数据删除方式删除数据，上述数据删除方式包括：将上述获取单元获取的上述SDU删除，或者，将上述SDU封装成的第一协议数据单元PDU删除，或者，将第一PDU中的数据域删除。
需要说明的是，上述各个单元的实现还可以对应参照图2至图6D以及图8所示的方法实施例的相应描述。
设备900的无线链路控制层可以根据不同的数据删除方式，将不需要传输的数据删除，节省了无线通信资源。
请参阅图10，图10为本申请实施例公开的一种基站1000的结构示意图。基站1000 可执行如图2至图6D以及图8的方法中的操作。
基站1000包括一个或多个远端射频单元(remote radio unit,RRU)1001和一个或多个基带单元(baseband unit，BBU)1002。上述RRU1001可以称为收发单元、收发机、收发电路、或者收发器等等，其可以包括至少一个天线1011和射频单元1012。上述RRU1001部分主要用于射频信号的收发以及射频信号与基带信号的转换。上述BBU1002部分主要用于进行基带处理，对基站进行控制等。上述RRU1001与BBU1002可以是物理上设置在一起，也可以物理上分离设置的，即分布式基站。
上述BBU1002为基站的控制中心，也可以称为处理单元，主要用于完成基带处理功能，如信道编码，复用，调制，扩频等等。例如上述BBU(处理单元)可以用于控制基站执行图2至图6D以及图8所示的流程。
在一个示例中，上述BBU1002可以由一个或多个单板构成，多个单板可以共同支持单一接入制式的无线接入网(如LTE网)，也可以分别支持不同接入制式的无线接入网。上述BBU1002还包括存储器1021和处理器1022。上述存储器1021用以存储必要的消息和数据。上述处理器1022用于控制基站进行必要的动作，例如控制基站执行图2至图6D以及图8所示的流程。上述存储器1021和处理器1022可以服务于一个或多个单板。也就是说，可以每个单板上单独设置存储器和处理器。也可以是多个单板公用相同的存储器和处理器。此外每个单板上还设置有必要的电路。
请参阅图11，图11为本申请实施例公开的一种终端1100的结构示意图。该终端可执行图2至图6D以及图8示出的方法中的终端的操作。
为了便于说明，图11仅示出了终端的主要部件。如图11所示，终端1100包括处理器、存储器、控制电路、天线以及输入输出装置。处理器主要用于对通信协议以及通信数据进行处理，以及对整个用户设备进行控制，执行软件程序，处理软件程序的数据，例如用于支持终端执行图2至图6D以及图8所描述的流程。存储器主要用于存储软件程序和数据。控制电路主要用于基带信号与射频信号的转换以及对射频信号的处理。控制电路和天线一起也可以叫做收发器，主要用于收发电磁波形式的射频信号。终端1100还具有输入输出装置，例如触摸屏、显示屏，键盘等主要用于接收用户输入的数据以及对用户输出数据。
当终端开机后，处理器可以读取存储单元中的软件程序，解释并执行软件程序的，处理软件程序的数据。当需要通过无线发送数据时，处理器对待发送的数据进行基带处理后，输出基带信号至射频电路，射频电路将基带信号进行射频处理后将射频信号通过天线以电磁波的形式向外发送。当有数据发送到终端时，射频电路通过天线接收到射频信号，将射频信号转换为基带信号，并将基带信号输出至处理器，处理器将基带信号转换为数据并对该数据进行处理。
本领域技术人员可以理解，为了便于说明，图11仅示出了一个存储器和处理器。在实际的终端中，可以存在多个处理器和存储器。存储器也可以称为存储介质或者存储设备等，本申请实施例对此不做限制。
作为一种可选的实现方式，处理器可以包括基带处理器和中央处理器，基带处理器主要用于对通信协议以及通信数据进行处理，中央处理器主要用于对整个终端进行控制，执 行软件程序，处理软件程序的数据。图11中的处理器集成了基带处理器和中央处理器的功能，本领域技术人员可以理解，基带处理器和中央处理器也可以是各自独立的处理器，通过总线等技术互联。本领域技术人员可以理解，终端可以包括多个基带处理器以适应不同的网络制式，终端可以包括多个中央处理器以增强其处理能力，终端的各个部件可以通过各种总线连接。上述基带处理器也可以表述为基带处理电路或者基带处理芯片。上述中央处理器也可以表述为中央处理电路或者中央处理芯片。对通信协议以及通信数据进行处理的功能可以内置在处理器中，也可以以软件程序的形式存储在存储单元中，由处理器执行软件程序以实现基带处理功能。
示例性的，在发明实施例中，可以将具有收发功能的天线和控制电路视为终端1100的收发单元1101，将具有处理功能的处理器视为终端1100的处理单元1102。如图11所示，终端1100包括收发单元1101和处理单元1102。收发单元也可以称为收发器、收发机、收发装置等。可选的，可以将收发单元1101中用于实现接收功能的器件视为接收单元，将收发单元1101中用于实现发送功能的器件视为发送单元，即收发单元1101包括接收单元和发送单元。示例性的，接收单元也可以称为接收机、接收器、接收电路等，发送单元可以称为发射机、发射器或者发射电路等。
终端1100的无线链路控制层可以根据不同的数据删除方式，将不需要传输的数据删除，节省了无线通信资源。
本申请实施例公开了一种调度请求发送方法与设备，其中，该方法包括：终端设备接收网络设备发送的调度请求配置消息，所述配置消息中包含调度请求的重复发送时长、调度请求资源周期、调度请求禁止定时器时长；终端设备根据所述调度请求配置消息分别重复发送第一调度请求和第二调度请求，其中，所述终端设备在开始重复发送所述第一调度请求时启动所述调度请求禁止定时器，所述终端设备在所述调度请求禁止定时器超时后，且在所述第一调度请求发送完成后发送所述第二调度请求。采用本申请实施例，可以避免发送调度请求的冲突，提高调度请求接收的成功率，降低无线通信资源消耗。
1、一种调度请求发送方法，其特征在于，包括：
终端设备接收网络设备发送的调度请求配置消息，所述配置消息中包含调度请求的重复发送时长、调度请求资源周期、调度请求禁止定时器时长；
终端设备根据所述调度请求配置消息分别重复发送第一调度请求和第二调度请求，其中，所述终端设备在开始重复发送所述第一调度请求时启动所述调度请求禁止定时器，所述终端设备在所述调度请求禁止定时器超时后，且在所述第一调度请求发送完成后发送所述第二调度请求。
2、根据权利要求1所述的方法，其特征在于：
所述重复发送时长小于或等于所述调度请求禁止定时器时长。
3、根据权利要求1所述的方法，其特征在于：
所述重复发送时长大于所述调度请求禁止定时器时长；
所述所述终端设备在所述调度请求禁止定时器超时后，且在所述第一调度请求发送完成后发送所述第二调度请求，包括：
所述终端设备放弃使用在重复发送所述第一调度请求时出现的调度请求资源来发送调度请求；或者，所述终端设备在所述调度请求禁止定时器时长内发送所述第一调度请求和/或第二调度请求；或者，所述终端设备的媒体接入控制层在物理层重复发送所述第一调度请求时放弃向物理层指示发送调度请求。
4、根据权利要求2所述的方法，其特征在于，所述禁止定时器时长为所述调度请求资源周期与非负整数的乘积，所述调度请求资源周期包含第一调度请求资源周期和第二调度请求资源周期，其中，所述第一调度请求资源周期大于所述第二调度请求资源周期，所述非负整数包含第一非负整数和第二非负整数，所述第一非负整数大于所述第二非负整数；
则所述重复发送时长小于或等于所述调度请求禁止定时器时长，包括：
所述调度请求禁止定时器时长为所述第一调度请求资源周期与所述非负整数的乘积；或者，所述调度请求禁止定时器时长为所述禁止定时器时长与所述第一非负整数的乘积。
5、一种调度请求接收方法，其特征在于，包括：
网络设备向终端设备发送调度请求配置消息，所述配置消息中包含调度请求的重复发送时长、调度请求资源周期、调度请求禁止定时器时长；
所述网络设备根据所述调度请求配置消息接收所述终端设备分别重复发送的第一调度请求和第二调度请求，其中，所述重复发送时长小于或等于所述调度请求禁止定时器时长。
6、根据权利要求5所述的方法，其特征在于，所述禁止定时器时长为所述调度请求资源周期与非负整数的乘积，所述调度请求资源周期包含第一调度请求资源周期和第二调度请求资源周期，其中，所述第一调度请求资源周期大于所述第二调度请求资源周期，所述非负整数包含第一非负整数和第二非负整数，所述第一非负整数大于所述第二非负整数；
则所述重复发送时长小于或等于所述调度请求禁止定时器时长，包括：
所述调度请求禁止定时器时长为所述第一调度请求资源周期与所述非负整数的乘积；或者，所述调度请求禁止定时器时长为所述禁止定时器时长与所述第一非负整数的乘积。
7、一种终端设备，其特征在于，包括：
接收单元和发送单元，
所述接收单元用于接收网络设备发送的调度请求配置消息，所述配置消息中包含调度请求的重复发送时长、调度请求资源周期、调度请求禁止定时器时长；
所述发送单元用于根据所述调度请求配置消息分别重复发送第一调度请求和第二调度请求，其中，所述发送单元在开始重复发送所述第一调度请求时启动所述调度请求禁止定时器，所述发送单元在所述调度请求禁止定时器超时后，且在所述第一调度请求发送完成后发送所述第二调度请求。
8、根据权利要求7所述的终端设备，其特征在于：
所述重复发送时长小于或等于所述调度请求禁止定时器时长。
9、根据权利要求7所述的终端设备，其特征在于：
所述重复发送时长大于所述调度请求禁止定时器时长；
所述所述发送单元在所述调度请求禁止定时器超时后，且在所述第一调度请求发送完成后发送所述第二调度请求，包括：
所述发送单元放弃使用在重复发送所述第一调度请求时出现的调度请求资源来发送调度请求；或者，所述发送单元在所述调度请求禁止定时器时长内发送所述第一调度请求和/或第二调度请求；或者，所述终端设备的媒体接入控制层在物理层重复发送所述第一调度请求时放弃向物理层指示发送调度请求。
10、根据权利要求8所述的方法，其特征在于，所述禁止定时器时长为所述调度请求资源周期与非负整数的乘积，所述调度请求资源周期包含第一调度请求资源周期和第二调度请求资源周期，其中，所述第一调度请求资源周期大于所述第二调度请求资源周期，所述非负整数包含第一非负整数和第二非负整数，所述第一非负整数大于所述第二非负整数；
则所述重复发送时长小于或等于所述调度请求禁止定时器时长，包括：
所述调度请求禁止定时器时长为所述第一调度请求资源周期与所述非负整数的乘积；或者，所述调度请求禁止定时器时长为所述禁止定时器时长与所述第一非负整数的乘积。
11、一种网络设备，其特征在于，包括：
发送单元和接收单元，
所述发送单元用于向终端设备发送调度请求配置消息，所述配置消息中包含调度请求的重复发送时长、调度请求资源周期、调度请求禁止定时器时长；
所述接收单元用于根据所述调度请求配置消息接收所述终端设备分别重复发送的第一调度请求和第二调度请求，其中，所述重复发送时长小于或等于所述调度请求禁止定时器时长。
12、根据权利要求11所述的方法，其特征在于，所述禁止定时器时长为所述调度请求资源周期与非负整数的乘积，所述调度请求资源周期包含第一调度请求资源周期和第二调度请求资源周期，其中，所述第一调度请求资源周期大于所述第二调度请求资源周期，所述非负整数包含第一非负整数和第二非负整数，所述第一非负整数大于所述第二非负整数；
则所述重复发送时长小于或等于所述调度请求禁止定时器时长，包括：
所述调度请求禁止定时器时长为所述第一调度请求资源周期与所述非负整数的乘积；或者，所述调度请求禁止定时器时长为所述禁止定时器时长与所述第一非负整数的乘积。
现有技术中，当用户设备(User Equipment,UE)(或称为终端设备)需要向演进型基站(evolved Node B,eNB)发送上行数据时，UE需要向eNB请求资源，即向eNB发送缓存状态报告(Buffer Status Report,BSR)来指示UE当前的数据量。若此时UE没有发送BSR的资源，则UE需要向eNB发送调度请求(Scheduling Request,SR)来向eNB请求发送BSR的资源。在连接态，eNB会配置给每个UE发送SR的资源。在长期演进(Long Term Evolution,LTE)通信***中，UE在一个子帧就可以发送完成SR，而在机器类型通信(Machine Type Communication,MTC)中，由于UE处于信号覆盖较差的区域，UE需要重复向eNB发送SR。考虑到eNB为UE配置的SR资源是周期出现的，若UE触发SR重复发送后，没有接收到eNB的资源分配消息，则UE会在SR资源出现时再次向eNB发送新的SR，若UE重复发送SR的时间比SR资源的周期长，或UE重复发送SR的时间比eNB允许UE发送SR的间隔时间长，则UE在前一次SR还没有发送完成时，即会触发新的SR发送，造成SR发送冲突，降低eNB接收SR的成功率。
本申请实施例提供了一种调度请求发送方法及设备，采用本申请实施例，可以避免发送调度请求的冲突，提高调度请求接收的成功率。
第一方面，本申请实施例提供了一种调度请求发送方法，包括：
终端设备接收网络设备发送的调度请求配置消息，所述配置消息中包含调度请求的重复发送时长、调度请求资源周期、调度请求禁止定时器时长；
终端设备根据所述调度请求配置消息分别重复发送第一调度请求和第二调度请求，其中，所述终端设备在开始重复发送所述第一调度请求时启动所述调度请求禁止定时器，所述终端设备在所述调度请求禁止定时器超时后，且在所述第一调度请求发送完成后发送所述第二调度请求。
作为一种可选的实施方式，所述重复发送时长小于或等于所述调度请求禁止定时器时长。
作为一种可选的实施方式，所述重复发送时长大于所述调度请求禁止定时器时长；所述终端设备在所述调度请求禁止定时器超时后，且在所述第一调度请求发送完成后发送所述第二调度请求，包括：
所述终端设备放弃使用在重复发送所述第一调度请求时出现的调度请求资源来发送调度请求；
作为一种可选的实施方式，所述重复发送时长大于所述调度请求禁止定时器时长；所述终端设备在所述调度请求禁止定时器超时后，且在所述第一调度请求发送完成后发送所述第二调度请求，包括：
所述终端设备在所述调度请求禁止定时器时长内发送所述第一调度请求和/或第二调度请求；
作为一种可选的实施方式，所述重复发送时长大于所述调度请求禁止定时器时长；所述终端设备在所述调度请求禁止定时器超时后，且在所述第一调度请求发送完成后发送所述第二调度请求，包括：
所述终端设备的媒体接入控制层在物理层重复发送所述第一调度请求时放弃向物理层指示发送调度请求。
作为一种可选的实施方式，所述禁止定时器时长为所述调度请求资源周期与非负整数的乘积，所述调度请求资源周期包含第一调度请求资源周期和第二调度请求资源周期，其中，所述第一调度请求资源周期大于所述第二调度请求资源周期，所述非负整数包含第一非负整数和第二非负整数，所述第一非负整数大于所述第二非负整数；
则所述重复发送时长小于或等于所述调度请求禁止定时器时长，包括：
所述调度请求禁止定时器时长为所述第一调度请求资源周期与所述非负整数的乘积；
作为一种可选的实施方式，所述禁止定时器时长为所述调度请求资源周期与非负整数的乘积，所述调度请求资源周期包含第一调度请求资源周期和第二调度请求资源周期，其中，所述第一调度请求资源周期大于所述第二调度请求资源周期，所述非负整数包含第一非负整数和第二非负整数，所述第一非负整数大于所述第二非负整数；
则所述重复发送时长小于或等于所述调度请求禁止定时器时长，包括：
所述调度请求禁止定时器时长为所述禁止定时器时长与所述第一非负整数的乘积。
第二方面，本申请提供一种调度请求接收方法，包括：
网络设备向终端设备发送调度请求配置消息，所述配置消息中包含调度请求的重复发送时长、调度请求资源周期、调度请求禁止定时器时长；
所述网络设备根据所述调度请求配置消息接收所述终端设备分别重复发送的第一调度请求和第二调度请求，其中，所述重复发送时长小于或等于所述调度请求禁止定时器时长。
作为一种可选的实施方式，所述禁止定时器时长为所述调度请求资源周期与非负整数的乘积，所述调度请求资源周期包含第一调度请求资源周期和第二调度请求资源周期，其中，所述第一调度请求资源周期大于所述第二调度请求资源周期，所述非负整数包含第一非负整数和第二非负整数，所述第一非负整数大于所述第二非负整数；
则所述重复发送时长小于或等于所述调度请求禁止定时器时长，包括：
所述调度请求禁止定时器时长为所述第一调度请求资源周期与所述非负整数的乘积；
作为一种可选的实施方式，所述禁止定时器时长为所述调度请求资源周期与非负整数的乘积，所述调度请求资源周期包含第一调度请求资源周期和第二调度请求资源周期，其中，所述第一调度请求资源周期大于所述第二调度请求资源周期，所述非负整数包含第一非负整数和第二非负整数，所述第一非负整数大于所述第二非负整数；
则所述重复发送时长小于或等于所述调度请求禁止定时器时长，包括：
所述调度请求禁止定时器时长为所述禁止定时器时长与所述第一非负整数的乘积。
第三方面，本申请提供一种终端设备，包括：
接收单元和发送单元，
所述接收单元用于接收网络设备发送的调度请求配置消息，所述配置消息中包含调度请求的重复发送时长、调度请求资源周期、调度请求禁止定时器时长；
所述发送单元用于根据所述调度请求配置消息分别重复发送第一调度请求和第二调度请求，其中，所述发送单元在开始重复发送所述第一调度请求时启动所述调度请求禁止定时器，所述发送单元在所述调度请求禁止定时器超时后，且在所述第一调度请求发送完成后发送所述第二调度请求。
作为一种可选的实施方式，所述重复发送时长小于或等于所述调度请求禁止定时器时长。
作为一种可选的实施方式，所述重复发送时长大于所述调度请求禁止定时器时长；
所述所述发送单元在所述调度请求禁止定时器超时后，且在所述第一调度请求发送完成后发送所述第二调度请求，包括：
所述发送单元放弃使用在重复发送所述第一调度请求时出现的调度请求资源来发送调度请求；
作为一种可选的实施方式，所述重复发送时长大于所述调度请求禁止定时器时长；
所述所述发送单元在所述调度请求禁止定时器超时后，且在所述第一调度请求发送完成后发送所述第二调度请求，包括：
所述发送单元在所述调度请求禁止定时器时长内发送所述第一调度请求和/或第二调 度请求；
作为一种可选的实施方式，所述重复发送时长大于所述调度请求禁止定时器时长；
所述所述发送单元在所述调度请求禁止定时器超时后，且在所述第一调度请求发送完成后发送所述第二调度请求，包括：
所述终端设备的媒体接入控制层在物理层重复发送所述第一调度请求时放弃向物理层指示发送调度请求。
作为一种可选的实施方式，所述禁止定时器时长为所述调度请求资源周期与非负整数的乘积，所述调度请求资源周期包含第一调度请求资源周期和第二调度请求资源周期，其中，所述第一调度请求资源周期大于所述第二调度请求资源周期，所述非负整数包含第一非负整数和第二非负整数，所述第一非负整数大于所述第二非负整数；
则所述重复发送时长小于或等于所述调度请求禁止定时器时长，包括：
所述调度请求禁止定时器时长为所述第一调度请求资源周期与所述非负整数的乘积；
作为一种可选的实施方式，所述禁止定时器时长为所述调度请求资源周期与非负整数的乘积，所述调度请求资源周期包含第一调度请求资源周期和第二调度请求资源周期，其中，所述第一调度请求资源周期大于所述第二调度请求资源周期，所述非负整数包含第一非负整数和第二非负整数，所述第一非负整数大于所述第二非负整数；
则所述重复发送时长小于或等于所述调度请求禁止定时器时长，包括：
所述调度请求禁止定时器时长为所述禁止定时器时长与所述第一非负整数的乘积。
第四方面，本申请提供一种网络设备，包括：
发送单元和接收单元，
所述发送单元用于向终端设备发送调度请求配置消息，所述配置消息中包含调度请求的重复发送时长、调度请求资源周期、调度请求禁止定时器时长；
所述接收单元用于根据所述调度请求配置消息接收所述终端设备分别重复发送的第一调度请求和第二调度请求，其中，所述重复发送时长小于或等于所述调度请求禁止定时器时长。
作为一种可选的实施方式，所述禁止定时器时长为所述调度请求资源周期与非负整数的乘积，所述调度请求资源周期包含第一调度请求资源周期和第二调度请求资源周期，其中，所述第一调度请求资源周期大于所述第二调度请求资源周期，所述非负整数包含第一非负整数和第二非负整数，所述第一非负整数大于所述第二非负整数；
则所述重复发送时长小于或等于所述调度请求禁止定时器时长，包括：
所述调度请求禁止定时器时长为所述第一调度请求资源周期与所述非负整数的乘积；
作为一种可选的实施方式，所述禁止定时器时长为所述调度请求资源周期与非负整数的乘积，所述调度请求资源周期包含第一调度请求资源周期和第二调度请求资源周期，其中，所述第一调度请求资源周期大于所述第二调度请求资源周期，所述非负整数包含第一非负整数和第二非负整数，所述第一非负整数大于所述第二非负整数；
则所述重复发送时长小于或等于所述调度请求禁止定时器时长，包括：
所述调度请求禁止定时器时长为所述禁止定时器时长与所述第一非负整数的乘积。
作为一种可选的实施方式，本申请提供的终端设备和网络设备可以包含用于执行上述方法设计中步骤的单元。所述单元可以是软件和/或是硬件。可选地，本申请提供的终端设备和网络设备的结构中包括处理器和收发器，所述处理器被配置为支持终端设备和网络设备执行上述方法中相应的功能。所述收发器用于支持网络设备与终端设备之间的通信，向网络设备发送上述方法中所涉及的信息或者消息。终端设备中还可以包括存储器，所述存储器用于与处理器耦合，其保存终端设备必要的程序消息和数据。
第五方面，本申请实施例提供了一种包含消息的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
第六方面，本申请实施例提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有消息，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
通过实施本申请实施例，可以避免发送调度请求的冲突，提高调度请求接收的成功率。
下面结合本申请实施例中的附图对本申请实施例进行描述。
请参阅图12，图12为本申请实施例公开的一种通信***应用场景的示意图。该通信***可应用LTE网络或下一代(Next Generation,NR或称为5G)网络。如图12所示，终端设备通过网络设备，如LTE中的演进型基站(Evolved Node B，eNB)接入到网络，通过与eNB进行交互实现数据的发送与接收。在5G***中，基站还可以为5G基站gNB。
上述终端设备可为手机、智能终端、多媒体设备和流媒体设备等，本申请实施例不做限定。而上述eNB是LTE网络中用户终端和演进后的分组核心网(Evolved Packet Core，EPC)之间的桥梁，eNB之间通过X2接口进行连接，其主要功能有：无线资源管理、IP头压缩及用户数据流加密、用户终端附着时的移动性管理实体(Mobility Management Entity，MME)选择、路由用户面数据至服务网关(Serving Gateway，S-GW)、寻呼消息的组织和发送、广播消息的组织和发送、以移动性或调度为目的的测量及测量报告配置等。
请参阅图13，图13为与本申请实施例相关的现有技术中的调度请求(Scheduling Request,SR)资源的配置示意图。现有技术中，当用户设备(User Equipment,UE)(或称为终端设备)需要向演进型基站(evolved Node B,eNB)发送上行数据时，UE需要向eNB请求资源，即向eNB发送缓存状态报告(Buffer Status Report,BSR)来指示UE当前的数据量。若此时UE没有发送BSR的资源，则UE需要向eNB发送调度请求(Scheduling Request,SR)来向eNB请求发送BSR的资源。在连接态，eNB会配置给每个UE发送SR的资源，其资源配置方式如图13所示。eNB为UE配置SR资源的周期(SR PERIODICITY)和偏置量(N OFFSET,SR)，UE在***帧号(System Frame Number,SFN)和子帧号(Subframe,sf)满足以下公式的子帧上发送SR：
(SFN×10+sf–N OFFSET,SR)mod S RPERIODICITY＝0
其中，mod是取模运算或取余运算。
以图13为例，其中N OFFSET,SR＝1，S RPERIODICITY＝5，则UE可以在每个***帧的子帖1和子帧6上发送SR。
在现有技术中，N OFFSET,SR和S RPERIODICITY还可以配置其他值，如表1所示。
表1
Figure PCTCN2018085611-appb-000001
由表F1可以，当前SR资源最大周期为80毫秒(millisecond,ms)。
eNB向UE配置SR配置索引，即可对应配置SR周期和偏移量。例如，eNB向UE配置SR配置索引I SR＝16，可知，其对应SR配置索引为(15-34)的行，此时SR PERIODICITY＝20ms，N OFFSET,SR＝I SR–15＝16–15＝1，即图14所示的SR资源配置。
此外，现在技术中，eNB还为UE配置一个调度请求禁止定时器(sr-ProhibitTimer)，当UE开始发送SR时，UE启动这个定时器，在这个定时器运行期间，UE不可以发送SR，即使当前UE有有效的SR资源，只有当这个定时器超时后，当UE需要发送SR，且UE有有效的SR资源时，UE才可以发送SR。其中，现在技术中，这个定时器的时长是通过SR周期与非负整数的乘积确定的，当前这个非负整数的取值范围为[0,1,2,3,4,5,6,7]。
在长期演进(Long Term Evolution,LTE)通信***中，UE在一个子帧就可以将SR发送完成，而在机器类型通信(Machine Type Communication,MTC)中，由于UE处于信号覆盖较差的区域，UE需要重复向eNB发送SR，如图15所示，eNB为UE配置了图14所示的SR资源，当UE需要发送SR时，例如，UE在第12号***帧的第1号子帧开始发送SR，由于UE处于信号较弱区域，UE需要重复向eNB发送SR，例如eNB配置UE发送SR的次数为10次，如图15所示，则UE从第12号***帧的第1号子帧开始发送SR，在接下来的9个子帧(或10个上行有效子帧)上共连续发送9次SR，即共发送10次SR。现有技术中，eNB配置UE重复发送SR的次数可以为16，32，64，128。
参阅图16，考虑到eNB为UE配置的SR资源是周期出现的，若UE触发SR重复发送后，没有接收到eNB的资源分配消息，则UE会在SR资源出现且调度请求禁止定时器超时后再次向eNB发送新的SR。此处，假设非负整数为1，即调度请求禁止定时器时长为一个SR周期。若UE重复发送SR的时间比SR资源的周期长，或UE重复发送SR的时间比eNB允许UE发送SR的间隔时间长，则UE在前一次SR还没有发送完成时，即会触发新的SR发送，造成SR发送冲突，降低eNB接收SR的成功率。以图16为例，此时eNB配置SR周期为5ms，偏移量为1个子帧，即1ms，SR重复发送次数为8，调度请求禁止定时器时长为5ms。UE在第12号***帧的第1号子帧开始发送SR，并持续发送8次。而在第12号***帧的第5号子帧上，由于UE没有收到eNB的资源分配消息，并且此时UE有有效的SR资源，则又会触发UE重复发送SR，而此时，UE前一次SR的重复发送还没有结束，又会触发新的SR发 送，造成SR发送冲突。
针对上述SR发送冲突问题，本申请公开以下实施例用于解决上述冲突问题。
实施例一
参阅图17，图17是本申请实施例公开的一种调度请求发送方法的流程示意图。该方法的执行主体为终端设备。
171、终端设备接收网络设备发送的调度请求配置消息，所述配置消息中包含调度请求的重复发送时长、调度请求资源周期、调度请求禁止定时器时长；
此处，终端设备以UE为例来说明，网络设备以eNB为例来说明。在连接态，eNB会配置UE周期性的SR资源。例如，UE接收eNB发送的无线资源控制(Radio Resource Control,RRC)的连接重配置消息(RRCConnectionReconfiguration)，其中包含调度请求配置消息(schedulingRequestConfig)，具体地，包含调度请求的重复发送时长、调度请求资源周期、调度请求禁止定时器时长，这些信息可以包含在一条消息中，也可以包含在多条消息中，本申请不作限定，这些消息统称为调度请求配置消息。其中，调度请求的重复发送时长可以是调度请求的重复发送次数，因为调度请求是在物理上行控制信道(Physical Uplink Control Channel,PUCCH)上发送的，所以调度请求的重复发送次数还可以是PUCCH的重复发送次数。此处，可以理解为次数是与子帧数对应的，例如重复发送10次，即在10个子帧上发送10次。或者，重复发送时长可以是从第一次发送到最后一次发送所经历的时间，即调度请求可以是在连续的上行子帧上发送的，如FDD，也可以是在非连续的上行子帧上发送的，如TDD，调度请求资源周期可以通过查表来获取，即eNB可以配置UE一个对应调度请求资源周期的索引，UE通过索引值来确定调度请求资源周期，如表F1所示。调度请求禁止定时器时长可以是具体的时间长度，也可以由调度请求资源周期与非负整数的乘积来确定。调度请求禁止定时器时长可以理解为一段连续的时间，也可以理解为若干非连续的上行子帧的时间。
172、终端设备根据所述调度请求配置消息分别重复发送第一调度请求和第二调度请求，其中，所述终端设备在开始重复发送所述第一调度请求时启动所述调度请求禁止定时器，所述终端设备在所述调度请求禁止定时器超时后，且在所述第一调度请求发送完成后发送所述第二调度请求。
该第一调度请求为UE最开始或前一次发送的SR，第二调度请求为UE在重复发送完第一调度请求之后(或UE在重复发送第一调度请求的过程中)，由于没有接收到eNB的资源分配消息，当UE有有效的SR资源，且调度请求禁止定时器超时后，UE再一次发送的SR。在本申请中，规定了UE要在第一调度请求发送完成后，且在所述调度请求禁止定时器超时后，才可以发送第二调度请求。其中对第一调度请求发送完成的理解，详见以下实施例。
通过实施本申请实施例，可以避免发送调度请求的冲突，提高调度请求接收的成功率。
实施例二
图18是本申请实施例公开的又一种调度请求发送方法的示意图。在实施例一的基础上，所述重复发送时长小于或等于所述调度请求禁止定时器时长。具体地，在图18中，SR重复发送时长为6个子帧，即6ms。SR禁止定时器时长为10个子帧，即10ms。SR禁止定 时器运行期间，UE不会再触发新的SR发送。这样一来，由于SR重复发送时长小于SR禁止定时器时长，所以UE能够在触发下一次SR重复发送之前将本次SR重复发送完成，即前一次SR重复发送不会与后一次SR重复发送产生冲突。这样一来，UE在第一调度请求(即前一次SR)发送完成后，且在调度请求禁止定时器超时后，可以正常触发并发送第二调度请求(即后一次SR)。
通过实施本申请实施例，可以避免发送调度请求的冲突，提高调度请求接收的成功率。
实施例三
图19是本申请实施例公开的又一种调度请求发送方法的示意图。在实施例一的基础上，所述重复发送时长大于所述调度请求禁止定时器时长。
作为一种可行的实施方式，具体地，在图19中，eNB配置的SR重复发送时长为7个子帧，即7ms。SR禁止定时器时长为5个子帧，即5ms。SR禁止定时器运行期间，UE不会再触发新的SR发送。但在SR禁止定时器超时后，若UE还没有接收到eNB的资源配置消息，那么，UE会在有效的SR资源上继续触发并发送SR。而图19中，UE先在第12号***帧的第1号子帧上触发SR发送，连续7个子帧重复发送SR。在第12号***帧的第6号子帧上，若UE没有接收到eNB的资源配置消息，此时由于SR禁止定时器已经超时，则UE会再次触发SR发送，这样就会与前一次重复发送的SR产生冲突。为避免冲突，此时，由于UE前一次SR还没有发送完成，所以UE可以放弃使用前一次SR发送过程中出现的SR资源，即UE继续发送未发送完的前一次SR(即第一SR)。这样一来，UE实际发送的SR时长与eNB配置给UE的SR发送时长是一样的。
若UE完成前一次SR(即第一SR)的重复发送，但仍然没有接收到eNB的资源配置消息，即在第13号***帧的第1号子帧之前，UE都没有接收到eNB的资源配置消息，在第13号***帧的第1号子帧上，UE可以继续触发并发送下一次SR(即第二SR)。
此时，实施例一中的第一调度请求发送完成可以理解为UE按着eNB配置的SR重复发送时长来发送SR，并发送完成，即实际发送SR的时长与配置发送的SR的时长相等。
通过实施本申请实施例，可以避免发送调度请求的冲突，提高调度请求接收的成功率。
作为另一种可行的实施方式，具体地，在图20中，eNB配置的SR重复发送时长为7个子帧，即7ms。SR禁止定时器时长为5个子帧，即5ms。SR禁止定时器运行期间，UE不会再触发新的SR发送。但在SR禁止定时器超时后，若UE还没有接收到eNB的资源配置消息，那么，UE会在有效的SR资源上继续触发并发送SR。而图20中，UE先在第12号***帧的第1号子帧上触发SR发送，连续7个子帧重复发送SR。在第12号***帧的第6号子帧上，若UE没有接收到eNB的资源配置消息，此时由于SR禁止定时器已经超时，则UE会再次触发SR发送，这样就会与前一次重复发送的SR产生冲突。为避免冲突，此时，由于UE前一次SR还没有发送完成，所以UE可以放弃前一次SR(即第一SR)发送，UE触发并发送下一次SR(即第二SR)。这样一来，UE实际发送的SR时长小于eNB配置给UE的SR发送时长。
若UE完成前一次SR(即第一SR)的重复发送，但仍然没有接收到eNB的资源配置消息，即在第12号***帧的第6号子帧之前，UE都没有接收到eNB的资源配置消息，在第 12号***帧的第6号子帧上，UE可以继续触发并发送下一次SR(即第二SR)。
此时，实施例一中的第一调度请求发送完成可以理解为UE按着eNB配置的SR禁止定时器时长来发送SR，当定时器超时，UE停止发送本次SR(即第一SR)，此时UE确定第一SR发送完成。
通过实施本申请实施例，可以避免发送调度请求的冲突，提高调度请求接收的成功率。
作为另一种可行的实施方式，具体地，在图19中，eNB配置的SR重复发送时长为7个子帧，即7ms。SR禁止定时器时长为5个子帧，即5ms。SR禁止定时器运行期间，UE不会再触发新的SR发送。本申请中，所说的触发是UE的媒体接入控制(Media Access Control,MAC)层向UE的物理(Physical,PHY)层指示发送SR。但在SR禁止定时器超时后，若UE还没有接收到eNB的资源配置消息，那么，UE会在有效的SR资源上继续触发并发送SR。而图19中，UE先在第12号***帧的第1号子帧上触发SR发送，连续7个子帧重复发送SR。在第12号***帧的第6号子帧上，若UE没有接收到eNB的资源配置消息，此时由于SR禁止定时器已经超时，则UE会再次触发SR发送，这样就会与前一次重复发送的SR产生冲突。为避免冲突，此时，由于UE前一次SR还没有发送完成，所以UE的媒体接入控制层在物理层重复发送前一次SR(即第一SR)时，放弃向物理层指示发送下一次SR(即第二SR)，即只有当前一次SR(即第一SR)按eNB配置的发送次数发送完成且调度请求禁止定时器超时后，MAC层才向PHY层指示发送后一次SR(即第二SR)。这样一来，UE实际发送的SR时长等于eNB配置给UE的SR发送时长。
若UE完成前一次SR(即第一SR)的重复发送，但仍然没有接收到eNB的资源配置消息，即在第13号***帧的第1号子帧之前，UE都没有接收到eNB的资源配置消息，在第13号***帧的第1号子帧上，UE的MAC层可以继续向PHY指示发送下一次SR(即第二SR)。
此时，实施例一中的第一调度请求发送完成可以理解为UE按着eNB配置的SR重复发送时长来发送SR，并发送完成，即实际发送SR的时长与配置发送的SR的时长相等。
通过实施本申请实施例，可以避免发送调度请求的冲突，提高调度请求接收的成功率。
作为一种可选的实施方式，根据实施例二，所述禁止定时器时长为所述调度请求资源周期与非负整数的乘积，所述调度请求资源周期包含第一调度请求资源周期和第二调度请求资源周期，即eNB可配置的候选调度请求资源周期至少包括两个值，其中一个称为第一调度请求资源周期，另一个称为第二调度请求资源周期。其中，所述第一调度请求资源周期大于所述第二调度请求资源周期，所述非负整数包含第一非负整数和第二非负整数，所述第一非负整数大于所述第二非负整数；
则所述重复发送时长小于或等于所述调度请求禁止定时器时长，包括：
所述调度请求禁止定时器时长为所述第一调度请求资源周期与所述非负整数的乘积；
即eNB在配置UE的调度请求禁止定时器时长和重复发送时长时，要确保重复发送时长小于或等于所述调度请求禁止定时器时长，这样，第一SR与第二SR才不会冲突。本申请中，重复发送时长，还可以是重复发送次数。如果eNB在配置SR禁止定时器时长和SR周期时都有多种选择时，即非负整数有大有小，和/或，SR周期有大有小。若对eNB配置非负整数不作限定，则需要规定eNB在配置SR周期时，使用较大的周期值，即第一调度请求 资源周期。
作为另一种可选的实施方式，根据实施例二，所述禁止定时器时长为所述调度请求资源周期与非负整数的乘积，所述调度请求资源周期包含第一调度请求资源周期和第二调度请求资源周期，即eNB可配置的候选调度请求资源周期至少包括两个值，其中一个称为第一调度请求资源周期，另一个称为第二调度请求资源周期。其中，所述第一调度请求资源周期大于所述第二调度请求资源周期，所述非负整数包含第一非负整数和第二非负整数，所述第一非负整数大于所述第二非负整数；
则所述重复发送时长小于或等于所述调度请求禁止定时器时长，包括：
所述调度请求禁止定时器时长为所述禁止定时器时长与所述第一非负整数的乘积。
即eNB在配置UE的调度请求禁止定时器时长和重复发送时长时，要确保重复发送时长小于或等于所述调度请求禁止定时器时长，这样，第一SR与第二SR才不会冲突。本申请中，重复发送时长，还可以是重复发送次数。如果eNB在配置SR禁止定时器时长和SR周期时都有多种选择时，即非负整数有大有小，和/或，SR周期有大有小。若对eNB配置SR周期不作限定，则需要规定eNB在配置非负整数时，使用较大的整数，即第一非负整数。
通过实施本申请实施例，可以避免发送调度请求的冲突，提高调度请求接收的成功率。
实施例四
参阅图21，图21是本申请实施例公开的一种调度请求发送方法的流程示意图。该方法的执行主体为网络设备。
211、网络设备向终端设备发送调度请求配置消息，所述配置消息中包含调度请求的重复发送时长、调度请求资源周期、调度请求禁止定时器时长；
该步骤中的消息以及参数配置的说明详见实施例一，此处不赘述。
212、所述网络设备根据所述调度请求配置消息接收所述终端设备分别重复发送的第一调度请求和第二调度请求，其中，所述重复发送时长小于或等于所述调度请求禁止定时器时长。
该步骤与实施例一的S102相似，此处不赘述。
通过实施本申请实施例，可以避免发送调度请求的冲突，提高调度请求接收的成功率。
作为一种可选的实施方式，根据实施例四，所述禁止定时器时长为所述调度请求资源周期与非负整数的乘积，所述调度请求资源周期包含第一调度请求资源周期和第二调度请求资源周期，其中，所述第一调度请求资源周期大于所述第二调度请求资源周期，所述非负整数包含第一非负整数和第二非负整数，所述第一非负整数大于所述第二非负整数；
则所述重复发送时长小于或等于所述调度请求禁止定时器时长，包括：
所述调度请求禁止定时器时长为所述第一调度请求资源周期与所述非负整数的乘积；
详细说明见实施例三，此处不赘述。
通过实施本申请实施例，可以避免发送调度请求的冲突，提高调度请求接收的成功率。
作为另一种可选的实施方式，根据实施例四，所述禁止定时器时长为所述调度请求资源周期与非负整数的乘积，所述调度请求资源周期包含第一调度请求资源周期和第二调度请求资源周期，其中，所述第一调度请求资源周期大于所述第二调度请求资源周期，所述 非负整数包含第一非负整数和第二非负整数，所述第一非负整数大于所述第二非负整数；
则所述重复发送时长小于或等于所述调度请求禁止定时器时长，包括：
所述调度请求禁止定时器时长为所述禁止定时器时长与所述第一非负整数的乘积。
详细说明见实施例三，此处不赘述。
通过实施本申请实施例，可以避免发送调度请求的冲突，提高调度请求接收的成功率。
图22为本申请实施例公开的一种终端设备2200的结构示意图。该终端设备包括接收单元2201和发送单元2202。
所述接收单元用于接收网络设备发送的调度请求配置消息，所述配置消息中包含调度请求的重复发送时长、调度请求资源周期、调度请求禁止定时器时长；
该终端设备涉及的消息以及参数配置的说明详见实施例一，此处不赘述。
所述发送单元用于根据所述调度请求配置消息分别重复发送第一调度请求和第二调度请求，其中，所述发送单元在开始重复发送所述第一调度请求时启动所述调度请求禁止定时器，所述发送单元在所述调度请求禁止定时器超时后，且在所述第一调度请求发送完成后发送所述第二调度请求。
该终端设备涉及的消息以及参数配置的说明详见实施例一，此处不赘述。
作为一种可选的实施方式，在图22所示的终端设备的基础上，所述重复发送时长小于或等于所述调度请求禁止定时器时长，详见实施例二。此时的终端设备记作210。
作为另一种可选的实施方式，在图22所示的终端设备的基础上，所述重复发送时长大于所述调度请求禁止定时器时长；
所述所述发送单元在所述调度请求禁止定时器超时后，且在所述第一调度请求发送完成后发送所述第二调度请求，包括：
所述发送单元放弃使用在重复发送所述第一调度请求时出现的调度请求资源来发送调度请求，详见实施例三。
作为另一种可选的实施方式，在图22所示的终端设备的基础上，所述重复发送时长大于所述调度请求禁止定时器时长；
所述所述发送单元在所述调度请求禁止定时器超时后，且在所述第一调度请求发送完成后发送所述第二调度请求，包括：
所述发送单元在所述调度请求禁止定时器时长内发送所述第一调度请求和/或第二调度请求，详见实施例三。
作为另一种可选的实施方式，在终端设备210的基础上，所述禁止定时器时长为所述调度请求资源周期与非负整数的乘积，所述调度请求资源周期包含第一调度请求资源周期和第二调度请求资源周期，其中，所述第一调度请求资源周期大于所述第二调度请求资源周期，所述非负整数包含第一非负整数和第二非负整数，所述第一非负整数大于所述第二非负整数；
则所述重复发送时长小于或等于所述调度请求禁止定时器时长，包括：
所述调度请求禁止定时器时长为所述第一调度请求资源周期与所述非负整数的乘积，详见实施例三。
作为另一种可选的实施方式，在终端设备210的基础上，所述禁止定时器时长为所述调度请求资源周期与非负整数的乘积，所述调度请求资源周期包含第一调度请求资源周期和第二调度请求资源周期，其中，所述第一调度请求资源周期大于所述第二调度请求资源周期，所述非负整数包含第一非负整数和第二非负整数，所述第一非负整数大于所述第二非负整数；
则所述重复发送时长小于或等于所述调度请求禁止定时器时长，包括：
所述调度请求禁止定时器时长为所述禁止定时器时长与所述第一非负整数的乘积，详见实施例三。
图23为本申请实施例公开的一种网络设备2300的结构示意图。该网络设备包括发送单元2301和接收单元2302。
所述发送单元用于向终端设备发送调度请求配置消息，所述配置消息中包含调度请求的重复发送时长、调度请求资源周期、调度请求禁止定时器时长；
该网络设备涉及的消息以及参数配置的说明详见实施例四，此处不赘述。
所述接收单元用于根据所述调度请求配置消息接收所述终端设备分别重复发送的第一调度请求和第二调度请求，其中，所述重复发送时长小于或等于所述调度请求禁止定时器时长。
该网络设备涉及的消息以及参数配置的说明详见实施例四，此处不赘述。
作为一种可选的实施方式，在图23所示的网络设备的基础上，所述禁止定时器时长为所述调度请求资源周期与非负整数的乘积，所述调度请求资源周期包含第一调度请求资源周期和第二调度请求资源周期，其中，所述第一调度请求资源周期大于所述第二调度请求资源周期，所述非负整数包含第一非负整数和第二非负整数，所述第一非负整数大于所述第二非负整数；
则所述重复发送时长小于或等于所述调度请求禁止定时器时长，包括：
所述调度请求禁止定时器时长为所述第一调度请求资源周期与所述非负整数的乘积，详见实施例四。
作为另一种可选的实施方式，在图23所示的网络设备的基础上，所述禁止定时器时长为所述调度请求资源周期与非负整数的乘积，所述调度请求资源周期包含第一调度请求资源周期和第二调度请求资源周期，其中，所述第一调度请求资源周期大于所述第二调度请求资源周期，所述非负整数包含第一非负整数和第二非负整数，所述第一非负整数大于所述第二非负整数；
则所述重复发送时长小于或等于所述调度请求禁止定时器时长，包括：
所述调度请求禁止定时器时长为所述禁止定时器时长与所述第一非负整数的乘积，详见实施例四。
本实施例中的网络设备，可以参照图24所示的设备。作为一个例子，该设备可以完成类似于图11中处理器1102的功能。在图24中，该设备包括处理器2410，发送数据处理器2420，接收数据处理器2430。上述实施例中的处理器1102可以是图24中的该处理器2410，并完成相应的功能。上述实施例中的控制电路1101可以是图24中的发送数据处理 器2420，和/或接收数据处理器2430。虽然图24中示出了信道编码器、信道解码器，但是可以理解这些模块并不对本实施例构成限制性说明，仅是示意性的。
图25示出本实施例的另一种网络设备形式。处理装置2500中包括调制子***、中央处理子***、周边子***等模块。本实施例中的网络设备可以作为其中的调制子***。具体的，该调制子***可以包括处理器2503，接口2504。其中处理器2503完成上述处理器1102的功能，接口2504完成上述控制电路1101的功能。作为另一种变形，该调制子***包括存储器2506、处理器2503及存储在存储器2506上并可在处理器上运行的程序，该处理器2503执行该程序时实现上述方法实施例中终端设备侧的方法。需要注意的是，所述存储器2506可以是非易失性的，也可以是易失性的，其位置可以位于调制子***内部，也可以位于处理装置2500中，只要该存储器2506可以连接到所述处理器2503即可。
作为本实施例的另一种形式，提供一种可在处理器上运行的程序，所述处理器执行所述程序时实现本发明实施例提供的任一项的方法。
作为本实施例的另一种形式，提供一种计算机可读存储介质，其上存储有指令，该指令被执行时执行本发明实施例提供的任一项的方法。
作为本实施例的另一种形式，提供一种包含指令的计算机程序产品，该指令被执行时执行本发明实施例提供的任一项的方法。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。上述计算机程序产品包括一个或多个计算机消息。在计算机上加载和执行上述计算机程序消息时，全部或部分地产生按照本申请实施例所述的流程或功能。上述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。上述计算机消息可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，上述计算机消息可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。上述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。上述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
另外，所描述***、设备和方法以及不同实施例的示意图，在不超出本申请的范围内，可以与其它***，模块，技术或方法结合或集成。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电子、机械或其它的形式。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。上述计算机程序产 品包括一个或多个计算机消息。在计算机上加载和执行上述计算机程序消息时，全部或部分地产生按照本申请实施例所述的流程或功能。上述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。上述计算机消息可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，上述计算机消息可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。上述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。上述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
另外，所描述***、设备和方法以及不同实施例的示意图，在不超出本申请的范围内，可以与其它***，模块，技术或方法结合或集成。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电子、机械或其它的形式。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。

Claims (30)

  1. 一种数据处理方法，其特征在于，包括：
    获取无线链路控制RLC层的服务数据单元SDU；
    按照数据删除方式删除数据，所述数据删除方式包括：将所述SDU封装成的第一协议数据单元PDU删除，或者，将所述第一PDU中的数据域删除。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    为所述SDU分配第一序列号；
    将所述SDU封装成所述第一PDU，所述第一PDU包含数据域和第一包头，所述第一包头中包含所述第一序列号。
  3. 根据权利要求2所述的方法，其特征在于，所述将所述SDU封装成所述第一PDU，包括：
    所述SDU被分段为N个子数据包的情况下，将所述N个子数据包封装成N个PDU。
  4. 根据权利要求3所述的方法，其特征在于，所述将所述第一PDU中的数据域删除，包括：
    将所述N个PDU中的数据域删除。
  5. 根据权利要求3所述的方法，其特征在于，所述数据删除方式还包括：
    在所述N个PDU中确定一个PDU作为第二PDU；
    将所述第二PDU中的数据域删除；
    将所述N个PDU中除所述第二PDU以外的PDU删除。
  6. 根据权利要求5所述的方法，其特征在于，所述按照数据删除方式删除数据之后，所述方法还包括：
    修改所述第二PDU的第二包头中用于指示所述第二PDU是否分段的指示信息，以指示所述第二PDU不分段。
  7. 根据权利要求2所述的方法，其特征在于，所述将所述SDU封装成的第一协议数据单元PDU删除，包括：
    删除所述第一PDU；
    构造第三PDU，所述第三PDU包含第三包头，所述第三包头中包含的序列号与所述第一序列号相同。
  8. 根据权利要求1～7中任意一项所述的方法，其特征在于，所述按照数据删除方式删除数据，包括：
    接收分组数据汇聚协议PDCP层发送的指示信息，所述指示信息用于指示所述RLC层删除所述SDU；在接收到所述指示信息的情况下，按照所述数据删除方式删除数据；
    或者，
    从获取到所述SDU时启动计时操作，所述计时操作的时间超过预设时间阈值的情况下，按照所述数据删除方式删除数据。
  9. 根据权利要求2所述的方法，其特征在于，若所述数据删除方式为所述将所述SDU封装成的第一协议数据单元PDU删除，所述按照数据删除方式删除数据之后，所述方法还 包括：
    生成用于指示所述第一PDU已被删除的状态报告，所述状态报告包括所述第一序列号。
  10. 根据权利要求3所述的方法，其特征在于，所述将所述SDU封装成的第一协议数据单元PDU删除，包括：
    将所述N个PDU删除；
    若所述数据删除方式为所述将所述SDU封装成的第一协议数据单元PDU删除，所述按照数据删除方式删除数据之后，所述方法还包括：
    生成用于指示序列号为所述第一序列号的PDU已被删除的状态报告。
  11. 根据权利要求9或10所述的方法，其特征在于，所述状态报告还包括用于指示所述状态报告为RLC层的控制PDU的指示信息；
    和/或，所述状态包括还包括比特图，所述比特图用于指示与所述第一PDU临近的PDU是否被删除；
    和/或，所述状态报告还包括数值，所述数值用于指示包括所述第一PDU在内连续删除的PDU的个数。
  12. 根据权利要求1所述的方法，其特征在于，所述数据删除方法还包括：将所述SDU删除；
    所述获取无线链路控制RLC层的服务数据单元SDU之后，所述按照数据删除方式删除数据之前，所述方法还包括：
    为所述SDU分配第一序列号；
    若所述数据删除方法为所述将所述SDU删除，所述按照数据删除方式删除数据之后，所述方法还包括：
    生成包含第四包头的第四PDU，所述第四包头包含所述第一序列号；或者，
    将所述第一序列号重新分配给所述SDU之后获取的第一个SDU。
  13. 一种数据处理方法，其特征在于，包括：
    接收无线链路控制RLC层的状态报告；
    获取所述状态报告中包含的序列号；
    所述状态报告中包含的序列号为第一序列号的情况下，确定序列号为所述第一序列号的PDU为已接收。
  14. 一种数据处理方法，其特征在于，包括：
    接收M个无线链路控制RLC层的PDU，所述M个RLC层的PDU包含的序列号为第一序列号的情况下，确定所述M个RLC层的PDU为RLC层的服务数据单元SDU分段后封装的PDU；
    所述M个RLC层的PDU中存在至少一个PDU的数据域为空的情况下，将所述M个RLC层的PDU删除，确定序列号为所述第一序列号的PDU为已接收。
  15. 一种数据处理设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其特征在于，所述处理器执行所述程序时实现以下步骤：
    获取无线链路控制RLC层的服务数据单元SDU；
    按照数据删除方式删除数据，所述数据删除方式包括：将所述获取单元获取的所述SDU 删除，或者，将所述SDU封装成的第一协议数据单元PDU删除，或者，将所述第一PDU中的数据域删除。
  16. 根据权利要求15所述的设备，其特征在于，所述处理器执行所述程序时还实现以下步骤：
    为所述SDU分配第一序列号；
    将所述SDU封装成所述第一PDU，所述第一PDU包含数据域和第一包头，所述第一包头中包含所述第一序列号。
  17. 根据权利要求16所述的设备，其特征在于，所述将所述SDU封装成所述第一PDU，包括：
    所述SDU被分段为N个子数据包的情况下，将所述N个子数据包封装成N个PDU。
  18. 根据权利要求17所述的设备，其特征在于，所述将所述第一PDU中的数据域删除包括：
    将所述N个PDU中的数据域删除。
  19. 根据权利要求17所述的设备，其特征在于，所述数据删除方式还包括：
    在所述N个PDU中确定一个PDU作为第二PDU；
    将所述第二PDU中的数据域删除；
    将所述N个PDU中除所述第二PDU以外的PDU删除。
  20. 根据权利要求19所述的设备，其特征在于，所述按照数据删除方式删除数据之后，所述处理器执行所述程序时还实现以下步骤：
    修改所述第二PDU的第二包头中用于指示所述第二PDU是否分段的指示信息，以指示所述第二PDU不分段。
  21. 根据权利要求16所述的设备，其特征在于，所述将所述SDU封装成的第一协议数据单元PDU删除，包括：
    删除所述第一PDU；构造第三PDU，所述第三PDU包含第三包头，所述第三包头中包含的序列号与所述分配单元分配的所述第一序列号相同。
  22. 根据权利要求15～21中任意一项所述的设备，其特征在于，所述按照数据删除方式删除数据，包括：
    接收分组数据汇聚协议PDCP层发送的指示信息，所述指示信息用于指示所述RLC层删除所述SDU；在接收到所述指示信息的情况下，按照所述数据删除方式删除数据；
    或者，
    从获取到所述SDU时启动计时操作，所述计时操作的时间超过预设时间阈值的情况下，按照所述数据删除方式删除数据。
  23. 根据权利要求16所述的设备，其特征在于，若所述数据删除方式为所述将所述SDU封装成的第一协议数据单元PDU删除，所述按照数据删除方式删除数据之后，所述处理器执行所述程序时还实现以下步骤：
    生成用于指示所述第一PDU已被删除的状态报告，所述状态报告包括所述第一序列号。
  24. 根据权利要求17所述的设备，其特征在于，所述将所述SDU封装成的第一协议数 据单元PDU删除，包括：
    将所述N个PDU删除；
    若所述数据删除方式为所述将所述SDU封装成的第一协议数据单元PDU删除，所述按照数据删除方式删除数据之后，所述处理器执行所述程序时还实现以下步骤：
    生成用于指示序列号为所述第一序列号的PDU已被删除的状态报告。
  25. 根据权利要求23或24所述的设备，其特征在于，所述状态报告还包括用于指示所述状态报告为RLC层的控制PDU的指示信息；
    和/或，所述状态包括还包括比特图，所述比特图用于指示与所述第一PDU临近的PDU是否被删除；
    和/或，所述状态报告还包括数值，所述数值用于指示包括所述第一PDU在内连续删除的PDU的个数。
  26. 根据权利要求15所述的设备，其特征在于，所述数据删除方法还包括：将所述SDU删除；
    所述获取无线链路控制RLC层的服务数据单元SDU之后，所述按照数据删除方式删除数据之前，所述处理器执行所述程序时还实现以下步骤：
    为所述SDU分配第一序列号；
    若所述数据删除方法为所述将所述SDU删除，所述按照数据删除方式删除数据之后，所述处理器执行所述程序时还实现以下步骤：
    生成包含第四包头的第四PDU，所述第四包头包含所述第一序列号；或者，
    将所述第一序列号重新分配给所述SDU之后获取的第一个SDU。
  27. 一种数据处理设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其特征在于，所述处理器执行所述程序时实现以下步骤：
    接收无线链路控制RLC层的状态报告；
    获取所述状态报告中包含的序列号；
    所述状态报告中包含的序列号为第一序列号的情况下，确定序列号为所述第一序列号的PDU为已接收。
  28. 一种数据处理设备，包括存储器、处理器及存储在存储器上并可在处理器上运行的计算机程序，其特征在于，所述处理器执行所述程序时实现以下步骤：
    接收到M个无线链路控制RLC层的PDU，所述M个RLC层的PDU包含的序列号为第一序列号的情况下，确定所述M个RLC层的PDU为RLC层的服务数据单元SDU分段后封装的PDU；
    所述M个RLC层的PDU中存在至少一个PDU的数据域为空的情况下，将所述M个RLC层的PDU删除，确定序列号为所述第一序列号的PDU为已接收。
  29. 一种可在处理器上运行的程序，其特征在于，所述处理器执行所述程序时实现权利要求1至14中任一项所述方法。
  30. 一种计算机可读存储介质，其上存储有指令，其特征在于，该指令被执行时执行权利要求1至14中任一项所述方法。
PCT/CN2018/085611 2017-05-05 2018-05-04 数据处理方法及设备 WO2018202133A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710313596.4A CN108809540B (zh) 2017-05-05 2017-05-05 数据处理方法及设备
CN201710313596.4 2017-05-05

Publications (1)

Publication Number Publication Date
WO2018202133A1 true WO2018202133A1 (zh) 2018-11-08

Family

ID=64016913

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/085611 WO2018202133A1 (zh) 2017-05-05 2018-05-04 数据处理方法及设备

Country Status (2)

Country Link
CN (1) CN108809540B (zh)
WO (1) WO2018202133A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113923713A (zh) * 2020-07-09 2022-01-11 维沃移动通信有限公司 数据处理的方法及装置
CN113923712A (zh) * 2020-07-09 2022-01-11 维沃移动通信有限公司 数据处理的方法及装置

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109688606B (zh) * 2018-12-29 2022-03-25 京信网络***股份有限公司 数据处理方法、装置、计算机设备及存储介质
WO2021217605A1 (zh) * 2020-04-30 2021-11-04 华为技术有限公司 处理数据包的方法和通信装置
CN112235826B (zh) * 2020-10-16 2023-05-02 展讯半导体(南京)有限公司 数据删除及同步方法和收发终端、电子设备及存储介质
CN117692957A (zh) * 2022-09-02 2024-03-12 上海朗帛通信技术有限公司 一种被用于无线通信中的方法和装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20080009470A (ko) * 2006-07-24 2008-01-29 엘지전자 주식회사 이동 통신 시스템에서 제어 정보를 처리하는 방법
CN201444641U (zh) * 2007-10-01 2010-04-28 交互数字专利控股公司 无线发射/接收单元
CN104506279A (zh) * 2014-12-29 2015-04-08 武汉虹信通信技术有限责任公司 用于lte中rlc am模式下的上下行并行处理方法
CN104837163A (zh) * 2014-02-08 2015-08-12 夏普株式会社 用于删除无线链路控制服务数据单元的方法和基站

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102957522B (zh) * 2011-08-24 2017-05-10 中兴通讯股份有限公司 一种rlc am状态报告处理的方法和***
CN104168214B (zh) * 2014-08-21 2018-02-27 京信通信***（中国）有限公司 一种丢弃分组数据的方法及装置
CN104683017B (zh) * 2015-03-24 2018-09-11 重庆邮电大学 一种卫星移动通信rlc层am模式传输方法
EP3353930B1 (en) * 2015-09-25 2020-10-21 Nokia Solutions and Networks Oy Enhancement of pdcp status report

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20080009470A (ko) * 2006-07-24 2008-01-29 엘지전자 주식회사 이동 통신 시스템에서 제어 정보를 처리하는 방법
CN201444641U (zh) * 2007-10-01 2010-04-28 交互数字专利控股公司 无线发射/接收单元
CN104837163A (zh) * 2014-02-08 2015-08-12 夏普株式会社 用于删除无线链路控制服务数据单元的方法和基站
CN104506279A (zh) * 2014-12-29 2015-04-08 武汉虹信通信技术有限责任公司 用于lte中rlc am模式下的上下行并行处理方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113923713A (zh) * 2020-07-09 2022-01-11 维沃移动通信有限公司 数据处理的方法及装置
CN113923712A (zh) * 2020-07-09 2022-01-11 维沃移动通信有限公司 数据处理的方法及装置

Also Published As

Publication number Publication date
CN108809540B (zh) 2021-09-17
CN108809540A (zh) 2018-11-13

Similar Documents

Publication Publication Date Title
US11751097B2 (en) Method and apparatus for reestablishing packet data convergence protocol (PDCP) entity in a wireless communication system
US11984989B2 (en) Transmission method and apparatus
JP6907444B2 (ja) データ伝送方法、通信デバイス、端末、および基地局
WO2018202133A1 (zh) 数据处理方法及设备
CN108617029B (zh) 无线承载配置方法、及相应的ue和基站
US10708940B2 (en) Method and apparatus for reporting buffer state by user equipment in communication system
US11153931B2 (en) Interference cancellation method and base station
TWI482523B (zh) 處理觸發暫存器狀態報告之計時器的方法及通訊裝置
KR101792167B1 (ko) 데이터 전송 방법, 장치 및 시스템
KR101630882B1 (ko) 무선 통신 시스템의 릴레이 노드(Ｒｅｌａｙ ｎｏｄｅ)에서 무선자원을 효율적으로 사용하는 방법
KR101637584B1 (ko) 무선 통신 시스템상에서 서비스의 품질(ＱｏＳ)을 보장하는 방법
JP6262359B2 (ja) データ伝送方法及びデータ伝送システム並びにデータ伝送装置
JP5567128B2 (ja) Ａｒｑフィードバック情報伝送及び受信方法
WO2012130094A1 (zh) 一种用于帧确认的方法和装置
JP7149258B2 (ja) 無線通信装置及び無線通信方法
WO2009117961A1 (zh) 一种发送数据的方法、***和设备
JP2022543157A (ja) 通信方法、ｓｌｒｂ確立方法、および通信装置
KR20180099135A (ko) 기지국간 캐리어 집적을 지원하기 위한 패킷 생성 및 분배 방법 및 장치
WO2022006914A1 (zh) 混合自动重传请求应答harq-ack的反馈方法和终端设备
JP2023015208A (ja) 送信装置、基地局及び無線通信システム
JP4896073B2 (ja) 無線通信システムにおいてデータ伝送状態をポーリングする方法及び装置
WO2019214619A1 (zh) 一种数据处理的方法及设备
WO2018086707A1 (en) Feedback based flexible transmission scheme for contention-based urllc transmission
WO2021249218A1 (zh) 数据传输方法和装置
WO2024140716A1 (zh) 一种通信方法、通信设备及计算机可读存储介质

Legal Events

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

Ref document number: 18793941

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

Country of ref document: EP

Kind code of ref document: A1