Capability determination method and apparatus, and storage medium

Abstract

The present disclosure relates to the technical field of communications, and in particular relates to a capability determination method and apparatus, and a storage medium. The capability determination method comprises: processing multi cell schedule downlink control information (MC-DCI) which is received in a scheduling cell; and, on the basis of the processing capability of a first cell for unicast downlink control information, counting processing of the MC-DCI. According to the present disclosure, when MC-DCI is introduced, the processing capability of a terminal for unicast DCI may be defined according to the granularity being a single cell, so that after the terminal processes MC-DCI received in a scheduling cell, the MC-DCI may be counted on the basis of the processing capability of a first cell for unicast DCI, thereby facilitating improvement of the DCI processing capability of the terminal.

Description

Capability determination method, device, and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a capability determination method, a capability determination apparatus, a terminal, a network device, a communication system, and a storage medium. Background Art

[0002] In order to improve scheduling flexibility, it is proposed to schedule data on multiple cells through single downlink control information (DCI). For example, the downlink control information may be called multi-cell scheduling downlink control information (MC-DCI).

[0003] Furthermore, the terminal's ability to process downlink control information within a period of time is limited, and in related technologies, there are some technical problems when considering the terminal's ability to process MC-DCI.

[0004] Summary of the Invention

[0005] The embodiments of the present disclosure provide a capability determination method, device, and storage medium to solve technical problems in related technologies.

[0006] According to a first aspect of an embodiment of the present disclosure, a capability determination method is proposed, which is executed by a terminal. The method includes: processing downlink control information MC-DCI for scheduling multiple cells received in a scheduling cell; and counting the processing of the MC-DCI according to the first cell's processing capability of unicast downlink control information.

[0007] According to the second aspect of an embodiment of the present disclosure, a capability determination method is proposed, which is executed by a network device. The method includes: sending downlink control information MC-DCI for scheduling multiple cells to a terminal in a scheduling cell; and counting the MC-DCI processed by the terminal according to the processing capability of the first cell for unicast downlink control information.

[0008] According to the third aspect of an embodiment of the present disclosure, a capability determination device is proposed, which is executed by a terminal, and the device includes: a processing module, configured to process downlink control information MC-DCI for scheduling multiple cells received in a scheduling cell; and count the processing of the MC-DCI according to the first cell's processing capability of unicast downlink control information.

[0009] According to the fourth aspect of an embodiment of the present disclosure, a capability determination device is proposed, which is executed by a network device, and the device includes: a sending module, configured to send downlink control information MC-DCI for scheduling multiple cells to a terminal in a scheduling cell; a processing module, configured to count the MC-DCI processed by the terminal according to the processing capability of the first cell for unicast downlink control information.

[0010] According to the fifth aspect of an embodiment of the present disclosure, a capability determination method is proposed, including: a network device sends downlink control information MC-DCI for scheduling multiple cells to a terminal in a scheduling cell; the terminal processes the MC-DCI; and the terminal counts the processing of the MC-DCI according to the processing capability of the first cell for unicast downlink control information.

[0011] According to a sixth aspect of an embodiment of the present disclosure, a terminal is proposed, comprising: one or more processors; a memory coupled to the one or more processors, wherein the memory stores executable instructions, and when the executable instructions are executed by the one or more processors, the terminal executes the capability determination method described in any one of the first aspect and the optional embodiments of the first aspect.

[0012] According to the seventh aspect of the embodiments of the present disclosure, a network device is proposed, comprising: one or more processors; a memory coupled to the one or more processors, wherein the memory stores executable instructions, and when the executable instructions are executed by the one or more processors, the network device executes the capability determination method described in any one of the second aspect and the optional embodiments of the second aspect.

[0013] According to an eighth aspect of an embodiment of the present disclosure, a communication system is proposed, comprising a terminal and a network device, wherein the terminal is configured to implement the capability determination method described in any one of the first aspect and the optional embodiments of the first aspect, and the network device is configured to implement the capability determination method described in any one of the second aspect and the optional embodiments of the second aspect.

[0014] According to the ninth aspect of the embodiments of the present disclosure, a storage medium is proposed, which stores instructions. When the instructions are executed on a communication device, the communication device executes the capability determination method described in any one of the first aspect, the optional embodiment of the first aspect, the second aspect, and the optional embodiment of the second aspect.

[0015] According to an embodiment of the present disclosure, when MC-DCI is introduced, the terminal's processing capability for unicast DCI can be defined at the granularity of a single cell. Thus, after processing MC-DCI received in the scheduling cell, the terminal can count the MC-DCI based on the first cell's processing capability for unicast DCI. Because the first cell is a single cell, not a collection of cells, the terminal performs MC-DCI processing on the first cell, causing the first cell's processing capability for unicast DCI to reach its upper limit. The terminal is simply unable to process DCI for the scheduling first cell, meaning it can no longer process DCI on the first cell. However, this does not affect the terminal's ability to process DCI in other cells, and therefore, the terminal can still process DCI in other cells, thereby effectively improving the terminal's DCI processing capability. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0017] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0018] FIG2 is an interactive schematic diagram illustrating a capability determination method according to an embodiment of the present disclosure.

[0019] FIG3 is a schematic flowchart illustrating a capability determination method according to an embodiment of the present disclosure.

[0020] FIG4 is a schematic flowchart illustrating a capability determination method according to an embodiment of the present disclosure.

[0021] FIG5 is a schematic block diagram showing a capability determination device according to an embodiment of the present disclosure.

[0022] FIG6 is a schematic block diagram showing a capability determination device according to an embodiment of the present disclosure.

[0023] FIG7 is a schematic structural diagram of a communication device proposed in an embodiment of the present disclosure.

[0024] FIG8 is a schematic diagram of the structure of a chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0025] The embodiments of the present disclosure provide a capability determination method, an apparatus, and a storage medium.

[0026] In a first aspect, an embodiment of the present disclosure proposes a capability determination method, which is executed by a terminal, and the method includes: processing downlink control information MC-DCI for scheduling multiple cells received in a scheduling cell; and counting the processing of the MC-DCI according to the first cell's processing capability of unicast downlink control information.

[0027] In the above embodiment, when MC-DCI is introduced, the terminal's unicast DCI processing capability can be defined at the granularity of a single cell. Thus, after processing MC-DCI received in the scheduling cell, the terminal can count the MC-DCI based on the first cell's unicast DCI processing capability. Because the first cell is a single cell, not a collection of cells, the terminal processes MC-DCI in the first cell, causing the first cell's unicast DCI processing capability to reach its upper limit. The terminal is merely unable to process DCI for the scheduling first cell, meaning it can no longer process DCI in the first cell. However, this does not affect the terminal's ability to process DCI in other cells. Therefore, the terminal can still process DCI in other cells, thereby effectively improving the terminal's DCI processing capability.

[0028] In combination with some embodiments of the first aspect, in some embodiments, the first cell includes at least one of the following: a reference cell; the scheduling cell; a cell among the cells that can be scheduled by the MC-DCI; or a cell among the cells actually scheduled by the MC-DCI.

[0029] In combination with some embodiments of the first aspect, in some embodiments, the cells that can be scheduled by the MC-DCI are agreed upon by a protocol, or are configured by a network device.

[0030] In combination with some embodiments of the first aspect, in some embodiments, the cells that can be scheduled by the MC-DCI include at least one of the following: a cell with the smallest index among the cells that can be scheduled by the MC-DCI; or a cell with the largest index among the cells that can be scheduled by the MC-DCI.

[0031] In combination with some embodiments of the first aspect, in some embodiments, the cells in the cells actually scheduled by the MC-DCI are agreed upon by a protocol, or are configured by a network device.

[0032] In combination with some embodiments of the first aspect, in some embodiments, the cells in the cells actually scheduled by the MC-DCI include at least one of the following: the cell with the smallest index in the cells actually scheduled by the MC-DCI; or the cell with the largest index in the cells actually scheduled by the MC-DCI.

[0033] In combination with some embodiments of the first aspect, in some embodiments, the MC-DCI includes at least one of the following: a first MC-DCI for scheduling uplink transmission; and a second MC-DCI for scheduling downlink transmission.

[0034] In combination with some embodiments of the first aspect. In some embodiments, counting the processing of the MC-DCI according to the processing capability of the first cell for unicast downlink control information includes: determining a first count value for the first MC-DCI; determining a first difference between a first upper limit value of the DCI for scheduling uplink transmission in the processing capability of the first cell for unicast DCI and the first count value;

[0035] The method further includes: determining, based on the first difference, the number of other unicast DCIs for scheduling uplink transmission that the terminal can process in the scheduling cell within the unit time for receiving the first MC-DCI on the first cell.

[0036] In combination with some embodiments of the first aspect. In some embodiments, the counting of processing the MC-DCI according to the processing capability of the first cell for unicast downlink control information includes: determining a second count value for the second MC-DCI count; determining a second difference between a second upper limit value of the DCI for scheduling downlink transmission in the processing capability of the first cell for unicast DCI and the second count value;

[0037] The method further includes: determining, based on the second difference, the number of other unicast DCIs for scheduling downlink transmission that the terminal can process on the first cell in the scheduling cell within the unit time for receiving the second MC-DCI.

[0038] In the second aspect, an embodiment of the present disclosure proposes a capability determination method, which is executed by a network device, and the method includes: sending downlink control information MC-DCI for scheduling multiple cells to a terminal in a scheduling cell; and counting the MC-DCI processed by the terminal according to the processing capability of the first cell for unicast downlink control information.

[0039] In some embodiments, when MC-DCI is introduced, the terminal's processing capability for unicast DCI can be defined at the granularity of a single cell, so that after the network device sends MC-DCI to the terminal in the scheduling cell, the terminal can process the MC-DCI, and the network device can count the MC-DCI based on the first cell's processing capability for unicast DCI. Since the first cell is a single cell, not a collection of cells, even if the network device determines that the terminal performs an operation to process MC-DCI in the first cell, causing the first cell's processing capability for unicast DCI to reach an upper limit, it only determines that the terminal can no longer process the DCI of the scheduled first cell, that is, the terminal can no longer process DCI in the first cell, but it does not affect the terminal's ability to process DCI in other cells. Therefore, it can still be determined that the terminal can process DCI in other cells, thereby effectively improving the terminal's processing capability for DCI.

[0040] On this basis, in some embodiments, the network device can configure the terminal as needed, and the terminal's processing capability of unicast DCI in the first cell and other cells can be considered during the configuration process to avoid configuring the terminal beyond its processing capability of unicast DCI in the first cell and other cells.

[0041] In combination with some embodiments of the second aspect, in some embodiments, the first cell includes at least one of the following: a reference cell; the scheduling cell; a cell among the cells that can be scheduled by the MC-DCI; or a cell among the cells actually scheduled by the MC-DCI.

[0042] In conjunction with some embodiments of the second aspect, in some embodiments, the cells that can be scheduled by the MC-DCI are agreed upon by a protocol, or are configured by the network device.

[0043] In combination with some embodiments of the second aspect, in some embodiments, the cells that can be scheduled by the MC-DCI include at least one of the following: a cell with the smallest index among the cells that can be scheduled by the MC-DCI; or a cell with the largest index among the cells that can be scheduled by the MC-DCI.

[0044] In combination with some embodiments of the second aspect, in some embodiments, the cells in the cells actually scheduled by the MC-DCI are agreed upon by a protocol, or are configured by the network device.

