CN108809540B

CN108809540B - Data processing method and device

Info

Publication number: CN108809540B
Application number: CN201710313596.4A
Authority: CN
Inventors: 王宏; 权威; 张戬
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-05-05
Filing date: 2017-05-05
Publication date: 2021-09-17
Anticipated expiration: 2037-05-05
Also published as: WO2018202133A1; CN108809540A

Abstract

The embodiment of the application discloses a data processing method and equipment. Wherein, the method comprises the following steps: acquiring a Service Data Unit (SDU) of a Radio Link Control (RLC) layer; deleting data according to a data deleting mode, wherein the data deleting mode comprises the following steps: and deleting the first protocol data unit PDU formed by packaging the SDU, or deleting the data field in the first PDU. By adopting the embodiment of the application, the data which does not need to be transmitted can be deleted according to different data deleting modes, and wireless communication resources are saved.

Description

Data processing method and device

Technical Field

The present application relates to the field of communications technologies, and in particular, to a data processing method and device.

Background

In a Long Term Evolution (LTE) network, user plane Data is transmitted between a user equipment and a network device in a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control (RLC) layer, a Media Access Control (MAC) layer, and a Physical (PHY) layer of the device in a format of an Internet Protocol (IP) Packet.

In the data transmission process, the data packet has certain timeliness, for example, voice call service has higher requirement on the timeliness of the data packet; and the requirement on the timeliness of the data packet is lower for the webpage browsing service. Therefore, the PDCP layer of the device starts a timer corresponding to the Service characteristics of the PDCP SDU (Service Data Unit, SDU)) for the PDCP SDU, and if the timer expires, the PDCP layer discards the PDCP SDU and sends an indication message to the RLC layer, which indicates to the RLC layer to discard the received Protocol Data Unit (PDU) of the PDCP layer, where the PDU is obtained by encapsulating the PDCP SDU by the PDCP layer.

In the LTE technology, the RLC layer has a concatenation function, that is, the RLC layer can receive a plurality of PDCP PDUs from the PDCP layer, and concatenate the plurality of PDCP PDUs into one RLC PDU; for example, PDCP PDU 3, PDCP PDU 4 and PDCP PDU 5 are concatenated into one RLC PDU. If the RLC layer receives the indication information sent by the PDCP layer, the indication information indicates the RLC layer to discard the PDCP PDU 4, and the generated RLC PDU includes the PDCP PDU 4, the PDCP PDU 3 and the PDCP PDU 5, so that the RLC PDU is not discarded, and the RLC layer normally transmits the RLC PDU, so that data which is not required to be transmitted is included in the data packet and transmitted, and radio communication resources are wasted.

Disclosure of Invention

The embodiment of the application provides a data processing method and data processing equipment, which can delete data which does not need to be transmitted according to different data deletion modes, and save wireless communication resources.

In a first aspect, an embodiment of the present application provides a data processing method, including:

acquiring a Service Data Unit (SDU) of a Radio Link Control (RLC) layer;

deleting data according to a data deleting mode, wherein the data deleting mode comprises the following steps: deleting the SDU, or deleting a first Protocol Data Unit (PDU) encapsulated by the SDU, or deleting a data field in the first PDU.

In this embodiment, the SDU is a radio link control service data unit RLC SDU, and the PDU is a radio link control protocol data unit RLC PDU. When the RLC layer of the device (which may be a user equipment or a network device) receives the RLC SDU from the PDCP layer of the device, if the RLC layer receives the indication information sent by the PDCP layer to indicate deletion of the RLC SDU, the RLC layer may delete data according to the above data deletion method, thereby avoiding waste of wireless communication resources caused by transmission of data that does not need to be transmitted in a subsequent retransmission process.

As an optional implementation, the first PDU corresponds to only one SDU.

In this embodiment, the data processing method is only applicable to the case where the RLC layer does not generate the PDU in a concatenated manner, that is, the RLC layer does not concatenate multiple SDUs into one PDU, that is, the first PDU only corresponds to one SDU.

As an optional implementation manner, after the obtaining of the service data unit SDU in the radio link control RLC layer and before the deleting of the data according to the data deleting manner, the method further includes:

distributing a first sequence number to the SDU;

encapsulating the SDU into the first PDU, wherein the first PDU comprises a data field and a first packet header, and the first packet header comprises the first sequence number;

and storing the first PDU after transmitting the first PDU to a Media Access Control (MAC) layer.

In this embodiment, the first PDU is identified as the PDU obtained after the SDU is encapsulated by the first sequence number, so that after the RLC layer receives the indication information for deleting the SDU, the first PDU can be obtained according to the first sequence number and the data deletion operation is performed on the first PDU.

As an optional implementation, the encapsulating the SDU into the first PDU includes:

and under the condition that the SDU is segmented into N sub-data packets, packaging the N sub-data packets into N PDUs.

In this embodiment, if the data packet SDU is too large, the SDU may be segmented into N sub-data packets, and then correspondingly encapsulated into N PDUs, so that the data packets SDU becomes a data frame suitable for transmission by the underlying network.

As an optional implementation, the deleting the data field in the first PDU includes:

deleting the data field in the N PDUs.

In this embodiment, if the RLC layer allocates the first sequence number to the SDU, N PDUs obtained by segmentation and encapsulation are all identified by the first sequence number, so that all PDUs whose sequence numbers are the first sequence number can be obtained, and the data fields of these PDUs are deleted.

As an optional implementation manner, the data deleting manner further includes:

determining one PDU as a second PDU from the N PDUs;

deleting a data field in the second PDU;

deleting the PDUs except the second PDU in the N PDUs.

In this embodiment, all PDUs except the second PDU among the N PDUs are deleted, which can further reduce redundant data at the time of transmission.

As an optional implementation manner, after deleting data according to the data deleting manner, the method further includes:

modifying indication information in a second header of the second PDU for indicating whether the second PDU is fragmented to indicate that the second PDU is not fragmented.

In this embodiment, after all PDUs except the second PDU among the N PDUs are deleted, only the second PDU will be transmitted during retransmission, thereby reaching the data receiving end. Therefore, modifying the second header to indicate that the second PDU is not fragmented facilitates normal packet ordering by the data receiving end.

As an optional implementation manner, the deleting the first protocol data unit PDU into which the SDU is encapsulated includes:

deleting the first PDU;

and constructing a third PDU, wherein the third PDU comprises a third packet header, and the sequence number contained in the third packet header is the same as the first sequence number.

In this embodiment, the constructed third PDU may only contain the header, and when the third PDU is retransmitted to the data receiving end, the data receiving end may be helped to correctly complete the data packet sequencing according to the first sequence number contained therein, and at the same time, it is avoided that the data that has lost timeliness in the first PDU is retransmitted, thereby wasting wireless communication resources.

As an optional implementation, the deleting data according to the data deleting method includes:

receiving indication information sent by a packet data convergence protocol PDCP layer, wherein the indication information is used for indicating the RLC layer to delete the SDU; deleting data according to the data deleting mode under the condition that the indication information is received; alternatively, the first and second electrodes may be,

and starting timing operation when the SDU is acquired, and deleting data according to the data deleting mode under the condition that the time of the timing operation exceeds a preset time threshold.

In this embodiment, the PDCP layer may have a certain delay when sending the indication information indicating that the data included in the SDU has lost timeliness to the RLC layer; therefore, the RLC layer may start a timer when the SDU is acquired, and perform a data deletion operation if the timer expires, thereby avoiding that the data cannot be deleted in time due to the aforementioned delay.

As an optional implementation manner, if the data deletion manner is the deletion of the first protocol data unit PDU encapsulated by the SDU, after the data is deleted according to the data deletion manner, the method further includes:

generating a status report indicating that the first PDU has been deleted, the status report including the first sequence number.

In this embodiment, if the first PDU is deleted entirely (the first header and the data field are both deleted), in order to avoid that the data receiving end continuously waits for the first PDU when performing packet sequencing, the device may generate a status report for indicating that the first PDU has been deleted, and send the status report to the data receiving end.

deleting the N PDUs;

if the data deleting mode is the deletion of the first protocol data unit PDU packaged by the SDU, after the data is deleted according to the data deleting mode, the method further comprises:

generating a status report indicating that the N PDUs have been deleted, the status report including the first sequence number.

In this embodiment, if all the N PDUs are deleted, in order to avoid that the data receiving end continuously waits for the N PDUs when performing packet sequencing, the device may generate a status report indicating that all the N PDUs are deleted, and send the status report to the data receiving end.

As an optional implementation manner, the status report further includes indication information for indicating that the status report is a control PDU of the RLC layer;

and/or, the status includes further comprising a bitmap for indicating whether PDUs adjacent to the first PDU are deleted;

and/or the status report further comprises a value indicating the number of consecutively deleted PDUs including the first PDU.

In this embodiment, the status report may be set so that the data receiving end can be informed of the information that more than one PDU is deleted.

As an optional implementation manner, the data deleting method further includes: deleting the SDU;

after the obtaining of the service data unit SDU in the RLC layer and before the deleting of the data according to the data deleting method, the method further includes:

distributing a first sequence number to the SDU;

if the data deletion method is the deletion of the SDU, after the data is deleted according to the data deletion method, the method further includes:

generating a fourth PDU containing a fourth packet header, wherein the fourth packet header contains the first sequence number; alternatively, the first and second electrodes may be,

re-assigning the first sequence number to a first SDU obtained after the SDU.

In this embodiment, 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 a header is generated for the sequence number, so as to keep the sequence number continuous, which is beneficial for the data receiver to perform packet sequencing.

In a second aspect, an embodiment of the present application provides a data processing method, including:

receiving a status report of a Radio Link Control (RLC) layer;

acquiring a serial number contained in the status report;

and determining that the PDU with the sequence number of the first sequence number is received under the condition that the sequence number contained in the status report is the first sequence number.

In a third aspect, an embodiment of the present application provides a data processing method, including:

