A method and apparatus for transmitting scheduling requests

Abstract

A method and apparatus for transmitting a scheduling request, which are used in a communication system, such as V2X, LTE-V, V2V, vehicle-to-everything network, MTC, IoT, LTE-M, M2M, Internet of Things, etc. A terminal device determines that there is a first uplink channel within a first time domain range, combines the scheduling request with information included in the first uplink channel to obtain first information, and sends the first information to the network device; wherein, the first time domain range is related to the time domain position of a physical uplink control channel PUCCH including the scheduling request, and the first uplink channel is any one of the following: a PUCCH including HARQ feedback, a PUCCH including CSI report, or a PUSCH. This can reduce the number of terminal device uplink transmissions to save the power consumption of the terminal device.

Description

[0001] This application claims the priority of a Chinese patent application with the application number 202110070788.3, titled "A Transmission Method of SR", filed with the Chinese Patent Office on January 19, 2021, the entire content of which is incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technologies, and in particular, to a method and apparatus for transmitting a scheduling request. Background Art

[0003] Terminal devices supporting the 5th Generation new radio access technology (5G NR) generally need to support a relatively large bandwidth (such as 100 megahertz (MHz), etc.), a relatively large number of antennas (such as 4 reception (RX) antennas and 2 transmission (TX) antennas, etc.), and a relatively complex baseband processing process (such as polar codes, etc.), which may result in a relatively high power consumption of the terminal device. Currently, in order to reduce the power consumption of the terminal device, research on power consumption savings for terminal devices has become increasingly common. However, in current research, optimization has mainly been carried out for the downlink transmission of terminal devices, and no optimization has been carried out for the uplink transmission. Summary of the Invention

[0004] This application provides a method and apparatus for transmitting a scheduling request, aiming to propose how to optimize the transmission of the scheduling request to save the power consumption of the terminal device.

[0005] In a first aspect, this application provides a method for transmitting a scheduling request. The method may include: after determining that there is a first uplink channel within a first time domain range, the terminal device combines the scheduling request with the information included in the first uplink channel to obtain first information, and finally the terminal device sends the first information to the network device; where the first time domain range is related to the time domain position of a physical uplink control channel (PUCCH) including the scheduling request, and the first uplink channel may be any one of the following: a PUCCH including hybrid automatic repeat request (HARQ) feedback, a PUCCH including channel state information (CSI) report, or a physical uplink shared channel (PUSCH).

[0006] In the above method, by combining and transmitting the scheduling request with the information included in the first uplink channel, the number of uplink transmissions can be reduced, thereby reducing the power consumption of the terminal device.

[0007] In a possible design, the first time domain range is the first time window and / or the second time window; wherein, the start time of the first time window may be the time triggered when the physical (PHY) layer of the terminal device receives the scheduling request from the media access control (MAC) layer of the terminal device, and the end time may be the time domain position of the PUCCH including the scheduling request; or, the end time of the first time window may be the time domain position of the PUCCH including the scheduling request, and the time domain length is the first time domain length; the start time of the second time window may be the time domain position of the PUCCH including the scheduling request, and the time domain length is the second time domain length. This can accurately determine the first time domain range, and further accurately determine whether there is a first uplink channel within the first time domain range.

[0008] In a possible design, the existence of the first uplink channel within the first time domain range may specifically be: there is a first uplink channel after the time when the PHY layer of the terminal device receives the scheduling request from the MAC layer of the terminal device and before the time domain position of the PUCCH including the scheduling request. This can accurately determine the existence of the first uplink channel within the first time domain range.

[0009] In a possible design, the existence of the first uplink channel within the first time domain range may specifically be: there is a first uplink channel within the first time domain length before the time domain position of the PUCCH including the scheduling request. This can accurately determine the existence of the first uplink channel within the first time domain range.

[0010] In a possible design, the existence of the first uplink channel within the first time domain range may specifically be: there is a first uplink channel within the second time domain length after the time domain position of the PUCCH including the scheduling request, where the first uplink channel is a PUCCH including a CSI report. This can accurately determine the existence of the first uplink channel within the first time domain range.

[0011] In a possible design, the first uplink channel exists within the first time domain range. Specifically, the first uplink channel exists within a second time domain length after the time domain position of the PUCCH containing the scheduling request, and the time domain position of the DCI that schedules or indicates the transmission of the first uplink channel is before the time domain position of the PUCCH containing the scheduling request. Here, the first uplink channel can be a PUCCH containing HARQ feedback or a PUSCH (such as a PUSCH without uplink data). In this way, the first uplink channel can accurately exist within the first time domain range.

[0012] In a possible design, when there are multiple uplink channels within the first time domain range, the first uplink channel can be the uplink channel with the earliest time domain position among the multiple uplink channels, or the first uplink channel can be the uplink channel with the smallest interval between its time domain position and the time domain position of the PUCCH containing the scheduling request among the multiple uplink channels. In this way, a unique position for sending the scheduling request can be determined, thus avoiding the misalignment between the network device and the terminal device.

[0013] In a possible design, the time slot in which the first uplink channel is located includes a scheduling request occasion. In this way, it can be ensured that the scheduling request is only combined and transmitted in a specific time slot, thus avoiding the network device assuming that there is a scheduling request transmission for each uplink signal or uplink channel.

[0014] In a possible design, when the format of the PUCCH containing the scheduling request is format 0 or format 1, and the first uplink channel is the PUCCH containing HARQ feedback and the format of the PUCCH containing HARQ feedback is format 0, the terminal device combines the scheduling request with the information contained in the first uplink channel to obtain first information. Specifically, the terminal device concatenates the scheduling request with the HARQ feedback to obtain the first information. Furthermore, the terminal device sends the first information to the network device. Specifically, the terminal device maps the first information to a first cyclic shift value and sends the first information to the network device according to the first cyclic shift value. In this way, the terminal device can successfully combine and transmit the scheduling request and the information in the first uplink channel.

[0015] In a possible design, when the format of the PUCCH containing the scheduling request is format 0 or format 1, the first uplink channel is the PUCCH containing HARQ feedback and the format of the PUCCH containing HARQ feedback is format 2, format 3, or format 4, the terminal device combines the scheduling request with the information contained in the first uplink channel to obtain first information. Specifically, the terminal device concatenates the scheduling request and the HARQ feedback to obtain the first information. Further, the terminal device sends the first information to the network device. Specifically, the terminal device sends the first information to the network device through the first uplink channel. In this way, the terminal device can successfully combine and transmit the scheduling request and the information in the first uplink channel.

[0016] In a possible design, when the format of the PUCCH containing the scheduling request is format 0 or format 1, the first uplink channel is the PUCCH containing CSI report and the format of the PUCCH containing CSI report is format 2, format 3, or format 4, the terminal device combines the scheduling request with the information contained in the first uplink channel to obtain first information. Specifically, the terminal device concatenates the scheduling request and the CSI report to obtain the first information. Further, the terminal device sends the first information to the network device. Specifically, the terminal device sends the first information to the network device through the first uplink channel. In this way, the terminal device can successfully combine and transmit the scheduling request and the information in the first uplink channel.

[0017] In a possible design, when the format of the PUCCH containing the scheduling request is format 0, the first uplink channel is the PUCCH containing HARQ feedback and the format of the PUCCH containing HARQ feedback is format 1, the terminal device combines the scheduling request with the information contained in the first uplink channel to obtain first information. Specifically, the terminal device concatenates the scheduling request and the HARQ feedback to obtain the first information. Further, the terminal device sends the first information to the network device. Specifically, the terminal device maps the first information to a second cyclic shift value and sends the first information to the network device according to the second cyclic shift value. In this way, the terminal device can successfully combine and transmit the scheduling request and the information in the first uplink channel.

[0018] In a possible design, when the format of the PUCCH containing the scheduling request is Format 1, the first uplink channel is the PUCCH containing HARQ feedback and the format of the PUCCH containing HARQ feedback is Format 1, the terminal device sends the first information to the network device. Specifically, when it is determined that there is a resource for transmitting the PUCCH Format 1 of the scheduling request in the time domain position of the first uplink channel, the terminal device sends the first information to the network device by means of channel selection. In this way, the terminal device can successfully combine and transmit the scheduling request and the information in the first uplink channel.

[0019] In a possible design, when the format of the PUCCH containing the scheduling request is Format 0 or Format 1 and the first uplink channel is the PUSCH, the terminal device combines the scheduling request and the information contained in the first uplink channel to obtain the first information. Specifically, the terminal device concatenates the scheduling request and the information contained in the PUSCH to obtain the first information. Furthermore, the terminal device sends the first information to the network device through the first uplink channel. In this way, the terminal device can successfully combine and transmit the scheduling request and the information in the first uplink channel.

[0020] In a possible design, when the format of the PUCCH containing the scheduling request is Format 0 or Format 1 and the first uplink channel is the PUSCH, the terminal device combines the scheduling request and the information contained in the first uplink channel to obtain the first information. Specifically, the terminal device punctures the PUSCH and maps the scheduling request to the punctured position of the PUSCH to obtain the first information. Furthermore, the terminal device sends the first information to the network device through the first uplink channel. In this way, the terminal device can successfully combine and transmit the scheduling request and the information in the first uplink channel.

[0021] In a possible design, the terminal device receives a first message from the network device, and the first message is used to configure or enable the function of the terminal device to combine and transmit the scheduling request and the information contained in the first uplink channel. In this way, the terminal device can combine and transmit the scheduling request and the information in the first uplink channel to the network device.

[0022] In a possible design, the terminal device sends a second message to the network device, and the second message is used to request to enable the function of combining and transmitting the scheduling request and the information contained in the first uplink channel. In this way, the terminal device can combine and transmit the scheduling request and the information in the first uplink channel to the network device.

[0023] In a possible design, the terminal device receives a third message from the network device, where the third message is used to instruct the terminal device to combine and transmit a scheduling request with the information included in a first uplink channel. This enables the terminal device to combine and transmit the scheduling request and the information in the first uplink channel to the network device.

[0024] In a possible design, before the terminal device combines the scheduling request with the information included in the first uplink channel to obtain first information, the terminal device determines that the reference signal received power (RSRP) sent to the network device after receiving a reference signal from the network device is greater than an RSRP threshold, where the RSRP is determined by the terminal device based on the reference signal. This can ensure the transmission performance of the terminal device.

[0025] In a possible design, the terminal device sends the first information to the network device, specifically: the terminal device sends the first information to the network device with a first transmission power; where the first transmission power is greater than the original transmission power of the first uplink channel; or the first transmission power is determined based on the original transmission power of the first uplink channel and the original transmission power of the PUCCH including the scheduling request. This can increase the energy per bit on average, thereby ensuring the transmission performance of the terminal device.

[0026] In a second aspect, the present application provides a method for transmitting a scheduling request. The method may include: the network device determines that there is a first uplink channel within a first time domain range; then the network device receives first information from the terminal device, where the first information is obtained by the terminal device combining the scheduling request with the information included in the first uplink channel; where the first time domain range is related to the time domain position of the PUCCH including the scheduling request, and the first uplink channel is any one of the following: a PUCCH including HARQ feedback, a PUCCH including CSI report, or a PUSCH.

[0027] In the above method, by combining and transmitting the scheduling request with the information included in the first uplink channel, the number of uplink transmissions of the terminal device can be reduced, thereby reducing the power consumption of the terminal device.