[0045] In combination with some embodiments of the second aspect, in some embodiments, the cells in the cells actually scheduled by the MC-DCI include at least one of the following: the cell with the smallest index in the cells actually scheduled by the MC-DCI; or the cell with the largest index in the cells actually scheduled by the MC-DCI.

[0046] In combination with some embodiments of the second aspect, in some embodiments, the MC-DCI includes at least one of the following: a first MC-DCI for scheduling uplink transmission; and a second MC-DCI for scheduling downlink transmission.

[0047] In combination with some embodiments of the second aspect. In some embodiments, counting the number of times the terminal processes the MC-DCI according to the first cell's processing capability of unicast downlink control information includes: determining a first count value for counting the number of times the terminal processes the first MC-DCI; determining a first difference between a first upper limit value of the DCI used for scheduling uplink transmission in the first cell's processing capability of unicast DCI and the first count value;

[0048] The method further includes: determining, based on the first difference, the number of other unicast DCIs for scheduling uplink transmission that the terminal can process in the scheduling cell within the unit time for receiving the first MC-DCI on the first cell.

[0049] In combination with some embodiments of the second aspect. In some embodiments, counting the number of times the terminal processes the MC-DCI according to the first cell's processing capability of unicast downlink control information includes: determining a second count value for counting the number of times the terminal processes the second MC-DCI; determining a second difference between a second upper limit value of the DCI for scheduling downlink transmission in the first cell's processing capability of unicast DCI and the second count value;

[0050] The method further includes: determining, based on the second difference, the number of other unicast DCIs for scheduling downlink transmission that the terminal can process on the first cell in the scheduling cell within the unit time for receiving the second MC-DCI.

[0051] In the third aspect, an embodiment of the present disclosure proposes a capability determination device, which is executed by a terminal, and the device includes: a processing module, configured to process downlink control information MC-DCI for scheduling multiple cells received in a scheduling cell; and count the processing of the MC-DCI according to the first cell's processing capability of unicast downlink control information.

[0052] In the fourth aspect, an embodiment of the present disclosure proposes a capability determination device, which is executed by a network device, and the device includes: a sending module, configured to send downlink control information MC-DCI for scheduling multiple cells to the terminal in the scheduling cell; a processing module, configured to count the MC-DCI processed by the terminal according to the processing capability of the first cell for unicast downlink control information.

[0053] In the fifth aspect, an embodiment of the present disclosure proposes a capability determination method, including: a network device sends downlink control information MC-DCI for scheduling multiple cells to a terminal in a scheduling cell; the terminal processes the MC-DCI; and the terminal counts the processing of the MC-DCI based on the first cell's processing capability of unicast downlink control information.

[0054] In the sixth aspect, an embodiment of the present disclosure proposes a terminal, comprising: one or more processors; a memory coupled to the one or more processors, on which executable instructions are stored, and when the executable instructions are executed by the one or more processors, the terminal executes the capability determination method described in any one of the first aspect and the optional embodiments of the first aspect.

[0055] In the seventh aspect, an embodiment of the present disclosure proposes a network device, comprising: one or more processors; a memory coupled to the one or more processors, wherein the memory stores executable instructions, and when the executable instructions are executed by the one or more processors, the network device executes the capability determination method described in any one of the second aspect and the optional embodiments of the second aspect.

[0056] In the eighth aspect, an embodiment of the present disclosure proposes a communication system, including a terminal and a network device, wherein the terminal is configured to implement the capability determination method described in any one of the first aspect and the optional embodiments of the first aspect, and the network device is configured to implement the capability determination method described in any one of the second aspect and the optional embodiments of the second aspect.

[0057] In the ninth aspect, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the capability determination method described in any one of the first aspect, the optional embodiment of the first aspect, the second aspect, and the optional embodiment of the second aspect.

[0058] In an eighth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes a method as described in any one of the first aspect, the optional embodiment of the first aspect, the second aspect, and the optional embodiment of the second aspect.

[0059] In the ninth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in any one of the first aspect, the optional embodiment of the first aspect, the second aspect, and the optional embodiment of the second aspect.

[0060] It is understandable that the above-mentioned capability determination device, communication device, communication system, storage medium, program product, and computer program are all used to execute the method proposed in the embodiment of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding method and will not be repeated here.

[0061] The present disclosure provides a capability determination method, apparatus, and storage medium. In some embodiments, the terms "capability determination method" and "information processing method" and "communication method" are interchangeable; "capability determination apparatus" and "information processing apparatus" and "communication apparatus" are interchangeable; and "information processing system" and "communication system" are interchangeable.

[0062] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0063] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0064] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0065] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular form, such as "a", "an", "the", "above", "said", "aforementioned", "this", etc., may mean "one and only one", or "one or more", "at least one", etc.

[0066] For example, when using articles such as “a”, “an”, and “the” in English in translation, the noun following the article can be understood as a singular expression or a plural expression.

[0067] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0068] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0069] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0070] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0071] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restrictions on the position, order, priority, quantity or content of the description objects. For the statement of the description objects, please refer to the description in the context of the claims or embodiments, and no unnecessary restrictions should be constituted due to the use of prefixes.

[0072] For example, if the description object is "field," the ordinal number preceding "field" in "first field" and "second field" does not restrict the position or order of the "fields." "First" and "second" do not restrict whether the modified "fields" are in the same message, nor do they restrict the order of the "first field" and "second field." For another example, if the description object is "level," the ordinal number preceding "level" in "first level" and "second level" does not restrict the priority of the "levels." For another example, the number of description objects is not restricted by the ordinal number and can be one or more. For example, in the case of "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the description object is "device," "first device" and "second device" can be the same or different devices, and their types can be the same or different. For another example, if the description object is "information," "first information" and "second information" can be the same or different information, and their content can be the same or different.

[0073] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0074] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0075] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0076] In some embodiments, devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.

[0077] In some embodiments, "network" can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

[0078] In some embodiments, the terms "access network device (AN device)", "radio access network device (RAN device)", "base station (BS)", "radio base station" "fixed station", "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)" and the like may be used interchangeably.

[0079] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc. can be used interchangeably.

[0080] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0081] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

[0082] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0083] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0084] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0085] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0086] As shown in FIG1 , a communication system 100 includes a terminal 101 and a network device 102 , wherein the network device includes at least one of the following: an access network device and a core network device.

[0087] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0088] In some embodiments, the access network device is, for example, a node or device that accesses a terminal to a wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.

[0089] In some embodiments, a core network device may be a device including one or more network elements, or may be multiple devices or device groups, each including all or part of the one or more network elements. The network element may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0090] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0091] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0092] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0093] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or a portion thereof, but are not limited thereto. The entities shown in FIG1 are illustrative only. The communication system may include all or part of the entities shown in FIG1 , or may include other entities outside of FIG1 . The number and form of the entities are arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0094] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0095] FIG2 is an interactive schematic diagram illustrating a capability determination method according to an embodiment of the present disclosure.

[0096] As shown in Figure 2, the capability determination method includes:

[0097] In step S201, the network device sends first information to the terminal.

[0098] In some embodiments, the network device sends the first information to the terminal in the scheduling cell.

[0099] In some embodiments, the terminal receives first information.

[0100] In some embodiments, the first information includes downlink control information (DCI).

[0101] In some embodiments, the downlink control information includes downlink control information (MC-DCI) for scheduling multiple cells.

[0102] In step S202 , the terminal processes MC-DCI.

[0103] In some embodiments, the terminal determines the terminal's processing capability for unicast downlink control information based on a cell granularity.

[0104] In step S203, the terminal counts the number of MC-DCIs processed according to (per) the first cell's processing capability of unicast downlink control information.

[0105] In some embodiments, the first cell includes at least one of the following: a reference cell; the scheduling cell; a cell among the cells that can be scheduled by the MC-DCI; and a cell among the cells actually scheduled by the MC-DCI.

[0106] In some embodiments, the cells that can be scheduled by the MC-DCI are agreed upon by a protocol or configured by a network device.

[0107] In some embodiments, the cells that can be scheduled by the MC-DCI include at least one of the following: a cell with the smallest index among the cells that can be scheduled by the MC-DCI; and a cell with the largest index among the cells that can be scheduled by the MC-DCI.

[0108] In some embodiments, the cells in the cells actually scheduled by the MC-DCI are agreed upon by a protocol or configured by a network device.

[0109] In some embodiments, the cells in the cells actually scheduled by the MC-DCI include at least one of the following: a cell with a smallest index in the cells actually scheduled by the MC-DCI; and a cell with a largest index in the cells actually scheduled by the MC-DCI.

[0110] In some embodiments, the MC-DCI includes at least one of the following: a first MC-DCI for scheduling uplink transmission; and a second MC-DCI for scheduling downlink transmission.

[0111] In some embodiments, the terminal processes the MC-DCI count based on the first cell's processing capability for unicast downlink control information. Specifically, the terminal may first determine a first count value for the first MC-DCI count; and then determine a first difference between a first upper limit value of the DCI used for scheduling uplink transmission in the first cell's processing capability for unicast DCI and the first count value.

[0112] On this basis, in some embodiments, the terminal determines, based on the first difference, the number of other unicast DCIs for scheduling uplink transmission that the terminal can process on the first cell in the scheduling cell within the unit time for receiving the first MC-DCI.

[0113] In some embodiments, the terminal counts the processing of the MC-DCI based on the processing capability of the first cell for unicast downlink control information. Specifically, the terminal may first determine a second count value for the second MC-DCI; then determine a second difference between a second upper limit value of the DCI for scheduling downlink transmission within the processing capability of the first cell for unicast DCI and the second count value.

[0114] On this basis, in some embodiments, the terminal determines, based on the second difference, the number of other unicast DCIs for scheduling downlink transmission that the terminal can process on the first cell in the scheduling cell within the unit time for receiving the second MC-DCI.

[0115] The communication method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S210x. For example, step S2101 can be implemented as an independent embodiment, step 2 can be implemented as an independent embodiment (the step where invention points 1 and 2 are located), steps 1+3 can be implemented as independent embodiments, and steps 1+2+3 can be implemented as independent embodiments (examples of permutations and combinations of important steps involving invention points), but are not limited to these.

[0116] In some embodiments, steps S201 and S202 may be executed in an exchanged order or simultaneously, steps S201 and S203 may be executed in an exchanged order or simultaneously, and steps S202 and S203 may be executed in an exchanged order or simultaneously.

[0117] In some embodiments, step S201 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0118] In some embodiments, step S202 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0119] In some embodiments, step S203 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0120] In some embodiments, steps S201 and S202 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0121] In some embodiments, steps S202 and S203 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0122] In some embodiments, steps S201 and S203 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0123] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2 .

[0124] In some embodiments, when downlink control information (e.g., MC-DCI) is introduced for scheduling multiple cells, the terminal's DCI processing capability also needs to be considered for MC-DCI. The MC-DCI format includes at least one of the following: DCI format 0_3 and DCI format 1_3.

[0125] In some embodiments, a terminal can receive and process unicast DCI, where unicast DCI refers to DCI sent to the terminal by a network device via unicast. Unicast DCI may include legacy DCI, such as DCI used to schedule a single cell, including but not limited to at least one of the following: DCI format 0_0, DCI format 0_1, DCI format 1_0, and DCI format 1_1. For unicast DCI, the terminal's DCI processing capability can be defined at the cell granularity. However, current unicast DCI does not include MC-DCI.

