Patent Description:
Compared with previous generations of mobile communication systems, a <NUM> communication system imposes higher requirements on a transmission rate, a latency, power consumption, and the like. Ultra-reliable and low-latency communication (ultra-reliable and low-latency communication, URLLC) is one of typical services of <NUM> communication, and specific requirements of the ultra-reliable and low-latency communication include: Data transmission reliability reaches <NUM>%, a transmission latency is less than <NUM>, and instruction overheads is reduced as much as possible while requirements for high reliability and a low latency are satisfied. Therefore, how to ensure the reliability and the low latency of URLLC becomes a problem of great concern in the art.

To support the URLLC service, carrier aggregation (carrier aggregation, CA) may be performed on frequency range (frequency range, FR) <NUM> and FR2, to increase a system capacity. In a CA scenario, a carrier on which uplink information is sent is indicated by a network device in advance. However, if a terminal device cannot send the uplink information in time by using an uplink resource indicated in advance, it is quite difficult to ensure the reliability and the low latency of the URLLC service.

<CIT> relates to a method for wireless communication. A user equipment receives downlink control information from an evolved NodeB that includes an uplink grant of resources. The downlink control information is configured to convey a modulation coding scheme table reference. The user equipment identifies the modulation coding scheme table reference from a plurality of modulation coding scheme tables based on the modulation coding scheme table reference conveyed in the downlink control information. The modulation coding scheme table defines modulation and coding to be utilized for uplink transmissions on the resources granted in the uplink grant. The user equipment sends one or more uplink transmissions modulated and coded according to the modulation coding scheme table.

<CIT> relates to a communication system in which a base station apparatus and a user equipment communicate on multiple component carriers. The multiple component carriers comprise a primary component carrier and a non-primary component carrier. The base station apparatus transmits to the user equipment four indices for physical uplink control channel resource using higher layer signaling. The base station further transmits to the user equipment an index indicator using transmission power control command for a physical uplink control channel field. The user equipment determines an index among the four indices according to the index indicator. The user equipment transmits to the base station apparatus HARQ-ACK/NACK using the physical uplink control channel resource the index. A transmission power control command for the physical uplink control channel field is included in a downlink control information format to schedule a physical downlink shared channel on the non-primary component carrier.

<CIT> relates to a method of transmitting an uplink signal by a user equipment in a wireless communication system. The method includes receiving downlink control information through a physical downlink control signal regarding a semi-persistent scheduling physical uplink shared channel. Further, a semi-persistent scheduling physical uplink shared channel signal is periodically transmitted based on the downlink control information. The periodic transmission of the semi-persistent scheduling physical uplink shared channel signal based on the downlink control information includes a state in which the semi-persistent scheduling physical uplink shared channel signal is subslot-based, a demodulation reference signal pattern field included in the downlink control information is set to a first value and a simultaneous transmission of a physical uplink control channel. The physical uplink shared channel is configured for the user equipment. The user equipment transmits uplink control information through the semi-persistent scheduling physical uplink shared channel signal, without simultaneously transmitting a physical uplink control channel signal.

<CIT> relates to systems and methods for triggering channel state information reporting on a physical uplink control channel. A network node transmits a downlink-related control message including a channel state information request field and a physical uplink control channel resource indicator. a wireless device receives the control message and determines to trigger a channel state information report in accordance with the channel state information request field and the physical uplink control channel resource indicator.

The object of the present invention is to provide a resource determining method and an apparatus, to reduce a latency of sending uplink information. This object is solved by the attached independent claims and further advantageous embodiments and improvements of the invention are listed in the dependent claims. Hereinafter, expressions like ". aspect according to the invention" or "according to the invention" or similar relate to technical teaching of the broadest embodiment as claimed with the independent claims. Expressions like "implementation", "scenario" or "optionally" or "optional design" or "may", relate to claimed embodiments, and expressions like "examples" or "according to an example" or "not claimed" relate to technical teaching of further not claimed embodiments which, however, contribute to the understanding of the claimed invention. The scope of the present invention is defined by the scope of the appended claims.

Aspects of the present invention are defined in the independent claims and further detailed in the dependent claims.

To make the objectives, technical solutions, and advantages of this application clearer, the following clearly and completely describes the technical solutions in this application with reference to the accompanying drawings in this application. Obviously, the described embodiments are a part rather than all of the embodiments of this application. The scope of the present invention is defined by the scope of the appended claims.

In the specification, embodiments, claims, and accompanying drawings of this application, the terms "first", "second", and the like are merely intended for distinguishing and description, and shall not be understood as an indication or implication of relative importance or an indication or implication of an order. Moreover, the terms "include", "have" and any variant thereof mean to cover non-exclusive inclusion, for example, include a series of steps or units. A method, a system, a product, or a device is not necessarily limited to those steps or units that are expressly listed, but may include other steps or units not expressly listed or inherent to such a procedure, a method, a product, or a device.

It should be understood that, in this application, "at least one" means one or more, and "a plurality of" means two or more. The term "and/or" is used to describe an association relationship between associated objects and represents that three relationships may exist. For example, "A and/or B" may represent the following three cases: Only A exists, only B exists, and both A and B exist, where A and B may be singular or plural. The character "/" generally indicates an "or" relationship between the associated objects. "At least one of the following" or a similar expression thereof means any combination of these items, including a single item or any combination of a plurality of items. For example, at least one of a, b, or c may represent a, b, c, "a and b", "a and c", "b and c", or "a, b, and c", where a, b, and c may be singular or plural.

For different bands, communication requirements may be different. Different communication requirements may be identified by using different frequency ranges FRs, and each FR may cover one or more bands. For example, a plurality of bands below a <NUM> band (sub-<NUM>) may be referred to as FR1, and millimeter wave bands (mmwave bands) may be referred to as FR2. Differences between FR1 and FR2 may be as follows:.

Frequency range: A frequency range of FR1 is <NUM> to <NUM>. After Release-<NUM> (Rel-<NUM>) of a communication protocol, a lowest frequency limit of FR1 may be extended to <NUM>, and a highest frequency limit may be extended to <NUM>. A frequency range of FR2 is <NUM> to <NUM>.

Channel bandwidth: A maximum channel bandwidth of FR1 may be <NUM>, and a maximum channel bandwidth of FR2 may be <NUM>. A channel bandwidth of a network device is greater than or equal to a channel bandwidth of a terminal device, and the channel bandwidth of the terminal device may be located in any part of the channel bandwidth of the network device. When there are a plurality of channel bandwidths of the network device, the channel bandwidth of the terminal device may cross a boundary of the channel bandwidths of the network device.

Subcarrier spacing (SCS): SCSs of FR1 include <NUM>, <NUM>, and <NUM>, and SCSs in sub-<NUM> include <NUM> and <NUM>. SCSs of FR2 include <NUM> and <NUM>.