[0028] In a possible design, the first time domain range may be a first time window and / or a second time window; wherein, the start time of the first time window may be the time when the PHY layer of the terminal device receives a scheduling request from the MAC layer of the terminal device, and the end time may be the start position of the time domain position of the PUCCH containing the scheduling request; alternatively, the end time of the first time window may be the start position of the time domain position of the PUCCH containing the scheduling request, and the time domain length may be a first time domain length; the start time of the second time window may be the end position of the time domain position of the PUCCH containing the scheduling request, and the time domain length may be a second time domain length. This can accurately determine the first time domain range, and further accurately determine whether there is a first uplink channel within the first time domain range.

[0029] In a possible design, the existence of the first uplink channel within the first time domain range may specifically be: there is a first uplink channel after the time when the PHY layer of the terminal device receives a scheduling request from the MAC layer of the terminal device and before the time domain position of the PUCCH containing the scheduling request. This can accurately determine the existence of the first uplink channel within the first time domain range.

[0030] In a possible design, the existence of the first uplink channel within the first time domain range may specifically be: there is a first uplink channel within the first time domain length before the time domain position of the PUCCH containing the scheduling request. This can accurately determine the existence of the first uplink channel within the first time domain range.

[0031] In a possible design, the existence of the first uplink channel within the first time domain range may specifically be: there is a first uplink channel within the second time domain length after the time domain position of the PUCCH containing the scheduling request, where the first uplink channel is a PUCCH containing a CSI report. This can accurately determine the existence of the first uplink channel within the first time domain range.

[0032] In a possible design, the existence of the first uplink channel within the first time domain range may specifically be: there is a first uplink channel within the second time domain length after the time domain position of the PUCCH containing the scheduling request, and the time domain position of the DCI scheduling or indicating the transmission of the first uplink channel is before the time domain position of the PUCCH containing the scheduling request, where the first uplink channel may be a PUCCH containing HARQ feedback or a PUSCH (such as a PUSCH without uplink data). This can accurately determine the existence of the first uplink channel within the first time domain range.

[0033] In a possible design, when there are multiple uplink channels within the first time domain range, the first uplink channel may be the uplink channel with the earliest time domain position among the multiple uplink channels, or the first uplink channel may be the uplink channel with the smallest interval between the time domain position of the multiple uplink channels and the time domain position of the PUCCH containing the scheduling request. In this way, a unique position for sending the scheduling request can be determined, thereby avoiding the inability of the network device and the terminal device to be aligned.

[0034] In a possible design, the time slot where the first uplink channel is located includes a scheduling request occasion. In this way, it can be ensured that the scheduling request is only combined and transmitted in a specific time slot, thereby avoiding the network device assuming that there is a scheduling request transmission for each uplink signal or uplink channel.

[0035] In a possible design, when the PUCCH for HARQ feedback and the format of the PUCCH containing the HARQ feedback is format 0, the first information is obtained by the terminal device cascading the scheduling request and the HARQ feedback; the network device receives the first information from the terminal device, specifically: the network device receives the first information sent by the terminal device according to a first cyclic shift value, and the first cyclic shift value is obtained by the terminal device mapping the first information. In this way, the network device can successfully receive the information of the combined transmission of the scheduling request and the information in the first uplink channel.

[0036] In a possible design, when the format of the PUCCH containing the scheduling request is format 0 or format 1, and the first uplink channel is the PUCCH containing the HARQ feedback and the format of the PUCCH containing the HARQ feedback is format 2, format 3, or format 4, the first information is obtained by the terminal device cascading the scheduling request and the HARQ feedback; the network device receives the first information from the terminal device, specifically: the network device receives the first information sent by the terminal device through the first uplink channel. In this way, the network device can successfully receive the information of the combined transmission of the scheduling request and the information in the first uplink channel.

[0037] In a possible design, when the format of the PUCCH containing the scheduling request is Format 0 or Format 1, the first uplink channel is the PUCCH containing the CSI report and the format of the PUCCH containing the CSI report is Format 2, Format 3 or Format 4, the first information is obtained by the terminal device concatenating the scheduling request and the CSI report; the network device receives the first information from the terminal device, specifically: the network device receives the first information sent by the terminal device through the first uplink channel. In this way, the network device can successfully receive the information transmitted by combining the scheduling request and the information in the first uplink channel.

[0038] In a possible design, when the format of the PUCCH containing the scheduling request is Format 0, the first uplink channel is the PUCCH containing the HARQ feedback and the format of the PUCCH containing the HARQ feedback is Format 1, the first information is obtained by the terminal device concatenating the scheduling request and the HARQ feedback; the network device receives the first information from the terminal device, specifically: the network device receives the first information sent by the terminal device according to a second cyclic shift value, and the second cyclic shift value is obtained by the terminal device mapping the first information. In this way, the network device can successfully receive the information transmitted by combining the scheduling request and the information in the first uplink channel.

[0039] In a possible design, when the format of the PUCCH containing the scheduling request is Format 1, the first uplink channel is the PUCCH containing the HARQ feedback and the format of the PUCCH containing the HARQ feedback is Format 1, the network device receives the first information from the terminal device, specifically: when there is a resource for transmitting PUCCH Format 1 of the scheduling request in the time domain position of the first uplink channel, the network device receives the first information sent by the terminal device through channel selection. In this way, the network device can successfully receive the information transmitted by combining the scheduling request and the information in the first uplink channel.

[0040] In a possible design, when the format of the PUCCH containing the scheduling request is Format 0 or Format 1, the first uplink channel is the PUSCH, the first information is obtained by the terminal device concatenating the scheduling request and the information contained in the PUSCH, and the network device can receive the first information sent by the terminal device through the first uplink channel. In this way, the network device can successfully receive the information transmitted by combining the scheduling request and the information in the first uplink channel.

[0041] In a possible design, when the format of the PUCCH containing the scheduling request is Format 0 or Format 1 and the first uplink channel is the PUSCH, the first information is obtained by the terminal device puncturing the PUSCH and mapping the scheduling request to the punctured position of the PUSCH. The network device may receive the first information sent by the terminal device through the first uplink channel. In this way, the network device can successfully receive the information transmitted by combining the scheduling request and the information in the first uplink channel.

[0042] In a possible design, the network device sends a first message to the terminal device, and the first message is used to configure the terminal device to combine and transmit the scheduling request and the information included in the first uplink channel. In this way, the network device can receive the information transmitted by combining the scheduling request and the information in the first uplink channel.

[0043] In a possible design, the network device receives a second message sent by the terminal device, and the second message is used to request the function of combining and transmitting the scheduling request and the information included in the first uplink channel. In this way, the network device can receive the information transmitted by combining the scheduling request and the information in the first uplink channel.

[0044] In a possible design, the network device sends a third message to the terminal device, and the third message is used to instruct the terminal device to combine and transmit the scheduling request and the information included in the first uplink channel. In this way, the network device can receive the information transmitted by combining the scheduling request and the information in the first uplink channel.

[0045] In a possible design, before the network device receives the first information from the terminal device, the network device determines that the RSRP from the terminal device is greater than the RSRP threshold, where the RSRP is sent by the terminal device after receiving the reference signal from the network device, and the RSRP is determined by the terminal device based on the reference signal. In this way, the transmission performance can be guaranteed.

[0046] In a third aspect, the present application further provides a communication device, which may be a terminal device. The communication device has the functions of the terminal device in the above first aspect or each possible design example of the first aspect. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0047] In a possible design, the structure of the communication device may include a transceiver unit and a processing unit, and these units may perform the corresponding functions of the terminal device in the above-mentioned first aspect or each possible design example of the first aspect. For specific details, refer to the detailed description in the method examples, which will not be elaborated here.

[0048] In a possible design, the structure of the communication device includes a transceiver and a processor, and optionally further includes a memory. The transceiver is used to transmit and receive data or information, and to communicate and interact with other devices in the communication system. The processor is configured to support the communication device in performing the corresponding functions of the terminal device in the above-mentioned first aspect or each possible design example of the first aspect. The memory is coupled to the processor and stores the necessary program instructions and data of the communication device.

[0049] In a fourth aspect, the present application further provides a communication device, which may be a network device, and this communication device has the functions of the network device in the above-mentioned second aspect or each possible design example of the second aspect. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0050] In a possible design, the structure of the communication device may include a transceiver unit and a processing unit, and these units may perform the corresponding functions of the network device in the above-mentioned second aspect or each possible design example of the second aspect. For specific details, refer to the detailed description in the method examples, which will not be elaborated here.

[0051] In a possible design, the structure of the communication device includes a transceiver and a processor, and optionally further includes a memory. The transceiver is used to transmit and receive data or information, and to communicate and interact with other devices in the communication system. The processor is configured to support the communication device in performing the corresponding functions of the network device in the above-mentioned second aspect or each possible design example of the second aspect. The memory is coupled to the processor and stores the necessary program instructions and data of the communication device.

[0052] In a fifth aspect, an embodiment of the present application provides a communication system, which may include the above-mentioned terminal device and network device.

[0053] Sixth aspect, a computer-readable storage medium provided by an embodiment of the present application. The computer-readable storage medium stores program instructions. When the program instructions run on a computer, the computer is caused to execute the methods of the first aspect or each possible design example of the first aspect or the second aspect or each possible design example of the second aspect in the embodiments of the present application. Exemplarily, the computer-readable storage medium can be any available medium that can be accessed by a computer. Taking this as an example but not limited to: the computer-readable medium can include a non-transitory computer-readable medium, random-access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), CD-ROM or other optical disc storage, magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer.

[0054] Seventh aspect, a computer program product provided by an embodiment of the present application includes computer program code or instructions. When it runs on a computer, the computer is caused to implement the methods of the first aspect or each possible design example of the first aspect or the second aspect or each possible design example of the second aspect.

[0055] Eighth aspect, the present application further provides a chip. The chip is coupled to a memory and is used to read and execute program instructions stored in the memory to implement the methods of the first aspect or each possible design example of the first aspect or the second aspect or each possible design example of the second aspect.

[0056] For the aspects from the third aspect to the eighth aspect above and the possible technical effects that each aspect may achieve, please refer to the description of the possible technical effects that can be achieved by various possible solutions in the first aspect or the second aspect above, and details will not be repeated here. Description of the Drawings

[0057] Figure 1 It is a schematic diagram of the architecture of a communication system provided by the present application;

[0058] Figure 2 It is a flowchart of a method for transmitting a scheduling request provided by the present application;

[0059] Figure 3 It is a schematic diagram of a first time window and a second time window provided by the present application;

[0060] Figure 4 It is a schematic diagram of the transmission of a scheduling request provided by the present application;

[0061] Figure 5 Another schematic diagram of the transmission of a scheduling request provided for this application;

[0062] Figure 6 Another schematic diagram of the transmission of a scheduling request provided for this application;

[0063] Figure 7 Another schematic diagram of the transmission of a scheduling request provided for this application;

[0064] Figure 8 Another schematic diagram of the transmission of a scheduling request provided for this application;

[0065] Figure 9 Another schematic diagram of the transmission of a scheduling request provided for this application;

[0066] Figure 10 A schematic flow diagram of the transmission of a scheduling request provided for this application;

