CN112385296A

CN112385296A - Resource scheduling method and related equipment

Info

Publication number: CN112385296A
Application number: CN201880095411.XA
Authority: CN
Inventors: 何朗; 宁磊; 李少华; 于薇
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2018-12-29
Filing date: 2018-12-29
Publication date: 2021-02-19
Also published as: WO2020133399A1

Abstract

The embodiment of the application provides a resource scheduling method and related equipment, which are used for reducing resource waste, reducing user transmission delay and power consumption and avoiding uplink pre-scheduling empty packets. The method comprises the following steps: the network equipment sends a resource scheduling instruction to the terminal, wherein the resource scheduling instruction is used for allocating resources to target data, and the target data comprises: a Radio Link Control (RLC) status report corresponding to downlink data sent by a network device, or an RLC layer packet failed to be received by the network device, wherein the RLC status report is used for indicating a receiving status corresponding to the downlink data received by a terminal; and the network equipment receives the target data sent by the terminal on the resources allocated by the resource scheduling instruction.

Description

Resource scheduling method and related equipment

Technical Field

The embodiment of the application relates to the technical field of communication, in particular to a resource scheduling method and related equipment.

Background

Discrete narrowband communication technology is a form of communication for cellular communication systems. In the discrete narrowband communication technology, when data transmission is performed between a base station and a terminal, the terminal needs to initiate a scheduling request to the base station to obtain an uplink transmission authorization indication, and perform data transmission on a video resource allocated to the terminal by the base station according to the uplink transmission authorization indication, so as to avoid data transmission conflict with other terminals.

Generally, a scheduling request is transmitted to a base station by reserving time-frequency resources, and in the scheduling request by reserving time-frequency resources, resources required for retransmission of a Radio Link Control (RLC) layer status report (hereinafter referred to as an RLC status report) and an uplink data RLC Service Data Unit (SDU) are both reserved in advance, which causes that time-frequency resources required for transmission of the RLC status report and retransmission of the uplink data RLC SDU are always occupied, resulting in resource waste.

Disclosure of Invention

The embodiment of the application provides a resource scheduling method and related equipment, which are applicable to a discrete narrowband cellular communication system and used for pre-allocating time-frequency resources required by RLC (radio link control) status reports and uplink data RLC SDU (service data Unit) retransmission so as to reduce resource waste, reduce user transmission delay and power consumption and avoid uplink pre-scheduling empty packets (padding).

In order to achieve the technical purpose, the embodiment of the application provides the following technical scheme:

in a first aspect, an embodiment of the present application provides a resource scheduling method, including: the network equipment sends a resource scheduling instruction to the terminal, wherein the resource scheduling instruction is used for allocating resources to target data, and the target data comprises: a Radio Link Control (RLC) status report corresponding to downlink data sent by a network device, or an RLC layer packet failed to be received by the network device, wherein the RLC status report is used for indicating a receiving status corresponding to the downlink data received by a terminal; and the network equipment receives the target data sent by the terminal on the resources allocated by the resource scheduling instruction. It should be noted that the method in the embodiment of the present application is particularly suitable for an application scenario of an internet of things of a discrete narrowband cellular communication system.

It can be seen from the above technical solutions that the embodiments of the present application have the following advantages: the network equipment pre-allocates time-frequency resources for the RLC status report and the RLC layer data packet which is failed to be received by the network equipment for data transmission, so that the time-frequency resources are not occupied all the time, the resource waste is avoided, the transmission resources are saved, the transmission delay and the power consumption of a user are reduced, and the uplink pre-scheduling empty packet is avoided.

With reference to the first aspect, in a first possible resource scheduling method of the first aspect of the present application, when the target data is an RLC status report corresponding to downlink data sent by a network device, sending, by the network device, a resource scheduling instruction to a terminal may specifically include: and when the condition of requesting the RLC status report is met, the network equipment sends the resource scheduling instruction to the terminal, wherein the condition of requesting the RLC status report is specifically considered to be met when the base station RLC layer Polling flag position is '1'. As can be seen from the first possible implementation manner of the first aspect, when the RLC layer requests the status report, uplink pre-scheduling of the time-frequency resource required by the RLC status report is triggered, so that resource waste is avoided, and transmission resources are saved.

