Communication method and apparatus

Abstract

The present application provides a communication method and an apparatus. In the method, during acquisition of an uplink grant by a terminal, the terminal determines that data arrives after a first time length, and by controlling the first time length to be greater than or equal to a second time length, the terminal sends a first SR before arrival of the data, thereby reducing a delay generated by an SR procedure during acquisition of the uplink grant by the terminal, and improving the efficiency of the terminal acquiring the uplink grant.

Description

A communication method and apparatus

[0001] This application claims priority to Chinese Patent Application No. 202410976937.6, filed on July 18, 2024, entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0003] Before sending uplink data to the network, a user equipment (UE) needs to obtain a network grant, also known as uplink grant. Currently, there are two ways for a UE to obtain uplink grant: configure grant (CG) and dynamic grant (DG).

[0004] CG refers to the long-term effective CG configuration issued to the UE via the network, allowing the UE to periodically obtain authorization for a fixed amount of data based on the CG configuration. It can be seen that CG is suitable for periodic services with relatively fixed data volumes, but not for non-periodic bursty services. DG refers to the process where, after receiving data, the UE first sends a scheduling request (SR) to the network, such as 1 bit. The UE then receives the SR response information, i.e., downlink control information (DCI), parses the DCI to obtain authorization for a smaller amount of data, mainly used by the UE to transmit a buffer status report (BSR), which indicates the amount of data waiting to be transmitted. After the UE transmits the BSR to the network, it receives the authorization for data transmission sent by the network based on the BSR. However, DG requires two rounds of signaling interaction, and the UE cannot send SR whenever it wants; it needs to wait for specific SR resources. Therefore, the DG process is too time-consuming and unsuitable for bursty services with high real-time requirements.

[0005] Therefore, for services that are sudden and have high real-time requirements, how to reduce the latency during the UE's acquisition of uplink authorization is an urgent technical problem that needs to be solved. Summary of the Invention

[0006] This application provides a communication method and apparatus that can reduce the latency during the UE's uplink authorization process.

