Downlink control information transmission method and related device

Abstract

The present application provides a downlink control information transmission method and related apparatus. In this method, a terminal device receives first configuration information (S102). The first configuration information instructs the terminal device to monitor physical downlink control channel PDCCH candidates in a first scheduling cell and a second scheduling cell, and the PDCCH candidates are used to carry downlink control information for scheduling data transmission in the same scheduled cell. Furthermore, the terminal device determines monitoring upper limits of PDCCH candidates in a first unit time and a second unit time for the same scheduled cell (S103). The first unit time is determined based on a subcarrier interval of an active downlink bandwidth portion in the first scheduling cell, and the second unit time is determined based on a subcarrier interval of an active downlink bandwidth portion in the second scheduling cell. It can be seen that the present application takes into account monitoring upper limits corresponding to two subcarrier intervals, thereby solving the problem of how to determine a monitoring upper limit in a scenario in which two cells schedule the same cell.

Description

[Technical Field]

[0001] The present application relates to the field of communication technologies, and in particular to a downlink control information transmission method and related apparatus. [Background technology]

[0002] This application claims priority to a Chinese patent application entitled "DOWNLINK CONTROL INFORMATION TRANSMISSION METHOD AND RELATED APPARATUS" filed with the State Intellectual Property Office of the People's Republic of China on April 2, 2021, which is incorporated herein by reference in its entirety.

[0003] In a new radio (NR) communication system, a physical downlink control channel (PDCCH) candidate may include L={1, 2, 4, 8, 16} control channel elements (CCEs). The PDCCH may or may not be transmitted on the PDCCH candidate. Thus, a terminal device may monitor (or detect) the PDCCH candidate to determine whether there is a PDCCH for that terminal device.

[0004] In monitoring PDCCH candidates, there are two tasks that significantly affect the implementation complexity of a terminal device: the number of PDCCH candidates to be monitored (also known as the number of blind detections) and the number of non-overlapping CCEs. An increase in the number of PDCCH candidates to be monitored indicates a higher decoding complexity for the terminal device, while an increase in the number of non-overlapping CCEs indicates a higher channel estimation complexity for the terminal device. This ultimately results in a higher implementation complexity for the terminal device. A monitoring upper limit per unit time in a cell may be preset to ensure that the implementation complexity of the terminal device falls within a specific range. The default monitoring upper limit per unit time in a single cell includes the maximum number of PDCCH candidates to be monitored and the maximum number of non-overlapping CCEs. The default monitoring upper limit per unit time in a single cell is related to the value of the subcarrier spacing of the active downlink bandwidth portion in that cell.

[0005] In self-scheduling, data transmission in a cell is scheduled through a PDCCH in that cell, and a predetermined monitoring upper limit of PDCCH candidates per unit time in a single cell monitored by a terminal device can be obtained by querying a table based on the subcarrier spacing of the active downlink bandwidth portion in that cell. In cross-carrier scheduling, for example, data transmission in a primary cell can be simultaneously scheduled by the PDCCH in the primary cell and the PDCCH in a secondary cell, i.e., there are two scheduling cells that schedule the scheduled cell. In this case, how to determine the monitoring upper limit per unit time becomes an urgent problem to be solved. Summary of the Invention

[0006] The present application provides a downlink control information transmission method and related device to solve the problem of how to determine a monitoring upper limit in a scenario where two cells schedule the same cell.

[0007] According to a first aspect, the present application provides a downlink control information transmission method. In the method, a terminal device may receive first configuration information. The first configuration information instructs the terminal device to monitor physical downlink control channel (PDCCH) candidates in a first scheduling cell and a second scheduling cell, where the PDCCH candidates are used to carry downlink control information for scheduling data transmission in the same scheduled cell. The terminal device determines monitoring upper limits for the PDCCH candidates in a first unit time and a second unit time for the same scheduled cell. The first unit time is determined based on a subcarrier spacing of an active downlink bandwidth portion in the first scheduling cell, and the second unit time is determined based on a subcarrier spacing of an active downlink bandwidth portion in the second scheduling cell.

[0008] It can be seen that in this method, the monitoring upper limit of PDCCH candidates in two unit times is determined, in particular, the subcarrier spacings corresponding to the first scheduling cell and the second scheduling cell respectively are taken into consideration, thereby solving the problem of how to determine the monitoring upper limit in a scenario where two scheduling cells schedule the same scheduled cell.

[0009] Furthermore, this downlink control information transmission method is also applicable to a scenario in which the subcarrier spacing is different. For example, the subcarrier spacing corresponding to a first scheduling cell is different from the subcarrier spacing corresponding to a second scheduling cell. In this method, monitoring upper limits for two unit times are determined. This avoids the problem of determining only the monitoring upper limit for one unit time and setting an excessively large monitoring upper limit for the other unit time.

[0010] According to a second aspect, the present application further provides a downlink control information transmission method. This method corresponds to the first aspect, but is described from the perspective of a network device. In this method, the network device transmits first configuration information. The first configuration information instructs a terminal device to monitor physical downlink control channel (PDCCH) candidates in a first scheduling cell and a second scheduling cell, where the PDCCH candidates are used to carry downlink control information for scheduling data transmission in the same scheduled cell. The network device determines monitoring upper limits of the PDCCH candidates in a first unit time and a second unit time for the same scheduled cell. The first unit time is determined based on a subcarrier spacing of an active downlink bandwidth portion in the first scheduling cell, and the second unit time is determined based on a subcarrier spacing of an active downlink bandwidth portion in the second scheduling cell.

[0011] It can be seen that in this method, the monitoring upper limit of PDCCH candidates in two unit times is determined, in particular, the subcarrier spacings corresponding to the first scheduling cell and the second scheduling cell respectively are taken into consideration, thereby solving the problem of how to determine the monitoring upper limit in a scenario where two scheduling cells schedule the same scheduled cell.

[0012] Optionally, this method is also applicable to a scenario in which multiple scheduling cells schedule the same scheduled cell. For example, in a scenario in which a first scheduling cell, a second scheduling cell, and a third scheduling cell schedule the same scheduled cell, a monitoring upper limit of PDCCH candidates from a first time unit to a third time unit may be determined for the scheduled cell. The first time unit is determined based on a subcarrier spacing of an active downlink bandwidth portion in the first scheduling cell, the second time unit is determined based on a subcarrier spacing of an active downlink bandwidth portion in the second scheduling cell, and the third time unit is determined based on a subcarrier spacing of an active downlink bandwidth portion in the third scheduling cell.

[0013] Furthermore, this downlink control information transmission method is also applicable to a scenario in which the subcarrier spacing is different. For example, the subcarrier spacing corresponding to a first scheduling cell is different from the subcarrier spacing corresponding to a second scheduling cell. In this method, monitoring upper limits for two unit times are determined. This avoids the problem of determining only the monitoring upper limit for one unit time and setting an excessively large monitoring upper limit for the other unit time.

[0014] One or more implementations applicable to the first or second aspect will be described below.

[0015] In an optional implementation, the first configuration information includes the following characteristics: Both the first scheduling cell and the second scheduling cell are configured such that the monitoring upper limit is determined at a slot granularity. Both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined at a granularity of a span. The number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool configured for each is 1; The number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool configured for each is 2; The first scheduling cell is configured in a control resource set pool CORESETPool, and the second scheduling cell is not configured in CORESETPool; The first scheduling cell is not configured in the control resource set pool CORESETPool and the second scheduling cell is configured in CORESETPool, or Both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined with a granularity of a span, and monitoring is performed in the first monitoring cell and the second monitoring cell using a combination (X, Y), wherein the second scheduling cell has a symbol group whose starting position overlaps with the starting position of any symbol group in the first scheduling cell, and a symbol group is configured every X symbols, the subcarrier spacing of the active downlink bandwidth portion in the first scheduling cell is greater than the subcarrier spacing of the active downlink bandwidth portion in the second scheduling cell, and the combination (X, Y) indicates that the spacing between the starting symbols of two consecutive spans is greater than or equal to X symbols, and each span is less than or equal to Y symbols. Satisfy one or more of the following:

[0016] It can be seen that in this implementation, the configuration information of the first scheduling cell and the second scheduling cell is limited, which helps to simplify the determination of the upper limit of monitoring PDCCH candidates per unit time.

[0017] The first scheduling cell and the second scheduling cell are both configured so that the monitoring upper limit is determined at slot granularity, which means that the first scheduling cell and the second scheduling cell are not configured with r16 monitoring capability (r16monitoringcapability), or the first scheduling cell and the second scheduling cell are not configured with monitoring capability configuration-r16 (monitoringCapabilityConfig-r16) that is equal to r16 monitoring capability (r16monitoringcapability), or the first scheduling cell and the second scheduling cell are not configured with monitoring capability configuration-r16 (monitoringCapabilityConfig-r16), or The first scheduling cell and the second scheduling cell may each be configured with a monitoring capability configuration-r16 (monitoringCapabilityConfig-r16) equal to r15 monitoring capability (r15monitoringcapability), the first scheduling cell and the second scheduling cell may each be configured with r15 monitoring capability (r15monitoringcapability), or the first scheduling cell may be configured with a monitoring capability configuration-r16 (monitoringCapabilityConfig-r16) equal to r15 monitoring capability (r15monitoringcapability) and the second scheduling cell may not be configured with monitoringCapabilityConfig-r16.

[0018] The first scheduling cell and the second scheduling cell are both configured such that the monitoring upper limit is determined at the granularity of the span, which may mean that the first scheduling cell and the second scheduling cell are each configured with an r16 monitoring capability (r16monitoringcapability), or the first scheduling cell and the second scheduling cell are each configured with a monitoring capability configuration-r16 (monitoringCapabilityConfig-r16) that is equal to the r16 monitoring capability (r16monitoringcapability).

[0019] The control resource set pool CORESETPool configured for the first scheduling cell and the second scheduling cell, respectively, may be a control resource set pool index CORESETPoolIndex configured for the first scheduling cell and the second scheduling cell, respectively. Correspondingly, the number of CORESETPool may also be the number of CORESETPoolIndex.

[0020] In an optional implementation, the monitoring upper limit in the first unit time is determined based on a predefined monitoring upper limit per unit time corresponding to the first scheduling cell, and the monitoring upper limit in the second unit time is determined based on a predefined monitoring upper limit per unit time corresponding to the second scheduling cell.

[0021] Optionally, the monitoring upper limit in each unit time includes a first upper limit in that unit time and / or a second upper limit in that unit time, where the first upper limit is a maximum number of monitored PDCCH candidates and the second upper limit is a maximum number of non-overlapping control channel elements (CCEs) among the monitored PDCCH candidates. The predefined monitoring upper limit per unit time includes a first predefined upper limit and / or a second predefined upper limit, where the first predefined upper limit is a predefined maximum number of monitored PDCCH candidates in that unit time and the second predefined upper limit is a predefined maximum number of non-overlapping CCEs among the monitored PDCCH candidates in that unit time.

[0022] In an optional implementation, for a controlled resource set corresponding to the same CORESETPool, when the first scheduling cell and the second scheduling cell are not configured in the controlled resource set pool CORESETPool, or are configured in the CORESETPool, respectively; when the first scheduling cell is configured in the CORESETPool and the second scheduling cell is not configured in the CORESETPool; when the first scheduling cell is not configured in the CORESETPool and the second scheduling cell is configured in the CORESETPool; or when the first scheduling cell and the second scheduling cell are configured in two CORESETPools, respectively; The monitoring upper limit for the first time unit is: a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit being determined based on a first predefined upper limit corresponding to the first scheduling cell; a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit being determined based on a second predefined upper limit corresponding to the first scheduling cell; a first upper limit corresponding to the first scheduling cell, the first upper limit being determined based on a first predefined upper limit corresponding to the first scheduling cell; and a second upper limit corresponding to the first scheduling cell, the second upper limit being determined based on a second predefined upper limit corresponding to the first scheduling cell; and The monitoring upper limit for the second unit of time is: a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit being determined based on a first predefined upper limit corresponding to the second scheduling cell; a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit being determined based on a second predefined upper limit corresponding to the second scheduling cell; a first upper limit corresponding to the second scheduling cell, the first upper limit being determined based on a first predefined upper limit corresponding to the second scheduling cell; and a second upper limit corresponding to the second scheduling cell, the second upper limit being determined based on a second predefined upper limit corresponding to the second scheduling cell; Contains one or more of:

[0023] It can be seen that in this implementation, the monitoring upper limit in the first unit time is determined such that the first upper limit corresponding to the first scheduling cell or the first upper limit corresponding to the first scheduling cell and the second scheduling cell is determined based on the first predefined upper limit corresponding to the first scheduling cell, and the second upper limit corresponding to the first scheduling cell or the second upper limit corresponding to the first scheduling cell and the second scheduling cell is determined based on the second predefined upper limit corresponding to the first scheduling cell. It can be seen that the monitoring upper limit in the second unit time is determined such that the first upper limit corresponding to the second scheduling cell or the first upper limit corresponding to the first scheduling cell and the second scheduling cell is determined based on the second predefined upper limit corresponding to the second scheduling cell.

[0024] In another implementation, when the first scheduling cell and the second scheduling cell are configured with two control resource set pools CORESETPool, The monitoring upper limit for the first time unit is: a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit being determined based on the third parameter and a first predefined upper limit corresponding to the first scheduling cell; a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit being determined based on the third parameter and a second predetermined upper limit corresponding to the first scheduling cell; a first upper limit corresponding to the first scheduling cell, the first upper limit being determined based on the third parameter and a first predefined upper limit corresponding to the first scheduling cell; and a second upper limit corresponding to the first scheduling cell, the second upper limit being determined based on the third parameter and a second predefined upper limit corresponding to the first scheduling cell; and The monitoring upper limit for the second unit of time is: a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit being determined based on the third parameter and a first predetermined upper limit corresponding to the second scheduling cell; a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit being determined based on the third parameter and a second predetermined upper limit corresponding to the second scheduling cell; a first upper limit corresponding to the second scheduling cell, the first upper limit being determined based on the third parameter and a first predefined upper limit corresponding to the second scheduling cell; and a second upper limit corresponding to the second scheduling cell, the second upper limit being determined based on the third parameter and a second predefined upper limit corresponding to the second scheduling cell; Contains one or more of:

[0025] The third parameter is used to determine the number of cells corresponding to the scheduled cells that are scheduled by the scheduling cells configured in the two CORESETPools.

[0026] It can be seen that in this implementation, the monitoring upper limit in the first unit time is determined such that the first upper limit corresponding to the first scheduling cell or the first upper limit corresponding to the first scheduling cell and the second scheduling cell is determined based on the third parameter and the first predetermined upper limit corresponding to the first scheduling cell, and the second upper limit corresponding to the first scheduling cell or the first and second scheduling cell is determined based on the third parameter and the second predetermined upper limit corresponding to the first scheduling cell. It can be seen that the monitoring upper limit in the second unit time is determined such that the first upper limit corresponding to the second scheduling cell or the first upper limit corresponding to the first and second scheduling cell is determined based on the third parameter and the first predetermined upper limit corresponding to the second scheduling cell, and the second upper limit corresponding to the second scheduling cell or the first and second scheduling cell is determined based on the third parameter and the second predetermined upper limit corresponding to the second scheduling cell. It can be seen that in this implementation, the number of cells corresponding to the scheduled cells (sometimes called the number of logical cells corresponding to the scheduled cells) scheduled by the scheduling cells configured in the two CORESETPools is taken into account.

[0027] In addition to providing a monitoring upper limit in two unit times determined for the same scheduled cell in any one of the above implementations, the present application further provides a monitoring upper limit in one unit time determined for multiple scheduled cells. Specifically, a terminal device determines a monitoring upper limit for all PDCCH candidates in multiple scheduled cells in a unit time having a subcarrier spacing μ for the multiple scheduled cells. The multiple scheduling cells are all scheduling cells configured for the terminal device whose active downlink bandwidth portion has a subcarrier spacing μ, and the multiple scheduled cells are all scheduled cells respectively scheduled by the multiple scheduling cells.

[0028] For multiple scheduled cells, the monitoring upper limit is determined based on a predetermined monitoring upper limit per unit time corresponding to the scheduling cells having a subcarrier spacing of μ. Specifically, the maximum number of all PDCCH candidates is determined based on a predetermined upper limit of PDCCH candidates corresponding to the scheduling cells having a subcarrier spacing of μ, and the upper limit of the number of non-overlapping CCEs among all PDCCH candidates is determined based on a predetermined upper limit of non-overlapping CCEs among PDCCH candidates corresponding to the scheduling cells having a subcarrier spacing of μ.

[0029] According to a third aspect, the present application provides a downlink control information transmission method. In this method, a terminal device receives first configuration information. The first configuration information instructs the terminal device to monitor physical downlink control channel (PDCCH) candidates in a first scheduling cell and a second scheduling cell, where the PDCCH candidates are used to carry downlink control information for scheduling data transmission in the same scheduled cell. The terminal device determines a monitoring upper limit of the PDCCH candidates for the same scheduled cell in a same unit time. The same unit time is determined based on a subcarrier spacing of an active downlink bandwidth portion in the first scheduling cell or the second scheduling cell.

[0030] In this method, it can be seen that when the unit time determined based on the subcarrier spacing of the active downlink bandwidth portion in the first scheduling cell and the unit time determined based on the subcarrier spacing of the active downlink bandwidth portion in the second scheduling cell are the same unit time, i.e., when the subcarrier spacing of the active downlink bandwidth portion in the first scheduling cell is the same as the subcarrier spacing of the active downlink bandwidth portion in the second scheduling cell, the monitoring upper limit of the PDCCH candidates in the same unit time can be determined.

[0031] According to a fourth aspect, the present application further provides a downlink control information transmission method. This method corresponds to the method of the third aspect, but is described from the perspective of a network device. In this method, the network device transmits first configuration information. The first configuration information instructs a terminal device to monitor physical downlink control channel (PDCCH) candidates in a first scheduling cell and a second scheduling cell, where the PDCCH candidates are used to carry downlink control information for scheduling data transmission in the same scheduled cell. The network device determines a monitoring upper limit of the PDCCH candidates in the same unit time for the same scheduled cell. The same unit time is determined based on a subcarrier spacing of an active downlink bandwidth portion in the first scheduling cell or the second scheduling cell.

[0032] In this method, when the unit time determined based on the subcarrier spacing of the active downlink bandwidth portion in the first scheduling cell and the unit time determined based on the subcarrier spacing of the active downlink bandwidth portion in the second scheduling cell are the same unit time, it can be seen that the monitoring upper limit of the PDCCH candidates in the same unit time can be determined.

[0033] In an optional implementation, in the method of the third aspect or the fourth aspect, the first setting information has the following characteristics: Both the first scheduling cell and the second scheduling cell are configured such that the monitoring upper limit is determined at a slot granularity. Both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined at a granularity of a span. The number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool configured for each is 1; The number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool configured for each is 2; The first scheduling cell is configured in the control resource set pool CORESETPool and the second scheduling cell is not configured in CORESETPool, or Both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined with a granularity of a span, and monitoring is performed using a combination (X, Y) in the first monitoring cell and the second monitoring cell; Satisfy one or more of the following:

[0034] The combination (X, Y) indicates that the spacing between the starting symbols of two consecutive spans is at least X symbols, and each span is at most Y symbols.

[0035] In this implementation, the upper limit of the PDCCH candidate monitoring is determined under the above-mentioned constraints, which reduces the implementation complexity of the terminal.

[0036] According to a fifth aspect, the present application further provides a downlink control information transmission method, in which a terminal device receives first configuration information, the first configuration information instructing the terminal device to monitor physical downlink control channel (PDCCH) candidates in a first scheduling cell and a second scheduling cell, the PDCCH candidates being used to carry downlink control information for scheduling data transmission in the same scheduled cell. The first configuration information has the following characteristics: Both the first scheduling cell and the second scheduling cell are configured such that the monitoring upper limit is determined at a slot granularity. Both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined at a granularity of a span. The number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool configured for each is 1; The number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool configured for each is 2; The first scheduling cell is configured in the control resource set pool CORESETPool and the second scheduling cell is not configured in CORESETPool, or Both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined with a granularity of a span, and monitoring is performed in the first monitoring cell and the second monitoring cell using a combination (X, Y), and the second scheduling cell has a symbol group whose starting position overlaps with the starting position of any symbol group in the first scheduling cell, and a symbol group is formed every X symbols, and the combination (X, Y) indicates that the interval between the starting symbols of two consecutive spans is equal to or greater than X symbols, and each span is equal to or less than Y symbols. When one or more of the following conditions are not met, the terminal device determines that no PDCCH candidates are monitored for the scheduled cell.

[0037] It can be seen that in this method, the determination of the monitoring upper limit of the PDCCH candidate can be simplified based on one or more of the above characteristics. Furthermore, the terminal device expects that the first configuration information satisfies one or more of the above characteristics. In other words, the terminal device does not expect that the first configuration information does not have one or more of the above characteristics.

[0038] From another perspective, the terminal device may monitor PDCCH candidates when determining that the first configuration information cannot satisfy one or more of the following characteristics, or the terminal device determines that PDCCH candidates for the scheduled cell will not be monitored when determining that the first configuration information satisfies one or more of the following characteristics: one of the first scheduling cell and the second scheduling cell is configured so that a monitoring upper limit is determined at a slot granularity, and the other scheduling cell is configured so that a monitoring upper limit is determined at a span granularity; the number of CORESETPools set for one of the first scheduling cell and the second scheduling cell is 2, and the number of CORESETPools set for the other scheduling cell is 1; The number of CORESETPools configured for one of the first scheduling cell and the second scheduling cell is 2, and the other scheduling cell is not configured with CORESETPool; Both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined with a granularity of a span, and monitoring is performed using different combinations (X, Y) in the first monitoring cell and the second monitoring cell, where the combination (X, Y) indicates that the interval between the start symbols of two consecutive spans is equal to or greater than X symbols, and each span is equal to or less than Y symbols; or Both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined with a granularity of a span, and monitoring is performed in the first monitoring cell and the second monitoring cell using a combination (X, Y), in which the second scheduling cell has no symbol group whose starting position overlaps with the starting position of at least one symbol group in the first scheduling cell, and a symbol group is configured every X symbols, and the combination (X, Y) indicates that the interval between the starting symbols of two consecutive spans is equal to or greater than X symbols, and each span is equal to or less than Y symbols. is.

[0039] According to a sixth aspect, the present application further provides a downlink control information transmission method, which corresponds to the method of the fifth aspect but is described from the perspective of a network device, wherein the network device is configured to transmit first configuration information, which instructs a terminal device to monitor physical downlink control channel (PDCCH) candidates in a first scheduling cell and a second scheduling cell, the PDCCH candidates being used to carry downlink control information for scheduling data transmission in the same scheduled cell.

[0040] The first setting information has the following characteristics: Both the first scheduling cell and the second scheduling cell are configured such that the monitoring upper limit is determined at a slot granularity. Both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined at a granularity of a span. The number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool configured for each is 1; The number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool configured for each is 2; The first scheduling cell is configured in the control resource set pool CORESETPool and the second scheduling cell is not configured in CORESETPool, or Both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined with a granularity of a span, and monitoring is performed in the first monitoring cell and the second monitoring cell using a combination (X, Y), and the second scheduling cell has a symbol group whose starting position overlaps with the starting position of any symbol group in the first scheduling cell, and a symbol group is formed every X symbols, and the combination (X, Y) indicates that the interval between the starting symbols of two consecutive spans is equal to or greater than X symbols, and each span is equal to or less than Y symbols. Satisfy one or more of the following:

[0041] Furthermore, the network device determines monitoring upper limits for PDCCH candidates in a first unit time and a second unit time for the same scheduled cell, where the first unit time is determined based on a subcarrier spacing of an active bandwidth portion in the first scheduling cell, and the second unit time is determined based on a subcarrier spacing of an active downlink bandwidth portion in the second scheduling cell.

[0042] In this manner, it can be seen that the determination of the monitoring upper limit for PDCCH candidates can be simplified based on one or more of the above characteristics.

[0043] According to a seventh aspect, the present application further provides a downlink control information transmission method, in which a terminal device receives first configuration information, the first configuration information instructing the terminal device to monitor physical downlink control channel (PDCCH) candidates in a first scheduling cell and a second scheduling cell, the PDCCH candidates being used to carry downlink control information for scheduling data transmission in the same scheduled cell. The first configuration information has the following characteristics: Both the first scheduling cell and the second scheduling cell are configured such that the monitoring upper limit is determined at a slot granularity. Both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined at a granularity of a span. The number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool configured for each is 1; The number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool configured for each is 2; The first scheduling cell is configured in the control resource set pool CORESETPool and the second scheduling cell is not configured in CORESETPool, or Both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined with a granularity of a span, and monitoring is performed using a combination (X, Y) in the first monitoring cell and the second monitoring cell; When one or more of the following conditions are not met, the terminal device determines that no PDCCH candidates are monitored for the scheduled cell.

[0044] The combination (X, Y) indicates that the spacing between the starting symbols of two consecutive spans is at least X symbols, and each span is at most Y symbols.

[0045] It can be seen that in this method, the determination of the monitoring upper limit of the PDCCH candidate can be simplified based on one or more of the above characteristics. Furthermore, the terminal device expects that the first configuration information satisfies one or more of the above characteristics. In other words, the terminal device does not expect that the first configuration information does not have one or more of the above characteristics.

[0046] From another perspective, the terminal device may monitor PDCCH candidates when determining that the first configuration information cannot satisfy one or more of the following characteristics, or the terminal device determines that PDCCH candidates for the scheduled cell will not be monitored when determining that the first configuration information satisfies one or more of the following characteristics: one of the first scheduling cell and the second scheduling cell is configured so that a monitoring upper limit is determined at a slot granularity, and the other scheduling cell is configured so that a monitoring upper limit is determined at a span granularity; the number of CORESETPools set for one of the first scheduling cell and the second scheduling cell is 2, and the number of CORESETPools set for the other scheduling cell is 1; The number of CORESETPools configured for one of the first scheduling cell and the second scheduling cell is 2, and the other scheduling cell is not configured with CORESETPool; or Both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined with a granularity of a span, and monitoring is performed using different combinations (X, Y) in the first monitoring cell and the second monitoring cell, where the combination (X, Y) indicates that the interval between the start symbols of two consecutive spans is equal to or greater than X symbols, and each span is equal to or less than Y symbols. is.

[0047] The combination (X, Y) indicates that the spacing between the starting symbols of two consecutive spans is at least X symbols, and each span is at most Y symbols.

[0048] It can be seen that in this method, when the subcarrier spacing of the active downlink bandwidth portion in the first scheduling cell is the same as the subcarrier spacing of the active downlink bandwidth portion in the second scheduling cell, the determination of the monitoring upper limit of the PDCCH candidates can be simplified.

[0049] According to an eighth aspect, the present application further provides a downlink control information transmission method, the method comprising: 7 The present invention corresponds to the method of aspect 1, but is described from the perspective of a network device, in which the network device is configured to transmit first configuration information, the first configuration information instructing a terminal device to monitor physical downlink control channel (PDCCH) candidates in a first scheduling cell and a second scheduling cell, the PDCCH candidates being used to carry downlink control information for scheduling data transmissions in the same scheduled cell.