Uplink and downlink transmission: In FR1, there may be a time division duplex (time division duplex, TDD) system or a frequency division duplex (frequency division duplex, FDD) system. In the TDD system, a time-frequency resource may be used only for downlink transmission or uplink transmission in a time unit. However, in the FDD system, the time-frequency resource may be used for both the uplink transmission and the downlink transmission in the time unit. For example, as shown in Table <NUM>, D represents the downlink transmission, and U represents the uplink transmission. In the TDD system, assuming that there are five slots (slots), where the first four slots are used for the downlink transmission, and the fifth slot is used for the uplink transmission. If a physical downlink shared channel (physical downlink shared channel, PDSCH) for sending downlink data is received in the first four slots, feedback information (for example, an acknowledgment (acknowledge, ACK) or a negative acknowledgment (negative acknowledge, NACK)) of the downlink data cannot be sent until the fifth slot. For example, the terminal device receives the PDSCH in the first slot, and the terminal device needs to wait for four slots to send the corresponding feedback information. Consequently, a long latency is caused. In the FDD system, assuming that there are five slots (slots), each slot is used for the downlink transmission and the uplink transmission. The terminal device may receive the PDSCH while sending the corresponding feedback information, so that a latency can be reduced.

There may be the TDD system or the FDD system in FR1. However, the maximum channel bandwidth of FR1 may only be <NUM>. A system bandwidth is limited. Consequently, a system capacity is limited. To support an ultra-reliable and low-latency communication (ultra-reliable and low-latency communication, URLLC) service, so that a plurality of terminal devices can satisfy requirements of reliability and a low latency, carrier aggregation (carrier aggregation, CA) may be performed on FR1 and FR2, to increase the system capacity.

In a CA scenario, a procedure in which the terminal device sends the feedback information includes the following several steps.

A protocol specifies the processing duration of the terminal device (namely, PDSCH processing procedure time (PDSCH processing procedure time)). As shown in Table <NUM>, µ represents that an SCS is <NUM>µ × <NUM>. For example, if µ is <NUM>, it indicates that the SCS is <NUM>; if µ is <NUM>, it indicates that the SCS is <NUM>; if µ is <NUM>, it indicates that the SCS is <NUM>; and if µ is <NUM>, it indicates that the SCS is <NUM>.

On a <NUM> carrier, the processing duration of the terminal device is <NUM> symbols (symbols). On a <NUM> carrier, the processing duration of the terminal device is <NUM> symbols. On a <NUM> carrier, the processing duration of the terminal device is <NUM> symbols. On a <NUM> carrier, the processing duration of the terminal device is <NUM> symbols. The terminal device usually determines a processing capability based on an SCS of the PDCCH, an SCS of the PDSCH, or an SCS of the PUCCH. For example, a smallest SCS is selected from the SCSs to determine the processing duration of the terminal device.

Example <NUM>: CA is performed on FR1 and FR2. An SCS of FR1 is <NUM>, and there is an FDD system. An SCS of FR2 is <NUM>, and there is a TDD system. It is configured by a higher layer that the feedback information is sent in FR2, that is, the carrier on which the PUCCH is located is FR2. That is, the terminal device sends the PUCCH in FR2. In this case, the SCS of the PUCCH is <NUM>. If both the PDCCH and the PDSCH are sent in FR2, the SCS of the PDCCH and the SCS of the PDSCH are both <NUM>. According to Table <NUM>, the processing duration of the terminal device is processing duration, namely, <NUM> symbols, corresponding to <NUM>. As shown in <FIG>, assuming that symbol numbers in a slot are <NUM> to <NUM>, and the PDSCH is sent on symbols <NUM> to <NUM> in a slot <NUM>, a symbol that can first send the feedback information is a symbol <NUM> in a slot <NUM> based on the processing duration of the terminal device. In this case, K1 may be set to <NUM>, and then it is indicated that the PUCCH resource corresponds to symbols <NUM> to <NUM>. However, because there is the TDD system in FR2, and only the fifth slot is used for the uplink transmission, K1 can be set only to <NUM>, and the terminal device needs to send the PUCCH on symbols <NUM> to <NUM> in the slot <NUM>.

It can be learned that in the foregoing Example <NUM>, because of the TDD system, the symbol on which the terminal device sends the feedback information is two slots later than expected, which is approximately equal to a feedback latency of <NUM>. Because the feedback information cannot reach the network device in time, the network device cannot schedule retransmission as soon as possible. Consequently, a service latency is caused, and service reliability is affected.

Example <NUM>: CA is performed on FR1 and FR2. An SCS of FR1 is <NUM>, and there is an FDD system. An SCS of FR2 is <NUM>, and there is a TDD system. It is configured by a higher layer that the feedback information is sent in FR1, that is, the carrier on which the PUCCH is located is FR1. That is, the terminal device sends the PUCCH in FR1. In this case, the SCS of the PUCCH is <NUM>. If both the PDCCH and the PDSCH are sent in FR2, the SCS of the PDCCH and the SCS of the PDSCH are both <NUM>. According to Table <NUM>, the processing duration of the terminal device is processing duration corresponding to <NUM> (the smallest SCS among the SCS of the PUCCH, the SCS of the PDCCH, and the SCS of the PDSCH), namely, <NUM> symbols corresponding to <NUM>. As shown in <FIG>, assuming that symbol numbers in a slot are <NUM> to <NUM>, and the PDSCH is sent on symbols <NUM> to <NUM> in a slot <NUM> of FR2, a symbol that can first send the feedback information is a symbol <NUM> in a slot <NUM> of FR1 based on the processing duration of the terminal device. In this case, K1 may be set to <NUM>, and then it is indicated that the PUCCH resource corresponds to symbols <NUM> and <NUM>. However, actually, time of sending on the indicated symbols is delayed compared with time of sending on the symbols <NUM> to <NUM> in FR2 in Example <NUM>.

It can be learned that in the foregoing Example <NUM>, the symbol on which the terminal device sends the feedback information is later than that in FR2, which is approximately equal to a feedback latency of <NUM>. Because the feedback information cannot reach the network device in time, the network device cannot schedule retransmission as soon as possible. Consequently, a service latency is caused, and service reliability is affected.

In a CA scenario, a procedure in which the terminal device sends channel state information (channel state information, CSI) includes the following several steps.

A protocol specifies the processing duration of the terminal device (namely, CSI computation time (CSI computation time)). As shown in Table <NUM>, µ represents that an SCS is <NUM>µ × <NUM>. For example, if µ is <NUM>, it indicates that the SCS is <NUM>; if µ is <NUM>, it indicates that the SCS is <NUM>; if µ is <NUM>, it indicates that the SCS is <NUM>; and if µ is <NUM>, it indicates that the SCS is <NUM>.

On a <NUM> carrier, the processing duration of the terminal device is <NUM> symbols (symbols). On a <NUM> carrier, the processing duration of the terminal device is <NUM> symbols. On a <NUM> carrier, the processing duration of the terminal device is <NUM> symbols. On a <NUM> carrier, the processing duration of the terminal device is <NUM> symbols. The terminal device usually determines a processing capability based on an SCS of the PDCCH, an SCS of a channel state information-reference signal (channel state information-reference signal, CSI-RS), or an SCS of the CSI (namely, the PUSCH or the PUCCH). For example, a smallest SCS is selected from the SCSs to determine the processing duration of the terminal device.