With reference to the first aspect, in a second possible resource scheduling method in the first aspect of this embodiment of the present application, when the target data is an RLC layer packet that the network device has failed to receive, after the network device sends a resource scheduling instruction to the terminal, the method further includes: the network equipment sends an RLC layer data retransmission request to the terminal, wherein the RLC layer data retransmission request is used for requesting the terminal to send an RLC layer data packet which is received by the network equipment in a failure mode. As can be seen from the second possible implementation manner of the first aspect, when the RLC layer requests uplink data RLC SDU retransmission, uplink pre-scheduling of resources required for uplink data RLC SDU retransmission is triggered, so that resource waste is avoided, and transmission resources are saved. Optionally, the RLC layer data retransmission reQuest may specifically be an automatic retransmission reQuest (ARQ) of the RLC layer.

In a second aspect, an embodiment of the present application provides a resource scheduling method, including: a terminal receives a resource scheduling instruction sent by network equipment, wherein the resource scheduling instruction is used for allocating resources to target data, and the target data comprises: a Radio Link Control (RLC) status report corresponding to downlink data sent by a network device, or an RLC layer packet failed to be received by the network device, wherein the RLC status report is used for indicating a receiving status corresponding to the downlink data received by a terminal; and the terminal sends the target data to the network equipment on the resources allocated by the resource scheduling instruction.

With reference to the second aspect, in a first possible implementation manner of the second aspect of the embodiment of the present application, when the target data is an RLC status report corresponding to downlink data sent by a network device, a terminal sends the target data to the network device on a resource allocated by a resource scheduling instruction, where the method includes: when downlink data sent by the network equipment reaches the RLC layer of the terminal, the terminal sends the RLC status report to the network equipment on the resource allocated by the resource scheduling instruction, wherein the condition for requesting the RLC status report is specifically the condition for requesting the status report by the RLC layer when the Polling flag position "1" of the RLC layer of the base station is satisfied.

With reference to the second aspect, in a second possible implementation manner of the second aspect of the embodiment of the present application, when the target data is an RLC layer packet that the network device has failed to receive, after the terminal receives a resource scheduling instruction sent by the network device, the method further includes: the terminal receives an RLC layer data retransmission request sent by network equipment, wherein the RLC layer data retransmission request is used for requesting the terminal to send an RLC layer data packet which is received by the network equipment in a failure mode. Optionally, the RLC layer data retransmission request may specifically be an automatic retransmission request (ARQ) of the RLC layer.

In a third aspect, an embodiment of the present application provides a network device, where the network device has a function of implementing the method of the first aspect or any one of the possible implementation manners of the first aspect. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a fourth aspect, an embodiment of the present application provides a terminal having a function of implementing a method according to any one of the second aspect and the second possible implementation manner. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In a fifth aspect, an embodiment of the present application provides a network device, including: a processor and a memory; the memory is configured to store computer executable instructions, and when the network device runs, the processor executes the computer executable instructions stored in the memory, so as to enable the network device to perform the resource scheduling method according to the first aspect or any one of the possible implementations of the first aspect.

In a sixth aspect, an embodiment of the present application provides a terminal, including: a processor and a memory; the memory is configured to store computer executable instructions, and when the terminal runs, the processor executes the computer executable instructions stored in the memory, so as to enable the terminal to execute the resource scheduling method according to the second aspect or any one of the possible implementation manners of the second aspect.

In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the instructions are executed on a computer, the computer may execute the method for scheduling resources according to the first aspect or any one of the possible implementations of the first aspect.

In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the instructions are executed on a computer, the computer may execute the resource scheduling method of any one of the second aspect and the second possible implementation manner.

In a ninth aspect, embodiments of the present application provide a computer program product, which when run on a computer, enables the computer to execute the resource scheduling method of the first aspect or any one of the possible implementations of the first aspect.

In a tenth aspect, embodiments of the present application provide a computer program product, which when run on a computer, enables the computer to execute the resource scheduling method of the second aspect or any one of the possible implementations of the second aspect.

In an eleventh aspect, an embodiment of the present application provides a chip system, where the chip system includes a processor, configured to support a network element that performs a function to implement the function in the first aspect or any one of the possible implementations of the first aspect. In one possible design, the system-on-chip further includes a memory for storing program instructions and data necessary to execute the functional network elements. The chip system may be constituted by a chip, or may include a chip and other discrete devices.