[0007] Firstly, a communication method is provided. This method can be executed by a terminal, by a module applied to the terminal (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the terminal's functions. For ease of description, the following description assumes the method is executed by a terminal. The method includes: determining that data arrives after a first time length; sending a first SRSR to a network device, wherein the first SR is used to request authorized resources for a Transmission Buffer Status Report (BSR), and the BSR is used to request authorized resources for transmitting data; wherein the first time length is greater than or equal to a second time length, and the second time length is the time interval between determining that the data arrives after the first time length and sending the first SR.

[0008] Based on the method in the first aspect, during the process of the terminal obtaining uplink authorization, the terminal determines that the data will arrive after a first time length. By controlling the first time length to be greater than or equal to the second time length, the terminal sends the first SR before the data arrives, thereby reducing the latency generated by the SR process during the process of obtaining uplink authorization and improving the efficiency of the terminal obtaining uplink authorization.

[0009] The time interval between determining the arrival time of the data after the first time length and sending the first SR can be understood as the time difference between the moment when the terminal "determines" the action and the moment when the terminal "sends" the action. For example, if the terminal determines the arrival time of the data at time #1 (i.e., after the first time length) and sends the first SR at time #2, then the time difference between time #1 and time #2 is the second time length.

[0010] In one possible implementation, the communication method may further include: receiving first information from a network device, the first information instructing the network device to authorize a terminal to transmit resources for a BSR. The first time length is greater than or equal to the total time length of a second time length and a third time length, where the third time length is the time interval between sending the first SR and receiving the first information.

[0011] In other words, the terminal receives the first information in response to the first SR before the data arrives, which reduces the latency generated by the SR process during the acquisition of uplink authorization and improves the efficiency of the terminal in acquiring uplink authorization.

[0012] Optionally, the communication method may further include: determining that data has arrived, and sending a BSR to the network device based on first information; wherein the time of sending the BSR is later than the time of data arrival.

[0013] In this way, the data volume in the BSR is the actual data volume to be transmitted, which can avoid situations where there are insufficient authorized resources or waste of authorized resources.

[0014] In one possible implementation, before sending the first SR to the network device, the communication method may further include: sending capability information to the network device, the capability information indicating that the terminal has the capability to predict data arrival after a first time length. Here, the capability information indicates the terminal's predictive capability. After receiving the capability information, the network device can determine that the terminal's predictive capability is the first time length, or in other words, the terminal's predictive capability is the ability to predict data arriving after the first time length. Therefore, when the network device receives the first SR, it can determine that the terminal predicts that data is about to arrive, and that the arrival time of the data is after the first time length.

[0015] In this way, the terminal and network devices share the ability to predict data arrival time in advance, meaning that the terminal and network devices are aligned on the first time length. The network device can control the timing of sending the first information. For example, on the network device side, it can control the timing of receiving the first SR, sending the first information, and the first time length to ensure that the first time length is greater than or equal to the total time length of the second and third time lengths, thereby reducing the latency of the SR process. Furthermore, the ability to predict data arrival after the first time length places lower demands on the terminal's computing power. When the terminal's computing power is limited, uplink authorization can be obtained as quickly as possible for sudden real-time services.

[0016] Optionally, before sending the first SR to the network device, the communication method may further include: receiving resource configuration information from the network device for transmitting the first SR. Sending the first SR to the network device may include: sending the first SR to the network device based on the resource configuration information of the first SR.

[0017] The resource configuration information of the first SR can be periodically allocated to the terminal by the network device, and can be the resources used by the terminal after determining the arrival time of the data. The terminal ensures that the transmission of the first SR can be completed by receiving the resource configuration information of the first SR from the network device.

[0018] Optionally, the communication method may further include: receiving resource configuration information from a network device for transmitting a second SR; wherein the second SR is used to request authorized resources for transmitting a BSR after data arrives; the resource configuration information of the first SR is different from the resource configuration information of the second SR; and sending the second SR to the network device according to the resource configuration information of the second SR.

[0019] It is understandable that the second SR is used after the data actually arrives, and the resource configuration information of the second SR can be periodically allocated to the terminal by the network device. The period during which the network device allocates the resource configuration information of the first SR can be the same as or different from the period during which it allocates the resource configuration information of the second SR; there is no limitation. The terminal can use the first SR when the arrival time of the data is predicted, or it can use the second SR when the arrival time of the data cannot be predicted, which increases the flexibility of SR transmission.

[0020] Optionally, at least one parameter in the resource configuration information of the first SR differs from that of the resource configuration information of the second SR. This at least one parameter includes a time-domain resource location and / or a frequency-domain resource location. By distinguishing between the resource configuration information of the first SR and the second SR, the network device can differentiate whether the received data represents the first SR used when the terminal predicts data or the second SR used when the data actually arrives, thereby ensuring the accuracy of the use of the first and second SRs.

[0021] In another possible implementation, before sending the first SR to the network device, the communication method may further include: receiving resource configuration information from a plurality of SRs from the network device, each of the plurality of SRs being associated with a different time length, the plurality of SRs including a first SR, the time length associated with the first SR matching a first time length; sending the first SR to the network device may include: sending the first SR to the network device according to the resource configuration information of the first SR associated with the first time length.

[0022] It is understandable that the resource configuration information of multiple Service Providers (SRs) can be periodically allocated to terminals by network devices. The different time lengths associated with each SR represent different lead times for the terminal to predict data arrival. The lead times that a terminal can predict for data arrival may vary, such as the different prediction capabilities of the terminal under different services and / or different computing power conditions. Selecting the first SR based on the different time lengths associated with each SR among multiple SRs achieves flexibility in the use of different SRs among multiple SRs.

[0023] Optionally, different time lengths are related to predictive power, which is the ability to predict data to arrive after different time lengths.

[0024] Thus, the amount of advance time that a terminal can predict the arrival time of data may vary. For example, the predictive ability of a terminal may differ depending on the service and / or the computing power of the terminal. Network devices can issue multiple SRs to a terminal based on the terminal's predictive ability, thereby enabling the use of SRs in various possible scenarios.

[0025] Optionally, the time length associated with the first SR is greater than or equal to the first time length, and among the differences between the fourth time length and the first time length, the difference between the time length associated with the first SR and the first time length is the smallest. The fourth time length is the time length among multiple SR associations that is greater than or equal to the first time length. It can be understood that after the terminal determines that the data arrives after the first time length, selecting a first SR association with a time length greater than or equal to the first time length and closest to it can prevent the authorized resources from expiring before the data arrives after receiving the BSR's authorized resources.

[0026] Optionally, the resource configuration information parameters for every two SRs in the plurality of SRs may include at least one different parameter. This at least one different parameter may include time-domain resource location and / or frequency-domain resource location.

[0027] In other words, the resource configuration information of each pair of SRs is different. This means that SRs can be distinguished by their resource configuration information, and the terminal can then send an SR to the network device based on the resource configuration information of any given SR. Since the terminal and network device share the resource configuration information and associated time lengths of multiple SRs, meaning that the terminal and network device are aligned regarding the resource configuration information and associated time lengths of each SR, the network device can determine a unique SR based on the resource configuration information. For example, when the network device receives an SR, it can determine that the received SR is the first SR based on the time-domain resource location and / or frequency-domain resource location of the received SR, thereby improving the accuracy of using multiple SRs.

[0028] Secondly, a communication method is provided. This method can be executed by a network device, a module applied to the network device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of the network device. For ease of description, the following description uses the execution of the method by a network device as an example. The method includes: after the terminal determines that the data has arrived after a first time length, the network device receives a first SR from the terminal, the first SR being used to request authorized resources for a Transmission Buffer Status Report (BSR); the network device sends first information to the terminal according to the first SR, the first information instructing the network device to authorize the terminal to transmit the resources of the BSR; wherein, the first time length is greater than or equal to a second time length, the second time length being the time interval between the terminal determining that the data has arrived after the first time length and the network device receiving the first SR from the terminal.

[0029] Optionally, the first time length is greater than or equal to the third time length, where the third time length is the time interval between the network device receiving the first SR and the network device sending the first information.

[0030] Optionally, the communication method may further include: after the terminal determines that the data has arrived, the network device receives a BSR sent by the terminal according to the first information, wherein the BSR is used to request authorized resources for transmitting the data; wherein the time of receiving the BSR is later than the time when the data arrives at the terminal.

[0031] In one possible implementation, the communication method may further include: before the network device receives the first SR from the terminal, the method also includes:

[0032] The network device receives capability information from the terminal, which indicates that the terminal has the ability to predict when the data will arrive after a certain time period.

[0033] Optionally, before the network device receives the first SR from the terminal, the communication method may further include: the network device sending resource configuration information for transmitting the first SR and resource configuration information for transmitting the second SR to the terminal; wherein the resource configuration information of the first SR is used by the terminal to determine when the data arrives after a first time length, and the resource configuration information of the second SR is used when the data arrives at the terminal.

[0034] Optionally, the resource configuration information of the first SR differs from that of the resource configuration information of the second SR in at least one parameter, and the at least one parameter includes the time domain resource location and / or the frequency domain resource location.

[0035] Optionally, the network device receiving the first SR from the terminal may include: the network device determining the SR as the first SR based on the time-domain resource location and / or frequency-domain resource location of the received SR.

[0036] In another possible implementation, before the network device receives the first SR from the terminal, the communication method may further include: the network device sending resource configuration information of multiple SRs to the terminal, each of the multiple SRs being associated with a different time length, the multiple SRs including the first SR, and the time length associated with the first SR matching the first time length.

[0037] Optionally, different time lengths are related to predictive power, which is the ability to predict data to arrive after different time lengths.

[0038] Optionally, the time length associated with the first SR is greater than or equal to the first time length, and among the differences between the fourth time length and the first time length, the difference between the time length associated with the first SR and the first time length is the smallest. The fourth time length is the time length among the multiple SR associated time lengths that is greater than or equal to the first time length.

[0039] Optionally, the parameters of the resource configuration information for each two SRs in the plurality of SRs include at least one different parameter, the at least one different parameter including time-domain resource location and / or frequency-domain resource location.

[0040] It is understood that the technical effects of the method in the second aspect mentioned above can also be referred to the relevant introduction in the first aspect mentioned above, and will not be repeated here.

[0041] Thirdly, a communication method is provided. This method can be executed by a terminal, by a module applied to the terminal (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of implementing all or part of the terminal's functions. For ease of description, the following description uses the method executed by the terminal as an example. The method includes: when it is determined at a first moment that data arrives after a first time length, sending a scheduling request SR to a network device at a second moment, the SR being used to request authorized resources for a transmission buffer status report (BSR); receiving first information from the network device, the first information instructing the network device to authorize the terminal to transmit the BSR resources; after the data arrives, sending a first BSR to the network device according to the first information, the first BSR being used to request authorized resources for transmitting the data; wherein, the second moment is earlier than the moment the data arrives; the first time length is greater than or equal to the total time length of the second time length and the third time length; the second time length is the time difference between the first moment and the second moment, and the third time length is the predicted time interval from sending the first SR to receiving the first information.

[0042] Based on the third approach, by defining the relationship between the first, second, and third time lengths, the second moment when the terminal sends the SR to the network device can be determined. This allows the terminal to receive the first information before the data arrives, thus authorizing the terminal to transmit the resources of the first BSR. In this way, without the cooperation of the network device, and without the network device being aware of the first time length or needing to control the timing of sending the first information, the latency generated in the SR process can be reduced.

[0043] Optionally, the first time length is less than or equal to the total time length of the second, third and fourth time lengths, where the fourth time length is the time interval between receiving the first information and sending the first BSR.

[0044] Thus, after predicting the third time length, the terminal determines the second time to send the SR to the network device by using the difference between the first time length and the third and fourth time lengths, as well as the first time. This allows the terminal to receive the data after receiving the first information and prepare to send the BSR based on the amount of data.

[0045] Optionally, the terminal sending the first SR to the network device at the second time point may include: triggering a second BSR before the second time point, wherein the data content in the second BSR is 0; and triggering the sending of the first SR to the network device based on the second BSR. It can be understood that when the terminal determines at the first time point that the data has arrived after the first time length, it triggers an "empty" second BSR, i.e., the data content in the second BSR is 0, thereby triggering the SR and sending the SR to the network device at the second time point.

[0046] Optionally, after data arrives, sending a first BSR to the network device based on the first information may include: generating a first BSR based on the data volume after data arrival, wherein the first BSR and the second BSR are different Media Access Control Elements (MAC CEs); and sending the first BSR to the network device based on the first information. The first BSR and the second BSR are different MAC CEs. For example, when data actually arrives at the UE, the UE regenerates a BSR based on the actual data volume and transmits the regenerated BSR. This provides different methods for generating the first BSR.

[0047] Optionally, after data arrives, sending a first BSR to the network device based on the first information may include: updating the data quantity (0) in the second BSR to the actual data quantity to obtain the first BSR, where the second BSR and the first BSR share the same MAC CE; and sending the first BSR to the network device based on the first information. The second BSR and the first BSR share the same MAC CE, but the values ​​related to the data quantity in the second BSR and the first BSR differ. For example, when data actually arrives at the UE, the UE rewrites the values ​​in the "empty" BSR based on the actual data quantity and transmits the rewritten BSR. This provides different methods for generating the first BSR.

[0048] Fourthly, a communication device is provided. The communication device includes a processor configured to perform the method according to any one of the embodiments of the first to third aspects.

[0049] In one possible implementation, the communication device described in the fourth aspect may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the fourth aspect and other communication devices.

[0050] In one possible implementation, the communication device described in the fourth aspect may further include a memory. This memory may be integrated with the processor or disposed separately. The memory may be used to store computer programs and / or data relating to the methods of any of the embodiments of the first to third aspects.

[0051] Furthermore, the technical effects of the communication device described in the fourth aspect can be referred to the technical effects of any of the embodiments in the first to third aspects, and will not be repeated here.

[0052] Fifthly, a communication device is provided. The communication device includes a processor coupled to a memory, the processor being configured to execute a computer program or instructions stored in the memory, such that the communication device performs the method of any one of the embodiments of the first to third aspects.

[0053] In one possible implementation, the communication device may further include a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device and other communication devices.

[0054] In one possible implementation, the communication device further includes the memory for storing the aforementioned computer program or instructions. Optionally, the memory and processor are integrated together.

[0055] Furthermore, the technical effects of the communication device described in the fifth aspect can be referred to the technical effects of any of the embodiments in the first to third aspects, and will not be repeated here.

[0056] A sixth aspect provides a communication system. The communication system includes: a terminal for performing the method described in any one of the first and third aspects, and a network device for performing any one of the second aspects.

[0057] A seventh aspect provides a computer-readable storage medium comprising: a computer program or instructions; which, when executed, cause the method of any of the embodiments of the first to second aspects described above to be implemented, or cause the method of any of the embodiments of the third aspect described above to be implemented.

[0058] Eighthly, a computer program product is provided, comprising a computer program or instructions that, when executed, cause the method as described in any of the embodiments of the first to second aspects above to be implemented, or cause the method as described in any of the embodiments of the third aspect above to be implemented. Attached Figure Description

[0059] Figure 1 is a flowchart of CG;

[0060] Figure 2 is a schematic diagram of the DG process;

[0061] Figure 3 is a schematic diagram of the process by which a UE obtains uplink authorization;

[0062] Figure 4 is a schematic diagram of the enhanced DG process;

[0063] Figure 5 is a flowchart illustrating the enhanced CG process;

[0064] Figure 6 is a schematic diagram of the communication system provided in an embodiment of this application;

[0065] Figure 7 is a schematic diagram of the communication system provided in an embodiment of this application;

[0066] Figure 8 is a schematic diagram of the communication method provided in an embodiment of this application;

[0067] Figure 9 is a schematic diagram of the communication method provided in an embodiment of this application (II).

[0068] Figure 10 is a schematic diagram of the communication method provided in the embodiment of this application;

[0069] Figure 11 is a schematic diagram of the communication method provided in the embodiment of this application;

[0070] Figure 12 is a schematic diagram of the communication method provided in the embodiment of this application.

[0071] Figure 13 is a schematic diagram of the communication device provided in an embodiment of this application;

[0072] Figure 14 is a schematic diagram of the structure of the communication device provided in the embodiment of this application. Detailed Implementation

[0073] The technical solutions of this application embodiment can be applied to various communication systems, such as Wireless Fidelity (Wi-Fi) systems, vehicle-to-everything (V2X) communication systems, device-to-device (D2D) communication systems, vehicle-to-everything (V2X) communication systems, fourth-generation (4G) mobile communication systems, such as long-term evolution (LTE) systems, worldwide interoperability for microwave access (WiMAX) communication systems, fifth-generation (5G) mobile communication systems, such as new radio (NR) systems, and future communication systems.

[0074] For ease of understanding, the technical terms involved in the embodiments of this application will be introduced below.

[0075] 1. Authorization (grant)

[0076] Uplink grant (UL grant) is a physical control message from the network (eNB) used by network devices (such as base stations) to instruct the UE to transmit uplink data, or in other words, to instruct the UE to transmit uplink data after 4ms, i.e., after 4 subframes. The uplink grant is transmitted on the physical downlink control channel (PDCCH). When the UE receives the uplink grant, it transmits uplink data to the network device.

[0077] In other words, before transmitting uplink data, the UE needs to obtain uplink authorization in advance and needs to transmit uplink data according to the time and data volume indicated by the network device.

[0078] Currently, there are two ways for UEs to obtain authorization: configure grant (CG) and dynamic grant (DG).

[0079] 2. CG

[0080] Figure 1 is a flowchart illustrating the CG (Current Access Control) process. As shown in Figure 1, the network (NW) sends long-term valid CG configuration information to the UE based on service characteristics. During the validity period of the CG configuration information, the UE can periodically obtain authorized resources for a fixed amount of data. Therefore, after the periodic data arrives (as shown in Figure 1, data arrives at intervals T), the UE can transmit data to the network within a short time based on this authorized resource. It can be seen that CG is suitable for periodic services with relatively fixed data volumes. However, CG is not suitable for non-periodic bursty services. After the data from a bursty service arrives, the UE will not have authorized resources to transmit data, resulting in a significant waste of air interface resources.

[0081] 3. DG

[0082] Figure 2 is a flowchart of DG. As shown in Figure 2, the DG process is as follows:

[0083] S201, the UE received the data.

[0084] The data received by the UE means that the data actually arrives at the UE.

[0085] S202, UE triggers BSR.

[0086] BSR is used to indicate the amount of data that the network is waiting to transmit in the UE buffer.

[0087] S203, the UE sends an SR to the network.

[0088] Transmitting a BSR requires authorized resources; therefore, the UE will further trigger an SR based on the BSR. An SR is usually a simple signal, such as 1 bit. Since the network allocates some periodic SR resources to the UE, the UE can send an SR to the network through these SR resources.

[0089] T1 is the time interval between when the UE receives data and when the UE sends an SR to the network. It is usually half of the SR period, where the SR period is 20 to 80 ms. That is to say, T1 is usually 10 to 40 ms.

[0090] S204, the network sends DCI information #1 to the UE.

[0091] DCI information #1 is the network response SR information. DCI information #1 includes authorized resource #1, which is mainly used by the UE to transmit BSR. After the network receives the UE's SR signal, it will first allocate a smaller authorized resource #1 to the UE, meaning that the authorized UE can transmit a smaller amount of data corresponding to authorized resource #1.

[0092] T2 is the time interval between receiving the SR from the network and sending the DCI information #1 to the UE from the network, which usually depends on the network scheduling time.

[0093] S205, the UE transmits the BSR to the network.

[0094] The UE transmits the BSR to the network according to the authorized resource #1.

[0095] K2 represents the time interval between the UE receiving DCI#1 and sending the BSR. After receiving DCI#1, the UE needs to decode the DCI#1 instruction internally before preparing for transmission and actually sending the data. K2 represents the time consumed in this process. K2 is typically 4 slots, with each slot being 0.5ms in the classic configuration; therefore, K2 is usually 2ms.

[0096] The time interval between the UE sending an SR to the network and the UE transmitting a BSR to the network is K2+T2, which is usually around 5ms.

[0097] S206, the network sends DCI information #2 to the UE.

[0098] DCI information #2 includes authorized resource #2, which is mainly used for UE data transmission. After the UE transmits the BSR, the network allocates authorized resource #2 for data transmission to the UE based on the information in the BSR. The information in the BSR may include the amount of data waiting to be transmitted in the UE's buffer. In other words, the network configures authorized resource #2 based on the data volume information in the BSR.

[0099] T3 is the time interval between receiving the BSR from the network and sending the DCI information #2 to the UE from the network, which usually depends on the network scheduling time.

[0100] S207, the UE sends data to the network.

[0101] The UE sends data to the network based on the authorized resource #2 in the DCI information #2.

[0102] The time interval between the UE transmitting the BSR to the network and the UE sending data to the network is K2+T3, which is usually around 5ms.

[0103] It can be seen that Direct Generation (DG) is suitable for non-periodic, bursty services. However, DG requires two rounds of signaling interaction, with each DG process taking approximately 20-50ms. Furthermore, in the current network, the UE often needs to send 3-4 Signaling Messages (SRs) to successfully receive the DCI information sent by the network, so each DG process takes about 100ms. Moreover, the UE cannot send SRs whenever it wants; it needs to wait for specific SR resources. Therefore, the DG process is too time-consuming and unsuitable for bursty services with high real-time requirements.

[0104] The following describes two current procedures for UEs to obtain uplink authorization for services with sudden and high real-time requirements. Both methods require the UE to have predictive capabilities to achieve data transmission, such as the predictive capabilities of artificial intelligence (AI).

[0105] Method 1:

[0106] Figure 3 illustrates the process of a UE obtaining uplink authorization. As shown in Figure 3, the process of a UE obtaining uplink authorization is as follows:

[0107] S300, relevant information about UE prediction data.

[0108] The relevant information may include the time T1 when the data arrives and the amount of data A. Optionally, the relevant information may include whether the data has periodic characteristics and the length of the period.

[0109] S301, the UE sends a predicted BSR to the base station.

[0110] The Predicted BSR, also known as the Predicted Buffer Status Report (eBSR), is a message sent by the UE to the base station containing information about the predicted data.

[0111] S302, the base station sends authorized resource #1 to the UE.

[0112] Authorized resource #1 is determined based on relevant data information. After time T1, the base station provides the terminal with authorized resource #1 containing data A, ensuring that when the data arrives at the UE, the UE has available authorized resource #1, meaning the waiting time for the data to arrive at the UE is 0ms.

[0113] S303, the UE sends data to the base station.

[0114] The UE sends data to the base station according to authorized resource #1.

[0115] S304, the base station sends authorized resource #2 to the UE.

[0116] S304 is an optional step. If the data has periodic characteristics, the base station will periodically send authorized resources to the UE. Authorized resource #2 is the same as authorized resource #1.

[0117] S305, the UE sends data to the base station.

[0118] S305 is an optional step. If S304 is executed, then S305 is executed; otherwise, S305 is not executed.

[0119] Method 2:

[0120] The enhanced DG process is obtained by combining periodic cadence reports (PCR) with data collection (DG), and the enhanced CG process is obtained by combining PCR with traffic characteristics (CG). PCR is used to report the traffic characteristics of the UE's services. Figure 4 shows a schematic diagram of the enhanced DG process. As shown in Figure 4, the process is as follows:

[0121] S401, the network sends uplink grant resource #1 to the UE.

[0122] Uplink grant resource #1 is used by the UE to send PCR. Uplink grant resource #1 can be referred to as grant resource #1 in S204, and will not be elaborated further.

[0123] S402, the UE determines that the buffer is empty.

[0124] S403, the UE sends a PCR to the network.

[0125] PCR indicates the arrival time and amount of uplink data predicted by the UE.

[0126] S404, the network sends uplink grant resource #2 to the UE.

[0127] The network provides uplink authorization resources #2 to the UE based on the arrival time and data volume of the uplink data, ensuring that there are available authorization resources when the uplink data arrives at the UE.

[0128] S405, the UE sends uplink data to the network according to uplink authorization resource #2.

[0129] When uplink data arrives at the UE, the UE has available uplink grant resource #2, meaning the data waiting for the grant resource is 0ms.

[0130] Figure 5 is a flowchart illustrating the enhanced CG process. As shown in Figure 5, the process is as follows:

[0131] S501, the network sends uplink grant resource #1 to the UE.

[0132] Uplink grant resource #1 is used by the UE to send PCR. Uplink grant resource #1 can be referred to as grant resource #1 in S204, and will not be elaborated further.

[0133] S502, the UE determines that the buffer is empty.

[0134] S503, the UE sends a PCR to the network.

[0135] PCR indicates the arrival time and data volume A of the uplink data predicted by the UE. Optionally, PCR indicates the periodicity of the uplink data.

[0136] S504, network selection: CG configuration.

[0137] The network selects the CG configuration based on the periodic characteristics of uplink data. For example, if uplink data arrives at the UE every T time interval, the CG configuration includes sending an authorized resource of A data volume to the UE every T time interval.

[0138] S505, the network sends DCI information to the UE.

[0139] The network sends DCI information to the UE according to the CG configuration.

[0140] S506, the UE obtains uplink authorized resources #2 from the network according to the CG configuration.

[0141] The UE periodically obtains uplink grant resource #2 from the network according to the CG configuration, and the amount of data granted by uplink grant resource #2 matches the amount of uplink data arriving at the UE.

[0142] S507, the UE sends uplink data to the network according to uplink authorization resource #2.

[0143] The network provides the CG configuration to the UE before the uplink data arrives. The time when the CG configuration takes effect coincides with the predicted time when the uplink data arrives at the UE, which can achieve a 0ms authorization wait.

[0144] However, both of these methods require the UE to accurately predict the amount of data that is about to arrive, which places high demands on the UE's predictive computing power, and the accuracy of the UE's prediction is relatively low. When the UE's computing power is insufficient, it cannot quickly obtain uplink authorization for sudden real-time services.

[0145] To address the aforementioned technical problems, the embodiments of this application propose the following technical solutions.

[0146] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0147] In the embodiments of this application, "instruction" can include direct and indirect instructions, as well as explicit and implicit instructions. The information indicated by a certain piece of information is called the information to be instructed. In the specific implementation process, there are many ways to instruct the information to be instructed, such as, but not limited to, directly instructing the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly instruct the information to be instructed by instructing other information, where there is a correlation between the other information and the information to be instructed. It can also instruct only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various pieces of information, thereby reducing instruction overhead to some extent. At the same time, common parts of various pieces of information can be identified and uniformly indicated to reduce the instruction overhead caused by individually indicating the same information.

[0148] Furthermore, the specific instruction method can also be any existing instruction method, such as, but not limited to, the above-mentioned instruction methods and their various combinations. As described above, for example, when multiple pieces of information of the same type need to be indicated, the instruction methods for different pieces of information may differ. In the specific implementation process, the required instruction method can be selected according to specific needs. This application embodiment does not limit the selected instruction method. Therefore, the instruction methods involved in this application embodiment should be understood to cover various methods that enable the party to be instructed to obtain the information to be indicated.

[0149] It should be understood that the information to be indicated can be sent as a whole or divided into multiple sub-information messages sent separately, and the sending period and / or timing of these sub-information messages can be the same or different. The specific sending method is not limited in this application embodiment. The sending period and / or timing of these sub-information messages can be predefined, for example, according to a protocol, or configured by the sending node device by sending configuration information to the receiving node device.

[0150] In this application, "sending information" can be understood as one device sending information to another device, or it can also be understood as one logical module within a device sending information to another logical module. For example, "network device sending information" can be understood as a network device sending information to another device (such as a terminal or other network device), or it can be understood as logical module 1 in the network device sending information to logical module 2 in the network device.

[0151] In this application, "receiving information" can be understood as one device receiving information from another device, or it can also be understood as a logical module within a device receiving information from another logical module. For example, "network device receiving information" can be understood as a network device receiving information from another device (such as a terminal or other network device), or it can be understood as logical module 1 in the network device receiving information from logical module 2 in the network device.

[0152] In this application, phrases such as "sending information to... (e.g., a terminal)" or related illustrations in the accompanying drawings can be understood as indicating that the destination of the information is a terminal. This can include sending information directly or indirectly to a terminal. Similarly, phrases such as "receiving information from... (e.g., a terminal)," "receiving information from... (e.g., a terminal)," or "receiving information sent by (e.g., a terminal)," or related illustrations in the accompanying drawings, can be understood as indicating that the source of the information is a terminal. This can include receiving information directly or indirectly from a terminal. Information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be interpreted similarly and will not be elaborated further here.

[0153] "Predefined" or "pre-configured" can be achieved by pre-saving corresponding codes, tables, or other means that can be used to indicate relevant information in the device. This application does not limit the specific implementation method. "Saving" can refer to saving in one or more memories. These memories can be separate installations or integrated into the encoder, decoder, processor, or communication device. Alternatively, some memories can be separately installed, while others are integrated into the decoder, processor, or communication device. The type of memory can be any form of storage medium, and this application does not limit this.

[0154] The “protocol” mentioned in the embodiments of this application may refer to a protocol family in the field of communication, a standard protocol with a similar protocol family frame structure, or a related protocol applied to future communication systems. The embodiments of this application do not specifically limit this.

[0155] In the embodiments of this application, descriptions such as "when," "under the circumstances," "if," and "if" all refer to the device making corresponding processing under certain objective circumstances, and are not limited to a specific time. They do not require the device to make a judgment action during implementation, nor do they imply any other limitations.

[0156] In the description of the embodiments of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in the embodiments of this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of the embodiments of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Additionally, to facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with essentially the same function and effect. Those skilled in the art will understand that the terms "first," "second," etc., do not limit the quantity or order of execution, and that "first," "second," etc., are not necessarily different. Furthermore, in the embodiments of this application, words such as "exemplary" or "for example" are used to indicate that something is being used as an example, illustration, or description. Any embodiment or implementation described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or implementations. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner for ease of understanding.

[0157] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0158] To facilitate understanding of the embodiments of this application, the communication system applicable to the embodiments of this application will be described in detail first using the communication system shown in FIG6 as an example. For example, FIG6 is a schematic diagram of the architecture of a communication system to which the method provided in the embodiments of this application is applicable.