Example <NUM>: CA is performed on FR1 and FR2. An SCS of FR1 is <NUM>, and there is an FDD system. An SCS of FR2 is <NUM>, and there is a TDD system. Assuming that the PDCCH and the CSI-RS are sent in FR2, and a channel state in FR2 needs to be measured, that is, the terminal device performs channel estimation based on the CSI-RS in FR2. In this case, the SCSs of the PDCCH and the CSI-RS are both <NUM>. If the PDCCH indicates to send the CSI in FR2, according to Table <NUM>, the processing duration of the terminal device is processing duration, namely, <NUM> symbols, corresponding to <NUM>. Because there is the TDD system in FR2, a downlink symbol may be included after the <NUM> symbols. Consequently, sending of the CSI needs to be delayed. If the PDCCH indicates to send the CSI in FR1, according to Table <NUM>, the processing duration of the terminal device is processing duration, namely, <NUM> symbols corresponding to <NUM>. The processing duration is equivalent to <NUM> symbols corresponding to <NUM>. There are still <NUM> more symbols than the <NUM> symbols for sending the CSI in FR2, and a latency of approximately <NUM> is caused.

It can be learned that in the foregoing Example <NUM>, if the CSI is sent in FR2, because of the TDD system, the symbol on which the terminal device sends the CSI is later than expected. If the CSI is sent in FR1, because the processing duration is determined based on <NUM>, a latency is also caused. The CSI cannot be fed back in time, and a base station cannot obtain the channel state information in time, and therefore cannot adjust a scheduling policy. Consequently, it is quite difficult to ensure service reliability and a low latency.

In a CA scenario, a procedure in which the terminal device sends a PUSCH includes the following several steps.

A protocol specifies the processing duration of the terminal device (namely, PUSCH preparation time (PUSCH preparation time)). As shown in Table <NUM>, µ represents that an SCS is <NUM>µ × <NUM>. For example, if µ is <NUM>, it indicates that the SCS is <NUM>; if µ is <NUM>, it indicates that the SCS is <NUM>; if µ is <NUM>, it indicates that the SCS is <NUM>; and if µ is <NUM>, it indicates that the SCS is <NUM>.

On a <NUM> carrier, the processing duration of the terminal device is <NUM> symbols (symbols). On a <NUM> carrier, the processing duration of the terminal device is <NUM> symbols. On a <NUM> carrier, the processing duration of the terminal device is <NUM> symbols. On a <NUM> carrier, the processing duration of the terminal device is <NUM> symbols. The terminal device usually determines a processing capability based on an SCS of a PDCCH or an SCS of a PUSCH. For example, a smallest SCS is selected from the SCSs to determine the processing duration of the terminal device.

Example <NUM>: CA is performed on FR1 and FR2. An SCS of FR1 is <NUM>, and there is an FDD system. An SCS of FR2 is <NUM>, and there is a TDD system. It is assumed that the PDCCH is transmitted in FR2. If the PDCCH indicates to send the uplink data in FR2, that is, the terminal device sends the PUSCH in FR2, according to Table <NUM>, the processing duration of the terminal device is processing duration, namely, <NUM> symbols, corresponding to <NUM>. Because there is the TDD system in FR2, a downlink symbol may be included after the <NUM> symbols. Consequently, sending of the uplink data needs to be delayed. If the PDCCH indicates to send the uplink data in FR1, according to Table <NUM>, the processing duration of the terminal device is processing duration, namely, <NUM> symbols, corresponding to <NUM>. The processing duration is equivalent to <NUM> symbols corresponding to <NUM>. There are still <NUM> more symbols than the <NUM> symbols for sending the CSI in FR2, and a latency of approximately <NUM> is caused.

It can be learned that in the foregoing Example <NUM>, if the uplink data is sent in FR2, because of the TDD system, the symbol on which the terminal device sends the uplink data is later than expected. If the uplink data is sent in FR1, because the processing duration is determined based on <NUM>, a latency is also caused. The uplink data cannot be fed back in time, and a base station cannot obtain data of the terminal device in time. Consequently, it is quite difficult to ensure service reliability and a low latency.

Based on the foregoing related technologies, this application provides a resource determining method. <FIG> is an example of a schematic diagram of a communication system. As shown in <FIG>, the communication system, for example, a long term evolution (long term evolution, LTE) system, may include a base station (base station) and user equipment (user equipment, UE) <NUM> to <NUM>. The UE <NUM> to the UE <NUM> send first information to the base station. In addition, a communication system may alternatively include the UE <NUM> to the UE <NUM>. In the communication system, the base station may send downlink information to the UE <NUM>, the UE <NUM>, the UE <NUM>, and the UE <NUM>. The UE <NUM> may also send the downlink information to the UE <NUM> and the UE <NUM>.

It should be noted that, in addition to being applied to the foregoing LTE system, a scheduling method provided in this application may be further applied to another communication system, for example, a <NUM> NR (new radio) system, a global system for mobile communications (global system for mobile communication, GSM), a universal mobile telecommunications system (universal mobile telecommunications system, UMTS), or code division multiple access (code division multiple access, CDMA) system, a wideband code division multiple access (wideband code division multiple access, WCDMA) system, a narrowband internet of things (narrow band internet of things, NB-IoT) system, an enhanced machine type communication (enhanced machine-type communication, eMTC) system, and another communication system. The scheduling method provided in this application may be used provided that a network device in the communication system needs to send downlink control information, and a terminal device needs to receive the downlink control information and determine a data channel based on the downlink control information.

The network device may be configured to mutually convert a received over-the-air frame and an internet protocol (internet protocol, IP) packet, and serve as a router between a wireless terminal and a remaining part of an access network, where the remaining part of the access network may include an IP network. The network device may further coordinate attribute management of an air interface. For example, the network device may be a base transceiver station (base transceiver station, BTS) in GSM or CDMA, may be a NodeB (NodeB) in WCDMA, or may be an evolved NodeB (evolutional NodeB, eNB or eNodeB) in LTE, or a gNB in <NUM> NR. This is not specifically limited in this application.

The terminal device may be a device that provides a user with a voice and/or data connectivity, a handheld device with a wireless connection function, or another processing device connected to a wireless modem. The terminal device may communicate with one or more core networks by using a radio access network (radio access network, RAN). The terminal device may be a mobile terminal, for example, a mobile phone (or referred to as a "cellular" phone) and a computer having a mobile terminal, or may be a portable, pocket-sized, handheld, computer built-in, or in-vehicle mobile apparatus. The terminal device exchanges language and/or data with the radio access network. For example, the terminal device is a device such as a personal communications service (personal communication service, PCS) phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (wireless local loop, WLL) station, or a personal digital assistant (personal digital assistant, PDA). The terminal device may also be referred to as a system, a subscriber unit (Subscriber Unit), a subscriber station (subscriber station), a mobile station (mobile station), a remote station (remote station), an access point (access point), a remote terminal (remote terminal), an access terminal (access terminal), a user terminal (user terminal), a user agent (user agent), a user device (user device), or user equipment (user equipment).

<FIG> is a flowchart of an embodiment of a resource determining method according to this application. As shown in <FIG>, the method in this embodiment may be applied to the communication system shown in <FIG>. The resource determining method may include the following steps.

Step <NUM>: A network device determines a resource of an uplink channel.

