Communication method, communication device, and communication system

Abstract

The application provides a communication method, a communication device and a communication system, and relates to the technical field of communication. In the method, when a terminal device has a data sending requirement, the terminal device simultaneously realizes uplink scheduling request and buffer data amount (or data amount range) reporting by reporting the data amount or data amount range of the data to be transmitted in the buffer to a base station. Thus, the base station can know the data amount (or data amount range) of the data to be transmitted while determining the uplink scheduling request of the terminal device, so that the base station can timely allocate uplink resources for the terminal device without obtaining the data amount of the data in the buffer of the terminal device through the next uplink transmission after one uplink scheduling, which helps to reduce the uplink scheduling transmission delay and improve the reliability of communication.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly to a communication method, communication device, and communication system. Background Technology

[0002] In a communication network, when a terminal device needs to transmit data, it can send a scheduling request (SR) to the network device on the Physical Uplink Control Channel (PUCCH) resource pre-configured for it. The SR consists of 1 bit. The network device can determine the terminal device's uplink scheduling request by performing energy detection on the PUCCH resource. Then, it allocates Physical Uplink Shared Channel (PUSCH) resources to the terminal device via Downlink Control Information (DCI). The terminal device can send a buffer status report (BSR) to the network device (e.g., a base station) on this PUSCH resource to inform the network device of its buffer status. After receiving the BSR from the terminal device, the network device can understand the terminal device's buffer status and, based on this status, decide when to schedule the terminal device for uplink data transmission and how much uplink resources to allocate.

[0003] As can be seen from the above introduction, the scheduling delay for uplink data is currently quite large. Summary of the Invention

[0004] This application provides a communication method, communication device, and communication system to reduce uplink scheduling transmission latency and improve communication reliability.

[0005] Firstly, a communication method is provided, which can be executed by a terminal device or by a unit / module / component (such as a chip, chip system, logic circuit, or software) configurable in (or usable in) a terminal device. The following explanation uses the execution of this method by a terminal device as an example.

[0006] The method includes: a terminal device sending first information requesting uplink authorization and indicating: a first data volume, the first data volume being greater than or equal to the data volume to be transmitted in the terminal device's buffer; or a first index indicating a range of the first data volume, the data volume to be transmitted in the terminal device's buffer belonging to the range of the first data volume. The terminal device receives second information indicating a first uplink resource. The terminal device transmits first data on the first uplink resource, the data to be transmitted including the first data.

[0007] According to the above scheme, the terminal device simultaneously requests uplink scheduling and reports the amount or range of data to be transmitted in its cache to the base station. This allows the base station to know the amount (or range) of data to be transmitted at the same time as determining the terminal device's request for uplink scheduling. The base station can then allocate uplink resources to the terminal device promptly, without needing to go through an uplink scheduling process and then wait for the next uplink transmission to obtain the amount of data in the terminal device's cache. This helps reduce uplink scheduling latency and improves communication reliability.

[0008] In conjunction with the first aspect, in some implementations of the first aspect, the first index is located in the first correspondence, which is a correspondence between multiple data ranges and multiple indexes, and the multiple data ranges include the first data range.

[0009] For example, the first correspondence can be represented in the form of a table (as shown in Table 2 below), but this application is not limited to this. The first correspondence can also be represented by other mapping methods (such as arrays, matrices, etc.).

[0010] According to the above scheme, the terminal device can determine a first index based on the amount of data to be transmitted in the cache and a first correspondence, and then indicate the first index to the base station. This allows the base station to determine a first data volume range based on the first index and allocate uplink resources to the terminal device based on that range. The terminal device's use of the first index to indicate the first data volume range also helps reduce the resource overhead of uplink grant requests.

[0011] In conjunction with the first aspect, in some implementations of the first aspect, the first information is carried on a first resource, which is a first physical uplink control channel (PUCCH) resource.

[0012] PUCCH resources can include various formats, such as short-format PUCCH resources (occupying 1 or 2 time-domain symbols) or long-format PUCCH resources (occupying 4 to 14 time-domain symbols). Whether the first information is carried in short-format or long-format PUCCH resources can be predefined by the protocol, defined, or pre-configured by the base station to the terminal equipment via signaling (such as radio resource control (RRC) signaling). This application does not impose any restrictions.

[0013] Optionally, the first information can be carried on multiple subcarriers on one or more time-domain symbols in the first PUCCH resource. Specifically, when the first PUCCH resource is in short format or long format, the implementation of how the first information is carried by the first PUCCH resource can be found in the relevant description below, which will not be elaborated here.

[0014] According to the above scheme, the terminal device can send the first information to the base station using either short-format or long-format PUCCH resources, while simultaneously requesting uplink authorization from the base station and reporting the amount of buffered data. This helps the base station obtain the amount of data to be transmitted in the terminal device's buffer earlier, thereby reducing uplink authorization latency and improving communication reliability.

[0015] In conjunction with the first aspect, in some implementations of the first aspect, the first information is carried in a first sequence on multiple subcarriers on one or more time-domain symbols in the first physical uplink control channel resource.

[0016] Optionally, the first sequence is obtained through encoding, which may include shift register-based encoding or channel coding-based encoding.

[0017] According to the above scheme, the terminal device can also improve the anti-interference capability of the first information and improve the reliability of communication by sending the first information in the form of a first sequence.

[0018] In conjunction with the first aspect, in some implementations of the first aspect, the coding process of the channel coding includes scrambling based on the wireless network temporary identifier of the terminal device.

[0019] In this implementation, the base station can determine which terminal device to allocate uplink resources to, which can improve the reliability of data transmission.

[0020] In conjunction with the first aspect, in some implementations of the first aspect, the first information further indicates the format of the first physical uplink control channel resource, the format of the first physical uplink control channel resource including a first format, which is a short format; or, the format of the first physical uplink control channel resource including a second format, which is a long format.

[0021] According to the above scheme, the base station can determine the number of symbols occupied in the time domain of the first PUCCH resource carrying the first information, and can parse the first information on the corresponding symbol based on the number of symbols. This helps to increase the probability that the base station will successfully receive the first information, enabling the base station to allocate uplink resources to the terminal device in a timely manner and improve the reliability of communication.

[0022] In conjunction with the first aspect, in some implementations of the first aspect, the first information is carried on a first resource, which is a resource pre-configured for sending the first information.

[0023] Optionally, the first resource may be a PUCCH resource pre-configured for the terminal device, or the first resource may be a PUSCH resource pre-configured for the terminal device, or part of the first resource may be a PUCCH resource and another part may be a PUCSH resource. This application does not impose any restrictions on this.

[0024] In this implementation, the base station can choose to configure PUCCH resources and / or PUSCH resources for the terminal device according to actual needs, which helps to improve the flexibility of configuring the primary resources.

[0025] In conjunction with the first aspect, in some implementations of the first aspect, before the terminal device sends the first information, the method further includes: the terminal device receiving third information, the third information being configured as one or more candidate resources for sending the first information, the one or more candidate resources including the first resource.

[0026] Optionally, the third information configuration includes one or more of the following for each candidate resource in one or more candidate resources: time-domain resource, frequency-domain resource, resource mapping style, or resource identifier.

[0027] Optionally, the third information is radio resource control configuration information or radio resource control reconfiguration information.

[0028] According to the above scheme, the base station can configure one or more candidate resources for the terminal device to carry the first information. The terminal device can send the first information to the base station on one of the one or more candidate resources to simultaneously request uplink scheduling and report the amount of buffered data (or the range of data), which helps to reduce the latency of uplink scheduling transmission and improve the reliability of communication.

[0029] In conjunction with the first aspect, in some implementations of the first aspect, the third information can configure a resource pool for candidate resources, which specifically includes one or more candidate resources.

[0030] In this implementation, a candidate resource in the resource pool can be a single time-frequency unit, or a candidate resource can include multiple time-frequency units scattered in the resource pool. When the terminal device has a data transmission requirement, the terminal device can select the next time-frequency unit of the first resource in the resource pool to send the first information to the base station.

[0031] The specific implementation method for determining which candidate resource to use to send the first information to the base station may include, but is not limited to, the following methods 1 and 2:

[0032] Method 1: The terminal device receives fourth information, which indicates a first resource among multiple candidate resources. The first resource is the resource to which the terminal device sent the first information.

[0033] Optionally, the fourth piece of information is downlink control information, radio resource control configuration information, or radio resource control reconfiguration information.

[0034] In this implementation, the base station can activate the first resource for carrying the first information for the terminal device through the fourth information. Alternatively, the base station can adjust the resources used by the terminal device to transmit the first information based on the utilization of radio resources, which helps to improve the flexibility of the terminal device in transmitting the first information.

[0035] Method 2: The terminal device selects the first resource from multiple candidate resources based on predefined rules and sends the first information to the base station. The specific predefined rules are described in detail below and will not be repeated here.

[0036] In this implementation, the terminal device can select the first resource to send the first information to the base station based on the actual situation, which helps to improve the flexibility of the terminal device in sending the first information.

[0037] In conjunction with the first aspect, in some implementations of the first aspect, the second information is downlink control information; and / or, the third information is radio resource control configuration information or radio resource control reconfiguration information; and / or, the fourth information is downlink control information, radio resource control configuration information, or radio resource control reconfiguration information; and / or, the uplink resource is physical uplink shared channel resource.

[0038] In conjunction with the first aspect, in certain implementations of the first aspect, the terminal device transmits first data on the first uplink resource, including: if the data to be transmitted in the terminal device's buffer is insufficient to be transmitted entirely on the first uplink resource, transmitting the first data and a second index on the first uplink resource, the second index indicating a second data volume range, the data volume of the remaining data to be transmitted in the terminal device's buffer belonging to the second data volume range; if the data to be transmitted in the terminal device's buffer is sufficient to be transmitted entirely on the first uplink resource, transmitting the first data on the first uplink resource, the data to be transmitted being the first data.

[0039] According to the above scheme, the terminal device can report the actual amount of data remaining to be transmitted in the cache, which helps the base station to understand the actual transmission needs of the terminal device more accurately, and can allocate uplink resources to the terminal device more accurately, thereby improving the allocation efficiency of uplink resources.

[0040] Secondly, a communication method is provided, which can be executed by a network device (such as a base station) or by a unit / module / component (such as a chip, chip system, logic circuit, or software) configurable in (or usable in) a network device. The following explanation uses a base station as an example of a network device.

[0041] The method includes: a base station receiving first information requesting uplink authorization and indicating: a first data amount, the first data amount being greater than or equal to the amount of data to be transmitted in the cache of a terminal device; or a first index indicating a range of the first data amount, the amount of data to be transmitted in the cache of the terminal device belonging to the range of the first data amount. In response to the uplink authorization, the base station determines a first uplink resource based on the first data amount. The base station sends second information indicating the first uplink resource. The base station receives first data on the first uplink resource, the data to be transmitted including the first data.

[0042] In conjunction with the second aspect, in some implementations of the second aspect, the first information is carried on a first resource, which is a resource pre-configured for sending the first information.

[0043] In conjunction with the second aspect, in some implementations of the second aspect, the first information is carried on a first resource, which is a first physical uplink control channel resource.

[0044] In conjunction with the second aspect, in some implementations of the second aspect, the first index is located in the first correspondence, which is a correspondence between multiple data ranges and multiple indexes, and the multiple data ranges include the first data range.

[0045] In conjunction with the second aspect, in some implementations of the second aspect, the first information is carried in a first sequence on multiple subcarriers on one or more time-domain symbols in the first physical uplink control channel resource.

[0046] In conjunction with the second aspect, in some implementations of the second aspect, the first sequence is obtained through encoding processing, which includes shift register-based encoding processing or channel coding-based encoding processing.

[0047] In conjunction with the second aspect, in some implementations of the second aspect, the coding process of the channel coding includes scrambling based on the wireless network temporary identifier of the terminal device.

[0048] In conjunction with the second aspect, in some implementations of the second aspect, the first information further indicates the format of the first physical uplink control channel resource, the format of the first physical uplink control channel resource including a first format, which is a short format; or, the format of the first physical uplink control channel resource including a second format, which is a long format.

[0049] In conjunction with the second aspect, in some implementations of the second aspect, before the base station receives the first information, the method further includes: the base station sending third information, the third information being configured as one or more candidate resources for sending the first information, the one or more candidate resources including the first resource.

[0050] In conjunction with the second aspect, in some implementations of the second aspect, the third information configures one or more of the following for each of the one or more candidate resources: time-domain resource, frequency-domain resource, resource mapping style, or resource identifier.

[0051] In conjunction with the second aspect, in some implementations of the second aspect, the method further includes: the base station sending fourth information, the fourth information indicating a first resource among a plurality of candidate resources, the first resource being the resource for which the terminal device sent the first information.

[0052] In conjunction with the second aspect, in some implementations of the second aspect, the second information is downlink control information; and / or, the third information is radio resource control configuration information or radio resource control reconfiguration information; and / or, the fourth information is downlink control information, radio resource control configuration information or radio resource control reconfiguration information; and / or, the uplink resource is physical uplink shared channel resource.

[0053] In conjunction with the second aspect, in some implementations of the second aspect, the base station receiving first data on the first uplink resource includes: the base station receiving the first data and a second index on the first uplink resource, the second index indicating a second data volume range, and the amount of data remaining to be transmitted in the buffer of the terminal device belonging to the second data volume range.

[0054] Thirdly, a communication device is provided. In one design, the device may include modules corresponding to the methods / operations / steps / actions described in the first aspect or any embodiment of the first aspect. These modules may be hardware circuits, software, or a combination of hardware circuits and software. In one design, the device includes: a transceiver unit, configured to send first information requesting uplink authorization and indicating: a first data amount greater than or equal to the amount of data to be transmitted in the buffer of the terminal device; or a first index indicating a range of the first data amount, wherein the amount of data to be transmitted in the buffer of the terminal device belongs to the range of the first data amount. The transceiver unit is further configured to receive second information indicating a first uplink resource. The transceiver unit is further configured to send first data on the first uplink resource, the data to be transmitted including the first data.

[0055] Fourthly, a communication device is provided. In one design, the device may include modules corresponding to the methods / operations / steps / actions described in the second aspect or any of the embodiments of the second aspect. These modules may be hardware circuits, software, or a combination of hardware circuits and software. In one design, the device includes: a transceiver unit configured to receive first information requesting uplink authorization and indicating: a first data amount greater than or equal to the amount of data to be transmitted in the cache of a terminal device; or a first index indicating a range of the first data amount, where the amount of data to be transmitted in the cache of the terminal device belongs to the first data amount range. In response to the uplink authorization, a processing unit is configured to determine a first uplink resource based on the first data amount. The transceiver unit is further configured to send second information indicating the first uplink resource. The transceiver unit is also configured to receive first data on the first uplink resource, the data to be transmitted including the first data.

[0056] Fifthly, a communication device is provided, including a processor. The processor can implement the methods of the first to second aspects and any possible implementations thereof. Optionally, the communication device further includes a memory, and the processor is coupled to the memory and can be used to execute instructions in the memory to implement the methods of the first to second aspects and any possible implementations thereof. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface. In the embodiments of this application, the communication interface may be a transceiver, a pin, a circuit, a bus, a module, or other types of communication interface, and is not limited thereto.

[0057] In one implementation, the communication device is a communication equipment (such as a terminal device or access network equipment). When the communication device is a communication equipment, the communication interface can be a transceiver, or an input / output interface.

[0058] In another implementation, the communication device is a chip configured within a communication device. When the communication device is a chip configured within a communication device, the communication interface can be an input / output interface.

[0059] Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0060] A sixth aspect provides a processor, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute the methods described in the first to second aspects and any possible implementation thereof.

[0061] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0062] A seventh aspect provides a computer program product comprising: a computer program (also referred to as code or instructions) that, when executed, causes the methods described in the first to second aspects and any possible implementations of the first to second aspects to be executed or implemented.