[0159] As shown in Figure 6, the communication system mainly includes terminals and network equipment.

[0160] In one possible scenario, this communication system can be applied to 5G or future communication systems. For example, as shown in Figure 7, the communication system 10 includes a RAN 100, a core network (CN) 200, and an Internet 300. RAN 100 includes at least one RAN node (as shown in Figure 7, 110a and 110b, collectively referred to as 110) and at least one terminal (as shown in Figure 7, 120a-120j, collectively referred to as 120). RAN 100 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment (not shown in Figure 7). Terminal 120 is wirelessly connected to RAN node 110. RAN node 110 is wirelessly or wired connected to core network 200. The core network equipment in core network 200 and RAN node 110 in RAN 100 can be different physical devices, or they can be the same physical device integrating core network logical functions and wireless access network logical functions.

[0161] RAN 100 can be a 3GPP-related cellular system, such as a 4G or 5G mobile communication system, or a future-oriented evolution system (such as a future mobile communication system). RAN 100 can also be an open access network (open RAN, O-RAN, or ORAN), a cloud radio access network (CRAN), or a Wi-Fi system. RAN 100 can also be a communication system that integrates two or more of the above systems.

[0162] RAN node 110, sometimes also referred to as access network equipment, RAN entity, or access node, constitutes part of the communication system and is used to help terminals achieve wireless access. Multiple RAN nodes 110 in communication system 10 can be of the same type or different types. In some scenarios, the roles of RAN node 110 and terminal 120 are relative. For example, network element 120i in Figure 7 can be a helicopter or drone, which can be configured as a mobile base station. For terminals 120j accessing RAN 100 through network element 120i, network element 120i is a base station; but for base station 110a, network element 120i is a terminal. RAN node 110 and terminal 120 are sometimes both referred to as communication devices. For example, network elements 110a and 110b in Figure 7 can be understood as communication devices with base station functions, and network elements 120a-120j can be understood as communication devices with terminal functions.