When a terminal device needs to send uplink information (for example, uplink data), or the network device requires the terminal device to send uplink information (for example, CSI or feedback information that corresponds to downlink information), the network device allocates a resource used by the terminal device to send the uplink information. Therefore, the network device may determine, based on factors such as a capability of each terminal device, a service requirement, and resource distribution, to allocate, to the terminal device, the resource that is of the uplink channel and that is used by the terminal device to send the uplink information.

Step <NUM>: The network device sends DCI to the terminal device, where the DCI is carried on a PDCCH.

The network device writes indication information indicating the resource of the uplink channel to the DCI, and sends the DCI to the terminal device via the PDCCH.

Step <NUM>: The terminal device determines the resource of the uplink channel based on the DCI, where the resource of the uplink channel is used to send the uplink information.

The terminal device receives the PDCCH, obtains the DCI through parsing, and obtains the indication information of the network device from the DCI, to determine the resource that is of the uplink channel and that is allocated by the network device. Then, the terminal device may send the uplink information in a corresponding time unit, on a corresponding carrier, and in a corresponding band by using the resource of the uplink channel.

The foregoing procedure is a basic procedure in which the network device dynamically schedules the terminal device. The procedure may be applied to the following three application scenarios:.

Scenario <NUM>: A procedure in which the terminal device sends the feedback information includes the following steps.

Specifically, in the scenario <NUM>, the uplink information is feedback information, for example, an acknowledgment (acknowledge, ACK) or a negative acknowledgment (negative acknowledge, NACK), corresponding to a PDSCH. The uplink channel is a PUCCH, and the PDSCH is scheduled by using the DCI carried in the PDCCH.

Scenario <NUM>: A procedure in which the terminal device sends the CSI includes the following steps.

Specifically, in the scenario <NUM>, the uplink information is the CSI, and the uplink channel is a PUCCH or a PUSCH.

Scenario <NUM>: A procedure in which the terminal device sends a PUSCH includes the following steps.

Specifically, in the scenario <NUM>, the uplink information is the uplink data, and the uplink channel is a PUSCH scheduled by using the DCI carried on the PDCCH.

The following describes the technical solutions of the resource determining method provided in this application in detail by using several embodiments with reference to the foregoing three scenarios.

Terminal device side: After determining the resource of the uplink channel based on the DCI, the terminal device may determine the processing duration. The processing duration includes at least one time unit. When feedback duration is greater than or equal to the processing duration, the terminal device sends the uplink information on the resource of the uplink channel.

The terminal device may determine the processing duration by using the following three methods.

Method <NUM>: Obtain at least one SCS and processing duration respectively corresponding to at least one SCS, and determine shortest duration in the processing duration respectively corresponding to the at least one SCS as the processing duration.

Corresponding to the scenario <NUM>, the at least one SCS includes an SCS of the PDCCH carrying the DCI, an SCS of the PDSCH scheduled by using the DCI, and an SCS of the PUCCH carrying the feedback information corresponding to the PDSCH. The feedback duration is a time length between the resource of the PDSCH and the resource of the PUCCH (the feedback information).

Corresponding to the scenario <NUM>, the at least one SCS includes an SCS of the PDCCH carrying the DCI, an SCS of a CSI-RS, and an SCS of a PUCCH or a PUSCH carrying CSI corresponding to the CSI-RS. The feedback duration is a time length between the resource of the PDCCH and a resource of the PUCCH or the PUSCH (the CSI).

Corresponding to the scenario <NUM>, the at least one SCS includes an SCS of the PDCCH carrying the DCI and an SCS of the PUSCH scheduled by using the DCI. The feedback duration is a time length between the resource of the PDCCH and the resource of the PUSCH.

As described in the foregoing examples, a protocol specifies the processing duration of the terminal device. There is a correspondence between an SCS and the processing duration. A smaller SCS indicates a smaller quantity of symbols included in the processing duration of the terminal device but longer total duration of the symbols. In other words, duration occupied by a symbol with a large SCS is less than duration occupied by a symbol with a small SCS. In this application, processing duration (where the processing duration is the shortest duration in the processing duration respectively corresponding to the at least one SCS) corresponding to a largest SCS in the at least one SCS is selected as the processing duration of the terminal device. The feedback duration may be set to a value that is slightly greater than or equal to the processing duration. Because the processing duration is the shortest, short feedback duration may be used to satisfy a condition of being greater than or equal to the processing duration. This reduces a latency of sending the uplink information by the terminal device.

Method <NUM>: Obtain an SCS of a downlink channel and processing duration corresponding to an SCS of the downlink channel, and determine the processing duration corresponding to the SCS of the downlink channel as the processing duration.

Corresponding to the scenario <NUM>, the SCS of the downlink channel is an SCS of the PDSCH scheduled by using the DCI. The feedback duration is a time length between the resource of the PDSCH and the resource of the PUCCH (the feedback information).

Corresponding to the scenario <NUM>, the SCS of the downlink channel is an SCS of a CSI-RS. The feedback duration is a time length between the resource of the PDCCH and the resource of the PUCCH or the PUSCH (the CSI).

As described in the foregoing examples, the processing duration corresponding to the SCS of the downlink channel is determined as the processing duration. When the SCS corresponding to the downlink channel is larger, the processing duration corresponding to the SCS is shorter. The processing duration corresponding to the SCS is used, so that shorter feedback duration can be used to satisfy a condition of being greater than or equal to the processing duration. This reduces a latency of sending the uplink information by the terminal device. When the SCS corresponding to the downlink channel is smaller, although the processing duration corresponding to the SCS is longer, because the SCS is used for the downlink channel, it indicates that processing time of the downlink channel should be longer. In other words, data carried on the downlink channel is not so urgent. In this case, using the SCS to determine a processing capability does not affect the latency.

Method <NUM>: Determine whether a condition is satisfied. The condition may include: A current service is a specified service; or a value of first indication information is a specified value. When the condition is satisfied, the foregoing method <NUM> or method <NUM> may be used to determine the processing duration. When the foregoing condition is not satisfied, the processing duration is determined by using the method in the foregoing related technology.