[0067] Figure 11 Another schematic flow diagram of the transmission of a scheduling request provided for this application;

[0068] Figure 12 Another schematic flow diagram of the transmission of a scheduling request provided for this application;

[0069] Figure 13 Another schematic flow diagram of the transmission of a scheduling request provided for this application;

[0070] Figure 14 A schematic diagram of time window 1 and time window 2 provided for this application;

[0071] Figure 15 A schematic diagram of the transmission of an SR provided for this application;

[0072] Figure 16 Another schematic diagram of the transmission of an SR provided for this application;

[0073] Figure 17 Another schematic diagram of the transmission of an SR provided for this application;

[0074] Figure 18 Another schematic diagram of the transmission of an SR provided for this application;

[0075] Figure 19 Another schematic diagram of the transmission of an SR provided for this application;

[0076] Figure 20 A schematic flow diagram of the transmission of an SR provided for this application;

[0077] Figure 21Another schematic diagram of the SR transmission provided by this application;

[0078] Figure 22 Another schematic diagram of the SR transmission provided by this application;

[0079] Figure 23 Another schematic diagram of the SR transmission provided by this application;

[0080] Figure 24 A schematic structural diagram of a communication device provided by this application;

[0081] Figure 25 A structural diagram of a communication device provided by this application. Detailed implementation manners

[0082] The present application will be further described in detail below with reference to the accompanying drawings.

[0083] The embodiments of the present application provide a method and a device for transmitting a scheduling request, which are used to propose how to optimize the transmission of the scheduling request to save the power consumption of the terminal device. Among them, the method and the device in the present application are based on the same technical concept. Since the principles of solving problems by the method and the device are similar, the implementation of the device and the method can be referred to each other, and the repeated parts will not be described again.

[0084] In the description of the present application, terms such as "first" and "second" are only used for the purpose of distinguishing descriptions, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying an order.

[0085] In the description of the present application, "at least one (item, kind)" means one (item, kind) or more than one (item, kind), and more than one (item, kind) means two (items, kinds) or more than two (items, kinds).

[0086] In order to more clearly describe the technical solutions of the embodiments of the present application, the method and the device for transmitting a scheduling request provided by the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0087] Figure 1 Shows the architecture of the communication system involved in the embodiments of the present application. The architecture of the communication system includes a network device and a terminal device, where:

[0088] The network device is a device with wireless transceiver functions or a chip that can be set in the network device. The network device includes, but is not limited to: a base station (generation node B, gNB), a radio network controller (RNC), a Node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., home evolved NodeB, or home Node B, HNB), a baseband unit (BBU), an access point (AP) in a wireless fidelity (Wi-Fi) system, a wireless relay node, a wireless backhaul node, a transmission and reception point (TRP or transmission point, TP), etc. It can also be a network node that constitutes a gNB or a transmission point, such as a baseband unit (BBU), or a distributed unit (DU), etc.

[0089] In some deployments, a gNB can include a centralized unit (CU) and a DU. A gNB can also include a radio unit (RU). The CU implements some functions of the gNB, and the DU implements some functions of the gNB. For example, the CU implements radio resource control (RRC) and the functions of the packet data convergence protocol (PDCP) layer, and the DU implements the functions of the radio link control (RLC), media access control (MAC), and physical (PHY) layers. Since the information of the RRC layer will ultimately become the information of the PHY layer, or is transformed from the information of the PHY layer, thus, in this architecture, high-layer signaling, such as RRC layer signaling or PHCP layer signaling, can also be considered to be sent by the DU, or sent by the DU + RU. It can be understood that the network device can be a CU node, or a DU node, or a device including a CU node and a DU node. In addition, the CU can be classified as a network device in the radio access network (RAN), or the CU can be classified as a network device in the core network (CN), and this is not limited.

[0090] The terminal device may also be referred to as a user equipment (UE), access terminal, user unit, user station, mobile station, mobile device, remote station, remote terminal, mobile equipment, user terminal, terminal, wireless communication device, user agent, or user device. The terminal device in the embodiments of the present application may be a mobile phone, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a smart wearable device (such as smart glasses, smart watches, smart earphones, etc.), a wireless terminal in smart home, etc., or may also be a chip or a chip module (or a chip system) that can be disposed in the above devices. The embodiments of the present application do not limit the application scenarios. In the present application, the terminal device with wireless transceiver function and the chip that can be disposed in the foregoing terminal device are collectively referred to as the terminal device.

[0091] It should be noted that Figure 1 The shown communication system may be but is not limited to a fourth-generation (4G) system, a fifth-generation (5G) system, such as a new radio access technology (NR). Optionally, the method of the embodiments of the present application is also applicable to various future communication systems, such as a sixth-generation (6G) system or other communication networks.

[0092] Currently, in some embodiments, the uplink transmission of NR and related processes may be as follows:

[0093] 1. Uplink data: It is carried and transmitted in the physical uplink shared channel (PUSCH).

[0094] (1) The time-domain position of PUSCH transmission is usually indicated by the downlink control information (DCI) sent by the network device to the terminal device. Specifically, if the network device sends a DCI in slot n and a K2 value is indicated in the DCI, the terminal device sends PUSCH in slot n + K2. The PUSCH scheduled by DCI is generally referred to as dynamic data scheduling.

[0095] (2) There is also another PUSCH transmission mode in the standard, which is the configured grant (CG) transmission mode. CG can be divided into two cases: In one case, the transmission parameters of PUSCH are configured to the terminal device through the radio resource control (RRC) signaling of the network device. When the terminal device has uplink data to send, it sends through the pre-configured PUSCH. In another case, some of the transmission parameters of PUSCH are configured through the RRC signaling of the network device, and the remaining transmission parameters are indicated by DCI. When the network device sends a DCI to activate the PUSCH transmission, the terminal device will perform periodic transmission according to the configured period value until the network device sends another DCI to stop the PUSCH transmission of the terminal device. Therefore, in the CG transmission mode, there may be a situation of "only PUSCH without DCI".

[0096] 2. Hybrid automatic repeat request (HARQ) feedback: HARQ feedback is usually carried in PUCCH for transmission. The time-domain position of the PUCCH carrying HARQ feedback can be indicated by DCI, which is sent by the network device to the terminal device. Specifically, if the network device sends a DCI to schedule the transmission of downlink data in slot n, a K0 value and a K1 value are indicated in the DCI. The terminal device receives the physical downlink shared channel (PDSCH) in slot n + K0, where the PDSCH contains downlink data, and the terminal device sends the HARQ feedback corresponding to the PDSCH in slot n + K0 + K1. HARQ feedback can be sent using PUCCH format 0 / 1 / 2 / 3 / 4.

[0097] 3. Channel State Information (CSI) Report: After the terminal device receives the CSI reference signal (CSI-RS) sent by the network device, it will send a CSI report to the network device. The CSI report can be classified into the following three categories:

[0098] (1) Periodic CSI Report (P-CSI report): Usually transmitted on the PUCCH. Once the network device configures a periodic CSI report for the terminal device, the terminal device will send the CSI report according to the configured period. That is, the time-domain position of the periodic CSI report is semi-statically configured through RRC signaling. The periodic CSI report can be sent using PUCCH format 2 / 3 / 4.

[0099] (2) Semi-persistence CSI Report (SP-CSI report): Similar to the periodic CSI report, it is usually transmitted on the PUCCH. However, the difference from the periodic CSI report is that after the network device configures the semi-persistence CSI report for the terminal device, it needs to be activated again. After activation, its time-domain position can be considered to be semi-statically configured through RRC signaling. The semi-persistence CSI report can be sent using PUCCH format 2 / 3 / 4.

[0100] (3) Aperiodic CSI Report (AP-CSI report): Transmitted on the PUSCH and triggered by DCI. Specifically, if the network device sends a DCI in slot n, in addition to indicating the K2 value, the DCI can also contain an aperiodic CSI trigger information. If the DCI contains the aperiodic CSI trigger information, the terminal device will carry the aperiodic CSI report in the scheduled PUSCH.

[0101] 4. Scheduling Request (SR): The SR is carried and sent in the PUCCH. The network device configures one or more PUCCH resources for the terminal device to send the SR, and each PUCCH resource appears periodically. When the terminal device has uplink data to send, the media access control (MAC) layer in the terminal device determines an SR transmission occasion and sends an indication to the physical (PHY) layer in the terminal device, instructing the PHY layer to send the SR on this SR transmission occasion. The SR can be sent using PUCCH format 0 / 1.

[0102] Currently, there are 5 formats of PUCCH, namely format 0 / 1 / 2 / 3 / 4. Among them, format 0 and format 1 can carry 1 to 2 bits of information, and format 2 / 3 / 4 can carry more than 2 bits of information. Format 0 and format 2 occupy 1 or 2 orthogonal frequency division multiplexing (OFDM) symbols in the time domain, so format 0 / 2 can be called short PUCCH, and format 1 / 3 / 4 occupy 4 or more OFDM symbols in the time domain, so format 1 / 3 / 4 can be called long PUCCH. Among them, PUCCH format can be abbreviated as PF.

[0103] In this application, in order to save the power consumption of the terminal device, it is proposed that the above uplink transmission can be optimized. Specifically, in this application, the transmission method of the scheduling request is mainly described in detail. It should be noted that the scheduling request can be a scheduling request (SR) in 5G; in future communication systems or networks, such as 6G, etc., it can still be SR, or it can have other names, and this application does not make any limitations in this regard.

[0104] It should be noted that the operations implemented by the terminal device involved in the following embodiments can also be implemented by a processor in the terminal device, or a chip or chip system, or a functional module, etc.; the operations implemented by the network device involved can also be implemented by a processor in the network device, or a chip or chip system, or a functional module, etc.

[0105] Based on the above description, a transmission method of a scheduling request provided by an embodiment of this application is applicable toFigure 1 The communication system shown. Refer to Figure 2 As shown, the specific process of this method may include:

[0106] Step 201: The terminal device determines that there is a first uplink channel within a first time domain range; wherein, the first time domain range is related to the time domain position of the PUCCH containing the scheduling request, and the first uplink channel may be any one of the following: PUCCH containing HARQ feedback, PUCCH containing CSI report, or PUSCH.

[0107] Among them, the PUSCH may be a PUSCH without uplink data, for example, a PUSCH without an uplink shared channel (UL-SCH); the HARQ feedback may be an acknowledgment (ACK) or a negative acknowledgment (NACK).

[0108] Step 202: The terminal device combines the scheduling request with the information contained in the first uplink channel to obtain first information.

[0109] Step 203: The terminal device sends the first information to the network device.

[0110] In an optional implementation manner, the first time domain range may be a first time window (window 1) and / or a second time window (window 2); wherein, the start moment of the first time window may be the moment triggered when the PHY layer of the terminal device receives the scheduling request from the MAC layer of the terminal device, and the end moment may be the time domain position of the PUCCH containing the scheduling request (which may also be referred to as the scheduling request occasion or the PUCCH resource containing the scheduling request); or, the end moment of the first time window may be the time domain position of the PUCCH containing the scheduling request, and the time domain length may be a first time domain length; the start moment of the second time window may be the time domain position of the PUCCH containing the scheduling request, and the time domain length may be a second time domain length. For example, an example of the first time window and the second time window may be as Figure 3 shown.