[0126] In some embodiments, when MC-DCI is introduced, for MC-DCI, the terminal's DCI processing capability is defined according to the cell set granularity. For example, the upper limit value of the terminal's DCI processing capability defined for a cell set (e.g., a set of cells that MC-DCI can schedule) is 1. Then, after the terminal processes the MC-DCI, for the cell set, the number of DCIs that the terminal can still process is 1-1=0, that is, the terminal can no longer process the DCI of any cell in the cell set.

[0127] It can be seen that defining the terminal's DCI processing capability with a cell set as the granularity reduces the terminal's DCI processing capability compared to defining it with a cell as the granularity. As mentioned in the previous analysis, defining the terminal's DCI processing capability with a cell set as the granularity will result in the terminal being unable to process the DCI of any cell in the cell set.

[0128] In a first aspect, embodiments of the present disclosure provide a capability determination method. Figure 3 is a schematic flow chart illustrating a capability determination method according to an embodiment of the present disclosure. The capability determination method illustrated in this embodiment can be executed by a terminal.

[0129] As shown in FIG3 , the capability determination method may include the following steps:

[0130] In step S301, downlink control information MC-DCI for scheduling multiple cells received in a scheduling cell is processed;

[0131] In step S302, the number of MC-DCIs processed is counted according to the processing capability of the first cell for unicast downlink control information.

[0132] It should be noted that the embodiment shown in FIG. 3 can be implemented independently or in combination with at least one other embodiment in the present disclosure. The specific selection can be made as needed and the present disclosure does not limit it.

[0133] In some embodiments, the processing capability of the first cell for unicast DCI may also be referred to as the processing capability of the terminal for unicast DCI in the first cell.

[0134] According to an embodiment of the present disclosure, when MC-DCI is introduced, the terminal's processing capability for unicast DCI can be defined at the granularity of a single cell. Thus, after processing MC-DCI received in the scheduling cell, the terminal can count the MC-DCI based on the first cell's processing capability for unicast DCI. Because the first cell is a single cell, not a collection of cells, the terminal performs MC-DCI processing on the first cell, causing the first cell's processing capability for unicast DCI to reach its upper limit. The terminal is simply unable to process DCI for the scheduling first cell, meaning it can no longer process DCI on the first cell. However, this does not affect the terminal's ability to process DCI in other cells, and therefore, the terminal can still process DCI in other cells, thereby effectively improving the terminal's DCI processing capability.

[0135] In some embodiments, the terminal in the embodiments of the present disclosure is a terminal that supports scheduling multiple cells through a single DCI (eg, MC-DCI).

[0136] In some embodiments, the terminal supports N1 cell sets in a physical uplink control channel (PUCCH) group. For example, N1 may be equal to 4 or other values, which is not limited in the present disclosure.

[0137] In some embodiments, the terminal supports scheduling N2 cells in a cell set through a single DCI. For example, N2 may be equal to 4 or other values, which is not limited in the present disclosure.

[0138] In the embodiments of the present disclosure, MC-DCI can be classified as unicast DCI. In addition to MC-DCI, unicast DCI can also include legacy DCI, such as DCI used to schedule a single cell. Therefore, in addition to counting the processing of MC-DCI based on the first cell's processing capability for unicast DCI, the processing of legacy DCI can also be counted.

[0139] For example, for the first cell, the upper limit value of the DCI used for scheduling downlink transmission in the processing capability is 2. The terminal first processes an MC-DCI for scheduling downlink transmission for multiple cells in the first cell. Then it can be determined that the number of unicast DCIs that the terminal can still process in the first cell is 2-1=1. Then the terminal processes a traditional DCI for scheduling downlink transmission. Then it can be determined that the number of unicast DCIs that the terminal can still process in the first cell is 1-1=0, so that the terminal can no longer process DCI for scheduling downlink transmission in the first cell.

[0140] In some embodiments, the terminal's processing capability of unicast DCI in the first cell may include the first cell's processing capability of unicast DCI within a unit time (also referred to as a time window), wherein the time unit includes at least one of the following: frame, subframe, time slot, symbol, and the symbol may be an OFDM (Orthogonal Frequency Division Multiplexing) symbol.

[0141] In some embodiments, the terminal's processing capability for unicast DCI in the first cell may be determined and indicated by the network device, or may be agreed upon by a protocol, or may be autonomously determined by the terminal, or may be indicated by the network device based on the processing capability after the terminal reports its own processing capability. Specifically, when the terminal autonomously determines the terminal's processing capability for unicast DCI in the first cell, the terminal may report the terminal's processing capability for unicast DCI in the first cell to the network device.

[0142] In some embodiments, the first cell's processing capabilities for unicast DCI may be the same or different when corresponding to a time division duplexing (TDD) carrier and when corresponding to a frequency division duplexing (FDD) carrier, and the present disclosure does not limit this.

[0143] The following embodiments mainly take the case where the first cell corresponds to an FDD carrier as an example. For example, in this case, the processing capability of the first cell for unicast DCI includes: the first upper limit value of the processing capability for DCI used to schedule uplink transmission within a unit time is 1, and the first upper limit value of the processing capability for DCI used to schedule downlink transmission within a unit time is 1.

[0144] In some embodiments, the MC-DCI includes at least one of the following:

[0145] A first MC-DCI for scheduling uplink transmission, for example, the uplink transmission includes a PUSCH (Physical Uplink Shared Channel);

[0146] The second MC-DCI is used for scheduling downlink transmission, for example, the downlink transmission includes a PDSCH (Physical Downlink Shared Channel).

[0147] In some embodiments, counting the number of MC-DCIs processed according to the first cell's processing capability of unicast downlink control information includes:

[0148] Determining a first count value for a first MC-DCI count;

[0149] Determine a first difference between a first upper limit value of the DCI for scheduling uplink transmission in the first cell's processing capability of unicast DCI and the first count value;

[0150] The method further includes: determining, based on the first difference, the number of other unicast DCIs for scheduling uplink transmission that the terminal can process in the first cell within the unit time for receiving the first MC-DCI in the scheduling cell.

[0151] For example, each time the terminal processes a first MC-DCI in the first cell, the first count value increases by 1. This description is mainly for the first MC-DCI. In fact, each time the terminal processes a transmission DCI for scheduling uplink transmission in the first cell, the first count value also needs to increase by 1.

[0152] The first cell's processing capability for DCI used for scheduling uplink transmission can be represented by a first upper limit value, for example, 1. Then, the difference between the first upper limit value and the first count value can be calculated, and this difference can represent the number of other unicast DCIs used for scheduling uplink transmission that the terminal can process on the first cell within the unit time used to receive MC-DCI in the scheduling cell. For example, if the difference is 0, then the terminal cannot process any other unicast DCIs used for scheduling uplink transmission on the first cell within the unit time used to receive MC-DCI in the scheduling cell. For example, if the difference is 1, then the terminal can still process one other unicast DCI used for scheduling uplink transmission on the first cell within the unit time used to receive MC-DCI in the scheduling cell.

[0153] In some embodiments, counting the number of MC-DCIs processed according to the first cell's processing capability of unicast downlink control information includes:

[0154] determining a second count value for the second MC-DCI count;

[0155] Determine a second difference between a second upper limit value of the DCI for scheduling downlink transmission in the first cell's processing capability of unicast DCI and the second count value;

[0156] The method further includes:

[0157] The number of other unicast DCIs for scheduling downlink transmission that can be processed by the terminal in the scheduling cell and in the first cell within the unit time for receiving the second MC-DCI is determined according to the second difference.

[0158] For example, each time the terminal processes a second MC-DCI in the first cell, the second count value is increased by 1. The explanation here is mainly for the second MC-DCI. In fact, when the terminal processes a transmission DCI for scheduling downlink transmission in the first cell, the second count value also needs to be increased by 1.

[0159] The first cell's processing capability for DCI used for scheduling uplink transmission can be represented by a second upper limit value, for example, 1. Then, the difference between the second upper limit value and the second count value can be calculated. This difference can represent the number of other unicast DCIs used for scheduling downlink transmission that the terminal processed on the first cell within the unit time used to receive MC-DCI in the scheduling cell. For example, if the difference is 0, then the terminal cannot process any other unicast DCIs used for scheduling downlink transmission on the first cell within the unit time used to receive MC-DCI in the scheduling cell. For example, if the difference is 1, then the terminal can still process one other unicast DCI used for scheduling downlink transmission on the first cell within the unit time used to receive MC-DCI in the scheduling cell.

[0160] In some embodiments, the first cell includes at least one of the following:

[0161] Reference cell;

[0162] Scheduling cell, wherein when the first cell includes the scheduling cell, the scheduling cell may also be included in the scheduled cell, that is, the cell actually scheduled by MC-DCI;

[0163] Cells among the cells that can be scheduled by MC-DCI;

[0164] The cell among the cells actually scheduled by MC-DCI.

[0165] In some embodiments, the reference cell may be determined based on a protocol agreement or indicated by a base station, and may be a cell in the cell set or a cell outside the cell set, which is not limited in the present disclosure.

[0166] For example, in some embodiments, the reference cell may be the cell with the smallest or largest identifier in the cell set; for example, in some embodiments, the reference cell may be a cell used to count the DCI size budget; for example, in some embodiments, the reference cell may be a cell used to count the blind detection parameters of MC-DCI, wherein the blind detection parameters include at least one of the following: BD (Blind Decoding), CCE (Control Channel Elements).

[0167] In some embodiments, the cells that can be scheduled by MC-DCI are agreed upon by a protocol or configured by a network device.

[0168] In some embodiments, the cells that can be scheduled by MC-DCI include at least one of the following:

[0169] The cell with the smallest index among the cells that can be scheduled by MC-DCI;

[0170] The cell with the largest index among the cells that can be scheduled by MC-DCI.

[0171] In some embodiments, the cells in the cells actually scheduled by MC-DCI are agreed upon by a protocol or configured by a network device.

[0172] In some embodiments, the cells actually scheduled by the MC-DCI include at least one of the following:

[0173] The cell with the smallest index among the cells actually scheduled by MC-DCI;

[0174] The cell with the largest index among the cells actually scheduled by MC-DCI.

[0175] In some embodiments, the cells actually scheduled by MC-DCI may be represented in the form of a cell combination.

[0176] Taking the first cell including the reference cell as an example, for example, MC-DCI can schedule 4 cells, namely cell#2, cell#3, cell#4, and cell#5, then the cell set can be {cell#2, cell#3, cell#4, cell#5}.

[0177] For example, a terminal receives MC-DCI on scheduling cell #1 (a cell outside the cell set). For example, the cells actually scheduled by the MC-DCI are cell #2, cell #3, cell #4, and cell #5, specifically, the PDSCH. If cell #2 is the reference cell, since the first upper limit of cell #2's processing capability for DCI used to schedule downlink transmissions per unit time is 1, after the terminal processes MC-DCI used to schedule PDSCHs of multiple cells on cell #2, the terminal can no longer process unicast DCI used to schedule downlink transmissions on cell #2 within the time domain unit in which it receives MC-DCI. However, since the first upper limit of the processing capability for DCI used to schedule uplink transmissions per unit time is 1, the terminal can still process one more unicast DCI used to schedule uplink transmissions on cell #2 within the time domain unit in which it receives MC-DCI.

