WO2020258264A1

WO2020258264A1 - Uplink channel scheduling method and apparatus, medium, base station, and user terminal

Info

Publication number: WO2020258264A1
Application number: PCT/CN2019/093760
Authority: WO
Inventors: 张璐; 刘松林; 盛为军
Original assignee: 海能达通信股份有限公司
Priority date: 2019-06-28
Filing date: 2019-06-28
Publication date: 2020-12-30

Abstract

The present invention provides an uplink channel scheduling method and apparatus, a medium, a base station, and a user terminal. The method comprises: receiving an uplink skipping notification from a user terminal, the uplink skipping notification being transmitted under the condition that the user terminal is in the absence of data transmission and an authorized data size authorized to the user terminal is not used up; verifying the uplink skipping notification; and if the uplink skipping notification is verified successfully, preventing transmission of a retransmission request to the user terminal. According to the method provided by the present invention, when the user terminal uses an uplink skipping function, the base station does not repeatedly require retransmission, so that resources are saved, and the utilization efficiency of the base station for network resources is improved.

Description

Uplink channel scheduling method and device, medium, base station and user terminal

Technical field

The present disclosure relates to the field of communication technologies, and in particular to an uplink channel scheduling method and device, medium, base station, and user terminal.

Background technique

With the development of LTE (Long Term Evolution) technology, the 3GPP (The 3rd Generation Partnership Project) protocol has been continuously updated and improved, and some new features have been introduced in the 3GPP protocol, including support for uplink short-cycle SPS (Semi-Persistent Scheduling) and UL Skipping (Up-Link Skipping, uplink skip) functions. The uplink short-period SPS is a semi-static scheduling with a shorter period. For services with high delay requirements, data can be sent quickly, which can reduce the delay of uplink services. The UL Skipping function is mainly for users who communicate with the base station. When the terminal does not have data to send but has the uplink authorization of the base station, it will enter a functional state of not transmitting data. In this functional state, the power consumption of the user terminal is significantly reduced.

At present, when the user terminal finishes sending data to the base station based on the 3GPP protocol, the agreement stipulates that the user terminal will no longer send data to the base station based on the UL Skipping function, but the base station has no action, so the user terminal is still notified to retransmit without knowing this status. , After requesting retransmission but failing to receive the uplink data (data sent by the user terminal to the base station) the predetermined maximum number of times, the channel resources are released. Repeatedly requesting retransmissions will cause a waste of resources for base stations and user terminals

Summary of the invention

One purpose of the present disclosure is to improve the utilization efficiency of network resources and solve the technical problem that the base station repeatedly requests retransmission and wastes resources during the use of the uplink skip function.

According to an aspect of the embodiments of the present disclosure, an uplink channel scheduling method is disclosed, including:

Receiving an uplink skip notification from a user terminal, the uplink skip notification being sent when the user terminal has no data to send and the authorized data size authorized to the user terminal has not been used up;

Verifying the uplink skip notification;

If the uplink skip notification is successfully verified, stop sending a retransmission request to the user terminal.

Determining that the user terminal is in a situation where there is no data to send and the authorized data size authorized to the user terminal has not been used up;

When the user terminal has no data to send and the authorized data size authorized to the user terminal has not been used up, an uplink skip notification is sent to the base station.

According to an aspect of the embodiments of the present disclosure, a base station is disclosed, including:

The first receiving unit is configured to receive an uplink skip notification from a user terminal, where the uplink skip notification is when the user terminal has no data to send and the authorized data size authorized to the user terminal has not been used up Send in case of;

A verification unit for verifying the uplink skip notification;

The first processing unit is configured to prevent sending a retransmission request to the user terminal if the uplink skip notification verification is successful.

According to an aspect of the embodiments of the present disclosure, a user terminal is disclosed, including:

The second processing unit is configured to determine that the user terminal is in a situation where there is no data to send and the authorized data size authorized to the user terminal has not been used up;

The second sending unit is configured to send an uplink skip notification to the base station when the user terminal has no data to send and the size of the authorized data authorized to the user terminal has not been used up.

Memory, storing computer readable instructions;

The processor reads computer readable instructions stored in the memory to execute the method as described above.

Memory, storing computer readable instructions;

According to one aspect of the embodiments of the present disclosure, a computer program medium is disclosed, including: a memory storing computer readable instructions; a processor, reading the computer readable instructions stored in the memory, to execute the method as described above.

According to one aspect of the embodiments of the present disclosure, a computer program medium is disclosed, on which computer-readable instructions are stored, and when the computer-readable instructions are executed by a processor of the computer, the computer is caused to execute the method as described above.

In the embodiment of the present disclosure, when the user terminal has no data to send to the base station and the size of the authorized data authorized by the base station to the user terminal has not been used up, the user terminal sends to the base station to indicate that the user terminal has no data to send to the base station and the base station is authorized to When the user terminal's authorized data size has not been used up, the uplink skip notification is performed. The base station verifies the uplink skip notification. When the verification succeeds, it is determined that the user terminal is not sending data to the base station and the base station authorizes the user terminal When the authorized data size of the base station has not been used up, the base station prevents the user terminal from requesting retransmission, so that the base station does not repeatedly request the user terminal to retransmit data, thereby saving the resources of the base station and improving the utilization efficiency of the network resources by the base station.

Other characteristics and advantages of the present disclosure will become apparent through the following detailed description, or partly learned through the practice of the present disclosure.

It should be understood that the above general description and the following detailed description are only exemplary and cannot limit the present disclosure.

Description of the drawings

By describing its exemplary embodiments in detail with reference to the accompanying drawings, the above and other objectives, features, and advantages of the present disclosure will become more apparent.

Fig. 1 shows an architecture diagram to which an uplink channel scheduling method according to an embodiment of the present disclosure is applied.

Fig. 2 shows a flowchart of an uplink channel scheduling method according to an embodiment of the present disclosure.

Fig. 3 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure.

Fig. 4 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure.

Fig. 5 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure.

Fig. 6 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure.

Fig. 7 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure.

FIG. 8 shows the LCID value table of the medium access control (MAC) control element (CE) in the uplink shared channel (UL-SCH) specified in the 3GPP protocol according to another embodiment of the present disclosure.

Fig. 9 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure.

FIG. 10 shows a schematic diagram of a medium access control (MAC) control element (CE) according to another embodiment of the present disclosure.

Fig. 11 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure.

FIG. 12 shows a schematic diagram of a medium access control (MAC) control element (CE) according to another embodiment of the present disclosure.

FIG. 13 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure.

Fig. 14 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure.

FIG. 15 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure.

FIG. 16 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure.

Fig. 17 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure.

FIG. 18 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure.

FIG. 19 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure.

Fig. 20 shows a block diagram of a base station according to an embodiment of the present disclosure.

FIG. 21 shows a block diagram of a user terminal according to an embodiment of the present disclosure.

Fig. 22 shows a hardware structure diagram of a base station or a user terminal according to an embodiment of the present disclosure.

Detailed ways

Example embodiments will now be described more fully with reference to the accompanying drawings. However, the example embodiments can be implemented in various forms, and should not be construed as being limited to the examples set forth herein; on the contrary, these example embodiments are provided so that the description of the present disclosure will be more comprehensive and complete, and the concept of the example embodiments Comprehensively communicate to those skilled in the art. The drawings are only schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the figures denote the same or similar parts, and thus their repeated description will be omitted.

Furthermore, the described features, structures or characteristics may be combined in one or more example embodiments in any suitable manner. In the following description, many specific details are provided to give a sufficient understanding of the exemplary embodiments of the present disclosure. However, those skilled in the art will realize that the technical solutions of the present disclosure can be practiced without one or more of the specific details, or other methods, components, steps, etc. can be used. In other cases, well-known structures, methods, implementations, or operations are not shown or described in detail to avoid overwhelming attention and obscure various aspects of the present disclosure.

Some of the block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in the form of software, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and/or processor devices and/or microcontroller devices.

Please refer to FIG. 1. FIG. 1 is an architecture applied by an embodiment of the present disclosure. The system architecture may include: a base station (NodeB, eNB) 11 and at least one user terminal (User Equipment, UE) 12. Among them, the base station 11 and the user terminal 12 may be connected through a wireless communication link, thereby realizing the interaction of wireless data communication. In one embodiment, the user terminal may be a walkie-talkie, a mobile phone, a tablet computer, and a mobile Internet device that supports wireless data communication through the 3GPP (The 3rd Generation Partnership Project) protocol at least. The base station is a mobile communication base station that supports communication with user terminals through the 3GPP protocol.

It should be understood that the number of user terminals 12 in FIG. 1 is merely illustrative. According to implementation needs, there may be any number of terminal devices 12.

Some technical solutions of the embodiments of the present disclosure may be specifically implemented based on the architecture shown in FIG. 1 or its modified architecture.

Referring to FIG. 2, FIG. 2 shows a flowchart of an uplink channel scheduling method according to an embodiment of the present disclosure. The embodiment of the present disclosure provides an uplink channel scheduling method on the base station side and a user terminal side Uplink channel scheduling method.

The uplink channel scheduling method on the base station side includes:

Step S230: Receive an uplink skip notification from the user terminal, the uplink skip notification is sent when the user terminal has no data to send and the authorized data size authorized to the user terminal has not been used up ；

Step S240, verify the uplink skip notification;

Step S250: If the uplink skip notification verification is successful, stop sending a retransmission request to the user terminal.

The uplink channel scheduling method on the user terminal side includes:

Step S210: Determine that the user terminal is in a situation where there is no data to send and the authorized data size authorized to the user terminal has not been used up;

Step S220: When the user terminal has no data to send and the authorized data size authorized to the user terminal has not been used up, send an uplink skip notification to the base station.

In order to show the interactive relationship between the base station and the user terminal, the above five steps are reflected in the interactive flowchart of FIG. 2.

These 5 steps are described in detail below.

In step S210, in 3G communication, when the user terminal communicates with the base station, the 3GPP protocol can be used as the communication protocol for communication. Before the user terminal sends uplink data to the base station, it needs to obtain authorization from the base station. Channel resources for sending uplink data, and the user terminal sends uplink data to the base station through the channel resources authorized by the base station.

When the base station grants channel resources to the user terminal, the scheduling mode of the user terminal selected by the base station may be one of dynamic scheduling, non-short period semi-persistent scheduling, and short period semi-persistent scheduling specified in the 3GPP protocol.

When the scheduling mode of the user terminal is dynamic scheduling, when the user terminal needs to send uplink data to the base station, in order for the user terminal to obtain channel resources authorized by the base station, the user terminal needs to actively send a request for channel resources to the base station. The request includes the user terminal The data size of the data to be sent to the base station. The base station receives the request of the user terminal, and according to the data size of the data to be sent by the user terminal to the base station in the request, determines the channel resource authorized by the user terminal and the authorized data size authorized to the user terminal to meet the needs of the user terminal to send The demand for data to the base station. After receiving the request for channel resource application sent by the user terminal, the base station sends a response to the request to the user terminal, where the response includes authorized channel resource information and authorized data size information authorized by the base station to the user terminal. The feature of dynamic scheduling is that the base station can accurately authorize corresponding channel resources for the user terminal according to the data size of the data that the user terminal needs to send.

When the scheduling mode of the user terminal is non-short-period semi-persistent scheduling, the base station actively grants channel resources to the user terminal, where the channel resources authorized by the base station to the user terminal only need to be specified once. When configuring the non-short-period semi-persistent scheduling of the user terminal, the base station will specify the communication period of the non-short-period semi-persistent scheduling. After the user terminal's non-short-period semi-persistent scheduling configuration is completed, the base station actively sends a notification to the user terminal, where the notification includes the authorized channel resource information and the authorized data size authorized by the base station to the user terminal, so that the user terminal can obtain the base station The authorized channel resource information and the authorized data size authorized by the base station to the user terminal. The base station authorizes the designated channel resource to the user terminal at the designated non-short-period semi-persistent scheduled communication cycle interval, so that the user terminal sends data to the base station through the channel resource authorized by the base station. The feature of non-short-period semi-persistent scheduling is that the base station only needs to be designated once, and the base station can periodically authorize the designated channel resources for the user terminal. In the subsequent communication process, when the user terminal sends data to the base station, there is no need Then initiate a request for channel resources to the base station, and the process is relatively simple.