[0111] Optionally, the time domain position of the PUCCH containing the scheduling request may specifically be the start position of the time domain position of the PUCCH, or may be the end position of the time domain position of the PUCCH, or may also be the middle position of the time domain position of the PUCCH, etc., and this application does not limit this.

[0112] In one example, the first time domain length or the second time domain length may be one or more symbols, or one or more slots, etc.

[0113] By means of the first time window and / or the second time window, it can be ensured that the scheduling request can be merged into the uplink channel (i.e., the first uplink channel) at a nearby time domain position and sent together, thereby reducing the number of times the terminal device sends uplink data and reducing the power consumption of the terminal device's uplink transmission. Specifically, if the first time window is located before the time domain position of the PUCCH carrying the scheduling request, the first time window can be used to ensure the uplink channel within a period of time before the scheduling request. In one case, the start time of the first time window can be the time when the PHY layer of the terminal device receives the scheduling request triggered by the MAC layer of the terminal device. If the terminal device follows the current embodiment process, that is, does not merge and transmit the scheduling request, the terminal device will generate a scheduling request and wait until the time domain position of the PUCCH containing the scheduling request to send the scheduling request. If there is another uplink channel (i.e., the first uplink channel) within the first time window, the terminal device can merge the generated scheduling request into this uplink channel without waiting until the time domain position of the PUCCH containing the scheduling request to send the scheduling request. In this way, on the one hand, the power consumption of the terminal device's uplink transmission can be reduced, and on the other hand, the scheduling request can be sent in advance, reducing the overall communication delay. In another case, the end time of the first time window can be the time domain position of the PUCCH containing the scheduling request, and the time domain length can be the first time domain length. This is because it is unknown to the network device when the MAC layer of the terminal device will trigger the scheduling request to be sent. Therefore, from the perspective of the network device, it can only start from the time domain position of the PUCCH containing the scheduling request and consider that the uplink channel within the previous first time domain length may carry the merged scheduling request. In this case, the first time domain length can be understood as the maximum value of a time range (i.e., time domain range) for the MAC layer of the terminal device to trigger the scheduling request to be sent.

[0114] The second time window is located after the time domain position of the PUCCH containing the scheduling request, that is, the second time window can be used to ensure the uplink channel within a period of time after the scheduling request. This second time window can ensure that the sending of the scheduling request will not be delayed too much, that is, the overall communication delay will not increase too much due to the merged transmission method of this application. At this time, the second time domain length can be understood as the time domain length determined according to the maximum data transmission delay (or data transmission delay budget).

[0115] It should be noted that the time window can also be referred to as a time domain range or a time region, etc., and this application does not make any limitations in this regard.

[0116] Exemplarily, the first time window and the second time window can be predefined in the standard, or can be configured by the network device to the terminal device, or there can be other ways to determine, and this application does not make any limitations in this regard.

[0117] Specifically, the existence of a first uplink channel within the first time domain range may include the following four cases:

[0118] Case a1: There is a first uplink channel after the moment when the PHY layer of the terminal device receives the scheduling request triggered by the MAC layer of the terminal device and before the time domain position of the PUCCH containing the scheduling request. That is, the first uplink channel is within the first time window. For example, in this case a1, the transmission of the scheduling request can be as Figure 4 shown.

[0119] Case a2: There is a first uplink channel within the first time domain length before the time domain position of the PUCCH containing the scheduling request. That is, the first uplink channel is within the first time window. For example, in this case a2, the transmission of the scheduling request can be as Figure 5 shown.

[0120] It should be noted that the above cases a1 and a2 are related to different interpretations of the above first time window. Among them, the above case a1 corresponds to the case where the start time of the first time window is the moment when the PHY layer of the terminal device receives the scheduling request triggered by the MAC layer of the terminal device, and the end time is the time domain position of the PUCCH containing the scheduling request; the above case a2 corresponds to the case where the end time of the first time window is the time domain position of the PUCCH containing the scheduling request, and the time domain length can be the first time domain length.

[0121] Case a3: There is a first uplink channel within the second time domain length after the time domain position of the PUCCH containing the scheduling request. That is, the first uplink channel is within the second time window. For example, in this case a3, the transmission of the scheduling request can be as Figure 6 shown.

[0122] For example, in this case a3, the first uplink channel can be a PUCCH containing a CSI report. Since the PUCCH containing a CSI report is semi-statically configured, the terminal device can pre-judge that there will definitely be such a PUCCH (i.e., the first uplink channel) that can be used within a certain range after the PUCCH of the scheduling request, and thus can successfully merge the scheduling request into the PUCCH containing the CSI report for transmission.

[0123] Case a4: There is a first uplink channel within the second time domain length after the time domain position of the PUCCH containing the scheduling request, and the time domain position of the DCI scheduling or indicating the transmission of the first uplink channel is before the time domain position of the PUCCH containing the scheduling request. That is, the first uplink channel is within the second time window. For example, in this case a4, the transmission of the scheduling request can be as Figure 7 shown.

[0124] For example, in this case a4, the first uplink channel may be a PUCCH including HARQ feedback or a PUSCH (such as a PUSCH without uplink data). In this case a4, although the transmission of the first uplink channel is not semi-statically configured but dynamically scheduled, the DCI scheduling the transmission of the first uplink channel is located before the PUCCH of the scheduling request. That is, before the PUCCH of the scheduling request, the terminal device can determine whether there will be an available first uplink channel in the subsequent second time window. If there is an available first uplink channel, the terminal device can merge the scheduling request into the first uplink channel. If there is no available first uplink channel, the terminal device uses the originally scheduled PUCCH of the scheduling request to send the scheduling request.

[0125] Of course, there may be other situations where there is a first uplink channel within the first time domain range. The above cases a1 to a4 are only examples and will not be listed one by one here.

[0126] In an alternative embodiment, when there are multiple uplink channels within the first time domain range, the first uplink channel may be the uplink channel with the earliest time domain position among the multiple uplink channels, or the first uplink channel may also be the uplink channel with the smallest interval between the time domain position and the time domain position of the PUCCH including the scheduling request among the multiple uplink channels. This can determine a unique position for sending the scheduling request, thus avoiding misalignment between the network device and the terminal device.

[0127] In an alternative embodiment, when there are multiple uplink channels within the first time domain range, the first uplink channel may be any one of the multiple uplink channels. For example Figure 8 as shown.

[0128] In an alternative embodiment, the time slot in which the first uplink channel is located includes a scheduling request occasion. That is, when there are multiple uplink channels within the first time domain range, the uplink channel including the scheduling request occasion among the multiple uplink channels is used as the first uplink channel. For example Figure 9 as shown.

[0129] In specific implementation, the MAC layer of the terminal device can determine whether the scheduling request and the information included in the first uplink channel can be merged (that is, determine whether there is a first uplink channel within the first time domain range), and the MAC layer instructs the PHY layer of the terminal device to transmit the uplink channel of the scheduling request, and then the PHY layer of the terminal device performs the transmission of the scheduling request; or, the MAC layer of the terminal device can only indicate the time domain position of a PUCCH of the scheduling request, and then the PHY layer of the terminal device determines whether the scheduling request and the information included in the first uplink channel can be merged and performs the transmission of the scheduling request.

[0130] Currently, in some embodiments, when the PUCCH containing the scheduling request partially or overlaps with other uplink channels in the time domain, the transmission methods of the scheduling request and the information in other uplink channels can be as shown in Table 1 below, where the scheduling request is taken as an example of SR in Table 1.

[0131] Table 1

[0132]

[0133]

[0134] Among them, in the above Table 1, m cs is the value of the cyclic shift value. For example, when m cs = 6, it means that the cyclic shift value used is 6.

[0135] In some examples, when the scheduling request can be combined and transmitted in the PUCCH containing HARQ feedback, and the format of the PUCCH containing HARQ feedback is format 0 / 2 / 3 / 4, or when the scheduling request can be combined and transmitted in the PUCCH containing CSI report, and the format of the PUCCH containing CSI report is format 2 / 3 / 4, the terminal device can adopt the corresponding method in the above Table 1 (that is, the method in bold in the above Table 1) to transmit the scheduling request. Specifically, it can include the following scenarios:

[0136] Scenario b1: When the format of the PUCCH containing the scheduling request is format 0 or format 1, and the first uplink channel is the PUCCH containing HARQ feedback and the format of the PUCCH containing HARQ feedback is format 0, the terminal device can concatenate the scheduling request and the HARQ feedback to obtain the first information; then, the terminal device maps the first information to the first cyclic shift value and sends the first information to the network device according to the first cyclic shift value. For example, when the HARQ feedback is 1 bit and the value of the HARQ feedback bit is ACK, and there is a scheduling request to be sent (that is, the current terminal device requests uplink data scheduling from the network device), then m cs = 3. At this time, the terminal device generates a PUCCH using a sequence with the first cyclic shift value of 3, and then sends the PUCCH to the network device.

[0137] Scenario b2: When the format of the PUCCH carrying the scheduling request is Format 0 or Format 1, and the first uplink channel is the PUCCH carrying HARQ feedback and the format of the PUCCH carrying HARQ feedback is Format 2, Format 3, or Format 4, the terminal device cascades the scheduling request and the HARQ feedback to obtain the first information; then, the terminal device sends the first information to the network device through the first uplink channel. Among them, when the terminal device cascades the scheduling request and the HARQ feedback, the bits corresponding to the scheduling request (for example, log(K + 1) bits) and the bits corresponding to the HARQ feedback are cascaded.

[0138] Scenario b3: When the format of the PUCCH carrying the scheduling request is Format 0 or Format 1, and the first uplink channel is the PUCCH carrying CSI report and the format of the PUCCH carrying CSI report is Format 2, Format 3, or Format 4, the terminal device cascades the scheduling request and the CSI report to obtain the first information; then, the terminal device sends the first information to the network device through the first uplink channel. Among them, when the terminal device cascades the scheduling request and the CSI report, the bits corresponding to the scheduling request (for example, log(K + 1) bits) and the bits corresponding to the CSI report are cascaded.

[0139] In some other examples, for the first uplink channel being the PUCCH carrying HARQ feedback and the format of this PUCCH being Format 1, or the first uplink channel being PUSCH (such as PUSCH without uplink data), the terminal device no longer adopts the corresponding method in Table 1 above (that is, the method corresponding to the non-bold font in Table 1). Specifically, the terminal device can adopt the methods in the following scenarios:

[0140] Scenario c1: When the format of the PUCCH carrying the scheduling request is Format 0, and the first uplink channel is the PUCCH carrying HARQ feedback and the format of the PUCCH carrying HARQ feedback is Format 1, the terminal device can adopt the following method:

[0141] Method 1: The terminal device does not combine the scheduling request and the HARQ feedback, that is, the scheduling request cannot be combined for transmission.

[0142] Method 2: (1) If the HARQ feedback has only 1-bit information, the terminal device cascades the scheduling request and the HARQ feedback to obtain the first information, then maps the first information to a second cyclic shift value, and sends the first information to the network device according to the second cyclic shift value. That is, the terminal device carries the scheduling request through the cyclic shift of the PUCCH, that is, if there is no scheduling request (that is, the current terminal device does not request uplink data scheduling from the network device), then m CS= 0 / 6 (i.e., the second cyclic shift value); if there is a scheduling request (i.e., the current terminal device requests uplink data scheduling from the network device), then m CS = 3 / 9 (i.e., the second cyclic shift value).