receiving M PDUs of Radio Link Control (RLC) layers, and determining the PDUs of the M RLC layers as PDUs packaged after segmentation of Service Data Units (SDUs) of the RLC layers under the condition that sequence numbers contained in the PDUs of the M RLC layers are first sequence numbers;

and deleting the PDUs of the M RLC layers under the condition that the data field of at least one PDU in the PDUs of the M RLC layers is empty, and determining that the PDU with the sequence number of the first sequence number is received.

In a fourth aspect, an embodiment of the present application provides a network device, including:

an obtaining unit, configured to obtain a service data unit SDU of a radio link control RLC layer;

a deleting unit, configured to delete data according to a data deletion method, where the data deletion method includes: deleting the SDU acquired by the acquisition unit, or deleting a first Protocol Data Unit (PDU) encapsulated by the SDU, or deleting a data field in the first PDU.

As an alternative implementation, the network device provided by the present application may contain a unit for performing the steps in the above method design. The units may be software and/or hardware. Optionally, the network device provided in the present application includes a processor and a transceiver, where the processor is configured to support the network device to execute corresponding functions in the foregoing method. The transceiver is used for supporting communication between the network device and the terminal and transmitting the information or the message related in the method to the terminal. A memory may also be included in the network device for coupling with the processor that stores program messages and data necessary for the network device. The network device may also include a communication interface for communicating with other network devices.

In a fifth aspect, an embodiment of the present application provides a terminal, including:

As an alternative embodiment, the terminal provided by the present application may comprise means for performing the steps in the above method design. The units may be software and/or hardware. Optionally, the terminal provided in the present application includes a processor and a transceiver in its structure, where the processor is configured to support the terminal to execute corresponding functions in the above method. The transceiver is used for supporting communication between the access network equipment and the terminal and sending the information or the message related in the method to the access network equipment. The terminal may also include a memory, coupled to the processor, that retains program messages and data necessary for the terminal.

In a sixth aspect, the present application provides a computer program product containing a message, which when run on a computer causes the computer to perform the method of the above aspects.

In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium, in which a message is stored, and when the computer-readable storage medium is run on a computer, the computer is caused to perform the method in the above aspects.

By implementing the embodiment of the application, the wireless link control layer of the equipment can delete the data which does not need to be transmitted according to different data deletion modes, thereby saving wireless communication resources.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments or the background art of the present application, the drawings required to be used in the embodiments or the background art of the present application will be described below.

Fig. 1A is a schematic diagram of an application scenario of a communication system disclosed in an embodiment of the present application;

fig. 1B is an interaction diagram of a user plane protocol stack disclosed in an embodiment of the present application;

FIG. 1C is a diagram illustrating the interaction between a PDCP layer and an RLC layer disclosed in the embodiments of the present application;

fig. 1D is a schematic structural diagram of an RLC PDU disclosed in an embodiment of the present application;

FIG. 2 is a flow chart of a data processing method disclosed in an embodiment of the present application;

FIG. 3 is a schematic flow chart diagram of another data processing method disclosed in the embodiments of the present application;

FIG. 4 is a schematic flow chart diagram illustrating yet another data processing method disclosed in an embodiment of the present application;

FIG. 5 is a schematic flow chart diagram illustrating yet another data processing method disclosed in an embodiment of the present application;

FIG. 6A is a schematic flow chart diagram illustrating another data processing method disclosed in the embodiments of the present application;

FIG. 6B is a diagram illustrating a status report format according to an embodiment of the present disclosure;

FIG. 6C is a diagram of another status report format disclosed in an embodiment of the present application;

FIG. 6D is a diagram illustrating another status report format disclosed in an embodiment of the present application;

fig. 7 is a schematic diagram of another application scenario of the communication system disclosed in the embodiment of the present application;

FIG. 8 is a schematic flow chart diagram illustrating yet another data processing method disclosed in an embodiment of the present application;

FIG. 9 is a schematic diagram of an apparatus 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 application;

fig. 11 is a schematic structural diagram of a terminal 1100 disclosed in an embodiment of the present application;

fig. 12 is a schematic diagram of an application scenario of a communication system disclosed in an embodiment of the present application;

fig. 13 is a schematic configuration diagram of a scheduling request resource according to an embodiment of the present application;

fig. 14 is a schematic configuration diagram of another scheduling request resource disclosed in an embodiment of the present application;

fig. 15 is a schematic diagram of a scheduling request repeat request disclosed in an embodiment of the present application;

fig. 16 is a schematic diagram illustrating a scheduling request conflict according to an embodiment of the present application;

fig. 17 is a flowchart illustrating a scheduling request sending method disclosed in an embodiment of the present application;

fig. 18 is a schematic diagram of another scheduling request sending method disclosed in an embodiment of the present application;

fig. 19 is a schematic diagram of another scheduling request sending method disclosed in an embodiment of the present application;

fig. 20 is a schematic diagram of another scheduling request sending method disclosed in the embodiment of the present application;

fig. 21 is a flowchart illustrating a scheduling request receiving method according to an embodiment of the present application;

fig. 22 is a schematic structural diagram of a terminal device disclosed in an embodiment of the present application;

fig. 23 is a schematic structural diagram of a network device disclosed in an embodiment of the present application.

Detailed Description

The embodiments of the present application will be described below with reference to the drawings.

Referring to fig. 1A, fig. 1A is a schematic diagram of an application scenario of a communication system according to an embodiment of the present disclosure. The communication system may apply an LTE network or a 5G network. As shown in fig. 1A, a user terminal accesses a core network through an evolved Node B (eNB), and performs data transmission and reception by interacting with the eNB. In a 5G system, the base station may also be a 5G base station gNB.

The user equipment may be a mobile phone, an intelligent terminal, a multimedia device, a streaming media device, and the like, and the embodiment of the present application is not limited. The eNB is a bridge between a user terminal in an LTE network and an Evolved Packet Core (EPC), and is connected to the eNB through an X2 interface, and has main functions of: radio resource Management, IP header compression and user data stream encryption, Mobility Management Entity (MME) selection when a user terminal is attached, routing of user plane data to a Serving Gateway (S-GW), organization and transmission of paging messages, organization and transmission of broadcast messages, measurement and measurement report configuration for Mobility or scheduling, and the like.

Referring to fig. 1B, fig. 1B is an interaction diagram of a user plane protocol stack disclosed in the embodiment of the present application. In the LTE network, user plane data is transmitted between the user equipment and the network equipment via the PDCP layer, the RLC layer, the MAC layer, and the PHY layer in an IP packet format. Arrows in the figure indicate the transmission flow of data packets when the user equipment sends data to the eNB, and the data packets generally need to pass through the PDCP layer, the RLC layer, the MAC layer, and the PHY layer by layer. It can be understood that when the eNB transmits data to the user equipment, the transmission flow of the data packets is reversed. When an IP packet is transmitted from the PDCP layer of the device to the RLC layer of the device, if the PDCP layer sends instruction information to the RLC layer to instruct the RLC layer to discard the stale packet, and the RLC layer concatenates the packet with a plurality of other packets and encapsulates the packet into one RLC PDU (i.e., a PDU of the RLC layer), the RLC layer cannot perform the operation of discarding the packet, and the RLC PDU carrying the packet is normally transmitted, which results in the waste of radio communication resources.

Referring to fig. 1C, fig. 1C is a schematic diagram illustrating an 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 (i.e., a PDU of the PDCP layer with Sequence Number (SN) of 4) to the RCL layer, and after receiving the PDCP PDU 4, the RCL layer allocates a Sequence Number 8 of the RLC layer to the PDCP PDU 4, and then encapsulates the data packet into an RLC PDU8 (i.e., a PDU of the RLC layer with Sequence Number 8), please refer to fig. 1D, where fig. 1D is a schematic diagram of a structure of an RLC PDU disclosed in this embodiment, and the structure of the RLC PDU includes a packet header and a data field.

After that, the RLC layer transmits the encapsulated RLC PDU8 to the MAC layer of the present apparatus. In the Acknowledged Mode (AM), the RLC layer stores, in the retransmission memory, the RLC PDU8 which is sent to the MAC layer and has not received ACK information fed back by the data receiving side (the ACK information indicates that the data receiving side has successfully received a certain data packet). In such a case, if the PDCP layer of the present device instructs the RLC layer to discard the PDCP PDU8 at this time, when the RLC layer does not concatenate RLC SDUs, one RLC PDU corresponds to only one RLC SDU, and the following methods in fig. 2 to 6 and 8 may be applied to perform a data deletion operation.

In addition, in AM mode, RLC SDU may also lose timeliness when RLC PDU is sent by RLC layer to MAC layer. For example, the PDCP layer sends PDCP PDU 1 and PDCP PDU2 (RLC SDU 5 and RLC SDU 6, respectively) to the RLC layer, and during the RLC layer sends RLC SDU 5 to the opposite end, the timer associated with PDCP PDU 1 corresponding to RLC SDU 6 expires, and the PDCP layer instructs to discard PDCP PDU 1, that is, to discard RLC SDU 5. It can be seen that, in this case, the RLC PDU corresponding to RLC SDU 6 is not sent to the MAC layer, and is not stored in the retransmission memory. In this case, the following method is also applicable.

In addition, in AM mode, if the RLC layer is transmitting RLC PDU segments, and all segments of RLC SDU corresponding to the segments are not yet transmitted to the peer end, the indication information of the PDCP layer is received, and the corresponding PDCP PDU is discarded, and the following method is also applicable.

In addition, the present invention is also applicable to a non-responded Mode (UM).

Referring to fig. 2, fig. 2 is a schematic flow chart of a data processing method according to an embodiment of the present application. The execution subject of the data processing method may be a user terminal or a network device, and the embodiment of the present application takes the user terminal as an example for description.

201. And acquiring SDU of the RLC layer.