[0178] Since cell#3, cell#4, and cell#5 are not reference cells, the DCI processing capabilities of these three cells are not affected. For example, in the above time-domain unit, the terminal can still process one unicast DCI for downlink scheduling and one unicast DCI for uplink scheduling in cell#3; in the above time-domain unit, the terminal can still process one unicast DCI for downlink scheduling and one unicast DCI for uplink scheduling in cell#4; and in the above time-domain unit, the terminal can still process one unicast DCI for downlink scheduling and one unicast DCI for uplink scheduling in cell#5.

[0179] For example, a terminal receives MC-DCI on scheduling cell #2 (a cell within a cell set). For example, the cells actually scheduled by MC-DCI are cell #2, cell #3, cell #4, and cell #5, specifically scheduling PDSCH. When cell #2 is the reference cell, since the first upper limit of cell #2's processing capability for DCI used for scheduling downlink transmissions per unit time is 1, after the terminal processes MC-DCI for scheduling PDSCHs of multiple cells on cell #2, the terminal can no longer process unicast DCI used for scheduling downlink transmissions on cell #2 within the time domain unit in which it receives MC-DCI. However, since the first upper limit of the processing capability for DCI used for scheduling uplink transmissions per unit time is 1, the terminal can still process one more unicast DCI used for scheduling uplink transmissions on cell #2 within the time domain unit in which it receives MC-DCI.

[0180] Since cell#3, cell#4, and cell#5 are not reference cells, the DCI processing capabilities of these three cells are not affected. For example, in the above time-domain unit, the terminal can still process one unicast DCI for downlink scheduling and one unicast DCI for uplink scheduling in cell#3; in the above time-domain unit, the terminal can still process one unicast DCI for downlink scheduling and one unicast DCI for uplink scheduling in cell#4; and in the above time-domain unit, the terminal can still process one unicast DCI for downlink scheduling and one unicast DCI for uplink scheduling in cell#5.

[0181] For example, a terminal receives MC-DCI on scheduling cell #2. For example, the cells actually scheduled by the MC-DCI are cell #2, cell #3, cell #4, and cell #5, specifically, the PDSCH. If cell #3 is the reference cell, and since the first upper limit of cell #3's processing capability for DCI used to schedule downlink transmissions per unit time is 1, after the terminal processes MC-DCI used to schedule PDSCHs of multiple cells on cell #3, the terminal can no longer process unicast DCI used to schedule downlink transmissions on cell #3 within the time domain unit in which it receives MC-DCI. However, since the first upper limit of the processing capability for DCI used to schedule uplink transmissions per unit time is 1, the terminal can still process one more unicast DCI used to schedule uplink transmissions on cell #3 within the time domain unit in which it receives MC-DCI.

[0182] Since cell#2, cell#4, and cell#5 are not reference cells, the DCI processing capabilities of these three cells are not affected. For example, in the aforementioned time-domain unit, a terminal in cell#2 can still process one unicast DCI for downlink scheduling and one unicast DCI for uplink scheduling; in cell#4, a terminal in the aforementioned time-domain unit can still process one unicast DCI for downlink scheduling and one unicast DCI for uplink scheduling; and in cell#5, a terminal in the aforementioned time-domain unit can still process one unicast DCI for downlink scheduling and one unicast DCI for uplink scheduling.

[0183] Taking the first cell including the scheduling cell as an example, for example, MC-DCI can schedule 4 cells, namely cell#2, cell#3, cell#4, and cell#5, then the cell set can be {cell#2, cell#3, cell#4, cell#5}.

[0184] For example, a terminal receives MC-DCI on scheduling cell #1. For example, the cells actually scheduled by the MC-DCI are cell #2, cell #3, cell #4, and cell #5, specifically, the PDSCH. Since the first upper limit of cell #1's processing capability for DCI used to schedule downlink transmissions per unit time is 1, after the terminal processes the MC-DCI used to schedule PDSCHs of multiple cells on cell #1, it can no longer process unicast DCI used to schedule downlink transmissions on cell #1 within the time domain unit in which it receives the MC-DCI. However, the first upper limit of the processing capability for DCI used to schedule uplink transmissions per unit time is 1, so the terminal can still process one more unicast DCI used to schedule uplink transmissions on cell #1 within the time domain unit in which it receives the MC-DCI.

[0185] Since cell#2, cell#3, cell#4, and cell#5 are not scheduling cells, the DCI processing capabilities of these three cells are not affected. For example, in the above time-domain unit, the terminal can still process one unicast DCI for downlink scheduling and one unicast DCI for uplink scheduling in cell#3; in the above time-domain unit, the terminal can still process one unicast DCI for downlink scheduling and one unicast DCI for uplink scheduling in cell#4; and in the above time-domain unit, the terminal can still process one unicast DCI for downlink scheduling and one unicast DCI for uplink scheduling in cell#5.

[0186] For example, a terminal receives MC-DCI on scheduling cell #2. For example, the cells actually scheduled by the MC-DCI are cell #2, cell #3, cell #4, and cell #5, specifically, the PDSCH. Since the first upper limit of cell #2's processing capability for DCI used to schedule downlink transmissions per unit time is 1, after the terminal processes the MC-DCI used to schedule PDSCHs of multiple cells on cell #2, the terminal can no longer process unicast DCI used to schedule downlink transmissions on cell #2 within the time domain unit in which it receives the MC-DCI. However, the first upper limit of the processing capability for DCI used to schedule uplink transmissions per unit time is 1, so the terminal can still process one more unicast DCI used to schedule uplink transmissions on cell #2 within the time domain unit in which it receives the MC-DCI.

[0187] Since cell#3, cell#4, and cell#5 are not scheduling cells, the DCI processing capabilities of these three cells are not affected. For example, in the above time-domain unit, the terminal can still process one unicast DCI for downlink scheduling and one unicast DCI for uplink scheduling in cell#3; in the above time-domain unit, the terminal can still process one unicast DCI for downlink scheduling and one unicast DCI for uplink scheduling in cell#4; and in the above time-domain unit, the terminal can still process one unicast DCI for downlink scheduling and one unicast DCI for uplink scheduling in cell#5.

[0188] For example, a terminal receives MC-DCI on scheduling cell #2. For example, the cells actually scheduled by the MC-DCI are cell #3, cell #4, and cell #5, specifically, the PDSCH. If cell #3 is the reference cell, and since the first upper limit of cell #3's processing capability for DCI used to schedule downlink transmissions per unit time is 1, after the terminal processes the MC-DCI used to schedule PDSCHs of multiple cells on cell #3, it can no longer process unicast DCI used to schedule downlink transmissions on cell #3 within the time domain unit in which it receives the MC-DCI. However, since the first upper limit of the processing capability for DCI used to schedule uplink transmissions per unit time is 1, the terminal can still process one more unicast DCI used to schedule uplink transmissions on cell #3 within the time domain unit in which it receives the MC-DCI.

[0189] Since cell#3, cell#4, and cell#5 are not scheduling cells, the DCI processing capabilities of these three cells are not affected. For example, in the above time-domain unit, the terminal can still process one unicast DCI for downlink scheduling and one unicast DCI for uplink scheduling in cell#2; in the above time-domain unit, the terminal can still process one unicast DCI for downlink scheduling and one unicast DCI for uplink scheduling in cell#4; and in the above time-domain unit, the terminal can still process one unicast DCI for downlink scheduling and one unicast DCI for uplink scheduling in cell#5.

[0190] Taking the example of a first cell including cells that can be scheduled by MC-DCI, for example, it can be the cell with the smallest index or the largest index among the cells that can be scheduled by MC-DCI. For example, if MC-DCI can schedule four cells, namely cell#2, cell#3, cell#4, and cell#5, then the cell set can be {cell#2, cell#3, cell#4, cell#5}. Taking the example of a first cell including the cell with the smallest index among the cells that can be scheduled by MC-DCI, that is, cell#2, as an example.

[0191] For example, a terminal receives MC-DCI on scheduling cell #1. For example, the cells actually scheduled by the MC-DCI are cell #2, cell #3, cell #4, and cell #5, specifically, the PDSCH. If the first cell is cell #2, since the first upper limit of cell #2's processing capability for DCI used for scheduling downlink transmissions per unit time is 1, after the terminal processes the MC-DCI used for scheduling PDSCHs of multiple cells on cell #2, the terminal can no longer process unicast DCI used for scheduling downlink transmissions on cell #2 within the time domain unit in which the MC-DCI is received. However, since the first upper limit of the processing capability for DCI used for scheduling uplink transmissions per unit time is 1, the terminal can still process one more unicast DCI used for scheduling uplink transmissions on cell #2 within the time domain unit in which the MC-DCI is received.

[0192] Since cell#3, cell#4, and cell#5 are not the primary cell, their DCI processing capabilities are not affected. For example, in the aforementioned time-domain unit, a terminal in cell#3 can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission. In the aforementioned time-domain unit, a terminal in cell#4 can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission. In the aforementioned time-domain unit, a terminal in cell#5 can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission.

[0193] For example, a terminal receives MC-DCI on scheduling cell #2. For example, the cells actually scheduled by the MC-DCI are cell #2, cell #3, cell #4, and cell #5, specifically, the PDSCH. When the first cell is cell #2, since the first upper limit of cell #2's processing capability for DCI used for scheduling downlink transmissions per unit time is 1, after the terminal processes the MC-DCI used for scheduling PDSCHs of multiple cells on cell #2, the terminal can no longer process unicast DCI used for scheduling downlink transmissions on cell #2 within the time domain unit in which the MC-DCI is received. However, since the first upper limit of the processing capability for DCI used for scheduling uplink transmissions per unit time is 1, the terminal can still process one more unicast DCI used for scheduling uplink transmissions on cell #2 within the time domain unit in which the MC-DCI is received.

[0194] Since cell#3, cell#4, and cell#5 are not the primary cell, their DCI processing capabilities are not affected. For example, in the aforementioned time-domain unit, a terminal in cell#3 can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission. In the aforementioned time-domain unit, a terminal in cell#4 can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission. In the aforementioned time-domain unit, a terminal in cell#5 can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission.

[0195] For example, a terminal receives MC-DCI on scheduling cell #2. For example, the cells actually scheduled by the MC-DCI are cell #3, cell #4, and cell #5, specifically, the PDSCH. When the first cell is cell #2, since the first upper limit of cell #2's processing capability for DCI used for scheduling downlink transmissions per unit time is 1, after the terminal processes the MC-DCI used for scheduling PDSCHs of multiple cells on cell #2, the terminal can no longer process unicast DCI used for scheduling downlink transmissions on cell #2 within the time domain unit in which it receives the MC-DCI. However, since the first upper limit of the processing capability for DCI used for scheduling uplink transmissions per unit time is 1, the terminal can still process one more unicast DCI used for scheduling uplink transmissions on cell #2 within the time domain unit in which it receives the MC-DCI.

[0196] Since cell#3, cell#4, and cell#5 are not the primary cell, their DCI processing capabilities are not affected. For example, in the aforementioned time-domain unit, a terminal in cell#3 can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission. In the aforementioned time-domain unit, a terminal in cell#4 can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission. In the aforementioned time-domain unit, a terminal in cell#5 can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission.