[0143] (2) If the HARQ feedback has 2-bit information, the 3-bit information composed of the scheduling request and the HARQ feedback can generate an 8-phase shift keying (8PSK) modulation symbol, which is multiplied by a sequence, for example, it can conform to the following formula one:

[0144]

[0145] where y(n) is the first information, is the sequence, u, v, α, and δ are sequence generation parameters, is the number of subcarriers included in a resource block (RB), and its value can be 12, etc.; d(0) is the 8PSK modulation symbol.

[0146] Optionally, when the HARQ feedback has 2-bit information, the terminal device may not combine the scheduling request and the HARQ feedback.

[0147] Scenario c2: When the format of the PUCCH containing the scheduling request is format 1, the first uplink channel is the PUCCH containing the HARQ feedback and the format of the PUCCH containing the HARQ feedback is format 1, when it is determined that there is a resource of PUCCH format 1 for transmitting the scheduling request at the time domain position of the first uplink channel, the terminal device sends the first information to the network device by means of channel selection.

[0148] Optionally, when it is determined that there is no resource of PUCCH format 1 for transmitting the scheduling request at the time domain position of the first uplink channel, the terminal device may not combine the scheduling request and the HARQ feedback.

[0149] Scenario c3: When the format of the PUCCH containing the scheduling request is format 0 or format 1, and the first uplink channel is a PUSCH (for example, a PUSCH without uplink data), the terminal device combines the scheduling request with the information included in the first uplink channel to obtain the first information, which may include the following two methods:

[0150] Method 1: The terminal device cascades the scheduling request and the information included in the PUSCH to obtain the first information.

[0151] In the first method, the scheduling request can be multiplexed into the PUSCH, that is, the information bits of the scheduling request are concatenated with the uplink data information bits, and then modulated and mapped together onto the physical resources of the PUSCH, thus obtaining the first information.

[0152] Method 2: The terminal device punctures the PUSCH and maps the scheduling request to the punctured positions of the PUSCH, obtaining the first information. Here, the first information is the scheduling request mapped to the punctured positions of the PUSCH and the information at the non-punctured positions of the PUSCH.

[0153] In this second method, the terminal device modulates the scheduling request separately. After the terminal device punctures the PUSCH, it replaces the modulation symbols on some resource elements (REs) occupied by the punctured PUSCH with the modulation symbols after modulating the scheduling request, thus obtaining the first information.

[0154] Exemplarily, the punctured positions of the PUSCH can be predefined. For example, in the time domain, the terminal device can start puncturing from the first symbol occupied by the PUSCH, or the terminal device can start puncturing from the first symbol in the PUSCH except for the DMRS; in the frequency domain, the terminal device can start puncturing from the starting RE occupied by the PUSCH, and the two punctured REs can be separated by h REs, where h can be predefined. Of course, there can be other possibilities for the punctured positions of the PUSCH, as long as the information at the punctured positions has less impact on data transmission. This application does not make any limitations in this regard.

[0155] Optionally, when the format of the PUCCH containing the scheduling request is format 0 or format 1 and the first uplink channel is the PUSCH (such as a PUSCH without uplink data), the terminal device may not combine the scheduling request with the information in the PUSCH.

[0156] Currently, when the scheduling request and the information in the first uplink channel are transmitted separately, the terminal device needs to send signals twice. Although the transmission power consumption of the terminal device is relatively large, the energy per bit in each of the two signals is also relatively high, which can resist stronger noise and the signal coverage range is relatively large. When using the method of this application to combine and transmit the scheduling request and the information in the first uplink channel, whether it is the scheduling request or the information in the first uplink channel, the energy per bit will be relatively low, the signal coverage range may be limited, and the signal transmission reliability will be reduced. To solve the problem of signal transmission reliability, this application can ensure signal transmission reliability through the following several methods:

[0157] Method d1: After the terminal device receives a reference signal from the network device, the terminal device performs steps 202 and 203 only when the reference signal received power (RSRP) sent to the network device is greater than the RSRP threshold. The RSRP is determined by the terminal device based on the reference signal.

[0158] Among them, the terminal device calculates an RSRP value according to the power of the reference signal received from the network device (such as a synchronization signal block and a physical broadcast channel (PBCH) block, or a CSI-RS, etc.). The larger the RSRP value, the closer the terminal device is to the network device. The RSRP threshold is equivalent to an equivalent distance threshold from the network device to the terminal device. When the RSRP corresponding to the reference signal received by the terminal device is greater than the RSRP threshold, it means that the terminal device is close enough to the network device. At this time, even if the terminal device combines the scheduling request with the information in the first uplink channel and sends it, it can ensure that the signal can be correctly transmitted. When the RSRP reported by the terminal device to the network device is greater than the RSRP threshold, it can be considered that the coverage of the terminal device is not limited. At this time, the scheduling request can be transmitted in the manner of steps 202 and 203 above.

[0159] Exemplarily, when the RSRP does not meet the conditions in method d1, the terminal device can use the commonly used method to send a scheduling request, such as the method of transmitting the scheduling request alone.

[0160] It should be noted that only when both the terminal device and the network device determine that the RSRP is greater than the RSRP threshold will the scheduling request be transmitted in the manner of steps 202 and 203. Therefore, by comparing the RSRP sent by the terminal device to the network device with the RSRP threshold, it can be determined whether the conditions are met for both the terminal device and the network device.

[0161] Method d2: When the terminal device sends the first information to the network device, the terminal device can send the first information to the network device with the first transmit power.

[0162] Among them, the first transmit power can be determined in the following two ways:

[0163] The first way: The first transmit power can be obtained by adding X decibels (dB) to the original transmit power of the first uplink channel, where the value of X can be pre-defined standard, or pre-configured by the network device to the terminal device, or indicated by the network device through a signaling (such as DCI). This application does not make any limitations in this regard.

[0164] The second method: The first transmission power can be determined based on the original transmission power of the first uplink channel and the original transmission power of the PUCCH including the scheduling request. Exemplarily, the first transmission power can be obtained by adding the original transmission power of the first uplink channel and the original transmission power of the PUCCH, or the first transmission power can be obtained by multiplying the sum of the original transmission power of the first uplink channel and the original transmission power of the PUCCH by a coefficient. For example, if the original transmission power of the PUCCH is 16 dBm and the original transmission power of the first uplink channel is 16 dBm, the first transmission power can be the sum of the two, i.e., 19 dBm, or the sum of the two multiplied by a coefficient, which is 18 dBm, etc. Of course, there can be other methods to obtain the first transmission power, and this application does not limit it.

[0165] It should be understood that the above two methods are both for increasing the transmission power. In some embodiments, the transmission power of the first uplink channel can be determined according to the path loss value estimated by the terminal device, the transmission parameters configured by the network device, and the transmit power control (TPC) command indicated by the network device in the DCI. To improve the transmission reliability of the combined transmission of the scheduling request and the information in the first uplink channel, the method in d2 above can be adopted to increase the transmission power of the first uplink channel, thereby increasing the energy per bit on average.

[0166] In an alternative embodiment, when the terminal device combines and transmits the scheduling request and the information included in the first uplink channel to the network device, and when the network device receives the combined transmission of the scheduling request and the information included in the first uplink channel from the terminal device, both parties need to reach an agreement to jointly enable or disable this function (i.e., the function of combining and transmitting the scheduling request and the information included in the first uplink channel). Exemplarily, the enabling of this function can be configured in the following four ways:

[0167] Method e1: The terminal device receives a first message from the network device, and the first message is used to configure or enable the function of the terminal device to combine and transmit the scheduling request and the information included in the first uplink channel.

[0168] Among them, the first message is also the configuration information sent by the network device to the terminal device. For example, the first message can be sent through radio resource control (RRC) signaling or a medium access control (MAC) control element (CE) (MAC CE).

[0169] Through the above method, when there is a first uplink channel within the first time domain range, the terminal device can combine and transmit the scheduling request with the information included in the first uplink channel, and the network device can receive the scheduling request combined and transmitted by the terminal device with the information included in the first uplink channel. For example, the specific process can be as Figure 10 shown.

[0170] Method e2: The terminal device sends a second message to the network device. The second message is used to request to enable the function of combining and transmitting the scheduling request with the information included in the first uplink channel. Then, the terminal device receives a first message from the network device. The first message is used to configure or enable the terminal device to combine and transmit the scheduling request with the information included in the first uplink channel. After that, when there is a first uplink channel within the first time domain range, the terminal device can combine and transmit the scheduling request with the information included in the first uplink channel, and the network device can receive the scheduling request combined and transmitted by the terminal device with the information included in the first uplink channel. For example, the specific process can be as Figure 11 shown.

[0171] Method e3: The terminal device receives a first message from the network device. The first message is used to configure or enable the terminal device to combine and transmit the scheduling request with the information included in the first uplink channel; then the terminal device receives a third message from the network device. The third message is used to instruct the terminal device to combine and transmit the scheduling request with the information included in the first uplink channel. After that, when there is a first uplink channel within the first time domain range, the terminal device can combine and transmit the scheduling request with the information included in the first uplink channel, and the network device can receive the scheduling request combined and transmitted by the terminal device with the information included in the first uplink channel. For example, the specific process can be as Figure 12 shown.

[0172] In this method e3, after the network device sends the configuration information (i.e., the first message) to the terminal device, it also needs to send dynamic indication information, that is, the third message (such as DCI), to indicate whether the terminal device can combine and transmit the scheduling request with the information included in the first uplink channel. For example, the third message can be added to the DCI of the PUSCH / PUCCH scheduled by the network device to indicate whether the scheduling request can be combined and transmitted with the information included in the first uplink channel.

[0173] Method e4: The terminal device sends a second message to the network device. The second message is used to request enabling the function of combining the scheduling request and the information included in the first uplink channel for transmission. Then, the terminal device receives a first message from the network device. The first message is used to configure or enable the terminal device to combine the scheduling request and the information included in the first uplink channel for transmission. After that, the terminal device receives a third message from the network device. The third message is used to instruct the terminal device to combine the scheduling request and the information included in the first uplink channel for transmission. Finally, when there is a first uplink channel within the first time domain range, the terminal device can combine the scheduling request and the information included in the first uplink channel for transmission, and the network device can receive the combined scheduling request and the information included in the first uplink channel sent by the terminal device. For example, the specific process can be as Figure 13 shown.

[0174] That is, method e4 is a combination of the above three methods. For the specific message descriptions, reference can be made to the relevant descriptions in the above methods.

[0175] By adopting the scheduling request transmission method provided in this application and combining the scheduling request and the information included in the first uplink channel for transmission, the number of uplink transmissions can be reduced, thereby reducing the power consumption of the terminal device.