[0163] In one possible scenario, the RAN node can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB), a next-generation base station in a future mobile communication system, a base station in a future mobile communication system, or an access point (AP) in a Wi-Fi system. The RAN node can be a macro base station (as shown in Figure 7, 110a), a micro base station or indoor station (as shown in Figure 7, 110b), a relay node or donor node, or a radio controller in a CRAN scenario. Optionally, the RAN node can also be a server, wearable device, vehicle, or in-vehicle equipment. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). All or part of the functions of the RAN node in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (e.g., a cloud platform). The RAN node in this application can also be a logical node, logical module, or software capable of implementing all or part of the RAN node functions.

[0164] In another possible scenario, multiple RAN nodes collaborate to assist the terminal in achieving wireless access, with different RAN nodes each implementing a portion of the base station's functions. For example, RAN nodes can be CUs, DUs, CUs (control plane, CP), CUs (user plane, UP), or radio units (RUs). CUs and DUs can be configured separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio frequency equipment or radio frequency units, such as RRUs, active antenna units (AAUs), or remote radio heads (RRHs).

[0165] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules.

[0166] It is understood that the RAN node mentioned above can be a newly defined name, and RAN nodes can also be described in different ways, such as access node, network device, wireless access node, etc., without limitation. Unless otherwise specified in this application, network device will be used as the term.

[0167] A terminal can also be called a terminal device, user equipment (UE), mobile station, mobile terminal, etc. Terminals can be widely used in various scenarios, such as device-to-device (D2D), V2X communication, machine-type communication (MTC), Internet of Things (IoT), point-of-sale (POS) machines, customer-premises equipment (CPE), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables (e.g., smartwatches, smart bracelets, pedometers, smart glasses), smart transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicle devices (e.g., vehicle units, in-vehicle modules, in-vehicle chips, on-board units (OBUs) or telematics boxes (T-BOXs)), drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, satellite terminals, etc. The embodiments of this application do not limit the device form of the terminal.

[0168] In this communication system, during the process of obtaining uplink authorization, the terminal determines that the data will arrive after a first time length. By controlling the first time length to be greater than or equal to a second time length, the terminal sends the first SR before the data arrives, thereby reducing the latency caused by the SR process during the acquisition of uplink authorization and improving the efficiency of the terminal in obtaining uplink authorization.

[0169] The interaction process between various network elements / devices in the above-described communication system will be specifically described below with reference to Figures 8-10 through method embodiments. The communication method provided in this application embodiment can be applied to the above-described communication system and specifically applied to various scenarios / processes mentioned in the above-described communication system, which will be described in detail below.

[0170] Figure 8 is a flowchart illustrating a communication method provided in an embodiment of this application. This communication method is applicable to the aforementioned communication system and mainly involves the interaction between terminals and network devices.

[0171] As shown in Figure 8, the flow of this communication method is as follows:

[0172] S801, the terminal determines that the data arrives after the first time period.

[0173] The first time length can be the difference between the time the terminal predicts the data will arrive and the current time. For example, if the UE predicts the data will arrive in 10ms, the first time length can also be 20ms, 30ms, etc., without limitation. Predictive capability refers to the terminal's ability to predict the data arrival in advance within the first time length, such as the predictive capabilities of AI. Data arriving after the first time length can also be indicated by the network device; that is, the terminal determines the data will arrive after the first time length through the network device, such as the UE receiving information from the base station indicating that the data will arrive in 10ms. For ease of explanation, the following description uses the terminal predicting the data as an example.

[0174] The arrival of data can be from an application (APP), a third-party application, a server, etc., without limitation.

[0175] S802, the terminal sends the first SR to the network device, and the network device receives the first SR accordingly.

[0176] Wherein, the first time length is greater than or equal to the second time length, and the second time length is the time interval between when the terminal determines that the data arrives after the first time length and when the terminal sends the first SR.

[0177] The first SR is used to request authorized resources for transmitting the BSR. The first SR can use existing SR signaling or new signaling, such as SR-AI, which indicates that the terminal uses the AI ​​to predict the data. It is usually 1 bit.

[0178] Optionally, the terminal determines that the data arrives after a first time period and confirms that the terminal's cached data is empty, and then obtains the resources for sending the first SR, thereby sending the first SR to the network device.

[0179] It is understandable that the time when the terminal sends the first SR to the network device can be the same as or different from the time when the terminal determines that the data will arrive after the first time length. The time when the terminal determines that the data will arrive after the first time length can be understood as the time when the terminal "determines" the data. For example, if the UE predicts that the data will arrive 10ms (i.e., the first time length) after time #1, and there are available resources for sending the first SR at this time, then the terminal sends the SR at time #1. Alternatively, if the UE predicts that the data will arrive 10ms after time #1, and after acquiring the resources for sending the SR, it sends the SR 2ms after time #1.

[0180] It should be understood that in the embodiments of this application, the moment when the terminal sends the first SR and the moment when the network device receives the first SR can be regarded as the same moment. Therefore, the second time length can be the time interval between the terminal determining that the data arrives after the first time length and the network device receiving the first SR.

[0181] In summary, the first time length is greater than or equal to the second time length, and the terminal determines that the data will arrive after the first time length. This means the terminal sends the first SR (Signal Transfer) before the data arrives, thereby reducing the latency generated by the SR process during uplink authorization acquisition and improving the efficiency of uplink authorization acquisition. The terminal only needs to predict the data arrival time; compared to schemes that require the terminal to predict both the arrival time and the data volume, the computational requirements of the terminal in this embodiment are relatively low.

[0182] S803: The network device sends the first information to the terminal, and the terminal receives the first information accordingly.

[0183] S803 is an optional step. The first information instructs the network device to authorize the terminal to transmit the resources of the BSR. The network device sends the first information to the terminal based on the first SR; the first information is used in response to the first SR. The first information can be DCI information or any other signaling that can indicate authorized resources, without limitation.

[0184] Optionally, the first time length is greater than or equal to the total time length of the second time length and the third time length, where the third time length is the time interval between the terminal sending the first SR and the terminal receiving the first information.

[0185] In other words, the terminal receives the first information in response to the first SR before the data arrives, which reduces the latency generated by the SR process during the acquisition of uplink authorization and improves the efficiency of the terminal in acquiring uplink authorization.

[0186] It should be understood that in the embodiments of this application, the moment when the network device sends the first information and the moment when the terminal receives the first information can be regarded as the same moment. Therefore, the third time length can be the time interval between the network device receiving the first SR and the network device sending the first information.

[0187] For example, the network device controls the timing of sending the first information by receiving the first SR at the first time, the first time length, and the second time length. If the network device knows that the terminal predicts the data will arrive in 10ms (i.e., the first time length), and 2ms (i.e., the second time length) has elapsed from the time the terminal determines the data arrival time until sending the first SR, the network device receives the first SR at time 1 and controls the transmission of the DCI within (10-2) = 8ms after time 1, ensuring the terminal receives the DCI before the data arrives.

[0188] For example, the network device considers the moment when the terminal determines the arrival time of the data to be the same moment as the moment it sends the first SR (Schedule Request). In other words, the network device considers the second time length to be 0. In an ideal state, the network device believes that when the terminal determines the data will arrive after the first time length, it can directly send the first scheduling request (SR) to the network device without waiting for resources to send the first SR. The network device controls the timing of sending the first information by receiving the first SR at the same time and the first time length. For instance, if the network device knows that the terminal predicts the data will arrive in 10ms (the first time length), the network device receives the first SR at time 1 and controls the sending of the DCI (Distributed Information Request) within 10ms after time 1, ensuring that the terminal receives the DCI before the data arrives.

[0189] S804: After the terminal confirms that the data has arrived, the terminal sends a BSR to the network device based on the first information, and the network device receives the BSR accordingly.

[0190] S804 is an optional step. The BSR is used to request authorized resources for data transmission. The terminal sends the BSR later than the data arrival time. Therefore, the data volume in the BSR is the actual amount of data to be transmitted, not the data volume predicted in the PCR (which may be inaccurate). This avoids situations where authorized resources are insufficient or wasted.

[0191] Optionally, the first time length is less than or equal to the total time length of the second time length, the third time length, and K2.

[0192] K2 can be understood as the time elapsed between the terminal receiving the first information and the terminal sending the BSR, such as the slot offset between receiving the DCI and sending the uplink information (BSR). K2 can also be referenced in the description of K2 in the DG process described above, and will not be repeated here.

[0193] If the first time length is less than the total time length of the second time length, the third time length, and K2, the terminal receives the first information before the data actually arrives, that is, it receives the authorized resources for transmitting the BSR, and sends the BSR according to the actual amount of data after the data arrives.

[0194] For example, the network device knows that the terminal predicts data will arrive in 10ms (the first time length), and that 2ms (the second time length) has elapsed from the time the terminal determines the data arrival time until it sends the first SR. Both the terminal and the network device know that after receiving the DCI instruction, the terminal needs 2ms (K2) to decode the DCI instruction and prepare for sending the BSR. Therefore, the network device receives the first SR at time 1 and controls the transmission of the DCI instruction to occur 6ms after time 1 (10-2-2) = 6ms. For example, if the SR is sent 7ms after time 1, the data arrives after the terminal receives the DCI instruction but before it is ready to send the BSR, thus enabling the BSR to be sent based on the amount of data received.

[0195] If the first time length equals the total time length of the second time length, the third time length, and K2, then when the data actually arrives, the terminal has already prepared to send the BSR based on the received first information and the K2 time, such as decoding the DCI instruction and preparing to send the BSR.

[0196] For example, continuing the above example, the network device controls the DCI to be sent at (10-2-2) = 6ms after time 1, thereby ensuring that after the terminal receives the DCI instruction, it has 2ms time to prepare to send the BSR, so that the BSR can be sent just when the data arrives. At this time, the BSR can include the amount of data.