[0050] The first setting information has the following characteristics: Both the first scheduling cell and the second scheduling cell are configured such that the monitoring upper limit is determined at a slot granularity. Both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined at a granularity of a span. The number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool configured for each is 1; The number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool configured for each is 2; The first scheduling cell is configured in the control resource set pool CORESETPool and the second scheduling cell is not configured in CORESETPool, or Both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined with a granularity of a span, and monitoring is performed using a combination (X, Y) in the first monitoring cell and the second monitoring cell; Satisfy one or more of the following:

[0051] The combination (X, Y) indicates that the spacing between the starting symbols of two consecutive spans is at least X symbols, and each span is at most Y symbols.

[0052] Furthermore, the network device determines a monitoring upper limit of the PDCCH candidates in the same unit time for the same scheduled cell, where the same unit time is determined based on a subcarrier spacing of an active downlink bandwidth portion in the first scheduling cell or the second scheduling cell.

[0053] It can be seen that in this method, when the subcarrier spacing of the active downlink bandwidth portion in the first scheduling cell is the same as the subcarrier spacing of the active downlink bandwidth portion in the second scheduling cell, the determination of the monitoring upper limit of the PDCCH candidates can be simplified.

[0054] It should be noted that the method of any one of the first to eighth aspects of the present application is also applicable to a scenario in which multiple scheduling cells schedule the same scheduled cell. For example, in a scenario in which a first scheduling cell, a second scheduling cell, and a third scheduling cell schedule the same scheduled cell, a monitoring upper limit of PDCCH candidates from a first time unit to a third time unit may be determined for the scheduled cell with reference to the method of the first or second aspect. The first time unit is determined based on a subcarrier spacing of an active downlink bandwidth portion in the first scheduling cell, the second time unit is determined based on a subcarrier spacing of an active downlink bandwidth portion in the second scheduling cell, and the third time unit is determined based on a subcarrier spacing of an active downlink bandwidth portion in the third scheduling cell.

[0055] According to a ninth aspect, the present application provides a communication device including a communication unit and a processing unit, the communication device being configured to implement a method according to any one of the first to eighth aspects or possible implementations of the first to eighth aspects.

[0056] In this aspect, the communication unit may be a transceiver configured to transmit and / or receive data in any one of the first to eighth aspects, and the processing unit may also be a processor configured to process data in any one of the first to eighth aspects.

[0057] According to a tenth aspect, the present application provides a chip system, including at least one processor configured to implement the functions of any one of the first to eighth aspects, such as receiving or processing data and / or information in the above-described method.

[0058] In a possible design, the chip system further includes a memory configured to store program instructions and data. The memory may be located within the processor or external to the processor. The chip system may include the chip, or may include the chip and other discrete components.

[0059] According to an eleventh aspect, the present application further provides a communication device, the communication device including at least one processor and a communication interface. The communication interface is configured to transmit and / or receive data. The at least one processor is configured to invoke a computer program stored in at least one memory to cause the communication device to perform a method according to any one of the first to eighth aspects or possible implementations of the first to eighth aspects.

[0060] According to a twelfth aspect, the present application further provides a downlink control channel transmission system. The downlink control channel transmission system includes at least a network device and a terminal device. The network device is configured to perform a method according to any one of possible implementations of the second, fourth, or eighth aspects. The terminal device is configured to perform a method according to any one of possible implementations of the first, third, or fifth aspects.

[0061] According to a thirteenth aspect, the present application further provides a computer-readable storage medium storing a computer program which, when executed on one or more processors, performs the method according to any one of the first to eighth aspects, or possible implementations of the first to eighth aspects.

[0062] According to a fourteenth aspect, an embodiment of the present application discloses a computer program product, which, when executed on one or more processors, performs a method according to any one of the first to eighth aspects or possible implementations of the first to eighth aspects. [Brief explanation of the drawings]

[0063] [Figure 1] 1 is a schematic diagram of the structure of a communication system according to an embodiment of the present application; [Figure 2] 1 is a schematic diagram of a method for determining a PDCCH monitoring occasion according to an embodiment of the present application; [Figure 3] 1 is a schematic diagram of self-scheduling of a PCell and an SCell, respectively, according to an embodiment of the present application; [Figure 4] FIG. 1 is a schematic diagram of cross-carrier scheduling from a PCell to an SCell according to an embodiment of the present application; [Figure 5] 1 is a schematic diagram showing how both a PCell and an SCell can schedule a PCell according to an embodiment of the present application; [Figure 6] FIG. 2 is a schematic diagram of a span in a slot with subcarrier spacing μ according to an embodiment of the present application; [Figure 7] FIG. 1 is a schematic diagram of a PDCCH monitoring occasion where both a PCell and an SCell can schedule a PCell according to an embodiment of the present application; [Figure 8] 1 is a schematic flow chart of a downlink control information transmission method 100 according to an embodiment of the present application; [Figure 9] 2 is a schematic flow diagram of a downlink control information transmission method 200 according to an embodiment of the present application; [Figure 10] 3 is a schematic flow diagram of a downlink control information transmission method 300 according to an embodiment of the present application. [Figure 11] FIG. 10 illustrates that there are X symbols in CC2 whose starting symbol overlaps with the starting symbol of every X symbols in CC1 according to an embodiment of the present application. [Figure 12] 4 is a schematic flow diagram of a downlink control information transmission method 400 according to an embodiment of the present application. [Figure 13] 13 is a schematic block diagram of a communication device 1300 according to an embodiment of the present application. [Figure 14] 14 is a schematic block diagram of another communication device 1400 according to an embodiment of the present application. [Figure 15] 1 is a schematic block diagram of a chip according to an embodiment of the present application; DETAILED DESCRIPTION OF THE INVENTION

[0064] According to the downlink control information transmission method and related apparatus provided in the present application, for a scenario in which multiple scheduling cells schedule the same scheduled cell, an upper limit of PDCCH candidates that need to be monitored by a terminal device can be determined.

[0065] First, the following describes a communication system to which the embodiments of the present application are applicable.

[0066] In the present application, communication between a network device and a terminal device, and communication between terminal devices, may be performed using a licensed spectrum, an unlicensed spectrum, or both a licensed spectrum and an unlicensed spectrum. Communication between a network device and a terminal device, and communication between terminal devices, may be performed using a sub-6G spectrum, a 6G or higher spectrum, or both a sub-6G spectrum and a 6G or higher spectrum. The spectrum resources used between a network device and a terminal device are not limited in the embodiments of the present application. The present application may be applied to various communication systems, such as a fourth-generation (4G) mobile communication system, a fifth-generation (5G) mobile communication system, and a sixth-generation (6G) mobile communication system. With the continuous development of communication technology, the technical solutions of the embodiments of the present application may further be applied to later evolved communication systems, such as a seventh-generation (7G) mobile communication system.

[0067] In an embodiment of the present application, a network device is an entity configured to transmit or receive signals on the network side, and the network device may be a device having wireless transceiver functionality or a chip that may be disposed within the device. Network devices include, but are not limited to, an evolved NodeB (eNB), an access point (AP), a wireless relay node, a wireless backhaul node, and a transmission reception point (TRP or TP) in a wireless fidelity (Wi-Fi) system. Alternatively, the network device may be a device used in a 4G system, a 5G system, or even a 6G system, such as a gNB in ​​an NR system, or a transmission point (TRP or TP) in a 4G system, or one antenna panel or a group of antenna panels (including multiple antenna panels) of a network device. Alternatively, the network device may be a network node forming a gNB or a transmission point, such as a baseband unit (BBU), a distributed unit (DU), a picocell, a femtocell, or a road side unit (RSU) in an autonomous driving scenario.

[0068] In the embodiments of the present application, a terminal device is an entity configured to receive or transmit signals at a terminal side, and the terminal device may be a device having wireless transceiver functionality or a chip that may be disposed within the device. The terminal device may also be called user equipment (UE), terminal, access terminal, subscriber unit, subscriber station, mobile station, mobile console, remote station, remote terminal, mobile device, user terminal, user agent, or user equipment, and may be used in a 4G system, a 5G system, or even a 6G system. The terminal in the embodiments of the present application may be a mobile phone, a tablet computer (Pad), a computer with wireless transceiver functionality, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self driving, a wireless terminal in telemedicine, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, or an RSU of the above wireless terminals.

[0069] The network devices and terminal devices may be deployed on land, such as indoor devices, outdoor devices, handheld devices, or vehicle-mounted devices, or may be deployed on water, or may be deployed on airborne aircraft, balloons, and satellites. The application scenarios of the radio access network devices and terminal devices are not limited in the embodiments of the present application.

[0070] The present application is applicable to downlink signal transmission, in which the transmitting device is a network device and the corresponding receiving device is a terminal device, and in D2D signal transmission, the transmitting device is a terminal device and the corresponding receiving device is also a terminal device.

[0071] FIG. 1 is a schematic diagram of the structure of a communication system according to an embodiment of the present application. The communication system includes a core network device 110, a radio access network device 120, and at least one terminal device (e.g., terminal device 130 and terminal device 140 in FIG. 1). The terminal device is connected to the radio access network device wirelessly, and the radio access network device is connected to the core network device wirelessly or wired. The core network device and the radio access network device may be independent and different physical devices, or the functions of the core network device and the logical functions of the radio access network device may be integrated into the same physical device, or part of the functions of the core network device and part of the functions of the radio access network device may be integrated into one physical device. The terminal device may be located at a fixed location or may be mobile. FIG. 1 is a schematic diagram. The communication system may further include other network devices not shown in FIG. 1, such as wireless relay devices and wireless backhaul devices. The number of core network devices, radio access network devices, and terminal devices included in this mobile communication system is not limited in this embodiment of the present application. In FIG. 1, for example, the radio access network device is a base station and the terminal device is a mobile phone.

[0072] For example, in the communication system shown in FIG. 1 , a base station may send first configuration information to a mobile phone. The first configuration information instructs the mobile phone to monitor physical downlink control channel candidates (PDCCH candidates) in a first scheduling cell and a second scheduling cell. The PDCCH candidates are used to carry downlink control information for scheduling data transmissions in the same scheduled cell. Furthermore, after receiving the first configuration information, the mobile phone may determine a monitoring upper limit of PDCCH candidates in one or two unit times for the same scheduled cell.

[0073] In another embodiment, the base station transmits first configuration information to a mobile phone, the first configuration information instructing the mobile phone to monitor physical downlink control channel PDCCH candidates in a first scheduling cell and a second scheduling cell, and the first configuration information has the following characteristics: both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined at a slot granularity, both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined at a span granularity, the number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool configured for each is 1, the number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell is the same, The number of CORESETPools to be configured is two; the first scheduling cell is configured with the control resource set pool CORESETPool and the second scheduling cell is not configured with CORESETPool; or both the first scheduling cell and the second scheduling cell are configured such that the monitoring upper limit is determined with a granularity of a span, and monitoring is performed in the first monitoring cell and the second monitoring cell using a combination (X, Y), and the second scheduling cell has a symbol group whose starting position overlaps with the starting position of any symbol group in the first scheduling cell, constituting a symbol group every X symbols, and the combination (X, Y) indicates that the interval between the starting symbols of two consecutive spans is equal to or greater than X symbols and each span is equal to or less than Y symbols.

[0074] In the embodiments provided herein, an NR network scenario in a wireless communication network is used as an example scenario for description. It should be noted that the solutions in the embodiments disclosed herein may also be applied to other wireless communication networks, and the corresponding names may also be replaced with the names of the corresponding functions in the other wireless communication networks.

[0075] In the embodiments provided herein, aspects, embodiments, or features of the present application are presented by describing systems that include multiple devices, components, modules, etc. It is to be appreciated and understood that each system may include other devices, components, modules, etc. and / or may not include all of the devices, components, modules, etc. described with reference to the accompanying drawings. Furthermore, combinations of these solutions may also be used.

[0076] Furthermore, a brief description of related concepts in the embodiments of the present application will be provided.

[0077] 1. Cell

[0078] A cell is described from the perspective of resource management or mobility management by a higher layer (e.g., a protocol layer above the physical layer, such as a radio resource control layer or a medium access control layer). The coverage area of ​​each network device may be divided into one or more cells. A cell is configured with one downlink carrier. Alternatively, optionally, a cell may be configured with at least one uplink carrier. A cell is a general term. For a terminal device, the cell that serves the terminal device is called a serving cell. Therefore, a cell in this application may also be a serving cell.

[0079] In dual connectivity (DC), a terminal device establishes links with multiple cells, which are divided into two groups: a master cell group (MCG) and a secondary cell group (SCG). When dual connectivity is not implemented, the group of cells communicating with the terminal device is the MCG. The primary cell in the MCG is the primary cell (PCell), the primary cell in the SCG is the primary secondary cell (PSCell), and other cells in the MCG and SCG are secondary cells (Scell). The PCell in the MCG and the SCell in the MCG are combined using carrier aggregation (CA) technology. The PSCell in the SCG and the SCell in the SCG are also combined using carrier aggregation technology.

[0080] 2. Subcarrier Spacing

[0081] Subcarrier Spacing (SCS): In NR, there are five subcarrier spacings, and the five subcarrier spacing indices can be from 0 to 4, which can correspond to 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz, respectively.

[0082] Furthermore, the concept of bandwidth part (BWP) is introduced to NR. One BWP is a segment of contiguous frequency resources on one carrier. After a BWP is configured and activated, it is called an active BWP. There can be one active downlink BWP on one downlink carrier, and one active uplink BWP on one uplink carrier. Uplink data and control information transmitted by a UE are transmitted on the active uplink BWP, and downlink data and control information are received on the active downlink BWP.

[0083] In multiple cells connected to a terminal device, the subcarrier spacing of the configured active downlink BWPs may be the same or different, with different subcarrier spacings corresponding to different slot lengths.

[0084] 3. PDCCH Candidates and PDCCH Monitoring Occasions

[0085] The terminal device needs to monitor the PDCCH candidates corresponding to this cell to determine whether there is a PDCCH for the terminal device. The PDCCH candidate for the cell may include L={1, 2, 4, 8, 16} control channel elements (CCEs). L is sometimes referred to as the PDCCH aggregation level (AL). One CCE includes six resource element groups (REGs), and each REG corresponds to one resource block (RB) on one orthogonal frequency division multiplexing (OFDM) symbol.

[0086] A cell may be configured with a search space where AL is L. The search space where AL is L is a set including several PDCCH candidates, each of which has a size of L control channel elements. A search space set (SS set) is a set including search spaces of different ALs. One search space set is associated with one control resource set (CORESET). One CORESET is defined for one cell, and one CORESET includes a group of consecutive or non-consecutive RBs in the frequency domain and one, two, or three consecutive OFDM symbols in the time domain.

[0087] A PDCCH monitoring occasion (PDCCH MO) is also sometimes called a monitoring occasion for short. The PDCCH monitoring occasion of an SS set in a slot is determined using the SS set and the configuration information of a CORESET associated with the SS set. For example, the configuration information of an SS set may include a 14-bit bitmap parameter (monitoringSymbolsWithinSlot). As shown in FIG. 2, each bit has a one-to-one correspondence with one OFDM symbol in a slot and indicates the starting symbol at which the SS set is listened to in a slot. For example, monitoringSymbolsWithinSlot=1000010000000 shown in FIG. 2 indicates that listening in the SS set should start from the first and fifth OFDM symbols in a slot. It is assumed that the SS set is associated with a CORESET having a length of three consecutive OFDM symbols. The PDCCH monitoring occasions of the SS set are PDCCH MO1 and PDCCH MO2 shown in FIG.

[0088] 4. Self-scheduling and cross-career scheduling

[0089] Self-scheduling means that data transmission in a cell is scheduled by a PDCCH in that cell. In other words, downlink control information (DCI) for scheduling data transmission in a cell is carried by a PDCCH in that cell. For example, as shown in Figure 3, a PDCCH in a primary cell (PCell) is used to schedule radio resources in the PCell for transmitting data of the PCell, and a PDCCH in a secondary cell (SCell) is used to schedule radio resources in the SCell for transmitting data of the SCell.

[0090] Cross-carrier scheduling means that data transmission in a cell can be scheduled by a PDCCH in another cell. In other words, DCI for scheduling data transmission in a cell may be carried by a PDCCH in another cell. For example, as shown in Figure 4, a PDCCH in a primary cell (PCell) is used to schedule radio resources in a secondary cell (SCell) for transmitting data of that SCell. A cell carrying a PDCCH, e.g., a PCell, may be referred to as a scheduling cell, and a cell carrying data transmission, e.g., an SCell, may be referred to as a scheduled cell.

[0091] When a data transmission in a cell may be scheduled by the PDCCH of that cell and may also be scheduled by the PDCCH of another cell, multiple scheduling cells may schedule the same scheduled cell. As shown in Figure 5, a data transmission in a PCell may be scheduled by the PDCCH in that PCell and may also be scheduled by the PDCCH in an SCell. In this way, the terminal device needs to monitor PDCCH candidates in each scheduling cell to obtain DCI for scheduling data transmission in the scheduled cell.

[0092] 5. Unit of Time

[0093] In this application, different subcarrier spacings correspond to unit times of different durations. For example, different subcarrier spacings correspond to slots of different durations. Optionally, the unit time may be a span in addition to a slot.

[0094] A slot contains either 14 consecutive OFDM symbols or 12 consecutive OFDM symbols. Different subcarrier spacings correspond to different durations of OFDM symbols in the slot.

[0095] A span, sometimes called a time unit or sub-time unit, is a group of consecutive OFDM symbols in a slot. Any PDCCH monitoring occasion supported by a terminal device is included in a span. The start symbol of a span is the start symbol of the PDCCH monitoring occasion, the end symbol of the span is the end symbol of the PDCCH monitoring occasion, and the maximum number of symbols in a span is Y. When a terminal device monitors PDCCH candidates in a cell using a combination (X, Y), the minimum interval between the start symbols of two consecutive spans in the cell is X symbols, and the two consecutive spans may be in the same slot or between slots.

[0096] For example, as shown in FIG. 6, in a slot having a subcarrier spacing μ, a terminal device monitors PDCCH candidates using a combination (4, 3). The spans within the slot may be those shown in FIG. 6. The minimum interval between the starting symbols of two consecutive spans is 4 symbols, and the maximum number of symbols in one span is 3. For example, the starting symbol of span 1 is symbol 0, the starting symbol of span 2 is symbol 5, and the starting symbol of span 3 is symbol 10. The interval between the starting symbol of span 1 and the starting symbol of span 2 is 4 symbols, and the interval between the starting symbol of span 2 and the starting symbol of span 3 is 4 symbols, and these intervals are equal to or greater than X (i.e., 4). Furthermore, the number of symbols in span 1 is 3, the number of symbols in span 2 is 2, and the number of symbols in span 3 is 3, and each number does not exceed Y (i.e., 3).

[0097] In this application, each unit time is determined based on the subcarrier spacing of the active downlink bandwidth portion in each scheduling cell, i.e., different values ​​of the unit time may be determined based on different subcarrier spacings.

[0098] 6. Monitoring limits and predefined hourly monitoring limits

[0099] In this application, in one case, the monitoring upper limit relates to a unit time and a cell. For example, in a first unit time, the monitoring upper limit is the maximum number of PDCCH candidates to be monitored and the maximum number of non-overlapping CCEs in a first scheduling cell. In another example, in a second unit time, the monitoring upper limit is the maximum number of PDCCH candidates to be monitored and the maximum number of non-overlapping CCEs in a second scheduling cell.

[0100] For example, both the PCell and the SCell can schedule the PCell. As shown in Figure 7, the subcarrier spacing of the active downlink bandwidth portion of the PCell is less than the subcarrier spacing of the active downlink bandwidth portion of the SCell. For example, the subcarrier spacing of the active downlink bandwidth portion of the PCell is 15 kHz, and the subcarrier spacing of the active downlink bandwidth portion of the SCell is 30 kHz. Therefore, the time length of a slot in the PCell is twice the time length of a slot in the SCell. Furthermore, as shown in Figure 7, in one slot in the SCell, the PDCCH monitoring occasion for cross-carrier scheduling of the PCell is radio resource 1, in the next consecutive slot in the SCell, the PDCCH monitoring occasion for cross-carrier scheduling of the PCell is radio resource 2, and in the slot in the PCell, the PDCCH monitoring occasion for self-scheduling is radio resource 3 and radio resource 4.

[0101] In this case, in a slot of the PCell, the maximum number of PDCCH candidates to be monitored in the PCell is the maximum number of PDCCH candidates to be monitored in radio resource 3 and radio resource 4, and in a slot of the PCell, the maximum number of non-overlapping CCEs in the PCell is the maximum number of non-overlapping CCEs in radio resource 3 and radio resource 4.

[0102] In this case, in a slot of an SCell, the maximum number of PDCCH candidates to be monitored in the SCell is the maximum number of PDCCH candidates to be monitored on radio resource 1 or radio resource 2, and in a slot of an SCell, the maximum number of non-overlapping CCEs in the SCell is the maximum number of non-overlapping CCEs on radio resource 1 or radio resource 2.

[0103] In another case, the monitoring upper limit relates to a unit time and a number of cells. For example, in a first unit time, the monitoring upper limit is the maximum total number of all monitored PDCCH candidates and the maximum total number of all non-overlapping CCEs in the first scheduling cell and the second scheduling cell. In another example, in a second unit time, the monitoring upper limit is the maximum total number of all monitored PDCCH candidates and the maximum total number of all non-overlapping CCEs in the first scheduling cell and the second scheduling cell.

[0104] For example, as shown in FIG. 7 , in a slot of an SCell, the maximum total number of PDCCH candidates to be monitored in the SCell and PCell is the maximum total number of PDCCH candidates to be monitored in radio resource 1 and radio resource 3, and the maximum total number of non-overlapping CCEs in the SCell and PCell is the maximum total number of non-overlapping CCEs in radio resource 1 and radio resource 3.

[0105] In a PCell slot, the maximum total number of PDCCH candidates to be monitored in the SCell and PCell is the maximum total number of PDCCH candidates to be monitored on radio resource 1, radio resource 2, radio resource 3, and radio resource 4, and the maximum total number of non-overlapping CCEs in the SCell and PCell is the maximum total number of non-overlapping CCEs on radio resource 1, radio resource 2, radio resource 3, and radio resource 4.

[0106] For ease of explanation, the maximum number of PDCCH candidates to be monitored, whether for one cell or multiple cells, is simply referred to as the first upper limit, and the maximum number of non-overlapping CCEs is simply referred to as the second upper limit. Furthermore, in each unit time, a monitoring upper limit corresponds to one or multiple cells, meaning that each unit time within that unit time must satisfy the monitoring upper limit. For example, as shown in FIG. 5, the monitoring upper limit per span must satisfy the monitoring upper limits in this span, e.g., the first upper limit and the second upper limit. As shown in FIG. 7, in a slot with a subcarrier spacing of 15 kHz, the monitoring upper limit per slot for an SCell must satisfy the monitoring upper limits for the SCell in that slot, e.g., the first upper limit and the second upper limit.

[0107] The predetermined monitoring upper limit per unit time may also be referred to as a predetermined monitoring upper limit per unit time in a single cell, and includes a predetermined maximum number of PDCCH candidates to be monitored in the single cell and a predetermined maximum number of non-overlapping CCEs per unit time. Similarly, for ease of explanation, the predetermined maximum number of PDCCH candidates to be monitored is simply referred to as a first predetermined upper limit, and the predetermined maximum number of non-overlapping CCEs is simply referred to as a second predetermined upper limit.

[0108] In an optional implementation, a predetermined per unit time monitoring upper limit in a single cell, such as the first predetermined upper limit or the second predetermined upper limit, may be obtained by querying a table.

[0109] For example, the subcarrier spacing of the active downlink bandwidth portion in a cell is μ. For a slot with subcarrier spacing μ, the first predefined upper bound corresponding to the cell is

[0110]

number

[0111] and a second predetermined upper bound corresponding to the cell is

[0112]

number

[0113] In this case, Table 1 is obtained when the subcarrier spacing μ corresponds to the indices 0, 1, 2, and 3 separately.

[0114]

number

[0115] Table 2 shows the values ​​obtained when the subcarrier spacing μ corresponds to the indices 0, 1, 2, and 3 separately.

[0116]

number

[0117] As shown in FIG. 7, for each slot with a subcarrier spacing of 15 kHz, the first predetermined upper limit corresponding to the SCell is 44, and the second predetermined upper limit is 56.

[0118] Table 1. Maximum number of monitored PDCCH candidates per slot in a single cell with subcarrier spacing μ in the active downlink bandwidth portion belonging to {0, 1, 2, 3}

[0119]

number

[0120] [Table 1]

[0121] Table 2. Maximum number of non-overlapping CCEs per slot in a single cell with subcarrier spacing μ in the active downlink bandwidth portion belonging to {0, 1, 2, 3}

[0122]

number

[0123] [Table 2]

[0124] For example, the subcarrier spacing of the active downlink bandwidth portion in a cell is μ. For each span of combination (X, Y) in slots with subcarrier spacing μ, the first predetermined upper bound corresponding to the cell is

[0125]

number

[0126] and a second predetermined upper bound corresponding to the cell is

[0127]

number

[0128] In this case, Table 1 is obtained when the subcarrier spacing μ corresponds to indices 0, 1, 2, and 3, respectively, and the combination (2, 2), the combination (4, 3), or the combination (7, 3).

[0129]

number

[0130] Table 2 shows the values ​​obtained when the subcarrier spacing μ corresponds to the indices 0, 1, 2, and 3, respectively, and the combination (2, 2), the combination (4, 3), or the combination (7, 3).

[0131]

number

[0132] Indicates the value of

[0133] Table 3. Maximum number of monitored PDCCH candidates per span for combination (X,Y) in a single cell with subcarrier spacing μ of the active downlink bandwidth portion belonging to {0, 1, 2, 3}

[0134]

number

[0135] [Table 3]

[0136] Table 4. Maximum number of non-overlapping CCEs per span for combination (X,Y) in a single cell with subcarrier spacing μ of the active downlink bandwidth portion belonging to {0, 1, 2, 3}

[0137]

number

[0138] [Table 4]

[0139] Furthermore, for ease of explanation, the predetermined monitoring upper limit per unit time may also be referred to as the predetermined monitoring upper limit per unit time corresponding to a cell, i.e., the predetermined monitoring upper limit per unit time corresponding to the subcarrier spacing of the active downlink bandwidth portion in the cell.

[0140] For ease of explanation, a unit time corresponding to a cell or a scheduling cell in this application is a unit time corresponding to a subcarrier spacing of an active downlink bandwidth portion of the cell or scheduling cell, and a predetermined monitoring upper limit per unit time corresponding to a cell or a scheduling cell is a first predetermined upper limit and / or a second predetermined upper limit in the unit time corresponding to the cell or scheduling cell.

[0141] In an optional implementation, when a cell is configured such that the monitoring upper limit is determined at slot granularity, for example, when the cell is not configured with r16 monitoring capability (r16monitoringcapability), when the cell is not configured with monitoring capability config-r16 (monitoringCapabilityConfig-r16) equal to r16 monitoring capability (r16monitoringcapability), when the cell is not configured with monitoring capability config-r16 (monitoringCapabilityConfig-r16), when the cell is configured with monitoring capability config-r16 (monitoringCapabilityConfig-r16) equal to r15 monitoring capability (r15monitoringcapability), or when the cell is configured with r15 monitoring capability (r15monitoringcapability), the default per unit time monitoring upper limit corresponding to the cell may be determined based on Tables 1 and 2.

