Scheduling method, terminal and base station

Abstract

This application relates to the field of communications technologies. Specifically, this application provides a programming method. In this method, when a terminal needs to send service data for an ultra-reliable, low-latency communications service, the terminal sends a programming request to a base station. This programming request carries temporary storage information in a temporary storage status report sent by the terminal to the base station in a unique programming procedure. Therefore, when compared to an existing programming procedure, in the programming method provided in this application, no temporary storage status report needs to be sent to the base station, thereby reducing the steps of the programming procedure and reducing programming latency.To achieve a concept of the invention of reducing the steps of the programming procedure, this application additionally provides a programming method to simplify the steps of a programming procedure. Furthermore, to ensure practical application and deployment of the programming method, this application additionally provides a corresponding programming device.

Description

1 / 52 “SCHEDULING METHOD, TERMINAL AND BASE STATION”

[0001] This application claims priority to Chinese Patent Application No. 201710025821.4, filed with the Chinese Patent Office on January 13, 2017, and entitled SCHEDULING METHOD AND RELATED DEVICE, which is incorporated herein by reference in its entirety. FIELD OF TECHNIQUE

[0002] This application relates to the field of communications technologies and, more specifically, to a scaling method and a related device. BACKGROUND

[0003] In the field of mobile communications, Long Term Evolution (LTE) is a commonly used communications technology. A scaling procedure is required during communication using this communications technology, and the scaling procedure can be called an LTE scaling procedure. In the LTE scaling procedure, data can be transmitted between a base station (eNB) and a terminal (User Equipment, UE) to implement a communication service between the terminal and the base station.

[0004] The LTE scheduling procedure specifically includes five steps shown in Figure 1, which are: sending a Scheduling Request (SR) to the base station via the terminal; returning an Uplink Grant (UL grant) to the terminal via the base station; sending a Buffer State Report (BSR) via the terminal using the Uplink Grant, where the Buffer State Report carries a volume of service data to be sent; returning an Uplink Grant corresponding to the data volume to the terminal via the base station; and sending the service data via the terminal using the Uplink Grant.

[0005] Currently, a trend in communication service development is the fast and efficient transmission of service data. However, in the existing LTE scaling procedure used by the communication service, there is a relatively large number of interactions of Petition 870250090736, dated 06 / 10 / 2025, page 33 / 84 2 / 52 signaling, and latency is relatively high. Therefore, a latency requirement for a latency-sensitive communication service cannot be met. SUMMARY

[0006] In one aspect, this application provides a scheduling method, which includes: sending a scheduling indication to a base station if there is service data to be sent on a target logical channel, wherein the target logical channel is a logical channel specified by the base station or by a terminal, and the scheduling indication is used to instruct the base station to allocate an uplink grant resource to the target logical channel in a predefined allocation mode; and receiving the uplink grant resource sent by the base station.In this method, the terminal can send the scheduling indication to the base station, instructing the base station to allocate the uplink grant resource to the terminal in a predefined accelerated allocation mode, thereby simplifying a step related to the allocation of uplink grant resources in an existing scheduling procedure, and reducing the latency of the existing scheduling procedure.

[0007] In a possible project, sending a scheduling indication to a base station includes: sending a scheduling request to the base station, where the scheduling request carries the scheduling indication using a bit. In this method, the scheduling indication is carried in the scheduling request in an explicit way by adding a bit, and the method of sending the scheduling indication is relatively simple and easy to implement.

[0008] In a possible project, sending a scheduling indication to a base station includes: sending a scheduling request to the base station based on a predefined scheduling request sending cycle, where the predefined scheduling request sending cycle is shorter than the scheduling request sending cycle of a logical channel other than the target logical channel. In this method, the fact that the terminal sends the scheduling request based on the predefined scheduling request sending cycle implicitly indicates that the terminal sends the scheduling indication to the base station, and Petition 870250090736, dated 06 / 10 / 2025, page 34 / 84 3 / 52 No bits need to be added to the scheduling request, thus reducing the resource consumed in sending the scheduling request.

[0009] In a possible project, sending a scheduling indication to a base station includes: sending a buffer status report to the base station, where the buffer status report carries the scheduling indication using a bit. In this method, the scheduling indication is carried in the buffer status report in an explicit way using a bit, and the method of sending the scheduling indication is relatively simple and easy to implement.

[0010] In a possible project, sending a scheduling indication to a base station includes: sending a buffer status report to the base station at a predefined location on a shared uplink physical channel. In this method, the fact that the terminal sends the buffer status report at the predefined location on the shared uplink physical channel implicitly indicates that the terminal sends the scheduling indication to the base station, and no bits need to be added to the buffer status report, thus reducing a resource consumed to send the buffer status report.

[0011] According to another aspect, this request provides a scheduling method, which includes: generating a scheduling request if there is service data to be sent on a target logical channel, wherein the target logical channel is a logical channel specified by a base station or a terminal, and the scheduling request includes buffer state information; sending the scheduling request to the base station, wherein the buffer state information in the scheduling request is used by the base station to allocate an uplink lease resource; and receiving the uplink lease resource sent by the base station.

[0012] In a possible design, buffer state information includes data volume indication information, and data volume indication information includes: a data volume value of the service data; or a data volume index of the service data, wherein the data volume index is used to indicate a data volume range of the service data. Petition 870250090736, dated 06 / 10 / 2025, page 35 / 84 4 / 52

[0013] According to another aspect, this request provides a scheduling method, which includes: sending a buffer status report to a base station using a pre-configured uplink resource if there is service data to be sent on a target logical channel, wherein the target logical channel is a logical channel specified by the base station or a terminal, and the buffer status report is used by the base station to allocate an uplink lease resource to the target logical channel; and receiving the uplink lease resource sent by the base station. In this method, the buffer status report is sent using the pre-configured uplink resource, so that a step of requesting an uplink resource from the base station is omitted, thereby reducing the latency of an existing scheduling procedure.

[0014] In a possible project, sending a buffer status report to a base station using a pre-configured uplink feature includes: sending the same buffer status report to the base station multiple times using the pre-configured uplink feature. In this method, sending the buffer status report multiple times can increase the success rate of the base station receiving the buffer status report.

[0015] According to another aspect, this application provides a scheduling method, which includes: continuously detecting, after a detection instruction is received, whether there is service data to be sent on a target logical channel of the terminal, wherein the target logical channel is a logical channel specified by a base station or the terminal; enabling a first predefined scheduling mode if there is service data to be sent on the target logical channel, wherein the first scheduling mode is a scheduling mode for sending a scheduling request, and the scheduling request carries any one or more of the following: a scheduling indication, buffer state information, and a type of service data;and switch the first scheduling mode to a second predefined scheduling mode if the enabled duration of the first scheduling mode reaches the first predefined duration, where the second scheduling mode is a scheduling mode to send a buffer status report to the base station using one; Petition 870250090736, dated 06 / 10 / 2025, page 36 / 84 5 / 52 pre-stored uplink resource. In this method, the resources used in the first scheduling mode are limited resources. Therefore, switching between the first scheduling mode and the second scheduling mode can alleviate a restricted demand of the first scheduling mode for limited resources.

[0016] In a possible project, the scheduling method additionally includes: after the first scheduling mode is enabled, disabling the first scheduling mode if there is no more service data to be sent on the target logical channel and the duration without service data reaches the second predefined duration.

[0017] In a possible project, the scheduling method additionally includes: after the first scheduling mode is disabled, enabling the first scheduling mode if it is detected that there is service data to be sent on the target logical channel.

[0018] According to another aspect, this application provides a scheduling method, which includes: receiving a scheduling indication sent by a terminal, wherein the scheduling indication is sent when there is service data to be sent on a target logical channel of the terminal, and the target logical channel is a logical channel specified by the base station or the terminal; and allocating an uplink grant resource to the target logical channel in a predefined allocation mode. This method is applied on one side of the base station and, after the scheduling indication is received, the uplink grant resource is quickly allocated to the terminal, thereby simplifying a step related to the allocation of uplink grant resources in an existing scheduling procedure, and reducing latency in the existing scheduling procedure.

[0019] In a possible project, allocating an uplink grant resource to the target logical channel in a predefined allocation mode includes: allocating the uplink grant resource to the target logical channel separately; or allocating the uplink grant resource to the target logical channel after a predefined short time interval, where the short time interval indicates that the time interval for the target logical channel to obtain the uplink grant resource is less than one Petition 870250090736, dated 06 / 10 / 2025, page 37 / 84 6 / 52 time interval of another logical channel; or preferentially allocate the uplink grant resource to the target logical channel after uplink grant resource allocation requests corresponding to a plurality of logical channels are received; or allocate, based on a volume of service data on the target logical channel, more uplink grant resources to the target logical channel than to the data volume.

[0020] According to another aspect, this application provides a scheduling configuration method, wherein the method includes: determining a logical channel that uses a predefined scheduling mode; and sending a predefined scheduling mode identifier and a logical channel identifier to a terminal, wherein the predefined scheduling mode is any one of the following three modes: a first scheduling mode, a second scheduling mode, and a mode that switches between the first scheduling mode and the second scheduling mode, wherein the first scheduling mode is a scheduling mode in which a base station receives a scheduling request sent by the terminal, the scheduling request carrying any one or more of the following: a scheduling indication, buffer state information, and a type of service data,The second scheduling mode is a scheduling mode in which the base station receives a buffer status report sent by the terminal using a pre-stored uplink resource. This method is a configuration method performed before a scheduling method, so that the terminal can perform scheduling based on a configured scheduling mode, thereby reducing the latency of an existing scheduling method.

[0021] In a possible project, sending a predefined scheduling mode identifier and a logical channel identifier to the terminal includes: sending a logical channel connection reconfiguration message to the terminal, where the logical channel connection reconfiguration message includes the predefined scheduling mode identifier and the logical channel identifier; or sending a downlink control physical channel resource to the terminal, where the downlink control physical channel resource includes the predefined scheduling mode identifier. Petition 870250090736, dated 06 / 10 / 2025, page 38 / 84 7 / 52 and the logical channel identifier; or send a media access control element to the terminal, wherein the media access control element includes the predefined scheduling mode identifier and the logical channel identifier.

[0022] According to another aspect, this application provides a scheduling configuration method, which includes: receiving a predefined scheduling mode identifier and a logical channel identifier that are sent by a base station, wherein the predefined scheduling mode is any one of the following three modes: a first scheduling mode, a second scheduling mode, and a mode that switches between the first scheduling mode and the second scheduling mode, wherein the first scheduling mode is a scheduling mode in which a terminal sends a scheduling request to the base station, the scheduling request carrying any one or more of the following: a scheduling indication, buffer state information, and a type of service data,The second scheduling mode is a scheduling mode in which the terminal sends a buffer state report to the base station using a pre-stored uplink resource; and determines the logical channel that corresponds to the logical channel identifier as a target logical channel, and determines a scheduling mode that corresponds to the predefined scheduling mode identifier as the scheduling mode used by the terminal. This method is a configuration method performed before a scheduling method, so that the terminal can perform scheduling based on a configured scheduling mode, thereby reducing the latency of an existing scheduling method.