[0197] Optionally, the first time length is equal to the total time length of the third time length and K2.

[0198] The network device considers the moment when the terminal determines the arrival time of the data to be the same moment as the moment the first SR is sent, meaning the second time length is considered to be 0. For example, the network device knows that the terminal predicts the data will arrive in 10ms (the first time length). Both the terminal and the network device know that after receiving the DCI instruction, the terminal needs 2ms (K2) to decode the DCI instruction and prepare to send the BSR. Therefore, the network device receives the first SR at time 1 and controls the DCI to be sent at (10-2) = 8s after time 1. This ensures that the terminal receives the DCI instruction 8s after sending the first SR and has 2ms to prepare to send the BSR, thus ensuring that the BSR is sent just as the data arrives.

[0199] S805: The network device sends the second information to the terminal, and the terminal receives the second information accordingly.

[0200] S805 is an optional step. The second information indicates the resources authorized by the network device for the terminal to transmit data. The network device sends the second information to the terminal according to the BSR; the second information is used in response to the BSR. The second information can be DCI information, or any other signaling that can indicate authorized resources, without limitation.

[0201] The S802 will be described in detail below.

[0202] Optionally, the terminal may repetition the first SR, meaning it may send the same first SR multiple times consecutively, ensuring that at least one first SR is successfully sent, thus improving the success rate of the first SR transmission. Alternatively, after sending the first SR, the terminal may receive feedback information from the network device. This feedback information indicates that the network device has received the terminal's first SR, and may further indicate whether the network device accepts or rejects the first SR. The feedback information may be messages from the physical layer DCI / media access control (MAC) layer, such as MAC-control element (MAC-CE) / radio resource control (RRC) messages, etc., which are not limited here.

[0203] Optionally, if no feedback information is received after a preset time period following the terminal sending the first SR, the first SR is resent until the number of times the first SR is sent reaches a preset number; or, the first SR is resent until the terminal cancels the data transmission; or, the first SR is resent until the terminal's data has actually arrived and there is available resource configuration information for the second SR, wherein the resource configuration information for the second SR can be referred to the description below.

[0204] The following describes two methods for aligning the first time length between the terminal and the network device.

[0205] Method 1:

[0206] In one possible implementation, before the terminal sends the first SR to the network device, the communication method may further include: the terminal sending capability information to the network device, the capability information indicating that the terminal has the capability to predict that the data will arrive after a first time length.

[0207] The capability information indicates the terminal's predictive capability. This can be achieved by the terminal sending capability information to the network device through a terminal capability reporting process or other procedures, without limitation. Upon receiving the capability information, the network device can determine that the terminal's predictive capability is a first time length, or in other words, that the terminal's predictive capability is the ability to predict data arriving after the first time length. Therefore, when the network device receives the first SR (Signal Report), it can determine that the terminal predicts that data is about to arrive, and that the data's arrival time is after the first time length.

[0208] In this way, the terminal and network device share the ability to predict the data timing in advance, meaning that the terminal and network device are aligned on the first time length. The network device can control the timing of sending the first information. For example, on the network device side, it can control the timing of receiving the first SR, sending the first information, and the first time length to ensure that the first time length is greater than or equal to the total time length of the second and third time lengths, thereby reducing the latency of the SR process.

[0209] Optionally, the communication method may further include: the terminal receiving resource configuration information from the network device for transmitting the first SR, and sending the first SR to the network device according to the resource configuration information of the first SR.

[0210] Among them, the resource configuration information of the first SR can be periodically allocated to the terminal by the network device, and can be the resources used by the terminal after determining the arrival time of the data.

[0211] For example, the network configures one SR resource for each logical channel (LCH) of the UE. One SR resource can be associated with multiple LCHs. The SR resource is the resource used by the UE after predicting the arrival time of the data. If the UE predicts that the data will arrive in 100ms, it requests the scheduling resource from the network through the SR resource (i.e., sends the first SR). At this time, the UE's buffer can be empty, that is, there is no data to be transmitted.

[0212] Optionally, the communication method may further include: the terminal receiving resource configuration information from the network device for transmitting the second SR, and sending the second SR to the network device according to the resource configuration information of the second SR. The second SR is used to request authorized resources for transmitting the BSR after data arrives; the resource configuration information of the first SR differs from the resource configuration information of the second SR.

[0213] It is understandable that the second SR is used after the data actually arrives, and the resource configuration information of the second SR can be periodically allocated to the terminal by the network device. The period during which the network device allocates the resource configuration information of the first SR can be the same as or different from the period during which it allocates the resource configuration information of the second SR, and there is no limitation.

[0214] In this configuration, at least one parameter differs between the resource configuration information of the first SR and the resource configuration information of the second SR, such as the time-domain resource location and / or the frequency-domain resource location. By distinguishing between the resource configuration information of the first SR and the second SR, the network device differentiates whether the received data represents the first SR used when the terminal predicts data or the second SR used when the data actually arrives, thereby ensuring the accuracy of the use of the first and second SRs.

[0215] For example, the network configures two sets of SR resources for each LCH: one is the SR resource used after data is predicted, such as SR-AI; the other is the SR resource used after the data actually arrives, such as SR-legacy, or other different labeling methods, such as SR1, SR2, etc., without limitation. At least one parameter in the configuration information of these two sets of SR resources must be different, such as the time-domain resource location and / or frequency-domain resource location. If the UE predicts that data will arrive after time T through AI, it uses the SR-AI resource to request network scheduling. At this time, the UE's buffer can be empty, i.e., there is no data to be transmitted.

[0216] The following describes the mechanism by which a terminal cancels sending the first SR to a network device after triggering the sending of the first SR.

[0217] Optionally, if the terminal determines that the data will arrive after the first time length, and if the terminal triggers the sending of the first SR to the network device, but the terminal has not actually sent the first SR to the network device, and the terminal determines that the prediction result is incorrect, such as no data arriving after the first time length, or the data arrival time prediction is incorrect, then the sending of the first SR to the network device is cancelled.

[0218] The first SR and the second SR can be used together. For example, the cancellation mechanism of the first SR mentioned above can also be used when the data arrives before the terminal sends the first SR to the network device. In this case, the terminal has not yet sent the first SR, so the terminal cancels sending the first SR and sends the second SR to indicate that the data has actually arrived.

[0219] Since the resource configuration information of the second SR is configured periodically, the terminal needs a certain amount of time to obtain it. Therefore, in the case where the data arrives before the terminal sends the first SR to the network device, the cancellation mechanism of the first SR can also include: the terminal determines that the data arrives after the first time length and triggers the terminal to send the first SR to the network device. However, if the data arrives before the terminal sends the first SR to the network device, it is determined whether the time domain position of the resource used to send the second SR is earlier than the time domain position of the resource used to send the first SR. If so, the second SR is sent; otherwise, the first SR is still sent.

[0220] For example, after a UE triggers SR-AI, it can obtain the SR-AI resource configuration after time T1. However, the resource configuration of traditional SR is very sparse, and it takes another time T2 to obtain the traditional SR resource configuration. If T2 is greater than T1, the UE continues to send SR-AI. Conversely, if T2 is less than T1, that is, the UE can obtain the traditional SR resource configuration faster than the SR-AI resource configuration, the UE will then send traditional SR.

[0221] Optionally, if the terminal determines that the data will arrive after the first time length, and if the terminal has not yet actually sent the first SR to the network device, or the terminal has failed to successfully send the first SR, and the terminal receives scheduling resources from the network device, the terminal sends a message through the scheduling resources. The message includes information indicating the first time length. This message is only used to transmit the first time length, i.e., the predicted data arrival time. Compared to the PCR indicating the predicted data arrival time and data volume, this message has lower computational requirements on the terminal. When the terminal's computational power is low, it can quickly obtain uplink authorization for sudden real-time services.

[0222] Method 2:

[0223] Considering that the amount of lead time that a terminal can predict the arrival time of data may vary, such as the different prediction capabilities of terminals under different services and / or different computing power, the following introduces another way for the terminal and network device to align the first time length for this situation.

[0224] In another possible implementation, before the terminal sends the first SR to the network device, the communication method may further include: the terminal receiving resource configuration information from multiple SRs from the network device, and sending the first SR to the network device according to the resource configuration information of the first SR associated with a first time length. Each of the multiple SRs is associated with a different time length, the multiple SRs include the first SR, and the time length associated with the first SR matches the first time length.

[0225] Resource configuration information for multiple SRs can be periodically allocated to terminals by network devices. The different time lengths associated with each SR are used to represent different lead times for the arrival of the terminal's predicted data.

[0226] Optionally, different time lengths are related to predictive capability, which refers to the ability to predict the arrival of data after different time lengths. Network devices can send multiple predictive signals (SRs) to the terminal based on its predictive capability. For example, the amount of time a terminal can predict in advance varies depending on the service; for games, it can predict data arrival 50ms in advance, while for SMS messages, it can predict data arrival 1ms in advance. For the same service, the terminal's predictive capability may differ at different times. For instance, for games, with sufficient computing power, it can predict data arrival 100ms in advance, while with insufficient computing power, it can only predict data arrival 50ms in advance. Therefore, network devices can send SR#1 associated with 1ms, SR#2 associated with 50ms, and SR#3 associated with 100ms, etc.

[0227] Each SR's resource configuration information is associated with a time length, or each SR's resource configuration information contains the associated time length. For example, terminals and network devices align different time lengths associated with each SR through the association between each SR and the time length, or align different time lengths associated with each SR through the resource configuration information of each SR.

[0228] For example, the network issues multiple sets of SR resource configurations for each LCH of the UE. Each set of SR resource configurations is associated with a timing advance, or each set of SR resource configurations contains a timing advance to indicate how long after the data will arrive. The same SR can be associated with multiple LCHs. The SRs are denoted as SR1, SR2, ..., SRn, and the timing advances associated with the SRs are denoted as T1, T2, ..., Tn.

[0229] The terminal determines the first SR associated with the data based on the determined arrival time of the data, i.e., the first time length. For example, if the UE predicts that data will arrive after time T1, it selects the SR1 resource associated with T1 to initiate a resource request network scheduling to the network. If T1 is not equal to 0, it means that the SR is sent when the terminal's buffer data is empty.

[0230] Optionally, the time length associated with any of the multiple SRs can be 0. If the time length associated with an SR is 0, it means that the SR is used when the data has arrived, and the second SR mentioned above can be referred to.

[0231] Optionally, the time length associated with the first SR is greater than or equal to the first time length, and among the differences between the fourth time length and the first time length, the difference between the time length associated with the first SR and the first time length is the smallest, and the fourth time length is the time length associated with multiple SRs that is greater than or equal to the first time length.