As explained in conjunction with FIG. 1C, the RLC layer of the user terminal receives PDCP PDU 4 transmitted by the PDCP layer of the user terminal, which is called RLC SDU after it reaches the RLC layer.

202. A first sequence number is assigned to the SDU.

The RLC layer of the user terminal assigns a Sequence Number (SN) 8 of the RLC layer to the RLC SDU, that is, the SN of the RLC SDU is 8.

If the RLC layer receives the indication information sent by the PDCP layer to delete the PDCP PDU 4 before the RLC layer encapsulates the RLC SDU 8 into the RLC PDU8, the RLC layer may directly delete the RLC SDU 8 and then generate the RLC PDU8, where the RLC PDU8 does not include a data field and only includes a header, and the header carries a sequence number SN of 8; or, after the RLC layer deletes the RLC SDU 8, when receiving the PDCP PDU 5 and the PDCP PDU 6, the sequence number 8 is re-allocated to the PDCP PDU 5, the sequence number 9 is allocated to the PDCP PDU 6, and so on.

203. And encapsulating the SDU into a first PDU, wherein the first PDU comprises a data field and a first packet header, and the first packet header comprises a first sequence number.

This RLC SDU is encapsulated into RLC PDU8, and the header of RLC PDU8 includes the assigned sequence number SN of 8.

In the response-retransmission mode, the RLC layer stores RLC PDU8, which is sent to the MAC layer of the device and has not received ACK information fed back by the data receiving side (e.g., network device), into the retransmission memory. Storing the data packet in the retransmission memory is optional, i.e. in RLC UM mode, the data packet (such as the RLC PDU8 described above) does not need to be stored after being transferred to the MAC layer. Alternatively, in RLC AM mode, packets (such as RLC PDU8 described above) may be discarded before being sent to the MAC layer.

204. The data field in the first PDU is deleted.

If the RLC layer of the user equipment receives the indication information transmitted by the PDCP layer of the user equipment after storing the RLC PDU8 in the retransmission memory, and the indication information indicates that the RLC layer deletes the PDCP PDU 4 (since the timer set for the PDCP PDU 4 by the PDCP layer is overtime, it indicates that the PDCP PDU 4 loses timeliness), the RLC layer finds the RLC PDU8 obtained by encapsulating the PDCP PDU 4 in the retransmission memory according to the sequence number, deletes the data field of the RLC PDU8, and only retains the header of the RLC PDU 8.

If the RLC layer of the user equipment does not store the RLC PDU8 in the retransmission memory yet, and receives the indication information sent by the PDCP layer of the user equipment, the indication information indicates the RLC layer to delete the PDCP PDU 4, the RLC layer deletes the data field of the RLC PDU8, and only retains the header of the RLC PDU 8.

If the RLC layer of the user equipment does not encapsulate the PDCP PDU 4 into the RLC PDU8, the RLC layer receives the indication information sent by the PDCP layer of the user equipment, and the indication information indicates the RLC layer to delete the PDCP PDU 4, deletes the PDCP PDU 4 by the RLC layer, and generates a header of the RLC PDU8 corresponding to the PDCP PDU 4.

In the acknowledgement-retransmission mode, the RLC layer of the user equipment retransmits the RLC PDU8 including only the header, avoiding retransmission of data (i.e., data field portion) that has been stale, and saving wireless communication resources.

Referring to fig. 3, fig. 3 is a schematic flow chart of another data processing method disclosed in the embodiment of the present application.

301. And acquiring SDU of the RLC layer.

302. And distributing a sequence number to the SDU.

The RLC layer of the user terminal assigns a sequence number 8 of the RLC layer to the RLC SDU.

303. And segmenting the SDU into N sub-data packets.

Before the RLC SDU is encapsulated into the RLC PDU, if data included in the RLC SDU is too long, which causes an overlarge data packet, the RLC SDU needs to be segmented into N sub-data packets (N is greater than or equal to 2), and then the segmented sub-data packets are encapsulated respectively. It should be noted that, the sequence numbers of the RLC layers of the N segmented sub-packets of the PDCP PDU 4 are all 8.

304. And encapsulating the N sub-data packets into N RLC PDUs.

305. And deleting the data fields of the N RLC PDUs.

If the RLC layer of the user equipment stores the N PDUs in the retransmission memory, receiving indication information transmitted by the PDCP layer of the user equipment, where the indication information indicates that the RLC layer deletes the PDCP PDU 4 (since the timer set for the PDCP PDU 4 by the PDCP layer is expired, it indicates that the PDCP PDU 4 has lost timeliness); the RLC layer finds the RLC PDU with the sequence number of 8 (i.e. the N RLC PDUs) in the retransmission memory according to the sequence number, deletes all the data fields of the N RLC PDUs, and only keeps the packet headers of the N RLC PDUs.

If the RLC layer of the user equipment has not stored the N RLC PDUs 8 in the retransmission memory, the indication information transmitted by the PDCP layer of the user equipment is received, and the indication information indicates the RLC layer to delete the PDCP PDU 4, the RLC layer deletes the data fields of the N RLC PDUs 8, and only retains the packet headers of the N RLC PDUs 8.

In the response-retransmission mode, the RLC layer of the ue retransmits the N PDUs only including the header, thereby avoiding retransmission of stale data (i.e., the data field portion of the N PDUs) and saving wireless communication resources.

Referring to fig. 4, fig. 4 is a schematic flowchart illustrating another data processing method according to an embodiment of the present application. In the embodiment of the present application, the implementation of steps 401 to 404 may refer to the description of steps 301 to 304 in fig. 3, and the description of the embodiment of the present application is not repeated herein. On the basis of fig. 3, in order to further save wireless communication resources, the RLC layer of the user equipment may delete N RLC PDUs encapsulated after segmentation to only the remaining one RLC PDU, and delete the data field of the remaining RLC PDU, so that only the packet header of the remaining RLC PDU needs to be transmitted during retransmission, thereby achieving the purpose of saving wireless communication resources.

401. And acquiring SDU of the RLC layer.

402. And distributing a sequence number to the SDU.

403. And segmenting the SDU into N sub-data packets.

404. And encapsulating the N sub-data packets into N RLC PDUs.

405. And determining one RLC PDU as a second PDU in the N RLC PDUs.

In this embodiment, the RLC layer of the ue may randomly select one PDU from the N PDUs as the second PDU.

As an alternative implementation, the RLC layer may select a PDU with the smallest header from the N PDUs as the second PDU, so that when retransmitting, if only the header of the second PDU is retransmitted, the consumption of wireless communication resources may be further reduced.

406. Deleting the data field in the second PDU.

407. And deleting the PDUs except the second PDU in the N PDUs.

As an optional implementation manner, after deleting the PDUs except the second PDU from the N PDUs, the indication information in the second header of the second PDU for indicating whether the second PDU is fragmented is modified to indicate that the second PDU is not fragmented.

As an optional implementation manner, after deleting the PDUs except the second PDU from the N PDUs, a field indicating a Segmentation Offset (SO) in the second header of the second PDU is deleted.

As an optional implementation, the method may be further applied to that, when a part of RLC PDUs 8 in the N RLC PDUs 8 is sent to the MAC layer, the RLC layer receives the instruction information of the PDCP and instructs to discard the PDCP PDU 4, at this time, the RLC layer processes another part of RLC PDUs 8 corresponding to the PDCP PDU 4 and not yet sent to the MAC layer, and the processing procedure is as follows:

the first method is as follows: the part of the RLC PDU8 which is not addressed to the MAC layer is deleted, and the RLC PDU8 including only the header of the RLC PDU, that is, the RLC PDU with the sequence number of 8 is generated.

The second method comprises the following steps: in the part of the RLC PDUs 8 which are not sent to the MAC layer, one RLC PDU8 is randomly selected as the third PDU, and other RLC PDUs 8 are deleted, the data field of the third PDU is deleted, and other similar steps are as described above.

By implementing the embodiment of the present application, after a data receiving side (e.g., a network device) receives a second PDU only including a packet header, the data packet ordering may be completed according to a sequence number included in the packet header.

Referring to fig. 5, fig. 5 is a schematic flow chart of another data processing method disclosed in the embodiment of the present application. The implementation of steps 501 to 504 can refer to the description of steps 201 to 204 in fig. 2, and the embodiment of the present application is not described in detail below. Compared with the data processing method described in fig. 2, the method described in fig. 5 deletes the first PDU in its entirety, and reconstructs a third PDU containing no data field or a data field with a very small size instead of the first PDU, thereby saving wireless communication resources.

501. And acquiring SDU of the RLC layer.

502. A first sequence number is assigned to the SDU.

503. And encapsulating the SDU into a first PDU, wherein the first PDU comprises a data field and a first packet header, and the first packet header comprises a first sequence number.

As an alternative embodiment, after transmitting the first PDU to the MAC layer, the RLC layer may store the first PDU in the retransmission memory.

504. And deleting the first PDU.

505. And constructing a third PDU, wherein the third PDU comprises a third packet header, and the sequence number contained in the third packet header is the same as the first sequence number.

In the embodiment of the application, the RLC layer constructs a third PDU, and the third PDU does not include a data field, at least includes a sequence number, and the sequence number is the same as the first sequence number. And when in retransmission, the third PDU is transmitted to replace the first PDU, thereby playing the roles of avoiding sending redundant data and saving wireless communication resources.

Referring to fig. 6A, fig. 6A is a schematic flowchart illustrating another data processing method according to an embodiment of the present disclosure. In the embodiment of the present application, the implementation of steps 601 to 604 may refer to the description of steps 201 to 204 in fig. 2, and the description of the embodiment of the present application is not repeated herein.

601. And acquiring SDU of the RLC layer.

602. A first sequence number is assigned to the SDU.

603. And encapsulating the SDU into a first PDU, wherein the first PDU comprises a data field and a first packet header, and the first packet header comprises a first sequence number.

604. And deleting the first PDU after receiving the instruction information used for instructing the RLC layer to delete the SDU.