[0063] Eighthly, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when the computer program is run, causes the methods described in the first to second aspects and any possible implementations of the first to second aspects to be executed or implemented.

[0064] A ninth aspect provides a chip system applied to a communication device, the chip system including one or more processors, the one or more processors being configured to invoke computer instructions to cause the communication device to perform the methods of the first to second aspects and any possible implementation thereof.

[0065] In a tenth aspect, a communication system is provided, comprising at least one network device and at least one terminal as described above.

[0066] It should be understood that the beneficial effects of the features corresponding to the first aspect in the second to tenth aspects can be referred to the relevant description of the first aspect above, and will not be repeated here. Attached Figure Description

[0067] Figure 1 This is a schematic diagram of the architecture of the communication system provided in the embodiments of this application;

[0068] Figure 2 This is a schematic diagram of a short BSR provided in an embodiment of this application;

[0069] Figure 3 This is a schematic diagram of a long BSR provided in an embodiment of this application;

[0070] Figure 4This is a schematic diagram of the uplink scheduling process provided in the embodiments of this application;

[0071] Figure 5 This is a schematic diagram of the available SR resources provided in the embodiments of this application;

[0072] Figure 6 This is a flowchart illustrating the communication method provided in an embodiment of this application;

[0073] Figure 7 This is a schematic diagram of the first type of first PUCCH resource provided in the embodiments of this application;

[0074] Figure 8 This is a schematic diagram of the second type of first PUCCH resource provided in the embodiments of this application;

[0075] Figure 9 This is a schematic diagram of the first candidate resource provided in the embodiments of this application;

[0076] Figure 10 This is a schematic diagram of the second candidate resource provided in the embodiments of this application;

[0077] Figure 11 This is a schematic diagram of a first type of terminal device providing resource indication according to an embodiment of this application;

[0078] Figure 12 This is a schematic diagram illustrating resource indication using the first and second terminal devices provided in the embodiments of this application;

[0079] Figure 13 This is a flowchart illustrating another communication method provided in an embodiment of this application;

[0080] Figure 14 This is a schematic block diagram of an example of a communication device provided in an embodiment of this application;

[0081] Figure 15 This is a schematic structural diagram of another example of the communication device provided in the embodiments of this application. Detailed Implementation

[0082] To facilitate understanding of the embodiments of this application, the following points will be explained first:

[0083] In the embodiments of this application, "instruction" may include direct instruction, indirect instruction, explicit instruction, and implicit instruction. When describing a certain instruction information for indicating A, it can be understood that the instruction information carries A, directly indicates A, or indirectly indicates A.

[0084] In the embodiments of this application, " / " can indicate that the objects before and after are in an "or" relationship. For example, A / B can mean A or B. "And / or" can be used to describe three relationships between the associated objects. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. A and B can be singular or plural.

[0085] In the embodiments of this application, "at least one" refers to one or more, and "more than one" refers to two or more, such as three, four or more. Similar expressions (such as at least one, at least one, etc.) are used in the same way. "At least one of the following," "one or more of the following," or similar expressions refer to any combination of these items, which may include only a single item or a combination of multiple items. For example, at least one of a, b, or c can represent: a, or b, or c; a and b; or a and c; or b and c; or a, b, and c. Where a, b, and c can be single or multiple.

[0086] In the embodiments of this application, in order to facilitate the description of the technical solutions of the embodiments of this application, the terms "first" and "second" may be used for distinction. The terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0087] In the embodiments of this application, the words "exemplary," "example," or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary," "example," or "for example" should not be construed as being more preferred or advantageous than other embodiments or designs. The use of the words "exemplary," "example," or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0088] In the embodiments of this application, "sending information / data" only indicates the direction of information / data transmission, including direct transmission through the device's communication interface (such as an air interface, or simply air interface). "Sending" can also be understood as the "output" of the module interface. "Sending" can include indirect transmission by the processing unit through the communication interface, that is, after the processing unit outputs information / data through the module interface, it is transmitted to the device's communication interface and then sent out. "Receiving information / data" only indicates the direction of information / data transmission, including direct reception through the communication interface. "Receiving" can also be understood as the "input" of the module interface. "Receiving information / data" can include indirect reception by the processing unit through the communication interface, that is, after the communication interface receives information / data, it is transmitted to the module interface of the processing unit and then input to the processing unit through the module interface. "Sending information / data to... (such as a terminal)" can be understood as the destination of the information being the terminal. It can include sending information / data directly or indirectly to the terminal. "Receiving information / data from... (such as a terminal)" can be understood as the source of the information being the terminal, and can include receiving information / data directly or indirectly from the terminal. Information / data may undergo necessary processing, such as format changes, between the source and destination, but the destination can understand the valid information / data from the source. Similar statements in the embodiments of this application can be understood in a similar way, and will not be repeated here.

[0089] The technical solutions of this application can be applied to various communication systems, such as Long Term Evolution (LTE) systems, 5th Generation (5G) communication systems, satellite communication systems, Wireless Fidelity (WiFi) systems, and the solutions provided in this application can also be applied to future communication systems or other communication systems. This application does not limit these applications.

[0090] Figure 1 This is a schematic diagram of the architecture of a communication system applicable to the communication method provided in the embodiments of this application. Figure 1 A schematic diagram of a possible, non-limiting system architecture is shown. (e.g.) Figure 1 As shown, the communication system 100 includes a radio access network (RAN) 10 and a core network (CN) 20. Optionally, the communication system 100 also includes an Internet 30. RAN 10 includes at least one RAN node (e.g., Figure 1 110a and 110b (collectively referred to as 110) and at least one terminal (such as Figure 1 RAN 10, denoted as RAN 10 (120a-120j), may also include other RAN nodes, such as wireless relay devices and / or wireless backhaul devices. Figure 1 (Not shown in the image). Terminal 120 is connected to RAN node 110 wirelessly. RAN node 110 is connected to core network 20 wirelessly or via wired connection. The core network equipment in core network 20 and RAN node 110 in RAN 10 can be different physical devices, or they can be the same physical device integrating core network logical functions and radio access network logical functions.

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

[0092] RAN node 110, sometimes also referred to as access network equipment, RAN entity, or access node, is part of the communication system and is used to help terminals achieve wireless access. Multiple RAN nodes 110 in communication system 100 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... Figure 1 Network element 120i can be a helicopter or a drone, and it can be configured as a mobile base station. For terminals 120j that access RAN 10 through network element 120i, network element 120i is a base station; however, for base station 110a, network element 120i is a terminal. RAN node 110 and terminal 120 are sometimes referred to as communication devices, for example... Figure 1 Network elements 110a and 110b can be understood as communication devices with base station functions, while network elements 120a-120j can be understood as communication devices with terminal functions.

[0093] In one possible scenario, a RAN node can be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next-generation NodeB (gNB), a next-generation base station in a 6G mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system, etc. A RAN node can also be a macro base station (such as...) Figure 1 110a), micro base stations or indoor stations (such as Figure 1 In CRAN scenarios, RAN nodes can be 110b), relay nodes or donor nodes, or wireless controllers. Optionally, RAN nodes can also be servers, wearable devices, vehicles, or in-vehicle equipment. For example, in vehicle-to-everything (V2X) technology, the access network equipment can be a roadside unit (RSU).

[0094] 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 central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be set up 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 remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0095] 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 in its embodiments. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in the embodiments of this application can be implemented through software modules, hardware modules, or a combination of software modules and hardware modules.

[0096] 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), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, etc. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc.

[0097] In this application embodiment, the terminal and network device can be hardware devices, or software functions running on dedicated hardware, or software functions running on general-purpose hardware, such as virtualization functions instantiated on a platform (e.g., cloud platform), or entities that include dedicated or general-purpose hardware devices and software functions. This application embodiment does not limit the specific form of the terminal and network device.

[0098] To better understand the methods provided in the embodiments of this application, the relevant technologies and terms involved in the embodiments of this application will be briefly explained below.

[0099] 1. Encoding method based on shift register

[0100] Shift register-based encoding methods utilize linear combinations and shifting of register bits to generate sequences. A shift register is a sequential logic circuit that stores data and can shift data bit by bit to the left or right under the control of a clock signal. Various sequence codes, such as pseudo-random sequences, can be generated through predefined feedback logic (such as XOR operations).

[0101] Compared to traditional channel coding (such as low-density parity check (LDPC) codes) which achieves error correction by adding redundant parity bits, shift register-based coding does not directly address channel noise or bit error tolerance. Instead, it enhances the anti-interference capability of the communication system and improves communication reliability by leveraging the characteristics of the sequence itself.

[0102] 2. Channel-based coding method

[0103] Channel coding-based methods enhance data transmission reliability by introducing redundant information. Channel coding schemes can include, for example, block codes (such as Hamming codes), convolutional codes, polar codes, or LDPC codes. Channel coding does not rely on shift register state transitions and feedback logic to generate specific sequences; instead, it redundantly expands the original data, adding redundant information during the coding process to improve transmission reliability.

[0104] When a terminal device uses channel-based coding, it can choose different code rates, such as 1 / 3 or 2 / 3. The amount of data after encoding will vary depending on the code rate used. For example, with a 1 / 3 code rate, every 3 bits of encoded output contains 1 bit of original information and 2 bits of redundant bits for error correction and detection. Assuming the terminal device has 100 bits of data to transmit, the data encoded at a 1 / 3 code rate will be 300 bits. Alternatively, with a 2 / 3 code rate, every 3 bits of encoded output contains 2 bits of original information and 1 bit of redundant bits for error correction and detection. Assuming the terminal device has 100 bits of data to transmit, the data encoded at a 2 / 3 code rate will be 150 bits.

[0105] 3. Uplink data buffer

[0106] Uplink data buffer, also known as uplink data cache, or simply cache or buffer area, refers to the storage area in a wireless communication system used by a terminal device to temporarily store uplink data (or uplink service data) to be transmitted. When a terminal device needs to send uplink data but has not obtained uplink transmission resources allocated to it by the base station, the data can be temporarily stored in this uplink data buffer.

[0107] 4. Scheduling Request (SR)

[0108] SR (Signaling Request) is a key control signaling mechanism used by terminal devices to request uplink resource allocation from network devices. When a terminal device has data to send but has not obtained uplink transmission resources, it notifies the network device of its transmission request via SR. SR can include 1 bit. The network device can perform energy detection on the PUCCH resource to determine that the terminal device has sent SR. In response to the SR, the network device can allocate uplink transmission resources to the terminal device. Specifically, the network device can send DCI (Distributed Control Information) to the terminal device, which indicates the uplink transmission resources allocated to the terminal device by the network device.

[0109] 5. Buffer Status Report (BSR)

[0110] After receiving a DCI (Distributed Content Response) from the network device in response to a Reporting Request (SR), the terminal device can determine the uplink transmission resources allocated to it by the network device. The terminal device can then send a Backlink Reporting Request (BSR) to the network device using these uplink resources. The BSR is a crucial mechanism in wireless communication systems for optimizing uplink (UL) resource allocation and data transmission efficiency. The terminal device sends a BSR to the network device (such as a base station) to report the buffer status of its uplink services, or, more specifically, to report the status of its uplink data buffer. Optionally, the terminal device can send the BSR through a Media Access Control (MAC) control element (CE).

[0111] After receiving a BSR from a terminal device, the network device can understand the terminal device's buffer status and thus decide when and how much uplink resources to allocate for uplink data transmission. This enables the network device to allocate uplink transmission resources more accurately to the terminal device.

[0112] To reduce the number of bits transmitted over the air interface and the signaling overhead caused by transmitting BSRs, terminal devices can report the amount of buffered data in units of logical channel groups (LCGs). Specifically, a BSR indicates the amount of data to be transmitted in the buffer corresponding to an LCG. An LCG can contain one or more logical channels. When grouping logical channels, grouping can be based on the Quality of Service (QoS) requirements of the logical channels; for example, logical channels belonging to an LCG may have similar QoS requirements. Different LCGs correspond to different LCGIDs, and each LCGID corresponds to a preset priority. Network devices can determine the order of uplink transmission resource allocation based on the priority corresponding to the LCG ID.

[0113] Optionally, the BSR may specifically include short BSR, truncated BSR, or long BSR. When the terminal device needs to report the amount of data to be transmitted in the buffer corresponding to one logical channel group, the terminal device reports a short BSR. When the terminal device needs to report the amount of data to be transmitted in the buffer corresponding to more than one LCG, but due to limited available BSR resources, it can only send a BSR corresponding to one LCG, the terminal device reports a truncated BSR. When the terminal device reports the amount of data to be transmitted in the buffer corresponding to more than one LCG, the terminal device may report a long BSR. The amount of data to be transmitted in the buffer can be referred to as the buffer size (BS), and these terms can be used interchangeably in this embodiment.

[0114] The following is combined with Figure 2 and Figure 3 The various formats of BSR MAC CE for different BSR types are described, but it should be understood that the embodiments of this application are not limited thereto.

[0115] like Figure 2 As shown, when the terminal device reports a short BSR or a truncated BSR, the BSR MAC CE can occupy 1 byte (octet). Figure 2Oct1 in the BSR includes an LCG identifier (ID) field and a buffer data size field. For example, the LCG ID can include 3 bits. Network devices can determine the corresponding priority based on this 3-bit LCG ID in the BSR, thereby determining the order in which uplink transmission resources are allocated to the BSRs of different terminal devices. The buffer data size indicates the amount of data to be transmitted in the buffer corresponding to this LCG ID, and can include 5 bits.

[0116] It should be noted that, Figure 2 The format of BSR MAC CE shown is merely an exemplary description for the purpose of understanding the embodiments of this application, and is not a specific limitation on the embodiments of this application. In practical applications, the number of bits occupied by the LCG ID field and the cached data volume field can be predefined by the protocol, for example... Figure 2 As shown, the protocol can predefine that the LCG ID field occupies 3 bits in one byte, and the cached data size field occupies the remaining 5 bits. Alternatively, the protocol can also predefine that the LCG ID field occupies 2 bits in one byte, and the cached data size field occupies the remaining 6 bits. This application embodiment does not impose any restrictions on this.