When the scheduling mode of the user terminal is short-period semi-persistent scheduling, the base station also actively grants channel resources to the user terminal. Among them, the channel resources authorized by the base station to the user terminal only need to be specified once. When configuring the short-period semi-persistent scheduling of the user terminal, the base station will specify the communication period of the short-period semi-persistent scheduling. After the short-period semi-persistent scheduling configuration of the user terminal is completed, the base station actively sends a notification to the user terminal. The notification includes the authorized channel resource information and the authorized data size authorized by the base station to the user terminal, so that the user terminal can obtain the authorization of the base station. The channel resource information and the authorized data size authorized by the base station to the user terminal. The base station authorizes the designated channel resource to the user terminal at the designated short-period semi-persistent scheduled communication cycle interval, so that the user terminal sends data to the base station through the channel resource authorized by the base station. Short-period semi-persistent scheduling has the same characteristics as non-short-period semi-persistent scheduling, and the process is relatively simple. It should be noted that short-period semi-persistent scheduling is compared with the scheduling mode of non-short-period semi-persistent scheduling. The communication cycle interval specified in the scheduling mode is shorter, because the communication cycle interval is shorter, which also makes the user terminal more efficient in sending uplink data to the base station.

In one embodiment, when the scheduling mode of the user terminal is non-short-period semi-persistent scheduling or short-period semi-persistent scheduling, because during the configuration process of the scheduling mode of non-short-period semi-persistent scheduling or short-period semi-persistent scheduling, The base station can designate the size of authorized sending data authorized by the base station to the user terminal, and the base station stores the designated authorized sending data size. When the base station is actively sending a notification to the user terminal, it can add the stored specified authorized data size information to the above notification, and send the above notification to the user terminal, so that the user terminal can obtain the authorization data authorized by the base station to the user terminal size.

In one embodiment, when the scheduling mode of the user terminal is non-short-period semi-persistent scheduling or short-period semi-persistent scheduling, the base station may first obtain the historical record of the user terminal and the base station when determining the size of the authorized transmission data. All logs of communication information, and obtain the data size of the uplink data each time the user terminal sends to the base station in the history, and determine the base station authorization to the user according to the data size of the uplink data each time the user terminal sends to the base station in the history The authorized data size of the terminal. Specifically, the base station may select several multiples of the maximum value from the data size of the uplink data sent by the user terminal each time as the authorized data size, so that authorization is guaranteed at least once, which can ensure that the multiple times send data without authorization and improve efficiency. Of course, the base station can also calculate several multiples of the average data size of the uplink data sent by the user terminal each time in history, as the authorized data size, to ensure that the multiples of data sent are free of authorization and improve efficiency.

It can be seen from the foregoing that the base station can send the authorized channel resource information and the authorized data size information authorized by the base station to the user terminal to the user terminal through the above response or the above notification, and the user terminal obtains the base station authorization from the received response or notification. The authorized data size of the user terminal. When obtaining the authorized data size, the user terminal can identify the specific identification field indicating the data amount in the obtained authorized data size information, determine the authorized data size according to the identification result, and the user terminal stores the recognized authorized data size.

For the data to be sent to the base station, the user terminal needs to calculate the data size of the data to determine the data size of the data to be sent to the base station. Specifically, the data to be sent can be obtained first, and the data size of the data to be sent can be calculated according to the number of bytes of the data to be sent. For the calculated data size of the data to be sent, the data size of the data to be sent can be stored in the buffer status report (BSR), where the buffer status report (BSR) is used in the user terminal to store the data to be sent to the base station The user terminal can quickly determine the data size of the data currently to be sent to the base station according to the buffer status report (BSR).

It can be seen from the foregoing that the user terminal obtains the channel resource authorized by the base station from the received response or notification, establishes a communication channel with the base station according to the channel resource authorized by the base station, and sends the data to be sent to the base station through the communication channel. Before sending the data to be sent, the user terminal will obtain the stored authorized data size authorized by the base station to the user terminal and the data size of the data to be sent to the base station in the Buffer Status Report (BSR), and compare the two to determine Whether the size of the authorized data authorized by the base station to the user terminal can meet the data transmission requirements of the base station to be sent by the user terminal. When the size of the authorized data authorized by the base station to the user terminal is greater than the data size of the data to be sent to the base station, it means that the size of the authorized data authorized by the base station to the user terminal can meet the data transmission requirements of the user terminal to be sent to the base station. It should be noted that this disclosure only discusses the case when the size of the authorized data authorized by the base station to the user terminal is greater than the data size of the data to be sent to the base station.

When the size of the authorized data authorized by the base station to the user terminal is greater than the data size of the data to be sent to the base station, the user terminal sends the data to be sent to the base station through the communication channel. When the user terminal sends the data to be sent to the base station through the communication channel, the user terminal can monitor whether the data to be sent is completed according to the data size of the data to be sent to the base station stored in the buffer status report (BSR) to determine Whether the user terminal is in a situation where no data is sent to the base station. The user terminal can also detect whether the user terminal is in a situation where the size of the authorized data authorized by the base station to the user terminal has not been used up according to the stored authorized data size authorized by the base station to the user terminal. When the user terminal has no data to send and the authorized data size authorized to the user terminal has not been used up, according to the provisions of the 3GPP protocol, it will automatically enter the uplink skip state. In this state, the user terminal cannot send data To the base station, thereby enabling the user terminal to reduce its own power consumption.

Referring to FIG. 3, FIG. 3 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure. In this embodiment, it is determined that the user terminal is in a state where there is no data transmission and is authorized to the user terminal. The step S210 in the case where the authorized data size has not been used up may include the following steps:

Step S2101, in response to receiving a request for establishing a communication channel from the base station, obtain and store the authorized data size from the request.

Step S2102: Obtain the size of the data to be sent and store it in the Buffer Status Report (BSR).

Step S2103: Whenever the communication channel is used to send data to the base station, the size of the data sent this time is deducted from the size of the authorized data stored, and from the buffer status report (BSR).

Step S2104: When it is detected that the size of the data to be sent in the Buffer Status Report (BSR) is 0 and the size of the authorized data stored is positive, it is determined that the user terminal is not sending data and the size of the authorized data authorized to the user terminal has not yet been sent. Used up situation.

These steps are described in detail below.

In step S2101, when a communication channel is established between the user terminal and the base station, when the scheduling mode of the user terminal is dynamic scheduling, the user terminal can establish a communication channel with the base station according to the received request from the base station to establish a communication channel. It can be seen from the foregoing that the above request for establishing a communication channel is the response sent by the base station to the user terminal after receiving the request for channel resource application sent by the user terminal.

When a communication channel is established between a user terminal and a base station, when the scheduling mode of the user terminal is non-short-period semi-persistent scheduling or short-period semi-persistent scheduling, it can be seen from the foregoing that the above-mentioned request for establishing a communication channel is the short-term After the periodic semi-persistent scheduling configuration is completed, the base station actively sends a notification to the user terminal.

After the user terminal receives the request to establish a communication channel, the user terminal obtains the channel resource information authorized by the base station from the above request, and establishes a communication channel with the base station through the channel resource information authorized by the base station, so that the data to be sent can be sent to the base station through the communication channel. Base station; In addition, the user terminal also obtains the authorized data size information authorized by the base station to the user terminal from the above request. When the user terminal determines the authorized data size authorized by the base station to the user terminal according to the obtained authorization data size information authorized by the base station, it can identify the specific identification field indicating the amount of data in the authorized data size information received from the base station According to the identification result, the authorized data size authorized by the base station to the user terminal is determined, and the user terminal stores the determined authorized data size authorized by the base station to the user terminal.

In step S2102, when the user terminal sends the data to be sent to the base station through the communication channel, in order to determine whether the data to be sent to the base station has been sent, the data size of the sent data and the data size of the data to be sent Make a comparison to determine whether the data of the data to be sent has been sent. Therefore, the user terminal needs to determine the data size of the data to be sent. Specifically, the user terminal can obtain the data to be sent, and calculate the data size of the data to be sent to the base station according to all the bytes of the data to be sent. The user terminal stores the data size of the data to be sent to the base station in the buffer status report (BSR) of the user terminal, so that the user terminal can determine the data to be sent according to the data size of the data to be sent to the base station in the buffer status report (BSR) Whether the transmission is complete.