605. A status report is generated indicating that the first PDU has been deleted, the status report including the first sequence number.

In the embodiment of the application, the user terminal sends the status report to the data receiver, and the data receiver can skip the deleted data packet to normally sequence the data packet according to the status report when sequencing the data packet.

Referring to fig. 6B, fig. 6B is a schematic diagram illustrating a status report format according to an embodiment of the present disclosure. As shown in fig. 6B, the status report at least includes a D/C field for indicating that the status report is an RLC control PDU; in addition to this, a sequence number Discard SN field for indicating discarded packets is included.

As an optional implementation, if there are multiple types of PDUs, the status report further includes a PDU Type (PDU Type) field for indicating that the RLC control PDU is a status report, and more specifically, for indicating that the RLC control PDU is a status report of discarded packets.

Referring to fig. 6C, fig. 6C is a schematic diagram of another status report format disclosed in the embodiment of the present application. As shown in fig. 6C, the status report may further include a bitmap (bitmap) in addition to the D/C field and the Discard SN field, for indicating which packets are discarded (i.e. deleted) and which packets are not discarded, starting from the packet with the sequence number of Discard SN or starting from the next packet with the sequence number of Discard SN.

For example, if Discard SN is 8 and bitmap is 100100, it indicates that the packet with sequence number 8 and sequence number 11 is discarded, that is, 6 bits in bitmap correspond to the status of sequence numbers 8 to 13 from left to right (or from right to left), respectively, "1" (or "0") indicates that the packet is discarded, and "0" (or "1") indicates that the packet is not discarded.

On the basis of fig. 6C, a PDU Type (PDU Type) field may be further included for indicating that the RLC control PDU is a status report, and more specifically, for indicating that the RLC control PDU is a status report of discarded packets.

Referring to fig. 6D, fig. 6D is a schematic diagram illustrating another status report format according to an embodiment of the present application. As shown in fig. 6D, the status report may further include a Number field (Number) in addition to the D/C field and the Discard SN field, for indicating the Number of packets consecutively discarded from the packet with the sequence Number of Discard SN (or from the next packet of the packet with Discard SN).

For example, if Discard SN is 8 and Number is 3, three packets with

sequence numbers

8, 9, and 10 are all discarded (or four packets with

sequence numbers

8, 9, 10, and 11 are all discarded).

The RLC layer of the apparatus as the data sender indicates the discarded RLC SDU or RLC PDU using the status report, and when the data receiver receives the status report, it can perform normal packet sequencing without waiting for the discarded packet.

On the basis of fig. 6D, a PDU Type (PDU Type) field may be further included for indicating that the RLC control PDU is a status report, and more specifically, for indicating that the RLC control PDU is a status report of discarded packets.

Referring to fig. 7, fig. 7 is a schematic diagram of another application scenario of a communication system according to an embodiment of the present application. In a 5G network, the physical composition of the network devices is a CU-DU architecture, in which the PDCP layer may be located in a Centralized Unit (CU), and the RLC, MAC and PHY layers are located in a DU (Distributed Unit). In this case, the data processing methods in fig. 2 to 6 described above can be applied.

However, considering that a large delay may be caused by data transmission between the CU and the DU, if the PDCP layer instructs the RLC layer to delete a data packet, the data packet may not be deleted in time due to the delay caused by the data transmission between the CU and the DU. Therefore, it can be considered to set a timer in the RLC layer and to perform a data deletion operation in time.

Referring to fig. 8, fig. 8 is a schematic flowchart illustrating another data processing method according to an embodiment of the present application.

801. The CU sends PDCP PDUs, also called RLC SDUs, to the DUs.

In the embodiment of the present application, the PDCP PDU reaches the RLC layer in the DU, which is called RLC SDU.

802. The DU starts a timing operation when it receives the RLC SDU.

That is, a timer for the RLC PDU is set in the RLC layer, and the timer for the RLC PDU is started when the DU receives the RLC SDU.

As an alternative embodiment, the DU may also start a timing operation when encapsulating the RLC SDU into an RLC PDU.

803. If the time of the timing operation exceeds a preset time threshold, the RLC layer in the DU deletes the data of the RLC SDU or the RLC SDU encapsulated into the RLC PDU.

That is, when the timer for the RLC SDU times out, the RLC layer in the DU deletes the RLC SDU or the RLC PDU corresponding to the RLC SDU.

As an optional implementation manner, the 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 and the requirement on timeliness is weak, the preset time threshold should be set to be longer.

As an alternative embodiment, the data deleting manner in step 703 may refer to the operations performed on the RLC PDU in fig. 2 to 5. In addition, if the RLC SDU is not yet encapsulated into the RLC PDU by the RLC layer at this time, the RLC SDU is deleted as it is.

With the data processing method described in fig. 8, it is possible to avoid a delay in data transmission between the CU and the DU so that the RLC layer in the DU cannot perform a data deletion operation in time.

Furthermore, the above embodiments are also applicable to the network architecture of fig. 1.

In addition, in the data transmission process, for example, if the base station is used as a data transmitting side and the user terminal is used as a data receiving side, the RLC layer of the base station performs data processing according to the method shown in any one of fig. 2 to 6 and 8 to obtain a data packet, and the data packet passes through the MAC layer, the PHY layer and the communication link and then reaches the user terminal which is used as the data receiving side.

The RLC layer of the user equipment receives the RLC PDU or the status report, and the specific situations include the following:

the first condition is as follows: the RLC layer receives the RLC PDU with the sequence number x, and the data field of the RLC PDU is empty, then the RLC layer considers (or determines) the RLC PDU (or SDU) with the sequence number x as received, does not wait for the PDU with the sequence number x any more, and receives the PDU with the sequence number unequal to x instead, or does not feed back the PDU with the sequence number x in a status report generated and fed back to a data sending party.

Case two: the RLC entity receives the RLC PDU with the sequence number x, and before receiving the RLC PDU, the RLC entity already receives a plurality of RLC PDUs with the sequence number x, if the data field of the received RLC PDU is empty, the RLC entity deletes all RLC PDUs with the sequence number x or data in the RLC PDUs, and considers (or determines) the RLC SDU with the sequence number x as received.

Case three: the RLC entity receives the status report, analyzes the status report, acquires information that the data packet with the sequence number x is discarded, and considers (or determines) that the data packet x indicated to be discarded in the status report is received.

Referring to fig. 9, fig. 9 is a schematic structural diagram of an apparatus 900 according to an embodiment of the present disclosure. As shown in fig. 9, the apparatus 900 may include an acquisition unit 901 and a deletion unit 902.

An obtaining unit 901 is configured to obtain a service data unit SDU of a radio link control RLC layer.

A deleting unit 902, configured to delete data according to a data deleting method, where the data deleting method includes: deleting the SDU acquired by the acquisition unit, or deleting a first Protocol Data Unit (PDU) encapsulated by the SDU, or deleting a data field in the first PDU.

It should be noted that the implementation of the above units may also correspond to the corresponding description of the method embodiments shown in fig. 2 to 6 and fig. 8.

The radio link control layer of the device 900 may delete data that does not need to be transmitted according to different data deletion modes, thereby saving wireless communication resources.

Referring to fig. 10, fig. 10 is a schematic structural diagram of a base station 1000 according to an embodiment of the present disclosure. The base station 1000 may perform operations as in the methods of fig. 2-6 and 8.

The base station 1000 includes one or more Remote Radio Units (RRUs) 1001 and one or more baseband units (BBUs) 1002. The RRU1001 may be referred to as a transceiver unit, transceiver circuit, or transceiver, etc., which may include at least one antenna 1011 and a radio frequency unit 1012. The RRU1001 section is mainly used for transceiving radio frequency signals and converting radio frequency signals and baseband signals. The BBU1002 is mainly used for performing baseband processing, controlling a base station, and the like. The RRU1001 and the BBU1002 may be physically disposed together or may be physically disposed separately, that is, distributed base stations.

The BBU1002 is a control center of a base station, and may also be referred to as a processing unit, and is mainly used for performing baseband processing functions, such as channel coding, multiplexing, modulation, and spreading. For example, the BBU (processing unit) described above can be used to control the base station to execute the flows shown in fig. 2 to 6 and 8.

In an example, the BBU1002 may be formed by one or more boards, and the boards may jointly support a radio access network (e.g., an LTE network) of a single access system, or may respectively support radio access networks of different access systems. The BBU1002 described above further includes a memory 1021 and a processor 1022. The memory 1021 is used for storing necessary messages and data. The processor 1022 is configured to control the base station to perform necessary operations, for example, control the base station to execute the flows shown in fig. 2 to 6 and 8. The memory 1021 and the processor 1022 may serve one or more boards. That is, the memory and processor may be provided separately on each board. Or multiple boards may share the same memory and processor. In addition, each single board is provided with necessary circuits.

Referring to fig. 11, fig. 11 is a schematic structural diagram of a terminal 1100 according to an embodiment of the present disclosure. The terminal may perform the operation of the terminal in the methods illustrated in fig. 2 to 6 and 8.

For convenience of explanation, fig. 11 shows only main components of the terminal. As shown in fig. 11, the terminal 1100 includes a processor, a memory, a control circuit, an antenna, and an input-output device. The processor is mainly configured to process the communication protocol and the communication data, control the entire user equipment, execute a software program, and process data of the software program, for example, to support the terminal to execute the processes described in fig. 2 to 6 and 8. The memory is used primarily for storing software programs and data. The control circuit is mainly used for converting baseband signals and radio frequency signals and processing the radio frequency signals. The control circuit and the antenna together, which may also be called a transceiver, are mainly used for transceiving radio frequency 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, etc. for mainly receiving data input by a user and outputting data to the user.