[0142] In another optional implementation, when a cell is configured such that the monitoring upper limit is determined at a span granularity, for example, when the cell is configured with an r16 monitoring capability (r16monitoringcapability) or when the cell is configured with a monitoring capability config-r16 (monitoringCapabilityConfig-r16) equal to the r16 monitoring capability (r16monitoringcapability), the default per unit time monitoring upper limit corresponding to the cell may be determined based on Tables 3 and 4.

[0143] Related embodiments provided in the present application will now be described with reference to the accompanying drawings.

[0144] The present application provides a downlink control information transmission method 100. In a scenario where multiple scheduling cells schedule the same scheduled cell, a terminal device or a network device may determine a monitoring upper limit for each unit time. Each unit time is determined based on the subcarrier spacing of the active downlink bandwidth portion in each scheduling cell. The present application is applicable to a scenario where the subcarriers of the active downlink bandwidth portion in the multiple scheduling cells are different.

[0145] The present application provides a downlink control information transmission method 200. In a scenario where multiple scheduling cells schedule the same scheduled cell, a terminal device or a network device may determine a monitoring upper limit in the same unit time. This same unit time is determined based on the subcarrier spacing of the active downlink bandwidth portion in one of the scheduling cells. The present application is applicable to a scenario where the subcarriers of the active downlink bandwidth portion in the multiple scheduling cells are the same.

[0146] The present application provides a downlink control information transmission method 300. In a scenario in which multiple scheduling cells schedule the same scheduled cell, the first configuration information sent by the network device may satisfy one or more of the following characteristics: all of the multiple scheduling cells are configured such that a monitoring upper limit is determined at the granularity of a slot, all of the multiple scheduling cells are configured such that a monitoring upper limit is determined at the granularity of a span, the number of control resource set pools CORESETPool that are configured for each of the multiple scheduling cells is the same, and the number of CORESETPool that is configured for each of the multiple scheduling cells is the same, and the number of CORESETPool that is configured for each of the multiple scheduling cells is two, some of the multiple scheduling cells are each configured with the control resource set pool CORESETPool and other scheduling cells are not configured with CORESETPool, or all of the multiple scheduling cells are configured such that a monitoring upper limit is determined at the granularity of a span, and monitoring is performed using a combination (X, Y) in the multiple monitoring cells. Furthermore, the scheduling cell with the small subcarrier spacing has a symbol group whose starting position overlaps with the starting position of any symbol group in the scheduling cell with the large subcarrier spacing, constituting a symbol group every X symbols. Correspondingly, in this method, the terminal device does not expect the first configuration information to not satisfy one or more of these characteristics, i.e., the terminal device expects the first configuration information to satisfy one or more of these characteristics. According to the downlink control information transmission method 300, determining the monitoring upper limit per unit time can be simplified. Optionally, the downlink control information transmission method 300 can be combined with the downlink control information transmission method 100 or the downlink control information transmission method 200 of the present application to simplify determining the monitoring upper limit per unit time.

[0147] The present application provides a downlink control information transmission method 400. For a plurality of scheduled cells, a monitoring upper limit is determined for all PDCCH candidates in the plurality of scheduling cells within a unit time period having a subcarrier spacing μ. The plurality of scheduling cells are all scheduling cells whose active downlink bandwidth portions have a subcarrier spacing μ, and the plurality of scheduled cells are all scheduled cells that are scheduled by the plurality of scheduling cells, respectively. For the plurality of scheduled cells, the monitoring upper limit is determined based on a predetermined monitoring upper limit per unit time period corresponding to the scheduling cells whose subcarrier spacing μ is μ. It should be understood that the downlink control information transmission method 400 may be combined with any one of the downlink control information transmission method 100, the downlink control information transmission method 200, and the downlink control information transmission method 300 to determine the monitoring upper limit for not only one scheduled cell but also multiple scheduled cells.

[0148] Embodiment 1: Downlink control information transmission method 100

[0149] 8 is a schematic flow chart of a downlink control information transmission method 100 according to an embodiment of the present application. The downlink control information transmission method 100 is described using an example in which a first scheduling cell and a second scheduling cell schedule the same scheduled cell. Optionally, the downlink control information transmission method 100 is also applicable to a scenario in which multiple scheduling cells schedule the same scheduled cell. The same inventive concept exists, and will not be described in detail in this application.

[0150] As shown in FIG. 8, the downlink control information transmission method 100 may include, but is not limited to, the following steps:

[0151] S101: A network device transmits first setting information.

[0152] S102: The terminal device receives first setting information.

[0153] The first configuration information instructs the terminal device to monitor physical downlink control channel PDCCH candidates in the first scheduling cell and the second scheduling cell, where the PDCCH candidates are used to carry downlink control information for scheduling data transmissions in the same scheduled cell, and the terminal device knows that it needs to monitor both the PDCCH candidates in the first scheduling cell and the PDCCH candidates in the second scheduling cell.

[0154] In an optional implementation, in the first configuration information configured by the network device for the terminal device, an identifier of the search space of the first scheduling cell is the same as an identifier of the search space of the second scheduling cell, so that the terminal device may know that physical downlink control channel PDCCH candidates need to be monitored in both the first scheduling cell and the second scheduling cell to obtain DCI for scheduling data transmission in the same scheduled cell.

[0155] S103: The terminal device determines, for the same scheduled cell, monitoring upper limits of PDCCH candidates in a first unit time and a second unit time.

[0156] S104: The network device also determines, for the same scheduled cell, monitoring upper limits of PDCCH candidates in the first time unit and the second time unit.

[0157] The first unit time is determined based on a subcarrier spacing of an active downlink bandwidth portion in the first scheduling cell, and the second unit time is determined based on a subcarrier spacing of an active downlink bandwidth portion in the second scheduling cell. The monitoring upper limit of the PDCCH candidates in the first unit time and the second unit time may further include a monitoring upper limit of the PDCCH candidates in a single scheduling cell in the first unit time and the second unit time, and / or a monitoring upper limit of all PDCCH candidates in the two scheduling cells in the first unit time and the second unit time. Therefore, in steps S103 and S104, the PDCCH candidates may be the PDCCH candidates in a single scheduling cell and / or all PDCCH candidates in the two scheduling cells.

[0158] Optionally, the monitoring upper limit of the PDCCH candidates in the first time unit and the second time unit may also be referred to as an actual monitoring upper limit of the terminal device.

[0159] In an optional implementation, the network device may first determine the first setting information, perform step S104 of determining the actual monitoring upper limit of the terminal device, and then perform step 101 of sending the first setting information to the terminal device, and the terminal device performs steps S102 and S103. In another optional implementation, the network device may jointly determine the first setting information and the actual monitoring upper limit of the terminal device, and then perform step 101 of sending the first setting information to the terminal device, and the terminal device performs steps S102 and S103.

[0160] In an optional implementation, the downlink control information transmission method 100 may further include: a network device sending a PDCCH-related configuration to a terminal device, and then transmitting a PDCCH in each scheduling cell, so that the terminal device monitors PDCCH candidates based on the PDCCH-related configuration and the actual monitoring upper limit to acquire a PDCCH. Optionally, the sequence in which the network device sends the PDCCH-related configuration and the terminal device performs step S103 may not be limited to this embodiment of the present application. The PDCCH-related configuration includes a CORESET configuration and an SS configuration, etc. The UE determines information including PDCCH candidate positions, etc. based on the PDCCH-related configuration, and performs PDCCH candidate monitoring.

[0161] It can be seen that in the downlink control information transmission method 100 shown in FIG. 8 , the monitoring upper limit of PDCCH candidates in two unit times is determined, specifically, the subcarrier intervals corresponding to the first scheduling cell and the second scheduling cell respectively are taken into consideration, thereby solving the problem of how to determine the monitoring upper limit in a scenario where two scheduling cells schedule the same scheduled cell.

[0162] Furthermore, the downlink control information transmission method of this embodiment is applicable to a scenario in which the subcarrier spacing is different. For example, the subcarrier spacing corresponding to a first scheduling cell is different from the subcarrier spacing corresponding to a second scheduling cell. In this method, monitoring upper limits for two unit times are determined. This avoids the problem that only the monitoring upper limit for one unit time is determined, and the monitoring upper limit for the other unit time becomes excessively large.

[0163] For example, as shown in Figure 7, the subcarrier spacing of the SCell is 30 kHz and the subcarrier spacing of the PCell is 15 kHz. The monitoring upper limit of PDCCH candidates in a 30 kHz slot is 36, and the monitoring upper limit of PDCCH candidates in a 15 kHz slot is 44. It is assumed that one of the subcarrier spacings is used as a reference subcarrier spacing, and the monitoring upper limit of PDCCH candidates in a unit time having the reference subcarrier spacing is determined by looking up a table.

[0164] For example, when the 30 kHz subcarrier spacing of the SCell is used as the reference subcarrier spacing, in a 30 kHz slot, the monitoring upper limit of PDCCH candidates in the PCell and SCell is 36; in other words, the monitoring upper limit of PDCCH candidates in radio resource 1 and radio resource 3 is 36, and the monitoring upper limit of PDCCH candidates in radio resource 2 and radio resource 4 is also 36.

[0165] It is assumed that radio resource 1 and radio resource 2 in the SCell are not configured with PDCCH candidates. To satisfy that the monitoring upper limit of PDCCH candidates in the PCell and SCell is 36 in a 30 kHz slot, the monitoring upper limit of PDCCH candidates that needs to be configured for radio resource 3 on the PCell is 36, and the monitoring upper limit of PDCCH candidates that needs to be configured for radio resource 4 on the PCell is 36. The monitoring upper limit of PDCCH candidates on the PCell in a 15 kHz slot is 36 + 36, or 72. However, the monitoring upper limit of PDCCH candidates in a 15 kHz slot is 44. It can be seen that when the monitoring upper limit in a 30 kHz slot is used as the monitoring upper limit of PDCCH candidates corresponding to the PCell and SCell, in some cases, a problem may occur in which the monitoring upper limit of PDCCH candidates corresponding to the PCell exceeds the monitoring upper limit in a 15 kHz slot.

[0166] In another example, when the 15 kHz subcarrier spacing of the PCell is used as the reference subcarrier spacing, in a 15 kHz slot, the monitoring upper limit of the PDCCH candidates corresponding to the PCell and SCell is 44, in other words, the monitoring upper limit of all PDCCH candidates in radio resource 1, radio resource 2, radio resource 3, and radio resource 4 is 44.

[0167] It is assumed that radio resource 1, radio resource 2, and radio resource 4 are not configured with PDCCH candidates. To satisfy that the monitoring upper limit of PDCCH candidates corresponding to PCell and SCell is 44 in a 15 kHz slot, the monitoring upper limit of PDCCH candidates that needs to be configured for radio resource 3 is 44. The monitoring upper limit of PDCCH candidates in a 30 kHz slot is 44. However, the monitoring upper limit of PDCCH candidates in a 30 kHz slot is 36. It can be seen that when the monitoring upper limit in a 15 kHz slot is used as the monitoring upper limit of PDCCH candidates corresponding to PCell and SCell, in some cases, a problem may occur in which the monitoring upper limit of PDCCH candidates corresponding to SCell exceeds the monitoring upper limit in a 30 kHz slot.

[0168] Please refer to Figure 7. The monitoring upper limits of PDCCH candidates in 15 kHz slots and 30 kHz slots are determined by the method of this embodiment of the present application. The monitoring upper limits of PDCCH candidates may include the following three schemes: one scheme is the monitoring upper limit of PDCCH candidates corresponding to PCells and SCells in 15 kHz slots and the monitoring upper limit of PDCCH candidates corresponding to PCells and SCells in 30 kHz slots; another scheme is the monitoring upper limit of PDCCH candidates corresponding to PCells in 15 kHz slots and the monitoring upper limit of PDCCH candidates corresponding to SCells in 30 kHz slots; and yet another scheme is the monitoring upper limit of PDCCH candidates corresponding to PCells in 15 kHz slots, the monitoring upper limit of PDCCH candidates corresponding to SCells in 30 kHz slots, the monitoring upper limit of PDCCH candidates corresponding to PCells and SCells in 15 kHz slots, and the monitoring upper limit of PDCCH candidates corresponding to PCells and SCells in 30 kHz slots. It can be seen that the monitoring upper limits of PDCCH candidates in these three schemes take two unit times into consideration. This avoids the problem that only the monitoring upper limit in one unit time is determined and the actual monitoring upper limit corresponding to a cell is greater than the predetermined per-unit-time monitoring upper limit in the corresponding unit time.

[0169] Some optional implementations of embodiment 1 are described below.

[0170] In an optional implementation, the monitoring upper limit in the first unit time is determined based on a predefined monitoring upper limit per unit time corresponding to the first scheduling cell, and the monitoring upper limit in the second unit time is determined based on a predefined monitoring upper limit per unit time corresponding to the second scheduling cell. It can be seen that the actual monitoring upper limit of the terminal device is related to the first configuration information and the predefined monitoring upper limit per unit time.

[0171] As described above, the predefined upper limit per unit time corresponding to each cell may be obtained by querying a table based on the subcarrier spacing of the active downlink bandwidth portion in that cell. Optionally, when both the first scheduling cell and the second scheduling cell are configured such that the monitoring upper limit is determined at a slot granularity, the predefined upper limit per unit time corresponding to each scheduling cell may be determined based on Tables 1 and 2. Optionally, when both the first scheduling cell and the second scheduling cell are configured such that the monitoring upper limit is determined at a span granularity, the predefined upper limit per unit time corresponding to each scheduling cell may be determined based on Tables 3 and 4.

[0172] Optionally, in this implementation, the monitoring upper limit in each unit time may alternatively be determined in a different manner based on the number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell. Hereinafter, Implementation 1.1 and Implementation 1.2 will be used separately for description.

[0173] Implementation 1.1: The monitoring upper limit in each unit time is determined based on the default monitoring upper limit per unit time in the scheduling cell corresponding to that unit time.

[0174] In Implementation 1.1, an explanation is provided using an example in which the monitoring upper limit includes a first upper limit and / or a second upper limit, and correspondingly, the predetermined per unit time monitoring upper limit includes a first predetermined upper limit and / or a second predetermined upper limit.

[0175] For controlled resource sets corresponding to the same CORESETPool, when the first scheduling cell and the second scheduling cell are not configured in the controlled resource set pool CORESETPool, or are configured in the CORESETPool, respectively; when the first scheduling cell is configured in the CORESETPool and the second scheduling cell is not configured in the CORESETPool; when the first scheduling cell is not configured in the CORESETPool and the second scheduling cell is configured in the CORESETPool; or when the first scheduling cell and the second scheduling cell are configured in two CORESETPools, respectively; The monitoring upper limit for the first unit time is: a first upper limit corresponding to the first scheduling cell and the second scheduling cell, wherein the first upper limit corresponding to the first scheduling cell and the second scheduling cell is determined based on a first predefined upper limit corresponding to the first scheduling cell; and a second upper limit corresponding to the first scheduling cell and the second scheduling cell, wherein the second upper limit corresponding to the first scheduling cell and the second scheduling cell is determined based on a second predetermined upper limit corresponding to the first scheduling cell; and a first upper limit corresponding to the first scheduling cell, where the first upper limit corresponding to the first scheduling cell is determined based on a first predefined upper limit corresponding to the first scheduling cell; and a second upper limit corresponding to the first scheduling cell, where the second upper limit corresponding to the first scheduling cell is determined based on a second predetermined upper limit corresponding to the first scheduling cell; and may include one or more of: The monitoring upper limit for the second unit of time is a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit being determined based on a first predefined upper limit corresponding to the second scheduling cell; and a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit being determined based on a second predetermined upper limit corresponding to the second scheduling cell; and a first upper limit corresponding to the second scheduling cell, where the first upper limit is determined based on a first predefined upper limit corresponding to the second scheduling cell; and a second upper limit corresponding to the second scheduling cell, where the second upper limit is determined based on a second predefined upper limit corresponding to the second scheduling cell; and may include one or more of:

[0176] For example, in the scenario shown in Figure 7, both the PCell and SCell are configured so that the monitoring upper limit is determined at slot granularity. For the controlled resource sets corresponding to the same CORESETPool, when the PCell and SCell are not configured in the controlled resource set pool CORESETPool, or are configured in CORESETPool, when the PCell is configured in CORESETPool and the SCell is not configured in CORESETPool, when the PCell is not configured in CORESETPool and the SCell is configured in CORESETPool, or when the PCell and SCell are configured in two CORESETPools, The monitoring limits for 15kHz slots are: a first upper limit corresponding to the PCell and the SCell, the first upper limit corresponding to the PCell and the SCell being determined based on a first predefined upper limit for a 15 kHz slot in Table 1, i.e., 44; a second upper limit corresponding to the PCell and the SCell, the second upper limit corresponding to the PCell and the SCell being determined based on the second predefined upper limit for a 15 kHz slot in Table 2, i.e., 56; a first upper limit corresponding to the PCell, the first upper limit being determined based on the first predefined upper limit for a 15 kHz slot in Table 1, i.e., 44; and a second upper limit corresponding to the PCell, the second upper limit being determined based on a second predefined upper limit for a 15 kHz slot in Table 2, i.e., 56; may include one or more of: The monitoring limits for 30kHz slots are: a first upper limit corresponding to the PCell and SCell, the first upper limit being determined based on the first predefined upper limit for a 30 kHz slot in Table 1, i.e., 36; a second upper limit corresponding to the PCell and SCell, the second upper limit being determined based on the second predefined upper limit for 30 kHz slots in Table 2, i.e., 56; a first upper limit corresponding to the SCell, the first upper limit being determined based on the first predefined upper limit for a 30 kHz slot in Table 1, i.e., 36; and a second upper limit corresponding to the SCell, the second upper limit being determined based on the second predefined upper limit for 30 kHz slots in Table 2, i.e., 56; may include one or more of:

[0177] It can be seen that in this implementation, the monitoring upper limit in the 15 kHz slot and the monitoring upper limit in the 30 kHz slot may be determined based on Tables 1 and 2 as the actual monitoring upper limits of the terminal device.

[0178] In another example, in the scenario shown in Figure 7, both the PCell and SCell are configured such that the monitoring upper limit is determined at the granularity of the span, and the span satisfies the combination (X, Y). For the controlled resource sets corresponding to the same CORESETPool, when the PCell and SCell are not configured in the controlled resource set pool CORESETPool, or are configured in CORESETPool, when the PCell is configured in CORESETPool and the SCell is not configured in CORESETPool, when the PCell is not configured in CORESETPool and the SCell is configured in CORESETPool, or when the PCell and SCell are configured in two CORESETPools, The monitoring limits for a 15 kHz span for the (X,Y) combination are as follows: a first upper limit corresponding to the PCell and the SCell, the first upper limit corresponding to the PCell and the SCell being determined based on a first predefined upper limit in a 15 kHz span of the combination (X, Y) in Table 3; a second upper limit corresponding to the PCell and the SCell, the second upper limit corresponding to the PCell and the SCell being determined based on a second predefined upper limit in a 15 kHz span for the combination (X, Y) in Table 4; a first upper limit corresponding to the PCell, the first upper limit being determined based on a first predefined upper limit in a 15 kHz span for the combination (X, Y) in Table 3; and a second upper limit corresponding to the PCell, the second upper limit being determined based on a second predefined upper limit in a 15 kHz span for the combination (X, Y) in Table 4; may include one or more of: The monitoring limits for a 30 kHz span for the (X,Y) combination are as follows: a first upper limit corresponding to the PCell and the SCell, the first upper limit being determined based on a first predefined upper limit in a 30 kHz span for the combination (X, Y) in Table 3; a second upper limit corresponding to the PCell and the SCell, the second upper limit being determined based on a second predetermined upper limit in a 30 kHz span for the combination (X, Y) in Table 4; a first upper limit corresponding to the SCell, the first upper limit being determined based on a first predefined upper limit in a 30 kHz span for the combination (X, Y) in Table 3; and a second upper limit corresponding to the SCell, the second upper limit being determined based on a second predetermined upper limit in a 30 kHz span for the combination (X, Y) in Table 4; may include one or more of:

[0179] It can be seen that in this implementation, the monitoring upper limit in the 15 kHz slot and the monitoring upper limit in the 30 kHz slot may be determined as the actual monitoring upper limit of the terminal device based on Tables 1 and 2. Alternatively, in this implementation, the monitoring upper limit in the 15 kHz span of the combination (X, Y) and the monitoring upper limit in the 30 kHz span of the combination (X, Y) may be determined as the actual monitoring upper limit of the terminal device based on Tables 3 and 4.

[0180] Implementation 1.2: The monitoring upper limit in each unit time is determined based on the third parameter and the default monitoring upper limit per unit time in the scheduling cell corresponding to that unit time. The third parameter is used to determine the number of cells corresponding to the scheduled cells scheduled by the scheduling cells configured in the two CORESETPools.

[0181] Similarly, in Implementation 1.2, an explanation is provided using an example in which the monitoring upper limit includes a first upper limit and / or a second upper limit, and correspondingly, the predetermined per unit time monitoring upper limit includes a first predetermined upper limit and / or a second predetermined upper limit.

[0182] When the first scheduling cell and the second scheduling cell are respectively configured with two control resource set pools CORESETPool, The monitoring upper limit for the first time unit is: a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit corresponding to the first scheduling cell and the second scheduling cell being determined based on the third parameter and a first predefined upper limit corresponding to the first scheduling cell; a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit corresponding to the first scheduling cell being determined based on the third parameter and a second predetermined upper limit corresponding to the first scheduling cell; a first upper limit corresponding to the first scheduling cell, the first upper limit being determined based on the third parameter and a first predefined upper limit corresponding to the first scheduling cell; and a second upper limit corresponding to the first scheduling cell, the second upper limit corresponding to the first scheduling cell being determined based on the third parameter and a second predefined upper limit corresponding to the first scheduling cell; may include one or more of: The monitoring upper limit for the second unit of time is: a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit being determined based on the third parameter and a first predetermined upper limit corresponding to the second scheduling cell; a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit being determined based on the third parameter and a second predetermined upper limit corresponding to the second scheduling cell; a first upper limit corresponding to the second scheduling cell, the first upper limit being determined based on the third parameter and a first predefined upper limit corresponding to the second scheduling cell; and a second upper limit corresponding to the second scheduling cell, the second upper limit being determined based on the third parameter and a second predefined upper limit corresponding to the second scheduling cell; may include one or more of:

[0183] For example, in the scenario shown in Figure 7, both the PCell and SCell are configured such that the monitoring upper limit is determined at slot granularity. When the PCell and SCell are each configured with two control resource set pools CORESETPool, the third parameter is assumed to be γ. In this case, the monitoring upper limit in a 15 kHz slot is as follows: a first upper bound corresponding to the PCell and the SCell, the first upper bound corresponding to the PCell and the SCell being determined based on γ and a first predefined upper bound (i.e., 44) for a 15 kHz slot in Table 1; a second upper bound corresponding to the PCell and SCell, determined based on γ and a second predefined upper bound (i.e., 56) for a 15 kHz slot in Table 2; a first upper limit corresponding to the PCell, determined based on γ and a first predefined upper limit (i.e., 44) for a 15 kHz slot in Table 1; and a second upper limit corresponding to the PCell, determined based on γ and a second predefined upper limit (i.e., 56) for a 15 kHz slot in Table 2; may include one or more of: The monitoring limits for 30kHz slots are: a first upper limit corresponding to the PCell and SCell, the first upper limit being determined based on γ and a first predefined upper limit (i.e., 36) for a 30 kHz slot in Table 1; a second upper limit corresponding to the PCell and SCell, the second upper limit being determined based on γ and a second predefined upper limit (i.e., 56) for a 30 kHz slot in Table 2; a first upper limit corresponding to the SCell, the first upper limit being determined based on γ and a first predefined upper limit (i.e., 36) for a 30 kHz slot in Table 1; and a second upper limit corresponding to the SCell, the second upper limit being determined based on γ and a second predefined upper limit (i.e., 56) for a 30 kHz slot in Table 2; may include one or more of:

[0184] It can be seen that in this implementation, the monitoring upper limit in the 15 kHz slot and the monitoring upper limit in the 30 kHz slot may be determined based on γ, Table 1, and Table 2 as the actual monitoring upper limit of the terminal device.

[0185] In another example, in the scenario shown in Figure 7, both the PCell and SCell are configured such that the monitoring upper limit is determined at the granularity of the span, and the span satisfies the combination (X, Y). When the PCell and SCell are configured with two control resource set pools CORESETPool, respectively, the third parameter is assumed to be γ. In this case, The monitoring limits for a 15 kHz span for the (X,Y) combination are as follows: a first upper limit corresponding to the PCell and the SCell, the first upper limit corresponding to the PCell and the SCell being determined based on γ and a first predefined upper limit in a 15 kHz span for the combination (X, Y) in Table 3; a second upper limit corresponding to the PCell and the SCell, the second upper limit corresponding to the PCell and the SCell being determined based on γ and a second predetermined upper limit in a 15 kHz span for the combination (X, Y) in Table 4; a first upper limit corresponding to the PCell, the first upper limit being determined based on γ and a first predefined upper limit in a 15 kHz span for the combination (X, Y) in Table 3; and a second upper limit corresponding to the PCell, the second upper limit being determined based on γ and a second predefined upper limit in a 15 kHz span for the combination (X, Y) in Table 4; may include one or more of: The monitoring limits for a 30 kHz span for the (X,Y) combination are as follows: a first upper limit corresponding to the PCell and the SCell, the first upper limit being determined based on γ and a first predefined upper limit in a 30 kHz span for the combination (X, Y) in Table 3; a second upper limit corresponding to the PCell and SCell, the second upper limit being determined based on γ and a second predetermined upper limit in a 30 kHz span for the combination (X, Y) in Table 4; a first upper limit corresponding to the SCell, the first upper limit being determined based on γ and a first predefined upper limit in a 30 kHz span for the combination (X, Y) in Table 3; and a first upper limit corresponding to the SCell, the first upper limit being determined based on γ and a second predetermined upper limit in a 30 kHz span for the combination (X, Y) in Table 4; may include one or more of:

[0186] In this implementation, it can be seen that the monitoring upper limit in the 15 kHz span of the combination (X, Y) and the monitoring upper limit in the 30 kHz span of the combination (X, Y) may be determined as the actual monitoring upper limit of the terminal device based on γ, Table 3, and Table 4.

[0187] In Implementation 1.1 provided in this embodiment of the present application (specifically, for a CORESET corresponding to the same CORESETPool, the first scheduling cell and the second scheduling cell are not configured in the two CORESETPools, respectively, or the first scheduling cell and the second scheduling cell are configured in the two CORESETPools, respectively), three implementations are described based on whether the first scheduling cell and the second scheduling cell are configured with a first parameter corresponding to the first scheduling cell and the second scheduling cell, or whether the first scheduling cell and the second scheduling cell are configured with a first parameter and a second parameter, respectively, to specifically determine the monitoring upper limit of PDCCH candidates in the first unit time and the second unit time. The first parameter is used to determine the number of cells corresponding to scheduled cells that are scheduled by the scheduling cell. Optionally, this number of cells may also be referred to as the number of logical cells. Hereinafter, Implementations 1.1.1 to 1.1.3 will be used separately for the description.

[0188] Implementation 1.1.1: The first scheduling cell and the second scheduling cell are not configured with the first parameters corresponding to the first scheduling cell and the second scheduling cell.