[0117] like Figure 3 As shown, when the terminal device reports a long BSR type, the BSR MAC CE can occupy 3 bytes (e.g., Figure 3 The terminal device can report the BSR of all LCGs using the three bytes (Oct1, Oct2, and Oct3). Assuming the protocol predefines four logical channel groups, denoted as LCG ID1, LCG ID2, LCG ID3, and LCG ID4, these four LCG IDs correspond one-to-one with four buffer data size fields in the long BSR MAC CE. These four buffer data size fields can be sequentially denoted as buffer data size #1, buffer data size #2, buffer data size #3, and buffer data size #4. For example, each buffer data size field can occupy 6 bits. Figure 3 As shown, cached data size #1 can be the cached data size corresponding to LCG ID1, and this cached data size #1 occupies the first 6 bits of Oct1. Similarly, cached data size #2 can be the cached data size corresponding to LCG ID2, and the 6 bits occupied by this cached data size #2 include the last 2 bits of Oct1 and the first 4 bits of Oct2. Cached data size #3 can be the cached data size corresponding to LCG ID3, and this cached data size #3 occupies the last 4 bits of Oct2 and the first 2 bits of Oct3. Cached data size #4 can be the cached data size corresponding to LCG ID4, and this cached data size #4 occupies the last 6 bits of Oct3.

[0118] It should be noted that, Figure 3 The BSR MAC CE shown occupies 3 bytes, and each cached data field occupies 6 bits, which is only an exemplary description for the purpose of understanding the embodiments of this application, and is not a specific limitation on the embodiments of this application. In practical applications, each cached data field may occupy more or fewer bits, and the corresponding BSR MAC CE may occupy more or fewer bytes. The embodiments of this application do not limit this.

[0119] Optionally, the cached data volume field in the BSR can carry the index value corresponding to the data volume of the cached data to be transmitted for the LCG ID in the BSR. The following uses Table 1 as an example to illustrate the correspondence between the index values ​​carried in the BSR and the data volume. As shown in Table 1, the data volume corresponding to index value 0 is 0, meaning there is no data to be transmitted in the corresponding cache. The data volume corresponding to index value 63 is greater than 150,000 bytes, meaning the data volume of the cached data to be transmitted is greater than 150,000 bytes. When the terminal device reports the BSR, it can report the index value corresponding to the data volume of the data to be transmitted based on the correspondence shown in Table 1. For example, when the terminal device has 30 bytes of data to send, 30 bytes falls within the data volume range corresponding to index value 8. Therefore, the terminal device can report index value 8 in the BSR; for example, the cached data volume field in the BSR carries index value 8. After receiving the BSR, the base station can determine that the amount of data to be transmitted by the terminal device is between 26 and 31 bytes based on the index value of 8 carried in the cached data volume field of the BSR and the correspondence between the index value and the cached data volume range shown in Table 1.

[0120] Table 1

[0121] index Data volume range: BS (bytes) index Data volume range: BS (bytes) 0 BS=0 32 1132<BS<=1326 1 0<BS<=10 33 1326<BS<=1552 2 10<BS<=12 34 1552<BS<=1817 3 12<BS<=14 35 1817<BS<=2127 4 14<BS<=17 36 2127<BS<=2490 5 17<BS<=19 37 2490<BS<=2915 6 19<BS<=22 38 2915<BS<=3413 7 22<BS<=26 39 3413<BS<=3995 8 26<BS<=31 40 3995<BS<=4677 9 31<BS<=36 41 4677<BS<=5476 10 36<BS<=42 42 5476<BS<=6411 11 42<BS<=49 43 6411<BS<=7505 12 49<BS<=57 44 7505<BS<=8787 13 57<BS<=67 45 8787<BS<=10287 14 67<BS<=78 46 10287<BS<=12043 15 78<BS<=91 47 12043<BS<=14099 16 91<BS<=107 48 14099<BS<=16507 17 107<BS<=125 49 16507<BS<=19325 18 125<BS<=146 50 19325<BS<=22624 19 146<BS<=171 51 22624<BS<=26487 20 171<BS<=200 52 26487<BS<=31009 21 200<BS<=234 53 31009<BS<=36304 22 234<BS<=274 54 36304<BS<=42502 23 274<BS<=321 55 42502<BS<=49759 24 321<BS<=376 56 49759<BS<=58255 25 376<BS<=440 57 58255<BS<=68201 26 440<BS<=515 58 68201<BS<=79846 27 515<BS<=603 59 79846<BS<=93479 28 603<BS<=706 60 93479<BS<=109439 29 706<BS<=826 61 109439<BS<=128125 30 826<BS<=967 62 128125<BS<=150000 31 967<BS<=1132 63 BS>150000

[0122] It is understandable that, based on the amount of cached data corresponding to one or more LCGs carried in the BSR reported from the terminal device, BSRs can be classified into short BSRs, truncated BSRs, or long BSRs. Optionally, based on the reason that triggers the terminal device to report a BSR, BSRs can also be classified into regular BSRs, periodic BSRs, or padding BSRs.

[0123] Regular BSR: When data from a higher-priority logical channel enters the terminal device's buffer (or transmission buffer queue), or when the terminal device's serving cell changes, the terminal device reports a regular BSR.

[0124] Periodic BSR: When the periodic BSR timer expires, the terminal device reports the periodic BSR. Optionally, the timer for the periodic BSR can be predefined by the protocol, defined, or pre-configured by the base station to the terminal device via signaling (such as RRC signaling). For example, the base station can configure the timer PERIODIC_BSR_TIMER for the terminal device. After the timer expires, the terminal device reports the periodic BSR in the next uplink data transmission subframe.

[0125] Filling BSR: When a base station allocates uplink resources to a terminal device and the terminal device uses these uplink resources to transmit uplink data, if there is remaining space in the allocated uplink resources and the remaining space (or fill size) can accommodate the BSR, the terminal device can use the fill size to report a fill BSR.

[0126] 6. Uplink scheduling

[0127] It can also be called uplink grant (UL grant). Uplink scheduling can be understood as the network device scheduling the terminal device to transmit uplink data. The network device can implement uplink scheduling through DCI. This DCI can also be called DCI for uplink scheduling, uplink scheduling DCI, DCI for uplink grant, or uplink grant DCI.

[0128] Network devices can use Uplink Scheduling Control (DCI) to instruct network devices on the uplink resources allocated for uplink data transmission to terminal devices, as well as modulation and coding-related information. Uplink resources include frequency domain resources and time domain resources, on which terminal devices can send uplink data to network devices. Modulation and coding-related information indicates the modulation scheme and coding rate used by the terminal device for data processing. However, this embodiment is not limited to this; for example, Uplink Scheduling DCI can also instruct network devices on power control-related information allocated to terminal devices, etc. For simplicity, these are not listed here.

[0129] The following example uses network equipment as a base station. Figure 4 This section describes the process by which terminal devices in the current system request and execute uplink scheduling. For example... Figure 4 As shown, this process may include, but is not limited to, the following steps:

[0130] S401, the terminal device detects that uplink data has arrived and triggers the BSR reporting process.

[0131] When a terminal device detects uplink data to be transmitted in its cache, it triggers a BSR reporting process. Specifically, the reporting process involves the terminal device generating a BSR, which indicates the cache status of the terminal device (such as the amount of uplink data to be transmitted in the cache) and preparing to send the BSR to the base station.

[0132] S402, the terminal device triggers SR reporting, that is, the terminal device sends SR to the base station.

[0133] The specific process by which the terminal device triggers the SR (Streaming Service) is that the terminal device notifies the base station of its uplink transmission needs through the SR, requesting the base station to allocate uplink resources for the terminal device. Depending on the resources used by the terminal device to send the SR, SRs can be divided into dedicated SRs (D-SRs) and random access SRs (RA-SRs).

[0134] The dedicated SR is carried on pre-configured PUCCH resources (hereinafter referred to as SR resources) associated with the SR. These SR resources are dedicated to the terminal device and allocated to it by network equipment (such as a base station). The SR resources of different terminal devices are unique in the time domain, frequency domain, or code domain, avoiding resource conflicts that may occur when different terminal devices send SRs. Furthermore, to enable the base station to identify which terminal device the dedicated SR carried on the SR resource originates from, the base station can maintain a mapping between terminal devices and SR resources. When the base station detects an SR carrying an SR resource through energy detection, it can determine which terminal device the SR originates from based on the mapping between terminal devices and SR resources.

[0135] When a terminal device is not allocated SR resources, meaning it has no available PUCCH resources to send an SR to the base station, a contention-based random access procedure can replace the function of the SR for the terminal device to request uplink scheduling. In other words, the terminal device can implicitly transmit an SR to the base station via a random access procedure on the physical random access channel (PRACH). This SR sent to the base station via the random access procedure is called RA-SR.

[0136] Specifically, a terminal device can trigger an SR report by sending an SR to the base station during a regular BSR cycle. For ease of understanding, the following explanation will illustrate this further. Figure 5 The process of triggering SR reporting by the terminal device is explained. Assuming the SR period is 6 time units, then... Figure 5As shown, the offset between two adjacent available SR resources in the time domain is 6 time-domain units. When the terminal device detects uplink data arrival but has no available (or insufficient) uplink resources to send a BSR, the terminal device will send an SR to the base station when the next available SR resource arrives, and simultaneously start an SR disable timer. Within the time limit of this SR disable timer, the terminal device will not send SRs to the base station. After the disable timer expires, if the terminal device has not received an uplink schedule from the base station, the terminal device can send the next SR to the base station when the next available SR resource arrives. If the number of SR transmissions by the terminal device is less than the maximum number of SR transmissions, the terminal device will retransmit the SR and start the SR disable timer again. If the terminal device receives an uplink schedule from the base station (this uplink schedule can be, for example, DCI), the terminal device will stop the disable timer.

[0137] Optionally, the aforementioned SR period and maximum number of SR transmissions can be predefined by the protocol, defined, or pre-configured by the base station to the terminal device via signaling (such as RRC signaling), or configured by the base station based on the terminal device's capabilities and configured by the base station via signaling. For example, the base station can configure one or more SRs for the terminal device based on the terminal device's capabilities.

[0138] S403, the base station sends DCI to the terminal equipment.

[0139] After receiving the SR from the terminal device in S404, the base station can only determine that the terminal device has uplink data to be transmitted. However, since the SR does not indicate the specific amount of uplink data to be transmitted, the base station cannot determine how much uplink resource should be allocated to the terminal device to transmit the uplink data. The base station can send an Uplink Scheduling Control (DCI) to the terminal device in S403 to allocate some uplink resources so that the terminal device can send a BSR on those uplink resources. This allows the base station to obtain the range of data volume in the terminal device's buffer to be transmitted based on the BSR.

[0140] The uplink scheduling DCI can be carried on physical downlink control channel (PDCCH) resources. The DCI includes uplink scheduling information, such as the uplink resources allocated by the base station to the terminal equipment, modulation and coding related information, and the uplink resources can specifically be physical uplink shared channel (PUSCH) resources.

[0141] S404, the terminal device sends BSR and uplink data to the base station on the PUSCH resource.

[0142] The terminal device can send a BSR to the base station on the PUSCH resource allocated to it by the base station through DCI. The base station can then determine the corresponding priority based on the LCG ID in the BSR, and determine the amount of data to be transmitted in the cache corresponding to the LCG ID based on the cache data volume field in the BSR. If there is spare capacity in the PUSCH resource, the terminal device can also send a portion of the cached uplink data to the base station on that PUSCH resource.

[0143] S405, the base station sends DCI to the terminal device.

[0144] After the base station obtains the BSR reported by the terminal device on the PUSCH resources in S404, the base station can determine the corresponding priority and buffer data amount based on the BSR. Based on the priority, the base station can determine when to schedule the terminal device to send uplink data, and based on the buffer data amount, determine how much uplink resource to allocate for uplink data transmission by the terminal device. In S405, the base station resends the uplink scheduling DCI to the terminal device. This DCI can be carried on the PDCCH, and it indicates the uplink resources (i.e., PUSCH resources) allocated by the network device to the terminal device based on the BSR.

[0145] S406, the terminal device sends uplink data and BSR to the base station.

[0146] Since the data to be transmitted in the buffer may accumulate continuously, the terminal device sends a BSR (Background Scheduler) while sending uplink data on the PUSCH resources allocated to it by the network device. The BSR indicates the amount of data to be transmitted in the current buffer. When the amount of data to be transmitted in the terminal device's buffer indicated by the BSR is 0 (e.g., the index value carried by the BSR is 0), the base station can stop uplink scheduling.

[0147] In the above, as Figure 4 During the process, between the terminal device detecting the arrival of uplink data and the terminal device sending uplink data, there are multiple information exchanges between the terminal device and the network device, resulting in significant latency. For example, if the terminal device fails to send the SR, the SR is lost during transmission, or the base station fails to decode the SR, causing the base station to not receive the scheduling request from the terminal device, the base station cannot allocate uplink resources to the terminal device in a timely manner.

[0148] Or even if the base station receives an SR from the terminal device, due to the time slot allocation of Time Division Duplex (TDD), there may be a long delay between the terminal device detecting the arrival of uplink data and the terminal device sending uplink data. For example, Figure 4 In the middle, D represents the downlink time slot, and U represents the uplink time slot, that is, the... Figure 4The time slot configuration shown is "1U:4D", meaning that in a 5ms half-frame, there is one uplink time slot and four downlink time slots. It can be understood that with a "1U:4D" time slot configuration, after the terminal device detects the arrival of uplink data, it sends a Service Request (SR) to the base station in the first uplink time slot (i.e., performs S402 in the first uplink time slot). The first uplink data (data) and the BSR can only be sent to the base station in the second uplink time slot after four downlink time slots. Similarly, the next uplink data (data) and BSR are sent in the third uplink time slot, and so on, until the base station receives a BSR indicating that the amount of data the terminal device needs to transmit is 0.

[0149] Therefore, in the current uplink transmission process, when data arrives at the terminal device (or when the terminal device has a data transmission requirement), there is a problem that the terminal device cannot transmit uplink data to the base station in a timely manner. This has a significant impact on the transmission of latency-sensitive data (such as service data that requires low latency), resulting in low communication reliability.

[0150] To address the aforementioned issues, this application proposes that when a terminal device has a data transmission requirement, it simultaneously requests uplink scheduling and reports the cached data volume (or data range) to the base station by reporting the amount or range of data to be transmitted in its cache. This allows the base station to know the amount (or data range) of data to be transmitted at the same time as determining the terminal device's uplink scheduling request. This enables the base station to allocate uplink resources to the terminal device promptly, without requiring an uplink scheduling process and subsequent uplink transmission to obtain the cached data volume. This helps reduce uplink scheduling latency and improves communication reliability.

[0151] The methods provided in the embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0152] It should be understood that, in the embodiments of this application, the communication method provided by the embodiments of this application is shown from the perspective of the interaction between functional nodes in the terminal device, base station, and core network, but the embodiments of this application do not limit the executing subject of the method. In each embodiment, the function of the terminal device can also be implemented by modules (such as chips, chip systems, processors, logic circuits, or software) configurable in (or used in) the terminal device. In each embodiment, the function of the base station (source base station / target base station) can be implemented by the access network nodes described above. Alternatively, it can be implemented by modules (such as chips, chip systems, processors, logic circuits, or software) configurable in the base station. When the executing subject is a module in the terminal device or base station, receiving / transmitting can be understood as input / output, that is, the module communicates with other modules or components of the terminal device or base station. Furthermore, the operation performed by a single executing subject can also be divided into operations performed by multiple executing subjects, which can be logically and / or physically separated. For example, the operation performed by the base station can be divided into operations performed by at least one of CU, DU, RU, etc.

[0153] Figure 6 This is a schematic flowchart of the communication method provided in the embodiments of this application. Figure 6 Taking a network device as a base station as an example, the communication method of this application embodiment will be described. The method may include, but is not limited to, the following S601 to S604.

[0154] S601, the terminal device sends first information to the base station, the first information requesting uplink authorization and indicating a first data volume or a first index.

[0155] Uplink grant (UL grant) can also be called uplink scheduling, or in other words, the first information can request uplink scheduling.

[0156] Optionally, when a terminal device has an uplink scheduling (or uplink authorization) requirement, the terminal device can send a first message to the base station. Accordingly, after receiving the first message from the terminal device, the base station can determine that the terminal device has an uplink scheduling requirement, and further, the base station can allocate uplink resources to the terminal device. Specifically, an uplink scheduling requirement for the terminal device can occur when data arrives at the terminal device, and the amount of data in the terminal device's buffer (or cache) changes from empty to non-empty. In this case, the terminal device can send a first message to the base station to request uplink resources. However, it should be understood that the embodiments of this application are not limited to this. In practical applications, when the terminal device sends uplink data to the base station but some data in the buffer is still not fully transmitted (i.e., the amount of data in the buffer changes from a large amount to a small amount), the terminal device can also send a first message to the base station. That is to say, the embodiments of this application do not limit the timing of the terminal device sending a first message to the base station to request uplink authorization. When the terminal device sends a scheduling request to the base station can be predefined by the protocol, defined, or pre-configured by the base station to the terminal device through signaling (such as RRC signaling).

[0157] The terminal device indicates the amount of data (or an approximate value of the data) to be transmitted in its buffer to the base station, either directly or indirectly, by indicating a first data amount or a first index. This allows the base station to allocate uplink resources to the terminal device based on the amount of data to be transmitted (or an approximate value of the data). For ease of understanding, the process of the terminal device indicating the first data amount or the first index to the base station is described in detail below. See Implementation Method 1 and Implementation Method 2 for details.

[0158] In implementation method 1, the first information indicates the first data volume.

[0159] In one example, the first data volume is greater than or equal to the amount of data to be transmitted in the terminal device's cache.