[0023] According to another aspect, this request provides a terminal, and the terminal has a function to implement the preceding scheduling method that is applied to a terminal. The function can be implemented by hardware, or it can be implemented by hardware running corresponding software. Hardware or software includes one or more modules that correspond to the preceding function.

[0024] According to another aspect, this request provides a terminal, and the terminal has a function to implement the preceding scheduling configuration method that is applied to a terminal. The function can be Petition 870250090736, dated 06 / 10 / 2025, p. 39 / 84 8 / 52 implemented by hardware, or it can be implemented by hardware running corresponding software. Hardware or software includes one or more modules that correspond to the preceding function.

[0025] According to another aspect, this request provides a base station, and the base station has a function to implement the antecedent scheduling method that is applied to a base station. The function can be implemented by hardware, or it can be implemented by hardware running corresponding software. Hardware or software includes one or more modules that correspond to the antecedent function.

[0026] According to another aspect, this request provides a base station, and the base station has a function to implement the antecedent scheduling configuration method that is applied to a base station. The function may be implemented by hardware, or it may be implemented by hardware running corresponding software. Hardware or software includes one or more modules that correspond to the antecedent function.

[0027] According to another aspect, this request provides a terminal, and the terminal includes the preceding processor and a communications interface. The processor may implement a function of a processing module applied to the terminal. The communications interface may implement a function of a sending module and / or a receiving module applied to the terminal.

[0028] According to another aspect, this request provides a base station, and the base station includes the preceding processor and a communications interface. The processor may implement a function of a processing module applied to a terminal. The communications interface may implement a function of a sending module and / or a receiving module applied to a terminal.

[0029] According to another aspect, this application provides a communications system, and the communications system includes the terminal and the base station, according to the preceding aspects.

[0030] According to another aspect, this application provides a computer storage medium configured to store computer software instructions used by the preceding terminal. The computer storage medium contains a program designed to execute the preceding aspects. Petition 870250090736, dated 06 / 10 / 2025, page 40 / 84 9 / 52

[0031] According to another aspect, this application provides a computer storage medium, configured to store computer software instructions used by the preceding base station. The computer storage medium contains a program designed to execute the preceding aspects.

[0032] According to the technical solutions provided in this application, the existing escalation procedure is simplified, thereby reducing the latency of the existing escalation procedure, and ensuring fast and efficient delivery of a communication service. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] To describe the technical solutions in the embodiments of this application or in the prior art more clearly, the following section describes, in a concise manner, the accompanying drawings required to describe the embodiments or the prior art.

[0034] Figure 1 is a schematic flowchart of an existing LTE scheduling procedure;

[0035] Figure 2 is a schematic diagram of the scheduling and connection interaction between a terminal and a base station, according to this request;

[0036] Figure 3 is a flowchart of embodiment 1 of a scheduling method, according to this request;

[0037] Figure 4 is a flowchart of embodiment 2 of a scheduling method, according to this request;

[0038] Figure 5 is a flowchart of embodiment 3 of a scheduling method, according to this request;

[0039] Figure 6 is a flowchart of embodiment 4 of a scheduling method, according to this request;

[0040] Figure 7 is a flowchart of a repeated BSR delivery mode, according to this request;

[0041] Figure 8 is a flowchart of embodiment 5 of a scheduling method, according to this request;

[0042] Figure 9 is a flowchart of a scheduling configuration method, according to this request;

[0043] Figure 10 is a schematic structural diagram of Petition 870250090736, dated 06 / 10 / 2025, page 41 / 84 10 / 52 terminal hardware, in accordance with this request; and

[0044] Figure 11 is a schematic structural hardware diagram of a base station, in accordance with this application. DETAILED DESCRIPTION OF THE INVENTION

[0045] Currently, a trend in the development of communication services is Ultra-Reliable and Low Latency Communications (URLLC). This service has a relatively high latency requirement. It should be noted that URLLC is a type of service rather than a specific service. This type of service requires relatively low latency in a communication process. Therefore, any communication service that has a latency requirement is covered by the scope of protection of this application. For ease of description, the following section describes the technical solutions of this application using URLLC as an example.

[0046] A communication service between a base station and a terminal can be implemented in an LTE scheduling procedure. In a specific URLLC communication service implementation scenario, the LTE scheduling procedure fails to meet a low latency requirement of the service. This is because, in an existing LTE scheduling procedure, before the terminal uploads service data, control signaling needs to be exchanged between the terminal and the base station multiple times to configure a communication resource to upload the service data.

[0047] Figure 1 is a schematic flowchart of the existing LTE scheduling procedure. As shown in Figure 1, the procedure specifically includes five steps.

[0048] Step 1: When a communication service requirement is met, the terminal sends a Scheduling Request (SR) to the base station. The SR scheduling request has only one bit, to notify the base station that the UE needs an Uplink Grant (UL grant).

[0049] Step 2: The base station sends a UL grant to the terminal, where the UL grant is used by the terminal to send a Buffer State Report (BSR). Petition 870250090736, dated 06 / 10 / 2025, page 42 / 84 11 / 52

[0050] Step 3: The terminal sends the BSR using the UL grant, where the BSR is used to report a volume of service data to be sent by the terminal.

[0051] Step 4: The base station allocates a UL lease to the terminal based on the BSR reported by the terminal and a scheduling algorithm, wherein the UL lease is used by the terminal to send service data (wherein service data may also be referred to as uplink data).

[0052] Step 5: The terminal sends the service data (Data) using the UL grant.

[0053] The preceding procedure refers to UL grants of two uplink grants. For ease of distinction, the uplink grant UL grant to send the BSR in step 2 is referred to as a first uplink grant (UL grant_1), and the uplink grant UL grant to send the service data in step 4 is a second uplink grant (UL grant_2). Additionally, the uplink grant may also be referred to as an uplink grant resource.

[0054] In the scheduling shown in Figure 1, the base station needs to determine the size of the second uplink lease resource based on the volume of service data to be uploaded by the terminal. However, the terminal does not directly notify the base station of the volume of data to be sent, but first notifies the base station, using step 1, of a request from the terminal that the terminal intends to send the service data, and after the base station sends the first uplink lease resource in step 2, the terminal uploads the volume of data to be sent using the first uplink lease resource in step 3.Furthermore, in step 4, the base station temporarily determines, based on the data volume and scheduling algorithm, the second uplink grant required by the terminal and then delivers the second uplink grant to the terminal.