[0189] The monitoring upper limit of the PDCCH candidates in the first time unit and the second time unit may be:

[0190] The monitoring upper limit for the first unit time is: The scheduling information may include a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit corresponding to the first scheduling cell and the second scheduling cell being equal to a first predetermined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit corresponding to the first scheduling cell being equal to a second predetermined upper limit corresponding to the first scheduling cell.

[0191] The monitoring upper limit for the second unit of time is: The scheduling limit may include one or more of: a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit corresponding to the first scheduling cell and the second scheduling cell being equal to a first predefined upper limit corresponding to the second scheduling cell; and / or a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit corresponding to the first scheduling cell and the second scheduling cell being equal to a second predefined upper limit corresponding to the second scheduling cell.

[0192] For example, in the scenario shown in Figure 7, both the PCell and the SCell are configured such that the monitoring upper limit is determined at the granularity of a slot. For control resource sets corresponding to the same CORESETPool, when the PCell and the SCell are not configured in the control resource set pool CORESETPool, or are configured in the CORESETPool, when the PCell is configured in the CORESETPool and the SCell is not configured in the CORESETPool, when the PCell is not configured in the CORESETPool and the SCell is configured in the CORESETPool, or when the PCell and the SCell are configured in two CORESETPools, and when the PCell and the SCell are not configured with the first parameters corresponding to the PCell and the SCell, respectively, the monitoring upper limits of the PDCCH candidates in the 15 kHz slot and the 30 kHz slot may be, respectively, as follows:

[0193] The monitoring limit for 15kHz slots is a first upper limit corresponding to the PCell and SCell, the first upper limit corresponding to the PCell and SCell being equal to the first predefined upper limit in a 15 kHz slot in Table 1, i.e., 44; and A second upper limit corresponding to the PCell and SCell, which is equal to the second predetermined upper limit in a 15 kHz slot in Table 2, i.e., 56. It may include:

[0194] The monitoring limit for 30kHz slots is a first upper limit corresponding to the PCell and SCell, the first upper limit corresponding to the PCell and SCell being equal to the first predetermined upper limit in a 30 kHz slot in Table 1, i.e., 36; and A second upper limit corresponding to the PCell and SCell, which is equal to the second predetermined upper limit in a 30 kHz slot in Table 2, i.e., 56. It may include:

[0195] It can be seen that in a 15 kHz slot, the maximum total number of PDCCH candidates in the PCell and SCell is 44, and the maximum total number of non-overlapping CCEs in the PCell and SCell is 56, and in a 30 kHz slot, the maximum total number of PDCCH candidates in the PCell and SCell is 36, and the maximum total number of non-overlapping CCEs in the PCell and SCell is 56. Therefore, this not only solves the problem of how to determine the monitoring upper limit in a unit time when both the PCell and the SCell schedule the PCell, but also avoids the problem that the first upper limit and the second upper limit corresponding to the PCell and the SCell are determined based on only one unit time, and the first upper limit and the second upper limit corresponding to one cell in another unit time are not satisfied.

[0196] Furthermore, in the scenario shown in Figure 7, if both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a span, it is also the same as in the above example. The difference is that different default monitoring upper limits per unit time are used for different unit times. Therefore, the details will not be repeated here.

[0197] Implementation 1.1.2: The first scheduling cell and the second scheduling cell are configured with a first parameter corresponding to the first scheduling cell and the second scheduling cell. The first parameter is assumed to be a.

[0198] The monitoring upper limits of the PDCCH candidates in the first time unit and the second time unit may be:

[0199] The monitoring upper limit for the first unit time is: a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit corresponding to the first scheduling cell being equal to the product of a and a first predefined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to the first scheduling cell and the second scheduling cell being equal to the product of a and a second predefined upper limit corresponding to the first scheduling cell; a first upper limit corresponding to the first scheduling cell, the first upper limit corresponding to the first scheduling cell being equal to a first predefined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to the first scheduling cell, the second upper limit corresponding to the first scheduling cell being equal to a second predefined upper limit corresponding to the first scheduling cell; It may include:

[0200] The monitoring upper limit for the second unit of time is a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit corresponding to the first scheduling cell and the second scheduling cell being equal to the product of a and a first predefined upper limit corresponding to the second scheduling cell, and / or a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit corresponding to the first scheduling cell and the second scheduling cell being equal to the product of a and a second predefined upper limit corresponding to the second scheduling cell; a first upper limit corresponding to the second scheduling cell, the first upper limit corresponding to the second scheduling cell being equal to a first predefined upper limit corresponding to the second scheduling cell, and / or a second upper limit corresponding to the second scheduling cell, the second upper limit corresponding to the second scheduling cell being equal to a second predefined upper limit corresponding to the second scheduling cell; It may include:

[0201] For example, in the scenario shown in Figure 7, both the PCell and the SCell are configured such that the monitoring upper limit is determined at the granularity of a slot. For control resource sets corresponding to the same CORESETPool, when the PCell and the SCell are not configured in the control resource set pool CORESETPool, or are configured in the CORESETPool, when the PCell is configured in the CORESETPool and the SCell is not configured in the CORESETPool, when the PCell is not configured in the CORESETPool and the SCell is configured in the CORESETPool, or when the PCell and the SCell are configured in two CORESETPools, and when the PCell and the SCell are not configured with the first parameters corresponding to the PCell and the SCell, respectively, the monitoring upper limits of the PDCCH candidates in the 15 kHz slot and the 30 kHz slot may be, respectively, as follows:

[0202] The monitoring limit for 15kHz slots is a first upper limit corresponding to the PCell and SCell, the first upper limit corresponding to the PCell and SCell being equal to the product of a and the first predefined upper limit for a 15 kHz slot in Table 1, i.e., 44a; a second upper limit corresponding to the PCell and SCell, the second upper limit corresponding to the PCell and SCell being equal to the product of a and the second predefined upper limit for a 15 kHz slot in Table 2, i.e., 56a; a first upper limit corresponding to the PCell, the first upper limit corresponding to the PCell being equal to the first predefined upper limit for a 15 kHz slot in Table 1, i.e., 44; and A second upper limit corresponding to the PCell, which is equal to the second predetermined upper limit in a 15 kHz slot in Table 2, i.e., 56. It may include:

[0203] In other words, a terminal device does not need to monitor more than 44 a total of PDCCH candidates and more than 56 a total of non-overlapping CCEs in the PCell and SCell in a 15 kHz slot, and a terminal device does not need to monitor more than 44 total of PDCCH candidates and more than 56 total of non-overlapping CCEs in a 15 kHz slot.

[0204] Furthermore, the monitoring limit for 30kHz slots is a first upper limit corresponding to the PCell and SCell, the first upper limit corresponding to the PCell and SCell being equal to the product of a and the first predefined upper limit for a 30 kHz slot in Table 1, i.e., 36a; a second upper limit corresponding to the PCell and SCell, the second upper limit corresponding to the PCell and SCell being equal to the product of a and the second predetermined upper limit for a 30 kHz slot in Table 2, i.e., 56a; a first upper limit corresponding to the SCell, which is equal to the first predetermined upper limit in a 30 kHz slot in Table 1, i.e., 36; and a second upper limit corresponding to the SCell, which is equal to the second predetermined upper limit in a 30 kHz slot in Table 2, i.e., 56; It may include:

[0205] In other words, a terminal device does not need to monitor more than 36a PDCCH candidates and 56a non-overlapping CCEs in total in a PCell and SCell in a 30 kHz slot, and a terminal device does not need to monitor more than 36 PDCCH candidates and 56 non-overlapping CCEs in a SCell in a 30 kHz slot.

[0206] It can be seen that in a 15 kHz slot, the maximum total number of PDCCH candidates in a PCell and an SCell is 44a, the maximum total number of non-overlapping CCEs in a PCell and an SCell is 56a, the maximum number of PDCCH candidates in a PCell is 44, and the maximum number of non-overlapping CCEs in a PCell is 56, and in a 30 kHz slot, the maximum total number of PDCCH candidates in a PCell and an SCell is 36a, the maximum total number of non-overlapping CCEs in a PCell and an SCell is 56a, the maximum number of PDCCH candidates in an SCell is 36, and the maximum number of non-overlapping CCEs in an SCell is 56. Therefore, this not only solves the problem of how to determine the monitoring upper limit in a unit time when both a PCell and an SCell schedule a PCell, but also avoids the problem that the first upper limit and the second upper limit corresponding to a PCell and an SCell are determined based on only one unit time, and the first upper limit and the second upper limit corresponding to a cell in another unit time are not satisfied.

[0207] Furthermore, in the scenario shown in Figure 7, if both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a span, it is also the same as in the above example. The difference is that different default monitoring upper limits per unit time are used for different unit times. Therefore, the details will not be repeated here.

[0208] Implementation 1.1.3: A first scheduling cell is configured with a first parameter, which is represented by a1. A second scheduling cell is configured with a second parameter, which is represented by a2. The first parameter a1 is used to determine the number of cells corresponding to scheduled cells scheduled by the first scheduling cell, and the second parameter a2 is used to determine the number of cells corresponding to scheduled cells scheduled by the second scheduling cell.

[0209] In the solution of Implementation 1.1.3, the monitoring upper limits of the PDCCH candidates in the first time unit and the second time unit may be respectively:

[0210] The monitoring upper limit for the first unit time is: a first upper limit corresponding to the first scheduling cell, the first upper limit corresponding to the first scheduling cell being equal to the product of a1 and a first predefined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to the first scheduling cell, the second upper limit corresponding to the first scheduling cell being equal to the product of a1 and a second predefined upper limit corresponding to the first scheduling cell; Includes.

[0211] The monitoring upper limit for the second unit of time is a first upper limit corresponding to the second scheduling cell, the first upper limit corresponding to the second scheduling cell being equal to the product of a2 and a first predefined upper limit corresponding to the second scheduling cell, and / or a second upper limit corresponding to the second scheduling cell, the second upper limit corresponding to the second scheduling cell being equal to the product of a2 and a second predefined upper limit corresponding to the second scheduling cell; It may include:

[0212] For example, in the scenario shown in Figure 7, both the PCell and the SCell are configured such that the monitoring upper limit is determined at slot granularity. For control resource sets corresponding to the same CORESETPool, when the PCell and the SCell are not configured in the control resource set pool CORESETPool, or are configured in the CORESETPool, when the PCell is configured in the CORESETPool and the SCell is not configured in the CORESETPool, when the PCell is not configured in the CORESETPool and the SCell is configured in the CORESETPool, or when the PCell and the SCell are configured in two CORESETPools, and when the PCell is configured in a1 and the SCell is configured in a2, the monitoring upper limits of the PDCCH candidates in the 15 kHz slot and the 30 kHz slot may be, respectively, as follows:

[0213] The monitoring limit for 15kHz slots is a first upper limit corresponding to the PCell, the first upper limit being equal to the product of a1 and the first predefined upper limit for a 15 kHz slot in Table 1, i.e., 44a1; and A second upper limit corresponding to the PCell, which is equal to the product of a1 and the second predetermined upper limit for a 15 kHz slot in Table 2, i.e., 56a1. It may include:

[0214] In other words, a terminal device need not monitor more than 44a1 PDCCH candidates and 56a1 non-overlapping CCEs in a PCell in a 15 kHz slot.

[0215] Furthermore, the monitoring limit for 30kHz slots is a first upper limit corresponding to the SCell, the first upper limit being equal to the product of a2 and the first predefined upper limit for a 30 kHz slot in Table 1, i.e., 36a2; and A second upper limit corresponding to the SCell, which is equal to the product of a2 and the second predetermined upper limit for the 30 kHz slot in Table 2, i.e., 56a2. It may include:

[0216] In other words, a terminal device does not need to monitor more than 36a2 PDCCH candidates and 56a2 non-overlapping CCEs in an SCell in a 30 kHz slot.

[0217] It can be seen that with this solution, a terminal device does not need to monitor more than 44a1 PDCCH candidates and more than 56a1 non-overlapping CCEs in a PCell in a 15 kHz slot, and a terminal device does not need to monitor more than 36a2 PDCCH candidates and more than 56a2 non-overlapping CCEs in an SCell in a 30 kHz slot. Therefore, this not only solves the problem of how to determine the monitoring upper limit in a unit time when both a PCell and an SCell schedule a PCell, but also avoids the problem that the monitoring upper limit in one unit time is determined based only on that unit time and the monitoring upper limit in another unit time is not met.

[0218] Furthermore, in the scenario shown in Figure 7, if both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a span, it is also the same as in the above example. The difference is that different default monitoring upper limits per unit time are used for different unit times. Therefore, the details will not be repeated here.

[0219] In another solution of Implementation 1.1.3, the monitoring upper limits of the PDCCH candidates in the first time unit and the second time unit may be:

[0220] The monitoring upper limit for the first unit time is: a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit corresponding to the first scheduling cell and the second scheduling cell being equal to the product of (a1+a2) and a first predefined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit corresponding to the first scheduling cell being equal to the product of (a1+a2) and a second predefined upper limit corresponding to the first scheduling cell; a first upper limit corresponding to the first scheduling cell, the first upper limit corresponding to the first scheduling cell being equal to a first predefined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to the first scheduling cell, the second upper limit corresponding to the first scheduling cell being equal to a second predefined upper limit corresponding to the first scheduling cell; Includes.

[0221] The monitoring upper limit for the second unit of time is a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit corresponding to the first scheduling cell and the second scheduling cell being equal to the product of (a1+a2) and a first predefined upper limit corresponding to the second scheduling cell, and / or a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit corresponding to the first scheduling cell and the second scheduling cell being equal to the product of (a1+a2) and a second predefined upper limit corresponding to the second scheduling cell; and a first upper limit corresponding to the second scheduling cell, the first upper limit corresponding to the second scheduling cell being equal to a first predefined upper limit corresponding to the second scheduling cell, and / or a second upper limit corresponding to the second scheduling cell, the second upper limit corresponding to the second scheduling cell being equal to a second predefined upper limit corresponding to the second scheduling cell; It may include:

[0222] For example, in the scenario shown in Figure 7, both the PCell and the SCell are configured such that the monitoring upper limit is determined at slot granularity. For control resource sets corresponding to the same CORESETPool, when the PCell and the SCell are not configured in the control resource set pool CORESETPool, or are configured in the CORESETPool, when the PCell is configured in the CORESETPool and the SCell is not configured in the CORESETPool, when the PCell is not configured in the CORESETPool and the SCell is configured in the CORESETPool, or when the PCell and the SCell are configured in two CORESETPools, and when the PCell is configured in a1 and the SCell is configured in a2, the monitoring upper limits of the PDCCH candidates in the 15 kHz slot and the 30 kHz slot may be, respectively, as follows:

[0223] The monitoring limit for 15kHz slots is a first upper limit corresponding to the PCell and SCell, the first upper limit corresponding to the PCell and SCell being equal to the product of (a1+a2) and the first pre-defined upper limit for a 15 kHz slot in Table 1, i.e., 44(a1+a2); and a second upper limit corresponding to the PCell and SCell, the second upper limit corresponding to the PCell and SCell being equal to the product of (a1+a2) and the second pre-defined upper limit for a 15 kHz slot in Table 1, i.e., 56(a1+a2); a first upper limit corresponding to the PCell, the first upper limit corresponding to the PCell being equal to the first predefined upper limit for a 15 kHz slot in Table 1, i.e., 44; and a second upper limit corresponding to the PCell, the second predefined upper limit corresponding to the PCell being equal to the second predefined upper limit for a 15 kHz slot in Table 2, i.e., 56. It may include:

[0224] In other words, a terminal device does not need to monitor more than 44 (a1+a2) PDCCH candidates and more than 56 (a1+a2) non-overlapping CCEs in the PCell and SCell in a 15 kHz slot, and a terminal device does not need to monitor more than 44 PDCCH candidates and more than 56 non-overlapping CCEs in the PCell in a 15 kHz slot.

[0225] Furthermore, the monitoring limit for 30kHz slots is a first upper limit corresponding to the PCell and SCell, the first upper limit corresponding to the PCell and SCell being equal to the product of (a1+a2) and the first pre-defined upper limit for a 30 kHz slot in Table 1, i.e., 36(a1+a2); and a second upper limit corresponding to the PCell and SCell, the second upper limit corresponding to the PCell and SCell being equal to the product of (a1+a2) and the second pre-defined upper limit for a 30 kHz slot in Table 1, i.e., 56(a1+a2); and a first upper limit corresponding to the SCell, which is equal to the first predefined upper limit for a 30 kHz slot in Table 1, i.e., 36; and a second upper limit corresponding to the SCell, which is equal to the second predefined upper limit for a 30 kHz slot in Table 2, i.e., 56. It may include:

[0226] In other words, a terminal device does not need to monitor more than 36 (a1+a2) PDCCH candidates and 56 (a1+a2) non-overlapping CCEs in total in the PCell and SCell in a 30 kHz slot, and a terminal device does not need to monitor more than 36 PDCCH candidates and 56 non-overlapping CCEs in the SCell in a 30 kHz slot.

[0227] It can be seen that with this solution, a terminal device does not need to monitor more than 44 (a1+a2) PDCCH candidates and more than 56 (a1+a2) non-overlapping CCEs in total in the PCell and SCell in a 15 kHz slot, and the terminal device does not need to monitor more than 44 PDCCH candidates and more than 56 non-overlapping CCEs in the PCell in a 15 kHz slot. The terminal device does not need to monitor more than 36 (a1+a2) PDCCH candidates and more than 56 (a1+a2) non-overlapping CCEs in total in the PCell and SCell in a 30 kHz slot, and the terminal device does not need to monitor more than 36 PDCCH candidates and more than 56 non-overlapping CCEs in the SCell in a 30 kHz slot. Therefore, this not only solves the problem of how to determine the monitoring upper limit in a unit time when both the PCell and the SCell schedule the PCell, but also avoids the problem that the monitoring upper limit in one unit time is determined based only on that unit time and the monitoring upper limit in another unit time is not met.

[0228] Furthermore, in the scenario shown in Figure 7, if both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a span, it is also the same as in the above example. The difference is that different default monitoring upper limits per unit time are used for different unit times. Therefore, the details will not be repeated here.

[0229] In yet another solution of Implementation 1.1.3, the monitoring upper limits of the PDCCH candidates in the first time unit and the second time unit may be:

[0230] The monitoring upper limit for the first unit time is: a first upper limit corresponding to the first scheduling cell, the first upper limit corresponding to the first scheduling cell being equal to a first predefined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to the first scheduling cell, the second upper limit corresponding to the first scheduling cell being equal to a second predefined upper limit corresponding to the first scheduling cell; Includes:

[0231] The monitoring upper limit for the second unit of time is a first upper limit corresponding to the second scheduling cell, the first upper limit corresponding to the second scheduling cell being equal to a first predefined upper limit corresponding to the second scheduling cell, and / or a second upper limit corresponding to the second scheduling cell, the second upper limit corresponding to the second scheduling cell being equal to a second predefined upper limit corresponding to the second scheduling cell; It may include:

[0232] For example, in the scenario shown in Figure 7, both the PCell and the SCell are configured such that the monitoring upper limit is determined at slot granularity. For control resource sets corresponding to the same CORESETPool, when the PCell and the SCell are not configured in the control resource set pool CORESETPool, or are configured in the CORESETPool, when the PCell is configured in the CORESETPool and the SCell is not configured in the CORESETPool, when the PCell is not configured in the CORESETPool and the SCell is configured in the CORESETPool, or when the PCell and the SCell are configured in two CORESETPools, and when the PCell is configured in a1 and the SCell is configured in a2, the monitoring upper limits of the PDCCH candidates in the 15 kHz slot and the 30 kHz slot may be, respectively, as follows:

[0233] The monitoring limit for 15kHz slots is a first upper limit corresponding to the PCell, where the first upper limit corresponding to the PCell is equal to the first predefined upper limit for a 15 kHz slot in Table 1, i.e., 44; and a second upper limit corresponding to the PCell, where the second upper limit corresponding to the PCell is equal to the second predefined upper limit for a 15 kHz slot in Table 2, i.e., 56. It may include:

[0234] In other words, a terminal device need not monitor more than 44 PDCCH candidates and 56 non-overlapping CCEs in a PCell in a 15 kHz slot.

[0235] Furthermore, the monitoring limit for 30kHz slots is a first upper limit corresponding to the SCell, where the first upper limit corresponding to the SCell is equal to the first predetermined upper limit for a 30 kHz slot in Table 1, i.e., 36; and a second upper limit corresponding to the SCell, where the second upper limit corresponding to the SCell is equal to the second predetermined upper limit for a 30 kHz slot in Table 2, i.e., 56. It may include:

[0236] In other words, a terminal device need not monitor more than 36 PDCCH candidates and 56 non-overlapping CCEs in an SCell in a 30 kHz slot.

[0237] It can be seen that with this solution, a terminal device does not need to monitor more than 44 PDCCH candidates and 56 non-overlapping CCEs in a PCell in a 15 kHz slot, and a terminal device does not need to monitor more than 36 PDCCH candidates and 56 non-overlapping CCEs in an SCell in a 30 kHz slot. Therefore, this not only solves the problem of how to determine the monitoring upper limit in a unit time when both a PCell and an SCell schedule a PCell, but also avoids the problem that the monitoring upper limit in one unit time is determined based only on that unit time and the monitoring upper limit in another unit time is not met.

[0238] Furthermore, the case where both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a span is also the same as the above example. The difference is that different default monitoring upper limits per unit time are used for different unit times. Therefore, the details will not be repeated here.

[0239] In Implementation 1.2 provided in this embodiment of the present application (specifically, the first scheduling cell and the second scheduling cell are configured with two CORESETPools, respectively), three implementations are described to specifically determine the monitoring upper limit of PDCCH candidates in the first and second unit times, depending on whether the first scheduling cell and the second scheduling cell are configured with a first parameter corresponding to the first scheduling cell and the second scheduling cell, or whether the first scheduling cell and the second scheduling cell are configured with a first parameter and a second parameter, respectively. The first parameter is used to determine the number of cells corresponding to the scheduled cells that are scheduled by the scheduling cell. Optionally, this number of cells may also be referred to as the number of logical cells. Hereinafter, Implementations 1.2.1 to 1.2.3 will be described separately. The third parameter is represented as γ.

[0240] Implementation 1.2.1: The first scheduling cell and the second scheduling cell are not configured with the first parameters corresponding to the first scheduling cell and the second scheduling cell.

[0241] The monitoring upper limit of the PDCCH candidates in the first time unit and the second time unit may be:

[0242] The monitoring upper limit for the first unit time is: a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit corresponding to the first scheduling cell being equal to the product of γ and a first predefined upper limit corresponding to the first scheduling cell; and / or a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit corresponding to the first scheduling cell being equal to the product of γ and a second predetermined upper limit corresponding to the first scheduling cell; It may include:

[0243] The monitoring upper limit for the second unit of time is: a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit corresponding to the first scheduling cell and the second scheduling cell being equal to the product of γ and a first predefined upper limit corresponding to the second scheduling cell; and / or a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit being equal to the product of γ and a second predetermined upper limit corresponding to the second scheduling cell; It may include:

[0244] For example, in the scenario shown in Figure 7, both the PCell and the SCell are configured such that the monitoring upper limit is determined at slot granularity. When the PCell and the SCell are configured with two control resource set pools CORESETPool, respectively, and the PCell and the SCell are not configured with the first parameters corresponding to the PCell and the SCell, respectively, the monitoring upper limits of the PDCCH candidates in the 15 kHz slot and the 30 kHz slot may be as follows:

[0245] The monitoring limit for 15kHz slots is a first upper limit corresponding to the PCell and SCell, the first upper limit corresponding to the PCell and SCell being equal to the product of γ and the first predefined upper limit for a 15 kHz slot in Table 1, i.e., 44γ; and A second upper limit corresponding to the PCell and SCell, which is equal to the product of γ and the second predetermined upper limit for a 15 kHz slot in Table 2, i.e., 56γ. It may include:

[0246] The monitoring limit for 30kHz slots is a first upper limit corresponding to the PCell and SCell, the first upper limit corresponding to the PCell and SCell being equal to the product of γ and the first predefined upper limit for a 30 kHz slot in Table 1, i.e., 36γ; and A second upper limit corresponding to the PCell and SCell, which is equal to the product of γ and the second predetermined upper limit for a 30 kHz slot in Table 2, i.e., 56γ. It may include:

[0247] It can be seen that in a 15 kHz slot, the maximum total number of PDCCH candidates in the PCell and SCell is 44γ, and the maximum total number of non-overlapping CCEs in the PCell and SCell is 56γ, and in a 30 kHz slot, the maximum total number of PDCCH candidates in the PCell and SCell is 36γ, and the maximum total number of non-overlapping CCEs in the PCell and SCell is 56γ. Therefore, this not only solves the problem of how to determine the monitoring upper limit in a unit time when both the PCell and the SCell schedule the PCell, but also avoids the problem that the first upper limit and the second upper limit corresponding to the PCell and the SCell are determined based on only one unit time, and the first upper limit and the second upper limit corresponding to one cell in another unit time are not satisfied.

[0248] Furthermore, the case where both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a span is also the same as the above example. The difference is that different default monitoring upper limits per unit time are used for different unit times. Therefore, the details will not be repeated here.

[0249] Implementation 1.2.2: The first scheduling cell and the second scheduling cell are configured with a first parameter corresponding to the first scheduling cell and the second scheduling cell. The first parameter is assumed to be a.

[0250] The monitoring upper limits of the PDCCH candidates in the first time unit and the second time unit may be:

[0251] The monitoring upper limit for the first unit time is: a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit corresponding to the first scheduling cell and the second scheduling cell being equal to the product of a·γ and a first predefined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit corresponding to the first scheduling cell being equal to the product of a·γ and a second predefined upper limit corresponding to the first scheduling cell; a first upper limit corresponding to the first scheduling cell, the first upper limit corresponding to the first scheduling cell being equal to the product of γ and a first predefined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to the first scheduling cell, the second upper limit corresponding to the first scheduling cell being equal to the product of γ and a second predefined upper limit corresponding to the first scheduling cell; It may include:

[0252] The monitoring upper limit for the second unit of time is a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit corresponding to the first scheduling cell and the second scheduling cell being equal to the product of a·γ and a first predefined upper limit corresponding to the second scheduling cell, and / or a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit corresponding to the first scheduling cell and the second scheduling cell being equal to the product of a·γ and a second predefined upper limit corresponding to the second scheduling cell; a first upper limit corresponding to the second scheduling cell, the first upper limit corresponding to the second scheduling cell being equal to the product of γ and a first predefined upper limit corresponding to the second scheduling cell, and / or a second upper limit corresponding to the second scheduling cell, the second upper limit corresponding to the second scheduling cell being equal to the product of γ and a second predefined upper limit corresponding to the second scheduling cell; It may include:

[0253] For example, in the scenario shown in Figure 7, both the PCell and the SCell are configured such that the monitoring upper limit is determined at slot granularity. When the PCell and the SCell are configured with two control resource set pools CORESETPool, respectively, and the PCell and the SCell are configured with the first parameter a corresponding to the PCell and the SCell, the monitoring upper limits of the PDCCH candidates in the 15 kHz slot and the 30 kHz slot may be, respectively, as follows:

[0254] The monitoring limit for 15kHz slots is a first upper limit corresponding to the PCell and SCell, the first upper limit corresponding to the PCell and SCell being equal to the product of a·γ and the first predefined upper limit for a 15 kHz slot in Table 1, i.e., 44a·γ; a second upper limit corresponding to the PCell and SCell, the second upper limit corresponding to the PCell and SCell being equal to the product of a·γ and the second predetermined upper limit for a 15 kHz slot in Table 2, i.e., 56a·γ; a first upper limit corresponding to the PCell, the first upper limit being equal to the product of γ and the first predefined upper limit for a 15 kHz slot in Table 1, i.e., 44γ; and A second upper limit corresponding to the PCell, which is equal to the product of γ and the second predetermined upper limit for a 15 kHz slot in Table 2, i.e., 56γ. It may include:

[0255] In other words, a terminal device does not need to monitor a total of more than 44a·γ PDCCH candidates and more than 56a·γ non-overlapping CCEs in the PCell and SCell in a 15 kHz slot, and a terminal device does not need to monitor more than 44γ PDCCH candidates and more than 56γ non-overlapping CCEs in the PCell in a 15 kHz slot.

[0256] Furthermore, the monitoring limit for 30kHz slots is a first upper limit corresponding to the PCell and SCell, the first upper limit corresponding to the PCell and SCell being equal to the product of a·γ and the first predefined upper limit for a 30 kHz slot in Table 1, i.e., 36a·γ; a second upper limit corresponding to the PCell and SCell, the second upper limit corresponding to the PCell and SCell being equal to the product of a·γ and the second predetermined upper limit for a 30 kHz slot in Table 2, i.e., 56a·γ; a first upper limit corresponding to the SCell, the first upper limit being equal to the product of γ and the first predefined upper limit for a 30 kHz slot in Table 1, i.e., 36γ; and a second upper limit corresponding to the SCell, the second upper limit being equal to the product of γ and the second predefined upper limit for a 30 kHz slot in Table 2, i.e., 56γ; It may include:

[0257] In other words, a terminal device does not need to monitor a total of more than 36a·γ PDCCH candidates and more than 56a·γ non-overlapping CCEs in a PCell and SCell in a 30 kHz slot, and a terminal device does not need to monitor more than 36γ PDCCH candidates and more than 56γ non-overlapping CCEs in a SCell in a 30 kHz slot.

[0258] It can be seen that for a 15 kHz slot, the maximum total number of PDCCH candidates in the PCell and SCell is 44α·γ, the maximum total number of non-overlapping CCEs in the PCell and SCell is 56α·γ, the maximum number of PDCCH candidates in the PCell is 44γ, and the maximum number of non-overlapping CCEs in the PCell is 56γ, and for a 30 kHz slot, the maximum total number of PDCCH candidates in the PCell and SCell is 36α·γ, the maximum total number of non-overlapping CCEs in the PCell and SCell is 56α·γ, the maximum number of PDCCH candidates in the SCell is 36γ, and the maximum number of non-overlapping CCEs in the SCell is 56γ. Therefore, this not only solves the problem of how to determine the monitoring upper limit in a unit time when both the PCell and the SCell schedule the PCell, but also avoids the problem that the first and second upper limits corresponding to the PCell and the SCell are determined based on only one unit time, and the first and second upper limits corresponding to one cell in another unit time are not satisfied.

[0259] Furthermore, the case where both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a span is also the same as the above example. The difference is that different default monitoring upper limits per unit time are used for different unit times. Therefore, the details will not be repeated here.

[0260] Implementation 1.2.3: The first scheduling cell is configured with a first parameter, which is represented by a1. The second scheduling cell is configured with a second parameter, which is represented by a2. The first parameter a1 is used to determine the number of cells corresponding to scheduled cells scheduled by the first scheduling cell, and the second parameter a2 is used to determine the number of cells corresponding to scheduled cells scheduled by the second scheduling cell.

[0261] In the solution of Implementation 1.2.3, the monitoring upper limits of the PDCCH candidates in the first time unit and the second time unit may be respectively:

[0262] The monitoring upper limit for the first unit time is: a first upper limit corresponding to the first scheduling cell, the first upper limit corresponding to the first scheduling cell being equal to the product of a1·γ and a first predefined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to the first scheduling cell, the second upper limit corresponding to the first scheduling cell being equal to the product of a1·γ and a second predefined upper limit corresponding to the first scheduling cell Includes:

[0263] The monitoring upper limit for the second unit of time is a first upper limit corresponding to the second scheduling cell, the first upper limit corresponding to the second scheduling cell being equal to the product of a2·γ and a first predefined upper limit corresponding to the second scheduling cell, and / or a second upper limit corresponding to the second scheduling cell, the second upper limit corresponding to the second scheduling cell being equal to the product of a2·γ and a second predefined upper limit corresponding to the second scheduling cell It may include:

[0264] For example, in the scenario shown in Figure 7, both the PCell and the SCell are configured such that the monitoring upper limit is determined at slot granularity. When the PCell and the SCell are configured with two control resource set pools, CORESETPool, respectively, and the PCell is configured with a1 and the SCell is configured with a2, the monitoring upper limits of the PDCCH candidates in the 15 kHz slot and the 30 kHz slot may be as follows, respectively:

[0265] The monitoring limit for 15kHz slots is a first upper limit corresponding to the PCell, the first upper limit being equal to the product of a1·γ and the first predefined upper limit for a 15 kHz slot in Table 1, i.e., 44a1·γ; and A second upper limit corresponding to the PCell, which is equal to the product of a1·γ and the second predetermined upper limit for a 15 kHz slot in Table 2, i.e., 56a1·γ. It may include:

[0266] In other words, a terminal device need not monitor more than 44a1·γ PDCCH candidates and 56a1·γ non-overlapping CCEs in a PCell in a 15 kHz slot.

[0267] Furthermore, the monitoring limit for 30kHz slots is a first upper limit corresponding to the SCell, the first upper limit being equal to the product of a1·γ and the first predefined upper limit for a 30 kHz slot in Table 1, i.e., 36a1·γ; and A second upper limit corresponding to the SCell, which is equal to the product of a1·γ and the second predetermined upper limit for the 30 kHz slot in Table 2, i.e., 56a1·γ. It may include:

[0268] In other words, a terminal device does not need to monitor more than 36a1·γ PDCCH candidates and 56a1·γ non-overlapping CCEs in an SCell in a 30 kHz slot.

[0269] It can be seen that with this solution, a terminal device does not need to monitor more than 44a1·γ PDCCH candidates and more than 56a1·γ non-overlapping CCEs in a PCell in a 15 kHz slot, and a terminal device does not need to monitor more than 36a1·γ PDCCH candidates and more than 56a1·γ non-overlapping CCEs in an SCell in a 30 kHz slot. Therefore, this not only solves the problem of how to determine the monitoring upper limit in a unit time when both a PCell and an SCell schedule a PCell, but also avoids the problem of the monitoring upper limit in one unit time being determined based only on that unit time and the monitoring upper limit in another unit time not being met.

[0270] Furthermore, the case where both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a span is also the same as the above example. The difference is that different default monitoring upper limits per unit time are used for different unit times. Therefore, the details will not be repeated here.

[0271] In another solution of Implementation 1.2.3, the monitoring upper limits of the PDCCH candidates in the first time unit and the second time unit may be:

[0272] The monitoring upper limit for the first unit time is: a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit corresponding to the first scheduling cell and the second scheduling cell being equal to the product of (a1+a2)·γ and a first predefined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit corresponding to the first scheduling cell being equal to the product of (a1+a2)·γ and a second predefined upper limit corresponding to the first scheduling cell; a first upper limit corresponding to the first scheduling cell, the first upper limit corresponding to the first scheduling cell being equal to the product of γ and a first predefined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to the first scheduling cell, the second upper limit corresponding to the first scheduling cell being equal to the product of γ and a second predefined upper limit corresponding to the first scheduling cell; Includes.

[0273] The monitoring upper limit for the second unit of time is a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit corresponding to the first scheduling cell and the second scheduling cell being equal to the product of (a1+a2)·γ and a first predefined upper limit corresponding to the second scheduling cell, and / or a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit corresponding to the first scheduling cell and the second scheduling cell being equal to the product of (a1+a2)·γ and a second predefined upper limit corresponding to the second scheduling cell; a first upper limit corresponding to the second scheduling cell, the first upper limit corresponding to the second scheduling cell being equal to the product of γ and a first predefined upper limit corresponding to the second scheduling cell, and / or a second upper limit corresponding to the second scheduling cell, the second upper limit corresponding to the second scheduling cell being equal to the product of γ and a second predefined upper limit corresponding to the second scheduling cell; It may include:

[0274] For example, in the scenario shown in Figure 7, both the PCell and the SCell are configured such that the monitoring upper limit is determined at slot granularity. When the PCell and the SCell are configured with two control resource set pools, CORESETPool, respectively, and the PCell is configured with a1 and the SCell is configured with a2, the monitoring upper limits of the PDCCH candidates in the 15 kHz slot and the 30 kHz slot may be as follows, respectively:

[0275] The monitoring limit for 15kHz slots is a first upper limit corresponding to the PCell and SCell, the first upper limit corresponding to the PCell and SCell being equal to the product of (a1+a2)·γ and the first predefined upper limit for a 15 kHz slot in Table 1, i.e., 44(a1+a2)·γ; and a second upper limit corresponding to the PCell and SCell, the second upper limit corresponding to the PCell and SCell being equal to the product of (a1+a2)·γ and the second predefined upper limit for a 15 kHz slot in Table 1, i.e., 56(a1+a2)·γ; and a first upper limit corresponding to the PCell, the first upper limit corresponding to the PCell being equal to the product of γ and the first predefined upper limit for the 15 kHz slot in Table 1, i.e., 44γ; and a second upper limit corresponding to the PCell, the second upper limit corresponding to the PCell being equal to the product of γ and the second predefined upper limit for the 15 kHz slot in Table 2, i.e., 56γ. It may include:

[0276] In other words, a terminal device does not need to monitor more than 44(a1+a2)·γ PDCCH candidates and more than 56(a1+a2)·γ non-overlapping CCEs in a PCell and SCell in a 15 kHz slot, and a terminal device does not need to monitor more than 44γ PDCCH candidates and more than 56γ non-overlapping CCEs in a PCell in a 15 kHz slot.

[0277] Furthermore, the monitoring limit for 30kHz slots is a first upper limit corresponding to the PCell and SCell, the first upper limit corresponding to the PCell and SCell being equal to the product of (a1+a2)·γ and the first predefined upper limit for a 30 kHz slot in Table 1, i.e., 36(a1+a2)·γ; and a second upper limit corresponding to the PCell and SCell, the second upper limit corresponding to the PCell and SCell being equal to the product of (a1+a2)·γ and the second predefined upper limit for a 30 kHz slot in Table 1, i.e., 56(a1+a2)·γ; and a first upper limit corresponding to the SCell, the first upper limit being equal to the product of γ and the first predefined upper limit for a 30 kHz slot in Table 1, i.e., 36γ; and a second upper limit corresponding to the SCell, the second upper limit being equal to the product of γ and the second predefined upper limit for a 30 kHz slot in Table 2, i.e., 56γ. It may include:

[0278] In other words, the terminal device does not need to monitor a total of more than 36(a1+a2)·γ PDCCH candidates and more than 56(a1+a2)·γ non-overlapping CCEs in the PCell and SCell in a 30 kHz slot, and the terminal device does not need to monitor more than 36γ PDCCH candidates and more than 56γ non-overlapping CCEs in the SCell in a 30 kHz slot.

[0279] It can be seen that with this solution, the terminal device does not need to monitor more than 44(a1+a2)·γ PDCCH candidates and more than 56(a1+a2)·γ non-overlapping CCEs in total in the PCell and SCell in a 15 kHz slot, and the terminal device does not need to monitor more than 44γ PDCCH candidates and more than 56γ non-overlapping CCEs in the PCell in a 15 kHz slot. The terminal device does not need to monitor more than 36(a1+a2)·γ PDCCH candidates and more than 56(a1+a2)·γ non-overlapping CCEs in total in the PCell and SCell in a 30 kHz slot, and the terminal device does not need to monitor more than 36γ PDCCH candidates and more than 56γ non-overlapping CCEs in the SCell in a 30 kHz slot. Therefore, this not only solves the problem of how to determine the monitoring upper limit in a unit time when both the PCell and the SCell schedule the PCell, but also avoids the problem that the monitoring upper limit in one unit time is determined based only on that unit time, and the monitoring upper limit in another unit time is not met.

[0280] Furthermore, the case where both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a span is also the same as the above example. The difference is that different default monitoring upper limits per unit time are used for different unit times. Therefore, the details will not be repeated here.

[0281] In yet another solution of Implementation 1.2.3, the monitoring upper limits of the PDCCH candidates in the first time unit and the second time unit may be:

[0282] The monitoring upper limit for the first unit time is: a first upper limit corresponding to the first scheduling cell, the first upper limit corresponding to the first scheduling cell being equal to the product of γ and a first predefined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to the first scheduling cell, the second upper limit corresponding to the first scheduling cell being equal to the product of γ and a second predefined upper limit corresponding to the first scheduling cell; Includes:

[0283] The monitoring upper limit for the second unit of time is a first upper limit corresponding to the second scheduling cell, the first upper limit corresponding to the second scheduling cell being equal to the product of γ and a first predefined upper limit corresponding to the second scheduling cell, and / or a second upper limit corresponding to the second scheduling cell, the second upper limit corresponding to the second scheduling cell being equal to the product of γ and a second predefined upper limit corresponding to the second scheduling cell; It may include:

[0284] For example, in the scenario shown in Figure 7, both the PCell and the SCell are configured such that the monitoring upper limit is determined at slot granularity. When the PCell and the SCell are configured with two control resource set pools, CORESETPool, respectively, and the PCell is configured with a1 and the SCell is configured with a2, the monitoring upper limits of the PDCCH candidates in the 15 kHz slot and the 30 kHz slot may be as follows, respectively:

[0285] The monitoring limit for 15kHz slots is a first upper limit corresponding to the PCell, the first upper limit corresponding to the PCell being equal to the product of γ and the first predefined upper limit for the 15 kHz slot in Table 1, i.e., 44γ; and a second upper limit corresponding to the PCell, the second upper limit corresponding to the PCell being equal to the product of γ and the second predefined upper limit for the 15 kHz slot in Table 2, i.e., 56γ. It may include:

[0286] In other words, the terminal device does not need to monitor more than 44γ PDCCH candidates and more than 56γ non-overlapping CCEs in the PCell in a 15 kHz slot.

[0287] Furthermore, the monitoring upper limit in a 30 kHz slot is the first upper limit corresponding to the SCell, which is equal to the product of γ and the first predefined upper limit in the 30 kHz slot in Table 1, i.e., 36γ, and the second upper limit corresponding to the SCell, which is equal to the product of γ and the second predefined upper limit in the 30 kHz slot in Table 2, i.e., 56γ may be included.

[0288] In other words, the terminal device does not need to monitor more than 36γ PDCCH candidates and more than 56γ non-overlapping CCEs in the SCell in a 30 kHz slot.

[0289] In this solution, it can be seen that the terminal device does not need to monitor more than 44γ PDCCH candidates and more than 56γ non-overlapping CCEs in the PCell in a 15 kHz slot, and the terminal device does not need to monitor more than 36γ PDCCH candidates and more than 56γ non-overlapping CCEs in the SCell in a 30 kHz slot. Therefore, this not only solves the problem of how to determine the monitoring upper limit per unit time when both the PCell and the SCell schedule the PCell, but also avoids the problem that the monitoring upper limit in one unit time is determined only based on that unit time and the monitoring upper limit in another unit time is not met.

[0290] Furthermore, the case where both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a span is also the same as the above example. The difference is that different default monitoring upper limits per unit time are used for different unit times. Therefore, the details will not be repeated here.

[0291] Embodiment 2: The downlink control information transmission method 200 of this embodiment of the present application is applicable to a scenario in which the subcarrier spacing of the active downlink bandwidth portions in multiple scheduling cells is the same.

[0292] 9 is a schematic flowchart of a downlink control information transmission method 200 according to an embodiment of the present application. The downlink control information transmission method 200 is described by using an example in which a first scheduling cell and a second scheduling cell schedule the same scheduled cell. Optionally, the downlink control information transmission method 200 is also applicable to a scenario in which multiple scheduling cells schedule the same scheduled cell. The same inventive concept exists, and details are not described in this application.

[0293] As shown in FIG. 9, the downlink control information transmission method 200 may include, but is not limited to, the following steps.

[0294] S201: A network device transmits first setting information.

[0295] S202: The terminal device receives first setting information.

[0296] Optionally, for steps S201 and S202, please refer to the relevant description of steps S101 and S102 in embodiment 1. Details are not described again in this specification.

[0297] S203: The terminal device determines a monitoring upper limit of PDCCH candidates in the same unit time for the same scheduled cell.

[0298] S204: The network device also determines a monitoring upper limit of PDCCH candidates in the same unit time for the same scheduled cell.

[0299] The same unit time is determined based on the subcarrier spacing of the active downlink bandwidth portion in one of the scheduling cells. The monitoring upper limit of the PDCCH candidates in the same unit time may include a monitoring upper limit of the PDCCH candidates in a single scheduling cell in the unit time, and / or further includes a monitoring upper limit of the total PDCCH candidates in two scheduling cells in the unit time. Therefore, in steps S203 and S204, the PDCCH candidates may be the PDCCH candidates in a single scheduling cell and / or the total PDCCH candidates in the two scheduling cells.

[0300] Similarly, the monitoring upper limit of PDCCH candidates in a unit time may also be referred to as the actual monitoring upper limit of the terminal device.

[0301] In an optional implementation, the network device may first determine the first setting information, perform step 204 of determining the actual monitoring upper limit of the terminal device, and then perform step 201 of sending the first setting information to the terminal device, and the terminal device performs steps S202 and S203. In another optional implementation, the network device may together determine the first setting information and the actual monitoring upper limit of the terminal device, and then perform step 201 of sending the first setting information to the terminal device, and the terminal device performs steps S202 and S203.

[0302] In an optional implementation, the downlink control information transmission method 200 may further include: the network device sends a PDCCH-related configuration to the terminal device, and then sends a PDCCH in each scheduling cell, so that the terminal device monitors PDCCH candidates based on the PDCCH-related configuration and the actual monitoring upper limit, and obtains a PDCCH. Optionally, the sequence in which the network device sends a PDCCH-related configuration and the terminal device performs step S203 may not be limited in this embodiment of the present application.

[0303] It can be seen that in the downlink control information transmission method 200 shown in FIG. 9, the monitoring upper limit of PDCCH candidates in the same unit time is determined, which solves the problem of how to determine the monitoring upper limit in a scenario where two scheduling cells schedule the same scheduled cell.

[0304] Furthermore, since the subcarrier spacing corresponding to the first scheduling cell is the same as the subcarrier spacing corresponding to the second scheduling cell, this method determines the monitoring upper limit in the same unit time, so there is no problem that the monitoring upper limit in one unit time is determined and the monitoring upper limit in another unit time is extremely large.

[0305] For example, it is assumed that the subcarrier spacing of the SCell is 30 kHz, the subcarrier spacing of the PCell is also 30 kHz, and both the PCell and the SCell can schedule the PCell. The monitoring upper limit of PDCCH candidates in a 30 kHz slot is 36, and the first predetermined upper limit in the predetermined monitoring upper limits per unit time corresponding to the SCell and the PCell is 36. Therefore, there is no problem that the monitoring upper limit of the total PDCCH candidates in the SCell and the PCell is extremely large in the 30 kHz slot of the terminal device.

[0306] The following describes some optional implementations of embodiment 2.

[0307] In an optional implementation, the monitoring upper limit in the same unit time is determined based on a predetermined monitoring upper limit per unit time corresponding to the first scheduling cell or the second scheduling cell, and it can be seen that the actual monitoring upper limit of the terminal device is related to the first configuration information and the predetermined monitoring upper limit per unit time.

[0308] As mentioned above, the predetermined per-unit-time monitoring upper limit corresponding to each cell can be obtained through a query in a table based on the subcarrier spacing of the active downlink bandwidth portion in the cell, and the details are not described again here.

[0309] Optionally, in this implementation, the monitoring upper limit in each unit time may alternatively be determined differently based on the number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell. Implementation 2.1 and Implementation 2.2 are used separately below for explanation. Because the default monitoring upper limit per unit time corresponding to the first scheduling cell is the same as the default monitoring upper limit per unit time corresponding to the second scheduling cell, in other words, the subcarrier intervals corresponding to the first scheduling cell and the second scheduling cell are the same, the following implementations are described by using the default monitoring upper limit per unit time corresponding to the first scheduling cell as an example.

[0310] Implementation 2.1: The monitoring upper limit in a unit time is determined based on a predetermined monitoring upper limit per unit time corresponding to one of the scheduling cells. The subcarrier spacing of the active downlink bandwidth portions in the first scheduling cell and the second scheduling cell is assumed to be μ.

[0311] In Implementation 2.1, an explanation is provided by using an example in which the monitoring upper limit includes a first upper limit and / or a second upper limit, and correspondingly, the predetermined per unit time monitoring upper limit includes a first predetermined upper limit and / or a second predetermined upper limit.

[0312] For controlled resource sets corresponding to the same CORESETPool, when the first scheduling cell and the second scheduling cell are not configured in the controlled resource set pool CORESETPool, or are configured in the CORESETPool, respectively; when the first scheduling cell is configured in the CORESETPool and the second scheduling cell is not configured in the CORESETPool; when the first scheduling cell is not configured in the CORESETPool and the second scheduling cell is configured in the CORESETPool; or when the first scheduling cell and the second scheduling cell are configured in two CORESETPools, respectively; The monitoring upper bound in unit time with subcarrier spacing μ is given by: a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit corresponding to the first scheduling cell and the second scheduling cell being determined based on a first predefined upper limit corresponding to the first scheduling cell; a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit corresponding to the first scheduling cell and the second scheduling cell being determined based on a second predefined upper limit corresponding to the first scheduling cell; a first upper limit corresponding to each scheduling cell, the first upper limit corresponding to each scheduling cell being determined based on a first predefined upper limit corresponding to the first scheduling cell; and The second upper limit may include one or more second upper limits corresponding to each scheduling cell, the second upper limits corresponding to each scheduling cell being determined based on a second predetermined upper limit corresponding to the first scheduling cell.

[0313] For example, it is assumed that the subcarrier spacing of the SCell is 30 kHz, the subcarrier spacing of the PCell is also 30 kHz, and both the PCell and the SCell can schedule the PCell. Furthermore, both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a slot. For control resource sets corresponding to the same CORESETPool, when the PCell and the SCell are not configured in the control resource set pool CORESETPool, or are configured in the CORESETPool, when the PCell is configured in the CORESETPool and the SCell is not configured in the CORESETPool, when the PCell is not configured in the CORESETPool and the SCell is configured in the CORESETPool, or when the PCell and the SCell are configured in two CORESETPools, The monitoring limit for the 30kHz slot is a first upper limit corresponding to the PCell and SCell, the first upper limit being determined based on the first predefined upper limit for a 30 kHz slot in Table 1, i.e., 36; a second upper limit corresponding to the PCell and SCell, the second upper limit being determined based on the second predefined upper limit for the 30 kHz slot in Table 2, i.e., 56; a first upper limit corresponding to the PCell or SCell, the first upper limit being determined based on the first predefined upper limit for a 30 kHz slot in Table 1, i.e., 36; and A second upper limit corresponding to a PCell or SCell, which is determined based on the second predetermined upper limit in a 30 kHz slot in Table 2, i.e., 56. 2 may include an upper limit of

[0314] It can be seen that in this implementation, the monitoring upper limit in the 30 kHz slot can be determined based on Tables 1 and 2 as the actual monitoring upper limit of the terminal device.

[0315] As another example, both the PCell and the SCell are configured such that the monitoring upper limit is determined at the granularity of the span, and the span satisfies the combination (X, Y). For the controlled resource sets corresponding to the same CORESETPool, when the PCell and the SCell are not configured in the controlled resource set pool CORESETPool, or are configured in the CORESETPool, when the PCell is configured in the CORESETPool and the SCell is not configured in the CORESETPool, when the PCell is not configured in the CORESETPool and the SCell is configured in the CORESETPool, or when the PCell and the SCell are configured in two CORESETPools, The monitoring upper limit in a 30 kHz span for the combination (X, Y) is: a first upper limit corresponding to the PCell and the SCell, the first upper limit being determined based on a first predefined upper limit in a 30 kHz span for the combination (X, Y) in Table 3; a second upper limit corresponding to the PCell and SCell, the second upper limit being determined based on a second predefined upper limit in a 30 kHz span for the combination (X, Y) in Table 4; a first upper limit corresponding to the PCell or SCell, the first upper limit being determined based on a first predefined upper limit in a 30 kHz span for the combination (X, Y) in Table 3; and It may include a second upper limit corresponding to the PCell or SCell, the second upper limit being determined based on the second predefined upper limit in a 30 kHz span for the combination (X, Y) in Table 4.

[0316] It can be seen that in this implementation, the monitoring upper limit in a 30 kHz slot can be determined based on Tables 1 and 2 as the actual monitoring upper limit of the terminal device, or in this implementation, the monitoring upper limit in a 30 kHz span for combination (X, Y) can be determined based on Tables 3 and 4 as the actual monitoring upper limit of the terminal device.

[0317] Implementation 2.2: The monitoring upper limit in the same unit time is determined in each scheduling cell based on the third parameter and a predetermined monitoring upper limit per unit time. The third parameter is used to determine the number of cells corresponding to the scheduled cells scheduled by the scheduling cells configured in the two CORESETPools. The subcarrier spacing of the active downlink bandwidth portions in the first scheduling cell and the second scheduling cell is assumed to be μ.

[0318] Similarly, in Implementation 2.2, an explanation is provided by using an example in which the monitoring upper limit includes a first upper limit and / or a second upper limit, and correspondingly, the predetermined per unit time monitoring upper limit includes a first predetermined upper limit and / or a second predetermined upper limit.

[0319] When the first scheduling cell and the second scheduling cell are respectively configured with two control resource set pools CORESETPool, The monitoring upper bound in unit time with subcarrier spacing μ is given by: a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit corresponding to the first scheduling cell and the second scheduling cell being determined based on the third parameter and a first predefined upper limit corresponding to the first scheduling cell; a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit corresponding to the first scheduling cell and the second scheduling cell being determined based on the third parameter and a second predetermined upper limit corresponding to the first scheduling cell; a first upper limit corresponding to each scheduling cell, the first upper limit corresponding to each scheduling cell being determined based on the third parameter and a first predefined upper limit corresponding to each scheduling cell; and The parameter may include one or more of a second upper limit corresponding to each scheduling cell, the second upper limit corresponding to each scheduling cell being determined based on the third parameter and a second predetermined upper limit corresponding to each scheduling cell.

[0320] For example, it is assumed that the subcarrier spacing of the SCell is 30 kHz, the subcarrier spacing of the PCell is also 30 kHz, and both the PCell and the SCell can schedule the PCell. Both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a slot. When the PCell and the SCell are configured in two control resource set pools, CORESETPool, respectively, it is assumed that the third parameter is γ. In this case, the monitoring upper limit in a 30 kHz slot is a first upper limit corresponding to the PCell and SCell, the first upper limit being determined based on γ and a first predefined upper limit (i.e., 36) for a 30 kHz slot in Table 1; a second upper limit corresponding to the PCell and SCell, the second upper limit being determined based on γ and a second predefined upper limit (i.e., 56) for the 30 kHz slot in Table 2; a first upper limit corresponding to the PCell or SCell, the first upper limit being determined based on γ and a first predefined upper limit (i.e., 36) for a 30 kHz slot in Table 1; and It may include a second upper limit corresponding to the PCell or SCell, determined based on γ and a second pre-defined upper limit in 30 kHz slots in Table 2 (i.e., 56).