[0160] For example, if the amount of data to be transmitted in the terminal device's buffer is 50 bytes, then the first data amount is 50 bytes. The first information may include field A, which represents the first data amount. That is, the terminal device can directly indicate the first data amount to the base station through this first information. Optionally, the terminal device can indicate the first data amount to the base station in bytes or bits. For example, assuming it's in bytes, if the terminal device detects that the amount of uplink data to be transmitted in its buffer is 50 bytes, and the first data amount equals the amount of data to be transmitted in the terminal device's buffer, then field A in the first information is 50. Correspondingly, after receiving the first information from the terminal device, the base station can determine the first data amount based on field A in the first information. For example, if the base station determines that field A is 50, it means the terminal device is requesting uplink resources capable of carrying 50 bytes of data.

[0161] Optionally, to reduce the resource overhead of the terminal device sending the first information, the terminal device can indicate a coarse-grained first data amount to the base station. For example, the terminal device can indicate the first data amount to the base station in units of 10 bytes. Suppose the terminal device detects that the amount of uplink data to be transmitted in the buffer is 50 bytes, and field A in the first information is 5. When the buffered data amount is not an integer multiple of 10 bytes, the terminal device can round up to an integer multiple of 10 bytes. For example, when the buffered data amount is greater than 40 bytes but less than or equal to 50 bytes, field A in the first information sent by the terminal device is always 5. That is, the first data amount indicated by the first information may be greater than or equal to the amount of data to be transmitted in the buffer. Correspondingly, after receiving the first information from the terminal device, the base station can determine the first data amount based on field A in the first information. For example, if the base station determines that the amount of data in the terminal device's buffer is less than or equal to 50 bytes based on field A being 5, the base station can allocate uplink resources to the terminal device based on this first data amount.

[0162] It should be noted that the above-described example of the terminal device indicating the first data amount to the base station in units of 10 bytes is merely an exemplary description for the purpose of understanding the embodiments of this application. In practical applications, the first data amount can also be in other units, such as 50 bytes or 100 bits. Specifically, the unit in which the terminal device indicates the first data amount can be pre-configured in the terminal device, or it can be pre-defined by the protocol, or it can be pre-configured to the terminal device by the base station through signaling (RRC signaling). The embodiments of this application do not limit this.

[0163] In implementation method 2, the first information indicates the first index.

[0164] The first index indicates a first data volume range, and the amount of data to be transmitted in the terminal device's buffer belongs to this first data volume range. In other words, the terminal device indicates to the base station the data volume range to which the data to be transmitted belongs, thus indicating an approximate value of the data volume. Furthermore, the base station can determine approximately how much uplink resource needs to be allocated to the terminal device based on this approximate value. For example, if the amount of data to be transmitted in the terminal device's buffer is 50 bytes, and this data volume belongs to the first data volume range (m, n), then the terminal device can indicate the first data volume range (m, n) to the base station by including the first index in the first information. Correspondingly, after receiving this first information, the base station can determine the first data volume range (m, n) corresponding to the first index based on the first index in the first information, and can then allocate uplink resources to the terminal device based on this first data volume range. For ease of understanding, the implementation method for the terminal device to determine the first index is described below.

[0165] Optionally, the terminal device can determine a first index based on the data volume of the data to be transmitted and a first correspondence relationship. The first correspondence relationship is a correspondence between multiple data volume ranges and multiple indices. The multiple data volume ranges include a first data volume range, and the multiple indices include the first index. The first data volume range corresponds to the first index. The terminal device can determine the first data volume range to which the data volume of the data to be transmitted belongs from the first correspondence relationship, and further determine the first index corresponding to the first data volume range. Then, it indicates the first index to the base station.

[0166] For ease of understanding, the first correspondence is illustrated in a table below. However, the embodiments of this application are not limited to this; the first correspondence can also be represented by other mapping methods (such as arrays, matrices, etc.). For the sake of brevity, these will not be listed here.

[0167] Table 2 is a schematic diagram of the first correspondence provided in the embodiments of this application. For ease of understanding, the indices of the first correspondence in this schematic diagram are illustrated using 1, 2, 3, ... as examples. As shown in Table 2, the index corresponding to the data range (0, m1) is 1, the index corresponding to the data range (m1, m2) is 2, and the index corresponding to the data range (m2, m3) is 3.

[0168] For example, when the terminal device detects that the amount of data to be transmitted in the buffer is ∈ (0, m1], the first index in the first information sent by the terminal device to the base station is 1. Accordingly, after receiving the first information from the terminal device, the base station can determine the amount of data to be transmitted in the terminal device's buffer ∈ (0, m1) based on the first index being 1. Other data ranges in the first correspondence are similar to this data range (0, m1], and for the sake of simplicity, they will not be listed here.

[0169] Optionally, the threshold values ​​for each data range, such as m1, m2, and m3, can be predefined by the protocol, defined, or pre-configured by the base station to the terminal device via signaling (such as RRC signaling), or determined by the base station based on the capabilities of the terminal device and configured to the terminal device, such as m1 = 10, m2 = 20, m3 = 50, etc. The threshold values ​​for each data range, such as m1, m2, and m3, can be any number greater than 0, and this application embodiment does not impose any restrictions on this.

[0170] Table 2

[0171] index Data volume range (bytes) 1 (0，m1] 2 (m1, m2) 3 (m2, m3) … …

[0172] It should be noted that the data ranges and corresponding indexes shown in Table 2 are merely exemplary descriptions for the purpose of understanding the embodiments of this application, and are not specific limitations on the embodiments of this application. In practical applications, the data ranges and corresponding indexes can be predefined by the protocol, defined, or pre-configured by the base station to the terminal device through signaling (such as RRC signaling), or configured to the terminal device, so that the base station and the terminal device can reach a consensus on multiple data ranges and corresponding indexes.

[0173] It should also be understood that the embodiments of this application do not limit the method of determining the multiple data ranges in the first correspondence. Specifically, the methods of determining the multiple data ranges may include, but are not limited to, the following methods 2-1 and 2-2:

[0174] Method 2-1: Multiple data ranges are determined by the upper and lower limits of each range.

[0175] For example, for the multiple data ranges shown in Table 2, the protocol can define, or the base station can indicate, the upper and lower limits of each data range to the terminal device. Further, the base station can determine multiple data ranges based on the upper and lower limits of each range. For example, the terminal device can determine the data range corresponding to index 1 as 0 to m1 based on the lower limit 0 and the upper limit m1, and can determine the data range corresponding to index 2 as m1 to m2 based on the lower limit m1 and the upper limit m2, and so on. The terminal device can determine the index of each data range in the first correspondence.

[0176] Furthermore, whether each data range includes its own threshold value can be predefined by the protocol, defined, or pre-configured by the base station to the terminal device via signaling (such as RRC signaling). For example, the protocol can predefine that each data range does not include the lower threshold value but includes the upper threshold value, then the data range corresponding to index 1 is (0, m1], and the data range corresponding to index 2 is (m1, m2). Alternatively, the protocol can also predefine that it includes the lower threshold value but does not include the upper threshold value; this application embodiment does not impose such restrictions.

[0177] Method 2-2: Multiple data ranges are determined by the upper limit of each range.

[0178] For example, for the multiple data ranges shown in Table 2, the protocol can explicitly define them, or the base station can explicitly indicate the upper limit of each data range to the terminal device. The terminal device can determine that the data range corresponding to index 1 is less than m1 based on the upper limit m1, and can determine that the data range corresponding to index 2 is less than m2 based on the upper limit m2, and so on. The lower limit of the data range corresponding to index 1 can be predefined by the protocol, defined, or pre-configured by the base station to the terminal device through signaling (such as RRC signaling), or configured to the terminal device, for example, it can be 0 or 1, etc. This application embodiment does not limit this.

[0179] The lower limit of each data volume range corresponding to indices other than index 1 can be the upper limit of the previous range. That is, the terminal device determines the lower limit of each data volume range based on the upper limit of the previous range. For example, if the upper limit of the previous range of the data volume range corresponding to index 2 is m1, then the terminal device can determine that the lower limit of the data volume range corresponding to index 2 is m1. The determination of the lower limit of other data volume ranges is similar, and for the sake of simplicity, they will not be listed one by one here.

[0180] The specific method used by the terminal device to determine the range of data quantities in the first correspondence relationship, whether it is method 2-1 or method 2-2, can be predefined by the protocol, defined, or pre-configured by the base station to the terminal device via signaling (such as RRC signaling). This application embodiment does not impose any limitations on this. Furthermore, the methods 2-1 and 2-2 described above for determining the range of data quantities in the first correspondence relationship are merely exemplary descriptions for ease of understanding of this application embodiment and are not specific limitations on this application embodiment. In practical applications, the terminal device can also use other methods to determine the range of data quantities in the first correspondence relationship, so that the terminal device and the base station can reach a consensus on the multiple data quantity ranges and multiple indices included in the first correspondence relationship. This application embodiment does not impose any limitations on this.

[0181] According to the above method, the terminal device can determine the first data volume range to which the data volume of the data to be transmitted in the buffer belongs, and can send the first index corresponding to the first data volume range to the base station, so that the base station can determine the first data volume range and allocate uplink resources to the terminal device based on the first data volume range. Specific implementation methods for the terminal device to indicate the first index to the base station may include, but are not limited to, the following:

[0182] Optionally, the first information may include field B, which represents the first index. For example, if field B is 1, it indicates that the data volume range of the data to be transmitted in the terminal device's cache is (0, m1]; if field B is 2, it indicates that the data volume range of the data to be transmitted in the terminal device's cache is (m1, m2]; if field B is 3, it indicates that the data volume range of the data to be transmitted in the terminal device's cache is (m2, m3], ...

[0183] Assuming the range of the first data volume to which the first data volume belongs is (m1, m2], then the first index is 2, which means that field B in the first information is 2. Accordingly, the base station receives the first information from the terminal device, and the terminal device determines that the range of the first data volume to which the first data volume belongs is (m1, m2] based on the fact that field B in the first information is 2, and can allocate uplink resources to the terminal device based on this range of the first data volume.

[0184] It should be noted that the indices 1, 2, and 3 in the first correspondence shown in Table 2 above are merely exemplary descriptions for the purpose of understanding the embodiments of this application, and are not specific limitations on the embodiments of this application. In actual applications, each index can also be other values, specifically, they can be predefined by the protocol, defined, or pre-configured by the base station to the terminal device through signaling (such as RRC signaling), or configured to the terminal device. The embodiments of this application do not impose any restrictions on this.

[0185] According to Embodiment 1 or Embodiment 2 described above, the terminal device requests uplink authorization from the base station by indicating a first data volume or a first data volume range, thereby enabling the terminal device to simultaneously request uplink authorization and report cached data volume. The base station can determine whether the terminal device is requesting uplink authorization based on the first data volume or the first data volume range, and can allocate appropriate uplink resources to the terminal device based on this first data volume or data volume range. In specific implementations, the first information can be predefined by the protocol (either Embodiment 1 or Embodiment 2), or it can be pre-configured by the base station for the terminal device via signaling. Alternatively, the protocol can predefine multiple implementation methods. In practical applications, the terminal device can send the first data volume or first index corresponding to the implementation method to the base station. According to the above scheme, the terminal device can simultaneously request uplink authorization from the base station and report cached data volume through the first information. This allows the base station to allocate uplink resources to the terminal device promptly based on the first data volume, without requiring an uplink scheduling and subsequent uplink transmission to obtain the data volume in the terminal device's cache. This helps reduce uplink scheduling transmission latency and improve communication reliability.

[0186] To improve the efficiency of base station allocation of uplink resources to terminal devices, the first information can also indicate data priority. This data priority corresponds to the priority of the data to be transmitted in the buffer indicated by the first information. Accordingly, after receiving the first information, the base station can obtain the amount of data to be transmitted in the terminal device's buffer and its corresponding priority. Based on the data amount and priority, the base station can allocate uplink resources to the terminal device. For example, in cases of limited (scarce) uplink resources, the base station can prioritize allocating uplink resources to higher-priority data. The specific priority is related to the real-time and latency requirements of the data; for instance, data with stronger real-time requirements and lower latency requirements have higher priority. Thus, for higher-priority data, the base station can prioritize allocating uplink resources or allocate sufficient uplink resources. In cases of limited uplink resources, the base station can prioritize allocating uplink resources to service data requiring low latency, further improving communication reliability.

[0187] In one possible implementation, the first information is also used to indicate the priority of the data. Specifically, the implementation of the first information indicating the priority of the data may include, but is not limited to, the following: the first information may include a field C, which represents the priority of the data. For example, field C may be a first preset value indicating high priority, a second preset value indicating medium priority, or a third preset value indicating low priority. If the data in the terminal device's cache has a high priority, then field C in the first information is the first preset value. Accordingly, after receiving the first information from the terminal device, the base station can determine that the data in the cache has a high priority based on field C in the first information. Furthermore, when allocating uplink resources to the terminal device, the base station may consider prioritizing the response to the terminal device's scheduling request.

[0188] It should be noted that the classification of the data priority levels into high, medium, and low priorities is merely an illustrative description and does not impose any specific limitation on the number of priorities. In the actual application of this application embodiment, the number of priorities can be predefined by the protocol, defined, or pre-configured to the terminal device by the base station through signaling (such as RRC signaling), or determined and configured to the terminal device by the base station based on the terminal device's capabilities, or pre-configured. This application embodiment does not impose any limitations on this. Furthermore, the naming of the priority levels as high, medium, and low priorities is merely an illustrative description and does not limit the priority names. In the actual application of this application embodiment, these priorities can be represented by other names, such as priority 0, priority 1, and priority 2, or first level, second level, and third level, etc., and can be replaced and adjusted as needed.

[0189] In addition, the terminal device may include one or more LCGs. Each LCG to be transmitted corresponds to a priority. The priority of the LCG can indicate the importance or urgency of the data in that LCG. The terminal device and the base station reach a consensus on the priority of each LCG. Therefore, the first information can indicate the priority of the data by indicating the identifier of the logical channel group.

[0190] For example, the first information may include a field D, which represents the LCGID. Assuming that the buffer corresponding to the logical channel group of the terminal device's LCGID1 contains data to be transmitted, then field D can be a fourth preset value (the fourth preset value can be, for example, 1), representing LCG ID1. Accordingly, after receiving the first information, the base station can determine, based on the fourth preset value of field D in the first information, that the buffer corresponding to the LCG of the terminal device's LCG ID1 contains data to be transmitted, and can allocate uplink resources to the terminal device based on the priority of the logical channel group corresponding to LCG ID1 and the first data volume (or the first data volume range).

[0191] According to the above scheme, while indicating the first data volume or a first data volume range to the base station, the terminal device can also indicate the priority of the data to be transmitted in the buffer. In this way, when allocating uplink resources to the terminal device, the base station can simultaneously consider the priority and data volume of the data in the buffer, which helps the base station to allocate uplink resources more efficiently and improves the flexibility of uplink resource allocation.

[0192] In some scenarios, there may be data to be transmitted in the caches corresponding to multiple LCGs of a terminal device. In order to improve the allocation efficiency of uplink resources allocated by the base station to the terminal device, this application embodiment also proposes that the first information sent by the terminal device to the base station can be used to indicate the amount of data to be transmitted in the caches corresponding to multiple LCGs.

[0193] In one possible implementation, the first information includes at least one LCG ID and an indication of the amount of data to be transmitted in the cache corresponding to that LCG.

[0194] Specifically, the first information includes at least one field for indicating an LCG. This at least one field may include, for example, fields E and F. For instance, if field E is 0, it indicates that there is data to be transmitted in the buffer corresponding to the LCG ID0. The first information also includes field G, which indicates (either directly or indirectly, as will not be elaborated below) the amount of data to be transmitted in the buffer corresponding to LCG ID0. If field F is 1, it indicates that there is data to be transmitted in the buffer corresponding to the LCG ID1 of the terminal device. The first information also includes field H, which indicates the amount of data to be transmitted in the buffer corresponding to LCG ID1.