The specified service may be a service of a specific type, and the service of the specific type requires reliability and a low latency, or the service of the specific type requires a high throughput. For example, if the terminal device determines that the specified service is a URLLC service, it is considered that the condition is satisfied, and the processing duration is determined by using the foregoing method <NUM> or method <NUM>; if the terminal device determines that a non-URLLC service is currently performed, it is considered that the condition is not satisfied, and the processing duration may be determined by using the method in the foregoing related technology. A service type may be identified by using any one of the following methods: The terminal device determines the service type based on a DCI format. There is a correspondence between the DCI format and the service type. For example, if the DCI format is DCI format 1_2, it is considered that the service is the URLLC service; if the DCI format is DCI format 1_1 or DCI format 1_0, it may be considered that the service is an enhanced mobile broadband (enhanced mobile broadband, eMBB) service, namely, an unspecified service. Alternatively, the terminal device determines the service type based on a mapping type of a PDSCH. There is a correspondence between the mapping type of the PDSCH and the service type. For example, if the mapping type of the PDSCH is A, it is considered that the service is a specified service; if the mapping type of the PDSCH is B, it is considered that the service is an unspecified service. The mapping type of the PDSCH refers to a location of a demodulation reference signal (demodulation reference signal, DMRS) used for demodulation of the PDSCH. The mapping type A indicates that the location of the DMRS is the third or the fourth symbol in one slot, and the mapping type B indicates that the location of the DMRS is the first symbol of data. Alternatively, the terminal device determines the service type based on search space in which a PDCCH is located. There is a correspondence between the search space in which the PDCCH is located and the service type. For example, if an identifier of the search space is <NUM>, it is considered that the service is a specified service; if an identifier of the search space is <NUM>, it is considered that the service is an unspecified service. Alternatively, for example, if an identifier of the search space is less than or equal to X, it is considered that the service is a specified service; if an identifier of the search space is greater than X, it is considered that the service is an unspecified service. Alternatively, the terminal device determines the service type based on a control resource set (control resource set, CORESET). There is a correspondence between the CORESET and the service type. For example, if an identifier of the CORESET is <NUM>, it is considered that the service is a specified service; if an identifier of the search space is <NUM>, it is considered that the service is an unspecified service. Alternatively, for example, if an identifier of the CORESET is less than or equal to X, it is considered that the service is a specified service; if an identifier of the CORESET is greater than X, it is considered that the service is an unspecified service. Alternatively, the terminal device determines the service type based on a bit field displayed in a PDCCH. There is a correspondence between the bit field displayed in the PDCCH and the service type. For example, there is one bit in DCI. If the bit indicates <NUM>, the service is a specified service; if the bit indicates <NUM>, the service is an unspecified service. Alternatively, the terminal device determines the service type based on a scrambling manner of DCI. There is a correspondence between the scrambling manner of the DCI and the service type. For example, if the DCI is scrambled by using a radio network temporary identifier (radio network temporary identifier, RNTI) <NUM>, it is considered that service is a specified service; if the DCI is scrambled by using an RNTI <NUM>, it is considered that service is a specified service. Alternatively, the terminal device determines the service type based on a time domain resource length of a PDSCH. There is a correspondence between the time domain resource length of the PDSCH and the service type. For example, if the time domain length of the PDSCH is less than or equal to L, it is considered that the service is a specified service; if the time domain length of the PDSCH is greater than or equal to L, it is considered that the service is an unspecified service.

The first indication information may be carried in higher layer signaling, for example, radio resource control (radio resource control, RRC) signaling, or may be indicated by the network device by using the DCI. When the value of the first indication information is the specified value (for example, the value is <NUM>), it is considered that the condition is satisfied. In this case, the terminal device may determine the processing duration by using the foregoing method <NUM> or method <NUM>. When the value of the first indication information is not the specified value (for example, the value is <NUM>), it is considered that the condition is not satisfied. In this case, the terminal device may determine the processing duration by using the method in the foregoing related technology. However, if the first indication information is configure neither at the higher layer nor in the DCI, the terminal device may determine the processing duration by using a default method (for example, the method in the foregoing related technology).

After determining the processing duration, the terminal device determines the feedback duration based on the information (for example, K1, K2, or K3) indicated in the DCI. As described in the scenario <NUM> to the scenario <NUM>, the feedback duration is compared with the processing duration. If the feedback duration is greater than or equal to the processing duration, the terminal device sends the uplink information on the uplink channel according to an indication of the DCI. If the feedback duration is less than the processing duration, it indicates that on the uplink channel, the terminal device does not have sufficient time for PDSCH processing, CSI computation, or PUSCH preparation, and therefore cannot send the uplink information on the uplink channel. In this case, the terminal device does not send the uplink information to the network device.

Network device side: After sending the DCI to the terminal device, the network device may determine the processing duration of the terminal device. The processing duration includes the at least one time unit. When the feedback duration indicated in the DCI is greater than or equal to the processing duration of the terminal device, the network device receives uplink information on the resource of the uplink channel.

The network device may also determine the processing duration of the terminal device by using three methods. Technical principles of the three methods are similar to those of the foregoing three methods on the terminal device side.

After determining the processing duration of the terminal device, the network device determines the feedback duration based on the information (for example, K1, K2, or K3) indicated in the DCI. As described in the scenario <NUM> to the scenario <NUM>, the feedback duration is compared with the processing duration of the terminal device. If the feedback duration is greater than or equal to the processing duration, the network device receives the uplink information on the uplink channel indicated by the feedback duration. However, if the feedback duration is less than the processing duration, it indicates that on the uplink channel indicated by the feedback duration, the terminal device does not have sufficient time for PDSCH processing, CSI computation, or PUSCH preparation, and therefore cannot send the uplink information on the uplink channel. In this case, the network device does not need to receive the uplink information.

In this embodiment, both the network device and the terminal device use the shortest duration as the processing duration of the terminal device. Therefore, the feedback duration may be set to the value slightly greater than or equal to the processing duration. Because the processing duration is the shortest, and the short feedback duration may be used to satisfy the condition of being greater than or equal to the processing duration, the terminal device sends, as soon as possible, the uplink information on the uplink channel corresponding to the time unit indicated by the feedback duration, to reduce a latency of sending the uplink information.

A method in this embodiment is applied to the case in the scenario <NUM>.

Terminal device side: In a procedure in which the terminal device determines the resource of the uplink channel, the terminal device is configured to first determine a carrier on which the PUCCH is located, and then determine the resource of the PUCCH based on the carrier on which the PUCCH is located and the DCI. The PUCCH carries the feedback information corresponding to the PDSCH, and the PDSCH is scheduled by using the DCI carried on the PDCCH.

The terminal device is configured to determine, by using any one of the following methods, the carrier on which the PUCCH is located:.

The network device may configure one or more PUCCH resource sets for the terminal device by using higher layer signaling, and configure a carrier corresponding to each PUCCH resource set. For example, a first PUCCH resource set corresponds to a carrier <NUM>, a second PUCCH resource set corresponds to a carrier <NUM>, and the like. Alternatively, after one or more PUCCH resource sets are configured, a carrier corresponding to each PUCCH resource set may be specified by using a protocol. For example, it is specified that a first PUCCH resource set corresponds to a carrier <NUM>, a second PUCCH resource set corresponds to a carrier <NUM>, and the like.

The network device may alternatively indicate, by using configuration information, or specify, by using a protocol, a correspondence between a plurality of bit quantities of the feedback information and a plurality of PUCCH resource sets. For example, a bit quantity range X1 and X2 corresponds to a first PUCCH resource set, a bit quantity range X3 and X4 corresponds to a second PUCCH resource set, and the like. The terminal device determines a bit quantity of the feedback information, to determine a PUCCH resource set corresponding to the bit quantity. Because a carrier corresponding to the PUCCH resource set is determined, the corresponding carrier may be obtained based on the PUCCH resource set. That is, all PUCCH resources in a same PUCCH resource set are on a same carrier. When a PUCCH resource set in which a PUCCH resource is located is known, a carrier on which the PUCCH resource is located is determined.

The terminal device determines, based on a service type of the PDSCH, the carrier on which the PUCCH is located. There is a correspondence between a plurality of service types of the PDSCH and a plurality of carriers. For example, a service type <NUM> corresponds to a carrier <NUM>, and a service type <NUM> corresponds to a carrier <NUM>.

