WO2018000362A1 - Resource scheduling method and corresponding device - Google Patents

Abstract

A resource scheduling method and a corresponding device, used for enhancing the uplink scheduling capability of a network side device. The method comprises the following content: the network side device acquires information of at least one terminal to be scheduled; the network side device determines the resource amount available for sending an uplink grant UL grant to at least two non-uplink sub-frames preceding a first uplink sub-frame; the network side device, on the basis of information of the at least one terminal to be scheduled and the resource amount available to the at least two non-uplink sub-frames for sending the UL grant, determines M terminals amongst the at least one terminal that can be scheduled over tha first uplink sub-frame, M being no less than 1; the network side device sends M UL grants over the at least two non-uplink sub-frames, each UL grant amongst the M UL grants being used for scheduling one terminal amongst the M terminals.

Description

Resource scheduling method and corresponding device Technical field

The present invention relates to the field of communications technologies, and in particular, to a resource scheduling method and a corresponding device.

Background technique

In the time division duplexing (TDD) system, uplink (English: uplink, UL) and downlink (English: downlink, DL) are separated in time, and data is received and transmitted in the same frequency band. Completed at different times. Long term evolution (LTE) TDD system can support 7 different TDD uplink and downlink configurations. In each configuration, which subframe is the uplink subframe and which is the 10 subframes of a radio frame. The subframe is a downlink subframe and which subframe is a special subframe.

The terminal sends the uplink data to the network side device by using the physical uplink shared channel (PUSCH) in the uplink subframe. The PUSCH resource used by the terminal is a non-uplink of the network side device before the uplink subframe. The uplink grant (English: UL grant) sent in the frame (downlink subframe or special subframe) is allocated.

The UL grant has a fixed timing relationship with the scheduled PUSCH. The timing relationship indicates that the downlink subframe of the current uplink subframe is scheduled by the UL grant on the downlink subframe or the special subframe. In other words, for the uplink subframe, the subframe number of the non-uplink subframe in which the UL grant for allocating the PUSCH resources of the uplink subframe is transmitted, and the subframe number of the uplink subframe is in one-to-one correspondence. For example, in the uplink and downlink subframe configuration 2 of the TDD-LTE, the PUSCH resources of the 7th uplink subframe in each radio frame are all scheduled by the UL grant sent in the downlink subframe 3 of the same radio frame. The PUSCH resource of the second uplink subframe in each radio frame is the UL grant schedule sent by the eighth downlink subframe of the previous radio frame.

The network side device sends a UL grant to the terminal by using a physical downlink control channel (PDCCH) or an enhanced physical downlink control channel (English: enhanced PDCCH, EPDCCH) of the downlink subframe or the special subframe. However, a downlink subframe or Only a part of the downlink transmission resources of the special subframe is allocated to the PDCCH or the EPDCCH, and the allocated resources of the PDCCH or the EPDCCH are used for transmitting the downlink scheduling information (English: DL assignment) and mixing, in addition to the UL grant. Information such as the automatic repeat request (HARQ), which results in less resources available for transmitting the UL grant in the PDCCH or EPDCCH resources of one downlink subframe or special subframe, and the uplink scheduling capability of the network side device Insufficient to meet the communication needs of current multi-user large business volume.

Summary of the invention

The present application provides a resource scheduling method and a corresponding device, which are used to enhance uplink scheduling capability of a network side device.

In a first aspect, the embodiment of the present application provides a resource scheduling method. First, the network side device obtains information of at least one terminal to be scheduled, and the information of the at least one terminal includes an identifier of the at least one terminal to be scheduled, except The information of the at least one terminal may further include information such as an uplink channel quality of the at least one terminal to be scheduled, a size of the uplink data to be sent by the at least one terminal to be scheduled, and the like. The network side device further determines a quantity of resources that can be used to send an uplink grant (English: UL grant) for at least two non-uplink subframes before the first uplink subframe. Then, the network side device determines, according to the information of the at least one terminal to be scheduled and the quantity of resources of the at least two non-uplink subframes that can be used to send the UL grant, that the schedule is configurable on the first uplink subframe. M terminals of at least one terminal, M is not less than 1; then, the network side device sends M UL grants in the at least two non-uplink subframes, and each UL grant of the M UL grants is used for scheduling One of the M terminals.

The network side device can send M UL grants by using at least two non-uplink subframes before the first uplink subframe, and allocate the physical uplink shared channel in the first uplink subframe to the M terminals (English: physical uplink) Shared channel, PUSCH) resources. Compared with the technical solution of scheduling the terminal in the first uplink subframe by using only one non-uplink subframe in the prior art, the number of terminals that can be scheduled in the first uplink subframe can be significantly increased, and the network side device is improved. Uplink scheduling capability.

In an optional implementation, the network side device sends at least one UL grant of the M UL grants in each of the at least two non-uplink subframes. In this optional implementation, the network side device can fully utilize the resources of each of the at least two non-uplink subframes that can be used to send the UL grant, and send the first to each of the at least two non-uplink subframes. The PUSCH resource in the uplink subframe performs the allocated resource of the UL grant, so that more terminals in the first uplink subframe can be scheduled.

In an optional implementation, the first UL grant for scheduling the first terminal in the M UL grants is divided into N parts, where N is greater than 1 and not greater than the at least two non-uplink subframes. Sending, by the network side device, the N parts of the first UL grant by using N subframes in the at least two non-uplink subframes, where the network side device is in the N subframes Transmitting one of the N portions in each of the subframes, wherein a portion of the N portions transmitted in any two of the N subframes is different; the N of the first UL grants The partial combination is used by the first terminal to determine a physical uplink shared channel PUSCH resource that is allocated by itself on the first uplink subframe. In this optional implementation manner, the network side device can fully utilize the resources of the non-uplink subframe that are insufficient to send the complete UL grant, and send a part of the UL grant resource to improve the non-uplink subframe for sending the UL grant resource. The utilization rate increases the number of schedulable terminals in the first uplink subframe and improves the uplink scheduling capability of the network side device.

In an optional implementation, when the uplink and downlink subframes of the radio frame are configured as the configuration 2 time division duplex TDD system, when the first uplink subframe is the uplink subframe 7 of the first radio frame, The at least two non-uplink subframes include: a downlink subframe 0 of the first radio frame, a special subframe 1 of the first radio frame, and a downlink subframe 3 of the first radio frame, The downlink subframe 4 of the first radio frame, the downlink subframe 5 of the first radio frame, the special subframe 6 of the first radio frame, and the previous frame of the first radio frame At least two of the downlink subframe No. 8 and the downlink subframe 9 of the previous frame of the first radio frame.

In an optional implementation, in a TDD system in which the uplink and downlink subframes of the radio frame are configured as configuration 2, when the first uplink subframe is the uplink subframe 2 of the first radio frame, the at least The two non-uplink subframes include: a downlink subframe No. 0 of the first radio frame, and a first radio frame of the first radio frame a sub-frame, a downlink sub-frame of the previous frame of the first radio frame, a downlink sub-frame of the previous frame of the first radio frame, and a previous frame of the first radio frame. No. downlink subframe, No. 6 special subframe of the previous frame of the first radio frame, No. 8 downlink subframe of the previous frame of the first radio frame, and a previous frame of the first radio frame At least two of the downlink subframes on the 9th.

In a second aspect, the embodiment of the present application provides a resource scheduling method. First, the terminal detects a UL grant sent by the network side device in at least two non-uplink subframes before the first uplink subframe, where the UL grant is used. And scheduling, by the terminal, the PUSCH resource of the first uplink subframe. After the terminal sends an uplink scheduling request (English: Scheduling Request, SR) to the network side device, the terminal may perform the step of detecting the UL grant sent by the network side device in the at least two non-uplink subframes before the first uplink subframe. The terminal may also perform detection on the at least two non-uplink subframes corresponding to the first uplink subframe after receiving the pre-scheduling information of the network side device, and after learning that the PUSCH resource in the first uplink subframe is allocated. The steps of the UL grant. After detecting the UL grant in any subframe of the at least two non-uplink subframes, the terminal determines, according to the UL grant, the PUSCH resource that is allocated by itself in the first uplink subframe. The terminal can detect the UL grant sent to itself on the at least two non-uplink subframes, so that the network side device can send M devices for scheduling M terminals by using at least two non-uplink subframes before the first uplink subframe. The UL grant is used to allocate the PUSCH resources on the first uplink subframe to the M terminals. Compared with the technical solution of scheduling the terminal in the first uplink subframe by using only one non-uplink subframe in the prior art, the number of terminals that can be scheduled in the first uplink subframe can be significantly increased, and the network side device is improved. The uplink scheduling capability also increases the likelihood that the terminal will be allocated resources on the first uplink subframe.