[0195] For example, assuming that the caches corresponding to LCG ID0 and LCG ID1 of the terminal device contain data to be transmitted, where the amount of data to be transmitted in the cache corresponding to LCG ID0 is 50 bytes and the amount of data to be transmitted in the cache corresponding to LCG ID1 is 60 bytes, then in the first information, field E is 0, field G indicates a data amount of 50 bytes, field F is 1, and field H indicates a data amount of 60 bytes. Accordingly, after receiving the first information from the terminal device, the base station can determine the amount of data to be transmitted in the cache corresponding to at least one LCG of the terminal device based on fields E, F, G, and H in the first information. For example, the base station determines that the amount of data to be transmitted in the cache corresponding to LCG ID0 of the terminal device is 50 bytes based on field E being 0 and field G being 50, and determines that the amount of data to be transmitted in the cache corresponding to LCG ID1 of the terminal device is 60 bytes based on field F being 1 and field H being 60.

[0196] In another possible implementation, the terminal device can report the amount of data to be transmitted in the buffers corresponding to all LCGs through the first information. Assuming the protocol predefines 8 LCGs, denoted as LCG ID0 to LCG ID7, the first information includes 8 fields (denoted as fields I0 to I7) indicating the amount of data to be transmitted in the buffers corresponding to each LCG of the terminal device. For example, assuming the amount of data to be transmitted in the buffer corresponding to LCG ID2 of the terminal device is 65 bytes, the amount of data to be transmitted in the buffer corresponding to LCG ID4 is 70 bytes, and there is no data to be transmitted in the buffers corresponding to the other LCGs of the terminal device, then field I2 in the first information is 65, field I4 is 70, and all other fields besides field I2 and field I4 are 0 (or can be empty). Accordingly, after receiving the first information from the terminal device, the base station can determine that the amount of data to be transmitted in the buffer corresponding to LCGID2 of the terminal device is 65 bytes and the amount of data to be transmitted in the buffer corresponding to LCGID4 is 70 bytes, based on the fact that I2 is 65 and I4 is 70 in the first information. The base station can also determine that there is no data to be transmitted in the buffer corresponding to other LCGs besides LCGID2 and LCGID4, based on the fact that other fields besides I2 and I4 are 0 (or empty).

[0197] According to the above scheme, the base station can allocate uplink resources to the terminal device based on the priority of at least one LCG and the amount of data to be transmitted in the buffer of the LCG, which helps to improve the efficiency of the base station in allocating uplink resources to the terminal device.

[0198] It should be noted that the above example of the terminal device indicating the identifier of at least one LCG and the amount of data to be transmitted in the buffer corresponding to at least one LCG in the terminal device is only an exemplary description for the purpose of understanding the embodiments of this application, and is not a specific limitation on the embodiments of this application. In practical applications, the indication information of at least one LCG in the first information can also be represented by other identifiers (or other preset values). Specifically, the indication information of each LCG can be predefined by the protocol, defined, or pre-configured by the base station to the terminal device through signaling (such as RRC signaling), or configured to the terminal device. The embodiments of this application do not limit this. In addition, the above description of the amount of data to be transmitted in the buffer corresponding to each LCG of the terminal device is an example of directly indicating the amount of data. However, the embodiments of this application are not limited to this. In practical applications, the terminal device can also indicate the index corresponding to the amount of data to be transmitted of each LCG, or other coarser-grained level information, so that the base station can determine an approximate value of the amount of data to be transmitted from each LCG.

[0199] The above describes the specific implementation of the first information (i.e., what information the first information may include), so that the base station can determine the amount of data (or an approximate value of the data amount) to be transmitted in the terminal device's buffer based on the first information. The following further describes how the terminal device sends the first information to the base station, and through which time-frequency resources the terminal device uses to send the first information to the base station. Specific implementation methods for the terminal device to send the first information to the base station may include, but are not limited to, the following implementation methods (I) and (II).

[0200] In one implementation method, the first information is carried on a first resource, which is a first physical uplink control channel (PUCCH) resource.

[0201] Specifically, the PUCCH resource can be configured by the base station for the terminal device via signaling. For example, the base station can send specific PUCCH resource configuration information to the terminal device via radio resource control (RRC) signaling. Correspondingly, after receiving the PUCCH resource configuration information from the base station, the terminal device can determine the PUCCH resource and send first information to the base station on that PUCCH resource. It should be understood that the base station configuring the PUCCH resource for the terminal device via RRC signaling is only an exemplary description for ease of understanding the embodiments of this application. For example, the base station can also allocate PUCCH resources to the terminal device when the terminal device initially accesses the network, or it can be PUCCH resources allocated to the terminal device when establishing a new RRC connection or re-establishing an RRC connection between the terminal device and the network. This can be determined according to the actual application, and the embodiments of this application do not limit this.

[0202] It should be understood that PUCCH resources can include various formats. For example, as shown in Table 3, PUCCH resources can include at least one format from format 0 to format 4. Format 0 and format 2 are short formats (occupying 1 or 2 time-domain symbols). Format 0 occupies 1 resource block in the frequency domain, and format 2 occupies a value from 1 to 16 resource blocks in the frequency domain. Format 1, format 3, and format 4 are long formats (occupying 4 to 14 time-domain symbols). Format 1 and format 4 occupy 1 resource block in the frequency domain, and format 3 occupies a value from 1 to 6, 8 to 10, 12, 15, or 16 resource blocks in the frequency domain. The format of the PUCCH resources configured by the base station for the terminal device can be configured by the base station based on the network status or the actual needs of the terminal device. This application embodiment does not limit this.

[0203] Table 3

[0204]

[0205] The first information can be carried on a PUCCH resource of any of the aforementioned PUCCH formats. This information can be predefined by the protocol, defined, or pre-configured by the base station to the terminal device via signaling (such as RRC signaling). For example, the first information can be predefined by the protocol and carried on a short-format PUCCH resource; exemplarily, this short-format PUCCH resource can be a format 0 or format 2 PUCCH resource. As another example, the first information can be predefined by the protocol and carried on a long-format PUCCH resource; exemplarily, this long-format PUCCH resource can be a format 1, format 3, or format 4 PUCCH resource. However, the embodiments of this application are not limited to these; the first information can be predefined by the protocol and carried on a PUCCH resource of any format. For ease of understanding, the following describes... Figure 7 and Figure 8 This section introduces both short-format PUCCH resources and long-format PUCCH resources.

[0206] For example, Figure 7 The first PUCCH resource shown occupies one symbol in the time domain and one resource block (RB) in the frequency domain, or can be understood as occupying 12 subcarriers in the frequency domain. In this case, the first information can be carried on multiple subcarriers within one time-domain symbol of the first PUCCH resource.

[0207] For example, Figure 8 The first PUCCH resource shown occupies 14 symbols in the time domain and one resource block (RB) in the frequency domain, or can be understood as occupying 12 subcarriers in the frequency domain. In this case, the first information can be carried on multiple subcarriers across one or more time-domain symbols in the first PUCCH resource. Furthermore, Figure 8 The long-format PUCCH resource shown also includes a PUCCH resource for carrying the demodulation reference signal (DMRS). The first information can be carried on other PUCCH resources besides the PUCCH resource carrying the DMRS, which will not be described in detail below.

[0208] The number of time-domain symbols occupied by the first PUCCH resource in the time domain is related to the length of the first information (or the amount of data in the first information). For example, a short-format PUCCH resource occupies fewer time-domain symbols in the time domain, and can carry a shorter length of first information. A long-format PUCCH resource occupies more time-domain symbols in the time domain, and can carry a longer (or more data) first information. During the process of the terminal device sending the first information to the base station, when the content of the indication information contained in the first information is determined, such as the first information containing indication information for indicating the first data amount or the first index, or the first information containing indication information for the first data amount or the first index, as well as indication information for data priority (specifically, it is predefined by the protocol, defined, or it can be pre-configured to the terminal device by the base station through signaling (such as RRC signaling), or configured to the terminal device; this application embodiment does not limit this), the factors affecting the length of the first information include the encoding method of the first information.

[0209] For example, when the terminal device uses shift register encoding to encode the original data of the first information, this encoding method enhances the anti-interference capability of the system by utilizing the characteristics of the sequence itself, without introducing a lot of redundant information. Therefore, compared with the channel coding method, the length of the first information obtained by the terminal device using shift register encoding to encode the original data of the first information is shorter. This shorter first information can be carried on both long-format PUCCH resources and short-format PUCCH resources.

[0210] For example, when the terminal device uses channel coding to encode the original data of the first information, this coding method enhances the reliability of data transmission by introducing redundant information. Compared with the coding method using shift registers, the first information obtained by the terminal device using channel coding to encode the original data of the first information is longer. This longer first information is more suitable for carrying on long-format PUCCH resources.

[0211] The following uses the first PUCCH resource as an example. Figure 7 The short format PUCCH resource shown (such as format 0 or format 2), or the first PUCCH resource as shown, is... Figure 8 Taking the long format PUCCH resource shown (such as format 1, format 3 or format 4) as an example, this article introduces how the terminal device can use the first PUCCH resource of different formats to send the first information, that is, in what form the first information is carried on the first PUCCH resource of different formats.

[0212] (1) In the first PUCCH resource, if Figure 7In the case of the short-format PUCCH resource shown, the first information is carried in a first sequence on multiple subcarriers in a time-domain symbol of the first PUCCH resource. The first sequence is obtained through encoding, which includes shift register-based encoding.

[0213] In other words, the first sequence is obtained by encoding the original data of the first information using a shift register. For example, a terminal device can generate an m-sequence based on the original data of the first information using a linear feedback shift register, and then obtain the first sequence after constellation modulation. The first sequence is a complex sequence composed of multiple modulation symbols, and this first sequence can be carried in a format such as... Figure 7 The short format PUCCH resource shown is used. However, this application embodiment does not limit the terminal device to using all resources of the first PUCCH resource to send the first information; that is, the first information can be carried on some or all of the resources of the first PUCCH resource. For example, for Figure 7 The first PUCCH resource shown (occupies 1 symbol in the time domain) includes 12 subcarriers per RB, each of which can carry one modulation symbol. If the first sequence includes 12 modulation symbols, then the first sequence occupies all the subcarriers of the first PUCCH resource, and each of the 12 subcarriers carries one modulation symbol from the first sequence. If the first sequence contains less than 12 modulation symbols, then the first sequence occupies a portion of the subcarriers in the first PUCCH resource. For example, if the first sequence includes 8 modulation symbols, then the first sequence occupies 8 subcarriers in the first PUCCH resource. When the first sequence occupies a portion of the subcarriers in the first PUCCH resource, the position of these subcarriers in the first PUCCH resource can be predefined by the protocol, defined, preconfigured by the network device through signaling, configured, or determined by predefined rules. This application embodiment does not limit this.

[0214] However, the embodiments of this application are not limited to this. In the case that the first PUCCH resource is a short format PUCCH resource, if the short format PUCCH resource can carry the first sequence obtained by the terminal device using the channel coding method, the terminal device can also use the channel coding method to process the original data of the first information to obtain the first sequence, and the first information is carried on the short format PUCCH resource in the form of the first sequence.

[0215] It should be understood that when the first PUCCH resource is in short format, it may also occupy two symbols in the time domain. Therefore, in the case where the first PUCCH resource occupies two symbols in the time domain, the aforementioned implementation of transmitting the first information on the first PUCCH resource can be replaced by: the first information being carried in a first sequence on multiple subcarriers across two time domain symbols in the first PUCCH resource. Furthermore, when the first PUCCH resource occupies two time domain symbols, the implementation of carrying the first information on the first PUCCH resource is similar to that when it occupies one time domain symbol; please refer to the relevant description above for details, which will not be repeated here.

[0216] According to the above scheme, the terminal device can send the first information to the base station using the short-format PUCCH resource pre-configured by the base station (i.e., the first PUCCH resource is a short-format PUCCH resource). Through the first information, the terminal device can simultaneously request uplink authorization from the base station and report the amount of buffered data. The base station can obtain the amount of data to be transmitted in the terminal device's buffer earlier, thereby reducing latency during the uplink authorization (or uplink scheduling) process and improving communication reliability. Furthermore, sending the first information in the form of a first sequence can also improve the anti-interference capability of the first information and enhance communication reliability.

[0217] (2) In the first PUCCH resource, if Figure 8 In the case of the long-format PUCCH resource shown, the first information is carried in a first sequence on multiple subcarriers across one or more time-domain symbols in the first PUCCH resource. The first sequence is obtained through encoding processing, which may include shift register-based encoding or channel coding-based encoding.

[0218] In other words, the first sequence is obtained by encoding the original data of the first information through shift register-based encoding or channel coding-based encoding, and can be carried in, for example... Figure 8 The long-format PUCCH resource shown is used. Similar to the short-format PUCCH resource described above, this application embodiment does not limit the terminal device to using all resources of the long-format PUCCH resource to send the first information.

[0219] For example, when the terminal device uses a shift register encoding method to encode the original data of the first information to obtain the first sequence, the length of the first sequence may be relatively short. It can be carried on multiple subcarriers of a time-domain symbol in a long-format PUCCH resource. The specific time-domain symbol on which the first sequence is carried can be predefined by the protocol, defined, or pre-configured to the terminal device by the base station through signaling (such as RRC signaling), or determined by the terminal device. This application embodiment does not impose any restrictions on this. Furthermore, the implementation method of carrying the first sequence on multiple subcarriers of a time-domain symbol in a long-format PUCCH resource is similar to the implementation method of carrying the first sequence on multiple subcarriers of a time-domain symbol in a short-format PUCCH resource described above. Please refer to the above description for details, which will not be repeated here.

[0220] For example, the first sequence is obtained by channel coding of the original data of the first information. Exemplarily, in addition to channel coding, the original data of the first information also undergoes at least one of the following processes: cyclic redundancy check (CRC), rate matching, scrambling, and modulation. The first sequence is a complex sequence composed of multiple modulation symbols, and this first sequence can be carried in, for example... Figure 8 The first information is transmitted on the long-format PUCCH resource shown. However, this application embodiment does not limit the terminal device to using all resources of the first PUCCH resource to transmit the first information. That is, the first information can be carried on part or all of the resources of the first PUCCH resource. Specifically, the position of the time-domain symbol carrying the first sequence and / or the position of the subcarrier in the long-format PUCCH resource can be predefined by the protocol, defined, or pre-configured by the base station to the terminal device through signaling (such as RRC signaling), or configured to the terminal device, or determined by the terminal device. This application embodiment does not impose any restrictions on this.

[0221] Furthermore, when using a channel-based coding method to encode the first information, this application embodiment does not limit which channel coding method is used. For example, the channel coding method can be one of turbo codes, polar codes, LDPC codes, convolutional codes, etc., and this application embodiment also does not limit the coding rate or modulation method used in the channel-based coding processing. The specific channel coding method used by the terminal device can be predefined by the protocol, defined, or pre-configured to the terminal device by the base station through signaling (such as RRC signaling), or configured to the terminal device, or determined by the base station based on the capabilities of the terminal device and configured to the terminal device through signaling, so that the base station and the terminal device can reach a consensus on the coding method adopted.

[0222] According to the above scheme, the terminal device sends first information to the base station on a long-format PUCCH resource (the first PUCCH resource is a long-format PUCCH resource). In this way, the terminal device can simultaneously request uplink authorization from the base station and report the amount of buffered data through the first information. The base station can obtain the amount of data to be transmitted in the terminal device's buffer earlier, thereby reducing the latency during the uplink authorization (or uplink scheduling) process. Furthermore, the first sequence carried on this long-format PUCCH resource can be obtained based on shift register encoding, which improves the anti-interference capability of the first information and also helps reduce the resource overhead of transmitting the first information, saving PUCCH resources. Alternatively, the first sequence carried on this long-format PUCCH resource can be obtained based on channel coding, which has higher robustness and helps improve communication reliability.