In step S2103, when the user terminal sends data to the base station once through the communication channel, in order to determine whether the data to be sent is completed, the user terminal can first calculate the data size of the data sent each time. Specifically, the user terminal can The number of bytes of data sent each time is calculated to obtain the data size of the data sent each time; the user terminal will determine the data size of the data sent each time and deduct it from the buffer status report (BSR), thereby reporting the buffer status ( The data size information to be sent stored in the BSR is updated, so that the user terminal can quickly and accurately determine whether the data to be sent by the user terminal is completed according to the data size to be sent stored in the updated Buffer Status Report (BSR). If the user terminal detects that the size of the data to be sent in the Buffer Status Report (BSR) is 0, the user terminal determines that the data to be sent has been sent, and the user terminal is currently in a situation where there is no data to send.

When the user terminal sends data to the base station once through the communication channel, in order to determine whether the authorized data size is not yet used up, the user terminal can calculate the data size of the data sent each time. Specifically, the user terminal may The number of bytes of the data sent each time is calculated to obtain the data size of the data sent each time; the user terminal will determine the data size of the data sent each time and deduct it from the stored authorized data size, thereby calculating the stored authorized data size information The update is performed so that the user terminal can quickly and accurately determine whether the authorized data size is not used up according to the updated authorized data size information. It should be noted that the user terminal will determine the data size of each sent data to be deducted from the stored authorized data size, and the data size of each sent data will be deducted from the buffer status report (BSR) The actions are carried out simultaneously. If the user terminal detects that the size of the data to be sent in the buffer status report (BSR) is positive, the user terminal determines that the authorized data size is not yet used up.

For example, the data size of the data to be sent by the user terminal is 2MB, and the authorized data size authorized by the base station to the user terminal is 3MB. Before the user terminal sends the data to be sent to the base station, the size of the authorized data stored by the user terminal in the storage area is 3MB, the data size of the data to be sent stored in the Buffer Status Report (BSR) is 2MB.

When the user terminal sends data to the base station once through the communication channel, assuming that the data size of the data sent to the base station for the first time is 0.7MB, the user terminal will send the data size of 0.7MB this time to the stored authorized data size of 3MB. It is reduced and deducted from 2MB in the Cache Status Report (BSR). After updating the size of the stored authorized data, the stored authorized data size is 2.3MB. After updating the stored Cache Status Report (BSR), the stored authorized data is obtained The Cache Status Report (BSR) is 1.3MB. Since the size of the stored authorization data is 2.3 MB and the stored buffer status report (BSR) is 1.3 MB greater than 0, the user terminal determines that there is still data to be sent, and no uplink skip notification is generated. Assuming that the data size of the data sent to the base station for the second time is 1.3MB, the user terminal will deduct the 1.3MB of the data sent this time from the stored authorized data size of 2.3MB, and use the buffer status report (BSR) 1.3MB deduction, after updating the stored authorized data size, the stored authorized data size is 1MB, and after updating the stored cache status report (BSR), the stored cache status report (BSR) is 0. Since the size of the stored authorization data is 1MB, that is, the size of the stored authorization data is positive, and the stored buffer status report (BSR) is 0, the user terminal determines that there is currently no data transmission and the base station authorized the authorization data of the user terminal The size has not been used up.

In step S2104, when the user terminal detects that the size of the data to be sent in the buffer status report (BSR) is 0, and the size of the stored authorized data is positive, the user terminal determines that there is no data sent to the base station and the base station authorized The data size authorized to the user terminal has not been used up.

Referring to FIG. 4, FIG. 4 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure. In this embodiment, it is determined that the user terminal is in a state where there is no data transmission and is authorized to the user terminal. The step S210 in the case where the authorized data size has not been used up may include the following steps:

Step S2111, in response to receiving a request for establishing a communication channel from the base station, obtain the authorized data size from the request;

Step S2112, obtaining the size of the data to be sent;

Step S2113, if the size of the obtained authorized data is greater than the size of the data to be sent, a trigger bit is placed at the end of the data to be sent;

Step S2114: Extract the trigger bit when extracting data from the data to be sent for sending, block the sending of the trigger bit, and determine that the user terminal is in a situation where there is no data to send and the authorized data size authorized to the user terminal has not been used up.

These steps are described in detail below.

For the content of step S2111 and step S2112 in this embodiment, please refer to the content of step S2101 and step S2102 in the foregoing embodiment, respectively, and will not be repeated here.

In step S2113, when the size of the authorized data authorized by the base station to the user terminal is greater than the data size of the data to be sent to the base station, it indicates that the size of the authorized data authorized by the base station to the user terminal can meet the data transmission requirements of the user terminal to be sent to the base station.

When the user terminal sends the data to be sent to the base station through the communication channel, in order to determine whether the data to be sent has been sent, a trigger bit can be placed at the end of the data to be sent. Among them, the above trigger bit can be a specific character string, such as "12ACBAC21". Its function is that when the user terminal extracts the data to be sent for transmission, if the trigger bit in the data to be sent is extracted, the user terminal The action of preventing the data corresponding to the trigger bit from being sent is triggered, so that the terminal device can quickly and accurately determine whether the data to be sent has been sent. Compared with the manner in which the user terminal in the foregoing embodiment determines whether the data to be sent has been sent and whether the authorized data size is not yet used up, this method does not need to calculate the data size of the sent data every time, and The data size sent each time is deducted from the authorized data size stored and the data size sent each time is deducted from the Buffer Status Report (BSR), which can significantly reduce the amount of calculation of the user terminal, thereby reducing the user terminal Due to the resources occupied by the above calculations.

In step S2114, when the user terminal sends the data to be sent to the base station, if the trigger bit in the data to be sent is extracted, the user terminal will trigger to block the data transmission corresponding to the trigger bit, thereby making the user terminal It is quickly and accurately determined that the data to be sent has been sent, so that the user terminal can determine that the user terminal is in a situation where there is no data sent to the base station and the size of the authorized sending data authorized by the base station to the user terminal has not been used up.

Referring to FIG. 5, FIG. 5 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure. In this embodiment, it is determined that the user terminal is in a state where there is no data transmission and is authorized to the user terminal. The step S210 in the case where the authorized data size has not been used up may include the following steps:

Step S2121, in response to receiving a request for establishing a communication channel from the base station, obtain the authorized data size from the request.

Step S2122: Obtain the size of the data to be sent.

Step S2123: If the size of the obtained authorized data is greater than the size of the data to be sent, determine the size of the data to be sent based on the size of the data to be sent, the size of the data sent to the base station in each communication, and the time interval between two adjacent transmissions. Send duration.

Step S2124: Set a timer based on the sending duration.

Step S2125: Send the data to be sent.

Step S2126: When the timer expires, it is determined that the user terminal is in a situation where there is no data to send and the authorized data size authorized to the user terminal has not been used up.

These steps are described in detail below.

For the content of step S2121 and step S2122 in this embodiment, please refer to the content of step S2101 and step S2102 in the foregoing embodiment, respectively, which will not be repeated here.

In step S2123, when the size of the authorized data authorized by the base station to the user terminal is greater than the data size of the data to be sent to the base station, it indicates that the authorized data size authorized by the base station to the user terminal can meet the data sending requirements of the user terminal to the base station.

Because when the user terminal sends the data to be sent to the base station, the data to be sent can be sent to the base station in a manner of multiple sending by using data of a specified data size at a specified time interval. Therefore, when the user terminal sends the data to be sent to the base station through the communication channel, in order to determine whether the data to be sent is completed, the user terminal obtains the data size of the data to be sent, and the data size that the user terminal sends to the base station for each communication. , The time interval between two adjacent transmissions to determine the transmission duration of the data to be sent by the user terminal. Among them, when the user terminal determines the data size sent to the base station in each communication, it can specifically calculate the data size of the data sent each time according to the number of bytes of data sent to the base station by the communication. For example, the data size of the data to be sent is 4MB, the data size that the user terminal sends to the base station for each communication is 0.8MB, and the time interval between two adjacent transmissions is 0.05ms, which can determine the user terminal to send The sending duration of the data is 0.2ms.

In step S2124, when determining whether the data to be sent is completed, the user terminal can set a timer according to the sending duration of the data to be sent, so that the timer time is consistent with the sending duration of the data to be sent. When the user terminal starts sending data to the base station for the first time, a timer is started. When the timer expires, and the sending duration of the data to be sent has just passed, the user terminal determines that the data to be sent has been sent. Compared with the method of setting a trigger bit in the data to be sent in the foregoing embodiment, this method does not need to modify the data to be sent, and directly uses the existing timer of the user terminal to quickly and accurately determine the data to be sent. Whether the data is sent is completed, reducing unnecessary data processing.

In step S2125, when the user terminal sends the data to be sent to the base station through the communication channel, the time of the timer changes accordingly.

In step S2126, when the timer expires, the user terminal determines that the transmission of the data to be sent is completed, and the user terminal is in a situation where no data is sent to the base station and the authorized transmission data size authorized by the base station to the user terminal has not been used up.

Please also continue to refer to Figure 2. In step S220, since the base station cannot obtain that the user terminal is in a situation where no data is sent to the base station and the authorized data size authorized by the base station to the user terminal has not been used up, the base station will request a retransmission from the user terminal. This will cause waste of base station resources. When the user terminal has no data to send and the authorized data size authorized to the user terminal has not been used up, it will generate an uplink skip notification, where the above uplink skip notification is an agreement between the user terminal and the base station. A type of notification information that indicates that the user terminal has no data to send to the base station and the size of the authorized data authorized by the base station to the user terminal has not been used up. The user terminal sends the generated uplink skip notification to the base station to notify the base station that the user terminal has no data to transmit and the authorized data size authorized to the user terminal has not been used up.

In step S230, when the user terminal has no data to send to the base station and the size of the authorized data authorized by the base station to the user terminal has not been used up, the user terminal generates the above-mentioned uplink skip notification and sends the generated uplink skip notification. The notification is sent to the base station, and the base station receives the uplink skip notification from the user terminal.

In step S240, when the base station receives the uplink skip notification from the user terminal, the base station needs to verify the uplink skip notification from the user terminal to confirm whether the uplink skip notification from the user terminal is The notification information agreed by the base station and the user terminal to indicate that the user terminal is in a situation where no data is sent to the base station and the authorized data size authorized by the base station to the user terminal has not been used up.

If the base station verifies that the uplink skip notification is the agreed notification information indicating that the user terminal is in a situation where no data is sent to the base station and the authorized data size authorized by the base station to the user terminal has not yet been used up, the base station responds to the uplink The skip notification verification is successful, and the base station confirms that the user terminal is currently in a situation where there is no data sent to the base station and the authorized data size authorized by the base station to the user terminal has not been used up; otherwise, the base station fails to verify the uplink skip notification, and the base station It is confirmed that the user terminal is not currently in a situation where no data is sent to the base station and the authorized data size authorized by the base station to the user terminal has not been used up. The base station can ensure the authenticity and validity of the uplink skip notification by verifying the foregoing uplink skip notification.

Referring to FIG. 6, FIG. 6 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure. In this embodiment, the step S240 of the base station verifying the uplink skip notification includes :

Step S2401: If a dedicated message is used between the base station and the user terminal to verify the uplink skip notification, then identify whether the specific identification field in the dedicated message carries a specific identification, and if it does, verify The uplink skip notification is successful.

In step S2401, when the base station and the user terminal agree on an uplink skip notification that indicates that there is no data to send and the authorized data size authorized to the user terminal has not been used up, they may agree to adopt some kind of protocol other than the 3GPP protocol. The dedicated message serves as an uplink skip notification indicating that the user terminal is in a situation where there is no data to send and the authorized data size granted to the user terminal has not been used up. Specifically, the base station and the user terminal may agree to set a specific identifier in the specific identifier field in the dedicated message, so that the base station can verify the dedicated message. The base station and the user terminal use the above-mentioned dedicated message as the uplink skip notification, even if there are criminals maliciously intercepting the above-mentioned dedicated message, because the above-mentioned dedicated message is a communication message outside the 3GPP protocol and is an agreed communication between the base station and the user terminal Therefore, even if third-party criminals maliciously intercept the above-mentioned dedicated message, they cannot identify or forge the information, thereby improving the security of communication between the base station and the user terminal.

When the user terminal is in a situation where there is no data to send to the base station and the size of the authorized sending data authorized by the base station to the user terminal has not been used up, the user terminal generates an agreed dedicated message and sends the above dedicated message to the base station. After receiving the above-mentioned dedicated message, the base station checks the above-mentioned dedicated message. During the check, the base station determines whether a specific identifier is included in the specific identifier field in the dedicated message. If the specific identifier field in the above-mentioned dedicated message contains a specific identifier, the base station will notify the above-mentioned dedicated message as an uplink skip notification that the verification is successful; otherwise, the base station will notify the above-mentioned dedicated message as an uplink skip notification that the verification has failed. The base station can ensure the authenticity and validity of the above-mentioned uplink skip notification by verifying the above-mentioned dedicated message.

Referring to FIG. 7, FIG. 7 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure. In this embodiment, the step S240 of the base station verifying the uplink skip notification includes :

Step S2411, if a medium access control (MAC) control element (CE) is used as the uplink skip notification between the base station and the user terminal, and a specific medium access control (MAC) control element (CE) is used The specific reserved value on the field indicates that the uplink is skipped, and it is determined whether the specific reserved value is on the specific field.

Step S2412, if the specific reserved value is present on the specific field, verify that the uplink skip notification is successful.

These steps are described in detail below.

In step S2411, when the base station and the user terminal agree to use the uplink skip notification indicating that the user terminal is in a situation where there is no data to send and the authorized data size authorized to the user terminal has not been used up, they can agree to adopt the 3GPP protocol A certain medium access control (MAC) control element (CE) serves as an uplink skip notification.

Refer to Figure 8. Figure 8 is a table of LCID values of medium access control (MAC) control elements (CE) in the uplink shared channel (UL-SCH) specified in the 3GPP protocol. In this embodiment, the base station and the user terminal agree to use a medium access control (MAC) control element (CE) with an LCID value of 01100-10100 in a specific reserved field in the 3GPP protocol as an uplink skip notification. For example, it may be agreed to use a medium access control (MAC) control element (CE) of a specific reserved field with an LCID value of 10100 as the uplink skip notification. By adopting the medium access control (MAC) control element (CE) as the uplink skip notification, only the medium access control (MAC) control of a specific reserved field with the LCID value of 01100-10100 in the 3GPP protocol is required The element (CE) is specified, that is, minor modifications to the existing 3GPP protocol are required, so that there is no need to establish an additional communication mechanism specifically for sending uplink skip notifications, thereby reducing unnecessary workload.

Therefore, when the user terminal is in a situation where no data is sent to the base station and the authorized data size authorized by the base station to the user terminal has not been used up, a medium access control (MAC) control element of a specific reserved field with an LCID value of 10100 can be generated (CE), and send the generated medium access control (MAC) control element (CE) to the base station. After the base station receives the above-mentioned medium access control (MAC) control element (CE), when checking it, it judges whether there is a specific reserved field in the above-mentioned medium access control (MAC) control element (CE). The LCID value is 10100. If the specific reserved field of the aforementioned medium access control (MAC) control element (CE) has an LCID value of 10100, the base station verifies that the aforementioned medium access control (MAC) control element (CE) is an uplink skip notification success, Otherwise, the base station verifies that the above-mentioned medium access control (MAC) control element (CE) notification is an uplink skip notification failure.

In step S2412, if the specific reserved field of the aforementioned medium access control (MAC) control element (CE) has an LCID value of 10100, the base station verifies that the aforementioned medium access control (MAC) control element (CE) is uplink The skip notification succeeded. The base station can ensure the authenticity and validity of the uplink skip notification by verifying the medium access control (MAC) control element (CE).

Referring to Figure 9, Figure 9 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure. In this embodiment, if the specific field has the specific reserved value, The step S2412 of the base station verifying the success of the uplink skip notification may include the following steps:

Step S24121, if the specific reserved value exists on the specific field, determine whether the message body of the medium access control (MAC) control element (CE) carries a specific message body value.

Step S24122: If the message body of the medium access control (MAC) control element (CE) carries a specific message body value, verify that the uplink skip notification is successful.

In step S24121, when the base station and the user terminal agree to adopt a certain medium access control (MAC) control element (CE) in the existing 3GPP protocol as the uplink skip notification, in order to improve the verification of the uplink skip To notify the accuracy of verification, the base station and the user terminal agree to use the medium access control (MAC) control element (CE) with a specific reserved field in the 3GPP protocol with an LCID value of 01100-10100 as an uplink skip notification , The base station and the user terminal may also agree to carry a specific message body value in the message body of the medium access control (MAC) control element (CE).

Refer to FIG. 10, which is a schematic diagram of a medium access control (MAC) control element (CE) in this embodiment. It can be seen from the figure that a specific reserved field of the medium access control (MAC) control element (CE) It has an LCID value of 10100, and the specific message body value carried in the message body of the media access control (MAC) control element (CE) is 0.

Therefore, when the base station verifies the medium access control (MAC) control element (CE), if the specific reserved field of the medium access control (MAC) control element (CE) has an LCID value of 10100, the base station also It is necessary to determine whether the message body of the media access control (MAC) control element (CE) carries a specific message body value, that is, whether the value of the specific message body carried in the message body is 0. If the value of the specific message body carried in the message body is 0, the base station verifies that the above-mentioned medium access control (MAC) control element (CE) is successful in the uplink skip notification; otherwise, the base station verifies the above-mentioned medium access control (MAC) The control element (CE) is an uplink skip notification failure. By checking whether the message body of the medium access control (MAC) control element (CE) carries a specific message body value, the accuracy of verifying the uplink skip notification can be further improved.

In step S24122, if the value of the specific message body carried in the message body is 0, the base station verifies that the above-mentioned medium access control (MAC) control element (CE) is an uplink skip notification success.

Referring to FIG. 11, FIG. 11 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure. In this embodiment, the step S240 of the base station verifying the uplink skip notification includes :

Step S2421: If a medium access control (MAC) control element (CE) is used as the uplink skip notification between the base station and the user terminal, and a specific medium access control (MAC) control element (CE) is used The value of the short period buffer status report (BSR) on the field indicates that the uplink is skipped, and it is determined whether the specific field of the medium access control (MAC) control element (CE) has a short period buffer status report (BSR). ) Value.