[0321] It can be seen that in this implementation, the monitoring upper limit in the 15 kHz slot and the monitoring upper limit in the 30 kHz slot can be determined based on γ, Table 1, and Table 2 as the actual monitoring upper limit of the terminal device.

[0322] As another example, both the PCell and the SCell are configured such that the monitoring upper limit is determined at the granularity of a span, and the span satisfies the combination (X, Y). When the PCell and the SCell are configured with two control resource set pools CORESETPool, respectively, the third parameter is assumed to be γ. In this case, The monitoring upper limit in a 30 kHz span for the combination (X, Y) is as follows: a first upper limit corresponding to the PCell and the SCell, the first upper limit being determined based on γ and a first predefined upper limit in a 30 kHz span for the combination (X, Y) in Table 3; a second upper limit corresponding to the PCell and SCell, the second upper limit being determined based on γ and a second predefined upper limit in a 30 kHz span for the combination (X, Y) in Table 4; a first upper limit corresponding to the PCell or SCell, the first upper limit being determined based on γ and a first predefined upper limit in a 30 kHz span for the combination (X, Y) in Table 3; and It may include one or more of the second upper limits corresponding to the PCell or SCell, determined based on γ and the second predefined upper limit in a 30 kHz span for the combination (X, Y) in Table 4.

[0323] In this implementation, it can be seen that the monitoring upper limit in a 15 kHz span for the combination (X, Y) and the monitoring upper limit in a 30 kHz span for the combination (X, Y) can be determined based on γ, Table 3, and Table 4 as the actual monitoring upper limit of the terminal device.

[0324] In Implementation 2.1 provided in this embodiment of the present application (specifically, for CORESETs corresponding to the same CORESETPool, the first scheduling cell and the second scheduling cell are not configured in the two CORESETPools, respectively, or the first scheduling cell and the second scheduling cell are configured in the two CORESETPools, respectively), three implementations are described based on whether the first scheduling cell and the second scheduling cell are configured with the first parameter corresponding to the first scheduling cell and the second scheduling cell, or whether the first scheduling cell and the second scheduling cell are configured with the first parameter and the second parameter, respectively, to specifically determine the monitoring upper limit of PDCCH candidates in the same unit time. The first parameter is used to determine the number of cells corresponding to the scheduled cells scheduled by the scheduling cell. Optionally, the number of cells may also be referred to as the number of logical cells. Implementations 2.1.1 to 2.1.3 will be used separately below for explanation. It is assumed that the subcarrier spacings corresponding to the first scheduling cell and the second scheduling cell, respectively, are both μ.

[0325] Implementation 2.1.1: The first scheduling cell and the second scheduling cell are not configured with the first parameter corresponding to the first scheduling cell and the second scheduling cell.

[0326] The upper limit of monitoring PDCCH candidates in a unit time with subcarrier spacing μ is The scheduling limit may include a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit corresponding to the first scheduling cell being equal to a first predetermined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit corresponding to the first scheduling cell being equal to a second predetermined upper limit corresponding to the first scheduling cell.

[0327] For example, it is assumed that the subcarrier spacing of the SCell is 30 kHz, the subcarrier spacing of the PCell is also 30 kHz, and both the PCell and the SCell can schedule the PCell. Both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a slot. For control resource sets corresponding to the same CORESETPool, when the PCell and the SCell are not configured in the control resource set pool CORESETPool, or are configured in the CORESETPool, when the PCell is configured in the CORESETPool and the SCell is not configured in the CORESETPool, when the PCell is not configured in the CORESETPool and the SCell is configured in the CORESETPool, or when the PCell and the SCell are configured in two CORESETPools, and when the PCell and the SCell are not configured with the first parameters corresponding to the PCell and the SCell, the monitoring upper limit of the PDCCH candidate in a 30 kHz slot is a first upper limit corresponding to the PCell and SCell, the first upper limit corresponding to the PCell and SCell being equal to the first predetermined upper limit in a 30 kHz slot in Table 1, i.e., 36; and The second upper limit corresponding to the PCell and SCell may be equal to the second predefined upper limit in the 30 kHz slot in Table 2, i.e., 56.

[0328] It can be seen that in a 30 kHz slot, the maximum total number of PDCCH candidates in the PCell and SCell is 36, and the maximum total number of non-overlapping CCEs in the PCell and SCell is 56. Therefore, this solves the problem of how to determine the monitoring upper limit in unit time when both the PCell and SCell schedule the PCell.

[0329] Furthermore, when both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a span, it is the same as in the previous example. The difference is that different predefined monitoring upper limits per unit time are used for different unit times. Therefore, the details are not described again in this specification.

[0330] Implementation 2.1.2: The first scheduling cell and the second scheduling cell are configured with a first parameter corresponding to the first scheduling cell and the second scheduling cell. The first parameter is assumed to be a.

[0331] The upper limit of monitoring PDCCH candidates in a unit time with subcarrier spacing μ is a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit corresponding to the first scheduling cell and the second scheduling cell being equal to the product of a and a first predefined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to the first scheduling cell and the second scheduling cell being equal to the product of a and a second predefined upper limit corresponding to the first scheduling cell; The scheduling limit may include a first upper limit corresponding to each scheduling cell, the first upper limit corresponding to each scheduling cell being equal to a first predetermined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to each scheduling cell, the second upper limit corresponding to each scheduling cell being equal to a second predetermined upper limit corresponding to the first scheduling cell.

[0332] For example, it is assumed that the subcarrier spacing of the SCell is 30 kHz, the subcarrier spacing of the PCell is also 30 kHz, and both the PCell and the SCell can schedule the PCell. Both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a slot. For control resource sets corresponding to the same CORESETPool, when the PCell and the SCell are not configured in the control resource set pool CORESETPool, or are configured in the CORESETPool, when the PCell is configured in the CORESETPool and the SCell is not configured in the CORESETPool, when the PCell is not configured in the CORESETPool and the SCell is configured in the CORESETPool, or when the PCell and the SCell are configured in two CORESETPools, and when the PCell and the SCell are not configured with the first parameters corresponding to the PCell and the SCell, the monitoring upper limit of the PDCCH candidate in a 30 kHz slot is a first upper limit corresponding to the PCell and SCell, the first upper limit corresponding to the PCell and SCell being equal to the product of a and the first pre-defined upper limit for a 30 kHz slot in Table 1, i.e., 36a; a second upper limit corresponding to the PCell and SCell, the second upper limit corresponding to the PCell and SCell being equal to the product of a and the second predetermined upper limit for a 30 kHz slot in Table 2, i.e., 56a; a first upper limit corresponding to each of the PCell and SCell, which is equal to the first predetermined upper limit in a 30 kHz slot in Table 1, i.e., 36; and The second upper limit corresponding to each of the PCell and SCell may be equal to the second predetermined upper limit in a 30 kHz slot in Table 2, i.e., 56.

[0333] In other words, a terminal device is not required to monitor a total of more than 36a PDCCH candidates and more than 56a non-overlapping CCEs in the PCell and SCell in a 30 kHz slot, and a terminal device is not required to monitor more than 36 PDCCH candidates and more than 56 non-overlapping CCEs in each of the PCell and SCell in a 30 kHz slot.

[0334] Furthermore, when both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a span, it is the same as in the previous example. The difference is that different predefined monitoring upper limits per unit time are used for different unit times. Therefore, the details are not described again in this specification.

[0335] Implementation 2.1.3: A first scheduling cell is configured with a first parameter, which is represented as a1. A second scheduling cell is configured with a second parameter, which is represented as a2. The first parameter a1 is used to determine the number of cells corresponding to scheduled cells scheduled by the first scheduling cell, and the second parameter a2 is used to determine the number of cells corresponding to scheduled cells scheduled by the second scheduling cell.

[0336] In the solution of Implementation 2.1.3, the monitoring upper limit of PDCCH candidates in a unit time with subcarrier spacing μ is a first upper limit corresponding to the first scheduling cell, the first upper limit corresponding to the first scheduling cell being equal to the product of a1 and a first predefined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to the first scheduling cell, the second upper limit corresponding to the first scheduling cell being equal to the product of a1 and a second predefined upper limit corresponding to the first scheduling cell; The scheduling information may include a first upper limit corresponding to the second scheduling cell, the first upper limit corresponding to the second scheduling cell being equal to the product of a2 and a first predefined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to the second scheduling cell, the second upper limit corresponding to the second scheduling cell being equal to the product of a2 and a second predefined upper limit corresponding to the first scheduling cell.

[0337] For example, it is assumed that the subcarrier spacing of the SCell is 30 kHz, the subcarrier spacing of the PCell is also 30 kHz, and both the PCell and the SCell can schedule the PCell. Both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a slot. For control resource sets corresponding to the same CORESETPool, when the PCell and the SCell are not configured in the control resource set pool CORESETPool, or are configured in the CORESETPool, when the PCell is configured in the CORESETPool and the SCell is not configured in the CORESETPool, when the PCell is not configured in the CORESETPool and the SCell is configured in the CORESETPool, or when the PCell and the SCell are configured in two CORESETPools, and when the PCell is configured in a1 and the SCell is configured in a2, the monitoring upper limit of the PDCCH candidates in a 30 kHz slot is a first upper limit corresponding to the PCell, the first upper limit corresponding to the PCell being equal to the product of a1 and the first predefined upper limit for a 30 kHz slot in Table 1, i.e., 36a1; a second upper limit corresponding to the PCell, the second upper limit corresponding to the PCell being equal to the product of a1 and the second predefined upper limit for the 30 kHz slot in Table 2, i.e., 56a1; a first upper limit corresponding to the SCell, the first upper limit being equal to the product of a2 and the first predefined upper limit for the 30 kHz slot in Table 1, i.e., 36a2; and It may include a second upper limit corresponding to the SCell, which is equal to the product of a2 and the second pre-defined upper limit for the 30 kHz slot in Table 2, i.e., 56a2.

[0338] In other words, a terminal device is not required to monitor more than 36a1 PDCCH candidates and more than 56a1 non-overlapping CCEs in a PCell in a 30 kHz slot, and a terminal device is not required to monitor more than 36a2 PDCCH candidates and more than 56a2 non-overlapping CCEs in a SCell in a 30 kHz slot.

[0339] Furthermore, when both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a span, it is the same as in the previous example. The difference is that different predefined monitoring upper limits per unit time are used for different unit times. Therefore, the details are not described again in this specification.

[0340] In another solution of implementation 2.1.3, the monitoring upper limit of PDCCH candidates in a unit time with subcarrier spacing μ is a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit corresponding to the first scheduling cell and the second scheduling cell being equal to the product of (a1+a2) and a first predefined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit corresponding to the first scheduling cell being equal to the product of (a1+a2) and a second predefined upper limit corresponding to the first scheduling cell; The scheduling information may include a first upper limit corresponding to each of the first scheduling cell and the second scheduling cell, the first upper limit corresponding to each of the first scheduling cell and the second scheduling cell being equal to a first predetermined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to each of the first scheduling cell and the second scheduling cell being equal to a second predetermined upper limit corresponding to the first scheduling cell.

[0341] For example, it is assumed that the subcarrier spacing of the SCell is 30 kHz, the subcarrier spacing of the PCell is also 30 kHz, and both the PCell and the SCell can schedule the PCell. Both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a slot. For control resource sets corresponding to the same CORESETPool, when the PCell and the SCell are not configured in the control resource set pool CORESETPool, or are configured in the CORESETPool, when the PCell is configured in the CORESETPool and the SCell is not configured in the CORESETPool, when the PCell is not configured in the CORESETPool and the SCell is configured in the CORESETPool, or when the PCell and the SCell are configured in two CORESETPools, and when the PCell is configured in a1 and the SCell is configured in a2, the monitoring upper limit of the PDCCH candidates in a 30 kHz slot is a first upper limit corresponding to the PCell and SCell, the first upper limit corresponding to the PCell and SCell being the product of (a1+a2) and the first pre-defined upper limit for the 30 kHz slot in Table 1, i.e., equal to 36(a1+a2); and a second upper limit corresponding to the PCell and SCell, the second upper limit corresponding to the PCell and SCell being the product of (a1+a2) and the second pre-defined upper limit for the 30 kHz slot in Table 1, i.e., equal to 56(a1+a2); The upper limit may include a first upper limit corresponding to each of the PCell and SCell, which is a first predetermined upper limit in a 30 kHz slot in Table 1, i.e., a first upper limit corresponding to each of the PCell and SCell, equal to 36, and a second upper limit corresponding to each of the PCell and SCell, which is a second predetermined upper limit in a 30 kHz slot in Table 2, i.e., a second upper limit corresponding to each of the PCell and SCell, equal to 56.

[0342] In other words, the terminal device is not required to monitor a total of more than 36 (a1+a2) PDCCH candidates and more than 56 (a1+a2) non-overlapping CCEs in the PCell and SCell in a 30 kHz slot, and the terminal device is not required to monitor more than 36 PDCCH candidates and more than 56 non-overlapping CCEs in each of the PCell and SCell in a 30 kHz slot.

[0343] Furthermore, when both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a span, it is the same as in the previous example. The difference is that different predefined monitoring upper limits per unit time are used for different unit times. Therefore, the details are not described again in this specification.

[0344] In yet another solution of implementation 2.1.3, the monitoring upper limit of PDCCH candidates in a unit time with subcarrier spacing μ is The scheduling information may include a first upper limit corresponding to each of the first scheduling cell and the second scheduling cell, the first upper limit corresponding to each of the first scheduling cell and the second scheduling cell being equal to a first predetermined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to each of the first scheduling cell and the second scheduling cell being equal to a second predetermined upper limit corresponding to the first scheduling cell.

[0345] For example, it is assumed that the subcarrier spacing of the SCell is 30 kHz, the subcarrier spacing of the PCell is also 30 kHz, and both the PCell and the SCell can schedule the PCell. Both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a slot. For control resource sets corresponding to the same CORESETPool, when the PCell and the SCell are not configured in the control resource set pool CORESETPool, or are configured in the CORESETPool, when the PCell is configured in the CORESETPool and the SCell is not configured in the CORESETPool, when the PCell is not configured in the CORESETPool and the SCell is configured in the CORESETPool, or when the PCell and the SCell are configured in two CORESETPools, and when the PCell is configured in a1 and the SCell is configured in a2, the monitoring upper limit of the PDCCH candidates in a 30 kHz slot is The upper limit may include a first upper limit corresponding to each of the PCell and SCell, the first upper limit corresponding to each of the PCell and SCell being equal to the first predefined upper limit in a 30 kHz slot in Table 1, i.e., 36, and a second upper limit corresponding to each of the PCell and SCell, the second predefined upper limit corresponding to each of the PCell and SCell being equal to the second predefined upper limit in a 30 kHz slot in Table 2, i.e., 56.

[0346] In other words, a terminal device does not need to monitor more than 36 PDCCH candidates and 56 non-overlapping CCEs in each of the PCell and SCell in a 30 kHz slot.

[0347] Furthermore, when both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a span, it is the same as in the previous example. The difference is that different predefined monitoring upper limits per unit time are used for different unit times. Therefore, the details are not described again in this specification.

[0348] In Implementation 2.2 provided in this embodiment of the present application (specifically, the first scheduling cell and the second scheduling cell are configured in two CORESETPools, respectively), three implementations are described to specifically determine the monitoring upper limit of PDCCH candidates in the first unit time and the second unit time, depending on whether the first scheduling cell and the second scheduling cell are configured with the first parameter corresponding to the first scheduling cell and the second scheduling cell, or whether the first scheduling cell and the second scheduling cell are configured with the first parameter and the second parameter, respectively. The first parameter is used to determine the number of cells corresponding to scheduled cells scheduled by the scheduling cell. Optionally, the number of cells may also be referred to as the number of logical cells. Implementations 2.2.1 to 2.2.3 are used separately below for explanation. The third parameter is used to determine the number of cells corresponding to scheduled cells scheduled by the scheduling cells configured in the two CORESETPools. It is assumed that the third parameter is represented as γ.

[0349] Implementation 2.2.1: The first scheduling cell and the second scheduling cell are not configured with the first parameter corresponding to the first scheduling cell and the second scheduling cell.

[0350] The upper limit of monitoring PDCCH candidates in a unit time with subcarrier spacing μ is The scheduling information may include a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit corresponding to the first scheduling cell being equal to a first predetermined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to the first scheduling cell and the second scheduling cell being equal to a second predetermined upper limit corresponding to the first scheduling cell.

[0351] For example, it is assumed that the subcarrier spacing of the SCell is 30 kHz, the subcarrier spacing of the PCell is also 30 kHz, and both the PCell and the SCell can schedule the PCell. Both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a slot. For control resource sets corresponding to the same CORESETPool, when the PCell and the SCell are not configured in the control resource set pool CORESETPool, or are configured in the CORESETPool, when the PCell is configured in the CORESETPool and the SCell is not configured in the CORESETPool, when the PCell is not configured in the CORESETPool and the SCell is configured in the CORESETPool, or when the PCell and the SCell are configured in two CORESETPools, and when the PCell and the SCell are not configured with the first parameters corresponding to the PCell and the SCell, the monitoring upper limit of the PDCCH candidates in a 30 kHz slot is a first upper limit corresponding to the PCell and SCell, the first upper limit corresponding to the PCell and SCell being equal to the first predetermined upper limit in a 30 kHz slot in Table 1, i.e., 36; and The second upper limit corresponding to the PCell and SCell may be equal to the second predefined upper limit in the 30 kHz slot in Table 2, i.e., 56.

[0352] It can be seen that in a 30 kHz slot, the maximum total number of PDCCH candidates in the PCell and SCell is 36, and the maximum total number of non-overlapping CCEs in the PCell and SCell is 56. Therefore, this solves the problem of how to determine the monitoring upper limit in unit time when both the PCell and SCell schedule the PCell.

[0353] Furthermore, when both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a span, it is the same as in the previous example. The difference is that different predefined monitoring upper limits per unit time are used for different unit times. Therefore, the details are not described again in this specification.

[0354] Implementation 2.2.2: The first scheduling cell and the second scheduling cell are configured with a first parameter corresponding to the first scheduling cell and the second scheduling cell. The first parameter is assumed to be a.

[0355] The upper limit of monitoring PDCCH candidates in a unit time with subcarrier spacing μ is a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit corresponding to the first scheduling cell and the second scheduling cell being equal to the product of a·γ and a first predefined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit corresponding to the first scheduling cell being equal to the product of a·γ and a second predefined upper limit corresponding to the first scheduling cell; The scheduling cell may include a first upper limit corresponding to each scheduling cell, the first upper limit corresponding to each scheduling cell being equal to the product of γ and a first predetermined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to each scheduling cell, the second upper limit corresponding to each scheduling cell being equal to the product of γ and a second predetermined upper limit corresponding to the first scheduling cell.

[0356] For example, it is assumed that the subcarrier spacing of the SCell is 30 kHz, the subcarrier spacing of the PCell is also 30 kHz, and both the PCell and the SCell can schedule the PCell. P Both the cell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a slot. When the PCell and the SCell are configured with two control resource set pools CORESETPool, respectively, and the PCell and the SCell are configured with the first parameter a corresponding to the PCell and the SCell, respectively, the monitoring upper limit of the PDCCH candidate in a 30 kHz slot is a first upper limit corresponding to the PCell and SCell, the first upper limit corresponding to the PCell and SCell being equal to the product of a·γ and the first predefined upper limit for the 30 kHz slot in Table 1, i.e., 36a·γ; a second upper limit corresponding to the PCell and SCell, the second upper limit corresponding to the PCell and SCell being equal to the product of a·γ and the second predetermined upper limit for the 30 kHz slot in Table 2, i.e., 56a·γ; a first upper limit corresponding to each of the PCell and SCell, the first upper limit being equal to the product of γ and the first predetermined upper limit for a 30 kHz slot in Table 1, i.e., 36γ; and There may be a second upper limit corresponding to each of the PCell and SCell, which is equal to the product of γ and the second pre-defined upper limit for a 30 kHz slot in Table 2, i.e., 56γ.

[0357] In other words, the terminal device is not required to monitor a total of more than 36a·γ PDCCH candidates and more than 56a·γ non-overlapping CCEs in the PCell and SCell in a 30 kHz slot, and the terminal device is not required to monitor more than 36γ PDCCH candidates and more than 56γ non-overlapping CCEs in each of the PCell and SCell in a 30 kHz slot.

[0358] Furthermore, when both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a span, it is the same as in the previous example. The difference is that different predefined monitoring upper limits per unit time are used for different unit times. Therefore, the details are not described again in this specification.

[0359] Implementation 2.2.3: A first scheduling cell is configured with a first parameter, which is represented as a1. A second scheduling cell is configured with a second parameter, which is represented as a2. The first parameter a1 is used to determine the number of cells corresponding to scheduled cells scheduled by the first scheduling cell, and the second parameter a2 is used to determine the number of cells corresponding to scheduled cells scheduled by the second scheduling cell.

[0360] In the solution of Implementation 2.2.3, the monitoring upper limit of PDCCH candidates in a unit time with subcarrier spacing μ is a first upper limit corresponding to the first scheduling cell, the first upper limit corresponding to the first scheduling cell being equal to the product of a1·γ and a first predefined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to the first scheduling cell, the second upper limit corresponding to the first scheduling cell being equal to the product of a1·γ and a second predefined upper limit corresponding to the first scheduling cell; The scheduling parameter may include a first upper limit corresponding to the second scheduling cell, the first upper limit corresponding to the second scheduling cell being equal to the product of a2·γ and a first predefined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to the second scheduling cell, the second upper limit corresponding to the second scheduling cell being equal to the product of a2·γ and a second predefined upper limit corresponding to the first scheduling cell.

[0361] For example, it is assumed that the subcarrier spacing of the SCell is 30 kHz, the subcarrier spacing of the PCell is also 30 kHz, and both the PCell and the SCell can schedule the PCell. Both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a slot. When the PCell and the SCell are configured in two control resource set pools, CORESETPool, respectively, and the PCell is configured in a1 and the SCell is configured in a2, the monitoring upper limit of the PDCCH candidate in the 30 kHz slot is a first upper limit corresponding to the PCell, the first upper limit being equal to the product of a1·γ and the first predefined upper limit for the 30 kHz slot in Table 1, i.e., 36a1·γ; a second upper limit corresponding to the PCell, the second upper limit corresponding to the PCell being equal to the product of a1·γ and the second predetermined upper limit for the 30 kHz slot in Table 2, i.e., 56a1·γ; a first upper limit corresponding to the SCell, the first upper limit being equal to the product of a2·γ and the first predefined upper limit for the 30 kHz slot in Table 1, i.e., 36a2·γ; and It may include a second upper limit corresponding to the SCell, the second upper limit corresponding to the SCell being equal to the product of a2·γ and the second pre-defined upper limit for the 30 kHz slot in Table 2, i.e., 56a2·γ.

[0362] In other words, a terminal device is not required to monitor more than 36a1·γ PDCCH candidates and more than 56a1·γ non-overlapping CCEs in a PCell in a 30 kHz slot, and a terminal device is not required to monitor more than 36a2·γ PDCCH candidates and more than 56a2·γ non-overlapping CCEs in a SCell in a 30 kHz slot.

[0363] Furthermore, when both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a span, it is the same as in the previous example. The difference is that different predefined monitoring upper limits per unit time are used for different unit times. Therefore, the details are not described again in this specification.

[0364] In another solution of implementation 2.2.3, the monitoring upper limit of PDCCH candidates in a unit time with subcarrier spacing μ is a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit corresponding to the first scheduling cell and the second scheduling cell being equal to the product of (a1+a2)·γ and a first predefined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit corresponding to the first scheduling cell being equal to the product of (a1+a2)·γ and a second predefined upper limit corresponding to the first scheduling cell; The scheduling parameter may include a first upper limit corresponding to each of the first scheduling cell and the second scheduling cell, the first upper limit corresponding to each of the first scheduling cell and the second scheduling cell being equal to the product of γ and a first predefined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to each of the first scheduling cell and the second scheduling cell being equal to the product of γ and a second predefined upper limit corresponding to the first scheduling cell.

[0365] For example, it is assumed that the subcarrier spacing of the SCell is 30 kHz, the subcarrier spacing of the PCell is also 30 kHz, and both the PCell and the SCell can schedule the PCell. Both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a slot. When the PCell and the SCell are configured in two control resource set pools, CORESETPool, respectively, and the PCell is configured in a1 and the SCell is configured in a2, the monitoring upper limit of the PDCCH candidate in the 30 kHz slot is a first upper limit corresponding to the PCell and SCell, the first upper limit corresponding to the PCell and SCell being equal to the product of (a1+a2)·γ and the first predefined upper limit for the 30 kHz slot in Table 1, i.e., 36(a1+a2)·γ; and a second upper limit corresponding to the PCell and SCell, the second upper limit corresponding to the PCell and SCell being equal to the product of (a1+a2)·γ and the second predefined upper limit for the 30 kHz slot in Table 1, i.e., 56(a1+a2)·γ; The upper limit may include a first upper limit corresponding to each of the PCell and SCell, the first upper limit corresponding to each of the PCell and SCell being equal to the product of γ and the first predefined upper limit for a 30 kHz slot in Table 1, i.e., 36γ, and a second upper limit corresponding to each of the PCell and SCell, the second upper limit corresponding to each of the PCell and SCell being equal to the product of γ and the second predefined upper limit for a 30 kHz slot in Table 2, i.e., 56γ.

[0366] In other words, the terminal device is not required to monitor a total of more than 36(a1+a2)·γ PDCCH candidates and more than 56(a1+a2)·γ non-overlapping CCEs in the PCell and SCell in a 30 kHz slot, and the terminal device is not required to monitor more than 36γ PDCCH candidates and more than 56γ non-overlapping CCEs in each of the PCell and SCell in a 30 kHz slot.

[0367] Furthermore, when both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a span, it is the same as in the previous example. The difference is that different predefined monitoring upper limits per unit time are used for different unit times. Therefore, the details are not described again in this specification.

[0368] In yet another solution of implementation 2.2.3, the monitoring upper limit of PDCCH candidates in a unit time with subcarrier spacing μ is The scheduling parameter may include a first upper limit corresponding to each of the first scheduling cell and the second scheduling cell, the first upper limit corresponding to each of the first scheduling cell and the second scheduling cell being equal to the product of γ and a first predetermined upper limit corresponding to the first scheduling cell, and / or a second upper limit corresponding to each of the first scheduling cell and the second scheduling cell being equal to the product of γ and a second predetermined upper limit corresponding to the first scheduling cell.