In an optional implementation manner, the terminal detects the UL grant in the at least two non-uplink subframes one by one according to a chronological order, and is in any one of the at least two non-uplink subframes. The detection is stopped after the UL grant is detected. In the above optional implementation manner, the network side device may preferentially send the UL grant for scheduling the terminal in the preceding subframe of the at least two non-uplink subframes; correspondingly, the terminal preferentially has at least two non-uplinks. The UL grant is detected in the previous subframe in the frame. In this way, the terminal can obtain the UL grant as early as possible, obtain the longest possible time for determining the uplink resource allocated according to the UL grant, and prepare the uplink data to be sent to ensure the uplink. The data was sent smoothly.

In an optional implementation manner, the UL grant is divided into N parts, where N is greater than 1 and not greater than the number of the at least two non-uplink subframes; and the terminal is in the at least two non-uplink subframes. The N parts are detected in the frame, and the combination of the N parts is used as the UL grant after detecting the N parts. Since the terminal can separately detect each part of the UL grant sent to itself, and combine all the received parts to form a UL grant to determine the PUSCH resource allocated by itself on the first uplink subframe, so that the network side device can fully utilize the The resources of the at least two non-uplink subframes before an uplink subframe can be used to transmit the UL grant, so that the network side device can schedule more terminals.

In an optional implementation, in a TDD system in which the uplink and downlink subframes of the radio frame are configured as configuration 2, when the first uplink subframe is the uplink subframe 7 of the first radio frame, the at least The two non-uplink subframes include: a downlink subframe 0 of the first radio frame, a special subframe 1 of the first radio frame, a downlink subframe 3 of the first radio frame, and the a downlink subframe 4 of a radio frame, a downlink subframe 5 of the first radio frame, a special subframe 6 of the first radio frame, and a downlink of the previous frame of the first radio frame a subframe, at least two of the downlink subframes of the previous frame of the first radio frame.

In an optional implementation, in a TDD system in which the uplink and downlink subframes of the radio frame are configured as configuration 2, when the first uplink subframe is the uplink subframe 2 of the first radio frame, the at least The two non-uplink subframes include: a downlink subframe 0 of the first radio frame, a special subframe 1 of the first radio frame, and a downlink subframe 3 of a previous frame of the first radio frame. And a downlink subframe of the previous frame of the first radio frame, a downlink subframe of the previous frame of the first radio frame, and a special subframe of the previous frame of the first radio frame. At least two of a frame, a downlink subframe 8 of a previous frame of the first radio frame, and a downlink subframe 9 of a previous frame of the first radio frame.

In some optional implementations, in the TDD system in which the uplink and downlink subframes of the radio frame are configured as configuration 2, when the first uplink subframe is the uplink subframe 2 of the first radio frame, the at least two The non-uplink subframe is the downlink subframe 8 of the previous frame of the first radio frame and the downlink subframe 9 of the previous frame of the first radio frame; and/or, in the first uplink The subframe is 7 of the first radio frame The at least two non-uplink subframes are the downlink subframe 3 of the first radio frame and the downlink subframe 4 of the first radio frame. Among them, A and / or B, including A, B, A and B.

In some optional implementations, in the TDD system in which the uplink and downlink subframes of the radio frame are configured as configuration 2, when the first uplink subframe is the uplink subframe 2 of the first radio frame, the at least two The non-uplink subframe is the downlink subframe 8 of the previous frame of the first radio frame, the downlink subframe 9 of the previous frame of the first radio frame, and the downlink of the first radio frame. And when the first uplink subframe is the uplink subframe 7 of the first radio frame, the at least two non-uplink subframes are the downlink of the first radio frame. a subframe, a downlink subframe 4 of the first radio frame, and a downlink subframe 5 of the first radio frame.

In a third aspect, the embodiment of the present application provides a network side device, where the network side device includes a transmitter, a processor, and a receiver, and performs the foregoing first aspect or the first aspect by using the foregoing transmitter, the processor, and the receiver. Any of the methods in the optional implementation.

In a fourth aspect, an embodiment of the present application provides a terminal, where the terminal includes a receiver and a processor, and performs the foregoing method in any optional implementation of the second aspect or the second aspect by using the receiver and the processor.

In a fifth aspect, the embodiment of the present application provides a network side device, where the network side device includes a sending module, a processing module, and a receiving module, and performs the foregoing first aspect or the first aspect by using the foregoing sending module, the processing module, and the receiving module. Any of the methods in the optional implementation.

In a sixth aspect, an embodiment of the present application provides a terminal, where the terminal includes a receiving module and a processing module, and performs the foregoing method in any optional implementation of the second aspect or the second aspect by using the receiving module and the processing module.

In a seventh aspect, the present application provides a computer readable medium for storing a computer program comprising instructions for performing the method of the first aspect or any possible implementation of the first aspect.

In an eighth aspect, the present application provides a computer readable medium for storing a computer program, the computer program comprising a method for performing the second aspect or any possible implementation of the second aspect Instructions.

Further on the basis of the implementations provided by the above aspects, the invention may be further combined to provide further implementation.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following drawings will be briefly described in the description of the embodiments. It is obvious that the drawings in the following description are only some embodiments of the present application, Those skilled in the art can also obtain other drawings based on these drawings without paying for inventive labor.

1 is a schematic flowchart of a resource scheduling method in an embodiment of the present application;

2 is a schematic flowchart of another resource scheduling method in an embodiment of the present application;

3a to 3c are schematic diagrams of scheduling at least two non-uplink subframes for uplink subframes in the embodiment of the present application;

4 is a schematic diagram of a network side device 300 in an embodiment of the present application;

FIG. 5 is a schematic diagram of a terminal 400 according to an embodiment of the present application;

FIG. 6 is a schematic diagram of a network side device 500 in an embodiment of the present application;

FIG. 7 is a schematic diagram of a terminal 600 in an embodiment of the present application.

detailed description

The technical solutions of the present application are described in detail below with reference to the drawings and specific embodiments. It should be understood that the specific features of the embodiments and the embodiments of the present application are the detailed description of the technical solutions of the present application, and are not limited to the technical solutions of the present application. In the case of no conflict, the technical features in the embodiments of the present application and the embodiments may be combined with each other.

The method provided by the embodiment of the present application can be applied to the TDD system, and can also be applied to other suitable communication systems, which is not limited in this application. The resource scheduling method provided by the embodiment of the present application is described below by taking the TDD system as an example.

In a TDD system, one radio frame includes 10 subframes, and 10 subframes are specifically divided into uplink subframes (English) Text: Uplink subframe), downlink subframe (English: Downlink subframe) and special subframe (English: Special subframe). The TDD system can support 7 different uplink and downlink configurations, and the ratio of uplink and downlink subframes is different in different configurations.

Table 1 is a list of seven uplink and downlink configurations of the TDD system, where D represents a downlink subframe (English: Downlink subframe), U represents an uplink subframe (English: Uplink subframe), and S represents a special subframe (English: Special subframe) ).

Table 1: TDD uplink and downlink subframe configuration

The TDD system includes a network side device and a terminal, wherein the network side device includes but is not limited to: a base station in a mobile communication network, a cell communication device, a relay device, and the like. For example, in a TDD-LTE system, the network side device may be an evolved base station (English: evolved NodeB, eNB).

The terminal may be a mobile terminal, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal, for example, a portable, pocket-sized, handheld, computer-integrated or in-vehicle mobile device that is connected to the wireless device. Incoming voice and/or data. For example, in a TDD-LTE system, a terminal may be referred to as a user equipment (UE).

FIG. 1 is a schematic flowchart of a resource scheduling method according to an embodiment of the present disclosure, where the method includes the following steps:

Step 101: The network side device obtains information about at least one terminal to be scheduled.

Specifically, the information of the at least one terminal to be scheduled includes the identifier of the at least one terminal to be scheduled, and the terminal identifier is information for identifying the terminal, and may include multiple implementation manners, for example, For example, when the terminal is a mobile phone, the terminal identifier may be an international mobile subscriber identification number (IMSI) or an international mobile equipment identity (IMEI). For another example, the terminal identifier may also be a globally unique temporary UE identity (GUTI). For other implementations of the terminal identifier, refer to the prior art, and the embodiments of the present application are not exemplified herein.

Optionally, the information about the at least one terminal to be scheduled further includes: information indicating an uplink channel quality of the at least one terminal to be scheduled, such as a channel quality indicator (CQI); and/or The size of the uplink data to be sent by at least one terminal to be scheduled.