Step S2422: If the specific field of the medium access control (MAC) control element (CE) has a value representing the short-period buffer status report (BSR), obtain the last time that the user terminal has received a specific field from the user terminal. Indicates the time for the value of the short-period buffer status report (BSR).

Step S2423: If the difference between the current time and the acquired time is not equal to a multiple of the predetermined buffer status report (BSR) interval, the uplink skips to notify that the verification is successful.

In step S2421, when the base station and the user terminal agree on the uplink skip notification that indicates that the user terminal is in a situation where there is no data to send and the authorized data size authorized to the user terminal has not been used up, they can agree to adopt the 3GPP protocol. Some media access control (MAC) control elements (CE) are used as uplink skip notifications.

Please also continue to refer to Figure 8. Figure 8 is the LCID value table of the medium access control (MAC) control element (CE) in the uplink shared channel (UL-SCH) specified in the 3GPP protocol. In this embodiment, it can be agreed The value of the short-period buffer status report (BSR) on the specific field of the medium access control (MAC) control element (CE) is used to indicate that the uplink is skipped. It can be seen from Figure 8 that the short-period buffer on the specific field The value of the status report (BSR) is specifically 11101. In this embodiment, the value of the short-period buffer status report (BSR) on the specific field of the medium access control (MAC) control element (CE) is used to indicate the way to skip the uplink. It only needs to use the 3GPP protocol The medium access control (MAC) control element (CE) is sufficient, there is no need to modify the existing 3GPP protocol, and there is no need to establish an additional communication mechanism specifically for sending uplink skip notifications, which can greatly reduce The workload of the developer.

When the user terminal is in a situation where no data is sent to the base station and the size of the authorized data authorized by the base station to the user terminal has not been used up, the short-period buffer can be generated on the specific field of the above-mentioned medium access control (MAC) control element (CE) The status report (BSR) information is used as an uplink skip notification, that is, the LCID value on the specific field of the above-mentioned medium access control (MAC) control element (CE) is 11101. The user terminal sends the generated medium access control (MAC) control element (CE) to the base station. After the base station receives the above-mentioned medium access control (MAC) control element (CE), when checking it, it judges whether the medium access control (MAC) control element (CE) has a short-period buffer status report (BSR). ), that is, check whether the LCID value on the specific field of the media access control (MAC) control element (CE) is 11101. If the LCID value on the specific field in the medium access control (MAC) control element (CE) is 11101, the base station determines that the above-mentioned medium access control (MAC) control element (CE) represents a short period buffer status report (BSR).

In step S2422, when the base station determines that the aforementioned medium access control (MAC) control element (CE) represents a short-period buffer status report (BSR), since the base station cannot distinguish the aforementioned short-period buffer status report (BSR), it means that the user terminal is in The periodic interval of the short-period buffer status report (BSR) is the regular short-period buffer status report (BSR) sent to the base station, or the short-period buffer status report (BSR) indicating the uplink skip notification.

As a result, the base station will obtain the last time it received the short-period buffer status report (BSR) from the user terminal, calculate the difference between the obtained last time and the current time, and report the difference with the buffer status (BSR) The multiples of the period interval are compared. If the difference is not equal to a multiple of the buffer status report (BSR) period interval, then the short-period buffer status report (BSR) currently received indicates the uplink skip notification; if the difference is equal to the buffer status report (BSR) The multiple of the period interval, then it means that the currently received short-period buffer status report (BSR) represents a regular short-period buffer status report (BSR).

In step S2423, if the difference is not equal to a multiple of the buffer status report (BSR) period interval, the base station determines that the currently received short-period buffer status report (BSR) represents an uplink skip notification.

Referring to FIG. 12, FIG. 12 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure. In this embodiment, the medium access control (MAC) control element (CE) The specific field of has a value representing the short-period buffer status report (BSR), and the step S2422 of obtaining the time when the value representing the short-period buffer status report (BSR) on the specific field from the user terminal is received last time, includes :

Step S24221, if the specific field of the medium access control (MAC) control element (CE) has a value indicating the short-period buffer status report (BSR), determine the value of the medium access control (MAC) control element (CE) Whether the message body carries a specific message body value.

Step S24222: If the message body of the medium access control (MAC) control element (CE) carries a specific message body value, obtain the last received report from the user terminal that indicates the short-period buffer status in the specific field. (BSR) value time.

In step S24221, when the base station and the user terminal agree to adopt the medium access control (MAC) control element (CE) representing the short-period buffer status report (BSR) as the uplink skip notification, in order to improve the verification of the short-period buffer status The accuracy of the report (BSR) can be agreed to carry a specific message body value in the message body of the medium access control (MAC) control element (CE) representing the short-period buffer status report (BSR).

Referring to FIG. 13, FIG. 13 is a schematic diagram of a medium access control (MAC) control element (CE) in this embodiment. It can be seen from the figure that a specific reserved field of the medium access control (MAC) control element (CE) It has an LCID value of 11101, and the specific message body value carried in the message body of the media access control (MAC) control element (CE) is BS=0.