[0232] It's understandable that after the terminal determines that data will arrive after the first time length, the first time length associated with the selected SR (Signal Sending Request) is greater than or equal to the first time length, and is closest to it. For example, if the UE predicts that data will arrive in 10ms, and the UE has four time lengths associated with SRs: 8ms, 9ms, 11ms, and 12ms, then if the UE chooses to send an SR associated with 8ms or 9ms, it's equivalent to instructing the network that the data will arrive in 8ms / 9ms. The network might allocate authorized resources for sending a BSR after 9.5ms or even 10ms, causing the BSR's authorized resources to expire before the data arrives. Therefore, the UE chooses an SR associated with a time length greater than the predicted 10ms, which is the closest to 10ms, i.e., 11ms.

[0233] Optionally, the resource configuration information parameters for every two SRs in the plurality of SRs include at least one different parameter. This at least one different parameter includes time-domain resource location and / or frequency-domain resource location.

[0234] In other words, the resource configuration information of each pair of SRs is different. That is, SRs can be distinguished by their resource configuration information, and the terminal can then send an SR to the network device based on the resource configuration information of any SR. Since the terminal and the network device share the resource configuration information and associated time length of multiple SRs, meaning that the terminal and the network device are aligned for the resource configuration information and associated time length of each SR, the network device can determine a unique SR based on the resource configuration information. For example, when the network device receives an SR, it determines that the received SR is the first SR based on the time domain resource location and / or frequency domain resource location of the received SR, and the network device controls the timing of sending the first information through the first time length associated with the first SR.

[0235] For example, the UE predicts that data will arrive after time Tj and selects the associated SRj resource to send SRj to the network. The network receives SRj and, based on the time Tj associated with SRj and the time K2 required for the UE to receive the DCI and send the BSR, sends the DCI to the UE at Ti-K2 after receiving SRj. Subsequently, the UE receives the DCI, and the data arrives after K2. At this point, the UE can parse the DCI to obtain authorized resources and send the BSR to the network. The BSR indicates the amount of data. In this way, the network ensures through scheduling that the UE has available authorized resources for transmitting the BSR after time Tj.

[0236] Methods 1 and 2 can be used in combination. In addition to the resource configuration information of multiple SRs, the terminal also receives resource configuration information from a second SR from the network device. Of course, a scheduling request with an associated time length of 0 among the multiple SRs can be equivalent to the second SR, achieving a similar effect, that is, indicating that the data has actually arrived at the terminal.

[0237] Thus, Method 2 can increase the flexibility of SR usage by taking into account different amounts of lead time that the terminal can predict when the data will arrive.

[0238] The overall flow of the communication method provided in the embodiments of this application has been illustrated above with reference to Figure 8. The specific flows of the communication method provided in the embodiments of this application under two specific scenarios are described below with reference to Figures 9 and 10.

[0239] Scene 1:

[0240] Figure 9 is a schematic flowchart of the communication method provided in this embodiment. This communication method is applicable to the above-mentioned communication system and specifically involves the interaction between the UE (i.e., the terminal) and the NW (i.e., the network device). During the process of the UE obtaining uplink authorization, the UE indicates capability information to the NW in advance, that is, the UE can predict the data in advance at time T. Thus, the NW can control the time of sending DCI#1 according to time T, so that when the data actually arrives, the UE already has authorized resources to prepare for sending BSR, such as decoding the DCI command and preparing for sending BSR, thereby reducing the latency generated in the SR process and improving the efficiency of the UE obtaining uplink authorization.

[0241] Specifically, as shown in Figure 9, the flow of this communication method is as follows:

[0242] S900, the UE sends its capability information to the NW.

[0243] The UE's capability information includes the UE's AI's ability to predict the lead time T for data arrival. This capability information can be found in the description in S801 and will not be repeated here.

[0244] S901, NW sends two SR resource configuration messages to UE.

[0245] The two SR resource configuration information include the resource configuration information of SR-AI and the resource configuration information of traditional SR. NW periodically sends the two SR resource configuration information to UE. SR-AI is used by UE after predicting data through AI, while traditional SR is used after the data actually arrives at UE. The resource configuration information of SR-AI and traditional SR can be referred to the description in S801, and will not be repeated here.

[0246] S902, the UE predicts that data will arrive after time T.

[0247] S903, the UE determines that the cache is empty.

[0248] S904, the UE sends SR-AI to the NW, and the NW receives SR-AI accordingly.

[0249] The NW determines that the received data is SR-AI based on the time-domain and / or frequency-domain resource location information when receiving SR-AI, which means that the UE can determine that the data will arrive after time T.

[0250] S905, NW sends DCI#1 to UE, and UE receives DCI#1 accordingly.

[0251] If the NW receives the SR-AI at time A, then the NW sends DCI#1 to the UE at time T-K2 after time A. DCI#1 includes authorized resource #1 for the UE to send the BSR.

[0252] S906, when data arrives, the UE sends a BSR to the NW.

[0253] If the UE receives DCI#1 at time B, and the data arrives after time K2, the UE will parse DCI#1 and obtain the authorized resource #1 for the UE to send BSR. The UE will then send BSR to NW through authorized resource #1. BSR includes the amount of data.

[0254] S907, NW sends DCI#2 to UE, and UE receives DCI#2 accordingly.

[0255] DCI#2 includes authorized resource #2 for UE to transmit data. The length of the time interval between the NW receiving the BSR and the NW sending DCI#2 to the UE typically depends on the network scheduling time.

[0256] S908, the UE sends data to the NW.

[0257] The interval K2 is from the moment the UE receives DCI#2 until the moment the UE sends data to the NW.

[0258] Thus, during the process of the UE obtaining uplink authorization, by having the UE indicate capability information to the NW in advance, that is, the UE can predict the data in advance at time T, the NW can control the time of sending DCI#1 according to time T. This ensures that when the data actually arrives, the UE already has authorized resources to prepare for sending BSR, such as decoding the DCI command and preparing for sending BSR, thereby reducing the latency generated in the SR process and improving the efficiency of the UE obtaining uplink authorization.

[0259] Scene 2:

[0260] Figure 10 is a flowchart illustrating the communication method provided in this embodiment. This communication method is applicable to the aforementioned communication system and specifically involves the interaction between the UE (i.e., the aforementioned terminal) and the NW (i.e., the aforementioned network device). Thus, during the UE's acquisition of uplink authorization, by receiving multiple SR resource configuration information and associated time advances from the NW, when the UE predicts data at time advance T2, it can send SR2 to the NW based on the resource configuration information of SR2 associated with T2. Upon receiving SR2, the NW can control the timing of sending DCI#1 based on time T2, ensuring that the UE has authorized resources to prepare for sending BSR when the data actually arrives. This reduces the latency generated in the SR process and improves the efficiency of the UE acquiring uplink authorization.

[0261] Specifically, as shown in Figure 10, the communication method flow is as follows:

[0262] S1001, NW sends resource configuration information for multiple SRs to UE.

[0263] Resource configuration information for multiple Service Controllers (SRs) can be periodically sent to the UE by the Network Controller (NW). Each SR in the resource configuration information is associated with a timing advance, indicating how long after data arrival it will be. The SRs are denoted as SR1, SR2, ..., SRn, and the associated timing advances are denoted as T1, T2, ..., Tn. The resource configuration information for any two SRs is different; that is, SRs can be distinguished by their resource configuration information, such as differences in time-domain and / or frequency-domain resource locations.

[0264] The resource configuration information for multiple SRs can also be found in the resource configuration information for multiple SRs described in S801, which will not be repeated here.

[0265] S1002, the UE predicts that data will arrive after time T2.

[0266] S1003, UE determines that the cache is empty.

[0267] S1004, the UE sends SR2 to the NW, and the NW receives SR2 accordingly.

[0268] The UE obtains SR2 associated with T2 based on the predicted time advance T2, and sends SR2 to the NW according to the time domain and / or frequency domain resource location of SR2. The NW determines that what it has received is SR2 based on the time domain and / or frequency domain resource location when it receives SR2, which means it can determine that the UE predicted that the data would arrive after time T2.

[0269] S1005, NW sends DCI#1 to UE, and UE receives DCI#1 accordingly.

[0270] If the time when the NW receives the SR-AI is time #A, then the NW sends DCI#1 to the UE according to time T2-K2 after time A. DCI#1 includes authorized resource #1 for the UE to send the BSR.

[0271] S1006, if data arrives, the UE sends a BSR to the NW.

[0272] If the UE receives DCI#1 at time B, and the data arrives after time K2, the UE will parse DCI#1 and obtain the authorized resource #1 for the UE to send BSR. The UE will then send BSR to NW through authorized resource #1. BSR includes the amount of data.

[0273] S1007, NW sends DCI#2 to UE, and UE receives DCI#2 accordingly.

[0274] DCI#2 includes authorized resource #2 for UE to transmit data. The length of the time interval between the NW receiving the BSR and the NW sending DCI#2 to the UE typically depends on the network scheduling time.

[0275] S1008, the UE sends data to the NW.

[0276] The interval K2 is from the moment the UE receives DCI#2 until the moment the UE sends data to the NW.

[0277] Thus, during the UE's acquisition of uplink authorization, by receiving multiple SR resource configuration information and associated time advances from the NW, when the UE predicts the data in advance time T2, it can send SR2 to the NW according to the resource configuration information of SR2 associated with T2. After receiving SR2, the NW can control the time of sending DCI#1 according to time T2, so that when the data actually arrives, the UE already has authorized resources to prepare for sending BSR, thereby reducing the latency generated in the SR process and improving the efficiency of the UE in acquiring uplink authorization.

[0278] As can be seen in the above embodiments, the terminal determines that the data will arrive after a first time length. The network device controls the time of sending the first information according to the first time length. That is, the network device needs to cooperate to control the first time length to be greater than or equal to the second time length, so that the terminal can receive the resources of the authorized terminal to transmit BSR before the data arrives.

[0279] The following describes a solution that reduces latency in the SR process without requiring network equipment cooperation, where the network equipment is unaware of the first time length and does not need to control the timing of sending the first information. It should be understood that the terms "first," "second," etc., are expressions at the implementation level; that is, the information indicated by "first," "second," etc., in this implementation differs from the information indicated by "first," "second," etc., in the above-described implementation. The expressions "first," "second," etc., described below apply only to Figures 11-12.

[0280] Figure 11 is a schematic flowchart of the communication method provided in an embodiment of this application. This communication method is applicable to the above-mentioned communication system and mainly involves the interaction between terminals and network devices.

[0281] As shown in Figure 11, the flow of this communication method is as follows:

[0282] S1101: When the terminal determines that the data will arrive after a first time period, it sends an SR to the network device at the second time period.

[0283] The SR is used to request authorized resources for the transmission of the BSR. The description of the first SR in S802 can be referred to, and will not be repeated here.

[0284] The first moment is the moment when the terminal determines the data arrival time, or it could be the moment when the network device instructs the terminal on the data arrival time. The second moment is the moment when the terminal sends the SR (Signal Request) to the network device; the first moment is earlier than or equal to the second moment. For example, if the terminal predicts that the data will arrive in 10ms, it needs to acquire the resources for sending the SR, which are periodically distributed by the network device. Therefore, the terminal acquires the SR resources 2ms later and sends the SR to the network device. Of course, it is possible that when the terminal predicts that the data will arrive in 10ms, it will receive the SR resources distributed by the network device and can immediately send the SR to the network device.