In a twelfth aspect, an embodiment of the present application provides a chip system, where the chip system includes a processor, configured to support a control function network element to implement the functions in the second aspect or any possible implementation manner of the second aspect. In one possible design, the system-on-chip further includes a memory for storing program instructions and data necessary to control the functional network elements. The chip system may be constituted by a chip, or may include a chip and other discrete devices.

It should be noted that beneficial effects corresponding to any one of the implementation manners of the second aspect to the twelfth aspect may refer to beneficial effects corresponding to the related implementation manner of the first aspect, and are not described herein again.

Drawings

Fig. 1 is a schematic diagram of a communication system according to an embodiment of the present application;

fig. 2 is a schematic diagram of an embodiment of a resource scheduling method provided in an embodiment of the present application;

fig. 3 is a schematic diagram of another embodiment of a resource scheduling method provided in an embodiment of the present application;

fig. 4 is a schematic diagram of an embodiment of a communication device in the embodiment of the present application;

FIG. 5 is a diagram of an embodiment of a network device in an embodiment of the present application;

fig. 6 is a schematic diagram of an embodiment of a terminal in the embodiment of the present application.

Detailed Description

Embodiments of the present application will now be described with reference to the accompanying drawings, and it is to be understood that the described embodiments are merely illustrative of some, but not all, embodiments of the present application. As can be known to those skilled in the art, with the development of technology and the emergence of new scenarios, the technical solution provided in the embodiments of the present application is also applicable to similar technical problems.

The embodiment of the application provides a resource scheduling method and related equipment, which are applicable to a discrete narrowband cellular communication system and used for pre-allocating time-frequency resources required by RLC (radio link control) status reports and uplink data RLC SDU (service data Unit) retransmission so as to reduce resource waste, reduce user transmission delay and power consumption and avoid uplink pre-scheduling empty packets (padding). The embodiments of the present application will be described in detail below.

The term "and/or" appearing in the present application may be an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" in this application generally indicates that the former and latter related objects are in an "or" relationship.

The terms "first," "second," and the like in the description and in the claims of the present application and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein. Moreover, the terms "comprises," "comprising," and any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or modules is not necessarily limited to those steps or modules explicitly listed, but may include other steps or modules not expressly listed or inherent to such process, method, article, or apparatus. The naming or numbering of the steps appearing in the present application does not mean that the steps in the method flow have to be executed in the chronological/logical order indicated by the naming or numbering, and the named or numbered process steps may be executed in a modified order depending on the technical purpose to be achieved, as long as the same or similar technical effects are achieved. The division of the modules presented in this application is a logical division, and in practical applications, there may be another division, for example, multiple modules may be combined or integrated into another system, or some features may be omitted, or not executed, and in addition, the shown or discussed coupling or direct coupling or communication connection between each other may be through some interfaces, and the indirect coupling or communication connection between the modules may be in an electrical or other similar form, which is not limited in this application. The modules or sub-modules described as separate components may or may not be physically separated, may or may not be physical modules, or may be distributed in a plurality of circuit modules, and some or all of the modules may be selected according to actual needs to achieve the purpose of the present disclosure.

The present application describes various embodiments in conjunction with a terminal, which may be referred to as a User Equipment (UE), a Mobile Station (MS), a mobile terminal (mobile terminal) and the like, and the terminal may communicate with one or more core networks through a Radio Access Network (RAN). For example, the terminal equipment may be a mobile phone (or so-called "cellular" phone), a computer with a mobile terminal, etc., and the terminal equipment may also be a portable, pocket, hand-held, computer-included or vehicle-mounted mobile device and terminal equipment in future 5G networks, which exchange voice or data with the radio access network. Description of terminal device: in this application, the terminal device may further include a Relay, and the terminal device and the base station that can perform data communication may be regarded as the terminal device.

In addition, various embodiments are described herein in connection with a network device. The network device may be an evolved Node B (evolved Node B, which may be referred to as eNB or e-NodeB for short) macro base station, a micro base station (also referred to as a "small base station"), a pico base station, an Access Point (AP) or a Transmission Point (TP), or a NodeB (new generation base station) in a Long Term Evolution (LTE) system or an authorized assisted access long-term evolution (LAA-LTE) system.