Therefore, when the base station verifies the media access control (MAC) control element (CE), if the specific field in the media access control (MAC) control element (CE) has an LCID value of 11101, the base station also needs Determine whether the message body of the media access control (MAC) control element (CE) carries a specific message body value, that is, determine whether the specific message body value carried in the message body of the media access control (MAC) control element (CE) is BS= 0. If the specific message body value carried in the message body of the media access control (MAC) control element (CE) is BS=0, the base station verifies that the media access control (MAC) control element (CE) is a short-period buffer status report ( The BSR is successful; otherwise, the base station verifies that the medium access control (MAC) control element (CE) indicates that the short-period buffer status report (BSR) has failed. By checking whether the message body of the medium access control (MAC) control element (CE) carries a specific message body value, the accuracy of verifying the uplink skip notification can be further improved.

In step S24222, if the message body of the medium access control (MAC) control element (CE) carries a specific message body value, the base station verifies that the medium access control (MAC) control element (CE) is a short-period buffer status report (BSR) Success.

Please also continue to refer to FIG. 2. In step S250, when the base station sends an uplink skip notification from the user terminal and the authentication succeeds, the base station can determine that the current user terminal is not sending data to the base station but the base station authorizes the authorization data to the user terminal. The size has not been used up. Therefore, the base station can prevent the retransmission request from being sent to the user terminal without instructing the user terminal to retransmit the uplink data through the retransmission request to the user terminal. Compared with the prior art, the user terminal does not send an uplink skip notification to the base station when no data is sent to the base station and the size of the authorized data authorized by the base station to the user terminal has not been used up. When the base station determines that the user terminal has no data sent to the base station and the authorized data size authorized by the base station to the user terminal has not been used up, the base station prevents the user terminal from requesting retransmission, that is, prevents the user terminal from sending adaptive retransmission or non-adaptive The retransmission prevents the base station from repeatedly requesting the user terminal to retransmit data, thereby saving the resources of the base station and improving the utilization efficiency of the network resources by the base station.

Referring to FIG. 14, FIG. 14 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure. In this embodiment, if the uplink skip notification is successfully verified, the user is prevented from reporting Step S250 in which the terminal sends a retransmission request includes:

Step S2501, if the uplink skip notification is successfully verified, monitor the data on the channel authorized for the user terminal in the next communication cycle;

Step S2502, if the data on the channel authorized for the user terminal cannot be monitored in the next communication cycle, stop sending a retransmission request to the user terminal.

These steps are described in detail below.

In step S2501, when the user terminal sends data to the base station through the communication channel established with the base station, it sends data to the base station within a certain communication period. When the base station successfully authenticates the uplink skip notification from the user terminal, in order to more accurately determine that the user terminal is in a situation where there is no data to send to the base station and the authorized transmission data size authorized by the base station to the user terminal has not been used up, the base station can also In the next communication cycle, it is monitored whether the base station receives data on the channel authorized for the user terminal. If the base station cannot monitor the data on the channel authorized for the user terminal in the next communication cycle, the base station determines that the user terminal is in a situation where no data is sent to the base station and the authorized transmission data size authorized by the base station to the user terminal has not been used up. ; Otherwise, the base station determines that the user terminal still has data to send to the base station. This enables the base station to accurately determine that the user terminal is not sending data to the base station and the base station authorizes the user when the mechanism for verifying the uplink skip notification is invalid or the result of the base station verifying the uplink skip notification is incorrect. The situation that the authorized sending data size of the terminal has not been used up can greatly improve the accuracy of verifying that the user terminal has no data to send to the base station and the authorized sending data size authorized to the user terminal by the base station has not been used up yet.

In step S2502, if the base station cannot monitor the data on the channel authorized for the user terminal in the next communication cycle, the base station determines that the user terminal is not sending data to the base station and the base station authorized the user terminal to send the authorized data size has not been used. The end of the situation. The base station prevents sending a retransmission request to the user terminal, thereby saving resources in the base station.

Referring to FIG. 15, FIG. 15 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure. In this embodiment, if the scheduling mode of the user terminal is non-short period semi-persistent scheduling, If the uplink skip notification verification is successful, after step S250 of preventing the retransmission request from being sent to the user terminal, the method includes:

Step S260: Send an implicit deactivation request for releasing the uplink semi-persistent scheduling (SPS) channel and scrambling resources to the user terminal.

In step S260, if the scheduling mode of the user terminal is non-short-period semi-persistent scheduling, the channel resources authorized by the base station include the hardware resources corresponding to the uplink semi-persistent scheduling (SPS) channel and the soft resources required by the base station to establish a communication channel with the user terminal. For example, scrambling resources. Therefore, when the base station determines that the user terminal is in a situation where no data is sent to the base station and the authorized transmission data size authorized by the base station to the user terminal has not been used up, the base station will release the uplink semi-persistent scheduling (SPS) channel corresponding to the user terminal in time. The hardware resources of the base station and the soft resources required to establish a communication channel between the base station and the user terminal save the resources of the base station. When the base station determines that the user terminal is in a situation where there is no data to send to the base station and the size of the authorized transmission data authorized by the base station to the user terminal has not been used up, the base station sends the user terminal an implicit release to release the uplink semi-persistent scheduling (SPS) channel and scrambling resources. Activation request, the base station sends the generated implicit deactivation request to release the uplink semi-persistent scheduling (SPS) channel and scrambled resources to the user terminal, so that the user terminal also releases the uplink semi-persistent scheduling (SPS) channel with the base station in time Corresponding hardware resources and soft resources required by the user terminal to establish a communication channel with the base station.

Referring to FIG. 16, FIG. 16 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure. In this embodiment, if the scheduling mode of the user terminal is non-short period semi-persistent scheduling, If the uplink skip notification verification is successful, after step 250 of preventing the retransmission request from being sent to the user terminal, the method further includes:

Step S261: Send a hybrid automatic repeat request (HARQ) channel release command for releasing an uplink hybrid automatic repeat request (HARQ) channel with the user terminal to the user terminal.

In step S261, if the scheduling mode of the user terminal is non-short-period semi-persistent scheduling, the channel resources authorized by the base station also include hardware resources corresponding to the uplink hybrid automatic repeat request (HARQ) channel of the user terminal. Therefore, when the base station determines that the user terminal is in a situation where there is no data to send to the base station and the authorized transmission data size authorized by the base station to the user terminal has not been used up, the base station does not need to send the uplink hybrid automatic repeat request (HARQ) to the user terminal. The terminal requests the user terminal to retransmit the data, and the base station will release the hardware resources corresponding to the uplink hybrid automatic repeat request (HARQ) channel of the user terminal in time, thereby saving the resources of the base station. The base station sends to the user terminal a hybrid automatic repeat request (HARQ) channel release command for releasing the uplink hybrid automatic repeat request (HARQ) channel with the user terminal, so that the user terminal can also release the uplink hybrid automatic repeat request (HARQ) channel with the base station in time. The hardware resource corresponding to the HARQ channel.

Referring to FIG. 17, FIG. 17 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure. In this embodiment, if the scheduling mode of the user terminal is short-period semi-persistent scheduling, if After the uplink skip notification verification succeeds and prevents sending a retransmission request to the user terminal step S250, the method further includes:

Step S262, waiting for the end of the current short period;

Step S263, sending the explicit deactivation request for releasing the uplink semi-persistent scheduling (SPS) channel and scrambling resources to the user terminal;

Step S264: Receive the user terminal's response to the explicit deactivation request for releasing the uplink semi-persistent scheduling (SPS) channel and the scrambled resource.

These steps are described in detail below.

In step S262, if the scheduling mode of the user terminal is short-period semi-persistent scheduling, the channel resources authorized by the base station include the hardware resources corresponding to the uplink semi-persistent scheduling (SPS) channel and the soft resources required for the base station to establish a communication channel with the user terminal. For example, scrambling resources. Therefore, when the base station determines that the user terminal is not sending data to the base station and the authorized transmission data size authorized by the base station to the user terminal has not been used up, the base station can choose to wait for the end of the current short period and then release the uplink semi-persistent scheduling ( The hardware resources corresponding to the SPS) channel and the soft resources required by the base station and the user terminal to establish a communication channel. Waiting for the end of the current short period can prevent the base station from suddenly releasing the channel resources required to establish a communication channel between the base station and the user terminal, which will affect the communication stability of the base station.

In step S263, when the base station determines that the user terminal is in a situation where no data is sent to the base station and the size of the authorized transmission data authorized by the base station to the user terminal has not been used up, the base station generates an indication to release the uplink semi-persistent scheduling (SPS) channel and scrambling resources. The base station sends the generated explicit deactivation request to release the uplink semi-persistent scheduling (SPS) channel and scrambled resources to the user terminal.

In step S264, after receiving an explicit deactivation request to release the uplink semi-persistent scheduling (SPS) channel and scrambling resources, the base station releases the hardware resources corresponding to the uplink semi-persistent scheduling (SPS) channel of the base station and the While establishing the soft resources required by the communication channel, the base station sends to the base station a response to the explicit deactivation request to release the uplink semi-persistent scheduling (SPS) channel and scrambled resources, so that the base station confirms that the user terminal has received the request from the base station. Release the explicit deactivation request of the uplink semi-persistent scheduling (SPS) channel and scrambling resources.

Referring to FIG. 18, FIG. 18 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure. In this embodiment, if the scheduling mode of the user terminal is non-short period semi-persistent scheduling, If the uplink skip notification verification is successful, after step 250 of preventing the retransmission request from being sent to the user terminal, the method further includes:

Step S265: Send a hybrid automatic repeat request (HARQ) channel release command for releasing an uplink hybrid automatic repeat request (HARQ) channel with the user terminal to the user terminal.

If the scheduling mode of the user terminal is short-period semi-persistent scheduling, the channel resources authorized by the base station also include hardware resources corresponding to the uplink hybrid automatic repeat request (HARQ) channel of the user terminal. Therefore, when the base station determines that the user terminal is in a situation where there is no data to send to the base station and the authorized transmission data size authorized by the base station to the user terminal has not been used up, the base station does not need to send the uplink hybrid automatic repeat request (HARQ) to the user terminal. The terminal requests the user terminal to retransmit the data, and the base station will release the hardware resources corresponding to the uplink hybrid automatic repeat request (HARQ) channel of the user terminal in time, thereby saving the resources of the base station. The base station sends to the user terminal a hybrid automatic repeat request (HARQ) channel release command for releasing the uplink hybrid automatic repeat request (HARQ) channel with the user terminal, so that the user terminal can also release the uplink hybrid automatic repeat request (HARQ) channel with the base station in time. The hardware resource corresponding to the HARQ channel.

Referring to FIG. 19, FIG. 19 shows a flowchart of an uplink channel scheduling method according to another embodiment of the present disclosure. In this embodiment, if the scheduling mode of the user terminal is dynamic scheduling, when the user terminal is in no data When the size of the authorized data sent and authorized to the user terminal has not been used up, after step S220 of sending the uplink skip notification to the base station, the method further includes:

Step S270: Release the uplink hybrid automatic repeat request (HARQ) channel with the base station.

If the scheduling mode of the user terminal is dynamic scheduling, the resources for establishing a communication channel between the user terminal and the base station include hardware resources corresponding to the uplink hybrid automatic repeat request (HARQ) channel of the base station. When the user terminal is in a situation where there is no data to send to the base station and the size of the authorized transmission data authorized by the base station to the user terminal has not been used up, the user terminal releases the hardware resources corresponding to the uplink hybrid automatic repeat request (HARQ) channel of the base station, Thus, resources in the user terminal can be saved.

Please also continue to refer to FIG. 15. In one embodiment, if the scheduling mode of the user terminal is non-short-period semi-static scheduling, there is no data transmission in the user terminal and the authorized data size authorized to the user terminal has not been used up. In the case of sending an uplink skip notification to the base station after step S220, the method includes:

Step S271, receiving an implicit deactivation request for releasing uplink semi-persistent scheduling (SPS) channel and scrambling resources from the base station;

Step S272: Release the uplink semi-persistent scheduling (SPS) channel and scrambling resources.

Step S271: If the scheduling mode of the user terminal is non-short-period semi-persistent scheduling, the base station generates a release uplink half when determining that the user terminal is in a situation where there is no data to send to the base station and the authorized transmission data size authorized by the base station to the user terminal has not been used up. Implicit deactivation request for static scheduling (SPS) channel and scrambled resources, the base station sends the generated implicit deactivation request for releasing uplink semi-persistent scheduling (SPS) channel and scrambled resources to the user terminal, so as to inform the user The terminal can perform the operation of releasing the hardware resources corresponding to the uplink semi-persistent scheduling (SPS) channel of the base station and the soft resources required to establish the communication channel with the base station.

Step S272: After receiving the implicit deactivation request for releasing the uplink semi-persistent scheduling (SPS) channel and scrambling resources, the user terminal determines that it can currently release the uplink semi-persistent scheduling (SPS) channel corresponding to the base station. The hardware resources and the soft resources required to establish a communication channel with the base station can save resources in the user terminal.

Please also continue to refer to FIG. 16. In one embodiment, if the scheduling mode of the user terminal is non-short-period semi-static scheduling, there is no data transmission in the user terminal and the authorized data size authorized to the user terminal has not been used up yet In the case, after step S220 of sending the uplink skip notification to the base station, the method further includes:

Step S273: Receive a hybrid automatic repeat request (HARQ) channel release command for releasing an uplink hybrid automatic repeat request (HARQ) channel with the user terminal from the base station;

Step S274: Release the uplink hybrid automatic repeat request (HARQ) channel with the base station.

In step S273, if the scheduling mode of the user terminal is non-short-period semi-persistent scheduling, the channel resources authorized by the base station also include hardware resources corresponding to the uplink hybrid automatic repeat request (HARQ) channel of the user terminal. Therefore, when the base station determines that the user terminal is in a situation where there is no data to send to the base station and the authorized transmission data size authorized by the base station to the user terminal has not been used up, it also generates a hybrid automatic repeat request (HARQ) channel release command, and the base station will generate The hybrid automatic repeat request (HARQ) channel release command is sent to the user terminal to inform the user terminal that it can release the hardware resources corresponding to the uplink hybrid automatic repeat request (HARQ) channel of the base station.

In step S274, after receiving the HARQ channel release command, the user terminal determines that the hardware resources corresponding to the uplink hybrid automatic repeat request (HARQ) channel of the base station can be released, thereby saving the user terminal Resources in.

Please also continue to refer to FIG. 17. In one embodiment, if the scheduling mode of the user terminal is short-period semi-persistent scheduling, when the user terminal is in no data transmission and the authorized data size authorized to the user terminal has not been used up In this case, after step S220 of sending the uplink skip notification to the base station, the method includes:

Step S275, receiving an implicit deactivation request for releasing uplink semi-persistent scheduling (SPS) channel and scrambling resources from the base station;

Step S276: Send the user terminal's response to the explicit deactivation request to release the uplink semi-persistent scheduling (SPS) channel and scrambled resources to the base station;

Step S277: Release the uplink semi-persistent scheduling (SPS) channel and scrambling resources.

In step S275, if the scheduling mode of the user terminal is short-period semi-persistent scheduling, the channel resources authorized by the base station include the hardware resources corresponding to the uplink semi-persistent scheduling (SPS) channel and the soft resources required by the base station to establish a communication channel with the user terminal. For example, scrambling resources. Therefore, when the base station determines that the user terminal is not sending data to the base station and the authorized transmission data size authorized by the base station to the user terminal has not been used up, the base station can choose to wait for the end of the current short period and then release the uplink semi-persistent scheduling ( The hardware resources corresponding to the SPS) channel and the soft resources required by the base station and the user terminal to establish a communication channel. Waiting for the end of the current short period can prevent the base station from suddenly releasing the channel resources required to establish a communication channel between the base station and the user terminal, which will affect the communication stability of the base station.

The base station generates an explicit deactivation request to release the uplink semi-persistent scheduling (SPS) channel and scrambling resources when determining that the user terminal is in a situation where there is no data to send to the base station and the size of the authorized transmission data authorized by the base station to the user terminal has not been used up, The base station sends the generated explicit deactivation request to release the uplink semi-persistent scheduling (SPS) channel and scrambled resources to the user terminal, so as to inform the user terminal that it can release the uplink semi-persistent scheduling (SPS) channel corresponding to the base station The operation of the hardware resources and the soft resources required by the user terminal to establish a communication channel with the base station.

In step S276, after receiving an explicit deactivation request to release the uplink semi-persistent scheduling (SPS) channel and scrambled resources, the user terminal sends an explicit deactivation request for releasing the uplink semi-persistent scheduling (SPS) channel and scrambled resources to the base station. A response to the type deactivation request, so that the base station confirms that the user terminal has received an explicit deactivation request from the base station to release the uplink semi-persistent scheduling (SPS) channel and scrambled resources.

In step S277, after receiving the explicit deactivation request to release the uplink semi-persistent scheduling (SPS) channel and scrambling resources, the user terminal determines that the current uplink semi-persistent scheduling (SPS) channel corresponding to the base station can be released. The hardware resources and the soft resources required to establish a communication channel with the base station can save resources in the user terminal.

Please also continue to refer to FIG. 18, if the scheduling mode of the user terminal is short-period semi-persistent scheduling, when the user terminal is in no data transmission and the authorized data size authorized to the user terminal has not been used up, send to the base station After step S220 of the uplink skip notification, the method further includes:

Step S278, receiving a hybrid automatic repeat request (HARQ) channel release command for releasing an uplink hybrid automatic repeat request (HARQ) channel with the user terminal from the base station;

Step S279: Release the uplink hybrid automatic repeat request (HARQ) channel with the base station.

In step S278, if the scheduling mode of the user terminal is short-period semi-persistent scheduling, the channel resources authorized by the base station also include hardware resources corresponding to the uplink hybrid automatic repeat request (HARQ) channel of the user terminal. Therefore, when the base station determines that the user terminal is in a situation where there is no data to send to the base station and the authorized transmission data size authorized by the base station to the user terminal has not been used up, it also generates a hybrid automatic repeat request (HARQ) channel release command, and the base station will generate The hybrid automatic repeat request (HARQ) channel release command is sent to the user terminal to inform the user terminal that it can release the hardware resources corresponding to the uplink hybrid automatic repeat request (HARQ) channel of the base station.

In step S279, after receiving the HARQ channel release command, the user terminal determines that the hardware resources corresponding to the uplink hybrid automatic repeat request (HARQ) channel of the base station can be released, thereby saving users Resources in the terminal.

The following takes base stations and user terminals supporting the 3GPP protocol as examples to illustrate the process of the user terminal sending voice service data to the base station.

When the user terminal needs to send voice service data to the base station, because the data that the user terminal needs to send is voice service data, the service quality (Quality of Service, QoS) of the voice service data is the QoS Class Identifier (abbreviated) :QCI)=1. Therefore, in order to ensure the quality of service of the voice service data sent by the user, the scheduling mode of the user terminal is short-period semi-static scheduling, thereby meeting the voice service data transmission requirement of the user terminal.