[0369] For example, it is assumed that the subcarrier spacing of the SCell is 30 kHz, the subcarrier spacing of the PCell is also 30 kHz, and both the PCell and the SCell can schedule the PCell. Both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a slot. When the PCell and the SCell are configured in two control resource set pools, CORESETPool, respectively, and the PCell is configured in a1 and the SCell is configured in a2, the monitoring upper limit of the PDCCH candidate in the 30 kHz slot is The upper limit may include a first upper limit corresponding to each of the PCell and SCell, the first upper limit corresponding to each of the PCell and SCell being equal to the product of γ and the first predefined upper limit for a 30 kHz slot in Table 1, i.e., 36γ, and a second upper limit corresponding to each of the PCell and SCell, the second upper limit corresponding to each of the PCell and SCell being equal to the product of γ and the second predefined upper limit for a 30 kHz slot in Table 2, i.e., 56γ.

[0370] In other words, the terminal device does not need to monitor more than 36γ PDCCH candidates and more than 56γ non-overlapping CCEs in each of the PCell and SCell in a 30 kHz slot.

[0371] Furthermore, when both the PCell and the SCell are configured so that the monitoring upper limit is determined at the granularity of a span, it is the same as in the previous example. The difference is that different predefined monitoring upper limits per unit time are used for different unit times. Therefore, the details are not described again in this specification.

[0372] Embodiment 3: A downlink control information transmission method 300.

[0373] In the downlink control information transmission method 300, the first configuration information may be restricted to satisfy one or more of the aforementioned characteristics.

[0374] 10 is a schematic flowchart of a downlink control information transmission method 300 according to an embodiment of the present application. As shown in FIG. 10, the downlink control information transmission method 300 may include, but is not limited to, the following steps:

[0375] S301: A network device transmits first setting information.

[0376] S302: The terminal device receives first setting information.

[0377] The first configuration information instructs the terminal device to monitor physical downlink control channel (PDCCH) candidates in the first scheduling cell and the second scheduling cell, and the PDCCH candidates are used to carry downlink control information for scheduling data transmission in the same scheduled cell. For some descriptions of the first configuration information, please refer to the related content of embodiment 1. Details will not be described again here.

[0378] In this embodiment of the present application, when the first scheduling cell and the second scheduling cell respectively correspond to different subcarrier intervals, the first configuration information has the following characteristics: (1) Both the first scheduling cell and the second scheduling cell are configured so that the monitoring upper limit is determined at a slot granularity; (2) Both the first scheduling cell and the second scheduling cell are configured such that the monitoring upper limit is determined at the granularity of a span; (3) The number of control resource set pools CORESETPool set for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool set for each is 1; (4) The number of control resource set pools CORESETPool set for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool set for each is 2; (5) the first scheduling cell is configured in the control resource set pool CORESETPool, and the second scheduling cell is not configured in CORESETPool; or (6) the first scheduling cell is not configured in the control resource set pool CORESETPool, and the second scheduling cell is configured in CORESETPool; or (7) The first scheduling cell and the second scheduling cell are both configured such that the monitoring upper limit is determined with a span granularity, and monitoring is performed in the first monitoring cell and the second monitoring cell using a combination (X, Y), and the second scheduling cell has a symbol group whose starting position overlaps with the starting position of any symbol group in the first scheduling cell, and a symbol group is formed every X symbols, and the subcarrier spacing of the active downlink bandwidth portion in the first scheduling cell is greater than the subcarrier spacing of the active downlink bandwidth portion in the second scheduling cell, and the combination (X, Y) indicates that the spacing between the starting symbols of two consecutive spans is greater than or equal to X symbols, and each span is less than or equal to Y symbols. Satisfy one or more of the following:

[0379] Optionally, with regard to feature (1), the fact that both the first scheduling cell and the second scheduling cell are configured such that the monitoring upper limit is determined at a slot granularity may be as follows: the first scheduling cell and the second scheduling cell are not configured with an r16 monitoring capability (r16monitoringcapability); the first scheduling cell and the second scheduling cell are not configured with a monitoring capability configuration-r16 (monitoringCapabilityConfig-r16) equal to the r16 monitoring capability (r16monitoringcapability); the first scheduling cell and the second scheduling cell are not configured with a monitoring capability configuration-r16 (monitoringCapabilityConfig-r16) equal to the r16 monitoring capability (r16monitoringcapability); the first scheduling cell and the second scheduling cell are each configured with a monitoring capability configuration-r16 (monitoringCapabilityConfig-r16) equal to r15 monitoring capability (r15monitoringcapability); the first scheduling cell and the second scheduling cell are each configured with r15 monitoring capability (r15monitoringcapability); or the first scheduling cell is configured with a monitoring capability configuration-r16 (monitoringCapabilityConfig-r16) equal to r15 monitoring capability (r15monitoringcapability) and the second scheduling cell is not configured with monitoringCapabilityConfig-r16.

[0380] Optionally, with regard to feature (2), the first scheduling cell and the second scheduling cell are both configured such that the monitoring upper limit is determined at the granularity of a span, which may be as follows: the first scheduling cell and the second scheduling cell are each configured with an r16 monitoring capability (r16monitoringcapability), or the first scheduling cell and the second scheduling cell are each configured with a monitoring capability configuration-r16 (monitoringCapabilityConfig-r16) equal to the r16 monitoring capability (r16monitoringcapability). For a schematic diagram of one span, please refer to the related content of FIG. 5. The details will not be described again here.

[0381] Optionally, with regard to features (3) and (4), a control resource set pool CORESETPool configured for the first scheduling cell and the second scheduling cell, respectively, may be a control resource set pool index CORESETPoolIndex configured for the first scheduling cell and the second scheduling cell, respectively. Correspondingly, the number of CORESETPools may be the number of CORESETPoolIndex.

[0382] Regarding feature (7), for example, as shown in FIG. 11, it is assumed that the subcarrier spacing of the active downlink bandwidth portion in the SCell is larger than the subcarrier spacing of the active downlink bandwidth portion in the PCell, both the first scheduling cell and the second scheduling cell are configured such that the monitoring upper limit is determined with a granularity of a span, and monitoring is performed in the first monitoring cell and the second monitoring cell using the combination (4, 3). Specifically, in FIG. 7, X is equal to 4 and Y is equal to 3. In this case, the PCell has four symbols (symbol groups) whose starting positions overlap with the starting positions of any four symbols (symbol groups) in the SCell. Specifically, the PCell has four symbols, for example, symbol 0 to symbol 3 in the PCell, and the starting symbol overlaps with the starting symbols of all four symbols in the SCell, for example, symbol 0 to symbol 3.

[0383] In this embodiment of the present application, when the first scheduling cell and the second scheduling cell separately correspond to the same subcarrier interval, the first configuration information has the following characteristics: (1) Both the first scheduling cell and the second scheduling cell are configured so that the monitoring upper limit is determined at a slot granularity; (2) Both the first scheduling cell and the second scheduling cell are configured such that the monitoring upper limit is determined at the granularity of a span; (3) The number of control resource set pools CORESETPool set for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool set for each is 1; (4) The number of control resource set pools CORESETPool set for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool set for each is 2; (5) the first scheduling cell is configured in the control resource set pool CORESETPool, and the second scheduling cell is not configured in CORESETPool; or (6) Both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined with a granularity of a span, and monitoring is performed in the first monitoring cell and the second monitoring cell using a combination (X, Y), where the combination (X, Y) indicates that the interval between the start symbols of two consecutive spans is equal to or greater than X symbols, and each span is equal to or less than Y symbols. Satisfy one or more of the following:

[0384] For the explanation of features (1) to (5), please refer to the relevant parameters of different subcarrier spacings mentioned above, and the details will not be repeated here.

[0385] Correspondingly, the method further includes the following steps:

[0386] S303: The network device determines, for the same scheduled cell, a monitoring upper limit of PDCCH candidates in one or more unit times.

[0387] S304: When the first configuration information satisfies one or more of the aforementioned characteristics, the terminal device determines, for the same scheduled cell, a monitoring upper limit of PDCCH candidates in one or more unit times.

[0388] The one or more unit times are determined based on subcarrier spacing of active downlink bandwidth portions of one or more scheduling cells in the first scheduling cell and the second scheduling cell. For example, regarding determining a monitoring upper limit of PDCCH candidates in multiple unit times for the same scheduled cell, see the related description of embodiment 1. For example, regarding determining a monitoring upper limit of PDCCH candidates in the same unit time for the same scheduled cell, see the related description of embodiment 2.

[0389] Specifically, when the first scheduling cell and the second scheduling cell respectively correspond to the same subcarrier interval, step S303 or S304 includes determining a monitoring upper limit of PDCCH candidates for the same scheduled cell in the same unit time. Optionally, for a description of step S303 or S304, please refer to the related content of embodiment 2. The details will not be described again here.

[0390] Optionally, when the first scheduling cell and the second scheduling cell correspond to different subcarrier intervals, respectively, step S303 or S304 includes determining a monitoring upper limit of PDCCH candidates in the first unit time and the second unit time for the same scheduled cell. Optionally, for a description of step S303 or S304, please refer to the related content of embodiment 1. The details will not be described again here.

[0391] Correspondingly, in the method, the terminal device may receive first configuration information, and expect the first configuration information to satisfy one or more of the above-mentioned characteristics. When the first configuration information does not satisfy any one of the above-mentioned characteristics, it may be determined that PDCCH candidates for the scheduled cell are not monitored. Optionally, the method further includes the following steps:

[0392] S305: When the first configuration information does not satisfy any one of the aforementioned characteristics, the terminal device determines that PDCCH candidates are not monitored for the scheduled cell.

[0393] Optionally, when the first configuration information does not satisfy any one of the aforementioned characteristics, the terminal device may determine that a monitoring upper limit of PDCCH candidates is not calculated for the scheduled cell.

[0394] In addition, in the embodiment of the present application, from another perspective, when the first scheduling cell and the second scheduling cell correspond to different subcarrier intervals, and the first configuration information does not satisfy one or more of the following characteristics, the terminal determines to calculate a monitoring upper limit of the PDCCH candidate: (1) One of the first scheduling cell and the second scheduling cell is configured so that the monitoring upper limit is determined at the granularity of a slot, and the other scheduling cell is configured so that the monitoring upper limit is determined at the granularity of a span. (2) The number of CORESETPools set for one of the first scheduling cell and the second scheduling cell is 2, and the number of CORESETPools set for the other scheduling cell is 1; (3) The number of CORESETPools configured for one of the first scheduling cell and the second scheduling cell is 2, and the other scheduling cell is not configured with CORESETPool; or (4) Both the first scheduling cell and the second scheduling cell are configured such that the monitoring upper limit is determined with a span granularity, and the monitoring is performed using different combinations (X, Y) in the first monitoring cell and the second monitoring cell, where the combination (X, Y) indicates that the interval between the start symbols of two consecutive spans is equal to or greater than X symbols, and each span is equal to or less than Y symbols; or (5) Both the first scheduling cell and the second scheduling cell are configured such that the monitoring upper limit is determined at a granularity of a span, and monitoring is performed in the first monitoring cell and the second monitoring cell using a combination (X, Y), and the second scheduling cell does not have a symbol group whose starting position overlaps with the starting position of at least one symbol group in the first scheduling cell, and constitutes a symbol group every X symbols, and the combination (X, Y) indicates that the interval between the starting symbols of two consecutive spans is equal to or greater than X symbols and each span is equal to or less than Y symbols.

[0395] In another aspect of the embodiment of the present application, when the first scheduling cell and the second scheduling cell separately correspond to the same subcarrier interval, and the first configuration information does not satisfy one or more of the following characteristics, the terminal determines to calculate a monitoring upper limit of the PDCCH candidate: (1) One of the first scheduling cell and the second scheduling cell is configured so that the monitoring upper limit is determined at the granularity of a slot, and the other scheduling cell is configured so that the monitoring upper limit is determined at the granularity of a span. (2) The number of CORESETPools set for one of the first scheduling cell and the second scheduling cell is 2, and the number of CORESETPools set for the other scheduling cell is 1; (3) The number of CORESETPools configured for one of the first scheduling cell and the second scheduling cell is 2, and the other scheduling cell is not configured with CORESETPool; or (4) Both the first scheduling cell and the second scheduling cell are configured such that the monitoring upper limit is determined at a granularity of a span, and monitoring is performed in the first monitoring cell and the second monitoring cell using different combinations (X, Y), where the combinations (X, Y) indicate that the interval between the start symbols of two consecutive spans is equal to or greater than X symbols and each span is equal to or less than Y symbols.

[0396] It can be seen that this implementation restricts the relevant characteristics of the first configuration information, which helps determine the upper limit of monitoring PDCCH candidates per unit time under some restrictive conditions, thereby simplifying the processing complexity.

[0397] Embodiment 4: A downlink control information transmission method 400.

[0398] In the downlink control information transmission method 400, for a plurality of scheduled cells, a monitoring upper limit of all PDCCH candidates in the plurality of scheduled cells within a unit time having a subcarrier spacing μ may be determined.

[0399] 12 is a schematic flowchart of a downlink control information transmission method 400 according to an embodiment of the present application. The downlink control information transmission method 400 may include, but is not limited to, the following steps:

[0400] S401: A network device transmits first setting information.

[0401] S402: The terminal device receives first setting information.

[0402] S403: The network device determines, for a plurality of scheduled cells, a monitoring upper limit of all PDCCH candidates in the plurality of scheduled cells within a unit time having a subcarrier spacing μ.

[0403] S404: The terminal device determines, for a plurality of scheduled cells, a monitoring upper limit of all PDCCH candidates in the plurality of scheduled cells within a unit time having a subcarrier spacing μ.

[0404] The plurality of scheduling cells are all scheduling cells whose subcarrier spacing of an active downlink bandwidth portion is μ in the cell connected to the terminal device, and the plurality of scheduled cells are all scheduled cells that are scheduled by the plurality of scheduling cells, respectively. Optionally, the plurality of scheduling cells may include a scheduling cell for self-scheduling and a scheduling cell for cross-carrier scheduling.

[0405] Optionally, for the multiple scheduling cells, the subcarrier spacing of the active downlink bandwidth portion is μ in unit time, and the monitoring upper limit of PDCCH candidates in all scheduling cells with subcarrier spacing μ may also be referred to as the actual monitoring upper limit of the terminal device for the multiple scheduling cells.

[0406] Optionally, the network device may first determine the first configuration information and perform step 403 of determining the actual monitoring upper limit of the terminal device, and then perform step 401 of sending the first configuration information to the terminal device, and the terminal device performs steps S402 and S404. In another optional implementation, the network device may jointly determine the first configuration information and the actual monitoring upper limit of the terminal device for a plurality of scheduled cells, and then perform step 401 of sending the first configuration information to the terminal device, and the terminal device performs steps S402 and S404.

[0407] In an optional implementation, for the multiple scheduled cells, the monitoring upper limit is determined based on a predetermined per-unit-time monitoring upper limit corresponding to the scheduling cell having a subcarrier spacing of μ. Specifically, within a unit time having a subcarrier spacing μ, for the multiple scheduled cells, the maximum total number of PDCCH candidates in the multiple scheduling cells is determined based on a predetermined maximum number of PDCCH candidates in one scheduling cell having a subcarrier spacing of μ, and the maximum total number of non-overlapping CCEs in the multiple scheduling cells is determined based on a predetermined maximum number of non-overlapping CCEs in one scheduling cell having a subcarrier spacing of μ.

[0408] The predetermined maximum number of PDCCH candidates in one scheduling cell with subcarrier spacing μ and the predetermined maximum number of non-overlapping CCEs in one scheduling cell with subcarrier spacing μ can be obtained by querying a table, with reference to the description of embodiment 1.

[0409] Optionally, for multiple scheduled cells, a monitoring upper limit of all PDCCH candidates in the multiple scheduling cells within a unit time with subcarrier spacing μ is determined based on the number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell in different implementations. A default maximum number of PDCCH candidates in one scheduling cell with subcarrier spacing μ is determined in the following implementations.

[0410] Implementation 4.1: For control resource sets corresponding to the same CORESETPool, when multiple scheduling cells with a subcarrier spacing of μ in the active downlink bandwidth portion are all configured so that the monitoring upper limit is determined at slot granularity, and when multiple scheduling cells are not configured in the control resource set pool CORESETPool or are configured in CORESETPool respectively; when one of the multiple scheduling cells is configured in CORESETPool and the other scheduling cell is not configured in CORESETPool, or when multiple scheduling cells are configured in two CORESETPools respectively; Maximum total number of PDCCH candidates in multiple scheduling cells in a slot with subcarrier spacing μ

[0411]

number

[0412] teeth,

[0413]

number

[0414] and Maximum total number of non-overlapping CCEs in multiple scheduling cells in a slot with subcarrier spacing μ

[0415]

number

[0416] teeth,

[0417]

number

[0418] is.

[0419] N μ denotes the number of cells corresponding to the multiple scheduling cells that are respectively scheduled by the multiple scheduling cells; N total denotes the total number of all scheduled cells respectively scheduled by all scheduling cells corresponding to all subcarrier intervals of the active downlink bandwidth portion;

[0420]

number

[0421] denotes a first predetermined upper limit (i.e., a predetermined upper limit of PDCCH candidates per unit time in a single cell) corresponding to one scheduling cell with a subcarrier spacing of μ in the active downlink bandwidth portion;

[0422]

number

[0423] denotes the predetermined upper limit corresponding to one scheduling cell with a subcarrier spacing of μ in the active downlink bandwidth portion (i.e., the predetermined upper limit of PDCCH candidates per unit time in a single cell); N terminal device capability indicates the number of cells available to be monitored as reported by the terminal device. Optionally, N terminal device capability is a default value and indicates the number of cells that can be supported by the terminal device.

[0424] Implementation 4.2: Compared with the aforementioned Implementation 4.1, in addition to the restriction conditions of Implementation 4.1, this implementation further includes: when multiple scheduling cells whose subcarrier spacing of the active downlink bandwidth portion is μ jointly correspond to the first parameter a; Maximum total number of PDCCH candidates in multiple scheduling cells in a slot with subcarrier spacing μ

[0425]

number

[0426] teeth,

[0427]

number

[0428] and Maximum total number of non-overlapping CCEs in multiple scheduling cells in a slot with subcarrier spacing μ

[0429]

number

[0430] teeth,

[0431]

number

[0432] is.

[0433] The first parameter a is used to determine the number of cells corresponding to scheduled cells that are scheduled by a scheduling cell with a subcarrier spacing μ in the active downlink bandwidth portion.

[0434] Implementation 4.3: All scheduling cells with a subcarrier spacing of μ in the active downlink bandwidth portion are configured so that the monitoring upper limit is determined at slot granularity; The plurality of scheduling cells may include:

[0435]

number

[0436] a first-type scheduling cell, the first-type scheduling cell having a subcarrier spacing μ, not configured in two control resource set pools CORESETPool, and not co-scheduling the scheduled cell with another scheduling cell;

[0437]

number

[0438] a second-type scheduling cell, the second-type scheduling cell having a subcarrier spacing of μ, configured in two CORESETPools, and not co-scheduling the scheduled cell with another scheduling cell;

[0439]

number

[0440] a third-type scheduling cell, the third-type scheduling cell having a subcarrier spacing of μ, not configured in two CORESETPools, and co-scheduling the scheduled cell with another scheduling cell;

[0441]

number

[0442] a fourth type scheduling cell, the fourth type scheduling cell having a subcarrier spacing μ, configured in two CORESETPools, and co-scheduling the scheduled cell with another scheduling cell; Includes.

[0443] The number of cells corresponding to the scheduled cells scheduled by each third-type scheduling cell or each fourth-type scheduling cell is a μ is equal to.

[0444] In all scheduling cells corresponding to all subcarrier intervals of the active downlink bandwidth portion, The number of scheduling cells whose subcarrier spacing of the active downlink bandwidth portion is the subcarrier spacing with index j, which are not configured with two control resource set pool indices CORESETPool respectively, and which do not schedule the scheduled cell together with another scheduling cell, is

[0445]

number

[0446] and The number of scheduling cells whose subcarrier spacing of the active downlink bandwidth portion is the subcarrier spacing with index j, each configured in two CORESETPools, and which do not schedule the scheduled cell together with another scheduling cell is

[0447]

number

[0448] and The number of scheduling cells whose subcarrier spacing of the active downlink bandwidth portion is the subcarrier spacing with index j, which are not configured in two CORESETPools respectively, and which schedule the scheduled cell together with another scheduling cell is

[0449]

number

[0450] and The number of scheduling cells whose subcarrier spacing of the active downlink bandwidth portion is the subcarrier spacing with index j, each configured in two CORESETPools, and scheduling the scheduled cell together with another scheduling cell is

[0451]

number

[0452] and The number of cells corresponding to the scheduled cells scheduled by the scheduling cell whose subcarrier spacing of the active downlink bandwidth portion is the subcarrier spacing with index j is a j is equal to.

[0453] N terminal device capability denotes the number of cells available to be monitored as reported by the terminal device.

[0454] In this case, the maximum total number of PDCCH candidates in multiple scheduling cells in a slot with subcarrier spacing μ

[0455]

number

[0456] teeth,

[0457]

number

[0458] and Maximum total number of non-overlapping CCEs in multiple scheduling cells in a slot with subcarrier spacing μ

[0459]

number

[0460] teeth,

[0461]

number

[0462] is.

[0463] γ is used to determine the number of cells corresponding to the scheduled cells that are scheduled by the scheduling cells configured in the two CORESETPools.

[0464] Implementation 4.4: All scheduling cells with a subcarrier spacing of μ in the active downlink bandwidth portion are configured so that the monitoring upper limit is determined at a slot granularity; The plurality of scheduling cells may include:

[0465]

number

[0466] a plurality of first-type scheduling cells, each of which has a subcarrier spacing of μ, is not configured with two control resource set pool indices (CORESETPoolIndex), and does not co-schedule the scheduled cell with another scheduling cell;

[0467]

number

[0468] a second type scheduling cell, the second type scheduling cell having a subcarrier spacing of μ, configured with two CORESETPoolIndex, and not co-scheduling the scheduled cell with another scheduling cell; a corresponding to the scheduled cell scheduled by the (k+1)th third-type scheduling cell μk cells, 0≦k≦K u The third type of scheduling cell is a scheduling cell with a subcarrier spacing of μ, which is not configured with two CORESETPoolIndexes, and which schedules the scheduled cell together with another scheduling cell, a μk cells, a corresponding to the scheduled cell scheduled by the (l+1)-th fourth-type scheduling cell μl cells, 0≦l≦L u The fourth type of scheduling cell is a scheduling cell with a subcarrier spacing of μ, configured with two CORESETPoolIndex, and co-scheduling the scheduled cell with another scheduling cell, a μl cells and Includes.

[0469] In all scheduling cells corresponding to all subcarrier intervals of the active downlink bandwidth portion, The number of scheduling cells whose subcarrier spacing of the active downlink bandwidth portion is the subcarrier spacing with index j, which are not configured with two control resource set pool indices (CORESETPoolIndex) and do not schedule the scheduled cell together with another scheduling cell, is

[0470]

number

[0471] and The number of scheduling cells whose active downlink bandwidth portion subcarrier spacing is the subcarrier spacing with index j, each configured with two CORESETPoolIndex, and which do not co-schedule the scheduled cell with another scheduling cell is

[0472]

number

[0473] and The number of cells corresponding to the scheduled cell scheduled by the (k+1)th scheduling cell, whose subcarrier spacing of the active downlink bandwidth portion is the subcarrier spacing with index j, is a, which is not configured with two CORESETPoolIndexes, and which schedules the scheduled cell together with another scheduling cell. jk where 0≦k≦K j and The number of cells corresponding to the scheduled cell scheduled by the (l+1)th scheduling cell, whose subcarrier spacing of the active downlink bandwidth portion is the subcarrier spacing with index j, is set by two CORESETPoolIndexes, and the scheduled cell is scheduled together with another scheduling cell. jl where 0≦l≦L j is.

[0474] N terminal device capability denotes the number of cells available to be monitored as reported by the terminal device.

[0475] In this case, the maximum total number of PDCCH candidates in multiple scheduling cells in a slot with subcarrier spacing μ

[0476]

number

[0477] teeth,

[0478]

number

[0479] and Maximum total number of non-overlapping CCEs in multiple scheduling cells in a slot with subcarrier spacing μ

[0480]

number

[0481] teeth,

[0482]

number

[0483] is.

[0484] γ is used to determine the number of cells corresponding to the scheduled cells that are scheduled by the scheduling cells configured in the two CORESETPools.

[0485] In an implementation, in embodiment 1, embodiment 2, and embodiment 4, the first parameter a may be set by the network device. For example, a is equal to 1 or 2. In another implementation, in embodiment 1, embodiment 2, and embodiment 4, the first parameter a1 and the second parameter a2 may be set by the network device. For example, a1=0.5 and a2=0.5, a1=1, and a2=1; or 0≦a1≦1, 0≦a2≦1, and a1+a2=1. In yet another implementation, a1 and a2 are set by the network device. value For example, a1=a2=a / 2, or a1=a2=a.

[0486] In addition, in the present application, the first scheduling cell and the second scheduling cell not being configured in two CORESETPools may mean the following: the first scheduling cell and the second scheduling cell are not configured in the control resource set pool CORESETPool, respectively; the first scheduling cell and the second scheduling cell are configured in CORESETPool, respectively; the first scheduling cell is configured in CORESETPool, and the second scheduling cell is not configured in CORESETPool; or the first scheduling cell is not configured in CORESETPool, and the second scheduling cell is configured in CORESETPool.

[0487] Optionally, embodiment 4 may be combined with the above-described embodiments 1 to 3, whereby a monitoring upper limit of PDCCH candidates in one or more unit times is determined for one scheduled cell, and then a monitoring upper limit of PDCCH candidates in the unit times is determined for multiple scheduled cells. Thus, the network device sends PDCCH-related configurations to the terminal device based on these monitoring upper limits. Correspondingly, the terminal device monitors PDCCH candidates used to carry each DCI for scheduling one or more scheduled cells based on these monitoring upper limits.

[0488] In this embodiment of the present application, in the implementation, as described above, all of the multiple scheduling cells are configured so that the monitoring upper limit is determined at the granularity of a slot. In another implementation, all of the multiple scheduling cells are configured so that the monitoring upper limit is determined at the granularity of a span. For related content in this implementation, please refer to the related content above about determining the monitoring upper limit at the granularity of a slot. The difference is that the unit time is a span with a subcarrier spacing μ in the combination (X, Y). Correspondingly, in this implementation,

[0489]

number

[0490] but

[0491]

number

[0492] may be replaced by, indicating an upper limit on the sum of PDCCH candidates in multiple scheduling cells per span;

[0493]

number

[0494] but

[0495]

number

[0496] to indicate a predefined upper limit of PDCCH candidates in one scheduling cell per span;

[0497]

number

[0498] but

[0499]

number

[0500] may be replaced by , indicating an upper bound on the total non-overlapping CCEs in multiple scheduling cells per span;

[0501]

number

[0502] but

[0503]

number

[0504] may be replaced with , to indicate the predefined upper bound of non-overlapping CCEs in one scheduling cell per span.

[0505] In the foregoing embodiments provided in the present application, the methods provided in the embodiments of the present application are described separately from the perspectives of a terminal device and a network device. To implement the functions of the methods provided in the embodiments of the present application, the terminal device and the network device each include a hardware structure and a software module, and may implement the functions in the form of a hardware structure, a software module, or a combination of a hardware structure and a software module. One of the functions may be performed by using a hardware structure, a software module, or a combination of a hardware structure and a software module. Below, a communication device in the embodiments of the present application will be described in detail with reference to Figures 13 to 15. The communication device is a terminal device or a network device. Optionally, the communication device may be a device within the terminal device or the network device.