[0197] Taking the example of a cell that includes a cell among the cells actually scheduled by MC-DCI as the first cell, for example, it can be the cell with the smallest index or the largest index among the cells actually scheduled by MC-DCI. For example, if MC-DCI can schedule four cells, namely cell#2, cell#3, cell#4, and cell#5, then the cell set can be {cell#2, cell#3, cell#4, cell#5}, and the actually scheduled cells can be one or more cells in the cell set. Taking the example of a cell that includes the cell with the smallest index among the cells actually scheduled by MC-DCI as the first cell.

[0198] For example, a terminal receives MC-DCI on scheduling cell #1 (a cell outside the cell set). For example, the cells actually scheduled by the MC-DCI are cell #2, cell #3, cell #4, and cell #5, specifically scheduling the PDSCH. Cell #2 has the smallest index, so cell #2 is selected as the first cell. Since the first upper limit of cell #2's processing capability for DCI used to schedule downlink transmissions per unit time is 1, after the terminal processes MC-DCI for scheduling PDSCHs of multiple cells on cell #2, it can no longer process unicast DCI used to schedule downlink transmissions on cell #2 within the time domain unit in which it receives MC-DCI. However, since the first upper limit of the processing capability for DCI used to schedule uplink transmissions per unit time is 1, the terminal can still process one more unicast DCI used to schedule uplink transmissions on cell #2 within the time domain unit in which it receives MC-DCI.

[0199] Since cell#3, cell#4, and cell#5 are not the primary cell, their DCI processing capabilities are not affected. For example, in the aforementioned time-domain unit, a terminal in cell#3 can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission. In the aforementioned time-domain unit, a terminal in cell#4 can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission. In the aforementioned time-domain unit, a terminal in cell#5 can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission.

[0200] For example, a terminal receives MC-DCI on scheduling cell #2 (a cell within a cell set). For example, the cells actually scheduled by the MC-DCI are cell #3, cell #4, and cell #5, specifically scheduling the PDSCH. Cell #3 has the smallest index, so cell #3 is selected as the first cell. Since the first upper limit of cell #3's processing capability for DCI used to schedule downlink transmissions per unit time is 1, after the terminal processes MC-DCI used to schedule PDSCHs of multiple cells on cell #3, it can no longer process unicast DCI used to schedule downlink transmissions on cell #3 within the time domain unit in which it receives MC-DCI. However, since the first upper limit of the processing capability for DCI used to schedule uplink transmissions per unit time is 1, the terminal can still process one more unicast DCI used to schedule uplink transmissions on cell #3 within the time domain unit in which it receives MC-DCI.

[0201] Since cell#2, cell#4, and cell#5 are not the primary cell, the DCI processing capabilities of these three cells are not affected. For example, in the aforementioned time-domain unit, the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#2; in the aforementioned time-domain unit, the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#4; and in the aforementioned time-domain unit, the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#5.

[0202] For example, a terminal receives MC-DCI on scheduling cell #2. For example, the MC-DCI actually schedules cells #4 and #5, specifically PDSCHs. Cell #4 has the smallest index, so cell #4 is selected as the first cell. Since the first upper limit of cell #4's processing capacity for DCI used to schedule downlink transmissions per unit time is 1, after the terminal processes MC-DCI used to schedule PDSCHs of multiple cells on cell #4, it can no longer process unicast DCI used to schedule downlink transmissions on cell #4 within the time domain unit in which it receives MC-DCI. However, since the first upper limit of the processing capacity for DCI used to schedule uplink transmissions per unit time is 1, the terminal can still process one more unicast DCI used to schedule uplink transmissions on cell #4 within the time domain unit in which it receives MC-DCI.

[0203] Since cell#2, cell#3, and cell#5 are not reference cells, the DCI processing capabilities of these three cells are not affected. For example, in the aforementioned time-domain unit, a terminal in cell#2 can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission; in the aforementioned time-domain unit, a terminal in cell#3 can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission; and in the aforementioned time-domain unit, a terminal in cell#5 can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission.

[0204] In a second aspect, embodiments of the present disclosure provide a capability determination method. Figure 4 is a schematic flow chart illustrating a capability determination method according to an embodiment of the present disclosure. The capability determination method illustrated in this embodiment can be executed by a network device.

[0205] As shown in FIG4 , the capability determination method may include the following steps:

[0206] In step S401, downlink control information MC-DCI for scheduling multiple cells is sent to the terminal in the scheduling cell;

[0207] In step S402, the number of times the terminal processes MC-DCI is counted according to the first cell's processing capability of unicast downlink control information.

[0208] According to an embodiment of the present disclosure, when MC-DCI is introduced, the terminal's processing capability for unicast DCI can be defined at the granularity of a single cell, so that after the network device sends MC-DCI to the terminal in the scheduling cell, the terminal can process the MC-DCI, and the network device can count the MC-DCI based on the first cell's processing capability for unicast DCI. Since the first cell is a single cell, not a collection of cells, even if the network device determines that the terminal performs an operation to process MC-DCI in the first cell, causing the first cell's processing capability for unicast DCI to reach the upper limit, it only determines that the terminal can no longer process the DCI of the scheduled first cell, that is, the terminal can no longer process DCI in the first cell, but it does not affect the terminal's ability to process DCI in other cells. Therefore, it can still be determined that the terminal can process DCI in other cells, thereby effectively improving the terminal's processing capability for DCI.

[0209] On this basis, in some embodiments, the network device can configure the terminal as needed, and the terminal's processing capability of unicast DCI in the first cell and other cells can be considered during the configuration process to avoid configuring the terminal beyond its processing capability of unicast DCI in the first cell and other cells.

[0210] In some embodiments, the terminal supports N1 cell sets in a physical uplink control channel (PUCCH) group. For example, N1 may be equal to 4 or other values, which is not limited in the present disclosure.

[0211] In some embodiments, the terminal supports scheduling N2 cells in a cell set through a single DCI. For example, N2 may be equal to 4 or other values, which is not limited in the present disclosure.

[0212] In the embodiments of the present disclosure, MC-DCI can be classified as unicast DCI. In addition to MC-DCI, unicast DCI can also include legacy DCI, such as DCI used to schedule a single cell. Therefore, in addition to counting the processing of MC-DCI based on the first cell's processing capability for unicast DCI, the processing of legacy DCI can also be counted.

[0213] For example, for the first cell, the upper limit of the DCI used for scheduling downlink transmission in the processing capability is 2. The terminal first processes an MC-DCI for scheduling downlink transmission for multiple cells in the first cell. Then it can be determined that the number of unicast DCIs that the terminal can still process in the first cell is 2-1=1. Then the terminal processes a traditional DCI for scheduling downlink transmission. Then it can be determined that the number of unicast DCIs that the terminal can still process in the first cell is 1-1=0, so that the terminal can no longer process DCI for scheduling downlink transmission in the first cell.

[0214] In some embodiments, the terminal's processing capability of unicast DCI in the first cell may include the first cell's processing capability of unicast DCI within a unit time (also referred to as a time window), wherein the time unit includes at least one of the following: frame, subframe, time slot, symbol, and the symbol may be an OFDM symbol.

[0215] In some embodiments, the terminal's processing capability for unicast DCI in the first cell may be determined and indicated by the network device, or may be agreed upon by a protocol, or may be autonomously determined by the terminal, or may be indicated by the network device based on the processing capability after the terminal reports its own processing capability. Specifically, when the terminal autonomously determines the terminal's processing capability for unicast DCI in the first cell, the terminal may report the terminal's processing capability for unicast DCI in the first cell to the network device.

[0216] In some embodiments, the first cell's processing capabilities for unicast DCI when corresponding to a time division duplex (TDD) carrier and when corresponding to a frequency division duplex (FDD) carrier may be the same or different, and the present disclosure is not limited in this regard.

[0217] The following embodiments mainly take the case where the first cell corresponds to an FDD carrier as an example. For example, in this case, the processing capability of the first cell for unicast DCI includes: the first upper limit value of the processing capability for DCI used to schedule uplink transmission within a unit time is 1, and the first upper limit value of the processing capability for DCI used to schedule downlink transmission within a unit time is 1.

[0218] In some embodiments, the MC-DCI includes at least one of the following:

[0219] A first MC-DCI for scheduling uplink transmission, for example, the uplink transmission includes a PUSCH;

[0220] The second MC-DCI is used for scheduling downlink transmission, for example, the downlink transmission includes PDSCH.

[0221] In some embodiments, counting the number of times a terminal processes MC-DCI according to the first cell's processing capability of unicast downlink control information includes:

[0222] Determine a first count value for counting a first MC-DCI processed by the terminal;

[0223] Determine a first difference between a first upper limit value of the DCI for scheduling uplink transmission in the first cell's processing capability of unicast DCI and the first count value;

[0224] The method further includes: determining, based on the first difference, the number of other unicast DCIs for scheduling uplink transmission that the terminal can process in the first cell within the unit time for receiving the first MC-DCI in the scheduling cell.

[0225] For example, each time the terminal processes a first MC-DCI in the first cell, the first count value increases by 1. This description is mainly for the first MC-DCI. In fact, each time the terminal processes a transmission DCI for scheduling uplink transmission in the first cell, the first count value also needs to increase by 1.

[0226] The processing capability of the first cell for the DCI for scheduling uplink transmission can be represented by a first upper limit value, for example, 1. Then, the difference between the first upper limit value and the first count value can be calculated, and the difference can represent the number of other unicast DCIs for scheduling uplink transmission that the terminal processes on the first cell within the unit time for receiving MC-DCI in the scheduling cell. For example, if the difference is 0, the network device can determine that within the unit time for receiving MC-DCI in the scheduling cell, the terminal can no longer process other unicast DCIs for scheduling uplink transmission in the first cell; for example, if the difference is 1, the network device can determine that within the unit time for receiving MC-DCI in the scheduling cell, the terminal can still process one other unicast DCI for scheduling uplink transmission in the first cell.

[0227] In some embodiments, counting the number of times a terminal processes MC-DCI according to the first cell's processing capability of unicast downlink control information includes:

[0228] Determine a second count value for counting a second MC-DCI processed by the terminal;

[0229] Determine a second difference between a second upper limit value of the DCI for scheduling downlink transmission in the first cell's processing capability of unicast DCI and the second count value;

[0230] The method further includes: determining, based on the second difference, the number of other unicast DCIs for scheduling downlink transmission that the terminal can process in the scheduling cell within the unit time for receiving the second MC-DCI on the first cell.

[0231] For example, each time the terminal processes a second MC-DCI in the first cell, the second count value is increased by 1. The explanation here is mainly for the second MC-DCI. In fact, when the terminal processes a transmission DCI for scheduling downlink transmission in the first cell, the second count value also needs to be increased by 1.

[0232] The first cell's processing capability for DCI for scheduling uplink transmission can be represented by a second upper limit value, for example, 1. Then, the difference between the second upper limit value and the second count value can be calculated, and the difference can represent the number of other unicast DCIs for scheduling downlink transmission that the terminal processes on the first cell within the unit time for receiving MC-DCI in the scheduling cell. For example, if the difference is 0, the network device can determine that within the unit time for receiving MC-DCI in the scheduling cell, the terminal can no longer process other unicast DCIs for scheduling downlink transmission in the first cell; for example, if the difference is 1, the network device can determine that within the unit time for receiving MC-DCI in the scheduling cell, the terminal can still process one other unicast DCI for scheduling downlink transmission in the first cell.

[0233] In some embodiments, the first cell includes at least one of the following:

[0234] Reference cell;