Since the scheduling mode of the user terminal is short-period semi-persistent scheduling, the base station actively grants channel resources to the user terminal, where the channel resources authorized by the base station to the user terminal only need to be specified once. When configuring the short-period semi-persistent scheduling of the user terminal, the base station will specify the communication period interval of the short-period semi-persistent scheduling, where the specified communication period interval may be 3 ms. In the process of configuring the scheduling mode of the short-period semi-persistent scheduling, the base station can specify that the size of authorized transmission data authorized by the base station to the user terminal is 2MB, and the base station stores the specified authorized transmission data size of 2MB. After the short-period semi-persistent scheduling configuration of the user terminal is completed, the base station actively sends a notification to the user terminal. The notification includes the authorized channel resource information and the authorized data size of 2MB authorized by the base station to the user terminal, so that the user terminal can obtain the base station. The authorized channel resource information and the authorized data size authorized by the base station to the user terminal.

The user terminal establishes a communication channel with the base station based on the channel resources authorized by the base station, thereby facilitating the transmission of voice service data to the base station at an interval of 3 ms in the short-period semi-static scheduling communication cycle. In addition, the user terminal also authorizes the base station to authorize the user terminal to send data The size is 2MB for storage.

When the user terminal needs to send voice service data to the base station, it sends the voice service data to be sent to the base station through the communication channel established by the channel resources authorized by the base station. Before the user terminal sends the voice service data, the user terminal can obtain the data size of the voice service data to be sent to the base station, and calculate the data size of the voice service data to be sent according to the number of bytes of the voice service data to be sent. , The calculated voice service data is 1.5MB. For the calculated data size of the voice service data to be sent to be 1.5 MB, the user terminal stores it in the buffer status report (BSR).

When sending the voice service data to be sent to the base station, the user terminal judges that the size of the authorized data authorized by the base station to the user terminal is greater than the data size of the voice service data to be sent to the base station, because the authorized data size 2MB authorized by the base station to the user terminal is greater than the size to be sent The data size of the voice service data to the base station is 1.5 MB, which indicates that the authorized data size authorized by the base station to the user terminal can meet the data transmission requirements of the base station to be sent by the user terminal.

When the user terminal sends voice service data to the base station through the communication channel, assuming that the data size of the voice service data sent by the user terminal to the base station for the first time is 0.7MB, then the data size of 0.7MB sent this time is taken from the stored authorization data The size is deducted from 2MB, and 1.5MB is deducted from the cache status report (BSR). After updating the stored authorized data size, the stored authorized data size is 1.3MB, and the stored cache status report (BSR) is performed After the update, the stored Cache Status Report (BSR) is 0.8MB. Since the size of the stored authorization data is 1.3 MB and the stored buffer status report (BSR) is 0.8 MB greater than 0, the user terminal determines that there is still data to be sent, and no uplink skip notification is generated. Assuming that the data size of the voice service data sent by the user terminal to the base station for the second time is 0.8MB, the data size of 0.8MB sent this time is deducted from the stored authorized data size of 1.3MB, and the buffer status report (BSR ) Is reduced by 0.8MB. After updating the size of the stored authorized data, the stored authorized data size is 0.5MB. After updating the stored cache status report (BSR), the stored cache status report (BSR) is 0. Since the size of the stored authorization data is 0.5MB, that is, the size of the stored authorization data is positive, and the stored buffer status report (BSR) is 0, the user terminal determines that there is no voice service data transmission and the base station authorizes the user terminal In the case where the authorized data size of the user terminal has not been used up, the user user terminal generates an uplink skip notification in this case, where the uplink skip notification generated by the user terminal may be the LCID value shown in FIG. 8 The media access control (MAC) control element (CE) of the specific reserved field of 10100.

Wherein, the medium access control (MAC) control element (CE) of a specific reserved field with an LCID value of 10100 generated by the user terminal is sent to the base station. When the base station receives the uplink skip notification from the user terminal, the base station checks it. During the check, the base station determines whether the specific reserved field of the medium access control (MAC) control element (CE) is It has an LCID value of 10100. When it is judged that the specific reserved field of the medium access control (MAC) control element (CE) has an LCID value of 10100, it is also judged whether the data size in the message body carrying the value of the specific message body is 0 . If the size of the data carrying the specific message body value in the message body is 0, the base station verifies that the above-mentioned medium access control (MAC) control element (CE) is that the uplink skip notification is successful.

When the user terminal sends voice service data through the channel authorized by the base station to the user terminal, it is sent in the specified communication cycle. When the base station skips the uplink from the user terminal and informs that the verification is successful, in order to more accurately determine The user terminal is in a situation where no data is sent to the base station and the size of the authorized transmission data authorized by the base station to the user terminal has not been used up. The base station can monitor the voice service data on the channel authorized by the base station for the user terminal in the next communication cycle. Since the user terminal currently has no voice service data to send, the base station can not monitor the voice service data on the channel authorized by the base station for the user terminal in the next communication cycle, and the base station determines that the user terminal is in no voice service data to send to In the case where the base station has not used up the authorized data size authorized by the base station to the user terminal, the base station prevents the user terminal from sending a retransmission request. The base station can choose to wait for the end of the current short period to release the hardware resources corresponding to the base station's uplink semi-persistent scheduling (SPS) channel and the soft resources required to establish the communication channel with the base station. Because the base station does not need to send the uplink hybrid automatic to the user terminal A repeat request (HARQ) is sent to the user terminal to request the user terminal to retransmit data, and the base station also timely releases the hardware resources corresponding to the uplink hybrid automatic repeat request (HARQ) channel of the user terminal, thereby saving the resources of the base station.

Since the user terminal cannot obtain the action that the base station has released the channel resources, the base station generates an explicit deactivation request to release the uplink semi-persistent scheduling (SPS) channel and scrambling resources and a hybrid automatic repeat request (HARQ) channel release command to User terminal. The user terminal sends to the base station an explicit deactivation request to release the uplink semi-persistent scheduling (SPS) channel and scrambled resources, and a response to the hybrid automatic repeat request (HARQ) channel release command, so that the base station confirms that the user terminal has received The base station releases the information of the explicit deactivation request of the uplink semi-persistent scheduling (SPS) channel and the scrambling resource, and the hybrid automatic repeat request (HARQ) channel release command.

The user terminal releases the hardware resources corresponding to the base station's uplink semi-persistent scheduling (SPS) channel, the soft resources required to establish a communication channel with the base station, and the hardware resources corresponding to the base station's uplink hybrid automatic repeat request (HARQ) channel , Which in turn can save resources in the user terminal.

Referring to FIG. 20, according to an embodiment of the present disclosure, an uplink channel scheduling apparatus is provided in FIG. 20, wherein the uplink channel scheduling apparatus is integrated in the base station 11 in FIG. 1, and the uplink channel scheduling Devices, including:

The first receiving unit S230 is configured to receive an uplink skip notification from a user terminal, where the uplink skip notification has no data to be sent at the user terminal and the authorized data size authorized to the user terminal has not been used up In case of sending.

The verification unit S240 is configured to verify the uplink skip notification.

The first processing unit S250 is configured to prevent sending a retransmission request to the user terminal if the uplink skip notification verification is successful.

In an embodiment, the first processing unit S250 includes:

The monitoring subunit (not shown) is configured to monitor data on the channel authorized for the user terminal in the next communication cycle if the uplink skip notification is successfully verified.

The first processing subunit (not shown) is configured to prevent sending a retransmission request to the user terminal if the data on the channel authorized for the user terminal cannot be monitored in the next communication cycle.

In an embodiment, if the scheduling mode of the user terminal is non-short-period semi-persistent scheduling, the uplink channel scheduling apparatus further includes:

The first sending unit (not shown) is configured to send an implicit deactivation request for releasing the uplink semi-persistent scheduling (SPS) channel and scrambling resources to the user terminal.

In an embodiment, the uplink channel scheduling apparatus further includes:

The second sending unit (not shown) is configured to send a hybrid automatic repeat request (HARQ) channel release command for releasing an uplink hybrid automatic repeat request (HARQ) channel with the user terminal to the user terminal.

In an embodiment, if the scheduling mode of the user terminal is short-period semi-persistent scheduling, the uplink channel scheduling apparatus further includes:

Waiting unit (not shown), used to wait for the end of the current short cycle;

The third sending unit (not shown) is configured to send the explicit deactivation request for releasing the uplink semi-persistent scheduling (SPS) channel and scrambling resources to the user terminal;

The second receiving unit (not shown) is configured to receive the response of the user terminal to the explicit deactivation request for releasing the uplink semi-persistent scheduling (SPS) channel and the scrambled resource.

In an embodiment, the uplink channel scheduling apparatus further includes:

The fourth sending unit (not shown) is configured to send a hybrid automatic repeat request (HARQ) channel release command for releasing an uplink hybrid automatic repeat request (HARQ) channel with the user terminal to the user terminal.

In an embodiment, the user terminal determines through the following process that the user terminal is in a situation where there is no data to send and the authorized data size authorized to the user terminal has not been used up:

In response to receiving a request for establishing a communication channel from the base station, obtain the authorized data size from the request and store it;

Get the size of the data to be sent and store it in the Buffer Status Report (BSR);

Whenever the communication channel is used to send data to the base station once, the size of the sent data is deducted from the stored authorized data size and deducted from the buffer status report (BSR);

When it is detected that the size of the data to be sent in the Buffer Status Report (BSR) is 0 and the size of the authorized data stored is positive, it is determined that the user terminal is in a situation where there is no data to send and the authorized data size authorized to the user terminal has not been used up Happening.

In response to receiving a request for establishing a communication channel from the base station, obtaining the authorized data size from the request;

Get the size of the data to be sent;

If the size of the obtained authorized data is greater than the size of the data to be sent, place a trigger bit at the end of the data to be sent;

The trigger bit is extracted when the data is sent from the data to be sent, and the trigger bit is prevented from being sent, and the user terminal is determined to be in a situation where there is no data to send and the authorized data size authorized to the user terminal has not been used up.

Get the size of the data to be sent;

If the size of the obtained authorized data is greater than the size of the data to be sent, based on the size of the data to be sent, the size of the data sent to the base station for each communication, and the time interval between two adjacent transmissions, determine the sending of the data to be sent duration;

Based on the sending duration, setting a timer;

Send the data to be sent;

When the timer expires, it is determined that the user terminal is in a situation where no data is sent and the authorized data size authorized to the user terminal has not been used up.

In an embodiment, the verification unit S240 includes:

The first verification subunit (not shown) is used to identify whether a specific identification field in the dedicated message contains a dedicated message between the base station and the user terminal to verify the uplink skip notification The specific identifier, if included, verifies that the uplink skip notification is successful.

In an embodiment, the verification unit S240 includes:

The first judging subunit (not shown) is used for if a medium access control (MAC) control element (CE) is used as the uplink skip notification between the base station and the user terminal, and the medium access control ( MAC) a specific reserved value on a specific field of a control element (CE) to indicate to skip the uplink, and determine whether the specific reserved value is on the specific field;

The second verification subunit (not shown) is configured to verify that the uplink skip notification is successful if the specific reserved value is on the specific field.

In one embodiment, the second verification subunit includes:

The first judgment module (not shown) is used to determine whether the message body of the medium access control (MAC) control element (CE) carries a specific message body value if the specific reserved value is on the specific field ；

A verification module (not shown), configured to verify that the uplink skip notification is successful if the message body of the medium access control (MAC) control element (CE) carries a specific message body value.

In one embodiment, the second verification subunit includes:

The second judging subunit (not shown) is used for if a medium access control (MAC) control element (CE) is used as the uplink skip notification between the base station and the user terminal, and the medium access control ( The value of the short-period buffer status report (BSR) on the specific field of the MAC control element (CE) indicates that the uplink is skipped, and it is determined whether the specific field of the medium access control (MAC) control element (CE) Has a value representing the short-period buffer status report (BSR);

The acquisition subunit (not shown) is used to acquire the last received data from the user if the specific field of the medium access control (MAC) control element (CE) has a value representing the short-period buffer status report (BSR) The time that the terminal has a value representing the short-period buffer status report (BSR) in a specific field;

The third verification subunit (not shown) is used to if the difference between the current time and the acquired time is not equal to a multiple of the predetermined buffer status report (BSR) interval, the uplink skips to notify that the verification is successful.

In an embodiment, the acquiring subunit includes:

The second judgment module (not shown) is configured to determine the medium access control (MAC) control element (CE) if the specific field of the medium access control (MAC) control element (CE) has a value representing the short period buffer status report (BSR) Whether the message body of the MAC control element (CE) carries a specific message body value;

The first obtaining module (not shown) is used to obtain the specific field value of the last received message from the user terminal if the message body of the medium access control (MAC) control element (CE) carries a specific message body value There is a time indicating the value of the short cycle buffer status report (BSR).

Referring to Fig. 21, according to an embodiment of the present disclosure, Fig. 21 provides an uplink channel scheduling device, wherein the uplink channel scheduling device is integrated in the user terminal 12 in Fig. 1, and the uplink channel Scheduling devices, including:

The second processing unit S210 is configured to determine that the user terminal is in a situation where there is no data to send and the authorized data size authorized to the user terminal has not been used up;

The second receiving unit S220 is configured to send an uplink skip notification to the base station when the user terminal is not sending data and the authorized data size authorized to the user terminal has not been used up.

In an embodiment, if the scheduling mode of the user terminal is dynamic scheduling, the uplink channel scheduling apparatus further includes:

The first release unit is used to release the uplink hybrid automatic repeat request (HARQ) channel with the base station.

A third receiving unit (not shown), configured to receive an implicit deactivation request for releasing uplink semi-persistent scheduling (SPS) channels and scrambling resources from the base station;

The second release unit is used to release the uplink semi-persistent scheduling (SPS) channel and scrambling resources.

In an embodiment, the uplink channel scheduling apparatus further includes:

A fourth receiving unit (not shown), configured to receive a hybrid automatic repeat request (HARQ) channel release command for releasing an uplink hybrid automatic repeat request (HARQ) channel with the user terminal from the base station;

The third releasing unit is used to release the uplink hybrid automatic repeat request (HARQ) channel with the base station.

In an embodiment, if the scheduling mode of the user terminal is short-period semi-persistent scheduling, the uplink channel scheduling apparatus further includes;

A fifth receiving unit (not shown), configured to receive an implicit deactivation request for releasing uplink semi-persistent scheduling (SPS) channels and scrambling resources from the base station;

A fifth sending unit (not shown), configured to send the user terminal's response to the explicit deactivation request to release the uplink semi-static scheduling (SPS) channel and scrambling resources to the base station;

The fourth release unit is used to release the uplink semi-persistent scheduling (SPS) channel and scrambling resources.

In an embodiment, the uplink channel scheduling apparatus further includes:

A sixth receiving unit (not shown), configured to receive a hybrid automatic repeat request (HARQ) channel release command used to release an uplink hybrid automatic repeat request (HARQ) channel with the user terminal from the base station;

The fifth release unit is used to release the uplink hybrid automatic repeat request (HARQ) channel with the base station.

In an embodiment, the second processing unit includes:

The first storage subunit (not shown) is configured to obtain and store the authorized data size from the request in response to receiving a request for establishing a communication channel from the base station;

The second storage subunit (not shown) is used to obtain the size of the data to be sent and store it in the buffer status report (BSR);

The offset subunit (not shown) is used to send data to the base station once using the communication channel, offset the size of the data sent this time from the size of the authorized data stored, and send it from the buffer status report (BSR) ) In deduction;

The second processing subunit (not shown) is used to determine that the user terminal is in the state of no data transmission and is authorized to the user terminal when it is detected that the size of the data to be sent in the buffer status report (BSR) is 0 and the size of the authorized data stored is positive The situation where the authorized data size of the user terminal has not been used up.

In an embodiment, the second processing unit includes:

The second storage subunit (not shown) is configured to obtain the authorized data size from the request for establishing a communication channel from the base station in response to receiving the request;

The second obtaining subunit (not shown) is used to obtain the size of the data to be sent;

Place a subunit (not shown) for placing a trigger bit at the end of the data to be sent if the size of the authorized data obtained is greater than the size of the data to be sent;

The third processing subunit (not shown) is used to extract the trigger bit when the data is extracted from the data to be sent and send, prevent the trigger bit from being sent, and determine that the user terminal is in the authorization granted to the user terminal without data sending The data size has not been used up.

In an embodiment, the second processing unit includes:

The third storage subunit (not shown) is configured to, in response to receiving a request for establishing a communication channel from the base station, obtain the authorized data size from the request and store the data size to be sent;

The third obtaining subunit (not shown) is used to obtain the size of the data to be sent;

The fourth processing subunit (not shown) is used to, if the size of the obtained authorized data is greater than the size of the data to be sent, based on the size of the data to be sent, the size of the data sent to the base station for each communication, and the difference between two adjacent transmissions. The time interval between to determine the sending duration of the data to be sent;

A setting subunit (not shown) for setting a timer based on the sending duration;

The fourth acquisition subunit (not shown) is used to send the data to be sent;

The fifth processing subunit (not shown) is used to determine that the user terminal is in a situation where there is no data transmission and the authorized data size authorized to the user terminal has not been used up when the timer expires.

In one embodiment, when the timer expires, it is determined that the user terminal is in a situation where there is no data to send and the authorized data size authorized to the user terminal has not been used up.

In an embodiment, the base station verifies the uplink skip notification through the following process:

If a dedicated message is used between the base station and the user terminal to verify the uplink skip notification, then identify whether the specific identifier field in the dedicated message carries a specific identifier, and if it does, verify the uplink The link skip notification succeeded.

The uplink channel scheduling method according to the embodiment of the present disclosure may be implemented by the base station 11 or the user terminal 12 of FIG. 22. The base station 11 or the user terminal 12 according to an embodiment of the present disclosure will be described below with reference to FIG. 22. The base station 11 or the user terminal 12 shown in FIG. 22 is only an example, and should not bring any limitation to the function and use range of the embodiments of the present disclosure.

As shown in FIG. 22, the base station 11 or the user terminal 12 is represented in the form of a general-purpose computing device. The components of the base station 11 or the user terminal 12 may include, but are not limited to: the aforementioned at least one processing unit 810, the aforementioned at least one storage unit 820, and a bus 830 connecting different system components (including the storage unit 820 and the processing unit 810).

Wherein, the storage unit stores program code, and the program code can be executed by the processing unit 810, so that the processing unit 810 executes the various exemplary methods described in the description section of the exemplary method in this specification. Implementation steps. For example, the processing unit 810 may perform various steps as shown in FIG. 2.

The storage unit 820 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 8201 and/or a cache storage unit 8202, and may further include a read-only storage unit (ROM) 8203.

The storage unit 820 may also include a program/utility tool 8204 having a set (at least one) program module 8205. Such program module 8205 includes but is not limited to: an operating system, one or more application programs, other program modules, and program data, Each of these examples or some combination may include the implementation of a network environment.

The bus 830 may represent one or more of several types of bus structures, including a storage unit bus or a storage unit controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local area using any bus structure among multiple bus structures. bus.

The base station 11 or the user terminal 12 can also communicate with one or more external devices 700 (such as keyboards, pointing devices, Bluetooth devices, etc.), and can also communicate with one or more devices that enable the user to interact with the base station 11 or the user terminal 12 Communicate and/or communicate with any device (such as a router, modem, etc.) that enables the base station 11 or user terminal 12 to communicate with one or more other computing devices. This communication can be performed through an input/output (I/O) interface 650. In addition, the base station 11 may also communicate with one or more networks (for example, a local area network (LAN), a wide area network (WAN), and/or a public network, such as the Internet) through the network adapter 860. As shown in the figure, the network adapter 860 communicates with other modules of the user terminal 12 through the bus 830. It should be understood that although not shown in the figure, other hardware and/or software modules can be used in conjunction with the base station 11 or the user terminal 12, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems , Tape drives and data backup storage systems.

Through the description of the foregoing embodiments, those skilled in the art can easily understand that the exemplary embodiments described herein can be implemented by software, or can be implemented by combining software with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (can be a CD-ROM, U disk, mobile hard disk, etc.) or on the network , Including several instructions to make a computing device (which may be a personal computer, a server, a terminal device, or a network device, etc.) execute the method according to the embodiments of the present disclosure.

In the exemplary embodiment of the present disclosure, there is also provided a computer program medium having computer readable instructions stored thereon, and when the computer readable instructions are executed by the processor of the computer, the computer can execute the above method embodiments. Partially described methods.

According to an embodiment of the present disclosure, there is also provided a program product for implementing the method in the above method embodiment, which can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can be used in the terminal Running on equipment, such as a personal computer. However, the program product of the present invention is not limited thereto. In this document, the readable storage medium can be any tangible medium that contains or stores a program, and the program can be used by or in combination with an instruction execution system, device, or device.

The program product can use any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or a combination of any of the above. More specific examples (non-exhaustive list) of readable storage media include: electrical connections with one or more wires, portable disks, hard disks, random access memory (RAM), read only memory (ROM), erasable Type programmable read only memory (EPROM or flash memory), optical fiber, portable compact disk read only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above.

The computer-readable signal medium may include a data signal propagated in baseband or as a part of a carrier wave, and readable program code is carried therein. This propagated data signal can take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing. The readable signal medium may also be any readable medium other than a readable storage medium, and the readable medium may send, propagate, or transmit a program for use by or in combination with the instruction execution system, apparatus, or device.

The program code contained on the readable medium can be transmitted by any suitable medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.

The program code used to perform the operations of the present invention can be written in any combination of one or more programming languages. The programming languages include object-oriented programming languages—such as Java, C++, etc., as well as conventional procedural styles. Programming language-such as "C" language or similar programming language. The program code can be executed entirely on the user's computing device, partly on the user's device, executed as an independent software package, partly on the user's computing device and partly executed on the remote computing device, or entirely on the remote computing device or server Executed on. In the case of a remote computing device, the remote computing device can be connected to a user computing device through any kind of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using Internet service providers) Business to connect via the Internet).

It should be noted that although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more modules or units described above may be embodied in one module or unit. Conversely, the features and functions of a module or unit described above can be further divided into multiple modules or units to be embodied.

In addition, although the various steps of the method of the present disclosure are described in a specific order in the drawings, this does not require or imply that these steps must be performed in the specific order, or that all the steps shown must be performed to achieve the desired result. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step for execution, and/or one step may be decomposed into multiple steps for execution, etc.

Through the description of the foregoing embodiments, those skilled in the art can easily understand that the exemplary embodiments described herein can be implemented by software, or can be implemented by combining software with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (can be a CD-ROM, U disk, mobile hard disk, etc.) or on the network , Including several instructions to make a computing device (which may be a personal computer, a server, a mobile terminal, or a network device, etc.) execute the method according to the embodiment of the present disclosure.

Those skilled in the art will easily think of other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptive changes of the present disclosure, which follow the general principles of the present disclosure and include common knowledge or conventional technical means in the technical field not disclosed in the present disclosure . The description and the embodiments are only regarded as exemplary, and the true scope and spirit of the present disclosure are pointed out by the appended claims.

Claims

An uplink channel scheduling method, characterized in that the method includes:

Receiving an uplink skip notification from a user terminal, the uplink skip notification being sent when the user terminal has no data to send and the authorized data size authorized to the user terminal has not been used up;

Verifying the uplink skip notification;