When the terminal is started, 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. When data needs to be sent wirelessly, the processor outputs a baseband signal to the radio frequency circuit after performing baseband processing on the data to be sent, and the radio frequency circuit performs radio frequency processing on the baseband signal and sends the radio frequency signal outwards in the form of electromagnetic waves through the antenna. When data is sent to the terminal, the radio frequency circuit receives radio frequency signals through the antenna, converts the radio frequency signals into baseband signals and outputs the baseband signals to the processor, and the processor converts the baseband signals into the data and processes the data.

Those skilled in the art will appreciate that 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, which is not limited in this application.

As an alternative implementation manner, the processor may include a baseband processor and a central processing unit, where the baseband processor is mainly used to process a communication protocol and communication data, and the central processing unit is mainly used to control the whole terminal, execute a software program, and process data of the software program. The processor in fig. 11 integrates the functions of the baseband processor and the central processing unit, and those skilled in the art will understand that the baseband processor and the central processing unit may also be independent processors, and are interconnected through a bus or the like. Those skilled in the art will appreciate that the terminal may include a plurality of baseband processors to accommodate different network formats, a plurality of central processors to enhance its processing capability, and various components of the terminal may be connected by various buses. The baseband processor may also be expressed as a baseband processing circuit or a baseband processing chip. The central processing unit may also be expressed as a central processing circuit or a central processing chip. The function 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 realize the baseband processing function.

For example, in the embodiment of the present invention, an antenna and a control circuit having a transceiving function may be regarded as the transceiving unit 1101 of the terminal 1100, and a processor having a processing function may be regarded as the processing unit 1102 of the terminal 1100. As shown in fig. 11, the terminal 1100 includes a transceiving unit 1101 and a processing unit 1102. A transceiver unit may also be referred to as a transceiver, a transceiving device, etc. Optionally, a device for implementing the receiving function in the transceiving unit 1101 may be regarded as a receiving unit, and a device for implementing the transmitting function in the transceiving unit 1101 may be regarded as a transmitting unit, that is, the transceiving unit 1101 includes a receiving unit and a transmitting unit. For example, the receiving unit may also be referred to as a receiver, a receiving circuit, etc., and the sending unit may be referred to as a transmitter, a transmitting circuit, etc.

The radio link control layer of the terminal 1100 may delete data that does not need to be transmitted according to different data deletion modes, thereby saving wireless communication resources.

The embodiment of the application discloses a scheduling request sending method and equipment, wherein the method comprises the following steps: the terminal equipment receives a scheduling request configuration message sent by network equipment, wherein the configuration message comprises the repeated sending time length of a scheduling request, a scheduling request resource period and the time length of a scheduling request prohibition timer; and respectively and repeatedly sending a first scheduling request and a second scheduling request by the terminal equipment according to the scheduling request configuration message, wherein the scheduling request prohibition timer is started when the terminal equipment starts to repeatedly send the first scheduling request, and the terminal equipment sends the second scheduling request after the scheduling request prohibition timer is overtime and the first scheduling request is sent. By adopting the embodiment of the application, the conflict of sending the scheduling request can be avoided, the success rate of receiving the scheduling request is improved, and the consumption of wireless communication resources is reduced.

1. A method for sending a scheduling request, comprising:

the terminal equipment receives a scheduling request configuration message sent by network equipment, wherein the configuration message comprises the repeated sending time length of a scheduling request, a scheduling request resource period and the time length of a scheduling request prohibition timer;

and respectively and repeatedly sending a first scheduling request and a second scheduling request by the terminal equipment according to the scheduling request configuration message, wherein the scheduling request prohibition timer is started when the terminal equipment starts to repeatedly send the first scheduling request, and the terminal equipment sends the second scheduling request after the scheduling request prohibition timer is overtime and the first scheduling request is sent.

2. The method of claim 1, wherein:

the repeated sending time length is less than or equal to the scheduling request forbidding timer time length.

3. The method of claim 1, wherein:

the repeated sending time length is longer than the time length of the scheduling request prohibition timer;

the terminal device sends the second scheduling request after the scheduling request prohibit timer is overtime and after the first scheduling request is sent, including:

the terminal device abandons the use of the scheduling request resource occurring when the first scheduling request is repeatedly transmitted to transmit the scheduling request; or the terminal equipment sends the first scheduling request and/or the second scheduling request within the duration of the scheduling request prohibit timer; or the media access control layer of the terminal device gives up sending the scheduling request to the physical layer when the physical layer repeatedly sends the first scheduling request.

4. The method of claim 2, wherein the prohibit timer duration is a product of the scheduling request resource period and a non-negative integer, wherein the scheduling request resource period comprises a first 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, wherein the non-negative integer comprises a first non-negative integer and a second non-negative integer, and wherein the first non-negative integer is greater than the second non-negative integer;

the repeatedly sending duration is less than or equal to the scheduling request prohibit timer duration, including:

the scheduling request prohibit timer duration is the product of the first scheduling request resource period and the non-negative integer; or the scheduling request prohibit timer duration is a product of the prohibit timer duration and the first non-negative integer.

5. A scheduling request receiving method, comprising:

the network equipment sends a scheduling request configuration message to the terminal equipment, wherein the configuration message comprises the repeated sending time length of a scheduling request, a scheduling request resource period and the time length of a scheduling request prohibition timer;

and the network equipment receives a first scheduling request and a second scheduling request which are respectively and repeatedly sent by the terminal equipment according to the scheduling request configuration message, wherein the repeated sending time length is less than or equal to the time length of a scheduling request prohibition timer.

6. The method of claim 5, wherein the prohibit timer duration is a product of the scheduling request resource period and a non-negative integer, wherein the scheduling request resource period comprises a first 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, wherein the non-negative integer comprises a first non-negative integer and a second non-negative integer, and wherein the first non-negative integer is greater than the second non-negative integer;

7. A terminal device, comprising:

a receiving unit and a sending unit, wherein,

the receiving unit is used for receiving a scheduling request configuration message sent by network equipment, wherein the configuration message comprises a repeated sending time length of a scheduling request, a scheduling request resource period and a scheduling request prohibition timer time length;

the sending unit is configured to repeatedly send a first scheduling request and a second scheduling request according to the scheduling request configuration message, wherein the sending unit starts the scheduling request prohibit timer when the first scheduling request starts to be repeatedly sent, and the sending unit sends the second scheduling request after the scheduling request prohibit timer expires and after the first scheduling request is sent.

8. The terminal device of claim 7, wherein:

9. The terminal device of claim 7, wherein:

the sending unit sends the second scheduling request after the scheduling request prohibit timer expires and after the first scheduling request is sent, including:

the transmission unit abandons transmission of a scheduling request using a scheduling request resource that occurs when the first scheduling request is repeatedly transmitted; or, the sending unit sends the first scheduling request and/or the second scheduling request within the duration of the scheduling request prohibit timer; or the media access control layer of the terminal device gives up sending the scheduling request to the physical layer when the physical layer repeatedly sends the first scheduling request.

10. The method of claim 8, wherein the prohibit timer duration is a product of the scheduling request resource period and a non-negative integer, wherein the scheduling request resource period comprises a first 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, wherein the non-negative integer comprises a first non-negative integer and a second non-negative integer, and wherein the first non-negative integer is greater than the second non-negative integer;

11. A network device, comprising:

a sending unit and a receiving unit, wherein,

the sending unit is used for sending a scheduling request configuration message to the terminal equipment, wherein the configuration message comprises the repeated sending time length of the scheduling request, the resource period of the scheduling request and the time length of a scheduling request prohibition timer;

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, respectively, where a repeatedly sent duration is less than or equal to a duration of a scheduling request prohibit timer.

12. The method of claim 11, wherein the prohibit timer duration is a product of the scheduling request resource period and a non-negative integer, wherein the scheduling request resource period comprises a first 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, wherein the non-negative integer comprises a first non-negative integer and a second non-negative integer, and wherein the first non-negative integer is greater than the second non-negative integer;