In a discrete narrowband cellular communication system, an RLC layer Acknowledged Mode (AM) is typically employed to ensure that RLC layer data packets are successfully transmitted. Specifically, in the downlink transmission process, the base station sends downlink data to the terminal, when the downlink data reaches the RLC layer of the terminal, the terminal needs to reply an RLC layer status report to the base station, and the base station continues to transmit the downlink data after receiving the RLC layer status report sent by the terminal; in the uplink transmission process, a terminal sends uplink data to a base station, if the base station receives the data and then analyzes the data incorrectly, the base station initiates a hybrid automatic repeat request (HARQ) of Medium Access Control (MAC) for retransmission, if the data is still not transmitted correctly, the base station initiates an automatic repeat request (ARQ) of an RLC layer for retransmission, at this time, the terminal transmits an RLC Service Data Unit (SDU) to the base station, and if the data is transmitted correctly, the terminal continues to transmit other uplink data.

Fig. 1 is a schematic diagram of a communication system according to an embodiment of the present application.

As shown in fig. 1, the communication system in the embodiment of the present application includes: a network device 101 and a terminal 102; wherein the network device 101 is configured to: sending a resource scheduling instruction to the terminal 102, where the resource scheduling instruction is used to allocate resources to target data, and the target data includes: a Radio Link Control (RLC) status report corresponding to downlink data sent by a network device, or an RLC layer packet failed to be received by the network device, wherein the RLC status report is used for indicating a receiving status corresponding to the downlink data received by a terminal; the terminal 102 is configured to: after receiving the resource scheduling instruction sent by the network device 101, the target data is sent to the network device 101 on the resource indicated by the resource scheduling instruction.

Optionally, in an example, when the target data is an RLC status report corresponding to downlink data sent by the network device, the network device 101 is specifically configured to: and when a condition for requesting the RLC status report is met, sending the resource scheduling instruction to the terminal 102, where the condition for requesting the RLC status report is specifically considered to be met when the base station RLC layer Polling flag position is "1".

Optionally, in an example, when the target data is an RLC layer packet that the network device has failed to receive, the network device is further configured to: sending an RLC layer data retransmission request to a terminal 102, where the RLC layer data retransmission request is used to request the terminal to send an RLC layer data packet that the network device failed to receive; the terminal 102 is further configured to: an RLC layer data retransmission request sent by network device 101 is received.

As can be seen from the communication system shown in fig. 1, in the embodiment of the present application, mainly for pre-allocation of time-frequency resources required by a downlink transmission medium RLC status report and pre-allocation of time-frequency resources required by uplink data RLC SDU retransmission in an uplink transmission process, the following network device takes the base station as an example to respectively describe the resource scheduling method in the embodiment of the present application in detail based on the two types of uplink pre-scheduling manners.

Uplink pre-scheduling of time-frequency resources required by RLC (radio link control) status report in downlink transmission process

Fig. 2 is a schematic diagram of an embodiment of a resource scheduling method according to an embodiment of the present application.

As shown in fig. 2, an embodiment of a resource scheduling method in the embodiment of the present application includes:

201. and when the requirement of the base station RLC layer on the RLC status report is met, the base station sends a resource scheduling instruction to the terminal, wherein the resource scheduling instruction is used for allocating resources for the RLC status report.

When downlink data reaches the RLC layer of the terminal in the process of sending the downlink data to the terminal by the base station, the terminal needs to send an RLC status report to the base station, where the RLC status report is used to indicate a receiving status corresponding to the downlink data received by the terminal, for example, the RLC status report may indicate a sequence number of a data packet that the terminal has not received. However, when the Polling flag position of the base station RLC layer is "1", the condition that the base station RLC layer is triggered to request the RLC status report is satisfied, and at this time, the base station sends a resource scheduling instruction to the terminal to allocate time-frequency resources required for transmitting the RLC status report. In the prior art, time-frequency resources required by a terminal for transmitting an RLC status report are pre-reserved by a base station, downlink data sent by the base station reaches an RLC layer of the terminal, and the terminal reports the RLC status report to the base station by using the reserved time-frequency resources. Therefore, compared with the existing mode of reserving time-frequency resources, the pre-scheduling of the time-frequency resources required by the RLC status report triggered by the base station RLC layer in the embodiment of the application can effectively save the time-frequency resources.

Optionally, the resource scheduling instruction may be an Uplink (UL) grant instruction, and specifically, the base station sends the UL grant instruction to the terminal through a Physical Downlink Control Channel (PDCCH), where the UL grant instruction is used to indicate a time-frequency resource for transmitting an RLC status report.