If the uplink skip notification is successfully verified, stop sending a retransmission request to the user terminal.
The method according to claim 1, wherein if the uplink skip notification verification succeeds, preventing sending a retransmission request to the user terminal comprises:

If the uplink skip notification is successful, monitor the data on the channel authorized for the user terminal in the next communication cycle;

If the data on the channel authorized for the user terminal cannot be monitored in the next communication cycle, the retransmission request is prevented from being sent to the user terminal.
The method according to claim 2, characterized in that if the scheduling mode of the user terminal is non-short-period semi-persistent scheduling, if the uplink skip notification verification succeeds, the user terminal is prevented from sending a retransmission request After that, the method further includes:

An implicit deactivation request for releasing the uplink semi-persistent scheduling (SPS) channel and scrambling resources is sent to the user terminal.
The method according to claim 3, characterized in that, after the retransmission request is prevented from being sent to the user terminal if the uplink skip notification verification is successful, the method further comprises:

Sending a hybrid automatic repeat request (HARQ) channel release command for releasing an uplink hybrid automatic repeat request (HARQ) channel with the user terminal to the user terminal.
The method according to claim 2, wherein if the scheduling mode of the user terminal is short-period semi-persistent scheduling, if the uplink skip notification verification succeeds, after the retransmission request is prevented from being sent to the user terminal , The method further includes:

Wait for the end of the current short cycle;

Sending the explicit deactivation request for releasing the uplink semi-persistent scheduling (SPS) channel and scrambling resources to the user terminal;

A response from the user terminal to the explicit deactivation request for releasing the uplink semi-persistent scheduling (SPS) channel and the scrambled resource is received.
The method according to claim 5, characterized in that, if the uplink skip notification verification is successful, the method further comprises:

Sending a hybrid automatic repeat request (HARQ) channel release command for releasing an uplink hybrid automatic repeat request (HARQ) channel with the user terminal to the user terminal.
The method according to claim 1, wherein the user terminal determines that the user terminal is in a situation where there is no data to send and the authorized data size authorized to the user terminal has not been used up:

In response to receiving a request for establishing a communication channel from the base station, obtain the authorized data size from the request and store it;

Get the size of the data to be sent and store it in the Buffer Status Report (BSR);

Whenever the communication channel is used to send data to the base station once, the size of the sent data is deducted from the stored authorized data size and deducted from the buffer status report (BSR);

When it is detected that the size of the data to be sent in the Buffer Status Report (BSR) is 0 and the size of the authorized data stored is positive, it is determined that the user terminal is in a situation where there is no data to send and the authorized data size authorized to the user terminal has not been used up Happening.
The method according to claim 1, wherein the user terminal determines that the user terminal is in a situation where there is no data to send and the authorized data size authorized to the user terminal has not been used up:

In response to receiving a request for establishing a communication channel from the base station, obtaining the authorized data size from the request;

Get the size of the data to be sent;

If the size of the obtained authorized data is greater than the size of the data to be sent, place a trigger bit at the end of the data to be sent;

The trigger bit is extracted when the data is sent from the data to be sent, and the trigger bit is prevented from being sent, and it is determined that the user terminal is in a situation where there is no data to send and the authorized data size authorized to the user terminal has not been used up.
The method according to claim 1, wherein the user terminal determines that the user terminal is in a situation where there is no data to send and the authorized data size authorized to the user terminal has not been used up:

In response to receiving a request for establishing a communication channel from the base station, obtaining the authorized data size from the request;

Get the size of the data to be sent;

If the size of the obtained authorized data is greater than the size of the data to be sent, based on the size of the data to be sent, the size of the data sent to the base station for each communication, and the time interval between two adjacent transmissions, determine the sending of the data to be sent duration;

Based on the sending duration, setting a timer;

Send the data to be sent;

When the timer expires, it is determined that the user terminal is in a situation where no data is sent and the authorized data size authorized to the user terminal has not been used up.
The method according to claim 1, wherein said verifying said uplink skip notification comprises:

If a dedicated message is used between the base station and the user terminal to verify the uplink skip notification, then identify whether the specific identifier field in the dedicated message carries a specific identifier, and if it does, verify the uplink The link skip notification succeeded.
The method according to claim 1, wherein said verifying said uplink skip notification comprises:

If a medium access control (MAC) control element (CE) is used as the uplink skip notification between the base station and the user terminal, and a specific field of the medium access control (MAC) control element (CE) is used A specific reserved value to indicate to skip the uplink, and determine whether the specific reserved value is on the specific field;

If the specific reserved value is on the specific field, verify that the uplink skip notification is successful.
The method according to claim 11, wherein the verifying that the uplink skip notification is successful if the specific reserved value is on the specific field comprises:

If the specific field has the specific reserved value, determining whether the message body of the medium access control (MAC) control element (CE) carries a specific message body value;

If the message body of the medium access control (MAC) control element (CE) carries a specific message body value, verify that the uplink skip notification is successful.
The method according to claim 1, wherein said verifying said uplink skip notification comprises:

If a medium access control (MAC) control element (CE) is used as the uplink skip notification between the base station and the user terminal, and a specific field of the medium access control (MAC) control element (CE) is used Represents the value of the short-period buffer status report (BSR) to indicate that the uplink is skipped, and determines whether a specific field of the medium access control (MAC) control element (CE) has a value representing the short-period buffer status report (BSR) ；

If the specific field of the medium access control (MAC) control element (CE) has a value representing the short-period buffer status report (BSR), it is acquired that the last time the user terminal received from the user terminal has a specific field representing the short-period Cache status report (BSR) value time;

If the difference between the current time and the acquired time is not equal to a multiple of the predetermined buffer status report (BSR) interval, the uplink skips to notify that the verification is successful.
The method according to claim 13, characterized in that, if a specific field of the medium access control (MAC) control element (CE) has a value representing a short-period buffer status report (BSR), obtain the last received The time until the user terminal has a value representing the short-period buffer status report (BSR) on a specific field includes:

If the specific field of the medium access control (MAC) control element (CE) has a value representing the short-period buffer status report (BSR), it is determined that the message body of the medium access control (MAC) control element (CE) Whether to carry a specific message body value;

If the message body of the medium access control (MAC) control element (CE) carries a specific message body value, obtain the last received message from the user terminal that indicates a short-period buffer status report (BSR) in the specific field. The value of time.
An uplink channel scheduling method, characterized in that the method includes:

Determining that the user terminal is in a situation where there is no data to send and the authorized data size authorized to the user terminal has not been used up;

When the user terminal has no data to send and the authorized data size authorized to the user terminal has not been used up, an uplink skip notification is sent to the base station.
The method according to claim 15, wherein if the scheduling mode of the user terminal is dynamic scheduling, when the user terminal is in a situation where there is no data transmission and the authorized data size authorized to the user terminal has not been used up, After sending the uplink skip notification to the base station, it includes:

Release the uplink hybrid automatic repeat request (HARQ) channel with the base station.
The method according to claim 15, wherein if the scheduling mode of the user terminal is non-short-period semi-persistent scheduling, there is no data transmission in the user terminal and the authorized data size authorized to the user terminal has not been used up In the case of sending the uplink skip notification to the base station, it includes:

Receiving, from the base station, an implicit deactivation request for releasing uplink semi-persistent scheduling (SPS) channels and scrambling resources;

Release the uplink semi-persistent scheduling (SPS) channel and scrambling resources.
The method according to claim 17, wherein when the user terminal has no data to transmit and the authorized data size authorized to the user terminal has not been used up, after sending the uplink skip notification to the base station, the include:

Receiving from the base station a hybrid automatic repeat request (HARQ) channel release command used to release an uplink hybrid automatic repeat request (HARQ) channel with the user terminal;

Release the uplink hybrid automatic repeat request (HARQ) channel with the base station.
The method according to claim 15, wherein if the scheduling mode of the user terminal is short-period semi-persistent scheduling, the size of the authorized data authorized to the user terminal is not used up when there is no data transmission at the user terminal In this case, after sending the uplink skip notification to the base station, it includes:

Receiving, from the base station, an implicit deactivation request for releasing uplink semi-persistent scheduling (SPS) channels and scrambling resources;

Sending, to the base station, the user terminal's response to the explicit deactivation request for releasing uplink semi-persistent scheduling (SPS) channels and scrambling resources;

Release the uplink semi-persistent scheduling (SPS) channel and scrambling resources.
The method according to claim 15, wherein when the user terminal has no data to send and the authorized data size authorized to the user terminal has not been used up, after sending the uplink skip notification to the base station, the include:

Receiving from the base station a hybrid automatic repeat request (HARQ) channel release command used to release an uplink hybrid automatic repeat request (HARQ) channel with the user terminal;

Release the uplink hybrid automatic repeat request (HARQ) channel with the base station.
The method according to claim 15, wherein the determining that the user terminal is in a situation where no data is sent and the size of the authorized data authorized to the user terminal has not been used up, comprises:

In response to receiving a request for establishing a communication channel from the base station, obtain the authorized data size from the request and store it;

Get the size of the data to be sent and store it in the Buffer Status Report (BSR);

Whenever the communication channel is used to send data to the base station once, the size of the sent data is deducted from the stored authorized data size and deducted from the buffer status report (BSR);

When it is detected that the size of the data to be sent in the Buffer Status Report (BSR) is 0 and the size of the authorized data stored is positive, it is determined that the user terminal is in a situation where there is no data to send and the authorized data size authorized to the user terminal has not been used up Happening.
The method according to claim 15, wherein the determining that the user terminal is in a situation where no data is sent and the size of the authorized data authorized to the user terminal has not been used up, comprises:

In response to receiving a request for establishing a communication channel from the base station, obtaining the authorized data size from the request;

Get the size of the data to be sent;

If the size of the obtained authorized data is greater than the size of the data to be sent, place a trigger bit at the end of the data to be sent;

The trigger bit is extracted when the data is sent from the data to be sent, and the trigger bit is prevented from being sent, and it is determined that the user terminal is in a situation where there is no data to send and the authorized data size authorized to the user terminal has not been used up.
The method according to claim 15, wherein the determining that the user terminal is in a situation where no data is sent and the size of the authorized data authorized to the user terminal has not been used up, comprises:

In response to receiving a request for establishing a communication channel from the base station, obtaining the authorized data size from the request and storing the data size to be sent;

Get the size of the data to be sent;

If the size of the obtained authorized data is greater than the size of the data to be sent, based on the size of the data to be sent, the size of the data sent to the base station for each communication, and the time interval between two adjacent transmissions, determine the sending of the data to be sent duration;

Based on the sending duration, setting a timer;

Send the data to be sent;

When the timer expires, it is determined that the user terminal is in a situation where no data is sent and the authorized data size authorized to the user terminal has not been used up.
The method according to claim 15, wherein the base station verifies the uplink skip notification through the following process:

If a dedicated message is used between the base station and the user terminal to verify the uplink skip notification, then identify whether the specific identifier field in the dedicated message carries a specific identifier, and if it does, verify the uplink The link skip notification succeeded.
An uplink channel scheduling device, characterized in that the device includes:

The first receiving unit is configured to receive an uplink skip notification from a user terminal, where the uplink skip notification is when the user terminal has no data to send and the authorized data size authorized to the user terminal has not been used up Send in case of;

A verification unit for verifying the uplink skip notification;

The first processing unit is configured to prevent sending a retransmission request to the user terminal if the uplink skip notification verification is successful.
An uplink channel scheduling device, characterized in that the device includes:

The second processing unit is used to determine a situation where the user terminal has no data to send and the authorized data size authorized to the user terminal has not been used up;

The second sending unit is configured to send an uplink skip notification to the base station when the user terminal has no data to send and the size of the authorized data authorized to the user terminal has not been used up.
A base station, characterized in that it comprises:

Memory, storing computer readable instructions;

The processor reads computer readable instructions stored in the memory to execute the method described in any one of claims 1-14.
A user terminal, characterized in that it includes:

Memory, storing computer readable instructions;

The processor reads computer readable instructions stored in the memory to execute the method described in any one of claims 15-26.
A computer program medium having computer readable instructions stored thereon, wherein when the computer readable instructions are executed by a processor of a computer, the computer is caused to execute the method described in any one of claims 1-14 .
A computer program medium having computer readable instructions stored thereon, wherein when the computer readable instructions are executed by a processor of a computer, the computer is caused to execute the method described in any one of claims 15-26 .