In the prior art, when a User Equipment (UE) (or called 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 a Buffer Status Report (BSR) to the eNB to indicate a current data volume of the UE. If the UE does not send BSR resources at this time, the UE needs to send a Scheduling Request (SR) to the eNB to Request the eNB to send BSR resources. In the connected state, the eNB may configure resources for each UE to transmit an SR. In a Long Term Evolution (LTE) Communication system, a UE may send a complete SR in one subframe, whereas in Machine Type Communication (MTC), since the UE is in an area with poor signal coverage, the UE needs to repeatedly send the SR to an eNB. Considering that the SR resource configured by the eNB for the UE appears periodically, if the UE triggers SR repeat transmission and does not receive the resource allocation message of the eNB, the UE may send a new SR to the eNB again when the SR resource appears, and if the time for the UE to repeatedly send 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 time allowed by the eNB to send the SR, the UE may trigger new SR transmission when the previous SR transmission is not completed, causing SR transmission collision, and reducing the success rate of the eNB receiving the SR.

The embodiment of the application provides a scheduling request sending method and equipment, and by adopting the embodiment of the application, the conflict of sending the scheduling request can be avoided, and the success rate of receiving the scheduling request is improved.

In a first aspect, an embodiment of the present application provides a scheduling request sending method, including:

As an optional implementation manner, the repeated transmission time length is less than or equal to the scheduling request prohibit timer time length.

As an optional implementation manner, the repeated sending duration is greater than the scheduling request prohibit timer duration; the terminal device sends the second scheduling request after the scheduling request prohibit timer is overtime and after the first scheduling request is sent, including:

the terminal device abandons the use of the scheduling request resource occurring when the first scheduling request is repeatedly transmitted to transmit the scheduling request;

the terminal equipment sends the first scheduling request and/or the second scheduling request within the duration of the scheduling request prohibition timer;

and the media access control layer of the terminal equipment gives up the instruction of sending the scheduling request to the physical layer when the physical layer repeatedly sends the first scheduling request.

As an optional implementation manner, the prohibit 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, 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, and the first non-negative integer is greater than the second non-negative integer;

the scheduling request prohibit timer duration is the product of the first scheduling request resource period and the non-negative integer;

the scheduling request prohibit timer duration is a product of the prohibit timer duration and the first non-negative integer.

In a second aspect, the present application provides a scheduling request receiving method, including:

In a third aspect, the present application provides a terminal device, including:

a receiving unit and a sending unit, wherein,

As an optional implementation manner, the repeated sending duration is greater than the scheduling request prohibit timer duration;

the transmission unit abandons transmission of a scheduling request using a scheduling request resource that occurs when the first scheduling request is repeatedly transmitted;

the sending unit sends the first scheduling request and/or the second scheduling request within the duration of the scheduling request prohibition timer;

In a fourth aspect, the present application provides a network device, comprising:

a sending unit and a receiving unit, wherein,

As an alternative implementation, the terminal device and the network device provided by the present application may contain units for performing the steps in the above method design. The units may be software and/or hardware. Optionally, the terminal device and the network device provided by the present application include a processor and a transceiver in their structures, where the processor is configured to support the terminal device and the network device to execute corresponding functions in the foregoing methods. The transceiver is used for supporting communication between the network equipment and the terminal equipment and sending the information or the message related in the method to the network equipment. The terminal device may also include a memory for coupling to the processor that stores program messages and data necessary for the terminal device.

In a fifth aspect, embodiments of the present application provide a computer program product containing messages, which when run on a computer, causes the computer to perform the method of the above aspects.

In a sixth aspect, the present application provides a computer-readable storage medium, which stores a message and when running on a computer, causes the computer to execute the method of the above aspects.

By implementing the embodiment of the application, the conflict of sending the scheduling request can be avoided, and the success rate of receiving the scheduling request is improved.

Referring to fig. 12, 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 may employ an LTE network or a Next Generation (NR or 5G) network. As shown in fig. 12, a terminal device accesses to a network through a network device, such as an Evolved Node B (eNB) in LTE, and interacts with the eNB to implement data transmission and reception. In a 5G system, the base station may also be a 5G base station gNB.

The terminal device may be a mobile phone, an intelligent terminal, a multimedia device, a streaming media device, and the like, and the embodiment of the present application is not limited. The eNB is a bridge between a user terminal in an LTE network and an Evolved Packet Core (EPC), and is connected to the eNB through an X2 interface, and has main functions of: radio resource Management, IP header compression and user data stream encryption, Mobility Management Entity (MME) selection when a user terminal is attached, routing of user plane data to a Serving Gateway (S-GW), organization and transmission of paging messages, organization and transmission of broadcast messages, measurement and measurement report configuration for Mobility or scheduling, and the like.

Referring to fig. 13, fig. 13 is a schematic diagram illustrating a Scheduling Request (SR) resource configuration in the prior art according to an embodiment of the present application. In the prior art, when a User Equipment (UE) (or called 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 a Buffer Status Report (BSR) to the eNB to indicate a current data volume of the UE. If the UE does not send BSR resources at this time, the UE needs to send a Scheduling Request (SR) to the eNB to Request the eNB to send BSR resources. In the connected state, the eNB may configure the resource for transmitting the SR to each UE, and the resource configuration is as shown in fig. 13. eNB configures period of SR Resources (SR) for UE_PERIODICITY) And offset (N)_OFFSET,SR) The UE transmits the SR on a Subframe in which a System Frame Number (SFN) and a Subframe Number (Subframe, sf) satisfy the following formula:

(SFN×10+sf–N_OFFSET,SR)mod S_RPERIODICITY＝0

where mod is a modulo operation or a remainder operation.

Taking FIG. 13 as an example, where N_OFFSET,SR＝1，S_RPERIODICITYThe UE may send an SR on sub-slot 1 and sub-slot 6 of each system frame, 5.

In the prior art, N_OFFSET,SRAnd S_RPERIODICITYOther values may also be configured, as shown in table 1.

TABLE 1

As can be seen from table F1, the current SR resource maximum period is 80 milliseconds (ms).

The eNB configures an SR configuration index to the UE, that is, the SR period and the offset may be configured correspondingly. For example, the eNB configures SR configuration index I to the UE_SRAs can be seen from 16, it corresponds to the row with SR configuration index (15-34), and SR is now the case_PERIODICITY＝20ms，N_OFFSET,SR＝I_SR15-16-15-1, i.e., the SR resource configuration shown in fig. 14.

In addition, in the prior art, the eNB also configures an SR-prohibit timer (SR-prohibit timer) for the UE, and when the UE starts to send the SR, the UE starts the timer, and during the running period of the timer, the UE may not send the SR, even if the current UE has valid SR resources, only when the timer is overtime, and when the UE needs to send the SR and the UE has valid SR resources, the UE may send the SR. In the prior art, the duration of the timer is determined by the product of the SR period and the nonnegative integer, and the value range of the nonnegative integer is [0,1,2,3,4,5,6,7 ].

In a Long Term Evolution (LTE) Communication system, a UE may complete SR transmission in one subframe, and in Machine Type Communication (MTC), since the UE is in an area with poor signal coverage, the UE needs to repeatedly transmit an SR to an eNB, as shown in fig. 15, the eNB configures an SR resource shown in fig. 14 for the UE, when the UE needs to transmit an SR, for example, the UE starts to transmit an SR in subframe 1 of system frame No. 12, and since the UE is in an area with weak signal, the UE needs to repeatedly transmit an SR to the eNB, for example, the eNB configures the UE to transmit an SR 10 times, as shown in fig. 15, the UE starts to transmit an SR from subframe 1 of system frame No. 12, and continuously transmits an SR 9 times in the next 9 subframes (or 10 uplink active subframes), that is, 10 times of total SR transmission. In the prior art, the number of times that the eNB configures the UE to repeatedly transmit the SR may be 16, 32, 64, 128.

Referring to fig. 16, considering that the SR resource configured by the eNB for the UE appears periodically, if the UE does not receive the resource allocation message of the eNB after triggering the SR repeat transmission, the UE may send a new SR to the eNB again after the SR resource appears and the scheduling request prohibit timer expires. Here, it is assumed that the non-negative integer is 1, i.e., the scheduling request prohibit timer duration is one SR period. If the time for the UE to repeatedly send 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 time allowed by the eNB to send the SR, the UE triggers new SR transmission when the previous SR is not sent, thereby causing SR transmission collision and reducing the success rate of the eNB receiving the SR. Taking fig. 16 as an example, at this time, the eNB configures an SR period of 5ms, an offset of 1 subframe, that is, 1ms, the number of SR repeated transmissions is 8, and the duration of the scheduling request prohibit timer is 5 ms. The UE starts to transmit the SR at subframe 1 of system frame No. 12 and continues to transmit 8 times. On the subframe No. 5 of the system frame No. 12, since the UE does not receive the resource allocation message of the eNB and has valid SR resources at this time, the UE is triggered to repeatedly send the SR, and at this time, the UE does not finish the previous SR repeated sending, and then triggers new SR sending, which causes SR sending collision.

In view of the above SR transmission collision problem, the following embodiments are disclosed in the present application to solve the above collision problem.

Example one

Referring to fig. 17, fig. 17 is a flowchart illustrating a scheduling request sending method disclosed in an embodiment of the present application. The execution subject of the method is terminal equipment.

171. The terminal equipment receives a scheduling request configuration message sent by network equipment, wherein the configuration message comprises the repeated sending time length of a scheduling request, a scheduling request resource period and the time length of a scheduling request prohibition timer;

here, the terminal device is described by taking UE as an example, and the network device is described by taking eNB as an example. In the connected state, the eNB configures the periodic SR resources of the UE. For example, the UE receives a connection reconfiguration message (RRCConnectionReconfiguration) of Radio Resource Control (RRC) sent by the eNB, where the RRCConnectionReconfiguration message includes a scheduling request configuration message (scheduling request configuration), specifically, a repeat sending duration of a scheduling request, a scheduling request Resource period, and a scheduling request prohibit timer duration, and these messages may be included in one message or may be included in multiple messages, which are not limited in this application and are collectively referred to as a scheduling request configuration message. The duration of the repeated transmission of the scheduling request may be the number of times of the repeated transmission of the scheduling request, and since the scheduling request is transmitted on a Physical Uplink Control Channel (PUCCH), the number of times of the repeated transmission of the scheduling request may also be the number of times of the repeated transmission of the PUCCH. Here, it can be understood that the number of times corresponds to the number of subframes, for example, 10 times of repeated transmission, i.e., 10 times of transmission over 10 subframes. Alternatively, the repeated transmission duration may be a time elapsed from the first transmission to the last transmission, that is, the scheduling request may be transmitted on a continuous uplink subframe, such as FDD, or may be transmitted on a discontinuous uplink subframe, such as TDD, the scheduling request resource period may be obtained by looking up a table, that is, the eNB may configure an index of the UE corresponding to the scheduling request resource period, and the UE determines the scheduling request resource period by using the index value, as shown in fig. F1. The duration of the scheduling request prohibit timer may be a specific time length, or may be determined by the product of the scheduling request resource period and a non-negative integer. The duration of the scheduling request prohibit timer may be understood as a continuous time, or may be understood as a time of several discontinuous uplink subframes.

172. And respectively and repeatedly sending a first scheduling request and a second scheduling request by the terminal equipment according to the scheduling request configuration message, wherein the scheduling request prohibition timer is started when the terminal equipment starts to repeatedly send the first scheduling request, and the terminal equipment sends the second scheduling request after the scheduling request prohibition timer is overtime and the first scheduling request is sent.

The first scheduling request is an SR which is sent by the UE at the beginning or at the previous time, and the second scheduling request is an SR which is sent by the UE again after the UE repeatedly sends the first scheduling request (or during the process of repeatedly sending the first scheduling request by the UE), because the UE does not receive the resource allocation message of the eNB, when the UE has valid SR resources and the scheduling request prohibit timer expires. In this application, it is specified that the UE may send the second scheduling request after the first scheduling request is sent and after the scheduling request prohibit timer expires. Wherein the understanding of the completion of the first scheduling request transmission is described in detail in the following embodiments.