[0223] Optionally, the first sequence is obtained by encoding the original data of the first information. The encoding process may also include scrambling, i.e., adding scrambling codes.

[0224] In one example, the terminal device can perform this scrambling process based on its Radio Network Temporary Identifier (RNTI). The RNTI can be used to distinguish different terminal devices within the wireless network. The terminal device sends first information scrambled based on its RNTI to the base station. Correspondingly, after receiving this first information, the base station can use the RNTI to descramble and identify the terminal device that sent it. Furthermore, the base station can determine which terminal device to allocate uplink resources to, thereby improving the reliability of data transmission.

[0225] For example, the first sequence is obtained based on channel coding processing. After the terminal device performs channel coding processing on the original data of the first information, it adds a CRC. The terminal device can scramble the CRC based on the cell-RNTI of the terminal device. The first sequence obtained by the terminal device includes the CRC scrambled based on the C-RNTI. However, this application is not limited to this.

[0226] For example, the first sequence can also be obtained through shift register-based encoding. The terminal device can use a shift register to encode the first sequence based on part or all of the C-RNTI (specifically, this can be achieved through protocol pre-definition or signaling interaction to reach a consensus between the terminal device and the base station) and the original data of the first information. For instance, the terminal device can scramble the original data of the first information based on part or all of the C-RNTI and then encode it using a shift register. However, this application is not limited to this; the C-RNTI and the original data of the first information can be used to initialize a sequence generator (which includes a shift register) to obtain the first sequence.

[0227] The above describes how the terminal device uses short-format or long-format PUCCH resources to send the first information to the base station. The specific PUCCH resource format used by the terminal device to send the first information to the base station can be predefined by the protocol, defined by the protocol, or pre-configured by the base station to the terminal device via signaling (such as RRC signaling). Alternatively, the protocol can pre-define multiple formats of PUCCH resources carrying the first information, and the terminal device can select one format of PUCCH resources to send the first information to the base station. This application embodiment does not impose any restrictions on this.

[0228] When a base station configures PUCCH resources in multiple formats for a terminal device, due to the uncertainty of the PUCCH resource format, in order for the base station to correctly parse the first information from the terminal device, the first information can also indicate the format of the first PUCCH resource (such as any one of format0 to format4). Correspondingly, after receiving the first information from the terminal device, the base station can parse the first information corresponding to the number of symbols on the PUCCH resource according to its format. For example, the first information can indicate that the format of the first PUCCH resource is format 0, which is a short format PUCCH resource, then the base station can parse the data corresponding to the number of symbols in the short format PUCCH resource (i.e., information within 1 or 2 symbols). As another example, the first information can indicate that the format of the first PUCCH resource is format 3, which is a long format PUCCH resource, then the base station can parse the data corresponding to the number of symbols in the long format PUCCH resource (i.e., information within 4 to 14 symbols).

[0229] Specifically, the format of the first information indicating the first PUCCH resource may include, but is not limited to, the following embodiments 1-3.

[0230] In Implementation Method 1, the first information may further include a field J, which represents the format of the first PUCCH resource. For example, if field J is a fifth preset value, it indicates that the format of the first PUCCH resource is format 0; if field J is a sixth preset value, it indicates that the format of the first PUCCH resource is format 1. Similarly, formats 2-4 can also be represented by other preset values; for simplicity, they are not listed here. If the terminal device sends the first information to the base station using a PUCCH resource with format 0, then field J in the first information is the fifth preset value. Accordingly, after receiving the first information from the terminal device, the base station can determine that the first information is carried on a PUCCH resource with format 0 based on the fifth preset value of field J in the first information, and then the base station can parse the data on the corresponding symbol number.

[0231] In implementation method 2, the first information may further include a field K, which indicates the format type of the first PUCCH resource (e.g., long format or short format). If field K is a seventh preset value, it indicates that the format type of the first PUCCH resource is short format; if field K is an eighth preset value, it indicates that the format type of the first PUCCH resource is long format. If the terminal device sends the first information to the base station using short format PUCCH resources, then field K in the first information is the seventh preset value. Correspondingly, after receiving the first information from the terminal device, the base station can determine that the first information is carried on short format PUCCH resources based on field K being the seventh preset value, and the base station can then parse the data on the corresponding symbol number.

[0232] In implementation method 3, the base station determines the format type of the first PUCCH resource based on the time-frequency location (such as symbol, RB position) of the received first information.

[0233] Specifically, when configuring PUCCH resources for a terminal device, the base station can maintain a correspondence between the terminal device and the PUCCH resources (hereinafter referred to as the second correspondence). Optionally, the second correspondence may include the terminal device identifier, resource index, PUCCH resource format type (such as long / short format, and / or format 0 / 1 / 2 / 3 / 4), and time-frequency position (including at least one of start symbol, symbol number, start RB, or number of RBs). After receiving the first information from the terminal device, the base station can determine the PUCCH resource format type based on the time-frequency position of the first signal in the second correspondence, and parse the first information corresponding to the number of symbols on the PUCCH resource according to the format type.

[0234] According to at least one of the above embodiments 1-3, the base station can determine the number of symbols occupied in the time domain by the first PUCCH resource carrying the first information, and can parse the first information on the corresponding symbols according to the number of symbols. This helps to improve the base station's ability to successfully receive the first information, enabling the base station to allocate uplink resources to the terminal device in a timely manner and improve communication reliability. The various embodiments of the first information indicating the format of the first PUCCH resource shown above are merely exemplary descriptions for the purpose of understanding the embodiments of this application, and are not specific limitations on the embodiments of this application. In practical applications, the base station can also determine the format type of the first PUCCH resource based on other embodiments, and the embodiments of this application do not limit this.

[0235] In implementation method (ii), the first information is carried on a first resource, which is a resource pre-configured by the base station for the terminal device to send the first information.

[0236] Optionally, the first resource may belong to the PUCCH resource pre-configured by the base station for the terminal device, or it may also belong to the PUSCH resource pre-configured by the base station for the terminal device. Specifically, the resource may be pre-defined by the protocol, defined, or pre-configured by the base station to the terminal device via signaling (such as RRC signaling), or configured to the terminal device. Alternatively, some of the first resource may belong to the PUCCH resource, and another part to the PUSCH resource; this application does not limit this. In practical applications, the base station can choose to configure PUCCH and / or PUSCH resources for the terminal device according to actual needs. For ease of understanding, the following explanation uses the example of the first resource belonging to the PUSCH resource. However, it should be understood that the embodiments of this application are not limited to this; the base station may also choose to configure the first resource for the terminal device using PUCCH resources. When the base station configures PUCCH resources for the terminal device, the PUSCH resource mentioned below can also be replaced with PUCCH resources. For simplicity, this will not be elaborated further below.

[0237] An implementation of a base station pre-configuring a first resource for a terminal device may include: the base station sending third information to the terminal device, the third information configuring one or more candidate resources for the terminal device to send the first information, the one or more candidate resources including the first resource.

[0238] The base station can configure each candidate resource for the terminal device by configuring one or more of the following for each candidate resource in one or more candidate resources through third information: time domain resources, frequency domain resources, resource mapping style or resource identifier.

[0239] The base station can configure the time-domain resources of candidate resources for the terminal device using third information. This time-domain resource can be a time-domain unit occupied by the candidate resource, and the time-domain unit can be an OFDM symbol or an OFDM symbol group, etc. The time-domain resource can also include the period of the candidate resource; for example, the third information can specifically indicate the start position and duration of the period. The periods of one or more candidate resources configured in the third information can be the same or different, and this embodiment does not limit this. The base station can configure the frequency-domain resources of candidate resources for the terminal device using third information. This frequency-domain resource can be a frequency-domain unit occupied by the candidate resource, and the frequency-domain unit can be a subcarrier or a subcarrier group.

[0240] It should be noted that the size of the time-domain resources occupied by multiple time-frequency units corresponding to a candidate resource in the time domain, or the size of the frequency-domain resources occupied in the frequency domain, can be predefined by the protocol, defined, or pre-configured by the base station to the terminal device through signaling (such as RRC signaling), or determined by the base station based on the capabilities of the terminal device. For example, each time-frequency unit may occupy 1 to 2 symbols in the time domain, or more symbols; each time-frequency unit may occupy one resource block in the frequency domain, or more resource blocks. This application embodiment does not impose any restrictions on this. In addition, the size of the time-domain resources occupied in the time domain, or the size of the frequency-domain resources occupied in the frequency domain, may be the same or different for different candidate resources. This application embodiment does not impose any restrictions on this.

[0241] In one implementation, the third information can configure a resource pool for candidate resources, which specifically includes one or more candidate resources.

[0242] For example, the third information can configure the time-frequency position of the resource pool within a time slot (or subframe, or frame), and the third information further indicates the time-frequency position of each candidate resource within the resource pool. The third information can also configure the period of the resource pool, such as the period start position and period duration, at which the resource pool appears periodically.

[0243] A candidate resource in the resource pool can be a single time-frequency unit, or it can be a candidate resource comprising multiple time-frequency units distributed throughout the resource pool. For example, the first resource may comprise multiple time-frequency units, with the first information specifically carried on one of these time-frequency units. In this way, multiple transmission opportunities can be provided for the first information within a single resource pool. When a terminal device has a data transmission requirement, it can select the next time-frequency unit of the first resource in the resource pool to send the first information to the base station.

[0244] For example, a candidate resource may include multiple time-frequency units distributed in the time domain within a resource pool. Third information can configure the resource mapping style of the candidate resource within the resource pool, indicating the multiple time-frequency units contained in the candidate resource within the resource pool. Figure 9 This diagram illustrates multiple candidate resources in a resource pool for embodiments of this application. For example... Figure 9 As shown, a candidate resource in this resource pool can include multiple time-frequency units that are distributed in the time domain.

[0245] It should also be understood that Figure 9 The resource mapping patterns of multiple candidate resources shown are merely an example for ease of understanding. A resource mapping pattern can be understood as a rule for mapping candidate resources in the time or frequency domain (or as the distribution of candidate resources in the time or frequency domain). In practical applications, the resource mapping pattern of each candidate resource can be predefined by the protocol, defined, or pre-configured by the base station to the terminal device via signaling (such as RRC signaling). For example, the corresponding multiple time-frequency units can also adopt other distribution methods. For instance, the multiple time-frequency units corresponding to the candidate resources can be uniformly distributed (equally spaced) or non-uniformly distributed (non-equally spaced) in the time domain. The multiple time-frequency units can be identical in the frequency domain, or they can be uniformly distributed or non-uniformly distributed. This application embodiment does not impose any limitations on this.

[0246] In a possible implementation, the resource mapping pattern of each candidate resource can be determined by the time-domain offset (e.g., the interval between the starting positions of two adjacent time-frequency units in the time domain direction) and the frequency-domain offset (e.g., the interval between the starting positions of two adjacent time-frequency units in the frequency domain direction) of multiple time-frequency units respectively. The third information can indicate that, given the time-domain and frequency-domain resources of the first (earliest in the time domain direction) time-frequency unit among the multiple time-frequency units corresponding to each candidate resource are determined, the terminal device can determine the time-domain position of the candidate resource in the time domain based on the time-domain resources and time-domain offset of the first time-frequency unit, and the terminal device can determine the frequency-domain position of the candidate resource in the frequency domain based on the frequency-domain resources and frequency-domain offset of the first time-frequency unit. For example, as... Figure 9 As shown, when the time-frequency position of the first time-frequency unit corresponding to candidate resource 1 is determined, the terminal device can determine the resource position of each time-frequency unit in the time domain and frequency domain based on the time domain offset and frequency domain offset, respectively.

[0247] For example, the third information can configure the time-domain and frequency-domain resources of the first (earliest in the time-domain direction) time-frequency unit among the multiple time-frequency units included in the candidate resource. For instance, the third information may include indication information for the time-domain resources and indication information for the frequency-domain resources of the first time-frequency unit. Accordingly, after receiving the third information from the base station, the terminal device can determine the time-frequency position of the first time-frequency unit among the multiple time-frequency units corresponding to the candidate resource based on the time-domain and frequency-domain resources included in the third information.

[0248] Optionally, the third information may further include indication information for indicating the resource mapping pattern of the candidate resources. For example, the third information may include indication information for indicating the time-domain offset and frequency-domain offset of the candidate resources. Accordingly, after receiving the third information from the base station, the terminal device can determine the time-frequency position of each time-frequency unit in the candidate resources based on the time-domain offset and frequency-domain offset included in the third information. Optionally, when the multiple time-frequency units contained in the candidate resources are uniformly distributed in the time or frequency domain, the base station can indicate a time-domain offset or a frequency-domain offset to the terminal device through the third information. Or, when the multiple time-frequency units contained in the candidate resources are non-uniformly distributed in the time or frequency domain, the base station can indicate multiple time-domain offsets or multiple frequency-domain offsets to the terminal device through the third information.

[0249] It should be noted that the above-described implementation method of configuring candidate resources for terminal devices by the base station using the time-domain and frequency-domain resources of the first time-frequency unit among the multiple time-frequency units included in the candidate resources, as well as the resource mapping style, is only an exemplary description for understanding the embodiments of this application, and is not a specific limitation on the embodiments of this application. In practical applications, the base station can also configure candidate resources for terminal devices through other implementation methods so that the base station and the terminal device can reach a consensus on the time-frequency position of the candidate resources. The embodiments of this application do not limit this.

[0250] In one embodiment, when the base station configures a candidate resource for sending first information to the terminal device via third information, after the terminal device has data to be transmitted in its cache, the candidate resource becomes the first resource carrying the first information, and the terminal device can use the candidate resource to send the first information to the base station. Alternatively, when the third information is configured as multiple candidate resources for sending first information, the multiple candidate resources include the first resource for carrying the first information. After the terminal device has data to be transmitted in its cache, the terminal device can select the first resource from the multiple candidate resources to send the first information to the base station. For example, the first resource is the first candidate resource that arrives after the terminal device generates the first information. In another embodiment, when the base station configures multiple candidate resources for sending first information to the terminal device via third information, the base station can also indicate the resource identifier corresponding to each candidate resource to the terminal device, such as... Figure 9 As shown, the resource identifier corresponding to candidate resource 1 can be, for example, 1, and the resource identifier corresponding to candidate resource 2 can be, for example, 2. In the specific implementation, the third information may also include indication information for indicating the resource identifier. Accordingly, after receiving the third information from the base station, the terminal device can not only determine the distribution of candidate resources in the time domain or frequency domain direction based on time domain resources, frequency domain resources, and resource mapping patterns, but also determine the resource identifier of the candidate resources according to the indication information for indicating the resource identifier.

[0251] Furthermore, when the base station configures multiple candidate resources for the terminal device, the embodiments of this application do not limit the distribution of the multiple candidate resources in the time domain or frequency domain. For example, the embodiments of this application do not limit the distribution of the multiple candidate resources in the time domain as follows: Figure 9 The cases where the time domain locations shown are different can also be represented as follows: Figure 10 As shown, the time-domain locations of the multiple candidate resources may be the same. The specific distribution of the multiple candidate resources in the time or frequency domain can be predefined by the protocol, defined, or pre-configured by the base station to the terminal device through signaling (such as RRC signaling). This application embodiment does not limit this.

[0252] Optionally, the third information may specifically be Radio Resource Control (RRC) configuration information or RRC reconfiguration information. Specifically, the base station may configure one or more candidate resources for the terminal device using RRC configuration information when the terminal device initially accesses the network, or the base station may configure one or more candidate resources for the terminal device using RRC reconfiguration information during cell handover. The choice of which configuration information to use depends on the actual situation, and this application embodiment does not impose any restrictions on this.