[0285] The second time point is earlier than the time when the data arrives, that is, the terminal sends the SR before the data arrives.

[0286] The first time length is greater than or equal to the total time length of the second and third time lengths. The second time length is the time difference between the first and second moments, and the third time length is the predicted time interval from sending the SR to receiving the first information.

[0287] It is understandable that the terminal predicts the time required from sending the SR to receiving the first information. For example, it can predict how many SRs are usually needed to obtain the DCI under a certain base station and current channel conditions through machine learning, deep learning, etc. In other words, the terminal predicts the time required for the SR.

[0288] After predicting the third time length, the terminal determines the second time to send the SR to the network device using the difference between the first and third time lengths and the first time. For example, if the UE predicts that the data will arrive 10ms (the first time length) after time #1, and the UE determines through machine learning that it will take 3ms (the third time length) from sending the SR to receiving the DCI, then the UE will send the SR within (10-3) = 7ms after time #1. If the SR is sent 6ms after time #1, the UE will receive the DCI before the data actually arrives, thus reducing the latency in the SR process.

[0289] The following describes two scenarios in which a terminal sends an SR to a network device.

[0290] Scenario 1:

[0291] Optionally, the terminal sending an SR to the network device at the second time may include: the terminal triggering a second BSR before the second time, and triggering the sending of an SR to the network device at the second time according to the second BSR, wherein the amount of data in the second BSR is 0.

[0292] It is understandable that when the terminal determines that the data has arrived after the first time period, it triggers an "empty" second BSR, that is, the amount of data in the second BSR is 0, and then sends an SR to the network device at the second time. In other words, the time when the second BSR is triggered is between the first time and the second time.

[0293] Scenario 2:

[0294] The terminal directly triggers the sending of the SR to the network device, skipping the process of triggering the second BSR. When the terminal determines that the data will arrive after the first time length in the first moment, it directly sends the SR to the network device in the second moment. If the UE predicts that data is about to arrive and the buffer is empty, it skips the BSR and directly triggers the SR process in the second moment. When the data actually arrives, the UE regenerates a BSR based on the actual amount of data that arrives and transmits it.

[0295] S1102, the network device sends the first information to the terminal, and the terminal receives the first information accordingly.

[0296] The first piece of information instructs the network device to authorize the terminal to transmit the BSR resources. S1102 can be referred to in the description of S802, and will not be repeated here.

[0297] S1103, after the data arrives, the terminal sends the first BSR to the network device based on the first information.

[0298] The first BSR is used to request authorized resources for transmitting data.

[0299] Optionally, the first time length is less than or equal to the total time length of the second, third and fourth time lengths. The fourth time length is the time interval between the terminal receiving the first information and the terminal sending the first BSR. The fourth time length can be referred to the above description of K2, and will not be repeated here.

[0300] After predicting the third time length, the terminal determines the second time to send the SR to the network device using the difference between the first time length and the third and fourth time lengths, as well as the first time. For example, the UE predicts that data will arrive 10ms (the first time length) after time #1, and the UE determines through machine learning that it will take 3ms (the third time length) from sending the SR to receiving the DCI, and knows that it will take 2ms (the fourth time length) to decode the DCI command and prepare for sending the first BSR. Therefore, the UE sends the SR 5ms after time #1 (10-3-2). For example, sending the SR 6ms after time #1 ensures that the data arrives after the UE receives the DCI and before it is ready to send the BSR, thus enabling the UE to send the BSR based on the amount of data after the data arrives. Alternatively, the UE sends the SR 5ms after time #1 (10-3-2), giving the UE 2ms time to prepare for sending the BSR after receiving the DCI, ensuring that the BSR is sent just as the data arrives.

[0301] The following describes two methods for generating the first BSR.

[0302] Optionally, S1103 may include: after the data arrives, the terminal generates a first BSR based on the amount of data, the first BSR and the second BSR are different MAC CEs, and sends the first BSR to the network device based on the first information.

[0303] The first BSR and the second BSR are different MAC CEs. For example, when the data actually arrives at the UE, the UE regenerates a BSR based on the amount of data that actually arrives and transmits the regenerated BSR.

[0304] Optionally, S1103 may further include: after the data arrives, the terminal updates the data quantity 0 in the second BSR to the data quantity of the data, and obtains the first BSR. The second BSR and the first BSR have the same MAC CE. The terminal sends the first BSR to the network device according to the first information.

[0305] The second BSR has the same MAC CE as the first BSR, but the data volume-related values ​​in the second BSR are different from those in the first BSR. For example, when the data actually arrives at the UE, the UE rewrites the value in the "empty" BSR according to the actual data volume and transmits the rewritten BSR.

[0306] It should be understood that the embodiments corresponding to Figure 11 can be used in combination with the embodiments corresponding to Figures 8-10. For example, the use of the first BSR and the second BSR in the embodiment corresponding to Figure 11 can be applied to the embodiments corresponding to Figures 8-10.

[0307] Thus, by defining the relationship between the first, second, and third time lengths, the second moment when the terminal sends the SR to the network device can be determined. This allows the terminal to receive the first information before the data arrives, thereby authorizing the terminal to transmit the resources of the first BSR. In this way, without the cooperation of the network device, and without the network device being aware of the first time length or needing to control the timing of sending the first information, the latency generated in the SR process can be reduced.

[0308] The overall flow of the communication method provided in the embodiments of this application has been illustrated above with reference to Figure 11. The specific flow of the communication method provided in the embodiments of this application under two specific scenarios is described below with reference to Figure 12.

[0309] Figure 12 is a flowchart illustrating the communication method provided in this embodiment. This communication method is applicable to the aforementioned communication system and specifically involves the interaction between the UE (i.e., the aforementioned terminal) and the NW (i.e., the aforementioned network device). The UE determines the time required for the SR process and, based on the predicted data arrival time and K2, determines the time when the UE sends the SR to the NW. This allows the UE to receive the resources authorized for transmitting the BSR before the data arrives. Thus, without the NW being aware of the predicted data arrival time or needing to control the DCI transmission time, the latency generated in the SR process can be reduced.

[0310] Specifically, as shown in Figure 12, the communication method flow is as follows:

[0311] S1201, UE predicts that data will arrive after time T1.

[0312] The UE predicts at time A that data will arrive after time T1.

[0313] S1202, UE determines that the cache is empty.

[0314] Optionally, the UE triggers an "empty" BSR.

[0315] S1203, the UE sends an SR to the NW at time B, and the NW receives the SR accordingly.

[0316] The UE uses machine learning to determine the time T3 required for the SR process, which is the time T3 required from when the UE sends the SR until it receives the DCI. The time interval between time A and time B is (T1-T2-K2), and time B is determined by (T1-T2-K2) and time A. K2 can be referred to in the description of S801, and will not be elaborated further.

[0317] S1204, NW sends DCI#1 to UE, and UE receives DCI#1 accordingly.

[0318] S1205, if data arrives, the UE sends a BSR to the NW.

[0319] When the data actually arrives, the UE regenerates a BSR based on the actual amount of data received and transmits it, or the UE rewrites the value in the "empty" BSR in S1202 and transmits the rewritten BSR.

[0320] S1206, NW sends DCI#2 to UE, and UE receives DCI#2 accordingly.

[0321] S1207, the UE sends data to the NW.

[0322] S1204-S1207 can also refer to the content of S905-S908, which will not be elaborated upon here.

[0323] In this way, the UE determines the time required for the SR procedure and, based on the predicted data arrival time and K2, determines when the UE should send the SR to the NW. This allows the UE to receive the resources authorized for the transmission of the BSR before the data arrives. Thus, without the NW being aware of the predicted data arrival time or needing to control the DCI transmission time, the latency generated by the SR procedure can be reduced.

[0324] It should be understood that the various implementations of the embodiments of this application can be used in combination. For example, the two methods of aligning the terminal and the network device for the first time length in the embodiment corresponding to FIG8 can be applied to the embodiment corresponding to FIG11. As another example, the two cases of the terminal sending an SR to the network device in the embodiment corresponding to FIG11 can be applied to the embodiment corresponding to FIG8. The combination of the various implementations of the above embodiments is not limited.

[0325] The method provided by the embodiments of this application has been described in detail above with reference to Figures 8-12. The communication apparatus used to perform the communication method provided by the embodiments of this application is described in detail below with reference to Figures 13-14.

[0326] Figure 13 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Exemplarily, as shown in Figure 13, the communication device 1300 includes a transceiver module 1301 and a processing module 1302. For ease of explanation, Figure 13 only shows the main components of the communication device.

[0327] The transceiver module 1301 is used to perform the transceiver function of the method shown in Figure 8, and the processing module 1302 is used to perform other functions of the method shown in Figure 8 besides the transceiver function.

[0328] Optionally, the transceiver module 1301 may include a transmitting module (not shown in FIG. 13) and a receiving module (not shown in FIG. 13). The transmitting module is used to implement the transmitting function of the communication device 1300, and the receiving module is used to implement the receiving function of the communication device 1300.

[0329] Optionally, the communication device 1300 may further include a storage module (not shown in FIG13) that stores programs or instructions. When the processing module 1302 executes the program or instructions, the communication device 1300 can perform the functions of the terminal or network device in the method shown in FIG8 above.

[0330] It is understood that the communication device 1300 may be a terminal or network device, or a chip (system) or other component or assembly that can be set in the terminal or network device, or a device that includes the terminal or network device. This application does not limit it in this respect.

[0331] Furthermore, the technical effects of the communication device 1300 can be referred to the technical effects of the communication method shown in Figure 8, and will not be repeated here.

[0332] Figure 14 is a second schematic diagram of the structure of the communication device provided in an embodiment of this application. Exemplarily, the communication device can be a terminal, or a chip (system) or other component or assembly that can be disposed in the terminal. As shown in Figure 14, the communication device 1400 may include a processor 1401. Optionally, the communication device 1400 may also include a memory 1402 and / or a transceiver 1403. The processor 1401 is coupled to the memory 1402 and / or the transceiver 1403, for example, by means of a communication bus, an internal chip interface, or other communication lines. Optionally, the memory 1402 may be integrated with the processor 1401.

[0333] The following is a detailed description of each component of the communication device 1400 with reference to Figure 14:

[0334] The processor 1401 is the control center of the communication device 1400. It can be a single processor or a collective term for multiple processing elements. For example, the processor 1401 can be one or more central processing units (CPUs), application-specific integrated circuits (ASICs), or one or more integrated circuits configured to implement the embodiments of this application, such as one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs).

[0335] Optionally, the processor 1401 can perform various functions of the communication device 1400 by running or executing software programs stored in the memory 1402 and calling data stored in the memory 1402, such as performing the communication method shown in FIG8 above.

[0336] In a specific implementation, as one example, processor 1401 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG14.

[0337] In a specific implementation, as one embodiment, the communication device 1400 may also include multiple processors, such as processors 1401 and 1404 shown in FIG. 14. Each of these processors may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). Here, a processor may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0338] The memory 1402 is used to store the software program that executes the solution of this application, and is controlled by the processor 1401 to execute it. The specific implementation method can be referred to the above method embodiment, and will not be repeated here.