[0235] Scheduling cell, wherein when the first cell includes the scheduling cell, the scheduling cell may also be included in the scheduled cell, that is, the cell actually scheduled by MC-DCI;

[0236] Cells among the cells that can be scheduled by MC-DCI;

[0237] The cell among the cells actually scheduled by MC-DCI.

[0238] In some embodiments, the reference cell may be determined based on a protocol agreement or indicated by a base station, and may be a cell in the cell set or a cell outside the cell set, which is not limited in the present disclosure.

[0239] For example, in some embodiments, the reference cell may be the cell with the smallest or largest identifier in the cell set; for example, in some embodiments, the reference cell may be a cell used to count the DCI size budget; for example, in some embodiments, the reference cell may be a cell used to count the blind detection parameters of MC-DCI, wherein the blind detection parameters include at least one of the following: BD, CCE.

[0240] In some embodiments, the cells that can be scheduled by MC-DCI are agreed upon by a protocol or configured by a network device.

[0241] In some embodiments, the cells that can be scheduled by MC-DCI include at least one of the following:

[0242] The cell with the smallest index among the cells that can be scheduled by MC-DCI;

[0243] The cell with the largest index among the cells that can be scheduled by MC-DCI.

[0244] In some embodiments, the cells in the cells actually scheduled by MC-DCI are agreed upon by a protocol or configured by a network device.

[0245] In some embodiments, the cells actually scheduled by the MC-DCI include at least one of the following:

[0246] The cell with the smallest index among the cells actually scheduled by MC-DCI;

[0247] The cell with the largest index among the cells actually scheduled by MC-DCI.

[0248] In some embodiments, the cells actually scheduled by MC-DCI may be represented in the form of a cell combination.

[0249] Taking the first cell including the reference cell as an example, for example, MC-DCI can schedule four cells, namely cell#2, cell#3, cell#4, and cell#5, then the cell set may be {cell#2, cell#3, cell#4, cell#5}.

[0250] For example, a network device sends MC-DCI to a terminal on scheduling cell #1. For example, the cells actually scheduled by the MC-DCI are cell #2, cell #3, cell #4, and cell #5, specifically scheduling the PDSCH. In the case where cell #2 is the reference cell, since the first upper limit of cell #2's processing capability for DCI used to schedule downlink transmissions per unit time is 1, the network device determines that after the terminal processes the MC-DCI used to schedule the PDSCHs of multiple cells on cell #2, it can no longer process unicast DCI used to schedule downlink transmissions on cell #2 in the time domain unit in which it receives the MC-DCI. However, since the first upper limit of the processing capability for DCI used to schedule uplink transmissions per unit time is 1, the network device can determine that the terminal can also process one more unicast DCI used to schedule uplink transmissions on cell #2 in the time domain unit in which it receives the MC-DCI.

[0251] Since cell#3, cell#4, and cell#5 are not reference cells, the DCI processing capabilities of these three cells are not affected. For example, the network device can determine that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#3 within the aforementioned time domain unit; that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#4 within the aforementioned time domain unit; and that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#5 within the aforementioned time domain unit.

[0252] For example, a network device sends MC-DCI to a terminal on scheduling cell cell#2. For example, the cells actually scheduled by MC-DCI are cell#2, cell#3, cell#4, and cell#5, specifically scheduling PDSCH. When cell#2 is the reference cell, since the first upper limit of cell#2's processing capability for DCI used for scheduling downlink transmissions per unit time is 1, the network device determines that after the terminal processes MC-DCI used for scheduling PDSCHs of multiple cells on cell#2, it can no longer process unicast DCI used for scheduling downlink transmissions on cell#2 in the time domain unit in which it receives MC-DCI. However, since the first upper limit of the processing capability for DCI used for scheduling uplink transmissions per unit time is 1, the network device can determine that the terminal can also process one more unicast DCI used for scheduling uplink transmissions on cell#2 in the time domain unit in which it receives MC-DCI.

[0253] Since cell#3, cell#4, and cell#5 are not reference cells, the DCI processing capabilities of these three cells are not affected. For example, the network device can determine that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#3 within the aforementioned time domain unit; that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#4 within the aforementioned time domain unit; and that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#5 within the aforementioned time domain unit.

[0254] For example, a network device sends MC-DCI to a terminal on scheduling cell #2. For example, the cells actually scheduled by the MC-DCI are cell #2, cell #3, cell #4, and cell #5, specifically scheduling the PDSCH. When cell #3 is the reference cell, since the first upper limit of cell #3's processing capability for DCI used to schedule downlink transmissions per unit time is 1, the network device determines that after the terminal processes the MC-DCI used to schedule the PDSCHs of multiple cells on cell #3, it can no longer process unicast DCI used to schedule downlink transmissions on cell #3 in the time domain unit in which it receives the MC-DCI. However, since the first upper limit of the processing capability for DCI used to schedule uplink transmissions per unit time is 1, the network device can determine that the terminal can also process one more unicast DCI used to schedule uplink transmissions on cell #3 in the time domain unit in which it receives the MC-DCI.

[0255] Since cell#2, cell#4, and cell#5 are not reference cells, the DCI processing capabilities of these three cells are not affected. For example, the network device can determine that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#2 within the above time domain unit; that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#4 within the above time domain unit; and that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#5 within the above time domain unit.

[0256] Taking the first cell including the scheduling cell as an example, for example, MC-DCI can schedule 4 cells, namely cell#2, cell#3, cell#4, and cell#5, then the cell set can be {cell#2, cell#3, cell#4, cell#5}.

[0257] For example, the network device sends MC-DCI to the terminal on the scheduling cell cell#1. For example, the cells actually scheduled by MC-DCI are cell#2, cell#3, cell#4, and cell#5, specifically scheduling PDSCH. Since the first upper limit of cell#1's processing capability for DCI used to schedule downlink transmission within a unit time is 1, the network device determines that after the terminal processes MC-DCI used to schedule PDSCH of multiple cells on cell#1, it can no longer process unicast DCI used to schedule downlink transmission on cell#1 in the time domain unit in which it receives MC-DCI. However, the first upper limit of the processing capability for DCI used to schedule uplink transmission within a unit time is 1, so the network device can determine that the terminal can also process one more unicast DCI used to schedule uplink transmission on cell#1 in the time domain unit in which it receives MC-DCI.

[0258] Since cell#2, cell#3, cell#4, and cell#5 are not scheduling cells, the DCI processing capabilities of these three cells are not affected. For example, the network device can determine that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#3 within the above time domain unit; that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#4 within the above time domain unit; and that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#5 within the above time domain unit.

[0259] For example, the network device sends MC-DCI to the terminal on the scheduling cell cell#2. For example, the cells actually scheduled by MC-DCI are cell#2, cell#3, cell#4, and cell#5, specifically scheduling PDSCH. Since the first upper limit of cell#2's processing capability for DCI used to schedule downlink transmission within a unit time is 1, the network device determines that after the terminal processes MC-DCI used to schedule PDSCH of multiple cells on cell#2, it can no longer process unicast DCI used to schedule downlink transmission on cell#2 in the time domain unit in which it receives MC-DCI. However, the first upper limit of the processing capability for DCI used to schedule uplink transmission within a unit time is 1, so the network device can determine that the terminal can also process one more unicast DCI used to schedule uplink transmission on cell#2 in the time domain unit in which it receives MC-DCI.

[0260] Since cell#3, cell#4, and cell#5 are not scheduling cells, the DCI processing capabilities of these three cells are not affected. For example, the network device can determine that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#3 within the above time domain unit; that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#4 within the above time domain unit; and that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#5 within the above time domain unit.

[0261] For example, a network device sends MC-DCI to a terminal on scheduling cell #2. For example, the cells actually scheduled by the MC-DCI are cell #3, cell #4, and cell #5, specifically scheduling the PDSCH. In the case where cell #3 is the reference cell, since the first upper limit of cell #3's processing capability for DCI used to schedule downlink transmissions per unit time is 1, the network device determines that after the terminal processes the MC-DCI used to schedule the PDSCHs of multiple cells on cell #3, it can no longer process unicast DCI used to schedule downlink transmissions on cell #3 in the time domain unit in which it receives the MC-DCI. However, since the first upper limit of the processing capability for DCI used to schedule uplink transmissions per unit time is 1, the network device can determine that the terminal can also process one more unicast DCI used to schedule uplink transmissions on cell #3 in the time domain unit in which it receives the MC-DCI.

[0262] Since cell#3, cell#4, and cell#5 are not scheduling cells, the DCI processing capabilities of these three cells are not affected. For example, the network device can determine that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#2 within the above time domain unit; that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#4 within the above time domain unit; and that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#5 within the above time domain unit.

[0263] Taking the example of a first cell including cells that can be scheduled by MC-DCI, for example, it can be the cell with the smallest index or the largest index among the cells that can be scheduled by MC-DCI. For example, if MC-DCI can schedule four cells, namely cell#2, cell#3, cell#4, and cell#5, then the cell set can be {cell#2, cell#3, cell#4, cell#5}. Taking the example of a first cell including the cell with the smallest index among the cells that can be scheduled by MC-DCI, that is, cell#2, as an example.

[0264] For example, a network device sends MC-DCI to a terminal on scheduling cell #1. For example, the cells actually scheduled by the MC-DCI are cell #2, cell #3, cell #4, and cell #5, specifically scheduling the PDSCH. When the first cell is cell #2, since the first upper limit of cell #2's processing capability for DCI used for scheduling downlink transmissions per unit time is 1, the network device determines that after the terminal processes the MC-DCI used for scheduling PDSCHs of multiple cells on cell #2, it can no longer process unicast DCI used for scheduling downlink transmissions on cell #2 in the time domain unit in which it receives the MC-DCI. However, since the first upper limit of the processing capability for DCI used for scheduling uplink transmissions per unit time is 1, the network device can determine that the terminal can also process one more unicast DCI used for scheduling uplink transmissions on cell #2 in the time domain unit in which it receives the MC-DCI.

[0265] Since cell#3, cell#4, and cell#5 are not the primary cell, the DCI processing capabilities of these three cells are not affected. For example, the network device can determine that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#3 within the aforementioned time domain unit; that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#4 within the aforementioned time domain unit; and that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#5 within the aforementioned time domain unit.

[0266] For example, a network device sends MC-DCI to a terminal on scheduling cell #2. For example, the cells actually scheduled by MC-DCI are cell #2, cell #3, cell #4, and cell #5, specifically scheduling PDSCH. When the first cell is cell #2, since the first upper limit of cell #2's processing capability for DCI used for scheduling downlink transmissions per unit time is 1, the network device determines that after the terminal processes MC-DCI for scheduling PDSCHs of multiple cells on cell #2, the terminal can no longer process unicast DCI used for scheduling downlink transmissions on cell #2 within the time domain unit in which it receives MC-DCI. However, since the first upper limit of the processing capability for DCI used for scheduling uplink transmissions per unit time is 1, the network device can determine that the terminal can process one more unicast DCI used for scheduling uplink transmissions on cell #2 within the time domain unit in which it receives MC-DCI.

[0267] Since cell#3, cell#4, and cell#5 are not the primary cell, the DCI processing capabilities of these three cells are not affected. For example, the network device can determine that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#3 within the aforementioned time domain unit; that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#4 within the aforementioned time domain unit; and that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#5 within the aforementioned time domain unit.