[0506] 13 is a schematic block diagram of a communication device 1300. The communication device 1300 may perform related operations of a terminal device or a network device in the above-described method embodiments.

[0507] In one possible design, the communication device 1300 may include: a communication unit 1301 configured to receive first configuration information, the first configuration information instructing a terminal device to monitor physical downlink control channel (PDCCH) candidates in a first scheduling cell and a second scheduling cell, the PDCCH candidates being used to carry downlink control information for scheduling data transmission in the same scheduled cell; a processing unit 1302 configured to determine a monitoring upper limit of PDCCH candidates in a first unit time and a second unit time for the same scheduled cell; Including, but not limited to:

[0508] The first unit time is determined based on the subcarrier spacing of an active downlink bandwidth portion in the first scheduling cell, and the second unit time is determined based on the subcarrier spacing of an active downlink bandwidth portion in the second scheduling cell.

[0509] In one possible design, the communication device 1300 may include: a communication unit 1301 configured to transmit first configuration information, the first configuration information instructing a terminal device to monitor physical downlink control channel (PDCCH) candidates in a first scheduling cell and a second scheduling cell, the PDCCH candidates being used to carry downlink control information for scheduling data transmission in the same scheduled cell; and a processing unit 1302 configured to determine a monitoring upper limit of PDCCH candidates in a first unit time and a second unit time for the same scheduled cell; Including, but not limited to:

[0510] The first unit time is determined based on the subcarrier spacing of an active downlink bandwidth portion in the first scheduling cell, and the second unit time is determined based on the subcarrier spacing of an active downlink bandwidth portion in the second scheduling cell.

[0511] In an optional implementation, for the related content of the first scheduling information in the communication device 1300, please refer to the implementation and optional implementation in the downlink control information transmission method 100 or the downlink control information transmission method 400.Specifically, the first scheduling cell and the second scheduling cell have the following characteristics: both the first scheduling cell and the second scheduling cell are configured so that the monitoring upper limit is determined at the granularity of a slot; the first scheduling cell and the second scheduling cell are configured so that the monitoring upper limit is determined at the granularity of a span; the number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool configured for each is 1; the number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool configured for each is 2; the first scheduling cell is configured with the control resource set pool CORESETPool, and the second scheduling cell is not configured with the CORESETPool. the first scheduling cell is not configured in the control resource set pool CORESETPool, and the second scheduling cell is configured in CORESETPool; or the first scheduling cell and the second scheduling cell are configured such that the monitoring upper limit is determined with a granularity of a span, and monitoring is performed in the first monitoring cell and the second monitoring cell using a combination (X, Y), and the second scheduling cell has a symbol group whose starting position overlaps with the starting position of any symbol group in the first scheduling cell, constituting a symbol group every X symbols, the subcarrier spacing of the active downlink bandwidth portion in the first scheduling cell is greater than the subcarrier spacing of the active downlink bandwidth portion in the second scheduling cell, and the combination (X, Y) indicates that the spacing between the starting symbols of two consecutive spans is greater than or equal to X symbols, and each span is less than or equal to Y symbols.

[0512] In an optional implementation, for related content of the monitoring upper limit in the first unit time in the communication device 1300, please refer to the implementation and optional implementation in the downlink control information transmission method 100 or the downlink control information transmission method 400. Specifically, the monitoring upper limit in the first unit time is determined based on a predetermined monitoring upper limit per unit time corresponding to the first scheduling cell, and the monitoring upper limit in the second unit time is determined based on a predetermined monitoring upper limit per unit time corresponding to the second scheduling cell.

[0513] In an optional implementation, for related content of the monitoring upper limit for each unit time in the communication device 1300, please refer to the implementation and optional implementation in the downlink control information transmission method 100 or the downlink control information transmission method 400. The monitoring upper limit for each unit time includes a first upper limit for the unit time and / or a second upper limit for the unit time. The first upper limit is the maximum number of PDCCH candidates to be monitored, and the second upper limit is the maximum number of non-overlapping control channel elements (CCEs) among the monitored PDCCH candidates. The predefined monitoring upper limit per unit time corresponding to each scheduling cell includes a first predefined upper limit for the scheduling cell and / or a second predefined upper limit for the scheduling cell. The first predefined upper limit is the predefined maximum number of PDCCH candidates to be monitored, and the second predefined upper limit is the predefined maximum number of non-overlapping CCEs among the monitored PDCCH candidates.

[0514] In an optional implementation, for the control resource sets corresponding to the same CORESETPool, when the first scheduling cell and the second scheduling cell are not configured in the control resource set pool CORESETPool, respectively, or are configured in CORESETPool, when the first scheduling cell is configured in CORESETPool and not configured in CORESETPool for the second scheduling cell, when the first scheduling cell is not configured in CORESETPool and is configured in CORESETPool for the second scheduling cell, or when the first scheduling cell and the second scheduling cell are configured in two CORESETPools, respectively, the processing unit 1302 sets the monitoring upper limit in the first unit time as follows: a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit being determined based on a first predetermined upper limit corresponding to the first scheduling cell; a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit being determined based on a first predetermined upper limit corresponding to the first scheduling cell; a second upper limit determined based on a second predetermined upper limit corresponding to the first scheduling cell; a first upper limit corresponding to the first scheduling cell, the first upper limit determined based on a first predetermined upper limit corresponding to the first scheduling cell; and a second upper limit corresponding to the first scheduling cell, the second upper limit determined based on a second predetermined upper limit corresponding to the first scheduling cell; the monitoring upper limit in the second unit time determined by the processing unit 1302 is one or more of the following: a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit determined based on a first predetermined upper limit corresponding to the second scheduling cell; a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit determined based on a second predetermined upper limit corresponding to the second scheduling cell; a first upper limit corresponding to the second scheduling cell, the first upper limit determined based on a first predetermined upper limit corresponding to the second scheduling cell;and a second upper limit corresponding to the second scheduling cell, the second upper limit being determined based on a second predefined upper limit corresponding to the second scheduling cell;

[0515] In an optional implementation, when the first scheduling cell and the second scheduling cell are respectively configured with two control resource set pools CORESETPool, the processing unit 1302 may set the monitoring upper limit in the first unit time as follows: a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit being determined based on the third parameter and a first predefined upper limit corresponding to the first scheduling cell; a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit being determined based on the third parameter and the second predefined upper limit corresponding to the first scheduling cell; a first upper limit corresponding to the first scheduling cell, the first predefined upper limit being determined based on the third parameter and the first predefined upper limit corresponding to the first scheduling cell; and a second upper limit corresponding to the first scheduling cell, the second upper limit being determined based on the third parameter and the second predefined upper limit corresponding to the first scheduling cell. the monitoring upper limit in the second unit time determined by the processing unit 1302 includes one or more of: a first upper limit corresponding to the first scheduling cell and the second scheduling cell, the first upper limit determined based on the third parameter and the first predefined upper limit corresponding to the second scheduling cell; a second upper limit corresponding to the first scheduling cell and the second scheduling cell, the second upper limit determined based on the third parameter and the second predefined upper limit corresponding to the second scheduling cell; a first upper limit corresponding to the second scheduling cell, the first upper limit determined based on the third parameter and the first predefined upper limit corresponding to the second scheduling cell; and a second upper limit corresponding to the second scheduling cell, the second upper limit determined based on the third parameter and the second predefined upper limit corresponding to the second scheduling cell.The third parameter is used to determine the number of cells corresponding to the scheduled cells that are scheduled by the scheduling cells configured in the two CORESETPools.

[0516] In an optional implementation, the processing unit 1302 is further configured to determine, for a plurality of scheduled cells, a monitoring upper limit of all PDCCH candidates in the plurality of scheduling cells within a unit time period having a subcarrier spacing μ. The plurality of scheduling cells are all scheduling cells whose active downlink bandwidth portions have a subcarrier spacing μ, and the plurality of scheduled cells are all scheduled cells that are scheduled by the plurality of scheduling cells, respectively. For the plurality of scheduled cells, the monitoring upper limit is determined based on a predetermined monitoring upper limit per unit time period corresponding to the scheduling cells whose subcarrier spacing μ is μ.

[0517] In yet another possible design, communication device 1300 may include: a communication unit 1301 configured to receive first configuration information, the first configuration information instructing a terminal device to monitor physical downlink control channel (PDCCH) candidates in a first scheduling cell and a second scheduling cell, the PDCCH candidates being used to carry downlink control information for scheduling data transmission in the same scheduled cell; a processing unit 1302 configured to determine a monitoring upper limit of PDCCH candidates in the same unit time for the same scheduled cell; Including, but not limited to:

[0518] The same unit time is determined based on the subcarrier spacing of the active downlink bandwidth portion in the first scheduling cell or the second scheduling cell.

[0519] In yet another possible design, communication device 1300 may include: a communication unit 1301 configured to transmit first configuration information, the first configuration information instructing a terminal device to monitor physical downlink control channel (PDCCH) candidates in a first scheduling cell and a second scheduling cell, the PDCCH candidates being used to carry downlink control information for scheduling data transmission in the same scheduled cell; and a processing unit 1302 configured to determine a monitoring upper limit of PDCCH candidates in the same unit time for the same scheduled cell; Including, but not limited to:

[0520] The same unit time is determined based on the subcarrier spacing of the active downlink bandwidth portion in the first scheduling cell or the second scheduling cell.

[0521] In yet another possible design, communication device 1300 may include: a communication unit 1301 configured to receive first configuration information, the first configuration information instructing a terminal device to monitor physical downlink control channel (PDCCH) candidates in a first scheduling cell and a second scheduling cell, the PDCCH candidates being used to carry downlink control information for scheduling data transmission in the same scheduled cell; The first setting has the following characteristics: Both the first scheduling cell and the second scheduling cell are configured such that the monitoring upper limit is determined at a slot granularity. Both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined at a granularity of a span. The number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool configured for each is 1; The number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool configured for each is 2; The first scheduling cell is configured in the control resource set pool CORESETPool and the second scheduling cell is not configured in CORESETPool, or Both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined with a granularity of a span, and monitoring is performed using a combination (X, Y) in the first monitoring cell and the second monitoring cell, and the second scheduling cell has a symbol group whose starting position overlaps with the starting position of any symbol group in the first scheduling cell, and a symbol group is configured every X symbols. a processing unit 1302 configured to determine that no PDCCH candidates are monitored for a scheduled cell when one or more of the following conditions are not satisfied; Including, but not limited to:

[0522] The combination (X, Y) indicates that the spacing between the starting symbols of two consecutive spans is at least X symbols, and each span is at most Y symbols.

[0523] In yet another possible design, the communications device 1300 may include, but is not limited to, a communications unit 1301 and a processing unit 1302 .

[0524] The communication unit 1301 is configured to transmit first configuration information, which instructs the terminal device to monitor physical downlink control channel PDCCH candidates in the first scheduling cell and the second scheduling cell, where the PDCCH candidates are used to carry downlink control information for scheduling data transmission in the same scheduled cell.

[0525] The first setting information has the following characteristics: Both the first scheduling cell and the second scheduling cell are configured such that the monitoring upper limit is determined at a slot granularity. Both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined at a granularity of a span. The number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool configured for each is 1; The number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool configured for each is 2; The first scheduling cell is configured in the control resource set pool CORESETPool and the second scheduling cell is not configured in CORESETPool, or Both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined with a granularity of a span, and monitoring is performed using a combination (X, Y) in the first monitoring cell and the second monitoring cell, and the second scheduling cell has a symbol group whose starting position overlaps with the starting position of any symbol group in the first scheduling cell, and a symbol group is configured every X symbols. Satisfy one or more of the following:

[0526] The combination (X, Y) indicates that the spacing between the starting symbols of two consecutive spans is at least X symbols, and each span is at most Y symbols.

[0527] The processing unit 1302 is configured to determine, for the same scheduled cell, a monitoring upper limit of PDCCH candidates in a first time unit and a second time unit.

[0528] The first unit time is determined based on the subcarrier spacing of an active downlink bandwidth portion in the first scheduling cell, and the second unit time is determined based on the subcarrier spacing of an active downlink bandwidth portion in the second scheduling cell.

[0529] In yet another possible design, communication device 1300 may include: a communication unit 1301 configured to receive first configuration information, the first configuration information instructing a terminal device to monitor physical downlink control channel (PDCCH) candidates in a first scheduling cell and a second scheduling cell, the PDCCH candidates being used to carry downlink control information for scheduling data transmission in the same scheduled cell; The first setting has the following characteristics: Both the first scheduling cell and the second scheduling cell are configured such that the monitoring upper limit is determined at a slot granularity. Both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined at a granularity of a span. The number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool configured for each is 1; The number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool configured for each is 2; The first scheduling cell is configured in the control resource set pool CORESETPool and the second scheduling cell is not configured in CORESETPool, or Both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined with a granularity of a span, and monitoring is performed using a combination (X, Y) in the first monitoring cell and the second monitoring cell; a processing unit 1302 configured to determine that no PDCCH candidates are monitored for a scheduled cell when one or more of the following conditions are not satisfied; Including, but not limited to:

[0530] The combination (X, Y) indicates that the spacing between the starting symbols of two consecutive spans is at least X symbols, and each span is at most Y symbols.

[0531] In yet another possible design, the communications device 1300 may include, but is not limited to, a communications unit 1301 and a processing unit 1302 .

[0532] The communication unit 1301 is configured to transmit first configuration information, which instructs the terminal device to monitor physical downlink control channel PDCCH candidates in the first scheduling cell and the second scheduling cell, where the PDCCH candidates are used to carry downlink control information for scheduling data transmission in the same scheduled cell.

[0533] The first setting information has the following characteristics: Both the first scheduling cell and the second scheduling cell are configured such that the monitoring upper limit is determined at a slot granularity. Both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined at a granularity of a span. The number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool configured for each is 1; The number of control resource set pools CORESETPool configured for the first scheduling cell and the second scheduling cell is the same, and the number of CORESETPool configured for each is 2; The first scheduling cell is configured in the control resource set pool CORESETPool and the second scheduling cell is not configured in CORESETPool, or Both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined with a granularity of a span, and monitoring is performed using a combination (X, Y) in the first monitoring cell and the second monitoring cell, and the second scheduling cell has a symbol group whose starting position overlaps with the starting position of any symbol group in the first scheduling cell, and a symbol group is configured every X symbols. Satisfy one or more of the following:

[0534] The combination (X, Y) indicates that the spacing between the starting symbols of two consecutive spans is at least X symbols, and each span is at most Y symbols.

[0535] The processing unit 1302 is configured to determine a monitoring upper limit of PDCCH candidates in the same unit time for the same scheduled cell.

[0536] The same unit time is determined based on the subcarrier spacing of the active downlink bandwidth portion in the first scheduling cell or the second scheduling cell.

[0537] Optionally, the communication device 1300 may further perform one or more implementations of the downlink control information transmission method 100 to the downlink control information transmission method 400. The details will not be described again here.

[0538] FIG. 14 is a schematic block diagram of a communication device 1400.

[0539] In implementation, the communication device 1400 corresponds to a terminal device in the aforementioned downlink control information transmission method. Optionally, the communication device 1400 is an apparatus, such as a chip, a chip system, or a processor, in the terminal device that executes the aforementioned method embodiments. The communication device 1400 may be configured to implement the methods described in the aforementioned method embodiments. For details, please refer to the descriptions in the aforementioned method embodiments.

[0540] In another implementation, the communication device 1400 corresponds to the network device in the aforementioned downlink control information transmission method. Optionally, the communication device 1400 is an apparatus, such as a chip, a chip system, or a processor, in the network device that executes the aforementioned method embodiments. The communication device 1400 may be configured to implement the method described in the aforementioned method embodiments. For details, please refer to the descriptions in the aforementioned method embodiments.

[0541] The communications device 1400 may include one or more processors 1401. The processor 1401 may be a general-purpose processor, a special-purpose processor, etc. For example, the processor 1401 may be a baseband processor or a central processing unit. The baseband processor may be configured to process communication protocols and communication data, and the central processing unit may be configured to control a communications device (e.g., a base station, a baseband chip, a terminal, a terminal chip, a DU, or a CU) to execute a computer program and process data of the computer program.

[0542] The communications device 1400 may further include a transceiver 1405. The transceiver 1405 may be referred to as a transceiver unit, transceiver, transceiver circuit, etc., and is configured to implement transceiver functionality. The transceiver 1405 may include a receiver and a transmitter. The receiver may be referred to as a receiving machine, receiving circuit, etc., and is configured to implement receiving functionality. The transmitter may be referred to as a transmitting machine, transmitting circuit, etc., and is configured to implement transmitting functionality. Optionally, the communications device 1400 may further include an antenna 1406.

[0543] Optionally, the communication device 1400 may include one or more memories 1402. The memories may store instructions 1404. The instructions 1404 may be computer programs. The computer programs are executed by the communication device 1400, causing the communication device 1400 to perform the methods described in the preceding method embodiments. Optionally, the memory 1402 may further store data. The communication device 1400 and the memory 1402 may be located separately or integrated.

[0544] In implementation, the communication apparatus 1400 is configured to implement the functionality of the terminal device in the above method embodiments.

[0545] The processor 1401 is configured to execute step S103 of FIG. 8, step S203 of FIG. 9, or steps S304 and S305 of FIG.

[0546] The transceiver 1405 is configured to perform step S102 of FIG. 8, step S202 of FIG. 9, or step S302 of FIG.

[0547] In another implementation, the communications apparatus 1400 is configured to implement the functionality of the network device in the method embodiments described above.

[0548] The transceiver 1405 is configured to perform step S101 of FIG. 8, step S201 of FIG. 9, or step S301 of FIG.

[0549] The processor 1401 is configured to execute step S104 of FIG. 8, step S204 of FIG. 9, or step S303 of FIG.

[0550] In implementation, the processor 1401 may include a transceiver configured to implement receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit configured to implement receiving and transmitting functions may be separate or integrated. The transceiver circuit, interface, or interface circuit may be configured to read and write code / data. Alternatively, the transceiver circuit, interface, or interface circuit may be configured to transmit or forward signals.

[0551] In implementation, the processor 1401 may store instructions 1403. The instructions may be a computer program. The computer program 1403 executes on the processor 1401 to enable the communication device 1400 to perform the methods described in the previous method embodiments. The computer program 1403 may be fixed within the processor 1401. In this case, the processor 1401 may be implemented by hardware.

[0552] In implementations, the communications device 1400 may include circuitry that may implement the transmitting, receiving, or communication functions in the method embodiments described above.

[0553] For cases where the communication device may be a chip or a chip system, please refer to the schematic diagram of the structure of the chip shown in Figure 15. The chip shown in Figure 15 includes a processor 1501, an interface 1502, and a memory 1503. There may be one or more processors 1501, and there may also be multiple interfaces 1502. The memory 1503 may store relevant data.

[0554] The case where the chip is configured to implement the functions of the terminal device in the above method embodiment is described as follows.

[0555] The processor 1501 is configured to execute step S103 of FIG. 8, step S203 of FIG. 9, or step S304 of FIG.

[0556] The interface 1502 is configured to perform step S102 of FIG. 8, step S202 of FIG. 9, or step S302 of FIG.

[0557] Optionally, the chip may further perform the functions of the network device in the above method embodiments.

[0558] The interface 1502 is configured to perform step S101 of FIG. 8, step S201 of FIG. 9, or step S301 of FIG.

[0559] The processor 1501 is configured to execute step S104 of FIG. 8, step S204 of FIG. 9, or step S303 of FIG.

[0560] Optionally, the chip may further perform related implementations in the above-mentioned method embodiments. Details will not be described again here. For example, optionally, the communication device 1500 may further perform one or more of the downlink control information transmission method 100 to the downlink control information transmission method 400. Details will not be described again here.

[0561] Those skilled in the art will further appreciate that the various illustrative logic blocks and steps set forth in the embodiments of the present application may be implemented by electronic hardware, computer software, or a combination thereof. Whether a function is implemented by hardware or software depends on the particular application and overall system design requirements.

[0562] The present application further provides a computer-readable storage medium storing a computer program, which, when executed by a computer, performs the functions of any one of the above-described method embodiments.

[0563] The present application further provides a computer program product, which, when executed by a computer, performs the functions of any one of the aforementioned method embodiments.

[0564] All or part of the above-described embodiments may be implemented by software, hardware, firmware, or any combination thereof. When software is used for implementation, all or part of the embodiments may be implemented in the form of a computer program product. The computer program product includes one or more computer programs. When the computer programs are loaded into a computer and executed, the procedures or functions according to the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or another programmable device. The computer program may be stored in a computer-readable storage medium or transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer program may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, optical fiber, or digital subscriber line (DSL)) or wireless (e.g., infrared, radio, or microwave) techniques. The computer-readable storage medium may be any available medium accessible by a computer, or may be a data storage device, such as a server or data center, integrating one or more available media. The media available may be magnetic media (e.g., floppy disks, hard disk drives, or magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), semiconductor media (e.g., solid state disks (SSDs)), and the like.

Claims

1. 1. A downlink control information transmission method performed by a terminal device or a chip in the terminal device, comprising: receiving first configuration information, the first configuration information instructing the terminal device to monitor Physical Downlink Control Channel (PDCCH) candidates in a first scheduling cell and a second scheduling cell, the PDCCH candidates being used to carry downlink control information for scheduling data transmissions in the same scheduled cell; determining a monitoring upper limit for the PDCCH candidates in a first time unit and a second time unit for the same scheduled cell; the first unit time is determined based on a subcarrier spacing of an active downlink bandwidth portion in the first scheduling cell, and the second unit time is determined based on a subcarrier spacing of an active downlink bandwidth portion in the second scheduling cell, and the subcarrier spacing of the active downlink bandwidth portion in the first scheduling cell is different from the subcarrier spacing of the active downlink bandwidth portion in the second scheduling cell; A monitoring upper limit of the PDCCH candidates in the first unit time and the second unit time is a monitoring upper limit corresponding to the first scheduling cell in the first unit time and a monitoring upper limit corresponding to the second scheduling cell in the second unit time; a total monitoring upper limit corresponding to the first scheduling cell and the second scheduling cell in the first unit time; Including, the total monitoring upper limit corresponding to the first scheduling cell and the second scheduling cell in the first unit time is determined based on a predetermined monitoring upper limit per unit time corresponding to the subcarrier spacing of the active downlink bandwidth portion in the first scheduling cell.

2. The first setting information is Both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined at a slot granularity; or the first scheduling cell and the second scheduling cell are not configured in a control resource set pool, respectively; The method according to claim 1, wherein

3. 2. The method of claim 1, wherein the monitoring upper limit corresponding to the first scheduling cell in the first unit of time is determined based on a predefined monitoring upper limit per unit of time corresponding to the subcarrier spacing of the active downlink bandwidth portion in the first scheduling cell, and the monitoring upper limit corresponding to the second scheduling cell in the second unit of time is determined based on a predefined monitoring upper limit per unit of time corresponding to the subcarrier spacing of the active bandwidth portion in the second scheduling cell.

4. The monitoring upper limit includes a first upper limit and / or a second upper limit, the first upper limit being a maximum number of monitored PDCCH candidates, and the second upper limit being a maximum number of non-overlapping control channel elements (CCEs) among the monitored PDCCH candidates; 4. The method according to claim 1, wherein the predetermined monitoring upper limit per unit time comprises a first predetermined upper limit and / or a second predetermined upper limit, the first predetermined upper limit being a predetermined maximum number of monitored PDCCH candidates, and the second predetermined upper limit being a predetermined maximum number of non-overlapping CCEs among the monitored PDCCH candidates.

5. The first upper limit corresponding to the first scheduling cell is a 1 and the first predetermined upper limit corresponding to the first scheduling cell; The second upper limit corresponding to the first scheduling cell is a 1 and the second predetermined upper limit corresponding to the first scheduling cell; a 1 The method of claim 4 , wherein: represents a first parameter configured for the first scheduling cell.

6. 0≦a 1 6. The method of claim 5, wherein ≦1.

7. 1. A downlink control information transmission method performed by a network device or a chip in the network device, comprising: transmitting first configuration information, the first configuration information instructing a terminal device to monitor Physical Downlink Control Channel (PDCCH) candidates in a first scheduling cell and a second scheduling cell, the PDCCH candidates being used to carry downlink control information for scheduling data transmissions in the same scheduled cell; determining a monitoring upper limit for the PDCCH candidates in a first time unit and a second time unit for the same scheduled cell; the first unit time is determined based on a subcarrier spacing of an active downlink bandwidth portion in the first scheduling cell, and the second unit time is determined based on a subcarrier spacing of an active downlink bandwidth portion in the second scheduling cell, and the subcarrier spacing of the active downlink bandwidth portion in the first scheduling cell is different from the subcarrier spacing of the active downlink bandwidth portion in the second scheduling cell; A monitoring upper limit of the PDCCH candidates in the first unit time and the second unit time is a monitoring upper limit corresponding to the first scheduling cell in the first unit time and a monitoring upper limit corresponding to the second scheduling cell in the second unit time; a total monitoring upper limit corresponding to the first scheduling cell and the second scheduling cell in the first unit time; Including, the total monitoring upper limit corresponding to the first scheduling cell and the second scheduling cell in the first unit time is determined based on a predetermined monitoring upper limit per unit time corresponding to the subcarrier spacing of the active downlink bandwidth portion in the first scheduling cell.

8. The first setting information has the following characteristics: both the first scheduling cell and the second scheduling cell are configured such that a monitoring upper limit is determined at a slot granularity; the first scheduling cell and the second scheduling cell are not configured in a control resource set pool, respectively; 8. The method of claim 7, wherein one or more of the following are satisfied:

9. 8. The method of claim 7, wherein the monitoring upper limit corresponding to the first scheduling cell in the first unit of time is determined based on a predefined monitoring upper limit per unit of time corresponding to the subcarrier spacing of the active downlink bandwidth portion in the first scheduling cell, and the monitoring upper limit corresponding to the second scheduling cell in the second unit of time is determined based on a predefined monitoring upper limit per unit of time corresponding to the subcarrier spacing of the active bandwidth portion in the second scheduling cell.

10. The monitoring upper limit includes a first upper limit and / or a second upper limit, the first upper limit being a maximum number of monitored PDCCH candidates, and the second upper limit being a maximum number of non-overlapping control channel elements (CCEs) among the monitored PDCCH candidates; 10. The method according to claim 7, wherein the predetermined monitoring upper limit per unit time comprises a first predetermined upper limit and / or a second predetermined upper limit, the first predetermined upper limit being a predetermined maximum number of monitored PDCCH candidates, and the second predetermined upper limit being a predetermined maximum number of non-overlapping CCEs among the monitored PDCCH candidates.

11. The first upper limit corresponding to the first scheduling cell is a 1 and the first predetermined upper limit corresponding to the first scheduling cell; The second upper limit corresponding to the first scheduling cell is a 1 and the second predetermined upper limit corresponding to the first scheduling cell; a 1 The method of claim 10, wherein ∑ i represents a first parameter configured for the first scheduling cell.

12. 0≦a 1 12. The method of claim 11, wherein ≦1.

13. Apparatus configured to carry out the method of any one of claims 1 to 6.

14. Apparatus configured to carry out the method of any one of claims 7 to 12.

15. 13. A computer-readable storage medium storing a computer program that, when executed by a processor, performs the method of any one of claims 1 to 6 or any one of claims 7 to 12.

Images