[0055] It can be learned that, before the terminal sends service data to the base station, signaling interactions (which include at least Petition 870250090736, dated 06 / 10 / 2025, page 43 / 84 12 / 52 interactions in steps 1 to 4 need to be performed a plurality of times. Table 1 shows latency data in the LTE scheduling procedure. It can be learned from Table 1 that, in each signaling interaction, the terminal and the base station need to obtain a particular processing time, and a greater number of signaling interactions causes greater latency. Table 1 Number Description Transmission Time Interval (TTI) 1 Average time the UE waits for a PUCCH (to send an SR) 0.5 2 The UE sends an SR 1 3 An eNB decodes the SR and generates an uplink grant (the UL grant in step 2) 1 4 The eNB delivers the uplink grant 1 5 UE processing time, which includes time to decode the uplink grant and time to encode a BSR 1 6 The UE sends the BSR 1 7 The eNB decodes the BSR and generates an uplink grant (the UL grant in step 4) 1 8 The eNB delivers the uplink grant 1 9 UE processing time, which includes time to decode the uplink grant and time to encode uplink data 1 Petition 870250090736, dated 06 / 10 / 2025, page 44 / 84 13 / 52 10 The EU sends the uplink data 1

[0056] It can be learned from both Figure 1 and Table 1 that the latency of the scheduling procedure before the terminal sends the service data to the base station is relatively high. To solve this problem, this application provides a scheduling method to reduce latency caused by a scheduling procedure and thus meet a latency requirement of an ultra-reliable, low-latency URLLC communications service in a scenario where a terminal sends the service.

[0057] In the technical solution of this application, the latency of the existing scheduling procedure is reduced by simplifying the steps of the scheduling procedure. Based on the concept, this application provides the following specific modalities. Mode 1

[0058] In this mode, an SR, sent by a terminal, carries more information. This information is originally carried in a BSR to be used by a base station to generate an uplink lease (namely, a second uplink lease) to upload service data. In this way, step 2 of sending a first uplink lease and step 3 of sending a BSR can be omitted, thus reducing the latency of a scheduling procedure.

[0059] Note that the terminal can add more information to the SR, and the fact that the terminal has this function may be based on a base station configuration in a connection process prior to the escalation procedure.

[0060] Specifically, prior to the scheduling procedure, the connection process is performed between the terminal and the base station. As shown in Figure 2, during the connection process, the base station sends a Radio Resource Control (RRC) connection reconfiguration message to the terminal. The RRC connection reconfiguration message includes a configuration message for a logical channel. Different logical channels are used for different services. The base station can configure a logical channel used by a URLLC service, so Petition 870250090736, dated 06 / 10 / 2025, page 45 / 84 Specifically, add a configuration identifier to a logical channel configuration message used by the URLLC service. The configuration identifier is used to instruct the terminal to send the SR on the logical channel in an enhanced mode. Thus, when performing the escalation procedure, the terminal encapsulates, according to an indication from the configuration identifier, more information in the SR to be sent to the base station. Of course, if the terminal does not detect the configuration identifier in the RRC connection reconfiguration message, the terminal may send the SR in an existing mode.

[0061] In terms of the preceding procedure, some technical details need to be described. The configuration identifier added to the logical channel configuration message can be in the form of an Information Element (IE). A specific name for the IE information element could be logicalChannel-SR-Enhancement-maskr15.

[0062] It should be noted that a configuration indication sent by the base station to the terminal is not limited to the form of the configuration identifier added to the RRC connection reconfiguration message, and may alternatively be in another form. For example, the configuration identifier may be carried in a Physical Downlink Control Channel (PDCCH) physical channel resource or in a MAC CE. The Media Access Control (MAC) Control Element (CE) may be referred to as a media access control element.

[0063] Additionally, the base station may not be limited to sending the configuration indication to the terminal during the connection process, and the base station may alternatively send the configuration indication to the terminal in another process before the scheduling procedure or during the scheduling procedure.

[0064] Additionally, the terminal can implement the function, as described above, based on the base station configuration, or based on a terminal configuration. Specifically, the terminal generates a configuration indication for the logical channel on which the URLLC service is located, to instruct the sending of the SR on the logical channel in enhanced mode. Petition 870250090736, dated 06 / 10 / 2025, page 46 / 84 15 / 52

[0065] After the preceding configuration, the terminal can send the SR in enhanced mode. Figure 3 shows a procedure of mode 1 of a scheduling method, according to this request. The scheduling method specifically includes steps S301 to S303.

[0066] S301: When the terminal needs to send URLLC service data, the terminal sends an enhanced SR to the base station, where the enhanced SR carries buffer state information in a BSR.

[0067] The terminal determines whether service data for a URLLC service needs to be sent. If service data for the URLLC service needs to be sent, the terminal generates an SR to be reported to the base station. Service data for the URLLC service can be sent on a logical channel specified by the base station, or it can be sent on the logical channel not specified by the base station.

[0068] The SR generated by the terminal includes more information than an existing SR shown in Figure 1. Therefore, for ease of distinction, the SR generated in this mode can be called an enhanced SR. The existing SR includes only one bit, and that bit is used to notify the base station that the terminal has service data to send. If buffer state information needs to be added to the SR, a bit can be added to the SR, and the added buffer state information is indicated using the added bit.

[0069] Optionally, in addition to information indicating that the terminal has service data to be sent, the enhanced SR additionally carries the buffer state information originally carried in the BSR. The buffer state information originally carried in the BSR is the buffer state information added in the enhanced SR, and includes, but is not limited to, any one or a combination of two of the following: a data volume of the service data to be sent and an identifier of a logical channel (or a logical channel group).

[0070] The volume of service data to be sent is used by the base station to calculate the size of the uplink lease resource (namely, the second uplink lease resource). The logical channel group identifier is used by the base station to determine whether the uplink lease resource is allocated. Petition 870250090736, dated 06 / 10 / 2025, page 47 / 84 16 / 52 for which logical channel group. These logical channel groups include logical channels for sending service data.

[0071] Optionally, the buffer state information added in the enhanced SR includes data volume indication information for the service data to be sent. Data volume indication information is used to indicate the data volume of the service data. Specifically, data volume indication information can be in any of the following forms:

[0072] 1. A level 1 index data volume index.

[0073] The base station stores a matching table of level 1 data volume indexes and level 1 data volume ranges. After receiving a level 1 data volume index, the base station searches the matching table for a level 1 data volume range that corresponds to the level 1 data volume index, to determine an approximate data volume of service data to be sent on the terminal.

[0074] For example, if a ported index value in the enhanced SR is 3, and a data volume that corresponds to index 3 in the matching table is 300 to 400, the base station can determine that a data volume of the service data to be sent to the terminal is between 300 and 400.

[0075] It can be learned that the information provided to the base station by the volume of data in such a form carried in the enhanced SR is of low precision, and the base station can only determine, in an approximate way, the volume of service data to be sent.

[0076] 2. A level 1 index data volume index and a level 2 index data volume sub-index.

[0077] In addition to the preceding matching table, the base station additionally stores a matching table of level 2 index data volume sub-indices and level 2 index data volume ranges. For ease of distinction, the first matching table may be referred to as a first matching table, and the last matching table may be referred to as a second matching table. In addition to the level 1 index data volume index, the enhanced SR includes, Petition 870250090736, dated 06 / 10 / 2025, page 48 / 84 17 / 52 Additionally, a level 2 index data volume sub-index. The level 2 index data volume sub-index is used to provide more detailed data volume range information.

[0078] For example, if a value of the index carried in the enhanced SR is 3, and a value of the subindex is 6, a level 1 data volume range found by the base station in a level 1 matching table, based on index 3, is 300 to 400, and a level 2 data volume range found in a level 2 matching table, based on subindex 6, is 60 to 70, and then the base station determines that the data volume of the service data to be sent is between 360 and 370.

[0079] It can be learned that adding the data volume in such a form to the enhanced SR can provide a more detailed data volume range lookup basis for the base station, so that the base station can more accurately determine the data volume of service data to be sent.

[0080] The indexes in the two preceding forms may be referred to as data volume indexes for the sake of brevity. The data volume index is used to indicate a range of data volume. The data volume index may include several levels of indexes, and a range of data volume indicated by each next-level index is more precise than a range of data volume indicated by a previous-level index. The preceding level 1 index and level 2 index are used as an example; the level 1 index indicates a range of data volume in the hundredths place, and the level 2 index indicates a range of data volume in the decimal place. Alternatively, a level 3 index may be included additionally, and the level 3 index may indicate a range of data volume in the units place.Certainly, the data volume ranges indicated by the level 1 index, the level 2 index, and the level 3 index are not limited to the hundredths place, the decimal place, and the unit place, but may alternatively be other value ranges in other unit places.

[0081] 3. A specific data volume value.

[0082] The terminal stores the service data to be sent in a buffer, and registers a volume of data in the buffer. The volume of Petition 870250090736, dated 06 / 10 / 2025, page 49 / 84 18 / 52 data is the volume of service data to be sent. The enhanced SR does not carry an index in the previous form, but carries a specific value of the data volume in the buffer, for example, 365.

[0083] It can be learned that adding the data volume in such a form to the enhanced SR can provide a more detailed basis for the base station, so that the base station can generate, based on the data volume, an uplink resource with a more accurate resource volume value. When compared to the two preceding forms, this form is the most accurate, but the bit overheads are the highest. In a real application, a corresponding data form can be selected based on a real need.

[0084] It should be noted that this request provides the three specific forms of data volume carried in the enhanced SR, but is not limited to them. Any form that can provide relatively more detailed data volume information to the base station can be used. In addition, the terminal can determine a form of data volume to be sent, or the base station can determine the form. Specifically, the base station adds, to the RRC connection reconfiguration message sent to the terminal, an indication that specifies a data volume form to be used, so that the terminal determines, according to the indication, a data volume form to be sent.

[0085] After generating the enhanced SR, the terminal can send the enhanced SR to the base station.

[0086] S302: The base station allocates a UL grant to the terminal based on the buffer state information ported in the enhanced SR.

[0087] The base station allocates an uplink grant resource UL to the terminal based on the buffer state information carried in the enhanced SR. The uplink grant resource is the second preceding uplink grant resource, used by the terminal to upload service data. Additionally, the base station delivers the uplink grant resource UL to the terminal.

[0088] S303: The terminal uploads the service data. Petition 870250090736, dated 06 / 10 / 2025, page 50 / 84 19 / 52 using the UL concession.

[0089] The terminal uploads the URLLC service data to be sent to the base station using the uplink resource UL grant allocated by the base station.

[0090] It can be learned from the preceding technical solution that, in this mode, a bit needs to be added to the SR to carry more information. However, the terminal needs to send an SR using a Physical Uplink Control Channel (PUCCH) resource, and more bits in the SR indicate that more PUCCH resources need to be used. Therefore, this mode is applicable to a scenario where PUCCH resources are extensible.

[0091] In this implementation, the enhanced SR, generated by the terminal, carries information required for scheduling. This information is originally included in a BSR for sending. In this mode, this information required for scheduling is added to the enhanced SR, so that step 2 of sending a UL grant and step 3 of sending a BSR in an existing scheduling procedure shown in Figure 1 can be omitted (the steps with dashed lines and with “X” shown in Figure 3 are omitted steps), thereby reducing latency in the existing scheduling procedure.

[0092] In mode 1, the enhanced SR generated by the terminal includes buffer state information in an original BSR, to omit steps 2 and 3 in the existing scheduling procedure. However, to simplify the existing scheduling procedure, in addition to omitting steps 2 and 3 in Figure 1, the processing steps of some steps can be further simplified. In this way, the latency of the existing scheduling procedure can also be reduced. Based on this, this application provides modes 2 and 3 below. Mode 2

[0093] An enhanced SR generated by a terminal may carry a high-priority scheduling indication (which may be termed a priority scheduling indication or a scheduling indication, for brevity) of URLLC service data to be sent, so that a base station can quickly allocate a first resource of Petition 870250090736, dated 06 / 10 / 2025, page 51 / 84 20 / 52 granting of uplink for URLLC service data based on high priority scheduling indication, thereby simplifying a step 2 and / or step 3 processing process in Figure 1.

[0094] Figure 4 shows a procedure of embodiment 2 of a scheduling method, according to this application. The scheduling method specifically includes steps S401 through S405.

[0095] S401: When a terminal needs to send URLLC service data, the terminal sends an enhanced SR to a base station, where the enhanced SR carries a high-priority escalation indication set for URLLC service data.

[0096] The base station can process multiple types of service data simultaneously. If a type of service data has a high priority, the base station can perform an upward link-grant resource allocation mode that is faster than that in the previous technique for service data. Therefore, the terminal can set a scheduling priority for URLLC service data to a high priority, and when it needs to send URLLC service data, the terminal adds the high-priority scheduling indication to the enhanced SR, so that the base station quickly allocates a second upward link-grant resource for URLLC service data. For a specific fast allocation method, see a description of step S402.

[0097] In a real-world application, the fact that the SR carries the high-priority scheduling indication can be implemented in either explicit or implicit mode as follows.

[0098] Firstly, the enhanced SR port explicitly indicates the high-priority scheduling of the service data to be sent. Specifically, the enhanced SR port indicates the scheduling using a bit.

[0099] Specifically, a bit indicating a priority is added to the enhanced SR, and a bit value is set to high. Priority indications can only include two types: high and low. If a priority indication for URLLC service data is high, a priority indication for other service data is low. Additionally, a bit value can be set to a priority value. For example, a natural number. Petition 870250090736, dated 06 / 10 / 2025, page 52 / 84 21 / 52 is used to indicate the priority value, and a lower value indicates a higher priority. Therefore, if the priority of URLLC service data is intended to be set to the highest, the URLLC service data priority indication could be set to 0.

[0100] Secondly, the enhanced SR port implicitly indicates high priority scheduling of the service data to be sent.

[0101] Specifically, the terminal establishes a plurality of logical channels with the base station, and different logical channels are used to send different service data. Each logical channel of the terminal continuously sends an SR based on a particular sending cycle, and the sending cycle can be called an SR sending cycle (namely, a scheduling request sending cycle).

[0102] The sending cycles of all existing logical channels are equal. In this mode, a logical channel used by URLLC service data can be shortened in advance, so that an SR sending cycle of URLLC service data is shorter than an SR sending cycle of other service data, to represent the urgency of processing URLLC service data. The shortened SR sending cycle can be called the standard escalation request sending cycle. The standard escalation request sending cycle is shorter than an escalation request sending cycle corresponding to a service other than a URLLC service. The base station may have an agreement with the endpoint through a protocol that a shorter SR sending cycle indicates a higher priority of service data to be sent that corresponds to the SR.

[0103] After reducing the SR sending cycle, the terminal can implicitly indicate to the base station, by sending an SR, a high priority of service data to be sent that corresponds to the SR, and can reduce a waiting time for an uplink resource grant for the service data to be sent, thereby reducing latency caused by resource waiting.

[0104] An SR transmission cycle length can be set by the terminal, or it can be set by the base station. If the cycle length Petition 870250090736, dated 06 / 10 / 2025, p. 53 / 84 If the SR sending cycle is defined by the base station, the base station can configure the SR sending cycle in a connection process before a scheduling procedure. For example, the base station adds the SR sending cycle to an RRC connection reconfiguration message and sends the RRC connection reconfiguration message to the terminal. The SR sending cycle is a sending cycle that indicates that the priority of the service data to be sent is relatively high.

[0105] In the first mode, a bit is added to the enhanced SR sent by the terminal to explicitly notify the base station that the priority of the service data to be sent is relatively high. In the second mode, the terminal does not directly notify the base station of the preceding information, but instead implicitly indicates the high priority of the service data to be sent using a relatively short SR sending cycle. In a real application, either of the preceding modes can be selected to report the high-priority scheduling indication of the service data to be sent to the base station.

[0106] After generating the enhanced SR, the terminal sends the enhanced SR to the base station, and the enhanced SR is sent based on a particular transmission cycle. If the enhanced SR carries the indication of high priority scheduling of service data to be sent in the second preceding mode, namely the implicit mode, the transmission cycle of the enhanced SR is inevitably shorter than a transmission cycle of other service data.

[0107] S402: The base station allocates a UL grant to the terminal in a fast allocation mode based on the high-priority scheduling indication ported to the enhanced SR. The UL grant is used by the terminal to upload a BSR.

[0108] If the enhanced SR carries the high-priority scheduling indication in explicit mode, after receiving an SR, the base station can detect if the SR includes a priority indication and a bit with the priority indication set to high. If so, this indicates that the SR is the enhanced SR carrying the high-priority scheduling indication. If the terminal adds the high-priority scheduling indication in implicit mode, after receiving an SR, the base station determines a send cycle for the SR and, if the send cycle is relatively shorter than a send cycle for another SR, the base station will determine the send cycle. Petition 870250090736, dated 06 / 10 / 2025, pp. 54 / 84 23 / 52 SR, the base station can determine that the SR is the enhanced SR that carries the high-priority escalation indication.

[0109] After determining that the enhanced SR is received, the base station allocates the first uplink grant resource to the terminal in a predefined accelerated allocation mode. The accelerated allocation mode is implemented based on the high-priority scheduling indication, and may include any one or a combination of more than one of the following four modes. It should be noted that there is no conflict between a plurality of combined modes. Therefore, all four modes can be combined for use.

[0110] 1. A first mode of fast allocation is separate allocation, specifically, an uplink lease resource is allocated separately for service data with the indication of high priority scheduling.

[0111] Specifically, in an existing uplink lease resource allocation mode, the terminal reports a sum of service data volumes to be sent on a plurality of logical channels to the base station, and the base station generates an uplink lease resource based on the sum of the data volumes and delivers the uplink lease resource to the terminal. After receiving the uplink lease resource, the terminal reallocates, based on a requirement of each logical channel, the uplink lease resource to each logical channel for use.

[0112] However, in this mode, the base station can separately allocate an uplink grant resource for the logical channel where the URLLC service data is located. In other words, after generating the uplink grant resource for the URLLC service data, the base station indicates that an allocation object for the uplink grant resource is the logical channel where the URLLC service data is located. Thus, after receiving the uplink grant resource, the terminal can directly allocate, based on the allocation object corresponding to the uplink grant resource, the uplink grant resource for the logical channel where the URLLC service data is located. The allocation object Petition 870250090736, dated 06 / 10 / 2025, page 55 / 84 24 / 52 can be specified in several ways, such as adding an allocation object identifier.

[0113] In separate allocation mode, a reallocation process (the reallocation process is included in an original scheduling procedure, and is specifically included in step 3 of the original scheduling procedure) from the terminal to the received uplink grant resource can be omitted, thereby simplifying a step 3 processing process in the original scheduling procedure, and further reducing scheduling procedure latency.

[0114] 2. A second method of fast allocation is to reduce the interval between sending uplink and downlink data. Specifically, after receiving the enhanced SR sent by the terminal, the base station reduces the time interval to send an uplink resource grant to the terminal.

[0115] Specifically, after receiving the enhanced SR uploaded by the terminal, the base station sends an uplink grant resource, which corresponds to the enhanced SR, to the terminal after a predefined time interval. For example, the base station receives the enhanced SR at time n, and the predefined time interval is 4. In this case, the base station sends an uplink grant resource to the terminal at time n+4. In this mode, the time interval is reduced. For example, the time interval is reduced from 4 to 2. In this way, the base station can send the uplink grant resource to the terminal more quickly. This also indicates that the terminal can quickly obtain the uplink grant resource.For ease of description, the time interval can be referred to as a predefined short time interval, indicating that the time interval for obtaining an uplink grant resource from the URLLC service is shorter than the time interval of another service.

[0116] With reference to the existing scheduling procedure, shown in Figure 1, the fast allocation mode can shorten a UL grant delivery processing in step 2 of the scheduling procedure.

[0117] 3. A third method of fast allocation is allocation of Petition 870250090736, dated 06 / 10 / 2025, page 56 / 84 25 / 52 priority, specifically, an uplink grant resource is allocated, preferentially, for service data with the indication of high priority scheduling.

[0118] Specifically, a plurality of terminals can send an SR to the same base station. Even if the same terminal has several types of service data to send, several types of SRs can also be sent to the base station on logical channels where different service data are located. Therefore, the base station can receive the various types of SRs at the same time.

[0119] In this mode, if the terminal defines an SR as an enhanced SR when sending URLLC service data, the enhanced SR carries a high-priority scheduling indication. After receiving the enhanced SR that includes the high-priority scheduling indication, the base station can determine that a service data priority corresponding to the SR is relatively high and preferentially allocate an uplink lease resource to the enhanced SR, thereby reducing the waiting latency of the scheduling procedure. With reference to the existing scheduling procedure shown in Figure 1, the fast allocation mode can shorten the delivery processing of a UL lease in step 2 of the scheduling procedure.

[0120] 4. A fourth mode of fast allocation is pre-allocation, specifically, an uplink grant resource is pre-allocated for service data with the indication of high priority scheduling.

[0121] As described above, the terminal continuously sends the enhanced SR to the base station based on a particular sending cycle. After the base station receives the enhanced SR, if the enhanced SR carries a high-priority scheduling indication, based on the allocation of an uplink grant resource of a corresponding size for the enhanced SR, the base station additionally pre-allocates some uplink grant resources. Thus, after receiving a subsequent enhanced SR sent by the terminal, the base station can directly send a pre-allocated uplink grant resource to the terminal, thereby saving generation time for the uplink grant resource and reducing the latency of the procedure. Petition 870250090736, dated 06 / 10 / 2025, page 57 / 84 26 / 52 Scheduling. With reference to the existing scheduling procedure shown in Figure 1, the fast allocation mode can shorten a processing step for delivering a UL grant in step 2 of the scheduling procedure. Alternatively, the base station can also send the pre-allocated uplink grant resource to the terminal when sending the uplink grant resource that corresponds to the enhanced SR. In this way, the terminal may not necessarily send an uplink grant resource requested by an SR, but directly send a BSR using a pre-allocated uplink grant resource. With reference to the existing scheduling procedure shown in Figure 1, in this way, a processing step 1 of sending an SR and step 2 of delivering a UL grant in the scheduling procedure can be omitted.

[0122] More specifically, a service data source can be of several different types. The service source refers to a specific type of service data. The volumes of service data generated based on different types of service sources can be different. Therefore, enhanced SR can additionally port a service data source type to provide a more accurate basis for the base station to pre-allocate a data volume.

[0123] In a real-world application, the base station can select any one or a combination of more than one of the four preceding fast allocation modes. Each fast allocation mode can reduce latency to some extent. A larger number of selected fast allocation modes can reduce latency more significantly.

[0124] S403: The terminal uploads a BSR to the base station using the UL lease.

[0125] It should be noted that if the base station selects the first fast scheduling mode, namely, separately allocating an uplink grant resource for service data with the high-priority scheduling indication, after receiving an uplink grant resource with an allocation object indication, the terminal directly allocates the uplink grant resource to a logical channel that corresponds to the allocation object indication. The allocation object indication Petition 870250090736, dated 06 / 10 / 2025, pp. 58 / 84 Allocation 27 / 52 is used to instruct the system to allocate the uplink grant resource for URLLC service data. In this case, the endpoint allocates, according to the allocation object indication, the uplink grant resource to the logical channel on which URLLC service data is allocated, so that the uplink grant resource is used by URLLC service data to upload the BSR.

[0126] S404: The base station sends a UL grant to the terminal. The UL grant is used by the terminal to upload service data.

[0127] S405: The terminal uploads service data using the UL lease.

[0128] After receiving the uplink grant resource UL delivered by the base station, the terminal uploads the URLLC service data using the received uplink grant resource UL.

[0129] It can be learned from the preceding technical solution that if a bit is added to an SR to carry a high-priority scheduling indication in this mode, this mode is applicable to a scenario in which PUCCH resources are extensible. If an SR carries a high-priority scheduling indication in an implicit mode, this mode is applicable to a scenario in which PUCCH resources are relatively limited, but a requirement for service data to be sent at a relatively high latency is required.

[0130] In this mode, the enhanced SR, sent by the terminal, carries the service data to be sent with the indication of high priority scheduling, and the base station quickly allocates an uplink grant resource for the URLLC service data, according to the high priority indication. The fast allocation mode can simplify the processing (e.g., the steps with bold cross lines in Figure 4) of step 2 and / or step 3 in the existing scheduling procedure shown in Figure 1, thereby reducing the latency of the existing scheduling procedure.

[0131] In mode 2, the high-priority escalation indication corresponding to URLLC service data is ported to the SR Petition 870250090736, dated 06 / 10 / 2025, page 59 / 84 28 / 52 enhanced in explicit or implicit mode. However, the high-priority escalation indication may not be carried in the enhanced SR, but it is carried in the BSR. Therefore, this request provides the following modality 3 for sending a high-priority escalation indication using a BSR. Mode 3

[0132] Figure 5 shows a procedure of embodiment 3 of a scheduling method, according to this request. The scheduling method specifically includes steps S501 through S505 below.

[0133] S501: A terminal sends an SR to a base station when URLLC service data needs to be sent.

[0134] An SR can include just one bit as an SR in an existing scheduling procedure, to notify the base station that the terminal needs to send service data.

[0135] S502: The base station sends a UL grant to the terminal.

[0136] The uplink resource grant UL is used by the terminal to upload a BSR.

[0137] S503: The terminal sends an enhanced BSR to the base station, where the enhanced BSR carries a high-priority escalation indication that corresponds to URLLC service data.

[0138] When determining the sending of URLLC service data, the terminal sets a high-priority scheduling indication for the URLLC service data, and adds a high-priority scheduling indication to the BSR. Specifically, the enhanced BSR can carry the high-priority scheduling indication in an explicit way. For example, a bit is added to the BSR to indicate the high-priority scheduling indication. The enhanced BSR carries, explicitly or implicitly, more information than an existing BSR, and the enhanced BSR is essentially a BSR.

[0139] Alternatively, the enhanced BSR can carry the high-priority escalation indication in an implicit mode. Specifically, the BSR is sent to the base station using a Physical Uplink Shared Channel (PUSCH), and the BSR has location information in the PUSCH resource during BSR transmission. The Petition 870250090736, dated 06 / 10 / 2025, pages 60 / 84 29 / 52 The terminal and the base station can agree on a location that corresponds to the high-priority service data in advance. When sending URLLC service data, the terminal can send a BSR to the predefined location in the PUSCH resource. Thus, after receiving the BSR, the base station can determine, based on information about the BSR's location in the PUSCH resource, that the BSR carries the high-priority escalation indication. For a description of the high-priority escalation indication, see the description in mode 2. The details are not described again in this document.

[0140] S504: The base station allocates a UL grant to the terminal in a fast allocation mode based on the high-priority scheduling indication ported to the enhanced BSR.

[0141] If the enhanced BSR carries the high-priority scheduling indication in explicit mode, after receiving the enhanced BSR, the base station can detect whether the enhanced BSR includes a priority indication and a bit with the priority indication being high. If so, an uplink resource is allocated to the terminal in a predefined fast allocation mode. For a description of the fast allocation mode, see the description in mode 2. The details are not described again in this document.

[0142] It should be noted that the base station can quickly allocate the uplink grant resource to the terminal based on the high-priority scheduling indication, and a difference from mode 2 is that the quickly allocated uplink grant resource is a second uplink grant resource. In this mode, if the first quick allocation mode in mode 2 is used, a step 5 processing process in the existing scheduling procedure can be simplified, and if any of the last three quick allocation modes is used, a step 4 processing process in the existing scheduling procedure can be simplified.

[0143] S505: The terminal uploads the service data to be sent using the UL lease.

[0144] The service data is URLLC service data.

[0145] It can be learned from the preceding technical solution that, Petition 870250090736, dated 06 / 10 / 2025, pp. 61 / 84 In this 30 / 52 mode, none of the information needs to be added to the SR. Therefore, this mode can be applied to a scenario where PUCCH resources are limited, but a requirement for relatively high service data latency is demanded.

[0146] As in mode 2, in this mode, a high-priority scheduling indication of service data to be sent is also sent. Therefore, the processing (e.g., the steps with bold cross lines in the figure) of step 4 and / or step 5 in the existing scheduling procedure can be simplified. Unlike mode 2, in this mode, the high-priority scheduling indication is carried in the BSR, instead of being carried in the SR.

[0147] In mode 1, buffer state information in the BSR is carried over to the SR, to omit steps 2 and 3. In mode 2, the high-priority scheduling indication is sent using the SR, to instruct the base station to quickly deliver the first uplink grant resource, to simplify a step 2 and / or step 3 procedure. In mode 3, the high-priority scheduling indication is sent using the BSR, to instruct the base station to quickly deliver the first uplink grant resource, to simplify a step 4 and / or step 5 procedure. There is no conflict between the implementations of these modes. Therefore, any two or three of the implementations can be combined to significantly reduce the latency of the existing scheduling procedure. Mode 4

[0148] The preceding embodiments are improvements to steps 3 to 5 in the existing escalation procedure. Research by the inventor has shown that it is possible to further optimize step 1 (submitting an SR) and step 2 (submitting a UL grant). Based on this concept of the invention, this application provides embodiment 4 below.

[0149] Figure 6 shows a procedure of embodiment 4 of a scheduling method, according to this application. The scheduling method specifically includes steps S601 to S603 below. Petition 870250090736, dated 06 / 10 / 2025, pp. 62 / 84 31 / 52

[0150] S601: A terminal sends a BSR to a base station using a pre-configured uplink feature when it needs to send URLLC service data.

[0151] The base station can pre-allocate some uplink grant resources for URLLC service data. For example, the base station pre-allocates uplink grant resources to the endpoint before a scheduling procedure. These uplink grant resources are used specifically for URLLC service data and therefore can be referred to as uplink grant resources. In one implementation, shared uplink resources can additionally be pre-configured on the endpoint. Shared uplink resources are provided for various types of service data for use, and are not provided specifically for URLLC service data for use.The terminal can contend for these shared uplink resources and, after obtaining these shared uplink resources through contention, the terminal can send the BSR using a shared uplink resource.

[0152] Both a preconfigured uplink grant resource and a preconfigured uplink shared resource can be referred to as a pre-allocated uplink resource (or a pre-stored uplink resource).

[0153] When it is necessary to send URLLC service data, the terminal selects a resource from the pre-allocated uplink resources to send the BSR. This method of sending a BSR using a pre-allocated uplink resource can be called a BSR enhancement method.

[0154] The fact that the terminal can implement the preceding function can be achieved based on a base station configuration. For the configuration mode, see the base station-enhanced SR configuration process. The following section provides only a brief description.

[0155] The base station may send an RRC connection reconfiguration message to the terminal during a connection process prior to the escalation procedure. The RRC connection reconfiguration message may include enhanced indication information, used to instruct Petition 870250090736, dated 06 / 10 / 2025, pp. 63 / 84 32 / 52 the terminal to send the BSR in BSR enhancement mode.

[0156] S602: The base station allocates a UL lease to the terminal based on buffer state information ported to the BSR.

[0157] The UL grant is used to send an uplink service data grant resource.

[0158] S603: The terminal sends service data to the base station using the UL lease.

[0159] The terminal sends URLLC service data to the base station using the uplink grant resource UL.

[0160] It can be learned from the preceding technical solution that, in the existing scheduling procedure, the terminal needs to apply for the UL grant from the base station using the SR. In this mode, the terminal pre-stores the uplink resources, and can directly and randomly select a resource from these resources to send the BSR, thus omitting step 1 of sending an SR and step 2 of sending a UL grant (the steps with dashed lines and “X” shown in Figure 6 are omitted steps), thereby reducing the latency of the scheduling procedure.

[0161] Furthermore, it is not necessary to occupy more PUCCH resources in this mode than in the bit-addition enhancement mode in an SR. Specifically, the terminal needs to send the SR using the PUCCH resource, and the more bits are included in the SR, the more PUCCH resources need to be used. However, in the scheduling procedure, the PUCCH resources for communicating with the base station are limited, and can be provided to a plurality of terminals for use. A larger amount of PUCCH resources occupied by a single terminal indicates a smaller number of terminals communicating with the base station.

[0162] It should be noted that, in mode 4, the terminal can send the BSR in a contender mode for an uplink resource for use. Specifically, if a plurality of terminals all need to send a BSR, the plurality of terminals contend for an uplink resource. Thus, if a terminal sends URLLC service data, the terminal's BSR may conflict with another terminal in the contention. Petition 870250090736, dated 06 / 10 / 2025, pp. 64 / 84 33 / 52 Consequently, the success rate of sending a BSR that matches the URLLC service data is relatively low. Therefore, to meet a URLLC service's requirement for data reliability, the BSR can be sent repeatedly in a pre-configured BSR repeated sending mode. As shown in Figure 7, a pre-defined repeated BSR sending mode is a mode in which the same BSR is sent repeatedly a plurality of times.

[0163] It should be noted that the mode of repeatedly sending the same BSR can be used in combination not only with mode 4, but the mode can be used in any mode in which there is a BSR to be sent, to alleviate the impact of channel fading, and additionally increase the success rate of receiving a BSR in a contention-based sending mode.

[0164] A specific BSR transmission mode may include, but is not limited to, the following modes. In a real application, which transmission mode should be used may be determined by the terminal, or it may be determined by the base station; specifically, the base station defines a transmission mode in the RRC connection reconfiguration message. The terminal receives the RRC connection reconfiguration message and repeatedly sends the BSR based on the transmission mode included in the RRC connection reconfiguration message.

[0165] 1. Dual Connectivity Mode (DC).

[0166] The mode is similar to frequency domain resource multiplexing, and the same BSR is sent over a plurality of connections between the terminal and the base station. A specific number of connections can be included in the RRC connection reconfiguration message.

[0167] 2. Carrier Aggregation (CA) mode.

[0168] The mode is similar to frequency domain resource multiplexing, and the same BSR is sent on a plurality of carriers. A specific number of carriers can be included in the RRC connection reconfiguration message.

[0169] 3. Transmission Time Interval-bundling (TTI-bundling) mode.

[0170] The mode is similar to time-domain multiplexing, and Petition 870250090736, dated 06 / 10 / 2025, pages 65 / 84 34 / 52 The same BSR is sent in a plurality of TTI groupings. A specific number of TTI groupings can be included in the RRC connection reconfiguration message.

[0171] 4. Multi-beam mode.

[0172] The mode is similar to domain-space multiplexing, and the same BSR is sent in a plurality of beams. A specific number of beams can be included in the RRC connection reconfiguration message.

[0173] It should be noted that the preceding mode of repeatedly sending the BSR can increase the success rate of sending the BSR, thereby improving the reliability of a service data transmission process. However, a greater number of times the BSR is sent indicates a longer time required by the terminal and the base station to process the BSR. This leads to an increase in the latency of the scheduling procedure. Therefore, to achieve a balance between latency and reliability, an appropriate number of repeated sends needs to be selected based on an actual application requirement. The appropriate number of repeated sends can be selected by the terminal or the base station. This is not specifically limited in this request. Mode 5

[0174] In some of the preceding embodiments, an SR is enhanced, and in some of the preceding embodiments, a BSR is enhanced. For example, in embodiment 1, buffer state information from an original BSR can be added to an SR. In embodiment 2, a high-priority scheduling indication of a service to be sent can be added to an SR. In embodiment 3, a high-priority scheduling indication of a service to be sent can be added to a BSR. In embodiment 4, a BSR is sent using a pre-configured uplink resource.

[0175] It should be noted that a PUCCH resource needs to be used to send the SR. However, the resource is a dedicated resource with a limited quantity. Specifically, the base station allocates respective PUCCH resources to each terminal, and the allocated PUCCH resources are limited. If an SR sent by a terminal carries more information, more Petition 870250090736, dated 06 / 10 / 2025, pp. 66 / 84 35 / 52 PUCCH resources need to be consumed. Therefore, transmission may fail and latency is relatively high due to limitations of PUCCH resources. On the other hand, there is a conflict between the allocation of the PUCCH resource to the terminal by the base station and the allocation of another resource, such as an uplink grant. If the PUCCH resource is always allocated to the terminal, the allocation of another resource to the terminal may be affected, impacting other communication processes.

[0176] Research by the inventor has shown that sending a BSR does not need to use the PUCCH resource and therefore can switch between an SR enhancement mode (a first scheduling mode) and a BSR enhancement mode (a second scheduling mode) to alleviate a restricted SR demand for the PUCCH resource. A specific switching mode is described in embodiment 5 below.

[0177] A terminal function can be defined before a mode 5 scheduling procedure is performed, so that the terminal can switch between the two sending modes when performing the scheduling procedure.

[0178] Specifically, the terminal can generate a switching function enable instruction and enable a switching function according to the instruction. Alternatively, a terminal switching function is defined by the base station. Specifically, in a connection process prior to the scheduling procedure, the base station can send an RRC connection reconfiguration message to the terminal. The RRC connection reconfiguration message can carry a switching function enable instruction. The instruction is used to cause the terminal to enable the switching function. The terminal whose switching function is enabled can implement the following forward mode switching in mode 5.

[0179] Figure 8 shows a procedure of embodiment 5 of an enhanced scheduling method, according to this request. The scheduling method specifically includes steps S801 through S805 below.

[0180] S801: After enabling a switching function, a terminal continuously detects whether the terminal needs to send URLLC service data.

[0181] A point in time at which the terminal enables the function of Petition 870250090736, dated 06 / 10 / 2025, pp. 67 / 84 36 / 52 Switching can occur before, during, or after a scheduling procedure is performed. For example, the terminal might receive an RRC connection reconfiguration message before the scheduling procedure and enable the switching function upon receiving the RRC connection reconfiguration message. Alternatively, the terminal might enable the switching function upon detecting that the scheduling procedure has begun. Yet another example might allow the terminal to enable the switching function at a point in time after the scheduling procedure has started. The point in time might be determined by the terminal or by the base station. For example, in addition to a switching function enable instruction, the RRC connection reconfiguration message sent by the base station might also include a point in time corresponding to the switching function enable instruction.In this case, the terminal executes the switching function enable instruction when the time point arrives, causing the terminal to enable the switching function.

[0182] The terminal can generate a detection instruction after enabling the switching function. The terminal can perform the following scheduling procedure, according to the detection instruction.

[0183] When service data needs to be sent, it is first determined whether the service data belongs to the predefined ultra-reliable, low-latency communications service data. If so, this indicates that the terminal currently needs to send URLLC service data. If not, this indicates that the terminal does not currently need to send URLLC service data.

[0184] S802: When needing to send URLLC service data, the terminal enables an SR enhancement mode to perform a scaling procedure based on the SR enhancement mode. In SR enhancement mode, an SR sent by the terminal to a base station is an enhanced SR.

[0185] If the service data is URLLC service data, the terminal needs to generate an enhanced SR and send the enhanced SR to the base station. Compared to an existing SR, in addition to indication information for sending service data, the enhanced SR includes additional information. This extra information can be referred to as information Petition 870250090736, dated 06 / 10 / 2025, pp. 68 / 84 37 / 52 newly added, and may include, but not limited to, any one or a combination of more than one of the following: buffer state information ported in an original BSR, a high-priority scheduling indication, and a service data type (namely, the antecedent service resource).

[0186] It should be noted that if the terminal enables SR enhancement mode, this indicates that the terminal can perform the scheduling procedure based on SR enhancement mode. Specifically, the enhanced SR includes different information, and the specific implementation processes of the SR enhancement mode are also different. If the enhanced SR sent by the terminal includes the buffer state information in the original BSR, the scheduling procedure in mode 1 is performed. If the enhanced SR sent by the terminal includes the indication of high priority scheduling or the type of service data (namely, the preceding service source), the scheduling procedure in mode 2 is performed.

[0187] The terminal sends the enhanced SR to the base station using PUCCH resources, and the PUCCH resources used are more than those used to send an existing SR. Therefore, this is applicable to a scenario where PUCCH resources are sufficient.

[0188] S803: The terminal counts the duration of the SR enhancement mode and, if the duration reaches the predefined duration, the terminal switches to a BSR enhancement mode to perform the scheduling procedure based on the BSR enhancement mode. In BSR enhancement mode, the terminal does not send SR to the base station.

[0189] After switching to SR enhancement mode in step S802, the terminal needs to account for the duration of the SR enhancement mode. It should be noted that, in this mode, in a real application, the terminal may switch between BSR enhancement mode and SR enhancement mode a plurality of times. The duration accounted for in this step is not the total duration of the SR enhancement mode, but the duration after the SR enhancement mode is enabled each time. In other words, each time the S802 step of switching to SR enhancement mode is performed, the duration accounted for is set to zero. Petition 870250090736, dated 06 / 10 / 2025, pp. 69 / 84 38 / 52

[0190] A specific implementation for accounting for the duration of SR enhancement mode can be timing using a timer or counting an SR transmission cycle. For example, the RRC connection reconfiguration message sent by the base station to the terminal includes a timer (e.g., an SR Enhancement Cycle Timer) and an SR transmission cycle, and the terminal continuously sends an enhanced SR based on the SR transmission cycle. After switching to SR enhancement mode, the terminal starts the timer to time or count a number of SR transmission cycles to implement the timing.

[0191] If the counted duration of the SR enhancement mode reaches the predefined duration (first predefined duration), the terminal switches to BSR enhancement mode. The terminal can perform the scheduling procedure based on the BSR enhancement mode. Importantly, in the send mode, the terminal does not send SR to the base station, thus reducing the use of PUCCH resources. The BSR enhancement mode can be the process in mode 4.

[0192] S804: When SR enhancement mode is enabled, if URLLC service data does not need to be sent, the duration of the URLLC service data that does not need to be sent is counted, and the terminal disables SR enhancement mode after the duration reaches the predefined duration.

[0193] To facilitate distinction, the duration accounted for in step S803 may be referred to as the first duration, and the default duration used for comparison is referred to as the first default duration; the duration accounted for in this step is referred to as the second duration, and the default duration used for comparison is referred to as the second default duration. The values ​​of the first default duration and the second default duration may be the same or may be different. This is not specifically limited in this application.

[0194] A method of accounting for the second duration may be the same as a method of accounting for the first duration. For example, timing is performed using the timer or the SR send cycle is accounted for. For a specific description, see a description of the first duration. The Petition 870250090736, dated 06 / 10 / 2025, pp. 70 / 84 39 / 52 details are not described again in this document.

[0195] When the terminal is in SR enhancement mode, if the terminal does not need to send URLLC service data for a long period of time, the terminal can disable SR enhancement mode to reduce the use of PUCCH resources.

[0196] S805: When SR enhancement mode is disabled, if the terminal detects that URLLC service data needs to be sent, the terminal enables SR enhancement mode to perform the escalation procedure based on SR enhancement mode.

[0197] When SR enhancement mode is disabled, if the terminal detects that URLLC service data needs to be sent, BSR enhancement mode can be temporarily implemented. In BSR enhancement mode, as described above, no SR is sent to the base station, thus reducing the use of PUCCH resources. When SR enhancement mode is disabled, if the terminal detects that URLLC service data needs to be sent, the terminal can alternatively re-enable SR enhancement mode to perform the scaling procedure based on SR enhancement mode.

[0198] It can be learned from the preceding technical solution that the terminal switches to BSR enhancement mode after SR enhancement mode remains active for a particular duration, to reduce the use of PUCCH resources. When no URLLC service data is being sent within a given time period, the terminal can disable SR enhancement mode, and re-enable SR enhancement mode when URLLC service data is being sent. SR enhancement mode requires a relatively large amount of PUCCH resources. Therefore, the terminal switches to BSR enhancement mode or disables SR enhancement mode to conserve PUCCH resources.

[0199] It should be noted that, in the preceding embodiments, an enhanced scheduling procedure is described from a service data perspective. For example, it is determined that a condition for performing an enhanced scheduling procedure is that there is service data from a URLLC service being sent. In this way, it can be ensured Petition 870250090736, dated 06 / 10 / 2025, pp. 71 / 84 40 / 52 that the enhanced scaling procedure can be performed when a service data type, such as service data from a URLLC service, is sent, to reduce scaling latency that corresponds to the service data type.

[0200] However, in this request, the enhanced scheduling procedure can alternatively be performed from a logical channel perspective. For example, it is determined that a condition for performing the enhanced scheduling procedure is that there is service data to be sent on a logical channel, so that the logical channel can be distinguished from another logical channel, and the enhanced scheduling procedure is performed to reduce the scheduling latency that corresponds to the logical channel. When the technical solution of this request is described from the logical channel perspective, all settings that correspond to the URLLC service are converted to settings that correspond to a target logical channel. For example, the high-priority scheduling indication is not an indication that corresponds to the URLLC service's service data, but an indication that corresponds to the target logical channel.

[0201] For ease of description, the logical channel can be referred to as a target logical channel. Service data from the URLLC service can be sent on the target logical channel. Of course, other types of service data can also be sent on the target logical channel. Furthermore, in this application, the target logical channel on the terminal is the logical channel that is not limited. The target logical channel can be a logical channel specified by the base station, or the target logical channel can be specified by the terminal. For example, the terminal specifies any logical channel as the target logical channel. As another example, the terminal specifies a logical channel that meets a predefined condition as the target logical channel. A specific implementation for specifying the logical channel that meets the predefined condition as the target logical channel is as follows.

[0202] The terminal determines whether a target parameter of the logical channel reaches a threshold that corresponds to the target parameter and, if so, specifies the logical channel as the target logical channel. The target parameter can be a parameter obtained in advance, or it can be a parameter collected in real time.

[0203] In one example, the target parameter could be a volume of Petition 870250090736, dated 06 / 10 / 2025, pp. 72 / 84 41 / 52 buffer data, and the limit corresponding to the target parameter is a buffer data volume limit. In another example, the target parameter is a rate of data arriving at a logical channel buffer unit, and the limit corresponding to the target parameter is a rate limit. In yet another example, the target parameter is the duration during which no available resources are allocated for data in the logical channel buffer unit, and the limit corresponding to the target parameter is a duration limit. Certainly, there may be other cases for the target parameter and the limit corresponding to the target parameter. This is not specifically limited in this request. Furthermore, the limit corresponding to the target parameter may be pre-configured by the base station, or it may be set based on a related parameter in a communication protocol. This is not specifically limited in this request.

[0204] It should be noted that, in addition to specifying the target logical channel for the terminal, the base station may additionally specify an enhanced scheduling method to be used for the terminal. For this purpose, this application provides a scheduling configuration method. As shown in Figure 9, the scheduling configuration method may include steps S901 through S903.

[0205] S901: The base station determines a logical channel that uses a predefined scheduling mode. The predefined scheduling mode is any one of the following three modes: a first scheduling mode, a second scheduling mode, and a mode that switches between the first scheduling mode and the second scheduling mode.

[0206] The first scheduling mode is a scheduling mode in which the terminal sends an enhanced scheduling request to the base station, and is also a scheduling mode in which the base station receives a scheduling request sent by the terminal. The enhanced scheduling request carries any one or more of the following: a scheduling indication, buffer state information, and a type of service data. When the first scheduling mode includes buffer state information, the first scheduling mode is the enhanced scheduling method in mode 1. When the first scheduling mode includes the high-priority scheduling indication or the type of service data, the first Petition 870250090736, dated 06 / 10 / 2025, pp. 73 / 84 42 / 52 scheduling mode is the enhanced scheduling method in mode 2.

[0207] The second scheduling mode is a scheduling mode in which the terminal sends a buffer status report to the base station using a pre-stored uplink resource, namely, the enhanced scheduling method in mode 4, and is also a scheduling mode in which the base station receives the buffer status report sent by the terminal using the pre-stored uplink resource.

[0208] The mode that switches between the first scheduling mode and the second scheduling mode is the enhanced scheduling method in mode 5.

[0209] S902: The base station sends a predefined scheduling mode identifier and a logical channel identifier to the terminal.

[0210] The base station can add the predefined scheduling mode identifier and the logical channel identifier to a logical channel connection reconfiguration message, a downlink control physical channel resource, or a media access control element, and send the logical channel connection reconfiguration message, the downlink control physical channel resource, or the media access control element to the terminal. Alternatively, the base station can add the predefined scheduling mode identifier and the logical channel identifier to another existing message or resource, and send that other existing message or resource to the terminal. Alternatively, the base station can directly send the predefined scheduling mode identifier and the logical channel identifier to the terminal.

[0211] S903: The terminal determines the logical channel that corresponds to the logical channel identifier as a target logical channel, and determines a scheduling mode that corresponds to the predefined scheduling mode identifier as a target scheduling mode.

[0212] The terminal can obtain both identifiers based on a mode in which the base station sends the identifier of the predefined scheduling mode and the identifier of the logical channel. Additionally, the terminal Petition 870250090736, dated 06 / 10 / 2025, pages 74 / 84 43 / 52 determines the logical channel indicated by the logical channel identifier as the target logical channel, and determines the scheduling mode that corresponds to the predefined scheduling mode identifier as the target scheduling mode, to perform an enhanced scheduling method that corresponds to the target scheduling mode.

[0213] In the scheduling configuration method provided in this application, the base station can configure the terminal so that the terminal can implement the scheduling method that corresponds to the determined scheduling mode.

[0214] In addition, this application provides, furthermore, a terminal, which includes a processing module, a sending module and a receiving module.

[0215] The processing module is configured to determine if there is service data to be sent on a target logical channel.

[0216] The sending module is configured to send a scheduling indication to a base station if the processing module determines that there is service data to be sent on the target logical channel, wherein the target logical channel is a logical channel specified by the base station, and the scheduling indication is used to instruct the base station to allocate an uplink lease resource to the target logical channel in a predefined allocation mode.

[0217] The receiver module is configured to receive the uplink lease resource sent by the base station.

[0218] In one implementation, when performing the step of sending the scheduling indication to the base station, the sending module is specifically configured to send a scheduling request to the base station, where the scheduling request carries the scheduling indication using a bit.

[0219] In one implementation, when performing the step of sending the escalation indication to the base station, the sending module is specifically configured to send an escalation request to the base station based on a predefined escalation request sending cycle, where the predefined escalation request sending cycle is shorter than a request sending cycle of Petition 870250090736, dated 06 / 10 / 2025, pp. 75 / 84 44 / 52 scheduling of a logic channel different from the target logic channel.

[0220] In one implementation, when performing the step of sending the scheduling indication to the base station, the sending module is specifically configured to send a buffer status report to the base station, where the buffer status report carries the scheduling indication using a bit.

[0221] In one implementation, when performing the step of sending the scheduling indication to the base station, the sending module is specifically configured to send a buffer status report to the base station at a predefined location on a shared physical uplink channel.

[0222] This application also provides a terminal, which includes a processing module, a sending module and a receiving module.

[0223] The processing module is configured to generate a scheduling request if there is service data to be sent on a target logical channel, where the target logical channel is a logical channel specified by a base station, and the scheduling request includes buffer state information.

[0224] The sending module is configured to send the scheduling request to the base station, where the buffer state information in the scheduling request is used by the base station to allocate an uplink lease resource.

[0225] The receiver module is configured to receive the uplink lease resource sent by the base station.

[0226] In one implementation, buffer state information includes data volume indication information, and data volume indication information includes: a data volume value of the service data; or a data volume index of the service data, where the data volume index is used to indicate a range of data volume of the service data.

[0227] This application also provides a terminal, which includes a processing module, a sending module and a receiving module.

[0228] The processing module is configured to determine if there is service data to be sent on a target logical channel. Petition 870250090736, dated 06 / 10 / 2025, pp. 76 / 84 45 / 52

[0229] The sending module is configured to send a buffer status report to a base station using a pre-configured uplink resource if the processing module determines that there is service data to be sent on the target logical channel, wherein the target logical channel is a logical channel specified by the base station, and the buffer status report is used by the base station to allocate an uplink lease resource to the target logical channel.

[0230] The receiver module is configured to receive the uplink lease resource sent by the base station.

[0231] In one implementation, when performing the step of sending the buffer status report to the base station using the pre-configured uplink feature, the sending module is specifically configured to send the same buffer status report to the base station a plurality of times using the pre-configured uplink feature.

[0232] This application also provides a terminal, which includes a receiver module and a processing module.

[0233] The receiver module is configured to receive a detection instruction.

[0234] The processing module is configured to continuously detect, after the receiving module receives the detection instruction, whether there is service data to be sent on a target logical channel of the terminal, where the target logical channel is a logical channel specified by a base station.

[0235] The processing module is further configured to enable a first predefined scheduling mode if there is service data to be sent on the target logical channel, wherein the first scheduling mode is a scheduling mode for sending a scheduling request, and the scheduling request carries any one or more of the following: a scheduling indication, buffer state information, and a type of service data.

[0236] The processing module is additionally configured to switch the first scheduling mode to a second predefined scheduling mode if the enabled duration of the first scheduling mode reaches the first predefined duration, where the second scheduling mode is a scheduling mode for sending a report. Petition 870250090736, dated 06 / 10 / 2025, pp. 77 / 84 46 / 52 buffer state for the base station using a pre-stored uplink resource.

[0237] In one implementation, the processing module is additionally configured to: after enabling the first scheduling mode, disable the first scheduling mode if there is no more service data to be sent on the target logical channel and the duration without service data reaches the second predefined duration.

[0238] In one implementation, the processing module is additionally configured to: after disabling the first scheduling mode, enable the first scheduling mode if it is detected that there is service data to be sent on the target logical channel.

[0239] This application also provides a base station, which includes a receiver module, a processing module and a transmission module.

[0240] The receiver module is configured to receive a scheduling indication sent by a terminal, wherein the scheduling indication is sent when there is service data to be sent on a target logical channel of the terminal, and the target logical channel is a logical channel specified by the base station or the terminal.

[0241] The processing module is configured to allocate an uplink grant resource to the target logical channel in a predefined allocation mode.

[0242] The sending module is configured to send the uplink grant resource to the endpoint.

[0243] In one implementation, when performing the step of allocating the uplink grant resource to the target logical channel in the predefined allocation mode, the processing module is specifically configured to allocate the uplink grant resource to the target logical channel separately.

[0244] In one implementation, when performing the step of allocating the uplink grant resource to the target logical channel in predefined allocation mode, the processing module is specifically configured to allocate the uplink grant resource to the target logical channel after a predefined short time interval, where the short time interval indicates a time interval of the target logical channel. Petition 870250090736, dated 06 / 10 / 2025, pp. 78 / 84 47 / 52 to obtain the uplink grant resource is less than a time interval of another logical channel.

[0245] In one implementation, when performing the step of allocating the uplink grant resource to the target logical channel in the predefined allocation mode, the processing module is specifically configured to preferentially allocate the uplink grant resource to the target logical channel after requests for uplink grant resource allocation that correspond to a plurality of logical channels are received.

[0246] In one implementation, when performing the step of allocating the uplink lease resource to the target logical channel in the predefined allocation mode, the processing module is specifically configured to allocate, based on a volume of service data on the target logical channel, more uplink lease resources to the target logical channel than to the data volume.

[0247] This order also provides a base station, which includes a processing module and a transmission module.

[0248] The processing module is configured to determine a logical channel that uses a predefined scheduling mode.

[0249] The sending module is configured to send a predefined scheduling mode identifier and a logical channel identifier to a terminal.

[0250] The default scheduling mode is any one of the following three modes: a first scheduling mode, a second scheduling mode, and a mode that switches between the first scheduling mode and the second scheduling mode, wherein the first scheduling mode is a scheduling mode in which the base station receives a scheduling request sent by the terminal, the scheduling request carrying any one or more of the following: a scheduling indication, buffer state information, and a type of service data, and the second scheduling mode is a scheduling mode in which the base station receives a buffer state report sent by the terminal using a pre-stored uplink resource.

[0251] In an implementation, when performing the step of sending the Petition 870250090736, dated 06 / 10 / 2025, pp. 79 / 84 48 / 52 Predefined scheduling mode identifier and logical channel identifier for the terminal, the sending module is specifically configured to send a logical channel connection reconfiguration message to the terminal, where the logical channel connection reconfiguration message includes the predefined scheduling mode identifier and the logical channel identifier.

[0252] In one implementation, when performing the step of sending the predefined scheduling mode identifier and the logical channel identifier to the terminal, the sending module is specifically configured to send a downlink control physical channel resource to the terminal, where the downlink control physical channel resource includes the predefined scheduling mode identifier and the logical channel identifier.

[0253] In one implementation, when performing the step of sending the predefined scheduling mode identifier and the logical channel identifier to the terminal, the sending module is specifically configured to send a media access control element to the terminal, where the media access control element includes the predefined scheduling mode identifier and the logical channel identifier.

[0254] This application also provides a terminal, which includes a receiver module and a processing module.

[0255] The receiver module is configured to receive a predefined scheduling mode identifier and a logical channel identifier that are sent by a base station, wherein the predefined scheduling mode is any one of the following three modes: a first scheduling mode, a second scheduling mode, and a mode that switches between the first scheduling mode and the second scheduling mode, wherein the first scheduling mode is a scheduling mode in which the terminal sends a scheduling request to the base station, the scheduling request carrying any one or more of the following: a scheduling indication, buffer state information, and a type of service data, and the second scheduling mode is a scheduling mode in which the terminal sends a buffer state report to the base station using a pre-stored uplink resource. Petition 870250090736, dated 06 / 10 / 2025, pages 80 / 84 49 / 52

[0256] The processing module is configured to: determine the logical channel that corresponds to the logical channel identifier as a target logical channel, and determine a scheduling mode that corresponds to the predefined scheduling mode identifier as the scheduling mode used by the terminal.

[0257] Figure 10 is a possible schematic structural diagram of a terminal. The terminal includes: A controller / processor 1001, a memory 1002, a communications interface 1003, an input device 1004, and an output device 1005. The processor 1001, the memory 1002, the communications interface 1003, the input device 1004, and the output device 1005 are connected to each other.

[0258] The controller / processor 1001 may be a general-purpose processor, for example, a central processing unit (CPU), a network processor (NP), or a microprocessor, or it may be an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of programs of solutions of the present invention, or it may be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete transistor or gate logic device, or discrete hardware component. Alternatively, the controller / processor 1101 may be a combination of processors that implement a computing function, for example, a combination of one or more microprocessors, or a combination of the DSP and a microprocessor. Specifically:

[0259] The terminal controller / processor 1001 can implement a processing module function in the preceding terminal, to perform the preceding scheduling method applied to a terminal and / or to another process of a technology described in this application.

[0260] Memory 1002 stores a program to execute the technical solutions of this request, and may additionally store an operating system and another application program. Specifically, the program may include program code, and the program code includes a computer operation instruction. More specifically, memory 1002 may be a Petition 870250090736, dated 06 / 10 / 2025, pages 81 / 84 50 / 52 read-only memory (ROM), a static storage device of another type that can store static information and an instruction, random access memory (RAM), a dynamic storage device of another type that can store information and an instruction, magnetic disk storage, or similar.

[0261] The 1003 communications interface can implement the functions of the sending module and the receiving module in the preceding terminal. The 1003 communications interface includes any device that uses a transceiver in order to communicate with another device or a communications network, for example, Ethernet, a radio access network (RAN), or a wireless local area network (WLAN).

[0262] The terminal's communications interface 1003 can receive information, such as a scheduling indication, a scheduling request, or a buffer status report sent by a base station, and send the received information to the controller / processor, and the controller / processor performs the upstream scheduling method applied to a terminal. Alternatively, the terminal's communications interface 1003 can receive an upstream link grant or similar resource sent by a base station.

[0263] Input device 1004 may include a device for receiving data and information entered by a user, for example, a keyboard, a light pen, a voice input device or a touch screen.

[0264] Output device 1005 may include a device that has the ability to transmit information to the user, for example, a display screen or a loudspeaker.

[0265] Figure 11 is a possible schematic structural diagram of a base station. The base station includes: A controller / processor 1101, a memory 1102, and a communications interface 1103. The processor 1101, the memory 1102, and the communications interface 1103 are connected to each other.

[0266] The controller / processor 1101 may be a general-purpose processor, for example, a central processing unit (CPU), a network processor (NP), or a microprocessor, or it may Petition 870250090736, dated 06 / 10 / 2025, pages 82 / 84 51 / 52 being an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of programs of solutions of the present invention, or it may be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic device, discrete transistor or gate logic device, or discrete hardware component. Alternatively, the controller / processor 1101 may be a combination of processors that implement a computing function, for example, a combination of one or more microprocessors, or a combination of the DSP and a microprocessor. Specifically:

[0267] The base station controller / processor 1101 can implement a processing module function in the preceding base station, to perform the preceding scheduling method applied to a base station and / or to another process of a technology described in this application.

[0268] Memory 1102 stores a program to execute the technical solutions of this application, and may additionally store an operating system and another application program. Specifically, the program may include program code, and the program code includes a computer operation instruction. More specifically, memory 1102 may be a read-only memory (ROM), a static storage device of another type that may store static information and an instruction, a random access memory (RAM), a dynamic storage device of another type that may store information and an instruction, a magnetic disk storage, or similar.

[0269] The 1103 communications interface can implement the functions of the transmitting module and the receiving module in the preceding base station. The 1103 communications interface includes any device that uses a transceiver in order to communicate with another device or a communications network, for example, Ethernet, a radio access network (RAN), or a wireless local area network (WLAN).

[0270] The base station's communications interface 1103 can receive information, such as a scheduling indication, a Petition 870250090736, dated 06 / 10 / 2025, pp. 83 / 84 52 / 52 A scheduling request or a buffer status report is sent by a terminal, and the received information is sent to the controller / processor, and the controller / processor performs the preceding scheduling method applied to a base station. The base station's communications interface 1103 can additionally send an uplink grant or similar resource to the terminal.

[0271] It should be noted that the modalities in this descriptive report are all described in a progressive manner, each modality highlights a difference from other modalities, and for equal or similar parts in the modalities, refer to those modalities.

[0272] It should be further noted that in this descriptive report, relational terms such as first and second are used only to distinguish one entity or operation from another, and do not necessarily require or imply that any actual relationship or sequence exists between those entities or operations. Furthermore, the terms include, comprise, or any other variant, are intended to encompass a non-exclusive inclusion, such that a process, method, article, or device that includes a list of elements includes not only those elements but also other elements not expressly listed, or additionally includes elements inherent to such process, method, article, or device. An element preceded by includes a... does not, without further restriction, exclude the presence of additional identical elements in the process, method, article, or device that includes the element.

[0273] The embodiments disclosed above are described to enable a person skilled in the art to implement or use this application. Various modifications made to the embodiments will be apparent to a person skilled in the art, and the general principles defined herein may also be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not intended to be limited to those embodiments illustrated in this descriptive report, but should be interpreted in the broader scope consistent with the innovative principles and features disclosed in this descriptive report. Petition 870250090736, dated 06 / 10 / 2025, page 84 / 84

Claims

1 / 4 CLAIMS 1. Scheduling method, applied to a terminal, CHARACTERIZED in that the method comprises: sending a scheduling indication to a base station if there is service data to be sent on a target logical channel, wherein the target logical channel is a logical channel specified by the base station or the terminal, and the scheduling indication is used to instruct the base station to allocate an uplink grant resource to the target logical channel in a predefined allocation mode; and receiving the uplink grant resource sent by the base station.

2. Scheduling method, according to claim 1, CHARACTERIZED in that sending a scheduling indication to a base station comprises: sending a scheduling request to the base station based on a predefined scheduling request sending cycle, wherein the predefined scheduling request sending cycle is shorter than a scheduling request sending cycle of a logical channel other than the target logical channel.

3. Scheduling method, applied to a terminal, CHARACTERIZED in that the method comprises: sending a buffer status report to a base station using a pre-configured uplink resource if there is service data to be sent on a target logical channel, wherein the target logical channel is a logical channel specified by the base station or the terminal, and the buffer status report is used by the base station to allocate an uplink lease resource to the target logical channel; and receiving the uplink lease resource sent by the base station.

4. Scheduling method, according to claim 3, CHARACTERIZED in that sending a buffer status report to a base station using a pre-configured uplink resource comprises: sending the same buffer status report to the base station a plurality of times using the pre-configured uplink resource.

5. Scheduling method, applied to a base station, CHARACTERIZED in that the method comprises: receiving a scheduling indication sent by a terminal, wherein the scheduling indication is sent when there is service data to be sent on a target logical channel of the terminal, and the target logical channel is a logical channel specified by the base station or the terminal; allocating an uplink lease resource to the target logical channel in a predefined allocation mode; and sending the uplink lease resource to the terminal.

6. Scheduling method, according to claim 5, CHARACTERIZED in that allocating an uplink grant resource to the target logical channel in a predefined allocation mode comprises: allocating the uplink grant resource to the target logical channel after a predefined short time interval, wherein the short time interval indicates that a time interval of the target logical channel to obtain the uplink grant resource is shorter than a time interval of another logical channel.

7. Terminal, CHARACTERIZED in that it comprises: a processing module, configured to determine whether there is service data to be sent on a target logical channel; a sending module, configured to send a scheduling indication to a base station if the processing module determines that there is service data to be sent on the target logical channel, wherein the target logical channel is a logical channel specified by the base station or the terminal, and the scheduling indication is used to instruct the base station to allocate an uplink grant resource to the target logical channel in a predefined allocation mode; and a receiving module, configured to receive the uplink grant resource sent by the base station.

8. Terminal, according to claim 7, CHARACTERIZED in that the sending module sending the scheduling indication to the base station comprises: Petition 870250090736, dated 06 / 10 / 2025, page 16 / 84 3 / 4 the sending module is configured to send a scheduling request to the base station based on a predefined scheduling request sending cycle, wherein the predefined scheduling request sending cycle is shorter than a scheduling request sending cycle of a logical channel other than the target logical channel.

9. Terminal, CHARACTERIZED in that it comprises: a processing module, configured to determine whether there is service data to be sent on a target logical channel; a sending module, configured to send a buffer status report to a base station using a pre-configured uplink resource if the processing module determines that there is service data to be sent on the target logical channel, wherein the target logical channel is a logical channel specified by the base station or the terminal, and the buffer status report is used by the base station to allocate an uplink lease resource to the target logical channel; and a receiving module, configured to receive the uplink lease resource sent by the base station.

10. Terminal, according to claim 9, CHARACTERIZED in that the sending module sends the buffer status report to the base station using the pre-configured uplink feature, comprising: the sending module is further configured to send the same buffer status report to the base station a plurality of times using the pre-configured uplink feature.

11. Base station, CHARACTERIZED by the fact that it comprises: a receiver module, configured to receive a scheduling indication sent by a terminal, wherein the scheduling indication is sent when there is service data to be sent on a target logical channel of the terminal, and the target logical channel is a logical channel specified by the base station or the terminal; a processing module, configured to allocate an uplink grant resource to the target logical channel in a predefined allocation mode; and a sending module, configured to send the uplink grant resource to the terminal.

12. Base station, according to claim 11, CHARACTERIZED in that the processing module allocating the uplink grant resource to the target logical channel in the predefined allocation mode comprises: the processing module is further configured to allocate the uplink grant resource to the target logical channel after a predefined short time interval, wherein the short time interval indicates that a time interval of the target logical channel to obtain the uplink grant resource is shorter than a time interval of another logical channel. Petition 870250090736, dated 06 / 10 / 2025, p. 18 / 84

Images