[0339] Optionally, the memory 1402 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory 1402 may be integrated with the processor 1401 or may exist independently and be coupled to the processor 1401 through the interface circuit of the communication device 1400 (not shown in FIG. 14). This application embodiment does not specifically limit this.

[0340] Transceiver 1403 is used for communication with other communication devices. For example, if communication device 1400 is a terminal, transceiver 1403 can be used to communicate with a network device or with another terminal device. As another example, if communication device 1400 is a network device, transceiver 1403 can be used to communicate with a terminal or with another network device.

[0341] Optionally, transceiver 1403 may include a receiver and a transmitter (not shown separately in Figure 14). The receiver is used to implement the receiving function, and the transmitter is used to implement the transmitting function.

[0342] Optionally, the transceiver 1403 can be integrated with the processor 1401 or exist independently and be coupled to the processor 1401 through the interface circuit of the communication device 1400 (not shown in FIG14). This application embodiment does not specifically limit this.

[0343] It is understood that the structure of the communication device 1400 shown in Figure 14 does not constitute a limitation on the communication device. Actual communication devices may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0344] Furthermore, the technical effects of the communication device 1400 can be referred to the technical effects of the method described in the above method embodiments, and will not be repeated here.

[0345] It should be understood that the processor in the embodiments of this application can be a central processing unit (CPU), or it can be other general-purpose processors, DSPs, ASICs, FPGAs, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor, etc.

[0346] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Non-volatile memory can be ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), EEPROM, or flash memory. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0347] The above embodiments can be implemented, in whole or in part, by software, hardware (such as circuits), firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0348] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. A and B can be singular or plural. Additionally, the character " / " in this article generally indicates an "or" relationship between the preceding and following related objects, but it can also represent an "and / or" relationship. Please refer to the context for a more accurate understanding.

[0349] In this application, "at least one" means one or more, and "more than one" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0350] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0351] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0352] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0353] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0354] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0355] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0356] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes all the various possible memories described above.

Claims

A communication method characterized by comprising: The method comprises: determining that data arrives after a first time length; sending a first scheduling request (SR) to a network device, the first SR being used to request a grant resource for transmitting a buffer status report (BSR), the BSR being used to request a grant resource for transmitting the data; wherein the first time length is greater than or equal to a second time length, the second time length being a time length between the determining that the data arrives after the first time length and the sending the first SR. The method of claim 1, wherein The method further comprises: receiving first information from the network device, the first information indicating that the network device grants a terminal a resource for transmitting the BSR; wherein the first time length is greater than or equal to a total time length of the second time length and a third time length, the third time length being a time length between the sending the first SR and the receiving the first information. The method according to claim 2, characterized in that The method further comprises: determining that the data arrives; sending the BSR to the network device according to the first information; wherein a time of sending the BSR is later than a time of the data arriving. The method according to any one of claims 1 to 3, characterized in that Before the sending the first SR to the network device, the method further comprises: sending capability information to the network device, the capability information indicating that the terminal has a capability of predicting that data arrives after the first time length. The method according to any one of claims 1 to 4, characterized in that Before the sending the first SR to the network device, the method further comprises: receiving resource configuration information for transmitting the first SR from the network device; The sending the first SR to the network device comprises: sending the first SR to the network device according to the resource configuration information of the first SR. The method according to claim 5, characterized in that The method further comprises: receiving resource configuration information for transmitting a second SR from the network device; wherein the second SR is used to request a grant resource for transmitting the BSR after the data arrives; the resource configuration information of the first SR is different from the resource configuration information of the second SR; sending the second SR to the network device according to the resource configuration information of the second SR. The method according to claim 6, characterized in that At least one parameter in the resource configuration information of the first SR and the resource configuration information of the second SR is different. The method of claim 7, wherein The at least one parameter comprises a time domain resource location and / or a frequency domain resource location. The method according to any one of claims 1 to 3, characterized in that Before the sending the first SR to the network device, the method further comprises: receiving resource configuration information of a plurality of SRs from the network device, each SR in the plurality of SRs being associated with a different time length, the plurality of SRs comprising the first SR, the first SR being associated with a time length matching the first time length; The sending the first SR to the network device comprises: sending the first SR to the network device according to the resource configuration information of the first SR associated with the first time length. The method of claim 9, wherein The different time lengths are related to a prediction capability, the prediction capability being a capability of predicting that data arrives after the different time lengths. The method according to claim 9 or 10, characterized in that The first SR associated time length is greater than or equal to the first time length, and the difference between the first SR associated time length and the first time length is the smallest in the difference between the fourth time length and the first time length, the fourth time length being the time length greater than or equal to the first time length in the plurality of SR associated time lengths. The method according to any one of claims 9 to 11, characterized in that The parameters of the resource configuration information of each two SRs in the plurality of SRs include at least one different parameter. The method of claim 12, wherein The at least one different parameter includes a time domain resource location and / or a frequency domain resource location. A communication method characterized by comprising: Comprise: After the terminal determines that data arrives after a first time length, the network device receives a first SR from the terminal, the first SR being used to request an authorized resource for transmitting a buffer status report (BSR); The network device sends first information to the terminal according to the first SR, the first information indicating that the network device authorizes the terminal to transmit the resource for transmitting the BSR; Wherein, the first time length is greater than or equal to a second time length, the second time length being a time length between the terminal determining that data arrives after a first time length and the network device receiving a first SR from the terminal. The method of claim 14, wherein The first time length is greater than or equal to a third time length, the third time length being a time length between the network device receiving the first SR and the network device sending the first information. The method according to claim 14 or 15, characterized in that The method further comprises: After the terminal determines that the data arrives, the network device receives the BSR sent by the terminal according to the first information, the BSR being used to request an authorized resource for transmitting the data; Wherein, the time of receiving the BSR is later than the time of the data arriving at the terminal. The method according to any one of claims 14 to 16, characterized in that Before the network device receives a first SR from the terminal, the method further comprises: The network device receives capability information from the terminal, the capability information indicating that the terminal has the capability of predicting that data will arrive after a first time length. The method according to any one of claims 14 to 17, characterized in that Before the network device receives a first SR from the terminal, the method further comprises: The network device sends resource configuration information for transmitting the first SR and resource configuration information for transmitting a second SR to the terminal, wherein the resource configuration information of the first SR is used when the terminal determines that data will arrive after a first time length, and the resource configuration information of the second SR is used when the data arrives at the terminal. The method of claim 18, wherein The parameters of the resource configuration information of the first SR and the resource configuration information of the second SR include at least one different parameter, the at least one parameter including a time domain resource location and / or a frequency domain resource location. The method of claim 19, wherein The network device receives a first SR from the terminal, comprising: The network device determines that the SR is the first SR according to the time domain resource location and / or the frequency domain resource location of the received SR. The method according to any one of claims 14 to 16, characterized in that Before the network device receives a first SR from the terminal, the method further comprises: The network device sends resource configuration information of multiple SRs to the terminal, each of the multiple SRs is associated with a different time length, the multiple SRs include the first SR, and the time length associated with the first SR matches the first time length. The method of claim 21, wherein The different time lengths are related to a prediction capability, and the prediction capability is a capability of predicting arrival of data after the different time lengths. The method according to claim 21 or 22, characterized in that The time length associated with the first SR is greater than or equal to the first time length, and among a difference between a fourth time length and the first time length, a difference between the time length associated with the first SR and the first time length is the smallest, the fourth time length is a time length greater than or equal to the first time length among the time lengths associated with the multiple SRs. The method according to any one of claims 21 to 23, characterized in that Parameters of the resource configuration information of each two SRs in the multiple SRs include at least one different parameter, and the at least one different parameter includes a time domain resource position and / or a frequency domain resource position. A communication method characterized by comprising: Comprise: When it is determined that data arrives after a first time length at a first time point, a scheduling request (SR) is sent to the network device at a second time point, the SR is used to request a grant resource for transmitting a buffer status report (BSR), and the first time point is earlier than or equal to the second time point; First information from the network device is received, the first information indicates that the network device authorizes a terminal to transmit a BSR; After the data arrives, a first BSR is sent to the network device according to the first information, the first BSR is used to request a grant resource for transmitting the data; Wherein, the second time point is earlier than the time point at which the data arrives; the first time length is greater than or equal to the total time length of a second time length and a third time length; the second time length is a time difference between the first time point and the second time point, and the third time length is a time length interval between sending the first SR and receiving the first information. The method of claim 25, wherein The first time length is less than or equal to the total time length of the second time length, the third time length and a fourth time length, and the fourth time length is a time length interval between receiving the first information and sending the first BSR. The method according to claim 25 or 26, characterized in that The terminal sends the first SR to the network device at the second time point, comprising: Trigger a second BSR before the second time point, and a data amount in the second BSR is 0; According to the second BSR, the first SR is triggered to be sent to the network device. The method of claim 27, wherein After the data arrives, the first BSR is sent to the network device according to the first information, comprising: After the data arrives, the first BSR is generated according to a data amount of the data, the first BSR and the second BSR are different medium access control elements (MAC CEs); The first BSR is sent to the network device according to the first information. The method of claim 27, wherein After the data arrives, the first BSR is sent to the network device according to the first information, comprising: After the data arrives, the data amount 0 in the second BSR is updated to the data amount of the data, obtaining a first BSR, the second BSR and the first BSR are same MAC CEs; According to the first information, the first BSR is sent to the network device. A communication device, characterized by The apparatus includes modules for performing the methods of any of claims 1-13, or modules for performing the methods of any of claims 14-24, or modules for performing the methods of any of claims 25-29. A communication device, characterized by The communication apparatus includes a processor and a memory, the memory is used to store computer instructions, when the processor executes the instructions, the methods of any of claims 1-13 are executed, or the methods of any of claims 14-24 are executed, or the methods of any of claims 25-29 are executed. A computer-readable storage medium, characterized by The computer readable storage medium includes computer programs or instructions, when the computer programs or instructions are run on a computer, the computer executes the methods of any of claims 1-13, or the computer executes the methods of any of claims 14-24, or the computer executes the methods of any of claims 25-29. A computer program product, characterized in that The computer program product includes computer programs or instructions, when the computer programs or instructions are run on a computer, the methods of any of claims 1-13 are executed, or the methods of any of claims 14-24 are executed, or the methods of any of claims 25-29 are executed. A chip characterized by The computer program product includes computer programs or instructions, when the computer programs or instructions are run on a computer, the methods of any of claims 1-13 are executed, or the methods of any of claims 14-24 are executed, or the methods of any of claims 25-29 are executed. The computer program product includes computer programs or instructions, when the computer programs or instructions are run on a computer, the methods of any of claims 1-13 are executed, or the methods of any of claims 14-24 are executed, or the methods of any of claims 25-29 are executed. The computer program product includes computer programs or instructions, when the computer programs or instructions are run on a computer, the methods of any of claims 1-13 are executed, or the methods of any of claims 14-24 are executed, or the methods of any of claims 25-29 are executed.

Images