Example two

Fig. 18 is a schematic diagram of another scheduling request sending method disclosed in an embodiment of the present application. On the basis of the first embodiment, the repeatedly sending duration is less than or equal to the scheduling request prohibit timer duration. Specifically, in fig. 18, the SR repetition transmission duration is 6 subframes, i.e., 6 ms. The SR prohibit timer duration is 10 subframes, i.e., 10 ms. During the SR prohibit timer running, the UE will not trigger a new SR transmission any more. In this way, since the SR retransmission time duration is less than the SR prohibit timer time duration, the UE can complete the SR retransmission before triggering the next SR retransmission, that is, the previous SR retransmission does not collide with the next SR retransmission. In this way, the UE can normally trigger and transmit the second scheduling request (i.e., the next SR) after the first scheduling request (i.e., the previous SR) is transmitted and after the scheduling request prohibit timer expires.

EXAMPLE III

Fig. 19 is a schematic diagram of another scheduling request sending method disclosed in an embodiment of the present application. On the basis of the first embodiment, the repeatedly sending duration is greater than the scheduling request prohibit timer duration.

As a possible implementation manner, in particular, in fig. 19, the eNB configured SR repetition transmission duration is 7 subframes, that is, 7 ms. The SR prohibit timer duration is 5 subframes, i.e., 5 ms. During the SR prohibit timer running, the UE will not trigger a new SR transmission any more. However, after the SR prohibit timer expires, if the UE has not received the eNB resource configuration message, the UE will continue to trigger and send the SR on the valid SR resource. In fig. 19, the UE first triggers SR transmission on subframe 1 of system frame 12, and repeatedly transmits SR for 7 consecutive subframes. In the subframe No. 6 of the system frame No. 12, if the UE does not receive the resource configuration message of the eNB, at this time, because the SR prohibit timer has timed out, the UE will trigger SR transmission again, which will collide with the SR repeatedly transmitted last time. To avoid collision, at this time, since the UE has not yet finished transmitting the previous SR, the UE may give up using the SR resource occurring during the previous SR transmission, that is, the UE continues to transmit the previous SR (i.e., the first SR) that has not been transmitted. In this way, the SR duration actually transmitted by the UE is the same as the SR transmission duration configured by the eNB to the UE.

If the UE completes the previous repeated SR transmission (i.e., the first SR), but still does not receive the eNB resource configuration message, i.e., the UE does not receive the eNB resource configuration message before the subframe 1 of the system frame No. 13, the UE may continue to trigger and transmit the next SR (i.e., the second SR) on the subframe 1 of the system frame No. 13.

At this time, the first scheduling request is sent in the first embodiment, that is, the UE sends the SR according to the SR repetition sending duration configured by the eNB, and the sending is completed, that is, the duration for actually sending the SR is equal to the duration for configuring the sent SR.

As another possible implementation, specifically, in fig. 20, the eNB configured SR repetition transmission duration is 7 subframes, that is, 7 ms. The SR prohibit timer duration is 5 subframes, i.e., 5 ms. During the SR prohibit timer running, the UE will not trigger a new SR transmission any more. However, after the SR prohibit timer expires, if the UE has not received the eNB resource configuration message, the UE will continue to trigger and send the SR on the valid SR resource. In fig. 20, the UE first triggers SR transmission on subframe 1 of system frame 12, and repeatedly transmits SRs for 7 consecutive subframes. In the subframe No. 6 of the system frame No. 12, if the UE does not receive the resource configuration message of the eNB, at this time, because the SR prohibit timer has timed out, the UE will trigger SR transmission again, which will collide with the SR repeatedly transmitted last time. To avoid collision, at this time, since the UE has not completed transmission of the previous SR, the UE may abandon the previous SR (i.e., the first SR) transmission, and the UE triggers and transmits the next SR (i.e., the second SR). Thus, the SR duration actually transmitted by the UE is smaller than the SR transmission duration configured by the eNB to the UE.

If the UE completes the previous repeated SR transmission (i.e., the first SR), but still does not receive the eNB resource configuration message, i.e., the UE does not receive the eNB resource configuration message before the subframe 6 of the system frame No. 12, the UE may continue to trigger and transmit the next SR (i.e., the second SR) on the subframe 6 of the system frame No. 12.

At this time, the first scheduling request is completely sent in the first embodiment, which may be understood as that the UE sends the SR according to the SR prohibit timer configured by the eNB, and when the timer expires, the UE stops sending the SR (i.e., the first SR), and at this time, the UE determines that the first SR is completely sent.

As another possible implementation, specifically, in fig. 19, the eNB configured SR repetition transmission duration is 7 subframes, that is, 7 ms. The SR prohibit timer duration is 5 subframes, i.e., 5 ms. During the SR prohibit timer running, the UE will not trigger a new SR transmission any more. In this application, the trigger is that a Media Access Control (MAC) layer of the UE instructs a Physical (PHY) layer of the UE to transmit the SR. However, after the SR prohibit timer expires, if the UE has not received the eNB resource configuration message, the UE will continue to trigger and send the SR on the valid SR resource. In fig. 19, the UE first triggers SR transmission on subframe 1 of system frame 12, and repeatedly transmits SR for 7 consecutive subframes. In the subframe No. 6 of the system frame No. 12, if the UE does not receive the resource configuration message of the eNB, at this time, because the SR prohibit timer has timed out, the UE will trigger SR transmission again, which will collide with the SR repeatedly transmitted last time. In order to avoid collision, at this time, since the previous SR of the UE has not been sent, when the physical layer repeatedly sends the previous SR (i.e., the first SR), the MAC layer of the UE abandons to instruct the physical layer to send the next SR (i.e., the second SR), that is, only after the current SR (i.e., the first SR) is sent according to the number of times configured by the eNB and the scheduling request prohibit timer is expired, the MAC layer instructs the PHY layer to send the next SR (i.e., the second SR). In this way, the SR duration actually transmitted by the UE is equal to the SR transmission duration configured by the eNB to the UE.

If the UE completes the previous repeated SR transmission (i.e., the first SR), but still does not receive the eNB resource configuration message, i.e., the UE does not receive the eNB resource configuration message before the subframe 1 of the system frame No. 13, the MAC layer of the UE may continue to transmit the next SR (i.e., the second SR) to the PHY indication on the subframe 1 of the system frame No. 13.

As an optional implementation manner, according to the second embodiment, the duration of the prohibit timer 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, that is, a candidate scheduling request resource period configurable by the eNB includes at least two values, one of which is referred to as the first scheduling request resource period, and the other is referred to as the second scheduling request resource period. Wherein 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;

that is, when the eNB configures the duration of the scheduling request prohibit timer and the duration of the repeat transmission of the UE, it is to be ensured that the duration of the repeat transmission is less than or equal to the duration of the scheduling request prohibit timer, so that the first SR and the second SR will not collide. In the present application, the repeated transmission duration may also be a repeated transmission number. If the eNB has multiple choices in configuring the SR prohibit timer duration and the SR period, that is, the non-negative integer has a large or small value, and/or the SR period has a large or small value. If the eNB configuration is not limited to the non-negative integer, it is required to specify that the eNB uses a larger period value, i.e., the first scheduling request resource period, when configuring the SR period.

As another optional implementation manner, according to the second embodiment, the duration of the prohibit timer 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, that is, the candidate scheduling request resource period configurable by the eNB includes at least two values, one of which is referred to as the first scheduling request resource period, and the other is referred to as the second scheduling request resource period. Wherein 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;

That is, when the eNB configures the duration of the scheduling request prohibit timer and the duration of the repeat transmission of the UE, it is to be ensured that the duration of the repeat transmission is less than or equal to the duration of the scheduling request prohibit timer, so that the first SR and the second SR will not collide. In the present application, the repeated transmission duration may also be a repeated transmission number. If the eNB has multiple choices in configuring the SR prohibit timer duration and the SR period, that is, the non-negative integer has a large or small value, and/or the SR period has a large or small value. If the eNB configuration SR period is not limited, it is necessary to specify that the eNB uses a larger integer, i.e., the first non-negative integer, when configuring the non-negative integer.

Example four

Referring to fig. 21, fig. 21 is a flowchart illustrating a scheduling request sending method disclosed in an embodiment of the present application. The main execution body of the method is a network device.

211. The network equipment sends a scheduling request configuration message to the terminal equipment, wherein the configuration message comprises the repeated sending time length of a scheduling request, a scheduling request resource period and the time length of a scheduling request prohibition timer;

the details of the message and the parameter configuration in this step are described in the first embodiment, and are not described herein.

212. And the network equipment receives a first scheduling request and a second scheduling request which are respectively and repeatedly sent by the terminal equipment according to the scheduling request configuration message, wherein the repeated sending time length is less than or equal to the time length of a scheduling request prohibition timer.

This step is similar to S102 of the first embodiment, and is not repeated here.

As an optional implementation manner, according to the fourth embodiment, the prohibit 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, 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, and the first non-negative integer is greater than the second non-negative integer;

the detailed description is given in the third embodiment, which is not repeated herein.

As another optional implementation manner, according to a fourth embodiment, the prohibit 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, 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, and the first non-negative integer is greater than the second non-negative integer;

Fig. 22 is a schematic structural diagram of a terminal device 2200 disclosed in an embodiment of the present application. The terminal device includes a receiving unit 2201 and a transmitting unit 2202.

the description of the message and the parameter configuration related to the terminal device is described in the first embodiment, and is not described herein again.

As an alternative implementation manner, on the basis of the terminal device shown in fig. 22, the repeated transmission time length is less than or equal to the scheduling request prohibit timer time length, which is described in detail in example two. The terminal device at this point is denoted 210.

As another alternative implementation, on the basis of the terminal device shown in fig. 22, the repeatedly sending duration is greater than the duration of the scheduling request prohibit timer;