[0176] The following combines an actual scenario to illustrate that by adopting the method involved in the above embodiments, the number of uplink transmissions can be reduced, thereby reducing the power consumption of the terminal device. Specifically, when the terminal device is a mobile phone, in the scenario where a mobile phone user uses the mobile phone to send and receive WeChat messages, when the user receives WeChat messages through the mobile phone, the user will receive downlink data packets (included in PDSCH) and send HARQ feedback (included in PUCCH) to the network device. When the user sends WeChat messages through the mobile phone, the user will first send a scheduling request to the network device. If the current method is adopted, if the time domain position for sending HARQ feedback determined by the mobile phone according to the configuration / indication of the network device does not overlap with the time domain position for sending the scheduling request, the mobile phone will send HARQ feedback and the scheduling request at two time domain positions respectively, that is, two uplink signals will be sent. If the solution in this application is adopted, under the condition of meeting the requirements, the mobile phone can combine the information of the scheduling request and HARQ feedback and send it through PUCCH, and the mobile phone only sends one uplink signal. Thus, the effect of power saving of the mobile phone is achieved.

[0177] Based on the above embodiments, some specific examples are used to elaborate in detail on the scheduling request transmission method. In the following examples, the terminal device is a UE, the network device is a base station, and the scheduling request is an SR for illustration.

[0178] In the following examples, this solution is used to implement how to reduce the number of uplink transmissions of the UE, thereby reducing the uplink transmission power consumption of the UE.

[0179] Specifically, in the following examples, in order to reduce the number of UE uplink transmissions, the UE can predict that there are other uplink transmissions near the PUCCH of the SR (i.e., the first uplink channel involved in the above embodiments) (which can also be referred to as uplink resources or uplink signals, etc.), and merge the SR into other uplink transmissions for sending, thereby reducing the number of uplink signal transmissions (i.e., the number of uplink transmissions) and reducing the uplink transmission power consumption. Further, this solution can be described in the following three aspects: In the first aspect, under what circumstances does the UE merge and send the SR, that is, how to define "near the PUCCH"; in the second aspect, how the SR is merged into other uplink transmissions for sending; in the third aspect, how to avoid affecting the transmission performance.

[0180] In the first aspect, under what circumstances does the UE merge and send the SR, that is, how to define "near the PUCCH":

[0181] Other uplink transmissions can include any one of the following: PUCCH carrying HARQ feedback (such as HARQ-ACK, and hereinafter HARQ feedback will be described by taking HARQ-ACK as an example), PUCCH carrying CSI report (report), PUSCH without UL-SCH (that is, PUSCH without uplink data).

[0182] Further, when there is also an SR resource in the time slot where other uplink transmissions are located, the SR can be merged into other uplink transmissions for sending.

[0183] The vicinity of the PUCCH of the SR can be defined as: within a certain time range before and after the PUCCH (i.e., the first time domain range involved above), which can be represented by two time windows.

[0184] In the second aspect, how the SR is merged into other uplink transmissions for sending:

[0185] Method 1: Some methods in current embodiments can be adopted, which are applicable to some scenarios, such as the scenario where the PF 0 / 2 / 3 / 4 information of HARQ-ACK is merged and sent with the SR, or the scenario where CSI in the PUCCH is merged and sent with the SR.

[0186] Method 2: The method proposed in this application is adopted for combined transmission, which can be applicable to scenarios other than those in Method 1, such as the scenario where the PF 1 information of HARQ-ACK is merged and sent with the SR, or the scenario where CSI included in the PUSCH without uplink data is merged and sent with the SR.

[0187] In the third aspect, how to avoid affecting the transmission performance:

[0188] Possible impact: When SR is merged into other uplink transmissions, the energy per bit will decrease, and the coverage performance will be affected.

[0189] Solution 1: Introduce an RSRP threshold. When the RSRP reported by the UE to the base station is higher than this RSRP threshold, it is considered that the coverage of the UE is not limited. Only in this case can the combined transmission method in this application be adopted; otherwise, the currently common method is used.

[0190] Solution 2: Enhance the power control of the uplink transmission.

[0191] For example, when SR is merged into other uplink transmissions for sending, the transmit power of other uplink transmissions is increased by X dB, and the value of X can be predefined, configured by the base station, or indicated by DCI.

[0192] For another example, when SR is merged into other uplink transmissions for sending, the final transmit power of other uplink transmissions can be determined by the PUCCH transmit power of the original SR and the transmit power of the original other uplink transmissions, such as adding the powers, or multiplying the sum of the powers by a coefficient, etc.

[0193] In the first specific example, the uplink transmission (i.e., the first uplink channel involved in the above embodiment) can include any one of the following: PUCCH carrying HARQ-ACK, PUCCH carrying CSI report, PUSCH without UL-SCH. That is to say, in this example, SR can only be merged with the above three uplink transmissions for sending together.

[0194] The vicinity of the PUCCH of SR can be defined as within the time window 1 (window 1) (i.e., the first time window involved in the above embodiment) and / or time window 2 (window 2) (i.e., the second time window involved in the above embodiment) as shown (i.e., within the first time domain range involved in the above embodiment), where: Figure 14 The definition of time window 1 can be: the starting point is "SR trigger received by the PHY layer from the MAC layer" (i.e., the starting moment is the moment when the PHY layer of the UE receives the SR trigger from the MAC layer of the UE), and the ending point is "SR occasion" (the SR occasion is the PUCCH resource of SR) (i.e., the ending moment is the time domain position of the PUCCH containing SR); or, the ending point is "SR occasion", and the length is length 1 (length 1) (i.e., the first time domain length involved in the above embodiment), where length 1 can be predefined or configured by the base station.

[0195] The definition of time window 1 can be: the starting point is "SR trigger received by the PHY layer from the MAC layer" (i.e., the starting moment is the moment when the PHY layer of the UE receives the SR trigger from the MAC layer of the UE), and the ending point is "SR occasion" (the SR occasion is the PUCCH resource of SR) (i.e., the ending moment is the time domain position of the PUCCH containing SR); or, the ending point is "SR occasion", and the length is length 1 (length 1) (i.e., the first time domain length involved in the above embodiment), where length 1 can be predefined or configured by the base station.

[0196] The starting point of time window 2 is the "SR timing", and the length of time window 2 is length 2, where length 2 can be predefined or configured by the base station.

[0197] That is, as long as there is other uplink transmission within the range of time window 1 and / or time window 2, the SR information can be merged into the other uplink transmission and sent together.

[0198] Optionally, if there are multiple uplink transmissions in time window 1 and / or time window 2, the one with the earliest occurrence time (i.e., the earliest time domain position) or the one closest to the SR timing (i.e., the one with the smallest interval between the time domain positions of the multiple uplink channels and the time domain position of the PUCCH containing the scheduling request in the above embodiments) can be selected to merge the SR. This can determine a unique position for sending the SR and avoid carrying redundant bits in each other uplink transmission.

[0199] Adopting this first specific example can reduce the number of transmissions by the UE, thereby reducing the UE power consumption.

[0200] In the second specific example, the determination of the existence of other uplink transmissions near the PUCCH of the SR is described in detail. Specifically, there are the following three possible situations:

[0201] (1) If the uplink transmission is a PUCCH carrying HARQ-ACK, or a PUCCH carrying a CSI report, or a PUSCH without carrying a UL-SCH, and the uplink transmission falls within time window 1, then the SR can be merged into this uplink transmission for sending. In this example, the above types of uplink transmissions can all carry SR information in some way, and the above types of uplink transmissions are before the PUCCH of the SR and after the UE's MAC triggers the PHY to send the SR (i.e., the moment when the PHY layer of the terminal device in the above embodiments receives the scheduling request triggered by the MAC layer of the terminal device) (i.e., within time window 1), as Figure 15 shown. Therefore, the UE can determine the existence of these uplink transmissions before the PUCCH of the SR and can perform merged transmission.

[0202] (2) If the uplink transmission is a PUCCH carrying a CSI report and the uplink transmission falls within time window 2, then the SR can be merged into this uplink transmission for sending. In this example, since the PUCCH carrying the CSI report is semi-statically configured, the UE can pre-determine that there will definitely be a PUCCH carrying the CSI report available within a certain range after the PUCCH of the SR (i.e., the second time domain length involved in the above embodiments), and thus can successfully merge the SR into the PUCCH carrying the CSI report for sending, for example Figure 16As shown. If the UE cannot determine whether there must be available uplink transmissions in Time Window 2, to avoid the inability to send the SR due to lack of available resources, the UE can only send the SR using the PUCCH for the SR, and thus cannot achieve the purpose of UE energy saving.

[0203] (3) If the uplink transmission is a PUSCH without carrying UL-SCH or a PUCCH carrying HARQ-ACK, the uplink transmission falls within Time Window 2, and the DCI scheduling the PUSCH or PUCCH is before the PUCCH for the SR, then the SR can be combined into this uplink transmission for transmission. For example Figure 17 As shown. In this example, although the uplink transmission is not semi-statically configured but dynamically scheduled, the DCI scheduling this uplink transmission is before the PUCCH for the SR. That is to say, before the PUCCH for the SR, the UE can determine that there may be available uplink transmissions in the subsequent Time Window 2. Therefore, the UE can combine the SR into this uplink transmission. If there is no available uplink transmission, then the UE uses the PUCCH for the SR to send the SR.

[0204] In addition, when any one of the above three situations is met, it can be further specified whether combined transmission is possible. For example, as long as there is an uplink transmission, it can be combined, as Figure 18 shown.

[0205] For another example, the time slot where other uplink transmissions are located must have an SR opportunity for combined transmission, as Figure 19 shown.

[0206] In any scenario, it can be determined by the MAC layer of the UE whether combined transmission is possible, and the PHY layer of the UE is instructed on which SR resource to transmit the SR. The PHY of the UE then multiplexes and transmits the SR according to the currently common method; or the MAC layer of the UE only indicates an SR opportunity, and it is determined by the PHY layer of the UE whether combination is possible and the SR is transmitted.

[0207] Using the second specific example, a method for clearly determining that there are other uplink transmissions near the PUCCH for the SR can be obtained.

[0208] In the third specific example, it is specifically introduced how the SR is combined into other uplink transmissions for sending.

[0209] For example Figure 2In some current embodiments shown in Example 1, when SR overlaps with other uplink transmissions, the practices corresponding to the combined methods shown in bold in Table 1 can all be applied to this example. That is, when it is determined according to the first specific example or the second specific example above that SR can be merged into PUCCH format (PF) 0 / 2 / 3 / 4 carrying HARQ-ACK, or when SR can be merged into PF 2 / 3 / 4 carrying CSI reports, the methods in the current embodiments can be adopted. However, the combined methods corresponding to the non-bold parts in Table 1 above may require certain enhancements. Specifically, there can be the following scenarios:

[0210] Scenario 1: If the PUCCH resource of SR is format 0 and SR is to be merged into PF1 carrying HARQ-ACK for transmission, there are the following possible practices:

[0211] Method 1: This combination cannot be merged for transmission, that is, in this scenario, SR cannot be merged and sent.

[0212] Method 2: If HARQ-ACK has only 1 bit, the SR information is carried through the cyclic shift of PUCCH (that is, the UE concatenates SR and HARQ-ACK, then maps the concatenated information to a second cyclic shift value and sends it to the network device according to the second cyclic shift value). That is, if there is no SR, then m CS = 0 / 6, if there is SR, then m CS = 3 / 9;

[0213] If HARQ-ACK has 2 bits, there can be the following two methods:

[0214] Method 2-1: SR cannot be merged into this PUCCH for transmission.

[0215] Method 2-2: The 3-bit information composed of SR and HARQ-ACK can generate an 8PSK symbol, which is then multiplied by a sequence (sequence). For example, refer to Formula 1 involved in the above embodiments, which will not be repeated here. In the current embodiments, d(0) is a complex symbol generated by at most 2 bits of information. In Method 2-2 here, d(0) is an 8PSK symbol.