202. When the downlink data sent by the base station reaches the RLC layer of the terminal, the terminal sends an RLC status report to the base station on the resources allocated by the resource scheduling instruction.

When the downlink data sent by the base station reaches the RLC layer of the terminal, the terminal generates an RLC status report according to the receiving status corresponding to the downlink data, and finally, the terminal reports the RLC status report to the base station on the time-frequency resource for transmitting the RLC status report allocated by the resource scheduling instruction.

Optionally, when the resource scheduling instruction is a UL grant instruction, the terminal sends the RLC status report to the base station on a Physical Uplink Shared Channel (PUSCH) according to the time-frequency resource indicated by the UL grant instruction.

In the embodiment of the application, the base station is triggered to distribute and transmit the RLC status report by the base station RLC layer status report, the uplink resources can be reduced, the extra resource overhead in the downlink transmission process can be reduced, the time delay is reduced, the network equipment distributes the time-frequency resources corresponding to the RLC layer status report to the terminal only when needed, namely when the RLC layer requests the status report, and the uplink pre-scheduling empty packet can be effectively avoided.

Second, uplink pre-scheduling of time frequency resources needed by uplink data RLC SDU in uplink transmission process

Fig. 3 is a schematic diagram of another embodiment of a resource scheduling method according to an embodiment of the present application.

As shown in fig. 3, another embodiment of the resource scheduling method in the embodiment of the present application includes:

301. when the RLC layer data packet of the base station fails to be received, the base station sends a resource scheduling instruction to the terminal, and the resource scheduling instruction is used for allocating resources to the RLC layer data packet which fails to be received by the base station.

In the process that the terminal sends uplink data to the base station, the RLC layer packet of the base station fails to be received, which means that one or more error packets exist in the RLC layer packet of the base station.

Optionally, the resource scheduling instruction may be a UL grant instruction, and specifically, the base station sends the UL grant instruction to the terminal through a PDCCH channel, where the UL grant instruction is used to indicate a time-frequency resource of an RLC layer packet that is received by the base station in uplink data transmission.

302. And the base station sends an RLC layer data retransmission request to the terminal.

The RLC layer data retransmission request is used for requesting the terminal to send a reported RLC layer data packet which is received by the base station in a failure mode, and optionally, the RLC layer data retransmission request carries a sequence number corresponding to the RLC layer data packet which is received by the base station in a failure mode.

Optionally, the RLC layer data retransmission request may specifically be an automatic retransmission request (ARQ) of the RLC layer, where the request carries a sequence number corresponding to an RLC layer data packet that has failed to be received by the base station.

It should be noted that, in uplink data transmission, if the base station receives data and then analyzes the data incorrectly, the base station may initiate hybrid automatic retransmission of a Media Access Control (MAC) layer, and if the RLC layer of the base station still does not receive a correct data packet, the base station may initiate automatic retransmission of the RLC layer.

303. And the terminal sends the RLC layer data packet which is received unsuccessfully by the base station to the base station on the resource allocated by the resource scheduling instruction.

After the terminal receives the RLC layer data retransmission request sent by the base station, the terminal acquires the information of the RLC layer data packet which is received by the base station in failure according to the RLC layer data retransmission request. Optionally, the terminal analyzes the RLC layer data retransmission request to obtain a sequence number carried in the request, and further, the terminal determines the RLC layer data packet which is received by the base station in failure according to the obtained sequence number.

Optionally, when the RLC layer data retransmission request is an automatic retransmission request of the RLC layer, the terminal performs automatic retransmission of the RLC layer on the resource allocated by the resource scheduling instruction, so as to report the RLC SDU corresponding to the RLC layer data packet which is received by the base station in failure to the base station.

Optionally, when the resource scheduling instruction is a UL grant instruction, the terminal sends, to the base station, the RLC SDU corresponding to the RLC layer packet which is received by the base station in failure on the PUSCH according to the time-frequency resource indicated by the UL grant instruction.

In the embodiment of the application, the base station is triggered by the base station RLC layer requesting data retransmission to allocate uplink resources required by the RLC layer data packet which is failed to be received by the transmission base station, so that extra resource overhead in the uplink transmission process can be reduced, time delay is reduced, and only when the uplink resources are needed, namely when the RLC layer requests data retransmission, the network equipment allocates time-frequency resources corresponding to the RLC layer data packet to be retransmitted to the terminal, so that an uplink pre-scheduling empty packet can be effectively avoided.