A higher layer may configure the correspondence between the service types and the carriers, or the correspondence between the service types and the carriers is specified in a protocol. After determining a current service type, the terminal device may obtain a corresponding carrier. For a manner of determining the service type by the terminal device, refer to the method in Embodiment <NUM>. Details are not described again in this application.

The terminal device may determine the resource of the PUCCH based on the carrier on which the PUCCH is located and the DCI by using any one of the following methods.

The higher layer may configure the correspondence between the plurality of carriers and the plurality of PUCCH resource sets. In other words, different carriers correspond to different PUCCH resource sets. For example, a carrier <NUM> corresponds to a PUCCH resource set <NUM>, and a carrier <NUM> corresponds to a PUCCH resource set <NUM>. Specifically, the terminal device may receive configuration information from the network device, and the configuration information indicates a PUCCH resource set corresponding to each carrier. After determining, by using the foregoing method, the carrier on which the PUCCH is located, the terminal device may obtain the PUCCH resource set corresponding to the carrier. The DCI includes a first indication value, and the terminal device finds a corresponding PUCCH resource from a determined PUCCH resource set based on the first indication value.

Network device side: In a procedure in which the network device determines the resource of the uplink channel, the network device may first determine the carrier on which the PUCCH is located, and then determine the resource of the PUCCH based on the carrier on which the PUCCH is located. The PUCCH carries the feedback information corresponding to the PDSCH, and the PDSCH is scheduled by using the DCI carried on the PDCCH.

The network device may write the indication information to the DCI, to indicate the resource of the PUCCH. The DCI may include one or more of the second indication information, the K1 indication information, the resource of the PUCCH, and the first indication value. A function of the DCI is the same as that on the terminal device side.

Alternatively, the network device may determine, by using the method <NUM> or <NUM> on the terminal device side, the carrier on which the PUCCH is located. A technical principle of the method on the network device side is similar to that of the method on the terminal device side.

In this embodiment, the carrier on which the uplink channel is located may be dynamically determined, and the terminal device may choose, during each time of scheduling, to send the feedback information on a fastest available carrier, to reduce a service latency.

Terminal device side: After determining the resource of the uplink channel based on the DCI, the terminal device may send the uplink information on the resource of the uplink channel. When an SCS of the uplink channel is less than a first SCS, the uplink channel is sent on the resource of the uplink channel at the first SCS.

Corresponding to the scenario <NUM>, the first SCS is an SCS of the PDCCH or an SCS of the PDSCH scheduled by using the DCI.

That is, in the scenario <NUM>, when an SCS of the PUCCH is less than the SCS of the PDCCH or the SCS of the PDSCH, the uplink channel is sent on the PUCCH at the SCS of the PDCCH or the SCS of the PDSCH. For a determining manner of the SCS of the PUCCH, refer to a manner in a related technology. Alternatively, the carrier on which the PUCCH is located may be determined based on Embodiment <NUM>, and an SCS corresponding to the carrier is the SCS of the PUCCH. For example, the SCS of the PUCCH is <NUM>, and the SCS of the PDSCH is <NUM>. This is equivalent to that a <NUM> signal needs to be sent on a <NUM> channel. In other words, a <NUM> channel is sent on a <NUM> carrier.

Corresponding to the scenario <NUM>, the first SCS is an SCS of the PDCCH or an SCS of a CSI-RS, where the CSI-RS corresponds to the CSI triggered by the PDCCH.

That is, in the scenario <NUM>, when an SCS of the PUCCH or an SCS of the PUSCH is less than the SCS of the PDCCH or the SCS of the CSI-RS, the uplink channel is sent on the PUCCH or the PUSCH at the SCS of the PDCCH or the SCS of the CSI-RS. For a determining manner of the SCS of the PUCCH, refer to a manner in a related technology. Alternatively, the carrier on which the PUCCH is located may be determined based on Embodiment <NUM>, and an SCS corresponding to the carrier is the SCS of the PUCCH. The SCS of the PUSCH may be determined in the manner in the related technology. Details are not described again. For example, the SCS of the PUCCH or the SCS of the PUSCH is <NUM>, and the SCS of the CSI-RS is <NUM>. This is equivalent to that a <NUM> signal needs to be sent on a <NUM> channel. In other words, a <NUM> channel is sent on a <NUM> carrier.

Corresponding to the scenario <NUM>, the first SCS is an SCS of the PDCCH.

That is, in the scenario <NUM>, when an SCS of the PUSCH is less than the SCS of the PDCCH, the uplink channel is sent on the PUSCH at the SCS of the PDCCH. For a determining manner of the SCS of the PUSCH, refer to a manner in a related technology. For example, the SCS of the PUSCH is <NUM>, and the SCS of the PDCCH is <NUM>. This is equivalent to that a <NUM> channel needs to be sent on a <NUM> channel. In other words, a <NUM> channel is sent on a <NUM> carrier.

As shown in <FIG>, CA is performed on FR1 and FR2. An SCS of FR1 is <NUM>, and there is an FDD system. An SCS of FR2 is <NUM>, and there is a TDD system. Assuming that symbol numbers in a slot are <NUM> to <NUM>, a PDSCH is sent on symbols <NUM> to <NUM> in a slot <NUM> in FR2, and DCI configures a terminal device to send feedback information in FR1, processing duration of the terminal device is eight symbols, namely, symbols <NUM> and <NUM> in the slot <NUM>, corresponding to <NUM>. Assuming that the DCI configures the terminal device to send the feedback information in FR2, processing duration of the terminal device is <NUM> symbols, namely, symbols <NUM> to <NUM> in a slot <NUM>, corresponding to <NUM>. In terms of time, time for sending a PUCCH in FR1 is later than time for sending the PUCCH in FR2. In this application, uplink information may be sent on a resource of an uplink channel n FR1 on a carrier in FR2. That is, in FR1, the uplink information starts to be sent from a time point aligned with the symbol <NUM> in the slot <NUM> in FR2. This method may shorten a feedback latency.

<FIG> is a schematic diagram of a structure of an embodiment of a communication apparatus according to this application. As shown in <FIG>, the apparatus in this embodiment may include a receiving module <NUM>, a processing module <NUM>, and a sending module <NUM>.

When the communication apparatus is used in a terminal device, the receiving module <NUM> is configured to receive downlink control information DCI sent by a network device, where the DCI is carried on a physical downlink control channel PDCCH; and the processing module <NUM> is configured to determine a resource of an uplink channel based on the DCI, where the resource of the uplink channel is used to send uplink information.

In a possible implementation, the processing module <NUM> is further configured to determine first processing duration, where the first processing duration includes at least one time unit; and the sending module <NUM> is configured to: when feedback duration is greater than or equal to the first processing duration, send the uplink information on the resource of the uplink channel, where the feedback duration is a time length between the resource of the uplink channel and a resource of a downlink channel corresponding to the uplink channel, and the downlink channel includes the PDCCH or a physical downlink shared channel PDSCH scheduled by using the DCI.

In a possible implementation, the processing module <NUM> is specifically configured to: obtain at least one subcarrier spacing SCS and processing duration respectively corresponding to the at least one SCS, where the at least one SCS includes an SCS of the PDCCH and an SCS of the uplink channel; and determine shortest duration in the processing duration respectively corresponding to the at least one SCS as the first processing duration.