[0216] Scenario 2: If the PUCCH resource of SR is format 1 and SR is to be merged into PF1 carrying HARQ-ACK for transmission, there can be the following practices:

[0217] If there is a PUCCH format 1 resource for SR transmission in the time slot where the PUCCH carrying HARQ-ACK is located, the UE uses the channel selection method (the same as the channel selection method in the current embodiment); otherwise, they cannot be combined.

[0218] Scenario 3: If the SR is to be combined and transmitted in the PUSCH that does not carry the UL-SCH, the following methods are available:

[0219] Method 1: The SR can be multiplexed into the PUSCH, that is, the SR information bits are concatenated with the uplink data bits, and then modulated and mapped together onto the physical resources of the PUSCH;

[0220] Method 2: The SR can puncture the PUSCH, that is, the UE modulates the SR separately. After the PUSCH is generated, the modulation symbols of some REs occupied by the PUSCH are replaced with the symbols after the SR is modulated.

[0221] Method 3: In this scenario, the SR cannot be combined and transmitted.

[0222] By adopting this third specific implementation manner, it can be clear how the UE combines and transmits the SR.

[0223] In the fourth specific example, the above specific example is further supplemented.

[0224] Specifically, the base station can send configuration information to the UE (for example, through RRC signaling (message) or MAC CE) (that is, the first message involved in the above embodiment). This configuration information enables this function (that is, the function of combining the SR and the uplink transmission, that is, the function of combining the scheduling request and the information included in the first uplink channel involved in the above embodiment). After the UE is configured with this function, when the relative positions of the PUCCH or PUSCH meet the conditions, both the base station and the UE can determine that the two (that is, the SR and the information in the PUCCH or PUSCH) can be combined and transmitted. An example process can be as Figure 20 shown.

[0225] On the other hand, the UE can send auxiliary information (that is, the second message involved in the above embodiment) to request or trigger the enabling (that is, activation) or disabling of this function. An example process can be as Figure 21 shown.

[0226] In another case, after the base station sends configuration information to the UE, it also needs to send dynamic indication information (such as DCI) (i.e., the third message involved in the above embodiment) to the UE to indicate whether the UE can perform combined transmission (i.e., whether to enable this function). For example, indication information is added to the DCI for scheduling PUSCH or PUCCH to indicate whether SR can be combined with the current PUSCH or PUCCH for joint transmission. An example process can be as Figure 22 shown.

[0227] Furthermore, in the above case, in combination with the UE's request, the opening or closing of this function can be requested or triggered. An example process can be as Figure 23 shown.

[0228] In the fifth specific example, this example is used to avoid the impact on transmission performance. When the PUCCH of SR is transmitted separately from other uplink transmissions, the UE needs to send signals twice. Although the transmission power consumption of the UE is relatively large, the energy per bit in the two signals is also relatively high, which can resist stronger noise and the signal coverage range is relatively large. When SR is transmitted jointly with other uplink transmissions, the energy per bit for both SR and the information in other uplink transmissions will be relatively low, the signal coverage range may be limited, and the signal transmission reliability will decrease. To solve the problem of signal transmission reliability, this example proposes several enhanced methods.

[0229] Method 1: Introduce a reference signal received power (RSRP) threshold. When the RSRP reported by the UE to the base station is higher than this RSRP threshold, it can be considered that the coverage of the UE is not limited. Only in this case can the combined transmission method in this application be adopted; otherwise, the commonly used method is adopted. The principle is that the UE calculates an RSRP value based on the power of the reference signal sent by the base station it receives. The larger this RSRP value is, the closer the UE is to the base station. An RSRP threshold is equivalent to an equivalent distance threshold from the base station to the UE. When the RSRP received by the UE is higher than this threshold, it means that the UE is close enough to the base station. At this time, even if the UE combines SR with other uplink transmissions for transmission, it can ensure that the signal can be correctly transmitted. It should be noted that in this method, the condition is "the RSRP reported by the UE to the base station" because only when both the UE and the base station know whether SR is combined with other uplink transmissions can the correct transmission be achieved. Therefore, both the UE and the base station must know whether the RSRP condition is met.

[0230] Method 2: Enhance the power control method. In some current embodiments, the transmission power of the uplink signal can be determined based on one or more of the path loss value estimated by the UE, the transmission parameters configured by the base station, or the TPC (Transmit Power Control) command indicated by the base station in the DCI. Without any enhancement, the UE will determine the transmission power of the uplink signal according to the method in the current embodiments. If it is desired to improve the transmission reliability of the combined signal, it can be considered to increase the transmission power of the combined signal when the SR and the uplink transmission are combined for transmission, so as to increase the energy per bit on average. Specifically, the following possible methods can be included:

[0231] Example 1: When the SR is combined and transmitted in other uplink transmissions, the transmission power of other uplink transmissions is increased by X dB, and the value of X can be predefined, configured by the base station, or indicated by the base station through the DCI.

[0232] Example 2: When the SR is combined and transmitted in other uplink transmissions, the final transmission power of other uplink transmissions can be determined by the original PUCCH transmission power of the SR (i.e., the original transmission power of the PUCCH) and the original transmission power of other uplink transmissions (i.e., the original transmission power of the first channel), for example, the two powers are added together, or the sum of the two powers is multiplied by a coefficient, etc. For example, if the original transmission power of the PUCCH of the SR is 16 dBm and the SR is combined and transmitted in the PUSCH, the original transmission power of the PUSCH is 16 dBm. After the SR is combined into the PUSCH, the transmission power of the PUSCH can be the sum of the two, i.e., 19 dBm; or the sum of the two is multiplied by a coefficient, which is 18 dBm, etc.

[0233] This fifth specific example further considers the feasibility of the combined transmission of the SR and other uplink transmissions, and minimizes the impact of the combined transmission on the transmission performance.

[0234] Based on the above embodiments, the embodiments of the present application further provide a communication device. Refer to Figure 24 As shown, the device 2400 may include a transceiver unit 2401 and a processing unit 2402. Among them, the transceiver unit 2401 is used for the communication device 2400 to transmit information (messages or data), that is, to receive information (messages or data) or send information (messages or data), and the processing unit 2402 is used to control and manage the actions of the communication device 2400. The processing unit 2402 can also control the steps executed by the transceiver unit 2401.

[0235] Exemplarily, the communication device 2400 may specifically be the terminal device in the above embodiments, the processor in the terminal device, or a chip or chip system, or a functional module, etc.; alternatively, the communication device 2400 may specifically be the network device in the above embodiments, the processor in the network device, or a chip or chip system, or a functional module, etc.

[0236] In one embodiment, when the communication device 2400 is used to implement the functions of the terminal device in the above Figure 2 embodiment, the transceiver unit 2401 may implement Figure 2 the transceiver operations (or transmission operations) performed by the terminal device in the embodiment shown; the processing unit 2402 may implement Figure 2 other operations performed by the terminal device in the embodiment shown except for the transceiver operations. For specific relevant descriptions, reference may be made to the relevant descriptions in the above Figure 2 embodiment shown, and details are not described herein again.

[0237] In another embodiment, when the communication device 2400 is used to implement the functions of the network device in the above Figure 2 embodiment, the transceiver unit 2401 may implement Figure 2 the transceiver operations performed by the network device in the embodiment shown; the processing unit 2402 may implement Figure 2 other operations performed by the network device in the embodiment shown except for the transceiver operations. For specific relevant descriptions, reference may be made to the relevant descriptions in the above Figure 2 embodiment shown, and details are not described herein again.

[0238] It should be noted that the division of units in the embodiments of the present application is illustrative, merely a logical function division, and there may be other division methods in actual implementation. In the embodiments of the present application, each functional unit may be integrated in a processing unit, or each unit may exist physically alone, or two or more units may be integrated in one unit. The above integrated units may be implemented in the form of hardware or in the form of software functional units.

[0239] When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that makes a contribution, or all or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical discs that can store program codes.

[0240] Based on the above embodiments, the embodiments of this application also provide a communication device. Refer to Figure 25 As shown, the communication device 2500 may include a transceiver 2501 and a processor 2502. Optionally, the communication device 2500 may further include a memory 2503. Among them, the memory 2503 may be disposed inside the communication device 2500 or outside the communication device 2500. Among them, the processor 2502 may control the transceiver 2501 to receive and send data (information or messages).

[0241] Specifically, the processor 2502 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP. The processor 2502 may further include a hardware chip. The above hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The above PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0242] Among them, the transceiver 2501, the processor 2502, and the memory 2503 are interconnected. Optionally, the transceiver 2501, the processor 2502, and the memory 2503 are interconnected via a bus 2504; the bus 2504 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 25 only a thick line is used to represent it in Figure 25 , but it does not mean that there is only one bus or one type of bus.

[0243] In an alternative embodiment, the memory 2503 is used to store programs, etc. Specifically, the program may include program code, and the program code includes computer operation instructions. The memory 2503 may include a RAM, and may also include a non-volatile memory, such as one or more disk memories. The processor 2502 executes the application programs stored in the memory 2503 to implement the above functions, thereby implementing the functions of the communication device 2500.

[0244] Exemplarily, the communication device 2500 may be the terminal device in the above embodiments; it may also be the network device in the above embodiments.

[0245] In one embodiment, when the communication device 2500 implements Figure 2 the functions of the terminal device in the embodiments shown, the transceiver 2501 can implement Figure 2 the transceiver operations (or transmission operations) performed by the terminal device in the embodiments shown; the processor 2502 can implement Figure 2 the other operations performed by the terminal device in the embodiments shown except for the transceiver operations. For specific relevant descriptions, reference can be made to the relevant descriptions in the above Figure 2 embodiments shown, and details are not described herein again.

[0246] In one embodiment, when the communication device 2500 implements Figure 2 the functions of the network device in the embodiments shown, the transceiver 2501 can implement Figure 2 the transceiver operations performed by the network device in the embodiments shown; the processor 2502 can implement Figure 2 the other operations performed by the network device in the embodiments shown except for the transceiver operations. For specific relevant descriptions, reference can be made to the relevant descriptions in the above Figure 2The relevant descriptions in the illustrated embodiments will not be elaborated here.

[0247] Based on the above embodiments, an embodiment of the present application further provides a communication system, which may include a terminal device, a network device, etc.

[0248] An embodiment of the present application further provides a computer-readable storage medium for storing a computer program, which when executed by a computer, enables the computer to implement the transmission method of the scheduling request provided in the above method embodiment.

[0249] An embodiment of the present application further provides a computer program product for storing a computer program, which when executed by a computer, enables the computer to implement the transmission method of the scheduling request provided in the above method embodiment.

[0250] An embodiment of the present application further provides a chip including a processor, the processor being coupled to a memory and configured to call a program in the memory to enable the chip to implement the transmission method of the scheduling request provided in the above method embodiment.

[0251] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memory, CD-ROM, optical memory, etc.) containing computer-usable program code.

[0252] The present application is described with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, as well as the combination of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing devices generate means for implementing the functions specified in Figure 1 one process or multiple processes and / or blocks Figure 1 one block or multiple blocks.