The above-mentioned scheme provided by the embodiment of the present application is introduced mainly from the perspective of interaction between a network device and a terminal. It is understood that the terminal and the network device include hardware structures and/or software modules for performing the respective functions in order to realize the functions. Those of skill in the art will readily appreciate that the various illustrative modules and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

Described in terms of hardware structures, a network device or a terminal may be implemented by one entity device, may also be implemented by multiple entity devices together, and may also be a logic function module in one entity device, which is not specifically limited in this embodiment of the present application.

For example, the network device or the terminal in the embodiment of the present application may be implemented by the communication device in fig. 4. Fig. 4 is a schematic hardware structure diagram of a communication device in the embodiment of the present application.

As shown in fig. 4, the communication device 400 includes at least one processor 401, communication circuitry 402, memory 403, and at least one communication interface 404.

The processor 401 may be a general processing unit (CPU), a microprocessor, an application-specific integrated circuit (server IC), or one or more ICs for controlling the execution of programs in accordance with the present invention.

The communication link 402 may include a path for communicating information between the aforementioned components.

The communication interface 404 may be any device, such as a transceiver, for communicating with other devices or communication networks, such as an ethernet, a Radio Access Network (RAN), a Wireless Local Area Network (WLAN), etc.

The memory 403 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disk read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to these. The memory may be separate and coupled to the processor via a communication line 402. The memory may also be integral to the processor.

The memory 403 is used for storing computer-executable instructions for executing the present invention, and is controlled by the processor 401. The processor 401 is configured to execute the computer-executable instructions stored in the memory 403, so as to implement the resource scheduling method provided by the foregoing embodiments of the present application.

Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.

In particular implementations, processor 401 may include one or more CPUs such as CPU0 and CPU1 in fig. 4 as an example.

In particular implementations, communication device 400 may include multiple processors, such as processor 401 and processor 408 in fig. 4, for example, as an embodiment. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

In particular implementations, communication device 400 may also include an output device 405 and an input device 406, as one embodiment. An output device 405 is in communication with the processor 401 and may display information in a variety of ways. For example, the output device 405 may be a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display device, a Cathode Ray Tube (CRT) display device, a projector (projector), or the like. The input device 406 is in communication with the processor 401 and may receive user input in a variety of ways. For example, the input device 406 may be a mouse, a keyboard, a touch screen device, or a sensing device, among others.

The communication device 400 described above may be a general purpose device or a special purpose device. In a specific implementation, the communication device 400 may be a desktop, a laptop, a web server, a Personal Digital Assistant (PDA), a mobile phone, a tablet, a wireless terminal, an embedded device, or a device with a similar structure as in fig. 4. The embodiment of the present application does not limit the type of the communication apparatus 400.

In the embodiment of the present application, the network device and the terminal may be divided into the functional modules according to the above method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation.

For example, in the case of dividing each functional module in an integrated manner, fig. 5 shows a schematic structural diagram of a network device;

as shown in fig. 5, the network device 50 includes a transmitting module 501 and a receiving module 502;

a sending module 501, configured to send a resource scheduling instruction to a terminal, where the resource scheduling instruction is used to allocate resources to target data, where the target data includes: a Radio Link Control (RLC) status report corresponding to downlink data sent by the network device, or an RLC packet data packet failed to be received by the network device, wherein the RLC status report is used for indicating a receiving status corresponding to the downlink data received by the terminal;

a receiving module 502, configured to receive the target data sent by the terminal on the resource allocated by the resource scheduling instruction.

Optionally, in an implementation manner, when the target data is a radio link control RLC status report corresponding to downlink data sent by the network device, the sending module 501 is specifically configured to: and when the condition of requesting the RLC status report is met, sending the resource scheduling instruction to the terminal.

Optionally, in an implementation manner, when the target data is an RLC layer packet that is received by the network device in a failure mode, the sending module 501 is further configured to: and sending an RLC layer data retransmission request to the terminal, wherein the RLC layer data retransmission request is used for requesting the terminal to send an RLC layer data packet which is received by the network equipment in a failure mode.

Similarly, in the case of dividing each functional module in an integrated manner, fig. 6 shows a schematic structural diagram of a terminal;

as shown in fig. 6, the terminal 60 includes a receiving module 601 and a transmitting module 602;