In a possible implementation, the at least one SCS further includes an SCS of the PDSCH scheduled by using the DCI, the uplink channel is a physical uplink control channel PUCCH, and the PUCCH carries feedback information corresponding to the PDSCH.

In a possible implementation, the at least one SCS further includes an SCS of a channel state information-reference signal CSI-RS, the uplink channel is a PUCCH or a PUSCH, the PUCCH or the PUSCH carries channel state information CSI corresponding to the CSI-RS, and the CSI is triggered by the DCI.

In a possible implementation, the uplink channel is a PUSCH scheduled by using the PDCCH.

In a possible implementation, the processing module <NUM> is specifically configured to: obtain an SCS of the PDSCH scheduled by using the DCI and processing duration corresponding to the SCS of the PDSCH, where the PDSCH corresponds to the uplink channel, the uplink channel is a PUCCH, and the PUCCH carries feedback information corresponding to the PDSCH; and determine the processing duration corresponding to the SCS of the PDSCH as the first processing duration.

In a possible implementation, the processing module <NUM> is specifically configured to: obtain an SCS of a CSI-RS and processing duration corresponding to the SCS of the CSI-RS, where the CSI-RS corresponds to the uplink channel, the uplink channel is a PUCCH or a PUSCH, the PUCCH or the PUSCH carries CSI corresponding to the CSI-RS, and the CSI is triggered by the DCI; and determine the processing duration corresponding to the SCS of the CSI-RS as the first processing duration.

In a possible implementation, the processing module <NUM> is further configured to: determine whether a first condition is satisfied; and when the first condition is satisfied, determine the first processing duration, where the first condition includes: a current service is a URLLC service; or a value of first indication information is a specified value.

The uplink channel is a PUCCH, and the PUCCH carries feedback information corresponding to a PDSCH scheduled by using the DCI. The processing module <NUM> is specifically configured to determine a carrier on which the PUCCH is located; and determine a resource of the PUCCH based on the carrier on which the PUCCH is located and the DCI.

The processing module <NUM> is specifically configured to: when the DCI includes second indication information, determine a carrier corresponding to a value of the second indication information as the carrier on which the PUCCH is located; when the DCI includes feedback duration, if a time unit that is indicated by the feedback duration and that is of the feedback information corresponding to the PDSCH includes a downlink symbol, determine a default carrier as the carrier on which the PUCCH is located; when the DCI includes the resource of the PUCCH, determine a carrier of the resource of the PUCCH as the carrier on which the PUCCH is located; determine, based on a bit quantity of the feedback information, the carrier on which the PUCCH is located, where there is a correspondence between a plurality of bit quantities of the feedback information and a plurality of PUCCH resource sets, and there is a correspondence between the plurality of PUCCH resource sets and a plurality of carriers; or determine, based on a service type of the PDSCH, the carrier on which the PUCCH is located, where there is a correspondence between a plurality of service types of the PDSCH and a plurality of carriers.

In a possible implementation, the processing module <NUM> is specifically configured to: obtain a feedback duration set corresponding to the carrier on which the PUCCH is located, where there is a correspondence between the plurality of carriers and a plurality of feedback duration sets; and determine a time unit indicated by first feedback duration in the feedback duration set corresponding to the carrier on which the PUCCH is located as a time unit in which the PUCCH is located, where the first feedback duration is included in the DCI.

In a possible implementation, the processing module <NUM> is specifically configured to: obtain a PUCCH resource set corresponding to the carrier on which the PUCCH is located, where there is the correspondence between the plurality of carriers and the plurality of PUCCH resource sets; and determine a PUCCH resource that is indicated by a first indication value and that is in the PUCCH resource set corresponding to the carrier on which the PUCCH is located as the resource of the PUCCH, where the first indication value is included in the DCI.

In a possible implementation, the sending module <NUM> is further configured to send the uplink information on the resource of the uplink channel.

In a possible implementation, the sending module <NUM> is specifically configured to: when an SCS of the uplink channel is less than a first SCS, send the uplink channel on the resource of the uplink channel at the first SCS.

In a possible implementation, the first SCS is an SCS of the PDCCH or an SCS of the PDSCH scheduled by using the DCI; the first SCS is an SCS of the PDCCH or an SCS of a CSI-RS, where the CSI-RS corresponds to CSI triggered by the PDCCH; or the first SCS is an SCS of the PDCCH.

When the communication apparatus is used in a network device, the processing module <NUM> is configured to determine a resource of an uplink channel, where the resource of the uplink channel is used to receive uplink information; and the sending module <NUM> is configured to send downlink control information DCI to a terminal device, where the DCI is carried on a physical downlink control channel PDCCH, and the DCI is used to indicate the resource of the uplink channel.

In a possible implementation, the processing module <NUM> is further configured to determine first processing duration, where the first processing duration includes at least one time unit; and the receiving module <NUM> is configured to: when feedback duration is greater than or equal to the first processing duration, receive the uplink information on the resource of the uplink channel, where the feedback duration is a time length between the resource of the uplink channel and a resource of a downlink channel corresponding to the uplink channel, and the downlink channel includes the PDCCH or a physical downlink shared channel PDSCH scheduled by using the DCI.

In a possible implementation, the uplink channel is a PUCCH, and the PUCCH carries feedback information corresponding to a PDSCH scheduled by using the DCI. The processing module <NUM> is specifically configured to determine a carrier on which the PUCCH is located; and determine a resource of the PUCCH based on the carrier on which the PUCCH is located.

In a possible implementation, when the DCI includes second indication information, a carrier corresponding to a value of the second indication information is the carrier on which the PUCCH is located; when the DCI includes feedback duration, if a time unit that is indicated by the feedback duration and that is of the feedback information corresponding to the PDSCH includes a downlink symbol, a default carrier is the carrier on which the PUCCH is located, where the feedback duration is a time length between the resource of the PUCCH and a resource of the PDSCH; or when the DCI includes the resource of the PUCCH, a carrier of the resource of the PUCCH is the carrier on which the PUCCH is located.

In a possible implementation, the processing module <NUM> is specifically configured to: determine, based on a bit quantity of the feedback information, the carrier on which the PUCCH is located, where there is a correspondence between a plurality of bit quantities of the feedback information and a plurality of PUCCH resource sets, and there is a correspondence between the plurality of PUCCH resource sets and a plurality of carriers; or determine, based on a service type of the PDSCH, the carrier on which the PUCCH is located, where there is a correspondence between a plurality of service types of the PDSCH and a plurality of carriers.

In a possible implementation, the DCI includes the feedback duration, and a time unit indicated by the feedback duration in a feedback duration set corresponding to the carrier on which the PUCCH is located is a time unit in which the PUCCH is located, and there is a correspondence between the plurality of carriers and a plurality of feedback duration sets.

In a possible implementation, the DCI includes a first indication value, and a PUCCH resource that is indicated by the first indication value and that is in a PUCCH resource set corresponding to the carrier on which the PUCCH is located is the resource of the PUCCH, and there is the correspondence between the plurality of carriers and the plurality of PUCCH resource sets.

In a possible implementation, the receiving module <NUM> is further configured to receive the uplink information on the resource of the uplink channel.