the sending unit abandons sending the scheduling request by using the scheduling request resource which appears when the first scheduling request is repeatedly sent, which is described in the third embodiment.

the sending unit sends the first scheduling request and/or the second scheduling request within the duration of the scheduling request prohibit timer, which is described in detail in the third embodiment.

As another optional implementation manner, on the basis of the terminal device 210, the prohibit 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, 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, and the first non-negative integer is greater than the second non-negative integer;

the duration of the scheduling request prohibit timer is a product of the first scheduling request resource period and the non-negative integer, which is described in detail in the third embodiment.

the duration of the scheduling request prohibit timer is a product of the duration of the prohibit timer and the first non-negative integer, which is described in detail in the third embodiment.

Fig. 23 is a schematic structural diagram of a network device 2300 disclosed in the embodiment of the present application. The network device includes a transmitting unit 2301 and a receiving unit 2302.

the details of the message and the parameter configuration related to the network device are described in the fourth embodiment, which are not described herein.

As an optional implementation manner, on the basis of the network device shown in fig. 23, the prohibit 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, 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, and the first non-negative integer is greater than the second non-negative integer;

the duration of the scheduling request prohibit timer is a product of the first scheduling request resource period and the non-negative integer, which is described in detail in the fourth embodiment.

As another optional implementation manner, on the basis of the network device shown in fig. 23, the prohibit 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, 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, and the first non-negative integer is greater than the second non-negative integer;

the duration of the scheduling request prohibit timer is a product of the duration of the prohibit timer and the first non-negative integer, which is described in detail in embodiment four.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product comprises one or more computer messages. The procedures or functions described in accordance with the embodiments of the present application are generated in whole or in part when the above-described computer program messages are loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The 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 transmitted from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that includes one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

Additionally, the systems, devices, and methods described, as well as the illustrations of various embodiments, may be combined or integrated with other systems, modules, techniques, or methods without departing from the scope of the present application. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of devices or units through some interfaces, and may be in an electronic, mechanical or other form.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A data processing method, comprising:

acquiring a Service Data Unit (SDU) of a Radio Link Control (RLC) layer;

deleting data according to a data deleting mode, wherein the data deleting mode comprises the following steps: deleting a first Protocol Data Unit (PDU) encapsulated by the SDU, or deleting a data field in the first PDU;

wherein the method further comprises: distributing a first sequence number to the SDU;

wherein the encapsulating the SDU into the first PDU comprises: under the condition that the SDU is segmented into N sub-data packets, packaging the N sub-data packets into N PDUs;

wherein the content of the first and second substances,

the data deleting mode further comprises: determining one PDU as a second PDU from the N PDUs; deleting a data field in the second PDU; deleting the PDUs of the N PDUs except the second PDU;

wherein the content of the first and second substances,

after the data is deleted according to the data deletion mode, the method further comprises the following steps: modifying indication information in a second header of the second PDU for indicating whether the second PDU is fragmented to indicate that the second PDU is not fragmented.

2. The method of claim 1, wherein the deleting the data field in the first PDU comprises:

deleting the data field in the N PDUs.

3. The method of claim 1, wherein the deleting the first Protocol Data Unit (PDU) into which the SDU is encapsulated comprises:

deleting the first PDU;

4. The method according to any one of claims 1 to 3, wherein the deleting data according to a data deleting mode comprises:

receiving indication information sent by a packet data convergence protocol PDCP layer, wherein the indication information is used for indicating the RLC layer to delete the SDU; deleting data according to the data deleting mode under the condition that the indication information is received;

alternatively, the first and second electrodes may be,

5. The method according to claim 1, wherein if the data deletion mode is the deletion of the first PDU encapsulated by the SDU, after the data deletion according to the data deletion mode, the method further comprises:

6. The method of claim 1, wherein the deleting the first Protocol Data Unit (PDU) into which the SDU is encapsulated comprises:

deleting the N PDUs;

generating a status report indicating that the PDU with the sequence number being the first sequence number is deleted.

7. The method according to claim 5 or 6, wherein the status report further comprises indication information for indicating that the status report is a control PDU of an RLC layer;

8. The method of claim 1, wherein the data deletion method further comprises: deleting the SDU;

distributing a first sequence number to the SDU;

re-assigning the first sequence number to a first SDU obtained after the SDU.

9. A data processing method, comprising:

acquiring a Service Data Unit (SDU) of a Radio Link Control (RLC) layer;

wherein the method further comprises:

distributing a first sequence number to the SDU; encapsulating the SDU into the first PDU, wherein the first PDU comprises a data field and a first packet header, and the first packet header comprises the first sequence number;

wherein, the deleting the first protocol data unit PDU packaged by the SDU comprises:

deleting the first PDU;

10. A data processing method, comprising:

acquiring a Service Data Unit (SDU) of a Radio Link Control (RLC) layer;

wherein the content of the first and second substances,

the data deleting method further comprises the following steps: deleting the SDU;

after the obtaining of the service data unit SDU in the RLC layer and before the deleting of the data according to the data deleting method, the method further includes: distributing a first sequence number to the SDU;

generating a fourth PDU containing a fourth packet header, wherein the fourth packet header contains the first sequence number; or, reassigning the first sequence number to a first SDU obtained after the SDU.

11. A data processing method, comprising:

receiving a status report of a Radio Link Control (RLC) layer;

acquiring a serial number contained in the status report;

determining that the PDU with the sequence number of the first sequence number is received when the sequence number included in the status report is the first sequence number,

wherein the content of the first and second substances,

the method further comprises the following steps: deleting data according to a data deleting mode, wherein the data deleting mode comprises the following steps: deleting a first Protocol Data Unit (PDU) encapsulated by the SDU, or deleting a data field in the first PDU;

wherein the method further comprises:

wherein the content of the first and second substances,

the data deleting mode further comprises: determining one PDU as a second PDU from the N PDUs; deleting a data field in the second PDU; deleting the PDUs except the second PDU in the N PDUs.

12. A data processing method, comprising:

and deleting the PDUs of the M RLC layers under the condition that the data field of at least one PDU in the PDUs of the M RLC layers is empty, and determining that the PDU with the sequence number of the first sequence number is received, wherein the first PDU comprises the data field and a first packet header, and the first packet header comprises the first sequence number.

13. A data processing apparatus comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor when executing the program implements the steps of:

acquiring a Service Data Unit (SDU) of a Radio Link Control (RLC) layer;

deleting data according to a data deleting mode, wherein the data deleting mode comprises the following steps: deleting the SDU acquired by the acquisition unit, or deleting a first Protocol Data Unit (PDU) encapsulated by the SDU, or deleting a data field in the first PDU;

wherein the processor, when executing the program, further implements the steps of: distributing a first sequence number to the SDU; encapsulating the SDU into the first PDU, wherein the first PDU comprises a data field and a first packet header, and the first packet header comprises the first sequence number;

wherein the content of the first and second substances,

after the data is deleted according to the data deleting mode, the processor executes the program and further realizes the following steps:

14. The apparatus of claim 13, wherein the deleting the data field in the first PDU comprises:

deleting the data field in the N PDUs.

15. The apparatus of claim 13, wherein the removing the first protocol data unit PDU into which the SDU is encapsulated comprises:

deleting the first PDU; constructing a third PDU comprising a third packet header comprising a sequence number that is the same as the first sequence number assigned by the assignment unit.

16. The apparatus according to any one of claims 13 to 15, wherein the deleting data according to a data deleting manner comprises:

alternatively, the first and second electrodes may be,

17. The apparatus according to claim 13, wherein if the data deleting manner is the deleting of the first PDU encapsulated by the SDU, after the data is deleted according to the data deleting manner, the processor executes the program to further implement the following steps:

18. The apparatus of claim 13, wherein the removing the first protocol data unit PDU into which the SDU is encapsulated comprises:

deleting the N PDUs;

if the data deleting mode is the deletion of the first protocol data unit PDU packaged by the SDU, after the data is deleted according to the data deleting mode, the processor further realizes the following steps when executing the program:

19. The apparatus according to claim 17 or 18, wherein the status report further comprises indication information indicating that the status report is a control PDU of an RLC layer;

20. The apparatus of claim 13, wherein the data deletion method further comprises: deleting the SDU;

after the service data unit SDU of the radio link control RLC layer is acquired and before the data is deleted according to the data deletion method, the processor further implements the following steps when executing the program:

distributing a first sequence number to the SDU;

if the data deleting method is to delete the SDU, after deleting the data according to the data deleting method, the processor further implements the following steps when executing the program:

re-assigning the first sequence number to a first SDU obtained after the SDU.

21. A data processing apparatus comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor when executing the program implements the steps of:

acquiring a Service Data Unit (SDU) of a Radio Link Control (RLC) layer;

22. A data processing apparatus comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor when executing the program implements the steps of:

acquiring a Service Data Unit (SDU) of a Radio Link Control (RLC) layer;

wherein, the data deleting method further comprises: deleting the SDU;

distributing a first sequence number to the SDU;

re-assigning the first sequence number to a first SDU obtained after the SDU.

23. A data processing apparatus comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor when executing the program implements the steps of:

receiving a status report of a Radio Link Control (RLC) layer;

acquiring a serial number contained in the status report;

wherein, still include: deleting data according to a data deleting mode, wherein the data deleting mode comprises the following steps: deleting a first Protocol Data Unit (PDU) encapsulated by the SDU, or deleting a data field in the first PDU;

wherein, still include: distributing a first sequence number to the SDU; encapsulating the SDU into the first PDU, wherein the first PDU comprises a data field and a first packet header, and the first packet header comprises the first sequence number;

wherein the content of the first and second substances,

24. A data processing apparatus comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor when executing the program implements the steps of:

25. A computer-readable storage medium, characterized in that,

the computer-readable storage medium stores a computer program which, when executed by a computer, is capable of implementing the method of any one of claims 1 to 12.