a receiving module 601, configured to receive a resource scheduling instruction sent by a network device, where the resource scheduling instruction is used to allocate resources to target data, and the target data includes: a Radio Link Control (RLC) status report corresponding to downlink data sent by the network device, or an RLC packet data packet failed to be received by the network device, wherein the RLC status report is used for indicating a receiving status corresponding to the downlink data received by the terminal;

a sending module 602, configured to send the target data to the network device on the resource allocated by the resource scheduling instruction.

Optionally, in an implementation manner, when the target data is a radio link control RLC status report corresponding to downlink data sent by the network device, the sending module 602 is specifically configured to: and when the downlink data sent by the network equipment reaches the RLC layer of the terminal, sending the RLC status report to the network equipment on the resources allocated by the resource scheduling instruction.

Optionally, in an implementation manner, when the target data is an RLC layer packet that is received by the network device in failure, the receiving module 601 is further configured to: and receiving an RLC layer data retransmission request sent by the network equipment, wherein the RLC layer data retransmission request is used for requesting the terminal to send an RLC layer data packet which is received by the network equipment in a failure mode.

All relevant contents of each step related to the above method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.

In the present embodiment, the network device and the terminal are presented in a form in which the respective functional modules are divided in an integrated manner. A "module" as used herein may refer to an application-specific integrated circuit (ASIC), an electronic circuit, a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other devices that provide the described functionality. In a simple embodiment, those skilled in the art will appreciate that the network device and the terminal may take the form shown in fig. 4.

For example, the processor 401 in fig. 4 may cause the network device or the terminal to execute the resource scheduling method in the foregoing method embodiment by calling a computer stored in the memory 403 to execute the instructions.

In particular, the functions/implementation processes of the sending module 501 and the receiving module 502 in fig. 5, and the receiving module 601 and the sending module 602 in fig. 6 may be implemented by the processor 401 in fig. 4 calling a computer executing instruction stored in the memory 403. Alternatively, the functions/implementation processes of the sending module 501 and the receiving module 502 in fig. 5, and the receiving module 601 and the sending module 602 in fig. 6 may be implemented by the communication interface 404 in fig. 4.

Since the network device and the terminal provided in the embodiment of the present application may be configured to execute the resource scheduling method, reference may be made to the method embodiment for obtaining technical effects, and details are not described herein again.

In the above embodiment, the network device and the terminal are presented in a form of dividing each functional module in an integrated manner. Of course, in the embodiment of the present application, each function module of the network device and the terminal may also be divided corresponding to each function, and this is not particularly limited in the embodiment of the present application.

Optionally, an embodiment of the present application provides a chip system, where the chip system includes a processor, and is configured to support a user plane functional entity to implement the resource scheduling method. In one possible design, the system-on-chip further includes a memory. The memory is used for storing program instructions and data necessary for the network equipment or the terminal. The chip system may be formed by a chip, and may also include a chip and other discrete devices, which is not specifically limited in this embodiment of the present application.

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 includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, 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.). The computer-readable storage medium can be any available medium that a computer can store or a data storage device, such as a server, a data center, etc., that is integrated with one or more 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.

Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by associated hardware instructed by a program, which may be stored in a computer-readable storage medium, and the storage medium may include: ROM, RAM, magnetic or optical disks, and the like.

The resource scheduling method and the related device provided by the embodiment of the present application are introduced in detail above, and a specific example is applied in the description to explain the principle and the embodiment of the present application, and the description of the above embodiment is only used to help understanding the method and the core idea of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims

A method for scheduling resources, comprising:

the network equipment sends a resource scheduling instruction to a terminal, wherein the resource scheduling instruction is used for allocating resources to target data, and the target data comprises: a Radio Link Control (RLC) status report corresponding to downlink data sent by the network device, or an RLC packet data packet failed to be received by the network device, wherein the RLC status report is used for indicating a receiving status corresponding to the downlink data received by the terminal;

and the network equipment receives the target data sent by the terminal on the resources allocated by the resource scheduling instruction.
The method according to claim 1, wherein when the target data is a radio link control RLC status report corresponding to downlink data sent by the network device, the network device sends a resource scheduling instruction to a terminal, and the method comprises:

and when the condition of requesting the RLC status report is met, the network equipment sends the resource scheduling instruction to the terminal.
The method according to claim 1, wherein when the target data is an RLC layer packet which has failed to be received by the network device, after the network device sends a resource scheduling instruction to a terminal, the method further comprises:

and the network equipment sends an RLC layer data retransmission request to the terminal, wherein the RLC layer data retransmission request is used for requesting the terminal to send an RLC layer data packet which is received by the network equipment in a failure mode.
A method for scheduling resources, comprising:

a terminal receives a resource scheduling instruction sent by network equipment, wherein the resource scheduling instruction is used for allocating resources to target data, and the target data comprises: a Radio Link Control (RLC) status report corresponding to downlink data sent by the network device, or an RLC packet data packet failed to be received by the network device, wherein the RLC status report is used for indicating a receiving status corresponding to the downlink data received by the terminal;

and the terminal sends the target data to the network equipment on the resources allocated by the resource scheduling instruction.
The method according to claim 4, wherein when the target data is a Radio Link Control (RLC) status report corresponding to downlink data sent by the network device, the terminal sends the target data to the network device on the resource allocated by the resource scheduling instruction, and the method comprises:

and when the downlink data sent by the network equipment reaches the RLC layer of the terminal, the terminal sends the RLC status report to the network equipment on the resources allocated by the resource scheduling instruction.
The method according to claim 4, wherein when the target data is an RLC layer packet which has failed to be received by the network device, after the terminal receives a resource scheduling instruction sent by the network device, the method further comprises:

and the terminal receives an RLC layer data retransmission request sent by the network equipment, wherein the RLC layer data retransmission request is used for requesting the terminal to send an RLC layer data packet which is received by the network equipment in a failure mode.
A network device, comprising:

a sending module, configured to send a resource scheduling instruction to a terminal, where the resource scheduling instruction is used to allocate resources to target data, and the target data includes: a Radio Link Control (RLC) status report corresponding to downlink data sent by the network device, or an RLC packet data packet failed to be received by the network device, wherein the RLC status report is used for indicating a receiving status corresponding to the downlink data received by the terminal;

a receiving module: the target data is sent by the terminal and is received on the resources allocated by the resource scheduling instruction.
The network device according to claim 7, wherein when the target data is a radio link control RLC status report corresponding to downlink data sent by the network device, the sending module is specifically configured to: and when the condition of requesting the RLC status report is met, sending the resource scheduling instruction to the terminal.
The network device of claim 7, wherein when the target data is an RLC layer packet that the network device has failed to receive, the sending module is further configured to: and sending an RLC layer data retransmission request to the terminal, wherein the RLC layer data retransmission request is used for requesting the terminal to send an RLC layer data packet which is received by the network equipment in a failure mode.
A terminal, comprising:

a receiving module, configured to receive a resource scheduling instruction sent by a network device, where the resource scheduling instruction is used to allocate resources to target data, and the target data includes: a Radio Link Control (RLC) status report corresponding to downlink data sent by the network device, or an RLC packet data packet failed to be received by the network device, wherein the RLC status report is used for indicating a receiving status corresponding to the downlink data received by the terminal;

and the sending module is used for sending the target data to the network equipment on the resources allocated by the resource scheduling instruction.
The terminal according to claim 10, wherein when the target data is a radio link control RLC status report corresponding to downlink data sent by the network device, the sending module is specifically configured to: and when the downlink data sent by the network equipment reaches the RLC layer of the terminal, sending the RLC status report to the network equipment on the resources allocated by the resource scheduling instruction.
The terminal of claim 10, wherein when the target data is an RLC layer packet that has failed to be received by the network device, the receiving module is further configured to: and receiving an RLC layer data retransmission request sent by the network equipment, wherein the RLC layer data retransmission request is used for requesting the terminal to send an RLC layer data packet which is received by the network equipment in a failure mode.
A network device, comprising:

a processing unit and a storage unit;

the storage unit is used for storing computer operation instructions;

the processing unit is configured to execute the resource scheduling method according to any one of the preceding claims 1 to 3 by calling the computer operation instruction.
A terminal, comprising:

a processing unit and a storage unit;

the storage unit is used for storing computer operation instructions;

the processing unit is configured to execute the resource scheduling method according to any one of the preceding claims 4 to 6 by calling the computer operation instruction.
A computer-readable storage medium having stored therein computer-operational instructions, which when run on a computer, cause the computer to perform the method of resource scheduling of any of claims 1 to 6.