In a possible implementation, the receiving module <NUM> is specifically configured to: when an SCS of the uplink channel is less than a first SCS, receive the uplink channel on the resource of the uplink channel at the first SCS.

The apparatus in this embodiment may be configured to perform the technical solutions in the method embodiment shown in <FIG> or <FIG>, and the implementation principle and the technical effect of the apparatus are similar to those of the method embodiment, and are not described herein again.

<FIG> is a schematic diagram of a structure of a terminal device according to this application. As shown in <FIG>, the terminal device <NUM> includes a processor <NUM> and a transceiver <NUM>.

Optionally, the terminal device <NUM> further includes a memory <NUM>. The processor <NUM>, the transceiver <NUM>, and the memory <NUM> may communicate with each other through an internal connection path, to transfer a control signal and/or a data signal.

The memory <NUM> is configured to store a computer program. The processor <NUM> is configured to execute the computer program stored in the memory <NUM>, to implement the functions of the communication apparatus in the foregoing apparatus embodiment.

Optionally, the memory <NUM> may be integrated into the processor <NUM>, or may be independent of the processor <NUM>.

Optionally, the terminal device <NUM> may further include an antenna <NUM>, configured to transmit a signal output by the transceiver <NUM>. Alternatively, the transceiver <NUM> receives a signal through the antenna.

Optionally, the terminal device <NUM> may further include a power supply <NUM>, configured to supply power to various components or circuits in the terminal device.

In addition, to improve the functions of the terminal device, the terminal device <NUM> may further include one or more of an input unit <NUM>, a display unit <NUM> (which may alternatively be considered as an output unit), an audio circuit <NUM>, a camera <NUM>, a sensor <NUM>, and the like. The audio circuit may further include a speaker <NUM>, a microphone <NUM>, and the like. Details are not described again.

<FIG> is a schematic diagram of a structure of a network device according to this application. As shown in <FIG>, the network device <NUM> includes an antenna <NUM>, a radio frequency apparatus <NUM>, and a baseband apparatus <NUM>. The antenna <NUM> is connected to the radio frequency apparatus <NUM>. In an uplink direction, the radio frequency apparatus <NUM> receives a signal from a terminal device through the antenna <NUM>, and sends the received signal to the baseband apparatus <NUM> for processing. In a downlink direction, the baseband apparatus <NUM> generates a signal that needs to be sent to the terminal device, and sends the generated signal to the radio frequency apparatus <NUM>. The radio frequency apparatus <NUM> transmits the signal through the antenna <NUM>.

The baseband apparatus <NUM> may include one or more processing units <NUM>. The processing unit <NUM> may be specifically a processor.

In addition, the baseband apparatus <NUM> may further include one or more storage units <NUM> and one or more communication interfaces <NUM>. The storage unit <NUM> is configured to store a computer program and/or data. The communication interface <NUM> is configured to exchange information with the radio frequency apparatus <NUM>. The storage unit <NUM> may be specifically a memory, and the communication interface <NUM> may be an input/output interface or a transceiver circuit.

Optionally, the storage unit <NUM> may be a storage unit located on a same chip as the processing unit <NUM>, that is, the storage unit is an on-chip storage unit, or may be a storage unit located on a different chip from the processing unit <NUM>, that is, the storage unit is an off-chip storage unit. This is not limited in this application.

In an implementation procedure, steps in the foregoing method embodiments may be completed by using an integrated logic circuit of hardware in the processor or instructions in a form of software. The processor may be a general purpose processor, a digital signal processor (digital signal processor, DSP), an application-specific integrated circuit (application-specific integrated circuit, ASIC), a field programmable gate array (field programmable gate array, FPGA) or another programmable logic device, a discrete gate or a transistor logic device, or a discrete hardware component. The general purpose processor may be a microprocessor, or the processor may be any conventional processor or the like. The steps of the methods disclosed in embodiments of this application may be directly executed and completed by using a hardware encoding processor, or may be executed and completed by using a combination of hardware and software modules in the encoding processor. The software module may be located in a mature storage medium in the art, for example, a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, and a register. The storage medium is located in the memory, and the processor reads information in the memory and completes the steps in the foregoing methods in combination with hardware of the processor.

The memory in the foregoing embodiments may be a volatile memory or a non-volatile memory, or may include both the volatile memory and the non-volatile memory. The non-volatile memory may be a read-only memory (read-only memory, ROM), a programmable read-only memory (programmable ROM, PROM), an erasable programmable read-only memory (erasable PROM, EPROM), an electrically erasable programmable read-only memory (electrically EPROM, EEPROM), or a flash memory. The volatile memory may be a random access memory (random access memory, RAM), used as an external cache. By way of example but not limitative description, many forms of RAMs may be used, for example, a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), a synchronous dynamic random access memory (synchronous DRAM, SDRAM), a double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), an enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), a synchlink dynamic random access memory (synchlink DRAM, SLDRAM), and a direct rambus dynamic random access memory (direct rambus RAM, DR RAM). It should be noted that memories in the system and method described in this specification are intended to include but are not limited to the memories and memories of any other proper types.

It may be clearly understood by a person skilled in the art that, for the purpose of convenient and brief description, for a detailed working procedure of the foregoing system, apparatus, and unit, refer to a corresponding procedure in the foregoing method embodiments.

For example, the foregoing apparatus embodiment is merely an example. For example, division into the units is merely logical function division and may be other division in actual implementation. The indirect couplings or communication connections between the apparatuses or units may be implemented in an electrical form, a mechanical form, or another form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, in other words, may be located in one location, or may be distributed on a plurality of network units.

In addition, the functional units in embodiments of this application may be integrated into one processing unit, or each of the units may exist alone physically, or two or more units may be integrated into one unit.

When the functions are implemented in the form of a software functional unit and sold or used as an independent product, the functions may be stored in a computer-readable storage medium. Based on such an understanding, the technical solutions of this application essentially, or the part contributing to the prior art, or some of the technical solutions may be implemented in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for instructing a computer device (a personal computer, a server, or a network device) to perform all or some of the steps of the methods in embodiments of this application. The foregoing storage medium includes various media that can store program code, such as a USB flash disk, a removable hard disk, a read-only memory (read-only memory, ROM), a random access memory (random access memory, RAM), a magnetic disk, or a compact disc.

Claim 1:
A resource determining method, the method being performed by a terminal device and comprising:
receiving downlink control information, DCI, from a network device, wherein the DCI is carried on a physical downlink control channel, PDCCH; and
determining (<NUM>) a resource of an uplink channel based on the DCI, wherein the resource of the uplink channel is used to send uplink information;
wherein the uplink channel is a physical uplink control channel, PUCCH, and the PUCCH carries feedback information corresponding to a physical downlink shared channel, PDSCH, scheduled by using the DCI; and
the determining a resource of an uplink channel based on the DCI comprises: determining a carrier on which the PUCCH is located;
the method being characterized by:
determining a resource of the PUCCH based on the carrier on which the PUCCH is located and the DCI; and
wherein the determining a carrier on which the PUCCH is located comprises: when the DCI comprises second indication information, determining a carrier corresponding to a value of the second indication information as the carrier on which the PUCCH is located.