[0268] For example, a network device sends MC-DCI to a terminal on the scheduling cell cell#2. For example, the cells actually scheduled by the MC-DCI are cell#3, cell#4, and cell#5, specifically scheduling the PDSCH. When the first cell is cell#2, since the first upper limit of cell#2's processing capability for DCI used to schedule downlink transmissions per unit time is 1, the network device determines that after the terminal processes the MC-DCI used to schedule the PDSCHs of multiple cells on cell#2, it can no longer process unicast DCI used to schedule downlink transmissions on cell#2 in the time domain unit in which it receives the MC-DCI. However, since the first upper limit of the processing capability for DCI used to schedule uplink transmissions per unit time is 1, the network device can determine that the terminal can also process one more unicast DCI used to schedule uplink transmissions on cell#2 in the time domain unit in which it receives the MC-DCI.

[0269] Since cell#3, cell#4, and cell#5 are not the primary cell, the DCI processing capabilities of these three cells are not affected. For example, the network device can determine that, in the aforementioned time domain unit, the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#3; that, in the aforementioned time domain unit, the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#4; and that, in the aforementioned time domain unit, the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#5.

[0270] Taking the example of a cell that includes a cell among the cells actually scheduled by MC-DCI as the first cell, for example, it can be the cell with the smallest index or the largest index among the cells actually scheduled by MC-DCI. For example, if MC-DCI can schedule four cells, namely cell#2, cell#3, cell#4, and cell#5, then the cell set can be {cell#2, cell#3, cell#4, cell#5}, and the actually scheduled cells can be one or more cells in the cell set. Taking the example of a cell that includes the cell with the smallest index among the cells actually scheduled by MC-DCI as the first cell.

[0271] For example, a network device sends MC-DCI to a terminal on scheduling cell #1. For example, the cells actually scheduled by the MC-DCI are cell #2, cell #3, cell #4, and cell #5, specifically scheduling the PDSCH. Cell #2 has the smallest index, so cell #2 is selected as the first cell. Since the first upper limit of cell #2's processing capability for DCI used to schedule downlink transmissions per unit time is 1, the network device determines that after the terminal processes MC-DCI used to schedule PDSCHs of multiple cells on cell #2, it can no longer process unicast DCI used to schedule downlink transmissions on cell #2 within the time domain unit in which it receives MC-DCI. However, since the first upper limit of the processing capability for DCI used to schedule uplink transmissions per unit time is 1, the network device can determine that the terminal can process one more unicast DCI used to schedule uplink transmissions on cell #2 within the time domain unit in which it receives MC-DCI.

[0272] Since cell#3, cell#4, and cell#5 are not the primary cell, the DCI processing capabilities of these three cells are not affected. For example, the network device can determine that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#3 within the aforementioned time domain unit; that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#4 within the aforementioned time domain unit; and that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#5 within the aforementioned time domain unit.

[0273] For example, a network device sends MC-DCI to a terminal on scheduling cell #2. For example, the cells actually scheduled by the MC-DCI are cell #3, cell #4, and cell #5, specifically scheduling the PDSCH. Cell #3 has the smallest index, so cell #3 is selected as the first cell. Since the first upper limit of cell #3's processing capability for DCI used to schedule downlink transmissions per unit time is 1, the network device determines that after the terminal processes MC-DCI used to schedule PDSCHs of multiple cells on cell #3, the terminal can no longer process unicast DCI used to schedule downlink transmissions on cell #3 within the time domain unit in which it receives MC-DCI. However, since the first upper limit of the processing capability for DCI used to schedule uplink transmissions per unit time is 1, the network device can determine that the terminal can process one more unicast DCI used to schedule uplink transmissions on cell #3 within the time domain unit in which it receives MC-DCI.

[0274] Since cell#2, cell#4, and cell#5 are not the primary cell, the DCI processing capabilities of these three cells are not affected. For example, the network device can determine that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#2 within the aforementioned time domain unit; that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#4 within the aforementioned time domain unit; and that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#5 within the aforementioned time domain unit.

[0275] For example, a network device sends MC-DCI to a terminal on scheduling cell #2. For example, the cells actually scheduled by the MC-DCI are cell #4 and cell #5, specifically, the PDSCH. Cell #4 has the smallest index, so cell #4 is used as the first cell. Since the first upper limit of cell #4's processing capability for DCI used to schedule downlink transmissions per unit time is 1, after the terminal processes the MC-DCI used to schedule PDSCHs of multiple cells on cell #4, the network device determines that the terminal can no longer process unicast DCI used to schedule downlink transmissions on cell #4 within the time domain unit in which it receives the MC-DCI. However, since the first upper limit of the processing capability for DCI used to schedule uplink transmissions per unit time is 1, the network device can determine that the terminal can also process one more unicast DCI used to schedule uplink transmissions on cell #4 within the time domain unit in which it receives the MC-DCI.

[0276] Since cell#2, cell#3, and cell#5 are not reference cells, the DCI processing capabilities of these three cells are not affected. For example, the network device can determine that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#2 within the time domain unit; that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#3 within the time domain unit; and that the terminal can still process one unicast DCI for scheduling downlink transmission and one unicast DCI for scheduling uplink transmission in cell#5 within the time domain unit.

[0277] In some embodiments, terms such as "uplink", "uplink", "physical uplink" can be interchangeable with each other, and terms such as "downlink", "downlink", "physical downlink" can be interchangeable with each other, and terms such as "side", "sidelink", "side communication", "sidelink communication", "direct connection", "direct link", "direct communication", "direct link communication" can be interchangeable with each other.

[0278] In some embodiments, the terms "downlink control information (DCI)", "downlink (DL) assignment", "DL DCI", "uplink (UL) grant", "UL DCI" and the like may be used interchangeably.

[0279] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, and terms such as "physical uplink shared channel (PUSCH)" and "UL data" can be used interchangeably.

[0280] In some embodiments, terms such as "moment", "time point", "time", and "time position" can be replaced with each other, and terms such as "duration", "period", "time window", "window", and "time" can be replaced with each other.

[0281] In some embodiments, the terms "component carrier (CC)", "cell", "frequency carrier", "carrier frequency" and the like can be used interchangeably.

[0282] In some embodiments, terms such as "frame", "radio frame", "subframe", "slot", "sub-slot", "mini-slot", "symbol", "symbol", and "transmission time interval (TTI)" can be used interchangeably.

[0283] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0284] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0285] Corresponding to the aforementioned embodiment of the capability determination method, the present disclosure also provides an embodiment of a capability determination device.

[0286] FIG5 is a schematic block diagram of a capability determination device according to an embodiment of the present disclosure. As shown in FIG5 , the capability determination device includes: a processing module 501 .

[0287] In some embodiments, the processing module is configured to process downlink control information MC-DCI for scheduling multiple cells received in the scheduling cell; and count the number of processed MC-DCI according to the first cell's processing capability for unicast downlink control information.

[0288] In some embodiments, the first cell includes at least one of the following: a reference cell; the scheduling cell; a cell among the cells that can be scheduled by the MC-DCI; and a cell among the cells actually scheduled by the MC-DCI.

[0289] In some embodiments, the cells that can be scheduled by the MC-DCI are agreed upon by a protocol or configured by a network device.

[0290] In some embodiments, the cells that can be scheduled by the MC-DCI include at least one of the following: a cell with the smallest index among the cells that can be scheduled by the MC-DCI; and a cell with the largest index among the cells that can be scheduled by the MC-DCI.

[0291] In some embodiments, the cells in the cells actually scheduled by the MC-DCI are agreed upon by a protocol or configured by a network device.

[0292] In some embodiments, the cells in the cells actually scheduled by the MC-DCI include at least one of the following: a cell with a smallest index in the cells actually scheduled by the MC-DCI; and a cell with a largest index in the cells actually scheduled by the MC-DCI.

[0293] In some embodiments, the MC-DCI includes at least one of the following: a first MC-DCI for scheduling uplink transmission; and a second MC-DCI for scheduling downlink transmission.

[0294] In some embodiments, the processing module is further configured to determine a first count value for the first MC-DCI count; determine a first difference between a first upper limit value of the DCI for scheduling uplink transmission in the first cell's processing capability of unicast DCI and the first count value;

[0295] And, it is configured to determine, based on the first difference, the number of other unicast DCIs for scheduling uplink transmission that the terminal can process on the first cell in the scheduling cell within the unit time for receiving the first MC-DCI.

[0296] In some embodiments, the processing module is further configured to determine a second count value for the second MC-DCI count; determine a second difference between a second upper limit value of the DCI for scheduling downlink transmission in the first cell's processing capability of unicast DCI and the second count value;

[0297] And, it is configured to determine, based on the second difference, the number of other unicast DCIs for scheduling downlink transmission that the terminal can process on the first cell in the scheduling cell within the unit time for receiving the second MC-DCI.

[0298] It should be noted that the modules included in the capability determination device shown in FIG5 may not be limited to the modules shown in the figure, and may also include, for example, a storage module, a receiving module, a sending module, etc., which is not limited in the present disclosure.

[0299] FIG6 is a schematic block diagram of a capability determination device according to an embodiment of the present disclosure. As shown in FIG6 , the capability determination device includes: a sending module 601 and a processing module 602 .

[0300] In some embodiments, the sending module is configured to send downlink control information MC-DCI for scheduling multiple cells to the terminal in the scheduling cell; the processing module is configured to count the MC-DCI processed by the terminal according to the first cell's processing capability of unicast downlink control information.

[0301] In some embodiments, the first cell includes at least one of the following: a reference cell; the scheduling cell; a cell among the cells that can be scheduled by the MC-DCI; and a cell among the cells actually scheduled by the MC-DCI.

[0302] In some embodiments, the cells in the cells that can be scheduled by the MC-DCI are agreed upon by a protocol, or are configured by the network device.

[0303] In some embodiments, the cells that can be scheduled by the MC-DCI include at least one of the following: a cell with the smallest index among the cells that can be scheduled by the MC-DCI; and a cell with the largest index among the cells that can be scheduled by the MC-DCI.

[0304] In some embodiments, the cells in the cells actually scheduled by the MC-DCI are agreed upon by a protocol, or are configured by the network device.

[0305] In some embodiments, the cells in the cells actually scheduled by the MC-DCI include at least one of the following: a cell with a smallest index in the cells actually scheduled by the MC-DCI; and a cell with a largest index in the cells actually scheduled by the MC-DCI.

[0306] In some embodiments, the MC-DCI includes at least one of the following: a first MC-DCI for scheduling uplink transmission; and a second MC-DCI for scheduling downlink transmission.

[0307] In some embodiments, the processing module is further configured to determine a first count value of the number of times the terminal processes the first MC-DCI; determine a first difference between a first upper limit value of the DCI for scheduling uplink transmission in the first cell's processing capability of unicast DCI and the first count value;

[0308] And, the processing module is configured to determine, based on the first difference, the number of other unicast DCIs for scheduling uplink transmission that the terminal can process on the first cell in the scheduling cell within the unit time for receiving the first MC-DCI.

[0309] In some embodiments, the processing module is further configured to determine a second count value for counting the number of times the terminal processes the second MC-DCI; determine a second difference between a second upper limit value of the DCI for scheduling downlink transmission in the first cell's processing capability of unicast DCI and the second count value;

[0310] And, the processing module is configured to determine, based on the second difference, the number of other unicast DCIs for scheduling downlink transmission that the terminal can process on the first cell in the scheduling cell within the unit time for receiving the second MC-DCI.