[0253] Optionally, after the base station configures one or more candidate resources for the terminal device, the specific candidate resource used by the terminal device to send the first information to the base station can be configured / instructed by the base station for the terminal device through signaling, or it can be determined by the terminal device based on predefined rules (the predefined rules can be predefined by the protocol, defined, or pre-configured by the base station to the terminal device through signaling (such as RRC signaling), as detailed below.

[0254] In implementation method 1, the base station can send fourth information to the terminal device, which indicates a first resource among a plurality of candidate resources. The first resource is the resource to which the terminal device sends the first information.

[0255] The fourth information sent by the base station can indicate the resource identifier of the first resource among the candidate resources. For example, the fourth information may include a field L, which represents the identifier of the first resource. If field L is a ninth preset value, it indicates that the resource identifier of the first resource is 1 (i.e., the first resource is candidate resource 1). If field L is a tenth preset value, it indicates that the resource identifier of the first resource is 2 (i.e., the first resource is candidate resource 2). Assuming the base station instructs the terminal device to send the first information using candidate resource 1, then the field L in the fourth information is the ninth preset value. Accordingly, after receiving the fourth information from the base station, the terminal device determines that the first resource is candidate resource 1 based on the ninth preset value of field L in the fourth information, and sends the first information to the base station using candidate resource 1. Optionally, the fourth information can be DCI, RRC configuration information, or RRC reconfiguration information. The specific information used by the base station to indicate the first resource to the terminal device can be predefined by the protocol, defined, or pre-configured by the base station to the terminal device via signaling (such as RRC signaling). Alternatively, the protocol can also have multiple types of fourth information. In practical applications, the base station can choose one of DCI, RRC configuration information, or RRC reconfiguration information to indicate the first resource to the terminal device.

[0256] The base station can configure multiple candidate resources using third information and notify the terminal device using fourth information that the first resource among the candidate resources is the resource from which the terminal device sends the first information. Upon receiving the fourth information, the terminal device can send the first information to the base station using the first resource when it has a data transmission requirement. This can be understood as the base station configuring multiple candidate resources using third information and activating the first resource for carrying the first information for the terminal device using the fourth information. The base station can adjust the resource from which the terminal device sends the first information based on radio resource utilization. For example, the base station can send an indication message to the terminal device indicating the second resource among the candidate resources. Upon receiving this indication message, the terminal device determines that the resource for carrying the first information has changed from the first resource to the second resource. Alternatively, this can be understood as the base station activating both the first and second resources using this indication message.

[0257] In implementation method 2, the terminal device selects a first resource from multiple candidate resources based on predefined rules and sends the first information to the base station.

[0258] Predefined rules could include, for example, that when a terminal device has a data transmission requirement, the terminal device prioritizes selecting the earliest available candidate resource to send the first information to the base station. Figure 9 As shown, the earliest candidate resource that arrives after the terminal device has a data transmission requirement is candidate resource 2. Then the terminal device can use candidate resource 2 to send the first information to the base station.

[0259] Alternatively, a predefined rule could be used: the terminal device determines the first resource based on the amount of data to be transmitted in the cache. Specifically, assume that candidate resource 1, candidate resource 2, and candidate resource 3 correspond to ranges A, B, and C, respectively. If the first data volume belongs to one of ranges A, B, and C (or the first index belongs to one of ranges A, B, and C), the terminal device sends the first information to the base station using the candidate resource corresponding to the range to which the first data volume or the first index belongs.

[0260] It should be noted that the two predefined rules for determining the first resource shown above are merely exemplary descriptions for the purpose of understanding the embodiments of this application, and are not specific limitations on the embodiments of this application. In actual application, the terminal device can also determine the first resource based on other predefined rules, which may be predefined by the protocol, defined, or pre-configured to the terminal device by the base station through signaling (such as RRC signaling). The embodiments of this application do not limit this.

[0261] Alternatively, Embodiments 1 and 2 described above can be used in combination. When the base station indicates a first resource to the terminal device, the terminal device sends first information to the base station based on the indicated first resource. When the base station does not indicate a first resource to the terminal device, the terminal device can use the first resource determined in Embodiment 2 to send first information to the base station. Whether the terminal device or the base station uses Embodiment 1, Embodiment 2, or a combination of Embodiments 1 and 2, and determines the first resource, it can be predefined by the protocol, defined, or pre-configured by the base station to the terminal device via signaling (such as RRC signaling). This application embodiment does not impose any restrictions on this.

[0262] Optionally, each candidate resource in the one or more candidate resources configured by the base station for the terminal device can be configured individually, or the base station can also configure the one or more candidate resources in the form of a resource pool. That is, the resource pool configured by the base station for the terminal device includes the one or more candidate resources. This application does not limit this.

[0263] The above describes how the terminal device sends first information to the base station to request uplink authorization, and simultaneously indicates a first data volume or a first index to the base station to indicate the amount of data to be transmitted in the terminal device's buffer. Accordingly, after receiving the first information from the terminal device, the base station can execute S602.

[0264] S602, in response to uplink authorization, the base station determines the first uplink resource to be allocated to the terminal device based on the first data volume or the first index.

[0265] It should be understood that the terminal device shown above instructs the base station to indicate the first data volume or the first index through the first information, which is only to provide a reference for the base station to allocate resources. In this embodiment, the base station is not limited to allocating uplink resources to the terminal device that can carry the first data volume or the data corresponding to the first data volume range. In practical applications, the base station may allocate less data to the terminal device than the first data volume (or less than the minimum value in the first data volume range), or the base station may not allocate uplink resources to the terminal device. This embodiment does not impose any restrictions on this.

[0266] For example, if the first information indicates a first data volume, assuming field A in the first information is 56, it means the terminal device indicates to the base station that the amount of data to be transmitted in the buffer is 56 bytes. When the base station allocates uplink resources to the terminal device based on this first data volume, it does not necessarily allocate uplink resources that can carry 56 bytes of data. Instead, it may allocate more or less uplink resources than it can carry 56 bytes of data, or it may not allocate any uplink resources at all.

[0267] For example, if the first information indicates a first index, assuming the first data volume range of the data to be transmitted in the terminal device's cache is (30, 50), after the base station receives the first information from the terminal device and determines the first data volume range as (30, 50) based on the first index and the first correspondence of the first information, the base station may not necessarily allocate uplink resources to the terminal device that can carry more than 30 bytes of data and less than or equal to 50 bytes of data. Instead, it may allocate less uplink resources to the terminal device than it can carry 30 bytes of data. The specific amount of uplink resources allocated by the base station to the terminal device can be determined by the base station, and this application embodiment does not limit this.

[0268] After the base station determines the first uplink resource, the base station executes S603, that is, the base station sends second information to the terminal device, which indicates the first uplink resource. Optionally, the uplink resource is specifically a Physical Uplink Shared Channel (PUSCH) resource.

[0269] The base station can indicate the first uplink resource to the terminal device via DCI, meaning the second information can be DCI or the second information is included in DCI. The second information can include fields M and N. Field M can be a frequency domain resource allocation field, used to indicate the location and number of resource blocks (RBs) used by the PUSCH. Field N can be a time domain resource allocation field, used to indicate the time position of the PUSCH transmission. Field N can, for example, represent the time position of the PUSCH resource transmission through start time and duration. The specific implementation of the time domain or frequency domain resources represented by fields M or N for the PUSCH can be predefined by the protocol, defined, or pre-configured by the base station to the terminal device via signaling (such as RRC signaling), or configured by the base station to the terminal device. This application does not impose any limitations on this.

[0270] Accordingly, after receiving the second information from the base station, the terminal device can determine the first uplink resource (PUSCH resource) based on the second information. The terminal device can then execute S604, which involves sending first data on the first uplink resource, the data to be transmitted including the first data.

[0271] If the data to be transmitted in the terminal device's buffer is sufficient to be transmitted entirely on the first uplink resource, the terminal device transmits the first data to the base station on the first uplink resource. This first data is the data to be transmitted. In other words, the terminal device transmits all the data to be transmitted to the base station on the first uplink resource.

[0272] In some scenarios, such as when uplink resources are limited (or scarce), the first uplink resource allocated by the base station to the terminal device may not be sufficient to carry the data to be transmitted in the terminal device's cache. Or, because the data in the terminal device's cache is continuously accumulating, when the first uplink resource arrives, the amount of data to be transmitted in the terminal device's cache is greater than the amount of data reported by the terminal device to the base station. Therefore, the first uplink resource is insufficient to carry the data to be transmitted in the terminal device's cache. Based on this, this application embodiment also proposes that if the data to be transmitted in the terminal device's cache is insufficient to be transmitted on the first uplink resource, the terminal device can not only send the first data to the base station on the first uplink resource, but also indicate to the base station the amount of data remaining to be transmitted in the terminal device's cache on the first uplink resource.

[0273] For example, assuming that the amount of data to be transmitted in the buffer of the terminal device is 56 bytes, and the first uplink resource allocated by the base station to the terminal device can carry 20 bytes of data, when the terminal device sends the first data to the base station on the first uplink resource, it can also indicate to the base station on the first uplink resource the amount of data to be transmitted in the buffer of the terminal device (i.e., 56-20=36 bytes).

[0274] Similar to the implementation method where the terminal device indicates the amount of data to be transmitted in the terminal device's buffer to the base station on the first resource, the implementation method where the terminal device indicates the amount of the remaining data to be transmitted may include, but is not limited to, the following implementation method 1 and implementation method 2.

[0275] In implementation method 1, the terminal device sends the first data and the fifth information to the base station on the first uplink resource. The fifth information indicates the second data amount, which is greater than or equal to the amount of data remaining to be transmitted in the terminal device's buffer.

[0276] The implementation method of the terminal device indicating the second data volume through the fifth information is similar to the implementation method of the terminal device indicating the first data volume through the first information described above. For details, please refer to the relevant description above, which will not be repeated here.

[0277] In implementation method 2, the terminal device sends first data and a second index to the base station on the first uplink resource. The second index indicates a second data volume range, and the amount of data remaining to be transmitted in the terminal device's buffer belongs to the second data volume range.

[0278] Optionally, the terminal device can determine the second index based on the amount of remaining data to be transmitted and the first correspondence. For example, assuming the amount of remaining data to be transmitted in the terminal device's buffer is 36 bytes, and this 36 bytes belongs to the data range (m1, m2) in the first correspondence (as shown in Table 2), then the second index is index 2. That is, the terminal device can send the first data and the indication information of index 2 to the base station on the first uplink resource. Correspondingly, after receiving the first data and the indication information of index 2 from the terminal device, the base station can determine the data range (m1, m2) to which the amount of remaining data to be transmitted in the terminal device's buffer belongs based on the indication information of index 2. The base station can then allocate the next uplink resource to the terminal device based on the data range (m1, m2).

[0279] To improve the accuracy of the data range corresponding to the second index sent by the terminal device to the base station, and to improve the efficiency of the base station in allocating uplink resources to the terminal device, the second index can also be determined by the terminal device based on the remaining data to be transmitted and a second correspondence. The length of each data range in this second correspondence is less than or equal to the length of the data range in the first correspondence. The length of the data range can be understood as the difference between the maximum and minimum values ​​of each data range; for example, the range length corresponding to the data range (m1, m2) is m2-m1. The longer data range indicates higher accuracy of the data range corresponding to the index, allowing the base station to more accurately understand the amount of data to be transmitted in the terminal device's buffer, thus enabling more precise resource allocation.

[0280] When the length of each data range in the second correspondence is less than or equal to the length of the data range in the first correspondence, the precision of each data range in the second correspondence is greater than the precision of each data range in the first correspondence. The second correspondence may, for example, include the correspondence between each index and data range in Table 1.

[0281] The terminal device indicates the second index determined based on the second correspondence with this fine granularity to the base station, which helps the base station to understand the actual transmission needs of the terminal device more accurately (i.e. the amount of data that is actually left to be transmitted in the terminal device's buffer), enabling the base station to allocate uplink resources to the terminal device more accurately and improve the efficiency of the base station in allocating uplink resources.

[0282] The specific terminal device determines the second index based on the first correspondence or the second correspondence. The second index can be predefined by the protocol, defined, or pre-configured by the base station to the terminal device through signaling (such as RRC signaling), or configured to the terminal device, or determined by the terminal device based on the amount of data remaining to be transmitted. This application does not limit this.

[0283] It should be noted that the indices and corresponding data ranges in the second and first correspondences shown in Tables 1 and 2 are merely examples for the purpose of understanding this application. This application does not limit the length of the data range corresponding to all indices in the second correspondence to be less than that in the first correspondence. For example, the length of the data range corresponding to some indices in the first correspondence may be the same as (or partially overlap) the length of the data range corresponding to some indices in the second correspondence. Furthermore, the lengths of the data ranges in the first correspondence may be the same or different, and the lengths of the data ranges in the second correspondence may be the same or different. Specifically, the indices and their corresponding data ranges in the first and second correspondences may be predefined by the protocol, defined, or pre-configured by the base station to the terminal device through signaling (such as RRC signaling). This application does not impose any restrictions on this.

[0284] Figure 11 and Figure 12 This is a schematic diagram illustrating resource indication by the terminal device during the process of the terminal device sending an uplink authorization request to the base station, as provided in an embodiment of this application.

[0285] like Figure 11 As shown, when the first resource is a PUCCH resource, the terminal device can send first information to the base station through the PUCCH resource to request uplink authorization and indicate a first data volume or a first index. Correspondingly, after receiving the first information on the PUCCH resource, the base station can allocate a first uplink resource to the terminal device, which is specifically a PUSCH resource.

[0286] If the first uplink resource is sufficient to carry the data to be transmitted in the terminal device's buffer, the terminal device transmits the first data on the first uplink resource. If the first uplink resource is insufficient to carry the data to be transmitted in the terminal device's buffer, the terminal device can transmit the first data and a second index (or a second data volume) to the base station on the first uplink resource. Accordingly, after receiving the first data and the second index (or the second data volume) from the terminal device on the first uplink resource, the base station can also allocate a second uplink resource to the terminal device based on the second index (or the second data volume), which can also be a PUSCH resource. Furthermore, the terminal device can transmit the remaining data to be transmitted in its buffer to the base station on the second uplink resource.

[0287] like Figure 12As shown, the first resource is a resource pre-configured by the base station for the terminal device to send first information. The terminal device can send the first information to the base station on one or more candidate resources (or resource pools) pre-configured by the base station. These one or more candidate resources can be PUSCH resources or PUCCH resources. Correspondingly, after receiving the first information on the first resource, the base station can allocate a first uplink resource to the terminal device. Further, the terminal device can send first data on the first uplink resource, or send first data or a second index, etc., on the first uplink resource; see [link to relevant documentation] for details. Figure 11 The relevant descriptions are not repeated here.

[0288] If the second uplink resources allocated by the base station to the terminal device are still insufficient to carry the remaining data to be transmitted in the terminal device's buffer, the terminal device can also send a third index (or a third data volume) to the base station on the second uplink resources allocated by the base station, and so on, until the uplink resources allocated by the base station to the terminal device are sufficient to carry the remaining data to be transmitted in the terminal device's buffer.

[0289] It is understandable that after the base station allocates uplink resources to the terminal device, the terminal device can subsequently send an indication to the base station of the amount of data remaining to be transmitted in the buffer along with the data on the uplink resources allocated to it by the base station. Then, after the base station receives the first information from the terminal device on one of the candidate resources (or resource pools), the base station can release the remaining one or more candidate resources (or resource pools). This improves the utilization rate of uplink resources.

[0290] Optionally, the base station may send a sixth message to the terminal device, which includes indication information for releasing one or more remaining candidate resources (or resource pools). Accordingly, after receiving the sixth message from the base station, the terminal device can release the remaining one or more candidate resources (or resource pools) based on the sixth message.

[0291] Optionally, the sixth information may be a DCI, or the sixth information may be included in a DCI; this application does not impose any restrictions on this.

[0292] Figure 13 for Figure 6 This is a specific example of the embodiment shown. The communication method of this application embodiment will be further described below using the first resource as a pre-configured resource as an example. Figure 13 Zhongyu Figure 6 The same parts as those shown in the embodiments can be referred to in Figure 6 The descriptions in the illustrated embodiments will not be repeated here.

[0293] S1301, the base station sends configuration information to the terminal device for configuring one or more candidate resources (or resource pools).

[0294] The configuration information for one or more candidate resources (or resource pools) can be, for example, the third information mentioned above. For details, please refer to the relevant description of the third information above, which will not be repeated here.

[0295] Accordingly, after receiving the configuration information from the base station, the terminal device determines one or more candidate resources (or resource pools) that can carry the first information. Further, the terminal device can send the first information to the base station on one of the candidate resources (or resource pools).

[0296] S1302, the base station sends an indication message to the terminal device indicating the first resource among multiple candidate resources.

[0297] The indication information used to indicate the first resource among multiple candidate resources can be, for example, the fourth information mentioned above. For details, please refer to the relevant description of the fourth information above, which will not be repeated here.

[0298] Optionally, the configuration information for configuring one or more candidate resources (or resource pools) and the indication information for indicating the first resource among multiple candidate resources can be carried in the same information transmission, or they can be transmitted separately. This application does not impose any restrictions on this.

[0299] S1303, the terminal device sends the first information to the base station on the first resource.

[0300] Accordingly, after receiving the first information from the terminal device, the base station can execute S1304.

[0301] S1304, the base station determines the first uplink resource to be allocated to the terminal device based on the first information.

[0302] The base station can determine the first uplink resource allocated to the terminal device based on the first data volume or the first index indicated by the first information.

[0303] S1305, the base station sends second information to the terminal device, which indicates the first uplink resource.

[0304] The second information can be DCI or may be included in DCI. The second information can be carried on the physical downlink control channel (PDCCH).

[0305] Accordingly, after receiving the second information from the base station, the terminal device can determine the first uplink resource (PUSCH resource) based on the second information. The terminal device can then execute S1306, which involves either sending first data on the first uplink resource or sending first data and a second index on the first uplink resource.

[0306] It is understood that, in order to achieve the functions in the above embodiments, the network device and terminal device include hardware structures and / or software modules corresponding to perform each function. Those skilled in the art should readily recognize that, based on the units and method steps of the various examples described in conjunction with the embodiments disclosed in this application, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0307] Figure 14 and Figure 15 This is a schematic diagram illustrating the structure of possible communication devices provided in embodiments of this application. These communication devices can be used to implement the functions of network devices (such as base stations) or terminal devices in the above-described method embodiments, and therefore can also achieve the beneficial effects of the above-described method embodiments. In the embodiments of this application, the communication device can be as follows: Figure 1 The access network node shown can be as follows: Figure 1 One of the terminals 120a-120j shown can also be as follows: Figure 1 The access network node 110a or 110b shown can also be a unit / module / component (such as a chip, chip system, logic circuit or software) applied to terminal equipment or access network nodes.

[0308] The communication device 1400 includes a transceiver unit 1420, which can be used to receive or send information. The communication device 1400 may also include a processing unit 1410, which can be used to process instructions or data to achieve corresponding operations.

[0309] It should be understood that when the communication device 1400 is a chip configured in (or used in) a communication device, the transceiver unit 1420 in the communication device 1400 can be the input / output interface or circuit of the chip, and the processing unit 1410 in the communication device 1400 can be the processor in the chip.

[0310] Optionally, the communication device 1400 may further include a storage unit 1430, which can be used to store instructions or data. The processing unit 1410 can execute the instructions or data stored in the storage unit to enable the communication device to perform corresponding operations.

[0311] The communication device 1400 can be used to achieve the above. Figures 6 to 13 The method embodiments shown illustrate the functions of network devices (such as base stations) or terminal devices.

[0312] When the communication device 1400 is used to implement Figure 6 In the illustrated method embodiment, the terminal device functions as follows: Transceiver unit 1420 is configured to send first information, which requests uplink authorization and indicates: a first data volume, which is greater than or equal to the data volume to be transmitted in the terminal device's cache; or a first index, which indicates a range of the first data volume, and the data volume to be transmitted in the terminal device's cache belongs to this range. Transceiver unit 1420 is also configured to receive second information, which indicates a first uplink resource. Transceiver unit 1420 is further configured to send first data on the first uplink resource, the data to be transmitted including the first data.

[0313] For a more detailed description of the aforementioned transceiver unit 1420, please refer to [link / reference]. Figure 6 The relevant descriptions in the method embodiments shown.

[0314] When the communication device 1400 is used to implement Figure 6 In the illustrated method embodiment, the network device functions as follows: Transceiver unit 1420 is configured to receive first information, which requests uplink authorization and indicates: a first data volume, which is greater than or equal to the amount of data to be transmitted in the terminal device's cache; or a first index, which indicates a range of the first data volume, and the amount of data to be transmitted in the terminal device's cache belongs to this range. In response to the uplink authorization, processing unit 1410 is configured to determine a first uplink resource based on the first data volume. Transceiver unit 1420 is further configured to send second information, which indicates the first uplink resource. Transceiver unit 1420 is further configured to receive first data on the first uplink resource, the data to be transmitted including the first data.

[0315] For a more detailed description of the processing unit 1410 and the transceiver unit 1420, please refer to [reference needed]. Figure 6 The relevant descriptions in the method embodiments shown.

[0316] It is understood that the division of units in the above-described device is merely a logical functional division. Each function can correspond to a functional unit, or two or more functions can be integrated into one functional unit. In actual implementation, all or some units can be integrated into a single physical entity, or they can be distributed across different physical entities. Furthermore, the aforementioned functional units can be implemented in hardware, software, or a combination of both. Whether a function is executed 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 the embodiments of this application.

[0317] like Figure 15 As shown, the communication device 1500 includes a processor 1510 and an interface circuit 1520. The processor 1510 and the interface circuit 1520 are coupled to each other. It is understood that the interface circuit 1520 can be a transceiver or an input / output interface. Optionally, the communication device 1500 may also include a memory 1530 for storing instructions executed by the processor 1510, or storing input data required by the processor 1510 to execute instructions, or storing data generated after the processor 1510 executes instructions.

[0318] In one implementation, the memory 1530 may be integrated into the processor 1510 or independent of the processor 1510.

[0319] When the communication device 1500 is used to achieve Figure 6 or Figure 13 In the method shown, the processor 1510 is used to implement the functions of the processing unit 1410, and the interface circuit 1520 is used to implement the functions of the transceiver unit 1420.

[0320] When the aforementioned communication device is a chip applied to a terminal device, the terminal device chip can implement the functions of the terminal device in the above method embodiments. The terminal device chip receives information from other modules (such as a radio frequency module or antenna) in the terminal device, the information being sent to the terminal device by the network device; or, the terminal device chip sends information to other modules (such as a radio frequency module or antenna) in the terminal device, the information being sent to the network device by the terminal device.

[0321] When the aforementioned communication device is a module applied to a network device, the network device module can implement the functions of the base station in the above method embodiments. The network device module receives information from other modules (such as radio frequency modules or antennas) in the network device, which is information sent from the terminal device to the network device; or, the network device module sends information to other modules (such as radio frequency modules or antennas) in the network device, which is information sent from the network device to the terminal device. Here, the network device module can be the baseband chip of the network device, or it can be a DU or other modules. The DU here can be a DU under an open radio access network (O-RAN) architecture.

[0322] It is understood that the processor in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), microprocessors (MPUs), microcontroller units (MCUs), graphics processing units (GPUs), artificial intelligence processors (AI processors), neural network processing units (NPUs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor or any conventional processor.

[0323] The method steps in the embodiments of this application can be implemented in hardware or in software instructions executable by a processor. The software instructions can consist of corresponding software modules, which can be stored in random access memory, flash memory, read-only memory, programmable read-only memory, erasable programmable read-only memory, electrically erasable programmable read-only memory, registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. The storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in an access network device or a terminal device. The processor and storage medium can also exist as discrete components in the access network device or terminal device.

[0324] According to the method provided in the application embodiments, this application embodiment also provides a computer program product, the computer program product comprising: computer program code, which, when executed by one or more processors, causes a device including the processor to perform as described above. Figure 6 or Figure 13 The method shown.

[0325] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. This computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed, in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, network equipment, user equipment, or other programmable device.

[0326] According to the method provided in the embodiments of this application, the embodiments of this application also provide a computer-readable storage medium that stores the aforementioned computer program or instructions. When the computer program or instructions are executed by one or more processors, they cause a device including the processor to perform actions such as... Figure 6 or Figure 13 The method shown.

[0327] As described above, computer programs or instructions can be stored in or transferred from one computer-readable storage medium to another. For example, the computer programs or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium can be a volatile or non-volatile storage medium, or it can include both volatile and non-volatile types of storage media.

[0328] According to the method provided in the embodiments of this application, this application also provides a communication system, including one or more of the aforementioned terminals. The system may further include one or more of the aforementioned access network devices.

[0329] 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.

[0330] 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.

[0331] 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.

[0332] The unit described as a separate component may or may not be physically separate. The component shown as a unit may or may not be a physical unit; that is, it 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.

[0333] In the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments according to their inherent logical relationship.

[0334] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1. A communication method, characterized in that, The method is applied to a terminal device or a chip in a terminal device, and the method includes: Send a first message, which requests uplink authorization and indicates: A first data volume, wherein the first data volume is greater than or equal to the data volume to be transmitted in the cache of the terminal device; or... A first index indicates a first data volume range, and the amount of data to be transmitted in the cache of the terminal device belongs to the first data volume range; Receive a second message, which indicates a first uplink resource; First data is transmitted on the first uplink resource, and the data to be transmitted includes the first data.

2. The method according to claim 1, characterized in that, The first information is carried on a first resource, which is a resource pre-configured for sending the first information.

3. The method according to claim 1, characterized in that, The first information is carried on a first resource, which is a first physical uplink control channel resource.

4. The method according to any one of claims 1 to 3, characterized in that, The first index is located in the first correspondence, which is a correspondence between multiple data ranges and multiple indexes, and the multiple data ranges include the first data range.

5. The method according to any one of claims 1 to 4, characterized in that, The first information is carried in a first sequence on multiple subcarriers on one or more time-domain symbols in the first physical uplink control channel resource.

6. The method according to claim 5, characterized in that, The first sequence is obtained through encoding processing, which includes shift register-based encoding processing or channel coding-based encoding processing.

7. The method according to claim 6, characterized in that, The channel coding process includes scrambling based on the wireless network temporary identifier of the terminal device.

8. The method according to any one of claims 5 to 7, characterized in that, The first information also indicates the format of the first physical uplink control channel resource. The format of the first physical uplink control channel resource includes a first format, which is a short format; or, The format of the first physical uplink control channel resource includes a second format, which is a long format.

9. The method according to claim 2, characterized in that, Before sending the first information, the method further includes: Receive third information, the third information being configured to send one or more candidate resources of the first information, the one or more candidate resources including the first resource.

10. The method according to claim 9, characterized in that, The third information configures one or more of the following for each of the one or more candidate resources: Time-domain resources, frequency-domain resources, resource mapping styles, or resource identifiers.

11. The method according to claim 9 or 10, characterized in that, The method further includes: The terminal device receives a fourth message indicating the first resource among the plurality of candidate resources. The first resource is the resource from which the terminal device sent the first message.

12. The method according to claim 11, characterized in that, The second information is downlink control information; and / or, The third piece of information is radio resource control configuration information or radio resource control reconfiguration information; and / or, The fourth piece of information is downlink control information, radio resource control configuration information, or radio resource control reconfiguration information; and / or, The uplink resources are physical uplink shared channel resources.

13. The method according to any one of claims 1 to 12, characterized in that, Sending first data on the first uplink resource includes: If the data to be transmitted in the cache of the terminal device is insufficient to be fully transmitted on the first uplink resource, the first data and the second index are transmitted on the first uplink resource. The second index indicates a second data volume range, and the data volume of the remaining data to be transmitted in the cache of the terminal device belongs to the second data volume range. If the data to be transmitted in the cache of the terminal device is sufficient to be transmitted entirely on the first uplink resource, the first data is transmitted on the first uplink resource, and the data to be transmitted is the first data.

14. A communication method, characterized in that, The method is applied to a network device or a chip in a network device, and the method includes: Receive the first message, which requests uplink authorization and indicates: A first data volume, wherein the first data volume is greater than or equal to the amount of data to be transmitted in the terminal device's buffer; or... A first index indicates a first data volume range, and the amount of data to be transmitted in the cache of the terminal device belongs to the first data volume range. In response to the uplink authorization, a first uplink resource is determined based on the first data volume; Send a second message, the second message indicating the first uplink resource; Receive first data on the first uplink resource, wherein the data to be transmitted includes the first data.

15. The method according to claim 14, characterized in that, The first information is carried on a first resource, which is a resource pre-configured for sending the first information.

16. The method according to claim 14, characterized in that, The first information is carried on a first resource, which is a first physical uplink control channel resource.

17. The method according to any one of claims 14 to 16, characterized in that, The first index is located in the first correspondence, which is a correspondence between multiple data ranges and multiple indexes, and the multiple data ranges include the first data range.

18. The method according to any one of claims 14 to 17, characterized in that, The first information is carried in a first sequence on multiple subcarriers on one or more time-domain symbols in the first physical uplink control channel resource.

19. The method according to claim 18, characterized in that, The first sequence is obtained through encoding processing, which includes shift register-based encoding processing or channel coding-based encoding processing.

20. The method according to claim 19, characterized in that, The channel coding process includes scrambling based on the wireless network temporary identifier of the terminal device.

21. The method according to any one of claims 18 to 20, characterized in that, The first information also indicates the format of the first physical uplink control channel resource. The format of the first physical uplink control channel resource includes a first format, which is a short format; or, The format of the first physical uplink control channel resource includes a second format, which is a long format.

22. The method according to claim 15, characterized in that, Before receiving the first information, the method further includes: Send a third message, the third message being configured to send one or more candidate resources of the first message, the one or more candidate resources including the first resource.

23. The method according to claim 22, characterized in that, The third information configures one or more of the following for each of the one or more candidate resources: Time-domain resources, frequency-domain resources, resource mapping styles, or resource identifiers.

24. The method according to claim 22 or 23, characterized in that, The method further includes: Send a fourth message, the fourth message indicating the first resource among the plurality of candidate resources, the first resource being the resource from which the terminal device sent the first message.

25. The method according to claim 24, characterized in that, The second information is downlink control information; and / or, The third piece of information is radio resource control configuration information or radio resource control reconfiguration information; and / or, The fourth piece of information is downlink control information, radio resource control configuration information, or radio resource control reconfiguration information; and / or, The uplink resources are physical uplink shared channel resources.

26. The method according to any one of claims 14 to 25, characterized in that, Receiving the first data on the first uplink resource includes: The first data and the second index are received on the first uplink resource, the second index indicating a second data volume range, and the amount of data remaining to be transmitted in the cache of the terminal device belongs to the second data volume range.

27. A communication device, characterized in that, The device includes a processor coupled to a memory for storing a computer program, the processor executing the computer program stored in the memory to cause the communication device to perform the method as claimed in any one of claims 1 to 13; or to cause the communication device to perform the method as claimed in any one of claims 14 to 26.

28. A communication device, characterized in that, It includes a processor and a communication interface, the processor being configured to control the communication interface to implement the method as described in any one of claims 1 to 13; or to implement the method as described in any one of claims 14 to 26.

29. A computer-readable storage medium, characterized in that, The device stores instructions that, when executed on the communication device, cause the communication device to perform the method as described in any one of claims 1 to 13; or cause the communication device to perform the method as described in any one of claims 14 to 26.

30. A computer program product, characterized in that, The computer program product includes: a computer program that, when run, causes the method as described in any one of claims 1 to 13 to be executed or implemented; or causes the method as described in any one of claims 14 to 26 to be executed or implemented.

Images