[0253] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the computer-readable memory generate a manufactured article including instruction means, the instruction means implementing the functions in the processFigure 1 one process or multiple processes and / or blocks Figure 1 the functions specified in one block or multiple blocks.

[0254] These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process. Thus, the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one process Figure 1 one process or multiple processes and / or blocks Figure 1 or the functions specified in multiple blocks.

[0255] Obviously, those skilled in the art can make various changes and modifications to this application without departing from the scope of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalent technologies, this application is also intended to include these changes and modifications.

Claims

1. A method for transmitting a scheduling request, characterized in that Including: The terminal device determines that there is a first uplink channel within a first time domain range; wherein, the first time domain range is related to the time domain position of a Physical Uplink Control Channel (PUCCH) including a scheduling request, and the first uplink channel is any one of the following: a PUCCH including Hybrid Automatic Repeat reQuest (HARQ) feedback, a PUCCH including Channel State Information (CSI) report, or a Physical Uplink Shared Channel (PUSCH); The terminal device combines the scheduling request with the information included in the first uplink channel to obtain first information; The terminal device sends the first information to the network device; Wherein, the first time domain range is a first time window and / or a second time window; Wherein, the start time of the first time window is the time triggered by the terminal device's Physical (PHY) layer receiving the scheduling request from the terminal device's Medium Access Control (MAC) layer, and the end time is the time domain position of the PUCCH including the scheduling request; or, the end time of the first time window is the time domain position of the PUCCH including the scheduling request, and the time domain length is a first time domain length; The start time of the second time window is the time domain position of the PUCCH including the scheduling request, and the time domain length is a second time domain length.

2. The method according to claim 1, characterized in that When there are multiple uplink channels within the first time domain range, the first uplink channel is the uplink channel with the earliest time domain position among the multiple uplink channels, or the first uplink channel is the uplink channel with the smallest interval between the time domain position and the time domain position of the PUCCH including the scheduling request among the multiple uplink channels.

3. The method according to any one of claims 1-2, characterized in that, The time slot where the first uplink channel is located includes a scheduling request occasion.

4. The method according to any one of claims 1-2, characterized in that, When the format of the PUCCH including the scheduling request is format 0 or format 1, and the first uplink channel is the PUCCH including HARQ feedback and the format of the PUCCH including HARQ feedback is format 0, The terminal device combines the scheduling request with the information included in the first uplink channel to obtain first information, including: The terminal device concatenates the scheduling request with the HARQ feedback to obtain the first information; The terminal device sends the first information to the network device, including: The terminal device maps the first information to a first cyclic shift value, and sends the first information to the network device according to the first cyclic shift value.

5. The method according to any one of claims 1-2, characterized in that When the format of the PUCCH including the scheduling request is format 0 or format 1, and the first uplink channel is the PUCCH including HARQ feedback and the format of the PUCCH including HARQ feedback is format 2, format 3, or format 4, The terminal device combines the scheduling request with the information included in the first uplink channel to obtain first information, including: The terminal device concatenates the scheduling request and the HARQ feedback to obtain the first information; The terminal device sends the first information to the network device, including: The terminal device sends the first information to the network device through the first uplink channel.

6. The method according to any one of claims 1-2, characterized in that, When the format of the PUCCH carrying the scheduling request is format 0 or format 1, the first uplink channel is the PUCCH carrying the CSI report, and the format of the PUCCH carrying the CSI report is format 2, format 3, or format 4, the terminal device combines the scheduling request with the information included in the first uplink channel to obtain first information, including: the terminal device concatenates the scheduling request and the CSI report to obtain the first information; the terminal device sends the first information to the network device, including: the terminal device sends the first information to the network device through the first uplink channel.

7. The method according to any one of claims 1-2, characterized in that, When the format of the PUCCH carrying the scheduling request is format 0, the first uplink channel is the PUCCH carrying the HARQ feedback, and the format of the PUCCH carrying the HARQ feedback is format 1, the terminal device combines the scheduling request with the information included in the first uplink channel to obtain first information, including: the terminal device concatenates the scheduling request and the HARQ feedback to obtain the first information; the terminal device sends the first information to the network device, including: the terminal device maps the first information to a second cyclic shift value and sends the first information to the network device according to the second cyclic shift value.

8. The method according to any one of claims 1-2, characterized in that, When the format of the PUCCH carrying the scheduling request is format 1, the first uplink channel is the PUCCH carrying the HARQ feedback, and the format of the PUCCH carrying the HARQ feedback is format 1, the terminal device sends the first information to the network device, including: when it is determined that there is a resource of PUCCH format 1 for transmitting the scheduling request in the time domain position of the first uplink channel, the terminal device sends the first information to the network device by means of channel selection.

9. The method according to any one of claims 1-2, characterized in that, When the format of the PUCCH carrying the scheduling request is format 0 or format 1, and the first uplink channel is the PUSCH, the terminal device combines the scheduling request with the information included in the first uplink channel to obtain first information, including: the terminal device concatenates the scheduling request and the information included in the PUSCH to obtain the first information.

10. The method according to any one of claims 1-2, characterized in that, When the format of the PUCCH carrying the scheduling request is format 0 or format 1, and the first uplink channel is the PUSCH, the terminal device combines the scheduling request with the information included in the first uplink channel to obtain first information, including: the terminal device punctures the PUSCH and maps the scheduling request to the punctured position of the PUSCH to obtain the first information.

11. The method according to any one of claims 1-2, characterized in that, Before the terminal device combines the scheduling request with the information included in the first uplink channel to obtain first information, the method further includes: After the terminal device determines that it has received a reference signal from the network device, the received reference signal power (RSRP) sent to the network device is greater than the RSRP threshold, where the RSRP is determined by the terminal device based on the reference signal.

12. The method according to any one of claims 1-2, characterized in that, The terminal device sending the first information to the network device includes: The terminal device sends the first information to the network device with a first transmission power; wherein, the first transmission power is greater than the original transmission power of the first uplink channel; or the first transmission power is determined based on the original transmission power of the first uplink channel and the original transmission power of the physical uplink control channel (PUCCH) including the scheduling request.

13. A method for transmitting a scheduling request, characterized in that including: The network device determines that there is a first uplink channel within a first time domain range; wherein, the first time domain range is related to the time domain position of the physical uplink control channel (PUCCH) including the scheduling request, and the first uplink channel is any one of the following: PUCCH including hybrid automatic repeat request (HARQ) feedback, PUCCH including channel state information (CSI) report, or physical uplink shared channel (PUSCH). The network device receives first information from the terminal device, where the first information is obtained by the terminal device combining the scheduling request with the information included in the first uplink channel. wherein, the first time domain range is the first time window and / or the second time window; wherein, the start time of the first time window is the moment triggered by the scheduling request received by the physical (PHY) layer of the terminal device from the medium access control (MAC) layer of the terminal device, and the end time is the start position of the time domain position of the PUCCH including the scheduling request; or, the end time of the first time window is the start position of the time domain position of the PUCCH including the scheduling request, and the time domain length is the first time domain length; The start time of the second time window is the time domain position of the PUCCH including the scheduling request, and the time domain length is the second time domain length.

14. The method according to claim 13, wherein When there are multiple uplink channels within the first time domain range, the first uplink channel is the uplink channel with the earliest time domain position among the multiple uplink channels, or, the first uplink channel is the uplink channel with the smallest interval between the time domain position and the time domain position of the PUCCH including the scheduling request among the multiple uplink channels.

15. The method according to any one of claims 13-14, characterized in that, The time slot where the first uplink channel is located includes a scheduling request opportunity.

16. The method according to any one of claims 13-14, characterized in that, When the format of the PUCCH including the scheduling request is format 0 or format 1, and the first uplink channel is the PUCCH including HARQ feedback and the format of the PUCCH including HARQ feedback is format 0, the first information is obtained by the terminal device concatenating the scheduling request and the HARQ feedback. The network device receiving the first information from the terminal device includes: The network device receives the first information sent by the terminal device according to a first cyclic shift value, where the first cyclic shift value is mapped by the terminal device from the first information.

17. The method according to any one of claims 13-14, characterized in that, When the format of the PUCCH including the scheduling request is Format 0 or Format 1, the first uplink channel is the PUCCH including HARQ feedback and the format of the PUCCH including HARQ feedback is Format 2, Format 3, or Format 4, the first information is obtained by the terminal device concatenating the scheduling request and the HARQ feedback; The network device receiving the first information from the terminal device includes: The network device receives the first information sent by the terminal device through the first uplink channel.

18. The method according to any one of claims 13-14, characterized in that, When the format of the PUCCH including the scheduling request is Format 0 or Format 1, the first uplink channel is the PUCCH including CSI report and the format of the PUCCH including CSI report is Format 2, Format 3, or Format 4, the first information is obtained by the terminal device concatenating the scheduling request and the CSI report; The network device receiving the first information from the terminal device includes: The network device receives the first information sent by the terminal device through the first uplink channel.

19. The method according to any one of claims 13-14, characterized in that When the format of the PUCCH including the scheduling request is Format 0, the first uplink channel is the PUCCH including HARQ feedback and the format of the PUCCH including HARQ feedback is Format 1, the first information is obtained by the terminal device concatenating the scheduling request and the HARQ feedback; The network device receiving the first information from the terminal device includes: The network device receives the first information sent by the terminal device according to a second cyclic shift value, and the second cyclic shift value is obtained by the terminal device mapping the first information.

20. The method according to any one of claims 13-14, characterized in that, When the format of the PUCCH including the scheduling request is Format 1, the first uplink channel is the PUCCH including HARQ feedback and the format of the PUCCH including HARQ feedback is Format 1, the network device receiving the first information from the terminal device includes: When there is a resource for transmitting PUCCH Format 1 of the scheduling request in the time domain position of the first uplink channel, receiving the first information sent by the terminal device in a channel selection manner.

21. The method according to any one of claims 13-14, characterized in that, When the format of the PUCCH including the scheduling request is Format 0 or Format 1, and the first uplink channel is the PUSCH, the first information is obtained by the terminal device concatenating the scheduling request and the information included in the PUSCH.

22. The method according to any one of claims 13-14, characterized in that, When the format of the PUCCH including the scheduling request is Format 0 or Format 1, and the first uplink channel is the PUSCH, the first information is obtained by the terminal device puncturing the PUSCH and mapping the scheduling request to the punctured position of the PUSCH.

23. The method according to any one of claims 13-14, characterized in that, Before the network device receives the first information from the terminal device, the method further includes: The network device determines that the reference signal received power (RSRP) from the terminal device is greater than the RSRP threshold, where the RSRP is sent by the terminal device after receiving the reference signal from the network device, and the RSRP is determined by the terminal device based on the reference signal.

24. A terminal device, characterized in that, Comprising a memory and a processor, wherein: The memory is used for storing computer instructions; The processor is coupled to the memory and is used for calling the computer instructions in the memory to cause the terminal device to execute the method according to any one of claims 1-12.

25. A network device, characterized in that, Comprising a memory and a processor, wherein: The memory is used for storing computer instructions; The processor, coupled to the memory, is used for calling the computer instructions in the memory to cause the network device to execute the method according to any one of claims 13-23.

26. A computer-readable storage medium, characterized in that, Computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are called by the computer, they are used to cause the computer to execute the method according to any one of claims 1-23 above.

Images