[0311] It should be noted that the modules included in the capability determination device shown in FIG6 may not be limited to the modules shown in the figure, and may also include, for example, a storage module, a receiving module, etc., which is not limited in the present disclosure.

[0312] For the device embodiment, since it basically corresponds to the method embodiment, the relevant parts can be referred to the partial description of the method embodiment. The device embodiment described above is merely illustrative, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Those of ordinary skill in the art can understand and implement it without paying any creative work.

[0313] An embodiment of the present disclosure also proposes a capability determination method, including: a network device sends downlink control information MC-DCI for scheduling multiple cells to a terminal in a scheduling cell; the terminal processes the MC-DCI; and the terminal counts the processing of the MC-DCI based on the first cell's processing capability of unicast downlink control information.

[0314] An embodiment of the present disclosure also proposes a terminal, comprising: one or more processors; a memory coupled to the one or more processors, wherein the memory stores executable instructions, and when the executable instructions are executed by the one or more processors, the terminal executes the capability determination method described in any one of the first aspect and the optional embodiments of the first aspect.

[0315] An embodiment of the present disclosure also proposes a network device, comprising: one or more processors; a memory coupled to the one or more processors, wherein the memory stores executable instructions, and when the executable instructions are executed by the one or more processors, the network device executes the capability determination method described in any one of the second aspect and the optional embodiments of the second aspect.

[0316] An embodiment of the present disclosure also proposes a communication system, including a terminal and a network device, wherein the terminal is configured to implement the capability determination method described in any one of the first aspect and the optional embodiments of the first aspect, and the network device is configured to implement the capability determination method described in any one of the second aspect and the optional embodiments of the second aspect.

[0317] An embodiment of the present disclosure also proposes a storage medium storing instructions. When the instructions are executed on a communication device, the communication device executes the capability determination method described in any one of the first aspect, the optional embodiment of the first aspect, the second aspect, and the optional embodiment of the second aspect.

[0318] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0319] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0320] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0321] Figure 7 is a schematic diagram of the structure of a communication device 7100 proposed in an embodiment of the present disclosure. Communication device 7100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user equipment, etc.), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. Communication device 7100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0322] As shown in Figure 7, the communication device 7100 includes one or more processors 7101. The processor 7101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, baseband chip, terminal device, terminal device chip, DU or CU, etc.), execute programs, and process program data. The processor 7101 is used to call instructions to enable the communication device 7100 to perform any of the above methods.

[0323] In some embodiments, the communication device 7100 further includes one or more memories 7102 for storing instructions. Optionally, all or part of the memories 7102 may be located outside the communication device 7100.

[0324] In some embodiments, the communication device 7100 further includes one or more transceivers 7103. When the communication device 7100 includes one or more transceivers 7103, the communication steps such as sending and receiving in the above method are performed by the transceiver 7103, and the other steps are performed by the processor 7101.

[0325] In some embodiments, a transceiver may include a receiver and a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0326] Optionally, the communication device 7100 further includes one or more interface circuits 7104, which are connected to the memory 7102. The interface circuits 7104 may be configured to receive signals from the memory 7102 or other devices, and may be configured to send signals to the memory 7102 or other devices. For example, the interface circuits 7104 may read instructions stored in the memory 7102 and send the instructions to the processor 7101.

[0327] The communication device 7100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 7100 described in the present disclosure is not limited thereto, and the structure of the communication device 7100 may not be limited by FIG. 7 . The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0328] FIG8 is a schematic diagram of the structure of a chip 8200 according to an embodiment of the present disclosure. If the communication device 7100 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 8200 shown in FIG8 , but the present disclosure is not limited thereto.

[0329] The chip 8200 includes one or more processors 8201, and the processor 8201 is used to call instructions so that the chip 8200 executes any of the above methods.

[0330] In some embodiments, the chip 8200 further includes one or more interface circuits 8202, which are connected to the memory 8203. The interface circuit 8202 can be used to receive signals from the memory 8203 or other devices, and can be used to send signals to the memory.

[0331] 8203 or other devices to send signals. For example, the interface circuit 8202 can read the instructions stored in the memory 8203 and send the instructions to the processor 8201. Optionally, the terms interface circuit, interface, transceiver pin, transceiver, etc. can be used interchangeably.

[0332] In some embodiments, the chip 8200 further includes one or more memories 8203 for storing instructions. Alternatively, all or part of the memories 8203 may be outside the chip 8200.

[0333] The present disclosure also proposes a storage medium having instructions stored thereon. When the instructions are executed on the communication device 7100, the communication device 7100 executes any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a temporary storage medium.

[0334] The present disclosure also provides a program product, which, when executed by the communication device 7100, enables the communication device 7100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0335] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A capability determination method, characterized in that: Executed by a terminal, the method includes: Processing downlink control information MC-DCI for scheduling multiple cells received in the scheduling cell; The MC-DCI processing is counted according to the processing capability of the first cell for the unicast downlink control information.

2. The method according to claim 1, characterized in that The first cell includes at least one of the following: Reference cell; The scheduling cell; A cell among the cells that can be scheduled by the MC-DCI; The cell in the cell actually scheduled by the MC-DCI.

3. The method according to claim 2, characterized in that The cells that can be scheduled by the MC-DCI are agreed upon by the protocol or configured by the network device.

4. The method according to claim 2 or 3, characterized in that: The cells that can be scheduled by the MC-DCI include at least one of the following: The cell with the smallest index among the cells that can be scheduled by the MC-DCI; The cell with the largest index among the cells that can be scheduled by the MC-DCI.

5. The method according to claim 2, characterized in that: The cells in the cells actually scheduled by the MC-DCI are agreed upon by the protocol or configured by the network device.

6. The method according to claim 2 or 5, characterized in that: The cells actually scheduled by the MC-DCI include at least one of the following: The cell with the smallest index among the cells actually scheduled by the MC-DCI; The cell with the largest index among the cells actually scheduled by the MC-DCI.

7. The method according to any one of claims 1 to 6, characterized in that The MC-DCI includes at least one of the following: A first MC-DCI for scheduling uplink transmission; The second MC-DCI is used for scheduling downlink transmission.

8. The method according to claim 7, characterized in that The counting of processing the MC-DCI according to the processing capability of the first cell for the unicast downlink control information includes: Determine a first count value for counting the first MC-DCI; Determine a first difference between a first upper limit value of DCI for scheduling uplink transmission in the processing capability of the first cell for unicast DCI and the first count value; Wherein, the method further comprises: The number of other unicast DCIs for scheduling uplink transmission that can be processed by the terminal in the scheduling cell within a unit time for receiving the first MC-DCI is determined according to the first difference.

9. The method according to claim 7, characterized in that: The counting of processing the MC-DCI according to the processing capability of the first cell for the unicast downlink control information includes: Determine a second count value for counting the second MC-DCI; Determine a second difference between a second upper limit value of the DCI for scheduling downlink transmission in the processing capability of the first cell for unicast DCI and the second count value; Wherein, the method further comprises: The number of other unicast DCIs for scheduling downlink transmission that can be processed by the terminal in the scheduling cell within the unit time for receiving the second MC-DCI is determined according to the second difference.

10. A method for determining capability, characterized in that: Executed by a network device, the method includes: Sending downlink control information MC-DCI for scheduling multiple cells to the terminal in the scheduling cell; The MC-DCI count is performed on the terminal according to the processing capability of the first cell for unicast downlink control information.

11. The method according to claim 10, characterized in that The first cell includes at least one of the following: Reference cell; The scheduling cell; A cell among the cells that can be scheduled by the MC-DCI; The cell in the cell actually scheduled by the MC-DCI.

12. The method according to claim 11, characterized in that The cells in the cells that can be scheduled by the MC-DCI are agreed upon by the protocol or configured by the network device.

13. The method according to claim 11 or 12, characterized in that: The cells that can be scheduled by the MC-DCI include at least one of the following: The cell with the smallest index among the cells that can be scheduled by the MC-DCI; The cell with the largest index among the cells that can be scheduled by the MC-DCI.

14. The method according to claim 11, characterized in that The cells in the cells actually scheduled by the MC-DCI are agreed upon by the protocol, or are configured by the network device.

15. The method according to claim 11 or 14, characterized in that The cells actually scheduled by the MC-DCI include at least one of the following: The cell with the smallest index among the cells actually scheduled by the MC-DCI; The cell with the largest index among the cells actually scheduled by the MC-DCI.

16. The method according to any one of claims 10 to 15, characterized in that The MC-DCI includes at least one of the following: A first MC-DCI for scheduling uplink transmission; The second MC-DCI is used for scheduling downlink transmission.

17. The method according to claim 16, characterized in that The counting of processing the MC-DCI by the terminal according to the processing capability of the first cell for unicast downlink control information includes: Determine a first count value for counting the first MC-DCI processed by the terminal; Determine a first difference between a first upper limit value of DCI for scheduling uplink transmission in the processing capability of the first cell for unicast DCI and the first count value; Wherein, the method further comprises: The number of other unicast DCIs for scheduling uplink transmission that can be processed by the terminal in the scheduling cell within a unit time for receiving the first MC-DCI is determined according to the first difference.

18. The method according to claim 16, characterized in that The counting of processing the MC-DCI by the terminal according to the processing capability of the first cell for unicast downlink control information includes: Determine a second count value for counting the second MC-DCI processed by the terminal; Determine a second difference between a second upper limit value of the DCI for scheduling downlink transmission in the processing capability of the first cell for unicast DCI and the second count value; Wherein, the method further comprises: The number of other unicast DCIs for scheduling downlink transmission that can be processed by the terminal in the scheduling cell within the unit time for receiving the second MC-DCI is determined according to the second difference.

19. A capability determination device, characterized in that: Executed by a terminal, the device includes: The processing module is configured to process downlink control information MC-DCI for scheduling multiple cells received in the scheduling cell; and count the processing of the MC-DCI according to the processing capability of the first cell for unicast downlink control information.

20. A capability determination device, characterized in that: Executed by a network device, the apparatus comprises: A sending module, configured to send downlink control information MC-DCI for scheduling multiple cells to the terminal in the scheduling cell; The processing module is configured to count the MC-DCI processed by the terminal according to the processing capability of the first cell for unicast downlink control information.

21. A method for determining capability, characterized in that: include: The network device sends downlink control information MC-DCI for scheduling multiple cells to the terminal in the scheduling cell; The terminal processes the MC-DCI; The terminal counts the number of times the MC-DCI is processed according to the processing capability of the first cell for the unicast downlink control information.

22. A terminal, characterized in that: include: one or more processors; A memory coupled to the one or more processors, wherein executable instructions are stored in the memory, and when the one or more processors execute the executable instructions, the terminal executes the capability determination method according to any one of claims 1 to 9.

23. A network device, characterized in that: include: one or more processors; A memory coupled to the one or more processors, wherein executable instructions are stored in the memory, and when the one or more processors execute the executable instructions, the network device executes the capability determination method according to any one of claims 10 to 18.

24. A communication system, characterized in that: It comprises a terminal and a network device, wherein the terminal is configured to implement the capability determination method according to any one of claims 1 to 9, and the network device is configured to implement the capability determination method according to any one of claims 10 to 18.

25. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device is caused to perform the capability determination method according to any one of claims 1 to 9 and 10 to 18.

Images