For a specific implementation manner of the network side device obtaining the information of the terminal to be scheduled, refer to various technical means in the prior art, which is not described in detail in the embodiment of the present application.

Step 102: The network side device determines, by using the at least two non-uplink subframes before the first uplink subframe, the quantity of resources that can be used to send the uplink grant UL grant.

Specifically, the first uplink subframe may be any uplink subframe in the radio frame. For example, in configuration 2 of Table 1, the first uplink subframe may be an uplink subframe of number 2 (#), or may be 7 Number uplink subframe.

The at least two non-uplink subframes before the first uplink subframe are: the non-uplink subframe located before the first uplink subframe and the wireless location of the first uplink subframe in the radio frame where the first uplink subframe is located At least two non-uplink subframes in the set of non-uplink subframes in the radio frame before the frame.

The at least two non-uplink subframes may be at least two downlink subframes, or may be at least two special subframes, and may also include both downlink subframes and special subframes.

The manner in which the network side device determines the number of resources that can be used to send the uplink grant UL grant in each of the at least two non-uplink subframes may be: the network side device determines the total number of PDCCH or EPDCCH resources owned by the subframe, and the sub The number of resources required to be transmitted by the PDCCH or the EPDCCH, such as DL assignment and HARQ, in the frame, and the number of resources occupied by DL assignment, HARQ, etc., from the total number of PDCCH or EPDCCH resources, which is available for transmission. The amount of resources that the upstream grant UL grant.

It should be noted that the order of execution between step 101 and step 102 is not limited, and the two It can be executed at the same time, or step 101 can be executed first, or step 102 can be executed first.

Step 103: The network side device determines, according to the information of the at least one terminal to be scheduled and the quantity of resources of the at least two non-uplink subframes that can be used to send the UL grant, that M of the at least one terminal can be scheduled in the first uplink subframe. Terminal, M is not less than 1.

Specifically, for a UE with better uplink channel quality, the UL grant that is scheduled for the UE can occupy less PDCCH or EPDCCH resources, and for the UE with poor uplink channel quality, the UL grant that is scheduled for the UE. More PDCCH or EPDCCH resources can be occupied.

After obtaining the information of the at least one terminal to be scheduled and the quantity of resources of the at least two non-uplink subframes that are available for transmitting the UL grant, the network side device determines M terminals from the at least one terminal, and sends the M terminals to the M terminals. Allocating PUSCH resources in the first uplink subframe.

The foregoing determines the M terminals from the at least one terminal, including multiple implementation manners, including but not limited to the following manners:

First, when the number of resources available for transmitting the UL grant in at least two non-uplink subframes is not less than the sum of resources occupied by all UL grants required to schedule the at least one terminal, the M terminals are all of the at least one terminal. .

Second, when the number of resources available for transmitting the UL grant in the at least two non-uplink subframes is smaller than the sum of the resources occupied by all the UL grants required to schedule the at least one terminal, all ULs required by the network side device to the at least one terminal The resources occupied by the grant are sorted, and the total number of resources occupied by the first M UL grants in the sorting is not greater than the number of resources available for transmitting the UL grant of at least two non-uplink subframes, and the first M+1 in the sorting If the total number of resources occupied by the UL grant is greater than the number of resources of the at least two non-uplink subframes that can be used to send the UL grant, determining that the terminals scheduled by the first M UL grants in the ranking are schedulable on the first uplink subframe M terminals.

Third, the terminal has an uplink scheduling priority, and the uplink scheduling priorities of different terminals may be different. For example, an advanced member's uplink scheduling priority is greater than that of an ordinary member. When the number of resources available for transmitting the UL grant in the at least two non-uplink subframes is smaller than the sum of the resources occupied by all the UL grants required to schedule the at least one terminal, the network side device sorts the uplink scheduling priorities of the at least one terminal, Determining that the total number of resources occupied by the first M terminals in the sorting is not greater than the at least two non-uplink subframes The number of resources that can be used to transmit the UL grant, and the total number of resources occupied by the first M+1 terminals in the ranking is greater than the number of resources available for transmitting the UL grant of at least two non-uplink subframes, and the pre-M in the ranking is determined. The terminals are M terminals that are schedulable on the first uplink subframe.

Fourth, combine the above two and the third. For example, when the uplink scheduling priorities of the at least one terminal are sorted in the foregoing three, the plurality of terminals having the same uplink scheduling priority in the at least one terminal are subjected to the number of resources occupied by the UL grant corresponding to each terminal. Sorting, in which the corresponding UL grant occupies a terminal with less resources.

For example, in the foregoing two, the resources of all the UL grants required by the at least one terminal are sorted, and the multiple UL grants having the same resources are sorted according to the uplink scheduling priority of the scheduled terminals, where The UL grant corresponding to the terminal with higher uplink scheduling priority is ranked first.

Fifth, the network side device to determine at least two non-first subframe of uplink sub-frame period may be scheduled in the most before the at least one terminal of the terminals M _1, wherein the network side device may be based on the Second to Fourth determining in any one of at least two non-first subframe may be an uplink sub-frame scheduling at least one terminal of the terminals M _1; or, selecting at least one terminal can be utilized most of the at least two non-uplink subframes a first subframe UL grant resources available for transmitting terminals of M _1, e.g., the first subframe occupied by the UL grant of the total resources of the M ₁ corresponding to the terminals of at least two non-uplink subframe The difference that can be used to send UL grant resources is the smallest. Then, the network side device sequentially determines M ₂ terminals of the at least one terminal in the second subframe of the second of the at least two non-uplink subframes, and so on, until at least two non-uplinks are determined. subframe time of the last row of the at least one terminal may schedule the terminals M _{n, wherein, M 1 + M 2 + ...} + M n = M.

Sixth, M is equal to 1, that is, the network side device determines that only one terminal can be scheduled in at least two non-uplink subframes. For example, the uplink scheduling priority of the terminal is higher than all other terminals in the at least one terminal, and the UL grant corresponding to the terminal needs to occupy more PDCCH or EPDCCH resources, and at least two Each of the non-uplink subframes cannot provide the resource for scheduling the terminal, and the sum of the resources of all the at least two non-uplink subframes that can be used for transmitting the UL grant is after the UL grant corresponding to the terminal. , the remaining resources are less than at least The resources required by the UL grant corresponding to any other terminal in a terminal. Therefore, the network side device determines that only one terminal can be scheduled in at least two non-uplink subframes.

It should be noted that the above-mentioned six examples are only a description of a possible case of M=1, and it cannot be considered that M=1 can only be the case in the above example. For example, when the number of terminals of the at least one terminal is 1, and the resource corresponding to the UL grant needs to be provided by the at least two non-uplink subframes, the network side device may also determine that M=1.

Step 104: The network side device sends M UL grants in the at least two non-uplink subframes, and each of the M UL grants is used to schedule one of the M terminals.

Specifically, the network side device sends, by using the PDCCH or the EPDCCH resource of the at least two non-uplink subframes, a UL grant that is scheduled for each of the M terminals.

Step 104 includes various implementations including, but not limited to, the following:

Mode 1, in combination with the foregoing six, M=1, if the number of at least two non-uplink subframes is K, the UL grant for scheduling the one terminal is divided into K parts, and the at least two are adopted. Each of the non-uplink subframes transmits a portion of the K portion, and different portions of the K portion are transmitted in different subframes.

In the foregoing manner 1, the terminal can be scheduled by using at least two non-uplink subframes to ensure that the terminal that cannot be mobilized through one non-uplink subframe can obtain the uplink resource in time.

Mode 2, in combination with the foregoing fifth, when M is greater than 1, the network side device sends at least one UL grant of the M UL grants in each of the at least two non-uplink subframes.

In the foregoing method 2, the resources of the UL grant allocated to the PUSCH resources in the first uplink subframe can be transmitted in each of the at least two non-uplink subframes, so that the first uplink subframe can have more resources. The terminal is scheduled.

In the third mode, in combination with any one of the foregoing four to four, when the M is greater than 1, the network side device may divide the first UL grant used for scheduling the first terminal in the M UL grants into N parts, where N is greater than 1. And not greater than the number of at least two non-uplink subframes.

The network side device sends N parts of the first UL grant by using N subframes in the at least two non-uplink subframes, where the network side device sends the N parts in each of the N subframes a portion, a portion of the N portions transmitted in any two of the N subframes being different; the combination of the N portions of the first UL grant is used by the first terminal to determine the physicality to which the first uplink subframe is allocated Uplink shared channel PUSCH resource.

For example, after the first non-uplink subframe of the at least two non-uplink subframes is allocated to transmit the UL grant for scheduling the second terminal of the M terminals, the remaining available for transmitting the UL grant resource is insufficient to send the first The resource required by the UL grant, in this case, the network side device may divide the first UL grant into two parts, where the resource occupied by the first part of the first UL grant is not greater than the first non-uplink subframe. The remaining ones are used to send the UL grant resource, and the resource occupied by the first part of the first UL grant is not greater than the second non-uplink subframe that is located after the first non-uplink subframe in the at least two non-uplink subframes. The number of resources for sending UL grants. The network side device may send the first part of the first UL grant by using the first non-uplink subframe, and send the second part of the first UL grant by using the second non-uplink subframe.

In the foregoing manner 3, the resources that can be used for transmitting the UL grant in the at least two non-uplink subframes can be fully utilized, and the number of schedulable terminals in the first uplink subframe is increased, and the uplink scheduling capability of the network side device is improved.

Optionally, the network side device is different in the terminal scheduled by any two of the foregoing M UL grants.

In the technical solution of the foregoing step 101 to step 104, the network side device can send M UL grants by using at least two non-uplink subframes before the first uplink subframe, and allocate the M terminals to the first uplink subframe. PUSCH resources. Compared with the technical solution of scheduling the terminal in the first uplink subframe by using only one non-uplink subframe in the prior art, the number of terminals that can be scheduled in the first uplink subframe can be significantly increased, and the network side device is improved. Uplink scheduling capability.

The embodiment of the present application further provides a resource scheduling method, which is used to enable a terminal to obtain a UL grant for allocating a PUSCH resource in a first uplink subframe. 2 is a schematic flow chart of the method, and the method includes the following steps:

Step 201: The terminal detects a UL grant sent by the network side device in the at least two non-uplink subframes before the first uplink subframe, where the UL grant is used by the scheduling terminal to use the PUSCH resource of the first uplink subframe. source;

Step 202: After detecting the UL grant in any subframe of the at least two non-uplink subframes, the terminal determines, according to the UL grant, the PUSCH resource that is allocated by itself in the first uplink subframe.

Specifically, there are multiple conditions that trigger the terminal to perform the foregoing step 201, including but not limited to the following:

Case 1: When the terminal needs to send uplink data, the terminal sends an uplink scheduling request (English: Scheduling Request, SR) to the network side device. After receiving the SR, the network side device sends a UL grant to the terminal. The terminal needs to perform step 201 to detect, in the at least two non-uplink subframes, whether there is a UL grant for scheduling the terminal to use the PUSCH resource of the first uplink subframe.

In case 2, the network side device actively allocates the PUSCH resource in the first uplink subframe to the terminal, and informs the terminal to detect that the UL grant is detected in the at least two non-uplink subframes to determine that the first uplink subframe is in the first uplink subframe according to the UL grant. The assigned PUSCH resource.

Step 201 also includes various implementations, including but not limited to the following:

In the mode A, after transmitting the SR to the network side device, the terminal detects the UL grant sent to itself in each non-uplink subframe.

In the mode B, the network side device and the terminal agree that only a part of the non-uplink subframes in the radio frame are used as the subframes for transmitting the UL grant. After transmitting the SR, the terminal detects the UL grant sent to itself only in the non-uplink subframe that can be used to transmit the UL grant.

For example, in the communication system corresponding to configuration 2 in Table 1, the network side device and the terminal agree that for the uplink subframe 7 of the radio frame, the UL transmitted through the downlink subframes 3 and 4 in the same radio frame The grant allocates its PUSCH resources. For the uplink subframe No. 2, the PU grant transmitted by the downlink subframes 8 and 9 in the previous radio frame is allocated to the PUSCH resource. The terminal may send the SR to the network side device in the uplink subframe 2 of the first radio frame, and then the terminal first detects the UL grant in the downlink subframe 3 of the next frame of the first radio frame, if not detected, Continuing to detect the UL grant in the downlink subframe 4 of the next frame of the first radio frame, if it is still not detected, it is determined that the network side device does not allocate the PUSCH resource of the uplink subframe 7 to the terminal. The terminal continues to detect the UL grant in the downlink subframe No. 8. If the UL grant sent to itself is detected, the terminal does The PUSCH resources of the No. 2 uplink subframe of the next radio frame are allocated, and it is determined according to the UL grant that they are specifically allocated those PUSCH resources.

In the above method B, the terminal detects the UL grant only in the subframe in which the UL grant can be transmitted, and can reduce the amount of detection operation of the terminal.

In the mode C, the network side device and the terminal agree that the PUSCH resource of the first uplink subframe of one radio frame is allocated by the UL grant sent by the determined at least two subframes before the first uplink subframe, for example, in Table 1. In the communication system corresponding to configuration 2, the network side device and the terminal agree that, for the uplink subframe 7 of the radio frame, the UL grant sent by the downlink subframes 3 and 4 in the same radio frame carries out the PUSCH resource. distribution.

After determining that the terminal allocates the PUSCH resource in the first uplink subframe to the terminal, the network side device sends a notification message to the terminal to inform the terminal that the PUSCH resource in the first uplink subframe has been allocated. However, it is not notified which part of the first uplink subframe is allocated to the terminal. The terminal needs to detect the UL grant sent to itself on at least two non-uplink subframes that are used for uplink scheduling of the first uplink subframe.

In the foregoing method C, after determining that the PUSCH resource in the first uplink subframe is allocated, the terminal detects the UL grant only on the at least one non-uplink subframe of the PUSCH resource that can schedule the first uplink subframe, and can reduce the UL grant. The amount of detection operation of the terminal.

In the mode D, in combination with the mode 1 or the mode 4 in the foregoing step 104, the UL grant is divided into N parts, where N is greater than 1 and not greater than the number of at least two non-uplink subframes; and the terminal is in at least two non-uplink subframes. N parts are detected, and the combination of N parts is regarded as a UL grant after N parts are detected.

The terminal may determine, according to the identifier of each part of the UL grant, that the part is part of the UL grant sent to the user, for example, the identifier of the UL grant includes “A-1”, where A is the identifier of the terminal, “- 1′′ indicates the first part of the UL grant corresponding to the terminal, and the network side device may add an end identifier to the last part of the UL grant, and according to the end identifier, the terminal may determine that all parts of the UL grant have been detected, and all parts are The combination is a UL grant.

It should be noted that the above-mentioned example is only one possible implementation manner of the mode D. For example, in another possible implementation of the foregoing mode D, the network side device informs the terminal in advance and sends the same. The UL grant is divided into N parts, and the verification information of each part is notified to the terminal, and the terminal determines whether a part of its own UL grant is detected based on the verification information.

In the foregoing manner D, the terminal can separately detect each part of the UL grant sent to itself, and combine all the received parts to form a UL grant to determine the PUSCH resource allocated by itself in the first uplink subframe, so that the network side The device can fully utilize the resources of the at least two non-uplink subframes before the first uplink subframe that can be used to send the UL grant, so that the network side device can schedule more terminals.

In the mode E, the terminal detects the UL grant in the at least two non-uplink subframes one by one according to the chronological order, and stops detecting after detecting the UL grant in any one of the at least two non-uplink subframes.

For example, in combination with the foregoing manner C, after detecting that the uplink resource is allocated to the first uplink subframe, the terminal detects the UL grant sent to itself in at least two non-uplink subframes corresponding to the first uplink subframe. The terminal first detects the UL grant in the first subframe with the earliest time in the at least two non-uplink subframes, and stops detecting in the remaining subframes of the at least two non-uplink subframes if the UL grant is detected. . If the UL grant is not detected in the first subframe, the UL grant is detected in the second subframe after the first subframe in at least two non-uplink subframes, and so on, until UL grant detected.

In the foregoing mode E, the network side device preferentially sends the UL grant for scheduling the terminal in the preceding subframe of the at least two non-uplink subframes; correspondingly, the terminal preferentially takes the time in the at least two non-uplink subframes. The UL grant is detected in the previous subframe. In this way, the terminal can obtain the UL grant as early as possible, obtain the longest time for determining the uplink resource that is allocated according to the UL grant, and prepare the uplink data to be sent to ensure the smooth transmission of the uplink data.

It should be noted that the terminal detects the implementation of the UL grant sent to itself in each of the at least two non-uplink subframes. Please refer to the prior art that the terminal is blind in the downlink subframe or the special subframe. The technical solution for detecting the UL grant is not described in detail in the embodiment of the present application.

Further, any of the above modes A to C may be combined with the above mode D or mode E.

In the technical solution of the foregoing step 201 to step 202, the terminal can detect the UL grant sent to itself on the at least two non-uplink subframes, so that the network side device can pass the first uplink subframe. The at least two non-uplink subframes send M UL grants for scheduling M terminals, and are used to allocate the PUSCH resources on the first uplink subframe to the M terminals. Compared with the technical solution of scheduling the terminal in the first uplink subframe by using only one non-uplink subframe in the prior art, the number of terminals that can be scheduled in the first uplink subframe can be significantly increased, and the network side device is improved. The uplink scheduling capability also increases the likelihood that the terminal will be allocated resources on the first uplink subframe.

Optionally, in the embodiment of the present invention, the resource scheduling method of step 101 to step 104 and step 201 to step 202 should be used for the time division duplex TDD system in which the uplink and downlink subframes of the radio frame are configured as configuration 2, in the first When the uplink subframe is the uplink subframe 7 of the first radio frame, the at least two non-uplink subframes include: the downlink subframe 0 of the first radio frame, the special subframe 1 of the first radio frame, and the first wireless The downlink subframe 3 of the frame, the downlink subframe 4 of the first radio frame, the downlink subframe 5 of the first radio frame, the special subframe 6 of the first radio frame, and the previous frame of the first radio frame At least two of the downlink subframe 8 and the downlink subframe 9 of the previous frame of the first radio frame.

Optionally, in the embodiment of the present invention, the resource scheduling method in step 101 to step 104 and step 201 to step 202 may be used in a time division duplex TDD system in which the uplink and downlink subframes of the radio frame are configured as configuration 2, in the first uplink. When the subframe is the uplink subframe 2 of the first radio frame, the at least two non-uplink subframes include: the downlink subframe 0 of the first radio frame, the special subframe 1 of the first radio frame, and the first radio frame. The downlink subframe 3 of the previous frame, the downlink subframe 4 of the previous frame of the first radio frame, the downlink subframe 5 of the previous frame of the first radio frame, and the previous frame of the first radio frame At least two of the special subframe No. 6, the eighth downlink subframe of the previous frame of the first radio frame, and the downlink subframe 9 of the previous frame of the first radio frame.

It should be noted that, in the case that the first uplink subframe is the uplink subframe 2 of the first radio frame or the uplink subframe 7 of the first radio frame, the subframes in the at least two non-uplink subframes The number can be discontinuous. For example, when the first uplink subframe is the uplink subframe 7 of the first radio frame, the at least two non-uplink subframes are: the downlink subframe 3 of the first radio frame and the downlink subframe 5 of the first radio frame. Frame two subframes.

In addition, at least two non-uplink subframes corresponding to the uplink subframe 2 of the radio frame may have an intersection with at least two non-uplink subframes corresponding to the uplink subframe 2 of the same radio frame, for example, the uplink of the radio frame. At least two non-uplink subframes corresponding to the subframe and at least two uplink subframes corresponding to the same radio frame The two non-uplink subframes may each include a downlink subframe No. 0 in the same radio frame. The downlink subframe No. 0 has a resource remaining for transmitting the UL grant after the scheduling of the uplink subframe 2 is completed, and the UL grant for scheduling the PUSCH in the uplink subframe 7 can be continuously transmitted.

Optionally, the resource scheduling method provided by the embodiment of the present application is applicable to the PUSCH resource in the uplink subframe of the second uplink subframe, where the uplink and downlink subframes are configured as the configuration 2, including but not limited to the following scheduling modes:

Scheduling mode 1, referring to FIG. 3a, transmitting 2 for the second radio frame by the downlink subframe 8 of the first radio frame and the downlink subframe 9 of the first radio frame as the previous frame of the second radio frame The UL grant of the allocated PUSCH resource of the uplink subframe.

Scheduling method 2, referring to FIG. 3b, passing the No. 8 downlink subframe of the first radio frame, the No. 9 downlink subframe of the first radio frame, and the No. 0 downlink of the second radio frame as the previous frame of the second radio frame The frame transmits a UL grant for the PUSCH resource of the second uplink subframe of the second radio frame.

Scheduling method 3, referring to FIG. 3c, passing the downlink subframe 8 of the first radio frame, the downlink subframe 9 of the first radio frame, and the downlink of the second radio frame of the second radio frame as the previous frame of the second radio frame The subframe and the second special subframe of the second radio frame transmit a UL grant for allocating PUSCH resources of the second uplink subframe of the second radio frame.

Optionally, in the TDD system in which the uplink and downlink subframes are configured as the configuration 2, the PUSCH resources on the uplink subframe 2 include, but are not limited to, the following scheduling modes:

Scheduling method 4, with reference to FIG. 3a, transmitting PUSCH resources for the uplink subframe 7 of the first radio frame by using the downlink subframe 3 of the first radio frame and the downlink subframe 4 of the first radio frame UL grant.

The scheduling mode 5, with reference to FIG. 3b, is sent by using the downlink subframe 3 of the first radio frame, the downlink subframe 4 of the first radio frame, and the downlink subframe 5 of the first radio frame for the first radio frame. The UL grant of the PUSCH resource of the uplink subframe 7 is allocated.

The scheduling method 6, referring to FIG. 3c, passes the downlink subframe 3 of the first radio frame, the downlink subframe 4 of the first radio frame, the downlink subframe 5 of the first radio frame, and the sixth subframe of the first radio frame. The special subframe transmits a PUSCH resource for scheduling the uplink subframe 7 of the first radio frame. UL grant.

It should be noted that any one of the scheduling methods 1 to 3 may be combined with any one of the scheduling methods 4 to 6 described above. For example, the solution shown in FIG. 3a is a combination of scheduling mode 1 and scheduling mode 4; the solution shown in FIG. 3b is a combination of scheduling mode 2 and scheduling mode 5; and the solution shown in FIG. 3c is a combination of scheduling mode 3 and scheduling mode 6. In addition, the scheduling mode 1 may be combined with the scheduling mode 5 or the scheduling mode 6. For other possibilities of the combination of the foregoing scheduling modes, the embodiments of the present application are not illustrated herein.

Optionally, in the embodiment of the present invention, when the resource scheduling method in step 101 to step 104 and step 201 to step 202 is applied to the TDD system, the radio frame structure of the TDD system is configured to be in a radio frame. The number of uplink subframes is smaller than the number of non-uplink subframes.

Referring to FIG. 4, an embodiment of the present application further provides a network side device 300, including:

a receiver 301, configured to obtain information about at least one terminal to be scheduled;

The processor 302 is configured to determine, by using at least two non-uplink subframes before the first uplink subframe, a quantity of resources that can be used to send the uplink grant UL grant, and according to information about the at least one terminal to be scheduled, and at least two non-uplinks. The number of resources of the frame that can be used to send the UL grant, determining that M terminals in at least one terminal can be scheduled on the first uplink subframe, where M is not less than 1;

The transmitter 303 is configured to send M UL grants in at least two non-uplink subframes, and each of the M UL grants is used to schedule one of the M terminals.

Optionally, in the embodiment of the present application, if M is greater than 1, the transmitter 303 sends at least one UL grant of the M UL grants in each of the at least two non-uplink subframes.

Optionally, in the embodiment of the present application, the processor 302 divides the first UL grant used for scheduling the first terminal in the M UL grants into N parts, where N is greater than 1 and not greater than at least two non-uplink subframes. Number

The transmitter 303 is configured to: send, by using N subframes of the at least two non-uplink subframes, N parts of the first UL grant, where the transmitter 303 sends the N parts in each of the N subframes. a portion, the portions of the N portions transmitted in any two of the N subframes are different; the combination of the N portions of the first UL grant is used by the first terminal to determine itself in the first uplink subframe The assigned physical uplink shared channel PUSCH resource.

Optionally, in the embodiment of the present application, the network side device 300 belongs to the time division duplex TDD system in which the uplink and downlink subframes of the radio frame are configured as the configuration 2, and the first uplink subframe is the uplink subframe 7 of the first radio frame. The at least two non-uplink subframes include: a downlink subframe 0 of the first radio frame, a special subframe 1 of the first radio frame, a downlink subframe 3 of the first radio frame, and 4 of the first radio frame. No. downlink sub-frame, No. 5 downlink sub-frame of the first radio frame, No. 6 special sub-frame of the first radio frame, No. 8 downlink sub-frame of the previous frame of the first radio frame, and a previous frame of the first radio frame At least two of the 9th downlink subframes.

Optionally, in the embodiment of the present application, the network side device 300 belongs to the TDD system in which the uplink and downlink subframes of the radio frame are configured as the configuration 2, and when the first uplink subframe is the uplink subframe 2 of the first radio frame, at least The two non-uplink subframes include: a downlink subframe 0 of the first radio frame, a special subframe 1 of the first radio frame, a downlink subframe 3 of the previous frame of the first radio frame, and a first radio frame. The downlink subframe No. 4 of the previous frame, the downlink subframe 5 of the previous frame of the first radio frame, the special subframe 6 of the previous frame of the first radio frame, and the previous frame of the first radio frame At least two of the downlink subframe and the downlink subframe 9 of the previous frame of the first radio frame.

Optionally, the network side device 300 further includes a memory 304 for storing instructions, and the processor 302 implements functions of the processor by executing instructions in the memory 304.

The receiver 301 and the transmitter 303 described above may be two separate devices or may be integrated to form a transceiver.

The above processor 302 may be a processing element or a collective name of a plurality of processing elements. For example, the processor 302 may be a central processing unit (CPU), or an application specific intergrated circuit (ASIC), or one configured to implement an embodiment of the present invention. A plurality of integrated circuits, such as one or more microprocessors (DSPs), or one or more field programmable gate arrays (FPGAs).

For the specific implementation of the components of the network-side device 300, reference may be made to the implementation of the steps performed by the network-side device in the method corresponding to FIG. 1, which is not repeated here.

Referring to FIG. 5, an embodiment of the present application further provides a terminal 400, including:

The receiver 401 is configured to detect, in the at least two non-uplink subframes before the first uplink subframe, a UL grant sent by the network side device, where the UL grant is used by the scheduling terminal to use the PUSCH resource of the first uplink subframe.

The processor 402 is configured to determine, by the receiver 401, the PUSCH resource that is allocated by itself in the first uplink subframe according to the UL grant after detecting the UL grant in any subframe of the at least two non-uplink subframes.

Optionally, in the embodiment of the present application, the receiver 401 detects the UL grant in the at least two non-uplink subframes one by one according to the chronological order, and detects the UL grant in any one of the at least two non-uplink subframes. Stop detection afterwards.

Optionally, in the embodiment of the present application, the UL grant is divided into N parts, where N is greater than 1 and not greater than the number of at least two non-uplink subframes;

The receiver 401 is configured to: detect N parts in at least two non-uplink subframes;

The processor 402 is configured to: after the receiver detects N parts, combine the N parts as a UL grant.

Optionally, in the embodiment of the present application, the terminal 400 belongs to the TDD system in which the uplink and downlink subframes of the radio frame are configured as the configuration 2, and when the first uplink subframe is the uplink subframe 7 of the first radio frame, at least two The non-uplink subframe includes: a downlink subframe 0 of the first radio frame, a special subframe 1 of the first radio frame, a downlink subframe 3 of the first radio frame, and a downlink subframe 4 of the first radio frame, No. 5 downlink sub-frame of the first radio frame, No. 6 special sub-frame of the first radio frame, No. 8 downlink sub-frame of the previous frame of the first radio frame, and No. 9 downlink sub-frame of the previous frame of the first radio frame At least two of the frames.

Optionally, in the embodiment of the present application, the terminal 400 belongs to the TDD system in which the uplink and downlink subframes of the radio frame are configured as the configuration 2, and when the first uplink subframe is the uplink subframe 2 of the first radio frame, at least two The non-uplink subframe includes: a downlink subframe 0 of the first radio frame, a special subframe 1 of the first radio frame, a downlink subframe 3 of the previous frame of the first radio frame, and a previous subframe of the first radio frame. No. 4 downlink subframe of the frame, No. 5 downlink subframe of the previous frame of the first radio frame, No. 6 special subframe of the previous frame of the first radio frame, and No. 8 downlink of the previous frame of the first radio frame At least two of the subframe, the downlink subframe 9 of the previous frame of the first radio frame.

Optionally, the terminal 400 further includes a transmitter 403, configured to send data or signaling to the network side device.

Optionally, the terminal 400 further includes a memory 404 for storing instructions, and the processor 402 implements its functions by executing instructions in the memory 404.

The receiver 401 and the transmitter 403 described above may be two separate devices or may be integrated to form a transceiver.

The above processor 402 may be a processing element or a collective name of a plurality of processing elements. For example, the processor 402 may be a central processing unit (CPU), or an application specific intergrated circuit (ASIC), or one configured to implement an embodiment of the present invention. A plurality of integrated circuits, such as one or more microprocessors (DSPs), or one or more field programmable gate arrays (FPGAs).

For the specific implementation of the components of the terminal 400, reference may be made to the implementation of the steps performed by the terminal in the method corresponding to FIG. 2, which is not repeated here.

Referring to FIG. 6, the embodiment of the present application further provides a network side device 500, including:

The receiving module 501 is configured to obtain information about at least one terminal to be scheduled.

The processing module 502 is configured to determine, according to information of at least two non-uplink subframes before the first uplink subframe, a quantity of resources that can be used to send the uplink grant UL grant, and, according to information about the at least one terminal to be scheduled, and at least two non-upstreams The number of resources of the subframe that can be used to send the UL grant, determining that M terminals in at least one terminal can be scheduled on the first uplink subframe, where M is not less than 1;

The sending module 503 is configured to send M UL grants in at least two non-uplink subframes, and each of the M UL grants is used to schedule one of the M terminals.

Optionally, in the embodiment of the present application, if M is greater than 1, the sending module 503 sends at least one UL grant of the M UL grants in each of the at least two non-uplink subframes.

Optionally, in the embodiment of the present application, the first UL grant for scheduling the first terminal in the M UL grants is divided into N parts, where N is greater than 1 and not greater than the number of at least two non-uplink subframes;

The sending module 503 is configured to: send, by using N subframes of the at least two non-uplink subframes, N parts of the first UL grant, where the sending module 503 sends in each of the N subframes One of the N parts, the part of the N parts transmitted in any two of the N subframes is different; the combination of the N parts of the first UL grant is used by the first terminal to determine the first uplink subframe The physical uplink shared channel PUSCH resource that is allocated by itself.

Optionally, in the embodiment of the present application, the network side device 500 is applied to the time division duplex TDD system in which the uplink and downlink subframes of the radio frame are configured as the configuration 2, and the first uplink subframe is the uplink subframe 7 of the first radio frame. In the case of a frame, the at least two non-uplink subframes include: a downlink subframe 0 of the first radio frame, a special subframe 1 of the first radio frame, a downlink subframe 3 of the first radio frame, and a first radio frame. No. 4 downlink sub-frame, No. 5 downlink sub-frame of the first radio frame, No. 6 special sub-frame of the first radio frame, No. 8 downlink sub-frame of the previous frame of the first radio frame, and the previous one of the first radio frame At least two of the number 9 downlink subframes of the frame.

Optionally, in the embodiment of the present application, the network side device 500 is applied to the TDD system in which the uplink and downlink subframes of the radio frame are configured as the configuration 2, and when the first uplink subframe is the uplink subframe 2 of the first radio frame, The at least two non-uplink subframes include: a downlink subframe 0 of the first radio frame, a special subframe 1 of the first radio frame, a downlink subframe 3 of the previous frame of the first radio frame, and a first radio frame. The downlink subframe 4 of the previous frame, the downlink subframe 5 of the previous frame of the first radio frame, the special subframe 6 of the previous frame of the first radio frame, and the previous frame of the first radio frame At least two of the downlink subframe 8 and the downlink subframe 9 of the previous frame of the first radio frame.

For the specific implementation of each module of the network side device 500, refer to the implementation manner of each step performed by the network side device in the method corresponding to FIG. 1, which is not repeated here.

Referring to FIG. 7, an embodiment of the present application provides a terminal 600, including:

The receiving module 601 is configured to detect, in the at least two non-uplink subframes before the first uplink subframe, a UL grant sent by the network side device, where the UL grant is used by the scheduling terminal to use the PUSCH resource of the first uplink subframe.

The processing module 602 is configured to determine, according to the UL grant, the PUSCH resource allocated by itself in the first uplink subframe after detecting the UL grant in any subframe of the at least two non-uplink subframes.

Optionally, in the embodiment of the present application, the receiving module 601 detects the UL grant in the at least two non-uplink subframes one by one according to the chronological order, and detects in any one of the at least two non-uplink subframes. Stop the test after the UL grant.

Optionally, in the embodiment of the present application, the UL grant is divided into N parts, where N is greater than 1 and not greater than the number of at least two non-uplink subframes;

The receiving module 601 is configured to: detect N parts in at least two non-uplink subframes;

The processing module 602 is configured to: after the receiving module 601 detects the N parts, combine the N parts as a UL grant.

Optionally, in the embodiment of the present application, the terminal 600 is applied to the TDD system in which the uplink and downlink subframes of the radio frame are configured as the configuration 2, and when the first uplink subframe is the uplink subframe 7 of the first radio frame, at least two The non-uplink subframe includes: a downlink subframe 0 of the first radio frame, a special subframe 1 of the first radio frame, a downlink subframe 3 of the first radio frame, and a downlink subframe 4 of the first radio frame. The downlink subframe 5 of the first radio frame, the special subframe 6 of the first radio frame, the downlink subframe 8 of the previous frame of the first radio frame, and the downlink of the previous frame of the first radio frame At least two of the sub-frames.

Optionally, in the embodiment of the present application, the terminal 600 is applied to the TDD system in which the uplink and downlink subframes of the radio frame are configured as the configuration 2, and when the first uplink subframe is the uplink subframe 2 of the first radio frame, at least two The non-uplink subframe includes: a downlink subframe 0 of the first radio frame, a special subframe 1 of the first radio frame, a downlink subframe 3 of the previous frame of the first radio frame, and a front of the first radio frame. No. 4 downlink sub-frame of one frame, No. 5 downlink sub-frame of the previous frame of the first radio frame, No. 6 special sub-frame of the previous frame of the first radio frame, No. 8 of the previous frame of the first radio frame At least two of the downlink subframe and the downlink subframe 9 of the previous frame of the first radio frame.

For the specific implementation of each module of the above terminal 400, reference may be made to the implementation manner of each step performed by the terminal in the method corresponding to FIG. 2, which is not repeated here.

Those skilled in the art will appreciate that embodiments of the present application can be provided as a method, system, or computer program product. Thus, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware. Moreover, the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.

The present application is made with reference to a method, a device (system), and a computer program according to an embodiment of the present application. The flow chart and/or block diagram of the product is described. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.

It will be apparent to those skilled in the art that various modifications and changes can be made in the present application without departing from the spirit and scope of the application. Thus, it is intended that the present invention cover the modifications and variations of the present invention.

Claims (28)

1. A resource scheduling method, comprising:

   The network side device obtains information of at least one terminal to be scheduled;

   The network side device determines, by using at least two non-uplink subframes before the first uplink subframe, a quantity of resources that can be used to send the uplink grant UL grant;

   Determining that the network side device can schedule the first uplink subframe according to the information of the at least one terminal to be scheduled and the quantity of resources of the at least two non-uplink subframes that can be used to send the UL grant M terminals in at least one terminal, M is not less than 1;

   The network side device sends M UL grants in the at least two non-uplink subframes, and each of the M UL grants is used to schedule one of the M terminals.
2. The method according to claim 1, wherein M is greater than 1, the network side device transmits at least one of the M UL grants in each of the at least two non-uplink subframes. Grant.
3. The method according to claim 1 or 2, wherein the first UL grant for scheduling the first terminal in the M UL grants is divided into N parts, N is greater than 1 and not greater than the at least two The number of non-uplink subframes;

   The sending, by the network side device, the first UL grant in the at least two non-uplink subframes includes:

   The network side device sends the N parts of the first UL grant by using N subframes in the at least two non-uplink subframes, where the network side device is in each of the N subframes Transmitting one of the N parts in a sub-frame, wherein a part of the N parts sent in any two of the N sub-frames is different; a combination of the N parts of the first UL grant The first terminal is used by the first terminal to determine a physical uplink shared channel PUSCH resource that is allocated on the first uplink subframe.
4. The method according to any one of claims 1 to 3, wherein the method is applied to a time division duplex TDD system in which an uplink and downlink subframe of a radio frame is configured as configuration 2, in the first uplink subroutine When the frame is the uplink subframe 7 of the first radio frame, the at least two non-uplink subframes include: a downlink subframe 0 of the first radio frame, and a special subframe 1 of the first radio frame. And the downlink subframe 3 of the first radio frame, the downlink subframe 4 of the first radio frame, the downlink subframe 5 of the first radio frame, and the special 6 of the first radio frame At least two of a subframe, a downlink subframe 8 of a previous frame of the first radio frame, and a downlink subframe 9 of a previous frame of the first radio frame.
5. The method according to any one of claims 1 to 3, wherein the method is applied to a TDD system in which an uplink and downlink subframe of a radio frame is configured as configuration 2, and the first uplink subframe is a first radio. The at least two non-uplink subframes of the second radio frame include: a downlink subframe No. 0 of the first radio frame, a special subframe 1 of the first radio frame, and the first The downlink subframe 3 of the previous frame of the radio frame, the downlink subframe 4 of the previous frame of the first radio frame, the downlink subframe 5 of the previous frame of the first radio frame, and the At least a special subframe of the previous frame of a radio frame, a downlink subframe of the first frame of the first radio frame, and at least a downlink subframe of the previous frame of the first radio frame Two.
6. The method according to any one of claims 1 to 3, wherein the method is applied to a TDD system in which an uplink and downlink subframe of a radio frame is configured as configuration 2, and the first uplink subframe is a first radio. In the uplink subframe 2 of the frame, the at least two non-uplink subframes are the downlink subframe 8 of the previous frame of the first radio frame and the downlink subframe 9 of the previous frame of the first radio frame. Subframe; and/or

   When the first uplink subframe is the uplink subframe 7 of the first radio frame, the at least two non-uplink subframes are the downlink subframe 3 of the first radio frame and the first The downlink subframe number 4 of the radio frame.
7. The method according to any one of claims 1 to 3, wherein the method is applied to a TDD system in which an uplink and downlink subframe of a radio frame is configured as configuration 2, and the first uplink subframe is a first radio. In the uplink subframe 2 of the frame, the at least two non-uplink subframes are the downlink subframe 8 of the previous frame of the first radio frame, and the downlink subframe 9 of the previous frame of the first radio frame. a subframe and a downlink subframe 0 of the first radio frame; and/or

   When the first uplink subframe is the uplink subframe 7 of the first radio frame, the at least two non-uplink subframes are the downlink subframe No. 3 of the first radio frame, and the first Wireless frame under the 4th A row subframe and a downlink subframe No. 5 of the first radio frame.
8. A resource scheduling method, the method comprising:

   The UE detects the UL grant sent by the network side device in the at least two non-uplink subframes before the first uplink subframe, where the UL grant is used to schedule the terminal to use the PUSCH resource of the first uplink subframe.

   After detecting the UL grant in any subframe of the at least two non-uplink subframes, the terminal determines, according to the UL grant, a PUSCH resource that is allocated by itself in the first uplink subframe.
9. The method according to claim 8, wherein the terminal detects the UL grant in the at least two non-uplink subframes one by one according to a chronological order, and in the at least two non-uplink subframes The detection is stopped after the UL grant is detected in any subframe.
10. The method according to claim 8 or 9, wherein the UL grant is divided into N parts, N is greater than 1 and not greater than the number of the at least two non-uplink subframes;

    The detecting, by the terminal, the UL grant sent by the network side device in the at least two non-uplink subframes before the first uplink subframe, including:

    The terminal detects the N parts in the at least two non-uplink subframes, and uses the combination of the N parts as the UL grant after detecting the N parts.
11. The method according to any one of claims 8 to 10, wherein the method is applied to a TDD system in which an uplink and downlink subframe of a radio frame is configured as configuration 2, and the first uplink subframe is a first radio. The at least two non-uplink subframes of the first radio frame include: a downlink subframe 0 of the first radio frame, a special subframe 1 of the first radio frame, and the first The downlink subframe 3 of the radio frame, the downlink subframe 4 of the first radio frame, the downlink subframe 5 of the first radio frame, and the special subframe 6 of the first radio frame, At least two of the downlink subframe 8 of the previous frame of the first radio frame and the downlink subframe 9 of the previous frame of the first radio frame.
12. The method according to any one of claims 8 to 10, wherein the method is applied to a TDD system in which an uplink and downlink subframe of a radio frame is configured as configuration 2, and the first uplink subframe is a first radio. The at least two non-uplink subframes of the second radio frame include: a downlink subframe No. 0 of the first radio frame, a special subframe 1 of the first radio frame, and the first Before the wireless frame a downlink subframe 3 of one frame, a downlink subframe 4 of a previous frame of the first radio frame, a downlink subframe 5 of a previous frame of the first radio frame, and a first radio frame of the first radio frame At least two of the special subframe No. 6 of the previous frame, the downlink subframe 8 of the previous frame of the first radio frame, and the downlink subframe 9 of the previous frame of the first radio frame.
13. The method according to any one of claims 8 to 10, wherein the method is applied to a TDD system in which an uplink and downlink subframe of a radio frame is configured as configuration 2, and the first uplink subframe is a first radio. In the uplink subframe 2 of the frame, the at least two non-uplink subframes are the downlink subframe 8 of the previous frame of the first radio frame and the downlink subframe 9 of the previous frame of the first radio frame. Subframe; and/or

    When the first uplink subframe is the uplink subframe 7 of the first radio frame, the at least two non-uplink subframes are the downlink subframe 3 of the first radio frame and the first The downlink subframe number 4 of the radio frame.
14. The method according to any one of claims 8 to 10, wherein the method is applied to a TDD system in which an uplink and downlink subframe of a radio frame is configured as configuration 2, and the first uplink subframe is a first radio. In the uplink subframe 2 of the frame, the at least two non-uplink subframes are the downlink subframe 8 of the previous frame of the first radio frame, and the downlink subframe 9 of the previous frame of the first radio frame. a subframe and a downlink subframe 0 of the first radio frame; and/or

    When the first uplink subframe is the uplink subframe 7 of the first radio frame, the at least two non-uplink subframes are the downlink subframe No. 3 of the first radio frame, and the first The downlink subframe 4 of the radio frame and the downlink subframe 5 of the first radio frame.
15. A network side device, comprising:

    a receiver, configured to obtain information about at least one terminal to be scheduled;

    a processor, configured to determine, according to the at least two non-uplink subframes before the first uplink subframe, a quantity of resources that can be used to send the uplink grant UL grant; and information according to the at least one terminal to be scheduled and the at least two The number of resources of the non-uplink subframe that can be used to send the UL grant, determining that the M terminals in the at least one terminal can be scheduled on the first uplink subframe, where M is not less than 1;

    And a transmitter, configured to send M UL grants in the at least two non-uplink subframes, where each UL grant of the M UL grants is used to schedule one of the M terminals.
16. The network side device according to claim 15, wherein M is greater than 1, and the transmitter transmits at least one of the M UL grants in each of the at least two non-uplink subframes. UL grant.
17. The network side device according to claim 15 or 16, wherein the processor divides the first UL grant for scheduling the first terminal in the M UL grants into N parts, where N is greater than 1 and Not more than the number of the at least two non-uplink subframes;

    The transmitter is configured to: send the N parts of the first UL grant by N subframes in the at least two non-uplink subframes, where the transmitter is in each of the N subframes Transmitting one of the N parts in a sub-frame, wherein a part of the N parts sent in any two of the N sub-frames is different; a combination of the N parts of the first UL grant The first terminal is used by the first terminal to determine a physical uplink shared channel PUSCH resource that is allocated on the first uplink subframe.
18. The network side device according to any one of claims 15 to 17, wherein the network side device belongs to a time division duplex TDD system in which the uplink and downlink subframes of the radio frame are configured as configuration 2, and the first uplink is performed. When the subframe is the uplink subframe 7 of the first radio frame, the at least two non-uplink subframes include: a downlink subframe 0 of the first radio frame, and a special subframe 1 of the first radio frame. a frame, a downlink subframe 3 of the first radio frame, a downlink subframe 4 of the first radio frame, a downlink subframe 5 of the first radio frame, and a 6th radio frame At least two of the special subframe, the downlink subframe 8 of the previous frame of the first radio frame, and the downlink subframe 9 of the previous frame of the first radio frame.
19. The network side device according to any one of claims 15 to 17, wherein the network side device belongs to a TDD system in which the uplink and downlink subframes of the radio frame are configured as configuration 2, and the first uplink subframe is In the second uplink subframe of the first radio frame, the at least two non-uplink subframes include: a downlink subframe 0 of the first radio frame, a special subframe 1 of the first radio frame, and a The downlink subframe 3 of the previous frame of the first radio frame, the downlink subframe 4 of the previous frame of the first radio frame, and the downlink subframe 5 of the previous frame of the first radio frame, a special subframe No. 6 of a previous frame of the first radio frame, a downlink subframe of the first frame of the first radio frame, and a first radio frame of the first radio frame At least two of the downlink subframes of the previous frame.
20. The network side device according to any one of claims 15 to 17, wherein the network side device belongs to a TDD system in which the uplink and downlink subframes of the radio frame are configured as configuration 2, and the first uplink subframe is When it is the uplink subframe 2 of the first radio frame, the at least two non-uplink subframes are the downlink subframe 8 of the previous frame of the first radio frame and the previous frame of the first radio frame. 9th downlink subframe; and/or

    When the first uplink subframe is the uplink subframe 7 of the first radio frame, the at least two non-uplink subframes are the downlink subframe 3 of the first radio frame and the first The downlink subframe number 4 of the radio frame.
21. The network side device according to any one of claims 15 to 17, wherein the network side device belongs to a TDD system in which the uplink and downlink subframes of the radio frame are configured as configuration 2, and the first uplink subframe is When it is the uplink subframe 2 of the first radio frame, the at least two non-uplink subframes are the downlink subframe 8 of the previous frame of the first radio frame, and the previous frame of the first radio frame. a downlink subframe No. 9 and a downlink subframe No. 0 of the first radio frame; and/or

    When the first uplink subframe is the uplink subframe 7 of the first radio frame, the at least two non-uplink subframes are the downlink subframe No. 3 of the first radio frame, and the first The downlink subframe 4 of the radio frame and the downlink subframe 5 of the first radio frame.
22. A terminal, comprising:

    a receiver, configured to detect, in the at least two non-uplink subframes before the first uplink subframe, a UL grant sent by the network side device, where the UL grant is used to schedule the terminal to use the first uplink subframe PUSCH resources;

    a processor, after the receiver detects the UL grant in any subframe of the at least two non-uplink subframes, determining, according to the UL grant, that the first uplink subframe is allocated according to the UL grant PUSCH resources.
23. The terminal according to claim 22, wherein the receiver detects the UL grant in the at least two non-uplink subframes one by one according to a chronological order, and in the at least two non-uplink subframes The detection is stopped after the UL grant is detected in any of the subframes.
24. The terminal according to claim 22 or 23, wherein the UL grant is divided into N parts, N is greater than 1 and not greater than the number of the at least two non-uplink subframes;

    The receiver is configured to: detect the N parts in the at least two non-uplink subframes;

    The processor is configured to: after the receiver detects the N parts, use the combination of the N parts as the UL grant.
25. The terminal according to any one of claims 22 to 24, wherein the terminal belongs to a TDD system in which the uplink and downlink subframes of the radio frame are configured as configuration 2, and the first uplink subframe is the first radio frame. The at least two non-uplink subframes include: a downlink subframe 0 of the first radio frame, a special subframe 1 of the first radio frame, and the first wireless a downlink subframe 3 of the frame, a downlink subframe 4 of the first radio frame, a downlink subframe 5 of the first radio frame, a special subframe 6 of the first radio frame, and the At least two of the downlink subframe 8 of the previous frame of the radio frame and the downlink subframe 9 of the previous frame of the first radio frame.
26. The terminal according to any one of claims 22 to 24, wherein the terminal belongs to a TDD system in which the uplink and downlink subframes of the radio frame are configured as configuration 2, and the first uplink subframe is the first radio frame. The at least two non-uplink subframes include: a downlink subframe 0 of the first radio frame, a special subframe 1 of the first radio frame, and the first wireless The downlink subframe 3 of the previous frame of the frame, the downlink subframe 4 of the previous frame of the first radio frame, the downlink subframe 5 of the previous frame of the first radio frame, and the first At least two of the special subframe No. 6 of the previous frame of the radio frame, the downlink sub-frame of the first frame of the first radio frame, and the downlink sub-frame of the previous frame of the first radio frame item.
27. The terminal according to any one of claims 22 to 24, wherein the terminal belongs to a TDD system in which the uplink and downlink subframes of the radio frame are configured as configuration 2, and the first uplink subframe is the first radio frame. In the uplink subframe No. 2, the at least two non-uplink subframes are the downlink subframe 8 of the previous frame of the first radio frame and the downlink subframe 9 of the previous frame of the first radio frame. Frame; and/or

    When the first uplink subframe is the uplink subframe 7 of the first radio frame, the at least two non-uplink subframes are the downlink subframe 3 of the first radio frame and the first The downlink subframe number 4 of the radio frame.
28. The terminal according to any one of claims 22 to 24, wherein the terminal belongs to a TDD system in which the uplink and downlink subframes of the radio frame are configured as configuration 2, and the first uplink subframe is the first radio frame. In the uplink subframe No. 2, the at least two non-uplink subframes are the downlink subframe 8 of the previous frame of the first radio frame, and the downlink subframe 9 of the previous frame of the first radio frame. a frame and a downlink subframe number 0 of the first radio frame; and/or

    When the first uplink subframe is the uplink subframe 7 of the first radio frame, the at least two non-uplink subframes are the downlink subframe No. 3 of the first radio frame, and the first The downlink subframe 4 of the radio frame and the downlink subframe 5 of the first radio frame.

Images